ss2000s.Top - Info ss2000s.top

ss2000s.top receives about n/a unique visitors and n/a page views per day which should earn about n/a/day from advertising revenue. Estimated site value is n/a. According to Alexa Traffic Rank ss2000s.top is ranked number 0 in the world and 0% of global Internet users visit it. Site is hosted in Mountain View, California, 94043, United States and links to network IP address 35.244.177.130. This server doesn't support HTTPS and doesn't support HTTP/2.

About - ss2000s.top


Technologies used on Website

CDN
Google Cloud
Web Servers
Nginx
Reverse proxies
Nginx

ss2000s.top Profile

Title: 冰恋论坛 冰恋网站 老梦视觉 2Kill4 PST EWP PKF 冰恋 迷晕 女尸解剖 女尸图片 - Powered by Discuz!
Last update was 3 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is ss2000s.top?

Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
 n/a
Monthly Unique Visitors:
n/a
Pages per Visit:
n/a
Daily Pageviews:
n/a
Alexa Rank:
Currently Not Available visit alexa
Alexa Reach:
n/a   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  ss2000s.top
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.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:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is ss2000s.top?

Facebook:
  0
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:
ss2000s.top
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:
ss2000s.top
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 ss2000s.top can earn?

Daily Revenue:
n/a
Monthly Revenue:
n/a
Yearly Revenue:
n/a
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do ss2000s.top lose due to Adblock?

Daily Revenue Loss:
n/a
Monthly Revenue Loss:
n/a
Yearly Revenue Loss:
n/a
Daily Pageviews Blocked:
n/a
Monthly Pageviews Blocked:
n/a
Yearly Pageviews Blocked:
n/a
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is ss2000s.top worth?

Website Value:
n/a

+ Where is ss2000s.top hosted?

Server IP:
35.244.177.130
ASN:
AS15169 
ISP:
Google LLC 
Server Location:
Mountain View
California, CA
94043
United States, US
 

Other sites hosted on 35.244.177.130

+ How fast does ss2000s.top load?

Average Load Time:
n/a ms n/a % 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

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.
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.5 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.
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.

Screenshot Thumbnails

This is what the load of your site looked like.

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

Resource Type
RequestsTransfer Size
Total
530 KB
Script
226 KB
Document
13 KB
Image
21 KB
Stylesheet
00 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
326 KB
Eliminate render-blocking resources - Potential savings of 220 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://image.uc.cn/s/uae/g/0n/wuweixin/adtrack-jssdk-1.0.6.js
11 KB230
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://ss2000s.top/
0 ms161 ms3 KB8 KB200text/htmlDocument
https://image.uc.cn/s/uae/g/0n/wuweixin/adtrack-jssdk-1.0.6.js
171 ms277 ms11 KB42 KB200text/javascriptScript
https://hm.baidu.com/hm.js?b150d8955dada51289c717fc938583d3
171 ms536 ms15 KB42 KB200application/javascriptScript
http://ss2000s.top/download-min.png
283 ms443 ms1 KB0 KB200image/pngImage
https://hm.baidu.com/hm.gif?cc=1&ck=1&cl=24-bit&ds=800x600&vl=940&et=0&ja=0&ln=en-us&lo=0&rnd=450350046&si=b150d8955dada51289c717fc938583d3&v=1.2.68&lv=1&sn=41992&ct=!!&tt=ss2000s.top
556 ms845 ms0 KB0 KB200image/gifImage
Uses efficient cache policy on static assets - 1 resource found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://ss2000s.top/download-min.png
2592000000 ms1 KB
Minimize third-party usage - Third-party code blocked the main thread for 0 ms
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.

Third-Party
SizeMain-Thread Blocking Time
15 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
185 ms
6 ms
306 ms
28 ms
562 ms
16 ms
867 ms
17 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
63 ms2 ms1 ms
Avoids enormous network payloads - Total size was 30 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://hm.baidu.com/hm.js?b150d8955dada51289c717fc938583d3
15 KB
https://image.uc.cn/s/uae/g/0n/wuweixin/adtrack-jssdk-1.0.6.js
11 KB
http://ss2000s.top/
3 KB
http://ss2000s.top/download-min.png
1 KB
https://hm.baidu.com/hm.gif?cc=1&ck=1&cl=24-bit&ds=800x600&vl=940&et=0&ja=0&ln=en-us&lo=0&rnd=450350046&si=b150d8955dada51289c717fc938583d3&v=1.2.68&lv=1&sn=41992&ct=!!&tt=ss2000s.top
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
41 ms
Script Evaluation
23 ms
Other
13 ms
Rendering
4 ms
Script Parsing & Compilation
4 ms
Parse HTML & CSS
1 ms
Avoids an excessive DOM size - 11 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
11
Maximum DOM Depth
5
Maximum Child Elements
4
Minify JavaScript - Potential savings of 5 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
https://image.uc.cn/s/uae/g/0n/wuweixin/adtrack-jssdk-1.0.6.js
11 KB5 KB
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 160 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.

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.

Serve images in next-gen formats
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.

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.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. 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

Speed Index 2.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.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 1.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.
First Meaningful Paint 1.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 30 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.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. 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.
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) 3109 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids enormous network payloads - Total size was 31 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://hm.baidu.com/hm.js?b150d8955dada51289c717fc938583d3
15 KB
https://image.uc.cn/s/uae/g/0n/wuweixin/adtrack-jssdk-1.0.6.js
11 KB
http://ss2000s.top/
3 KB
http://ss2000s.top/download-min.png
1 KB
https://hm.baidu.com/hm.gif?cc=1&ck=1&cl=24-bit&ds=412x660&vl=660&ep=event*CallApp%20%26%20download*android&et=4&ja=0&ln=en-us&lo=0&rnd=1126734263&si=b150d8955dada51289c717fc938583d3&v=1.2.68&lv=1&api=8_0&sn=41987
0 KB
https://hm.baidu.com/hm.gif?cc=1&ck=1&cl=24-bit&ds=412x660&vl=660&ep=event*CallApp%20%26%20download*setTimeout&et=4&ja=0&ln=en-us&lo=0&rnd=966560850&si=b150d8955dada51289c717fc938583d3&v=1.2.68&lv=1&api=8_0&sn=41987
0 KB
https://hm.baidu.com/hm.gif?cc=1&ck=1&cl=24-bit&ds=412x660&vl=660&et=0&ja=0&ln=en-us&lo=0&rnd=1985482226&si=b150d8955dada51289c717fc938583d3&v=1.2.68&lv=1&sn=41987&ct=!!
0 KB
https://adtrack.ucweb.com/v1/collect?st_name=JSSDK&st_event=click&appkey=cc77796ca7c25dff9607d31b29effc07&ch=gongyp%40outsizeothersAR&bid=800&pkg=com.UCMobile&ua=Mozilla%2F5.0%20(Linux%3B%20Android%206.0.1%3B%20Nexus%205%20Build%2FMRA58N)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F74.0.3694.0%20Mobile%20Safari%2F537.36%20Chrome-Lighthouse&fp=71046559-6418-4d6d-9385-6dcc11302ab9-1581401537039&uc_param_str=cpfrvelasvprktdndd
0 KB
Minimizes main-thread work - 0.6 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
345 ms
Script Evaluation
172 ms
Other
67 ms
Rendering
18 ms
Script Parsing & Compilation
15 ms
Parse HTML & CSS
8 ms
Avoids an excessive DOM size - 11 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
11
Maximum DOM Depth
5
Maximum Child Elements
4
Minify JavaScript - Potential savings of 5 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
https://image.uc.cn/s/uae/g/0n/wuweixin/adtrack-jssdk-1.0.6.js
11 KB5 KB
Keep request counts low and transfer sizes small - 9 requests • 31 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
931 KB
Script
226 KB
Document
13 KB
Image
42 KB
Stylesheet
00 KB
Media
00 KB
Font
00 KB
Other
20 KB
Third-party
727 KB
Eliminate render-blocking resources - Potential savings of 0 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://image.uc.cn/s/uae/g/0n/wuweixin/adtrack-jssdk-1.0.6.js
11 KB930
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://ss2000s.top/
0 ms442 ms3 KB8 KB200text/htmlDocument
https://image.uc.cn/s/uae/g/0n/wuweixin/adtrack-jssdk-1.0.6.js
453 ms898 ms11 KB42 KB200text/javascriptScript
https://hm.baidu.com/hm.js?b150d8955dada51289c717fc938583d3
454 ms820 ms15 KB42 KB200application/javascriptScript
https://hm.baidu.com/hm.gif?cc=1&ck=1&cl=24-bit&ds=412x660&vl=660&et=0&ja=0&ln=en-us&lo=0&rnd=1985482226&si=b150d8955dada51289c717fc938583d3&v=1.2.68&lv=1&sn=41987&ct=!!
848 ms1187 ms0 KB0 KB200image/gifImage
http://ss2000s.top/download-min.png
905 ms1104 ms1 KB0 KB200image/pngImage
https://adtrack.ucweb.com/v1/collect?st_name=JSSDK&st_event=click&appkey=cc77796ca7c25dff9607d31b29effc07&ch=gongyp%40outsizeothersAR&bid=800&pkg=com.UCMobile&ua=Mozilla%2F5.0%20(Linux%3B%20Android%206.0.1%3B%20Nexus%205%20Build%2FMRA58N)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F74.0.3694.0%20Mobile%20Safari%2F537.36%20Chrome-Lighthouse&fp=71046559-6418-4d6d-9385-6dcc11302ab9-1581401537039&uc_param_str=cpfrvelasvprktdndd
1208 ms1212 ms0 KB0 KB-1Other
https://adtrack.ucweb.com/v1/sdkClick
1211 ms0 ms0 KB0 KB-1XHR
https://hm.baidu.com/hm.gif?cc=1&ck=1&cl=24-bit&ds=412x660&vl=660&ep=event*CallApp%20%26%20download*setTimeout&et=4&ja=0&ln=en-us&lo=0&rnd=966560850&si=b150d8955dada51289c717fc938583d3&v=1.2.68&lv=1&api=8_0&sn=41987
1215 ms1518 ms0 KB0 KB200image/gifImage
https://hm.baidu.com/hm.gif?cc=1&ck=1&cl=24-bit&ds=412x660&vl=660&ep=event*CallApp%20%26%20download*android&et=4&ja=0&ln=en-us&lo=0&rnd=1126734263&si=b150d8955dada51289c717fc938583d3&v=1.2.68&lv=1&api=8_0&sn=41987
1215 ms1539 ms0 KB0 KB200image/gifImage
Uses efficient cache policy on static assets - 1 resource found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://ss2000s.top/download-min.png
2592000000 ms1 KB
Minimize third-party usage - Third-party code blocked the main thread for 30 ms
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.

Third-Party
SizeMain-Thread Blocking Time
16 KB28 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
461 ms
7 ms
841 ms
24 ms
922 ms
76 ms
1204 ms
15 ms
1220 ms
8 ms
JavaScript execution time - 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.

URL
Total CPU TimeScript EvaluationScript Parse
Other
449 ms15 ms3 ms
https://hm.baidu.com/hm.js?b150d8955dada51289c717fc938583d3
121 ms108 ms5 ms
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.

Serve images in next-gen formats
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.

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.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. 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 440 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.

Page Speed (Google PageSpeed Insights) - v2

Currently Not Available

+ Does ss2000s.top use compression?

ss2000s.top use gzip compression.
Original size: 13.04 KB
Compressed size: 4.36 KB
File reduced by: 8.68 KB (66%)

+ 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

ss2000s.top does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

ss2000s.top does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: nginx
Date: Fri, 22 May 2020 23:28:27 GMT
Content-Type: text/html
Last-Modified: Fri, 15 May 2020 06:13:23 GMT
Transfer-Encoding: chunked
Vary: Accept-Encoding
ETag: W/"5ebe3303-3429"
Content-Encoding: gzip
Via: 1.1 google

+ DNS Lookup

Type Ip Target TTL
A 35.244.177.130 300
SOA 2560
Mname ns1.dynadot.com
Rname hostmaster.ss2000s.top
Serial Number 1590189850
Refresh 16384
Retry 2048
Expire 1048576
Minimum TTL 0
NS ns2.dynadot.com 300
NS ns1.dynadot.com 300

+ Whois Lookup

Domain Created:
2020-01-05
Domain Age:
4 months 17 days  
WhoIs:
 

whois lookup at whois.nic.top...
Domain Name: ss2000s.top
Registry Domain ID: D20200105G10001G_29941560-top
Registrar WHOIS Server: whois.dynadot.com
Registrar URL: http://www.dynadot.com
Updated Date: 2020-01-05T11:04:12Z
Creation Date: 2020-01-05T03:04:45Z
Registry Expiry Date: 2021-01-05T03:04:45Z
Registrar: Dynadot LLC
Registrar IANA ID: 472
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +86.6502620100
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization:
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: California
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns1.dynadot.com
Name Server: ns2.dynadot.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2020-05-22T23:25:16Z <<<

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

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: The information in the Whois database is collected through ICANN-accredited registrars. Jiangsu bangning science & technology Co., Ltd(“BANGNING”) make this information available to you and do not guarantee its accuracy or completeness. By submitting a whois query, you agree to abide by the following terms of use: you agree that you may use this data only for lawful purposes and that under no cir***stances will you use this data to: (1) to allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, electronic mail, or by telephone; (2) in contravention of any applicable data and privacy protection acts; or (3) to enable high volume, automated, electronic processes that apply to BANGNING (or its computer systems). Compilation, repackaging, dissemination, or other use of the WHOIS database in its entirety, or of a substantial portion thereof, is not allowed without BANGNING prior written permission. You agree not to use electronic processes that are automated and high-volume to access or query the whois database except as reasonably necessary to register domain names or modify existing registrations. BANGNING reserves the right to restrict your access to the whois database in its sole discretion to ensure operational stability. BANGNING may restrict or terminate your access to the whois database for failure to abide by these terms of use. BANGNING reserves the right to modify these terms at any time without prior or subsequent notification of any kind.
Last update was 3 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with ss2000s.top in any way. Only publicly available statistics data are displayed.
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!
ss2000s.top widget