Skip to content
https://test.de

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
9
3 PASS 5 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
Redirect Chain
1 redirect(s), 1592 ms total
REVIEW
1 redirect(s), 1592 ms total
Info::
Single redirect
Got: https://test.de → https://www.test.de/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1592 ms total
Got: 1592 ms

https://test.de

1057 ms · HTTP/1.1

301

https://www.test.de/

534 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://test.de3011057 msHTTP/1.1
2https://www.test.de/200534 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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

C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.test.de/
200https://test.de/

Inconsistent — duplicate content risk

HTTP → HTTPS

307http://test.de/ → https://test.de/

Use 301 (permanent) instead of 302 (temporary)

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

Connection waterfall

DNS Lookup 186 ms TCP Connect 163 ms TLS Handshake 361 ms Server Processing 195 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
73 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

73
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, 183 ms lookup
PASS
1 A records, 183 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 128.65.209.96
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: dns3.iwelt-ag.de, dns2.iwelt-ag.net, dns.iwelt-ag.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::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 183 ms
Got: 183 ms
A128.65.209.96
AAAA—
CNAME—
NSdns3.iwelt-ag.de, dns2.iwelt-ag.net, dns.iwelt-ag.net
MX
10 sw-proxy01.stiftung-warentest.de
20 mx.colt.net
TXT
google-site-verification=gSjWCcpkGgrzWYsBnodFOql3lGv0QuUefyv8G_hxalk
google-site-verification=n2KldH97TSAaOkv_07PyB_O85HLNRBl_ZZz4yJ4mZOc
google-site-verification=yoIazl7YOALcEaxLVW7_qDnRkBcUK7Zqq0NqVY73Iiw
google-site-verification=RuWN3Sj86zMWFKgLbDLRgau7n33k7t5p43QMHisAKCI
apple-domain-verification=3QULLkVSDqLP8spQBHk4D0dUUCXSYeREm8kd7WLtDSs
google-site-verification=Y93N542x1M_8JPZ-w5-R2JU7v8b-_XJCVTG-GpegmQ4
google-site-verification=o3DL6kBjWm0pv2hkbN9zrTGgFSiaEto8AiP-cVfQ-Hs
CAALookup not available with standard resolver
Resolved in 183 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+
Crawlability
robots.txt present, sitemap with 14 URLs
PASS
robots.txt present, sitemap with 14 URLs
Info::
robots.txt is present
Got: 1423 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 14 entries
Info::
Sitemap index with 14 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1423 B Sitemaps referenced 2 User-agents CCBot, Google-Extended, ClaudeBot, *, GPTBot, ChatGPT-User, anthropic-ai, FacebookBot, monitoring360bot, Claude-Web, YouBot, AmazonBot, YandexBot, PetalBot, SemrushBot, Omgilibot, Diffbot, UptimeRobot, SeobilityBot Blocking No — crawling allowed
User-agent: GPTBot
Disallow: /
Allow: /unternehmen/

User-agent: ChatGPT-User
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: Google-Extended
Disallow: /
Allow: /unternehmen/

User-agent: anthropic-ai
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: ClaudeBot
Disallow: /
Allow: /unternehmen/

User-agent: YouBot
Disallow: /

User-agent: Omgilibot
Disallow: /

User-agent: FacebookBot
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: AmazonBot
Disallow: /

User-agent: monitoring360bot
Disallow: /

User-agent: UptimeRobot
Disallow: /

User-agent: YandexBot
Disallow: /

User-agent: PetalBot
Disallow: /

User-agent: SeobilityBot
Disallow: /

User-agent: SemrushBot
Disallow: /

User-agent: *
Disallow: /bezahlen/
Disallow: /meintest/
Disallow: /payment/
Disallow: /statusmeldung/
Disallow: /suche/
Disallow: /filestore/
Allow: /meintest/login/

Sitemap: https://www.test.de/sitemap
Sitemap: https://www.test.de/sitemap/news

Legal notice: Stiftung Warentest expressly reserves the right to use its content for commercial text and data mining (para. 44 b UrhG).

The use of robots or other automated means to access http://test.de  or collect or mine data without the express permission of Stiftung Warentest is strictly prohibited.

Stiftung Warentest may, in its discretion, permit certain automated access to certain http://test.de  pages.

The rights from para. 60d UrhG remain unaffected.
sitemap.xml 200 OK
Type Sitemap Index URLs 14 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
test.de — hosted on LINK11 Link11 GmbH, DE
PASS
test.de — hosted on LINK11 Link11 GmbH, 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: LINK11 Link11 GmbH, DE
Got: AS34309
Domain expiry

Unknown

SSL certificate

73 days

Issued by GlobalSign nv-sa

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

LINK11 Link11 GmbH, DE

ASN AS34309

128.65.209.96

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 128.65.209.96
ASN AS34309 (LINK11 Link11 GmbH, DE)
Provider LINK11 Link11 GmbH, DE
Data source: whois (1.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