Autofocus.Ca - Info autofocus.ca

autofocus.ca receives about 102 unique visitors and 102 (1.00 per visitor) page views per day which should earn about $0.42/day from advertising revenue. Estimated site value is $191.51. According to Alexa Traffic Rank autofocus.ca is ranked number 4,538,570 in the world and 6.0E-6% of global Internet users visit it. Site is hosted in Toronto, Ontario, M5V, Canada and links to network IP address 199.85.66.27. This server supports HTTPS and HTTP/2.

About - autofocus.ca


Technologies used on Website

Currently Not Available

autofocus.ca Profile

Title: Autofocus.ca
Description: Autofocus.ca
Keywords: autofocus is your source for auto news, new 2014 cars, auto show info & new car prices. get news, photos & videos, tips & advice on how to maintain your car.
Last update was 173 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with autofocus.ca in any way. Only publicly available statistics data are displayed.

How popular is autofocus.ca?

102 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
102
Monthly Unique Visitors:
2,448
Pages per Visit:
1.00
Daily Pageviews:
102
Alexa Rank:
4,538,570 visit alexa
Alexa Reach:
6.0E-6%   (of global internet users)
Avg. visit duration:
02:24
Bounce rate:
89.50%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
0%
Referral:
17.03%
Search:
76.98%
Social:
5.99%
Paid:
0%

Visitors by country

Users%Pageviews%Rank
Canada 51.6%71.3%8463
France 20.1%10.3%42898
United States 7.9%4.5%397967

Where do visitors go on this site?

Reach%Pageviews%PerUser
autofocus.ca
74.00%74.00%1
OTHER
0%26.00%0

Competitive Data

SEMrush
Domain:
  autofocus.ca
Rank:
(Rank based on keywords, cost and organic traffic)
  3,005,258
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  18,326
Organic Traffic:
(Number of visitors coming from top 20 search results)
  3,138
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $1,507.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  53
Page Authority:
  41
MozRank:
  4

+ How socially engaged is autofocus.ca?

Facebook:
  3
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
autofocus.ca
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
autofocus.ca
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much autofocus.ca can earn?

Daily Revenue:
$0.42
Monthly Revenue:
$12.60
Yearly Revenue:
$153.30
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Canada 73$0.51
United States 5$0.05
France 11$0.05

How much money do autofocus.ca lose due to Adblock?

Daily Revenue Loss:
$0.14
Monthly Revenue Loss:
$4.27
Yearly Revenue Loss:
$51.96
Daily Pageviews Blocked:
20
Monthly Pageviews Blocked:
605
Yearly Pageviews Blocked:
7,360
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Canada 18$0.13
United States 1$0.01
France 1$0.01

How much is autofocus.ca worth?

Website Value:
$191.51

+ Where is autofocus.ca hosted?

Server IP:
199.85.66.27
ASN:
AS53829 
ISP:
CTV Television Network Limited 
Server Location:
Toronto
Ontario, ON
M5V
Canada, CA
 

Other sites hosted on 199.85.66.27

+ How fast does autofocus.ca load?

Average Load Time:
(2504 ms) 32 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

First Meaningful Paint 0.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 0.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.6 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Keep request counts low and transfer sizes small - 5 requests • 44 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
544 KB
Image
142 KB
Document
11 KB
Stylesheet
11 KB
Other
21 KB
Media
00 KB
Font
00 KB
Script
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 70 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://www.autofocus.ca/styles.css
1 KB70
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://autofocus.ca/
0 ms73 ms0 KB0 KB301text/html
http://www.autofocus.ca/index.html
74 ms205 ms0 KB0 KB301
https://www.autofocus.ca/index.html
205 ms439 ms1 KB1 KB200text/htmlDocument
https://www.autofocus.ca/styles.css
449 ms470 ms1 KB1 KB200text/cssStylesheet
https://www.autofocus.ca/logo.png
472 ms515 ms42 KB41 KB200image/pngImage
Uses efficient cache policy on static assets - 2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://www.autofocus.ca/logo.png
86391000 ms42 KB
https://www.autofocus.ca/styles.css
86400000 ms1 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
472 ms
6 ms
503 ms
9 ms
Avoids enormous network payloads - Total size was 44 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.autofocus.ca/logo.png
42 KB
https://www.autofocus.ca/index.html
1 KB
https://www.autofocus.ca/styles.css
1 KB
http://autofocus.ca/
0 KB
http://www.autofocus.ca/index.html
0 KB
Minimizes main-thread work - 0.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Other
11 ms
Style & Layout
9 ms
Script Evaluation
3 ms
Parse HTML & CSS
1 ms
Rendering
1 ms
Script Parsing & Compilation
1 ms
Serve images in next-gen formats - Potential savings of 34 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
https://www.autofocus.ca/logo.png
41 KB34 KB
Avoids an excessive DOM size - 14 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
14
Maximum DOM Depth
6
Maximum Child Elements
3
Avoid multiple page redirects - Potential savings of 380 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://autofocus.ca/)
0
http://www.autofocus.ca/index.html
190
https://www.autofocus.ca/index.html
190
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 230 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

JavaScript execution time
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Minimize Critical Requests Depth - 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

99
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 1.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
First Contentful Paint (3G) 3720 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Speed Index 2.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.9 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 1.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoid multiple page redirects - Potential savings of 1,260 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://autofocus.ca/)
0
http://www.autofocus.ca/index.html
630
https://www.autofocus.ca/index.html
630
Keep request counts low and transfer sizes small - 5 requests • 44 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
544 KB
Image
142 KB
Document
11 KB
Stylesheet
11 KB
Other
21 KB
Media
00 KB
Font
00 KB
Script
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 180 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://www.autofocus.ca/styles.css
1 KB180
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://autofocus.ca/
0 ms117 ms0 KB0 KB301text/html
http://www.autofocus.ca/index.html
117 ms275 ms0 KB0 KB301
https://www.autofocus.ca/index.html
275 ms426 ms1 KB1 KB200text/htmlDocument
https://www.autofocus.ca/styles.css
437 ms892 ms1 KB1 KB200text/cssStylesheet
https://www.autofocus.ca/logo.png
895 ms931 ms42 KB41 KB200image/pngImage
Uses efficient cache policy on static assets - 2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://www.autofocus.ca/styles.css
86150000 ms1 KB
https://www.autofocus.ca/logo.png
86396000 ms42 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
449 ms
7 ms
915 ms
11 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
118 ms11 ms3 ms
Avoids enormous network payloads - Total size was 44 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.autofocus.ca/logo.png
42 KB
https://www.autofocus.ca/index.html
1 KB
https://www.autofocus.ca/styles.css
1 KB
http://autofocus.ca/
0 KB
http://www.autofocus.ca/index.html
0 KB
Minimizes main-thread work - 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Other
51 ms
Style & Layout
43 ms
Script Evaluation
11 ms
Rendering
5 ms
Parse HTML & CSS
5 ms
Script Parsing & Compilation
3 ms
Serve images in next-gen formats - Potential savings of 34 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
https://www.autofocus.ca/logo.png
41 KB34 KB
Avoids an excessive DOM size - 14 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
14
Maximum DOM Depth
6
Maximum Child Elements
3
Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 150 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Minimize Critical Requests Depth - 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://autofocus.ca/
http://www.autofocus.ca/index.html
https://www.autofocus.ca/index.html

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Optimize CSS Delivery of the following:

https://www.autofocus.ca/styles.css

Reduce server response time

In our test, your server responded in 0.29 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://www.autofocus.ca/logo.png (24 hours)
https://www.autofocus.ca/styles.css (24 hours)
Optimize images
Your images are optimized. Learn more about optimizing images.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does autofocus.ca use compression?

autofocus.ca use gzip compression.
Original size: 1.3 KB
Compressed size: 581 B
File reduced by: 750 B (56%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

autofocus.ca supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: sports.bellmedia.ca
Organization:
Location:
Issuer: Entrust Certification Authority - L1K
Valid from: May 30 17:05:13 2019 GMT
Valid until: Mar 10 17:35:12 2021 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

autofocus.ca supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Wed, 19 Jun 2019 23:32:05 GMT
Location: http://www.autofocus.ca/index.html
Content-Length: 242
Content-Type: text/html; charset=iso-8859-1
Set-Cookie: TS011c596f=01881d1d7e12db0dc87d7ca396e9f9379970ea9ce98bce72f9c7f561a5339567e5d402ec60709187d3052df29478ef7b090d49e864; Path=/

HTTP/1.1 301 Moved Permanently
Server: AkamaiGHost
Content-Length: 0
Location: https://www.autofocus.ca/index.html
Date: Wed, 19 Jun 2019 23:32:04 GMT
Connection: keep-alive

HTTP/2 200 
last-modified: Thu, 20 Dec 2018 16:01:51 GMT
etag: "533-57d763faecc39"
accept-ranges: bytes
content-type: text/html; charset=UTF-8
content-encoding: gzip
content-length: 581
expires: Wed, 19 Jun 2019 23:32:05 GMT
cache-control: max-age=0, no-cache, no-store
pragma: no-cache
date: Wed, 19 Jun 2019 23:32:05 GMT
vary: Accept-Encoding
set-cookie: TS011c596f=01881d1d7e27293ed86eb01d4b773321d054c532e84b3a59de4719d8214dd1896288972d589e249eba7671f9349906bd31a1c8f129; Path=/

+ DNS Lookup

Type Ip Target TTL
TXT 300
TXT 300
MX mx-wyn.bell.ca 120
MX mx-dor.bell.ca 120
SOA 900
Mname ns-1367.awsdns-42.org
Rname awsdns-hostmaster.amazon.com
Serial Number 1
Refresh 7200
Retry 900
Expire 1209600
Minimum TTL 0
A 199.85.66.27 300
NS ns-1876.awsdns-42.co.uk 3600
NS ns-1367.awsdns-42.org 3600
NS ns-1011.awsdns-62.net 3600
NS ns-51.awsdns-06.com 3600

+ Whois Lookup

Domain Created:
2004-11-19
Domain Age:
14 years 7 months  
WhoIs:
 

whois lookup at whois.cira.ca...
Domain Name: autofocus.ca
Registry Domain ID: D240567-CIRA
Registrar WHOIS Server: whois.ca.fury.ca
Registrar URL: Markmonitor.com
Updated Date: 2019-04-30T16:03:59Z
Creation Date: 2004-11-19T19:00:08Z
Registry Expiry Date: 2022-11-19T05:00:00Z
Registrar: MarkMonitor International Canada Ltd.
Registrar IANA ID:
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID: 74018904-CIRA
Registrant Name: Bell Media Inc.
Registrant Organization:
Registrant Street: 9 Channel Nine Court
Registrant City: Scarborough
Registrant State/Province: ON
Registrant Postal Code: M1S4B5
Registrant Country: CA
Registrant Phone: +1.4163846000
Registrant Phone Ext:
Registrant Fax: +1.5148704833
Registrant Fax Ext:
Registrant Email: email
Registry Admin ID: 74022352-CIRA
Admin Name: Claudia Mack
Admin Organization: Bell Media Inc.
Admin Street: 9 Channel Nine Court
Admin City: Scarborough
Admin State/Province: ON
Admin Postal Code: M1S4B5
Admin Country: CA
Admin Phone: +1.4163846000
Admin Phone Ext:
Admin Fax: +1.5148704833
Admin Fax Ext:
Admin Email: email
Registry Tech ID: 74022352-CIRA
Tech Name: Claudia Mack
Tech Organization: Bell Media Inc.
Tech Street: 9 Channel Nine Court
Tech City: Scarborough
Tech State/Province: ON
Tech Postal Code: M1S4B5
Tech Country: CA
Tech Phone: +1.4163846000
Tech Phone Ext:
Tech Fax: +1.5148704833
Tech Fax Ext:
Tech Email: email
Registry Billing ID: 7388***04-CIRA
Billing Name: CCOPS Billing
Billing Organization: MarkMonitor Inc.
Billing Street: 3540 East Longwing Lane, Suite 300
Billing City: Meridian
Billing State/Province: ID
Billing Postal Code: 83646
Billing Country: US
Billing Phone: +1.2083895740
Billing Phone Ext:
Billing Fax: +1.2083895771
Billing Fax Ext:
Billing Email: email
Name Server: ns-51.awsdns-06.com
Name Server: ns-1367.awsdns-42.org
Name Server: ns-1876.awsdns-42.co.uk
Name Server: ns-1011.awsdns-62.net
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2019-06-19T23:30:21Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

%
% Use of CIRA's WHOIS service is governed by the Terms of Use in its Legal
% Notice, available at http://www.cira.ca/legal-notice/?lang=en
%
% (c) 2019 Canadian Internet Registration Authority, (http://www.cira.ca/)
Last update was 173 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with autofocus.ca in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

clicars.com
3 secs
system.szps.pl
20 secs
helpree.com
38 secs
cydia.7evasi0n.com
58 secs
synskonline.se
1 min
hdadelhi.com
1 min
sycourse.com
2 mins
harpreetmunjal.com
3 mins
swingingheaven.ca
3 mins
gumofiro.net
4 mins

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
autofocus.ca widget