9e.Cz 9e.cz

Szdgndsf.9e.Cz

szdgndsf.9e.cz receives about 1,222 unique visitors and 5,986 (4.90 per visitor) page views per day which should earn about $11.66/day from advertising revenue. Estimated site value is $4,766.50. According to Alexa Traffic Rank szdgndsf.9e.cz is ranked number 514,344 in the world and 7.2E-5% of global Internet users visit it. Site is hosted in Prague, Hlavni mesto Praha, 150 00, Czechia and links to network IP address 88.86.120.160. This server supports HTTPS and HTTP/2.

About - szdgndsf.9e.cz


Technologies used on Website

Currently Not Available

szdgndsf.9e.cz Profile

Title: best online dating website
Last update was 99 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is szdgndsf.9e.cz?

1.2K daily visitors
Daily Unique Visitors:
1,222
Monthly Unique Visitors:
36,660
Pages per Visit:
4.90
Daily Pageviews:
5,986
Alexa Rank:
514,344 visit alexa
Alexa Reach:
7.2E-5%   (of global internet users)
Avg. visit duration:
00:00
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
0%
Referral:
0%
Search:
0%
Social:
0%
Paid:
0%

Visitors by country

Users%Pageviews%Rank
Czech Republic 64.8%89.7%6958
Russian Federation 1.3%0.1%958009

Where do visitors go on this site?

Reach%Pageviews%PerUser
vyhra-vyhra.9e.cz
46.35%78.87%20
OTHER
0%21.13%0

+ Competitive Data

SEMrush
Domain:
  szdgndsf.9e.cz
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

On October 30 SEMrush is hosting first of a kind 24-hour online conference for marketers around the globe — Global Marketing Day. The event is designed for marketers to learn from the most successful in the field. Speakers from Google, Walt Disney, Adobe, BBC, WeWork, and many more will share real cases, tools and insights, so attendees can find out more about marketing in a day than many do by slaving over books for months. This unique experience is absolutely free!
Sign up & watch for free >>

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is szdgndsf.9e.cz?

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:
9e.cz
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:
9e.cz
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 szdgndsf.9e.cz can earn?

Daily Revenue:
$11.66
Monthly Revenue:
$349.80
Yearly Revenue:
$4,255.90
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Czech Republic 5,369$11.65
Russian Federation 6$0.01

How much money do szdgndsf.9e.cz lose due to Adblock?

Daily Revenue Loss:
$1.17
Monthly Revenue Loss:
$34.98
Yearly Revenue Loss:
$425.55
Daily Pageviews Blocked:
537
Monthly Pageviews Blocked:
16,119
Yearly Pageviews Blocked:
196,116
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Czech Republic 537$1.17
Russian Federation 0$0.00

How much is szdgndsf.9e.cz worth?

Website Value:
$4,766.50

+ Where is szdgndsf.9e.cz hosted?

Server IP:
88.86.120.160
ASN:
AS39392 
ISP:
SuperNetwork s.r.o. 
Server Location:
Prague
Hlavni mesto Praha, 10
150 00
Czechia, CZ
 

Other sites hosted on 88.86.120.160

+ How fast does szdgndsf.9e.cz load?

Average Load Time:
(1527 ms) 60 % 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

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.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 0.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.
First Meaningful Paint 0.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 0.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

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

URL
Size
http://szdgndsf.9e.cz/dati5086.jpg
117 KB
http://szdgndsf.9e.cz/
4 KB
http://szdgndsf.9e.cz/styles3094.css
1 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
Style & Layout
17 ms
Other
12 ms
Rendering
4 ms
Script Evaluation
3 ms
Parse HTML & CSS
2 ms
Script Parsing & Compilation
1 ms
Serve images in next-gen formats - Potential savings of 77 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://szdgndsf.9e.cz/dati5086.jpg
116 KB77 KB
Avoids an excessive DOM size - 246 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
246
Maximum DOM Depth
19
Maximum Child Elements
39
Keep request counts low and transfer sizes small - 3 requests • 122 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
3122 KB
Image
1117 KB
Document
14 KB
Stylesheet
11 KB
Media
00 KB
Font
00 KB
Script
00 KB
Other
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 60 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
http://szdgndsf.9e.cz/styles3094.css
1 KB70
Efficiently encode images - Potential savings of 14 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://szdgndsf.9e.cz/dati5086.jpg
116 KB14 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://szdgndsf.9e.cz/
0 ms359 ms4 KB11 KB200text/htmlDocument
http://szdgndsf.9e.cz/styles3094.css
369 ms601 ms1 KB0 KB200text/cssStylesheet
http://szdgndsf.9e.cz/dati5086.jpg
369 ms950 ms117 KB116 KB200image/jpegImage
Serve static assets with an efficient cache policy - 2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://szdgndsf.9e.cz/dati5086.jpg
0 ms117 KB
http://szdgndsf.9e.cz/styles3094.css
0 ms1 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
377 ms
6 ms
619 ms
17 ms
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.

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.

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.

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

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.


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

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) 1560 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.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.8 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.8 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.8 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.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
596 ms
7 ms
1174 ms
26 ms
1202 ms
9 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
229 ms10 ms4 ms
Avoids enormous network payloads - Total size was 122 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://szdgndsf.9e.cz/dati5086.jpg
117 KB
http://szdgndsf.9e.cz/
4 KB
http://szdgndsf.9e.cz/styles3094.css
1 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Style & Layout
95 ms
Other
65 ms
Rendering
48 ms
Script Evaluation
10 ms
Parse HTML & CSS
8 ms
Script Parsing & Compilation
4 ms
Serve images in next-gen formats - Potential savings of 77 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://szdgndsf.9e.cz/dati5086.jpg
116 KB77 KB
Avoids an excessive DOM size - 246 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
246
Maximum DOM Depth
19
Maximum Child Elements
39
Keep request counts low and transfer sizes small - 3 requests • 122 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
3122 KB
Image
1117 KB
Document
14 KB
Stylesheet
11 KB
Media
00 KB
Font
00 KB
Script
00 KB
Other
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 130 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
http://szdgndsf.9e.cz/styles3094.css
1 KB180
Efficiently encode images - Potential savings of 14 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://szdgndsf.9e.cz/dati5086.jpg
116 KB14 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://szdgndsf.9e.cz/
0 ms574 ms4 KB11 KB200text/htmlDocument
http://szdgndsf.9e.cz/styles3094.css
585 ms1150 ms1 KB0 KB200text/cssStylesheet
http://szdgndsf.9e.cz/dati5086.jpg
586 ms1161 ms117 KB116 KB200image/jpegImage
Serve static assets with an efficient cache policy - 2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://szdgndsf.9e.cz/dati5086.jpg
0 ms117 KB
http://szdgndsf.9e.cz/styles3094.css
0 ms1 KB
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.

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.

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

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.

International…sites Missouri and 27 others render only 5 pixels tall (12 CSS pixels) .
Heading renders only 5 pixels tall (12 CSS pixels).
People pass th…nic as for me. and 1 others render only 5 pixels tall (12 CSS pixels).
Best dating ap…over 50 Sarnia and 2 others render only 5 pixels tall (12 CSS pixels).
What about me…ile in return. renders only 5 pixels tall (12 CSS pixels) .
03.07.2019 and 7 others render only 4 pixels tall (10 CSS pixels) .
1st year anniv…her Gladstone and 7 others render only 6 pixels tall (16 CSS pixels) .
I was in panic…aid. This ... and 7 others render only 5 pixels tall (12 CSS pixels) .
szdgndsf.9e.cz renders only 5 pixels tall (14 CSS pixels).
„Proti hlupost…hrát se nedá!“ renders only 5 pixels tall (12 CSS pixels).
Jan Werich renders only 5 pixels tall (12 CSS pixels).

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://szdgndsf.9e.cz">Главная</a> and 21 others are close to other tap targets .
The tap target <a href="topic-5***715.html">Best dating ap…over 50 Sarnia</a> and 2 others are close to other tap targets.

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.

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:

http://szdgndsf.9e.cz/styles3094.css

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 48.5KiB (42% reduction).

Compressing http://szdgndsf.9e.cz/dati5086.jpg could save 48.5KiB (42% reduction).

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:

http://szdgndsf.9e.cz/dati5086.jpg (expiration not specified)
http://szdgndsf.9e.cz/styles3094.css (expiration not specified)

Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 183B (44% reduction).

Compressing http://szdgndsf.9e.cz/styles3094.css could save 183B (44% reduction).
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.
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.
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.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does szdgndsf.9e.cz use compression?

szdgndsf.9e.cz use gzip compression.
Original size: 18.43 KB
Compressed size: 3.98 KB
File reduced by: 14.45 KB (78%)

+ 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

szdgndsf.9e.cz supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: *.8u.cz
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Jul 7 21:08:15 2019 GMT
Valid until: Oct 5 21:08:15 2019 GMT
Authority: Is not a CA
Keysize:
Common Name: Let's Encrypt Authority X3
Organization: Let's Encrypt
Location: US
Issuer: DST Root CA X3
Valid from: Mar 17 16:40:46 2016 GMT
Valid until: Mar 17 16:40:46 2021 GMT
Authority: Is a CA
Keysize: 2048 Bits

+ Verify HTTP/2 Support

szdgndsf.9e.cz supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: nginx
Date: Tue, 09 Jul 2019 07:51:13 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Last-Modified: Tue, 09 Jul 2019 07:33:53 GMT
ETag: W/"2b58-58d3a952ddc35"
Content-Encoding: gzip

+ DNS Lookup

Type Ip Target TTL
A 88.86.120.160 3579

+ Whois Lookup

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

Currently Not Available
Last update was 99 days ago
loader
This can take up to 60 seconds. Please wait...

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

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!
szdgndsf.9e.cz widget