Tvrdypostoj.Cz - Info tvrdypostoj.cz

tvrdypostoj.cz receives about 408 unique visitors and 408 (1.00 per visitor) page views per day which should earn about $1.67/day from advertising revenue. Estimated site value is $1,215.97. According to Alexa Traffic Rank tvrdypostoj.cz is ranked number 3,627,093 in the world and 9.0E-6% of global Internet users visit it. Site is hosted in Czechia and links to network IP address 31.15.10.106. This server supports HTTPS and HTTP/2.

About - tvrdypostoj.cz


Technologies used on Website

Font Scripts
Google Font API
Web Servers
Nginx
Reverse Proxy
Nginx
CMS
WordPress
Blogs
WordPress
Programming Languages
PHP
Databases
MySQL

tvrdypostoj.cz Profile

Title: Tvrdý postoj.cz - Žij tvrdě a budeš tvrdý. Blog empatického muže.
Description: Po desítkách let v kanceláři chcete zažít dobrodružství.
Last update was 2 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is tvrdypostoj.cz?

408 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
408
Monthly Unique Visitors:
9,792
Pages per Visit:
1.00
Daily Pageviews:
408
Alexa Rank:
3,627,093 visit alexa
Alexa Reach:
9.0E-6%   (of global internet users)
Avg. visit duration:
00:00
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:
  tvrdypostoj.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

+ Moz Data

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

+ How socially engaged is tvrdypostoj.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:
tvrdypostoj.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:
tvrdypostoj.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 tvrdypostoj.cz can earn?

Daily Revenue:
$1.67
Monthly Revenue:
$50.10
Yearly Revenue:
$609.55
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do tvrdypostoj.cz 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 tvrdypostoj.cz worth?

Website Value:
$1,215.97

+ Where is tvrdypostoj.cz hosted?

Server IP:
31.15.10.106
ASN:
AS25234 
ISP:
ACTIVE 24 
Server Location:

Czechia, CZ
 

Other sites hosted on 31.15.10.106

+ How fast does tvrdypostoj.cz load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

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

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.
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.8 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.
First Meaningful Paint 0.6 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.

Efficiently encode images - Potential savings of 4 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
https://tvrdypostoj.cz/wp-content/themes/videopro/images/tvrdy.jpg
91 KB4 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://tvrdypostoj.cz/
0 ms543 ms0 KB0 KB301text/html
https://tvrdypostoj.cz/
544 ms754 ms1 KB2 KB200text/htmlDocument
https://fonts.googleapis.com/css?family=Open+Sans:400,700&subset=latin,latin-ext
768 ms787 ms1 KB5 KB200text/cssStylesheet
https://tvrdypostoj.cz/wp-content/cache/wpfc-minified/6y186lus/a0xw0.css
768 ms887 ms9 KB36 KB200text/cssStylesheet
https://tvrdypostoj.cz/wp-content/themes/videopro/images/tvrdy.jpg
769 ms1212 ms91 KB91 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
https://tvrdypostoj.cz/wp-content/themes/videopro/images/tvrdy.jpg
0 ms91 KB
https://tvrdypostoj.cz/wp-content/cache/wpfc-minified/6y186lus/a0xw0.css
0 ms9 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
780 ms
9 ms
913 ms
5 ms
918 ms
13 ms
Properly size images - Potential savings of 50 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
https://tvrdypostoj.cz/wp-content/themes/videopro/images/tvrdy.jpg
91 KB50 KB
Avoids enormous network payloads - Total size was 103 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://tvrdypostoj.cz/wp-content/themes/videopro/images/tvrdy.jpg
91 KB
https://tvrdypostoj.cz/wp-content/cache/wpfc-minified/6y186lus/a0xw0.css
9 KB
https://fonts.googleapis.com/css?family=Open+Sans:400,700&subset=latin,latin-ext
1 KB
https://tvrdypostoj.cz/
1 KB
http://tvrdypostoj.cz/
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. Learn more.

Category
Time Spent
Other
17 ms
Style & Layout
14 ms
Parse HTML & CSS
4 ms
Script Evaluation
3 ms
Rendering
2 ms
Script Parsing & Compilation
2 ms
Serve images in next-gen formats - Potential savings of 36 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://tvrdypostoj.cz/wp-content/themes/videopro/images/tvrdy.jpg
91 KB36 KB
Avoids an excessive DOM size - 8 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
8
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://tvrdypostoj.cz/)
0
https://tvrdypostoj.cz/
190
Keep request counts low and transfer sizes small - 5 requests • 103 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
5103 KB
Image
191 KB
Stylesheet
211 KB
Document
11 KB
Other
10 KB
Media
00 KB
Font
00 KB
Script
00 KB
Third-party
11 KB
Eliminate render-blocking resources - Potential savings of 230 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://fonts.googleapis.com/css?family=Open+Sans:400,700&subset=latin,latin-ext
1 KB230
https://tvrdypostoj.cz/wp-content/cache/wpfc-minified/6y186lus/a0xw0.css
9 KB70
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.

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.

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.

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


Page Speed (Google PageSpeed Insights) - Mobile

98
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.
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) 3690 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 2.9 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.

Avoids an excessive DOM size - 8 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
8
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://tvrdypostoj.cz/)
0
https://tvrdypostoj.cz/
630
Keep request counts low and transfer sizes small - 5 requests • 103 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
5103 KB
Image
191 KB
Stylesheet
211 KB
Document
11 KB
Other
10 KB
Media
00 KB
Font
00 KB
Script
00 KB
Third-party
11 KB
Eliminate render-blocking resources - Potential savings of 780 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://fonts.googleapis.com/css?family=Open+Sans:400,700&subset=latin,latin-ext
1 KB780
https://tvrdypostoj.cz/wp-content/cache/wpfc-minified/6y186lus/a0xw0.css
9 KB180
Efficiently encode images - Potential savings of 4 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
https://tvrdypostoj.cz/wp-content/themes/videopro/images/tvrdy.jpg
91 KB4 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://tvrdypostoj.cz/
0 ms603 ms0 KB0 KB301text/html
https://tvrdypostoj.cz/
603 ms1046 ms1 KB2 KB200text/htmlDocument
https://fonts.googleapis.com/css?family=Open+Sans:400,700&subset=latin,latin-ext
1062 ms1082 ms1 KB5 KB200text/cssStylesheet
https://tvrdypostoj.cz/wp-content/cache/wpfc-minified/6y186lus/a0xw0.css
1062 ms1180 ms9 KB36 KB200text/cssStylesheet
https://tvrdypostoj.cz/wp-content/themes/videopro/images/tvrdy.jpg
1062 ms1599 ms91 KB91 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
https://tvrdypostoj.cz/wp-content/themes/videopro/images/tvrdy.jpg
0 ms91 KB
https://tvrdypostoj.cz/wp-content/cache/wpfc-minified/6y186lus/a0xw0.css
0 ms9 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1070 ms
11 ms
1204 ms
7 ms
1211 ms
16 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
200 ms12 ms5 ms
Avoids enormous network payloads - Total size was 103 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://tvrdypostoj.cz/wp-content/themes/videopro/images/tvrdy.jpg
91 KB
https://tvrdypostoj.cz/wp-content/cache/wpfc-minified/6y186lus/a0xw0.css
9 KB
https://fonts.googleapis.com/css?family=Open+Sans:400,700&subset=latin,latin-ext
1 KB
https://tvrdypostoj.cz/
1 KB
http://tvrdypostoj.cz/
0 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. Learn more.

Category
Time Spent
Other
73 ms
Style & Layout
70 ms
Parse HTML & CSS
28 ms
Rendering
12 ms
Script Evaluation
12 ms
Script Parsing & Compilation
6 ms
Serve images in next-gen formats - Potential savings of 36 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://tvrdypostoj.cz/wp-content/themes/videopro/images/tvrdy.jpg
91 KB36 KB
Avoid chaining critical requests - 2 chains 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 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.

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.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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://fonts.googleapis.com/css?family=Open+Sans:400,700&subset=latin,latin-ext

Optimize images

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

Optimize the following images to reduce their size by 18.5KiB (21% reduction).

Compressing https://tvrdypostoj.cz/wp-content/themes/videopro/images/tvrdy.jpg could save 18.5KiB (21% 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:

https://tvrdypostoj.cz/wp-content/cache/wpfc-minified/6y186lus/a0xw0.css (expiration not specified)
https://tvrdypostoj.cz/wp-content/themes/videopro/images/tvrdy.jpg (expiration not specified)

Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and p*** times.

Minify HTML for the following resources to reduce their size by 116B (12% reduction).

Minifying https://tvrdypostoj.cz/ could save 116B (12% reduction) after compression.
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.
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.
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 JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
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.
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.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does tvrdypostoj.cz use compression?

tvrdypostoj.cz use gzip compression.
Original size: 1.71 KB
Compressed size: 991 B
File reduced by: 765 B (43%)

+ 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

tvrdypostoj.cz supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: www.tvrdypostoj.cz
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Oct 16 22:39:24 2019 GMT
Valid until: Jan 14 22:39:24 2020 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

tvrdypostoj.cz supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: nginx
Date: Sat, 09 Nov 2019 20:10:08 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 0
Connection: keep-alive
Keep-Alive: timeout=30
Location: https://tvrdypostoj.cz/

HTTP/2 200 
server: nginx
date: Sat, 09 Nov 2019 20:10:09 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip

+ DNS Lookup

Type Ip Target TTL
AAAA 1771
MX wes1-mx-backup.wedos.net 1771
MX wes1-mx1.wedos.net 1771
MX wes1-mx2.wedos.net 1771
A 31.15.10.106 1771
SOA 3571
Mname ns.wedos.com
Rname wedos.wedos.com
Serial Number 2019110702
Refresh 3600
Retry 1800
Expire 2592000
Minimum TTL 0
NS ns.wedos.com 3570
NS ns.wedos.cz 3570
NS ns.wedos.net 3570
NS ns.wedos.eu 3570

+ Whois Lookup

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

whois lookup at whois.nic.cz...
% (c) 2006-2019 CZ.NIC, z.s.p.o.
%
% Intended use of supplied data and information
%
% Data contained in the domain name register, as well as information
% supplied through public information services of CZ.NIC association,
% are appointed only for purposes connected with Internet network
% administration and operation, or for the purpose of legal or other
% similar proceedings, in process as regards a matter connected
% particularly with holding and using a concrete domain name.
%
% Full text available at:
% http://www.nic.cz/page/306/intended-use-of-supplied-data-and-information/
%
% See also a search service at http://www.nic.cz/whois/
%
%
% Whoisd Server Version: 3.12.0
% Timestamp: Sat Nov 09 21:10:33 2019

domain: tvrdypostoj.cz
registrant: WEDOS-AWD-202414
nsset: WEDOS
keyset: WEDOS
registrar: REG-WEDOS
registered: 13.02.2017 11:29:25
expire: 13.02.2020

contact: WEDOS-AWD-202414
org: ELIXIRMAN DISTRIBUTION s.r.o.
name: Michal Mrhač
address: Ocelkova 643/20
address: Praha
address: 19000
address: Liberecky
address: CZ
registrar: REG-WEDOS
created: 13.02.2017 11:29:25
changed: 15.05.2018 21:32:00

nsset: WEDOS
nserver: ns.wedos.net
nserver: ns.wedos.eu
nserver: ns.wedos.com
nserver: ns.wedos.cz (46.28.104.67, 2a02:2b88:1:1::2)
tech-c: WEDOS-INTERNET
registrar: REG-WEDOS
created: 01.03.2010 15:38:08
changed: 14.12.2010 20:23:49

contact: WEDOS-INTERNET
org: WEDOS Internet, a.s.
name: Petr Šťastný
address: Masarykova 1230
address: Hluboká nad Vltavou
address: 37341
address: CZ
registrar: REG-WEDOS
created: 01.03.2010 15:34:12
changed: 15.05.2018 21:32:00

keyset: WEDOS
dnskey: 257 3 7 AwEAAdmJufzAkEEy/uev2Qz1E0IQWP+hH0/20jGjduA+UL5Dkk8enE62SN3p7gj+3mfBZGaJBAfZ3p68gWt630yNT2e6qtHOUcriRqKJgUCaP/AKa7w9MoJrciCsy9ABYSv60MrhroV/LLVWD+Tmpt***BgyXtxARbiqYvpoFE***6zfHr6bafWQpjRfH6v3sG1K2zVvP6Sgd+taQn2lhFfIp5O4IMimGGYzTm2nGWUasSZMj16RZznYHRPwphSZYM2Vzgn2Le1qQBfiyOR1xAgP7LNC+QFRLFVfsvuAGVBCZFqubnQE4E/sMJcX0FfVIvl8PHxhXDIOU0toDjNxGBP7gc0YM=
tech-c: WEDOS-INTERNET
registrar: REG-WEDOS
created: 14.06.2011 14:31:48
changed: 24.07.2018 09:18:47
Last update was 2 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with tvrdypostoj.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!
tvrdypostoj.cz widget