Google.Cn - Info google.cn

google.cn receives about 16,103,683 unique visitors and 194,854,568 (12.10 per visitor) page views per day which should earn about $711,002.88/day from advertising revenue. Estimated site value is $523,226,364.24. According to Alexa Traffic Rank google.cn is ranked number 115 in the world and 0.355% of global Internet users visit it. Site is hosted in Draper, Utah, 84020, United States and links to network IP address 216.58.192.195. This server supports HTTPS and doesn't support HTTP/2.

About - google.cn


Technologies used on Website

Currently Not Available

google.cn Profile

Title: Google
Keywords: google
Last update was 183 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is google.cn?

16.1M daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
16,103,683
Monthly Unique Visitors:
386,488,392
Pages per Visit:
12.10
Daily Pageviews:
194,854,568
Alexa Rank:
115 visit alexa
Alexa Reach:
0.355%   (of global internet users)
Avg. visit duration:
10:30
Bounce rate:
31.39%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
80.86%
Referral:
1.29%
Search:
17.61%
Social:
0.09%
Paid:
0.01%

Visitors by country

Users%Pageviews%Rank
China 84.7%73.3%33
Japan 4.4%1.8%292
Hong Kong 3.7%14.4%18
United States 2.6%6.8%751
Germany 0.7%0.1%1429
Macao 0.6%2.1%8

Where do visitors go on this site?

Reach%Pageviews%PerUser
translate.google.cn
73.59%89.90%14.4
google.cn
35.31%9.78%3.26
android.google.cn
0.46%0.10%2.5
OTHER
0%0.21%0

Competitive Data

SEMrush
Domain:
  google.cn
Rank:
(Rank based on keywords, cost and organic traffic)
  4,521
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  17,113
Organic Traffic:
(Number of visitors coming from top 20 search results)
  626,446
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $1,827,251.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  1
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  695
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $278.00

+ Moz Data

Domain Authority:
  91
Page Authority:
  64
MozRank:
  6

+ How socially engaged is google.cn?

Facebook:
  2
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:
google.cn
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:
google.cn
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 google.cn can earn?

Daily Revenue:
$711,002.88
Monthly Revenue:
$21,330,086.40
Yearly Revenue:
$259,516,051.20
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
China 142,828,398$441,339.75
United States 13,250,111$151,978.77
Hong Kong 28,059,058$96,803.75
Japan 3,507,382$11,223.62
Macao 4,091,946$8,715.84
Germany 194,855$941.15

How much money do google.cn lose due to Adblock?

Daily Revenue Loss:
$95,194.68
Monthly Revenue Loss:
$2,855,840.38
Yearly Revenue Loss:
$34,746,057.96
Daily Pageviews Blocked:
24,002,186
Monthly Pageviews Blocked:
720,065,571
Yearly Pageviews Blocked:
8,760,797,775
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
China 18,567,692$57,374.17
United States 2,385,020$27,356.18
Hong Kong 2,805,906$9,680.37
Japan 105,221$336.71
Germany 56,508$272.93
Macao 81,839$174.32

How much is google.cn worth?

Website Value:
$523,226,364.24

+ Where is google.cn hosted?

Server IP:
216.58.192.195
ASN:
AS15169 
ISP:
Google LLC 
Server Location:
Draper
Utah, UT
84020
United States, US
 

Other sites hosted on 216.58.192.195

+ How fast does google.cn load?

Average Load Time:
(2116 ms) 39 % 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 FAST 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.

First Contentful Paint (FCP)842ms 80% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 80% 15% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 15% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
First Input Delay (FID)12ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 0% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Origin Data

All pages served from this origin have an FAST 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.

First Contentful Paint (FCP)883ms 79% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 79% 17% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 17% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
First Input Delay (FID)13ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 0% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

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 0.4 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.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. 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.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 0.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.4 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.4 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.

Avoids an excessive DOM size - 13 elements
A large DOM will 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
13
Maximum DOM Depth
5
Maximum Child Elements
3
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://google.cn/)
0
http://www.google.cn/
190
Keep request counts low and transfer sizes small - 4 requests • 28 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
428 KB
Image
225 KB
Document
12 KB
Other
10 KB
Stylesheet
00 KB
Media
00 KB
Font
00 KB
Script
00 KB
Third-party
00 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://google.cn/
0 ms24 ms0 KB0 KB301text/html
http://www.google.cn/
25 ms38 ms2 KB3 KB200text/htmlDocument
http://www.google.cn/landing/cnexp/google-search.png
52 ms58 ms23 KB23 KB200image/pngImage
http://www.google.cn/intl/zh-CN_cn/images/cn_icp.gif
56 ms114 ms2 KB2 KB404text/htmlImage
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
68 ms
9 ms
81 ms
58 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
80 ms3 ms1 ms
Properly size images - Potential savings of 17 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
http://www.google.cn/landing/cnexp/google-search.png
23 KB17 KB
Avoids enormous network payloads - Total size was 28 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://www.google.cn/landing/cnexp/google-search.png
23 KB
http://www.google.cn/
2 KB
http://www.google.cn/intl/zh-CN_cn/images/cn_icp.gif
2 KB
http://google.cn/
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. Learn more.

Category
Time Spent
Style & Layout
53 ms
Other
14 ms
Rendering
7 ms
Script Evaluation
3 ms
Parse HTML & CSS
2 ms
Script Parsing & Compilation
2 ms
Serve images in next-gen formats - Potential savings of 10 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
http://www.google.cn/landing/cnexp/google-search.png
23 KB10 KB
Avoid chaining critical requests - 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.

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 10 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. 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.

Uses efficient cache policy on static assets - 0 resources found
A long cache lifetime can speed up repeat visits to your page. 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.

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.


Page Speed (Google PageSpeed Insights) - Mobile

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE 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.

First Contentful Paint (FCP)1.1s 80% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 71% 23% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 23% 5% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 5%
First Input Delay (FID)286ms 0% of loads for this page have a fast (<100ms) First Input Delay (FID) 0% 96% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 96% 2% of loads for this page have a slow (>300ms) First Input Delay (FID) 2%

Origin Data

All pages served from this origin have an AVERAGE 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.

First Contentful Paint (FCP)1.5s 60% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 60% 29% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 29% 9% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 9%
First Input Delay (FID)295ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 2% 92% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 92% 4% of loads for this page have a slow (>300ms) First Input Delay (FID) 4%

Lab Data

First Meaningful Paint 1.3 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.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
First Contentful Paint (3G) 2460 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. 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.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 1.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.3 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.3 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 - 4 requests • 28 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
428 KB
Image
225 KB
Document
12 KB
Other
10 KB
Stylesheet
00 KB
Media
00 KB
Font
00 KB
Script
00 KB
Third-party
00 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://google.cn/
0 ms11 ms0 KB0 KB301text/html
http://www.google.cn/
12 ms56 ms2 KB3 KB200text/htmlDocument
http://www.google.cn/landing/cnexp/google-search.png
68 ms76 ms23 KB23 KB200image/pngImage
http://www.google.cn/intl/zh-CN_cn/images/cn_icp.gif
72 ms123 ms2 KB2 KB404text/htmlImage
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
87 ms
8 ms
100 ms
49 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
284 ms8 ms4 ms
Avoids enormous network payloads - Total size was 28 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://www.google.cn/landing/cnexp/google-search.png
23 KB
http://www.google.cn/
2 KB
http://www.google.cn/intl/zh-CN_cn/images/cn_icp.gif
2 KB
http://google.cn/
0 KB
Minimizes main-thread work - 0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Style & Layout
183 ms
Other
55 ms
Rendering
22 ms
Parse HTML & CSS
12 ms
Script Evaluation
10 ms
Script Parsing & Compilation
6 ms
Serve images in next-gen formats - Potential savings of 10 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
http://www.google.cn/landing/cnexp/google-search.png
23 KB10 KB
Avoids an excessive DOM size - 13 elements
A large DOM will 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
13
Maximum DOM Depth
5
Maximum Child Elements
3
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://google.cn/)
0
http://www.google.cn/
630
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 50 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. 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.

Uses efficient cache policy on static assets - 0 resources found
A long cache lifetime can speed up repeat visits to your page. 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.

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.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. 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.

Avoid chaining critical requests - 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.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

google.com.hk renders only 8 pixels tall (20 CSS pixels) .
请收藏我们的网址 renders only 5 pixels tall (13 CSS pixels) .
翻译 renders only 5 pixels tall (13 CSS pixels) .
©2011 - renders only 4 pixels tall (10 CSS pixels) .
ICP证合字B2-20070004号 renders only 4 pixels tall (10 CSS pixels) .

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="http://transla…?sourceid=cnhp">翻译</a> is close to 1 other tap targets .
The tap target <a href="http://www.miibeian.gov.cn/">ICP证合字B2-20070004号</a> is close to 1 other tap targets .
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
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.
Enable compression
You have compression enabled. Learn more about enabling compression.
Leverage browser caching
You have enabled browser caching. Learn more about browser caching recommendations.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Eliminate render-blocking JavaScript and CSS in above-the-fold content
You have no render-blocking resources. Learn more about removing render-blocking resources.
Optimize images
Your images are optimized. Learn more about optimizing images.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does google.cn use compression?

google.cn use gzip compression.
Original size: 1.41 KB
Compressed size: 1.41 KB
File reduced by: n/a

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  91
Vendor reliability:
  91
Privacy:
  91
Child safety:
  89

+ SSL Checker - SSL Certificate Verify

google.cn supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: google.com
Organization: Google LLC
Location: Mountain View, California, US
Issuer: GTS CA 1O1
Valid from: Nov 5 07:48:15 2019 GMT
Valid until: Jan 28 07:48:15 2020 GMT
Authority: Is not a CA
Keysize:
Common Name: GTS CA 1O1
Organization: Google Trust Services
Location: US
Issuer: GlobalSign
Valid from: Jun 15 00:00:42 2017 GMT
Valid until: Dec 15 00:00:42 2021 GMT
Authority: Is a CA
Keysize: 2048 Bits

+ Verify HTTP/2 Support

google.cn does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Location: http://www.google.cn/
Content-Type: text/html; charset=UTF-8
Date: Tue, 26 Nov 2019 11:05:10 GMT
Expires: Thu, 26 Dec 2019 11:05:10 GMT
Cache-Control: public, max-age=2592000
Server: gws
Content-Length: 218
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN

HTTP/1.1 200 OK
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Type: text/html
Content-Security-Policy-Report-Only: script-src 'nonce-J2gOQeHH2X1NJWILrGXfYQ' 'strict-dynamic' 'unsafe-eval' 'unsafe-inline' http: https:; object-src 'none'; report-uri https://csp.withgoogle.com/csp/static-on-bigtable; base-uri 'none'
Content-Length: 1443
Date: Tue, 26 Nov 2019 11:05:10 GMT
Pragma: no-cache
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Cache-Control: no-cache, must-revalidate
Last-Modified: Thu, 03 Oct 2019 12:00:00 GMT
X-Content-Type-Options: nosniff
Content-Encoding: gzip
Server: sffe
X-XSS-Protection: 0

+ DNS Lookup

Type Ip Target TTL
TXT 300
CAA 3600
SOA 60
Mname ns1.google.com
Rname dns-admin.google.com
Serial Number 282320765
Refresh 900
Retry 900
Expire 1800
Minimum TTL 0
MX alt2.aspmx.l.google.com 600
MX alt4.aspmx.l.google.com 600
MX alt1.aspmx.l.google.com 600
MX aspmx.l.google.com 600
MX alt3.aspmx.l.google.com 600
AAAA 300
A 216.58.192.195 283
NS ns1.google.com 3583
NS ns3.google.com 3583
NS ns4.google.com 3583
NS ns2.google.com 3583

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

whois lookup at whois.cnnic.cn...
Domain Name: google.cn
ROID: 20030311s10001s00033735-cn
Domain Status: clientDeleteProhibited
Domain Status: serverDeleteProhibited
Domain Status: serverUpdateProhibited
Domain Status: clientTransferProhibited
Domain Status: serverTransferProhibited
Registrant ID: ename_el7l***azw
Registrant: 北京谷翔信息技术有限公司
Registrant Contact Email: email
Sponsoring Registrar: 厦门易名科技股份有限公司
Name Server: ns2.google.com
Name Server: ns1.google.com
Name Server: ns3.google.com
Name Server: ns4.google.com
Registration Time: 2003-03-17 12:20:05
Expiration Time: 2021-03-17 12:48:36
DNSSEC: unsigned
Last update was 183 days ago
loader
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

seetrue3d.com
0 secs
coinpro.co.uk
6 secs
cabinet.vbcc.io
22 secs
likesvest18.com
42 secs
seetehran.com
1 min
seer.blogsky.com
2 mins
etelligens.com
2 mins
clubtogethernow.com
3 mins
globalnews.ca
3 mins
seek-web.net
3 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

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!
google.cn widget