Skip to content
https://taz.de

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
99
GRADE
A+
FIX
1
REVIEW
1
PASS
7
INFO
0
Probed from New York, United Stated
200 OK
Checks
9
7 PASS 1 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.

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

Certificate validity

79
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 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, 98 ms lookup
PASS
1 A records, 98 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 193.104.220.23
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: 2001:67c:13c::7a2:de
Info::
4 nameserver(s) configured
Got: ns3.ipberlin.com, osiris.taz.de, tazns01.lwlcom.net, ns.ipberlin.com
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: 98 ms
Got: 98 ms
A193.104.220.23
AAAA2001:67c:13c::7a2:de
CNAME—
NSns3.ipberlin.com, osiris.taz.de, tazns01.lwlcom.net, ns.ipberlin.com
MX
4 prime.taz.de
4 isis.taz.de
TXT
SPF v=spf1 ip4:193.104.220.0/25 ip6:2001:67c:13c::/48 -all
ZOOM_verify_F46fdfl9SGSDi75NhvXAKQ
21.02.2025
google-site-verification=YFanqmWAmGg7-f6kQrljxkU51Uz1Jln-2-OpY6cjdgI
google-site-verification=wVmqSygpOr2D3RWIrjscZkwkdTx3oLVftjZqV5isapk
2b8f2f31d011a000676fe5646730712961e6be56
cisco-ci-domain-verification=3b7b83ffa84288aacd381919e81fb78930ad7489034c5e70e38...
sendinblue-code:d63320b053dde6b4aeda7f56ef9977e1
MS=C5CCF32B521E32B0CADD4DF2A496828F1B649391
adobe-idp-site-verification=d1a7871405eacdda6420de0aaae055604e00dd7b99c78f4a5ba3...
CAALookup not available with standard resolver
Resolved in 98 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://taz.de

https://taz.de

375 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://taz.de200375 msHTTP/1.1nginx
A+
IPv6 Readiness
IPv6 reachable (83 ms)
PASS
IPv6 reachable (83 ms)
Info::
IPv6 is configured and reachable at 2001:67c:13c::7a2:de
Got: 83 ms connect
IPv6 Ready
AAAA Records 2001:67c:13c::7a2:de Connection Reachable (83 ms)
A+
Crawlability
robots.txt present, sitemap with 182 URLs
PASS
robots.txt present, sitemap with 182 URLs
Info::
robots.txt is present
Got: 796 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 182 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 796 B Sitemaps referenced 2 User-agents Slurp, *, GPTBot Blocking No — crawling allowed
User-agent: Slurp
Crawl-delay: 60

User-agent: *
Disallow: /openads
Disallow: /48f6543196cbbdefb88f247a0a8e4375

User-agent: GPTBot
Disallow: /
# as per https://platform.openai.com/docs/gptbot

UserAgent: Bytespider
Disallow: /

Sitemap: https://taz.de/sitemap-google-news.xml
Sitemap: https://taz.de/sitemap-index.xml

# Legal notice: taz.de expressly reserves the right to use its content for commercial text and data mining (§ 44 b UrhG).
# The use of robots or other automated means to access taz.de or collect or mine data without the express permission of taz.de is strictly prohibited.
# taz.de may, in its discretion, permit certain automated access to certain taz.de pages.
# If you would like to apply for permission to crawl taz.de, collect or use data, please email lizenzen@taz.de.
sitemap.xml 200 OK
Type URL Set URLs 182 entries Valid XML Yes
Sample URLs:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.taz.de/
200https://taz.de/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
taz.de
PASS
taz.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.
Domain expiry

Unknown

SSL certificate

79 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2001:67c:13c::7a2:de

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 2001:67c:13c::7a2:de
Data source: whois (0.3s)

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 458 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
3 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
89 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
96 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
279 ms
Total Time Total request time from DNS lookup through full response.
458 ms

Connection waterfall

DNS Lookup 3 ms TCP Connect 89 ms TLS Handshake 96 ms Server Processing 91 ms Content Transfer 179 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback