A quick breakdown about the Cur.to website can be found further down:
Aspect | Summary |
---|---|
Website load speed: | 0.4542s this is quite good! |
Number of (outgoing) links: | 15 |
HTML size: | 5.9 kilobytes Good |
meta-tag csrf-token | baNBHSGmFYnCPLgG5issGWm5+cAgTMK2M2Pnfx5xXotxjKDDl8NHchauBICixzEwrPugA68C4I4vnPP4hTgUtg== |
meta-tag og:title | Cur.to - Social networks aggregator based on topics (hashtags) |
meta-tag og:url | http://cur.to/ |
meta-tag og:description | Type cur.to/hashtag in your browser address bar to follow the topic on social networks (tip: cur.to/soccer |
meta-tag og:image | http://cur.to/images/fb-share-logo.png |
meta-tag csrf-param | authenticity_token |
meta-tag viewport | width=device-width, user-scalable=no |
HTTP/1.1 200 OK Connection: keep-alive X-Frame-Options: SAMEORIGIN X-Xss-Protection: 1; mode=block X-Content-Type-Options: nosniff Content-Type: text/html; charset=utf-8 Etag: W/"e6450674807a9da237265b1ecc6a67dd" Cache-Control: max-age=0, private, must-revalidate X-Request-Id: 3411aef3-842e-4857-83ca-2e3d037a491f X-Runtime: 0.012724 Server: WEBrick/1.3.1 (Ruby/2.0.0/2015-04-13) Date: Wed, 13 Jul 2016 10:36:47 GMT Content-Length: 6068 Set-Cookie: _curto_session=VmV2YTlucGtFUGIyUjgwb2ZvR1A1ZWJ1S1hqZElubmhwTm4rN2VTQjRpRmx6bUliNVYxR3NqQlUrczdpdEs5dGhmd0ZwU0pKOHAwQ0d2bmhFbEhEN0trTkdlQmV4ZFlPOGNCenhrZjIyY2lMeXQ1ZG56Uzg5bVpNbnhuVDVnU2FuV2I2TVphQ3J0ZjNKdHlSamVIVDlZdTdvZi9XY2lERTJkdzVCaHFIYUtrM01pOElhdnZyNlVycG1YUXYxTnZLLS1HcGFvcnBPaXpLVUhFdDQxVEpsR1B3PT0%3D--58df6b91625ebf981db94f0a345af89351bb2b11; path=/; HttpOnly Via: 1.1 vegur
The following domains are, too, hosted on 54.243.209.176:
A total of 12 keywords are used by the website
Based on A and B block, the following IP adresses are similar to 54.243.209.176
Website address | IP in detail |
---|---|
54.243.105.104 ec2-54-243-105-104.compute-1.amazonaws.com | |
54.243.101.112 ec2-54-243-101-112.compute-1.amazonaws.com | |
54.243.107.130 ec2-54-243-107-130.compute-1.amazonaws.com | |
54.243.105.198 ec2-54-243-105-198.compute-1.amazonaws.com | |
54.243.103.182 ec2-54-243-103-182.compute-1.amazonaws.com | |
54.243.104.48 ec2-54-243-104-48.compute-1.amazonaws.com | |
54.243.108.183 ec2-54-243-108-183.compute-1.amazonaws.com | |
54.243.108.111 ec2-54-243-108-111.compute-1.amazonaws.com | |
54.243.106.42 ec2-54-243-106-42.compute-1.amazonaws.com | |
54.243.110.180 ec2-54-243-110-180.compute-1.amazonaws.com | |
54.243.100.70 ec2-54-243-100-70.compute-1.amazonaws.com | |
54.243.101.230 ec2-54-243-101-230.compute-1.amazonaws.com | |
54.243.106.213 ec2-54-243-106-213.compute-1.amazonaws.com | |
54.243.109.100 ec2-54-243-109-100.compute-1.amazonaws.com | |
54.243.104.37 ec2-54-243-104-37.compute-1.amazonaws.com | |
54.243.104.3 ec2-54-243-104-3.compute-1.amazonaws.com | |
54.243.106.231 ec2-54-243-106-231.compute-1.amazonaws.com | |
54.243.100.148 ec2-54-243-100-148.compute-1.amazonaws.com | |
54.243.102.244 ec2-54-243-102-244.compute-1.amazonaws.com | |
54.243.108.169 ec2-54-243-108-169.compute-1.amazonaws.com | |
54.243.104.72 ec2-54-243-104-72.compute-1.amazonaws.com | |
54.243.107.167 ec2-54-243-107-167.compute-1.amazonaws.com | |
54.243.106.214 ec2-54-243-106-214.compute-1.amazonaws.com | |
54.243.109.167 ec2-54-243-109-167.compute-1.amazonaws.com | |
54.243.109.147 ec2-54-243-109-147.compute-1.amazonaws.com | |
54.243.110.123 ec2-54-243-110-123.compute-1.amazonaws.com | |
54.243.108.235 ec2-54-243-108-235.compute-1.amazonaws.com | |
54.243.107.232 ec2-54-243-107-232.compute-1.amazonaws.com | |
54.243.103.225 ec2-54-243-103-225.compute-1.amazonaws.com | |
54.243.101.238 ec2-54-243-101-238.compute-1.amazonaws.com | |
54.243.101.54 ec2-54-243-101-54.compute-1.amazonaws.com | |
54.243.109.139 ec2-54-243-109-139.compute-1.amazonaws.com | |
54.243.103.140 ec2-54-243-103-140.compute-1.amazonaws.com | |
54.243.105.17 ec2-54-243-105-17.compute-1.amazonaws.com | |
54.243.100.110 ec2-54-243-100-110.compute-1.amazonaws.com | |
54.243.106.15 ec2-54-243-106-15.compute-1.amazonaws.com | |
54.243.103.107 ec2-54-243-103-107.compute-1.amazonaws.com | |
54.243.107.135 ec2-54-243-107-135.compute-1.amazonaws.com | |
54.243.107.181 ec2-54-243-107-181.compute-1.amazonaws.com | |
54.243.101.119 ec2-54-243-101-119.compute-1.amazonaws.com | |
54.243.106.123 elitesitesdirectory.com | |
54.243.109.104 ec2-54-243-109-104.compute-1.amazonaws.com | |
54.243.101.244 ec2-54-243-101-244.compute-1.amazonaws.com | |
54.243.104.136 ec2-54-243-104-136.compute-1.amazonaws.com | |
54.243.110.152 ec2-54-243-110-152.compute-1.amazonaws.com | |
54.243.101.155 ec2-54-243-101-155.compute-1.amazonaws.com | |
54.243.108.222 ec2-54-243-108-222.compute-1.amazonaws.com | |
54.243.109.105 ec2-54-243-109-105.compute-1.amazonaws.com | |
54.243.101.66 ec2-54-243-101-66.compute-1.amazonaws.com | |
54.243.110.166 ec2-54-243-110-166.compute-1.amazonaws.com |
The following domain extensions are available for the domain name, with a total of 731 variations available:
As mentioned by Alexa on their official page, the Alexa rank or rating is calculated using a number of different parameters, such as daily average of unique visitors as well as pageviews over the last three months. The more unique visitors and pageviews, the higher the overall rank.
Lowest rating: | 964,783 spotted 3,198 days ago |
---|---|
Current rating: | 928,202 spotted 3,188 days ago |
Best rating: | 553,052 spotted 3,738 days ago |
Average rating: | 687,664 |
Visitors frequently mistype cur.to.
Here is a list of most common misspellings:
It seems cur.to has only been registered once and was never abandoned or has never expired.
Established in 2006, the technology company Quantcast provides audience measurements and an opportunity for advertising in real time. In addition to that, the American company ensures public access to all sorts of website-related data (traffic and demographic) for millions of websites, as well as in-depth user insights to digital bloggers and publishers enrolled in Quantcast's Quantified Publisher Program. The processing capability provided by Quantcast is impressive – over 800 thousand transactions per second, with, as claimed by the company, accurate audience calculation for over 100 million online destinations. In 2013, Quantcast was widely believed to be among the top five of world's largest data processing companies. Holding offices in London, Dublin, New York and Chicago, the main headquarters of Quantcast is in San Francisco, CA.
Unfortunately, our database contains no Quantcast rank data for Cur.to at this time.
Other lists the domain cur.to appears in are: