Skip to content
https://sachsen.de

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
75
GRADE
C
FIX
2
REVIEW
5
PASS
2
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
2 PASS 5 REVIEW 2 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2a02:101c:1800:1306::196
Info::
IPv6 connection error
Got: dial tcp6 [2a02:101c:1800:1306::196]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2a02:101c:1800:1306::196 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

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.

B
Redirect Chain
1 redirect(s), 1918 ms total
REVIEW
1 redirect(s), 1918 ms total
Info::
Single redirect
Got: https://sachsen.de → https://www.sachsen.de/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1918 ms total
Got: 1918 ms

https://sachsen.de

951 ms · HTTP/1.1

301

https://www.sachsen.de/

967 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://sachsen.de301951 msHTTP/1.1Apache
2https://www.sachsen.de/200967 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 39 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 39 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /cps/rde/xchg/
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.sachsen.de/
200https://sachsen.de/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://sachsen.de/ → https://sachsen.de/

Consistent

B
HTTP Probe Timing
Total 949 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
154 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
158 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
479 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
949 ms
Total Time Total request time from DNS lookup through full response.
949 ms

Connection waterfall

DNS Lookup 154 ms TCP Connect 158 ms TLS Handshake 479 ms Server Processing 158 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
314 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 163 ms lookup
PASS
1 A records, 163 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 31.12.58.19
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a02:101c:1800:1306::196
Info::
4 nameserver(s) configured
Got: pns.dtag.de, S2VG300NS02.pzd-svn.de, S2VG300NS03.pzd-svn.de, secondary006.dtag.net
Info::
2 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: 163 ms
Got: 163 ms
A31.12.58.19
AAAA2a02:101c:1800:1306::196
CNAME—
NSpns.dtag.de, S2VG300NS02.pzd-svn.de, S2VG300NS03.pzd-svn.de, secondary006.dtag.net
MX
20 s2vg300mr01.pzd-svn.de
20 s2vg300mr02.pzd-svn.de
TXT
SPF v=spf1 include:pzd-svn.de ?all
swisssign-check=03JNaK96vvkH-qLFODTLJK3r5XY
swisssign-check=FBmo5ynA7atuutSW0Qz9ZRibrWM
swisssign-check=YSTdsxVVU3RXFPEGvso05u1Xl-Y
swisssign-check=trJygSuZgC1UOvdu6j2--hBIRWo
_telesec-domain-validation=5938DC2F7CDBABA84996137E6C1C5291D8B59542F82148E8EB973...
cisco-ci-domain-verification=2d704a891f2fd05972ef8138fb334de8d0f4bdf38fd8c594f3a...
CAALookup not available with standard resolver
Resolved in 163 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+
Domain Intelligence
sachsen.de — hosted on SUB-LIR-SN-AS Sub-LIR SN, DE
PASS
sachsen.de — hosted on SUB-LIR-SN-AS Sub-LIR SN, DE
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: SUB-LIR-SN-AS Sub-LIR SN, DE
Got: AS61352
Domain expiry

Unknown

SSL certificate

314 days

Issued by SwissSign AG

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

SUB-LIR-SN-AS Sub-LIR SN, DE

ASN AS61352

31.12.58.19

Registrar

Registrar unknown

Unlocked Name servers unknown
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar
Hosting
IP Address 31.12.58.19
ASN AS61352 (SUB-LIR-SN-AS Sub-LIR SN, DE)
Provider SUB-LIR-SN-AS Sub-LIR SN, DE
Data source: whois (0.6s)

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback