Skip to content
https://idnes.cz

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.idnes.cz/
200https://idnes.cz/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://idnes.cz/ https://idnes.cz/

Consistent

B
TLS Certificate Expiry & Recommendations
293 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

293
days left
0d 30d 60d 90d+

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 38 ms lookup
PASS
1 A records, 38 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 185.17.117.32
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns.mafra.cz, ns.mafracz.net, ns2.mafra.cz
Info::
4 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 38 ms
Got: 38 ms
A185.17.117.32
AAAA
CNAME
NSns.mafra.cz, ns.mafracz.net, ns2.mafra.cz
MX
10 smtp1.mafra.cz
10 smtp2.mafra.cz
20 smtp4.mafra.cz
20 smtp3.mafra.cz
TXT
google-site-verification=3gmVU4Owr1irArdk1y6yJuW61YwWidJGkuHorgyLxDc
google-site-verification=e8vQLJxL2f86eMT_umz9otbgNecaKeIPbOc3APmK_tI
asv_domain=11002d5c5b01eab3f7176d9abcdde1f0
cisco-ci-domain-verification=1c493ddf9c6e7bbb3accae8c8bcaffdc5bc73dcee0a05cf2228...
MS=ms45743943
google-site-verification=VdNNYIF4KCAI_-Fde4OKMfDGyYUb4JtYO8m8IbuDKAg
SPF v=spf1 include:_spf.xqueue.com include:spf.mafra.cz ip4:195.146.144.22 ip4:195.1...
CAALookup not available with standard resolver
Resolved in 38 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 371 ms total
PASS
1 redirect(s), 371 ms total
Info::
Single redirect
Got: https://idnes.cz → https://www.idnes.cz/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://idnes.cz

https://idnes.cz

112 ms · HTTP/1.1

302

https://www.idnes.cz/

258 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://idnes.cz302112 msHTTP/1.1
2https://www.idnes.cz/200258 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
Crawlability
robots.txt present, sitemap with 73 URLs
PASS
robots.txt present, sitemap with 73 URLs
Info::
robots.txt is present
Got: 1084 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 73 entries
Info::
Sitemap index with 73 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1084 B Sitemaps referenced 1 User-agents MachineLearning, Google-Extended, PerplexityBot, YouBot, Diffbot, *, Amazonbot, ClaudeBot, Omgilibot, Applebot, Bytespider, anthropic-ai, ImagesiftBot, Omgili, Claude-Web, GPTBot, FacebookBot Blocking No — crawling allowed
User-agent: *

Disallow: /*/diskuse*reakce=

Disallow: /*/diskuse*vlakno=

Disallow: /*/diskuse*strana=

Disallow: /*/diskuse/

Allow:    /*/diskuse$

Disallow: /*/diskuse*razeni=

Disallow: /*/tisk$

Disallow: /*/ankety/

Disallow: /ankety.aspx*hlasuj

Disallow: /export/

Disallow: /data.aspx

Disallow: /*/undefined

Disallow: /_servix/*

Disallow: */redir.aspx

Disallow: */Redir.aspx

Disallow: *?setver=


User-agent: MachineLearning

Disallow: /

User-agent: GPTBot

Disallow: /

User-agent: Google-Extended

Disallow: /

User-agent: PerplexityBot

Disallow: /

User-agent: Amazonbot

Disallow: /

User-agent: ClaudeBot

Disallow: /

User-agent: Omgilibot

Disallow: /

User-Agent: FacebookBot

Disallow: /

User-Agent: Applebot

Disallow: /

User-agent: anthropic-ai

Disallow: /

User-agent: Bytespider

Disallow: /

User-agent: Claude-Web

Disallow: /

User-agent: Diffbot

Disallow: /

User-agent: ImagesiftBot

Disallow: /

User-agent: Omgilibot

Disallow: /

User-agent: Omgili

Disallow: /

User-agent: YouBot

Disallow: /


Sitemap: https://www.idnes.cz/sitemap.xml


sitemap.xml 200 OK
Type Sitemap Index URLs 73 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
idnes.cz — via REG-INTERNET-CZ, 28 years, 9 months old, hosted on MAFRA-CZ-AS, CZ
PASS
idnes.cz — via REG-INTERNET-CZ, 28 years, 9 months old, hosted on MAFRA-CZ-AS, CZ
Info::
Domain registered until Oct 19, 2026 (6 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: REG-INTERNET-CZ
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: MAFRA-CZ-AS, CZ
Got: AS38952
Domain expiry

93 days

October 19, 2026

SSL certificate

293 days

Issued by Sectigo Limited

Domain age

28 years, 9 months

Registered November 30, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

MAFRA-CZ-AS, CZ

ASN AS38952

185.17.117.32

Registrar

REG-INTERNET-CZ

Unlocked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar REG-INTERNET-CZ
Created November 30, 1997 (28 years, 9 months ago)
Expires October 19, 2026 (6 months)
Last Updated May 27, 2019
Name Servers ns2.mafra.cz, ns.mafra.cz, ns.mafracz.net
DNSSEC Enabled
Hosting
IP Address 185.17.117.32
ASN AS38952 (MAFRA-CZ-AS, CZ)
Provider MAFRA-CZ-AS, CZ
Data source: rdap (1.1s)

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 148 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
38 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
34 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
39 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
149 ms
Total Time Total request time from DNS lookup through full response.
149 ms

Connection waterfall

DNS Lookup 38 ms TCP Connect 34 ms TLS Handshake 39 ms Server Processing 38 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback