A quick breakdown about the Blogforacure.com website can be found further down:
Aspect | Summary |
---|---|
Website load speed: | 2.8055s poor |
Number of (outgoing) links: | 85 |
HTML size: | 30.6 kilobytes Good |
meta-tag viewport | width=device-width, initial-scale=1, maximum-scale=1 |
HTTP/1.1 200 OK Date: Mon, 22 May 2017 20:56:48 GMT Server: Apache X-Powered-By: PHP/5.6.23 Set-Cookie: PHPSESSID=sgfpbc5kdkllc2u8439brohmd7; expires=Tue, 23-May-2017 10:56:48 GMT; Max-Age=50400; path=/; domain=.blogforacure.com; secure; HttpOnly Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Transfer-Encoding: chunked Content-Type: text/html; charset=UTF-8
The following domains are, too, hosted on 54.191.41.224:
Website address | IP in detail |
---|---|
54.191.41.224 blogforacure.com |
Strangely, no meta keywords are used by the website Blogforacure.com.
Based on A and B block, the following IP adresses are similar to 54.191.41.224
Website address | IP in detail |
---|---|
54.191.111.168 ec2-54-191-111-168.us-west-2.compute.amazonaws.com | |
54.191.0.26 ec2-54-191-0-26.us-west-2.compute.amazonaws.com | |
54.191.118.53 - | |
54.191.112.51 ec2-54-191-112-51.us-west-2.compute.amazonaws.com | |
54.191.103.237 ec2-54-191-103-237.us-west-2.compute.amazonaws.com | |
54.191.108.3 ec2-54-191-108-3.us-west-2.compute.amazonaws.com | |
54.191.123.10 ec2-54-191-123-10.us-west-2.compute.amazonaws.com | |
54.191.121.244 ec2-54-191-121-244.us-west-2.compute.amazonaws.com | |
54.191.117.91 ec2-54-191-117-91.us-west-2.compute.amazonaws.com | |
54.191.13.6 ec2-54-191-13-6.us-west-2.compute.amazonaws.com | |
54.191.0.206 ec2-54-191-0-206.us-west-2.compute.amazonaws.com | |
54.191.1.143 ec2-54-191-1-143.us-west-2.compute.amazonaws.com | |
54.191.115.171 ec2-54-191-115-171.us-west-2.compute.amazonaws.com | |
54.191.124.140 ec2-54-191-124-140.us-west-2.compute.amazonaws.com | |
54.191.107.90 ec2-54-191-107-90.us-west-2.compute.amazonaws.com | |
54.191.105.155 ec2-54-191-105-155.us-west-2.compute.amazonaws.com | |
54.191.116.26 ec2-54-191-116-26.us-west-2.compute.amazonaws.com | |
54.191.0.178 ec2-54-191-0-178.us-west-2.compute.amazonaws.com | |
54.191.103.182 - | |
54.191.121.80 ec2-54-191-121-80.us-west-2.compute.amazonaws.com | |
54.191.109.127 ec2-54-191-109-127.us-west-2.compute.amazonaws.com | |
54.191.12.39 ec2-54-191-12-39.us-west-2.compute.amazonaws.com | |
54.191.115.226 ec2-54-191-115-226.us-west-2.compute.amazonaws.com | |
54.191.127.235 ec2-54-191-127-235.us-west-2.compute.amazonaws.com | |
54.191.127.175 ec2-54-191-127-175.us-west-2.compute.amazonaws.com | |
54.191.127.46 ec2-54-191-127-46.us-west-2.compute.amazonaws.com | |
54.191.123.249 ec2-54-191-123-249.us-west-2.compute.amazonaws.com | |
54.191.120.95 ec2-54-191-120-95.us-west-2.compute.amazonaws.com | |
54.191.103.79 ec2-54-191-103-79.us-west-2.compute.amazonaws.com | |
54.191.1.212 ec2-54-191-1-212.us-west-2.compute.amazonaws.com | |
54.191.101.105 ec2-54-191-101-105.us-west-2.compute.amazonaws.com | |
54.191.127.156 ec2-54-191-127-156.us-west-2.compute.amazonaws.com | |
54.191.103.225 ec2-54-191-103-225.us-west-2.compute.amazonaws.com | |
54.191.111.86 ec2-54-191-111-86.us-west-2.compute.amazonaws.com | |
54.191.0.168 ec2-54-191-0-168.us-west-2.compute.amazonaws.com | |
54.191.115.155 ec2-54-191-115-155.us-west-2.compute.amazonaws.com | |
54.191.103.205 ec2-54-191-103-205.us-west-2.compute.amazonaws.com | |
54.191.119.38 - | |
54.191.120.116 ec2-54-191-120-116.us-west-2.compute.amazonaws.com | |
54.191.0.45 ec2-54-191-0-45.us-west-2.compute.amazonaws.com | |
54.191.114.184 - | |
54.191.124.243 ec2-54-191-124-243.us-west-2.compute.amazonaws.com | |
54.191.100.252 ec2-54-191-100-252.us-west-2.compute.amazonaws.com | |
54.191.104.146 ec2-54-191-104-146.us-west-2.compute.amazonaws.com | |
54.191.129.12 ec2-54-191-129-12.us-west-2.compute.amazonaws.com | |
54.191.1.133 ec2-54-191-1-133.us-west-2.compute.amazonaws.com | |
54.191.123.138 ec2-54-191-123-138.us-west-2.compute.amazonaws.com | |
54.191.125.61 ec2-54-191-125-61.us-west-2.compute.amazonaws.com | |
54.191.102.93 ec2-54-191-102-93.us-west-2.compute.amazonaws.com | |
54.191.129.80 ec2-54-191-129-80.us-west-2.compute.amazonaws.com |
The following domain extensions are available for the domain name, with a total of 730 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: | 960,720 spotted 3,775 days ago |
---|---|
Current rating: | 691,359 spotted 3,162 days ago |
Best rating: | 375,354 spotted 3,200 days ago |
Average rating: | 555,936 |
Visitors frequently mistype blogforacure.com.
Here is a list of most common misspellings:
It seems blogforacure.com 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.
Current rating: | 49,329 spotted 3,751 days ago |
---|---|
Worst rating: | 69,528 spotted 3,792 days ago |
Best rating: | 49,329 spotted 3,751 days ago |
Average rating: | 61,746 |
Other lists the domain blogforacure.com appears in are: