Skip to content
https://web.de

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from New York, United Stated
200 OK
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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 721 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 721 B Sitemaps referenced 0 User-agents Ai2Bot, Cincraw, Yandex, ClaudeBot, GPTBot, VelenPublicWebCrawler, *, Amazonbot, Applebot-Extended, FriendlyCrawler, ImagesiftBot, Meta-ExternalAgent, PetalBot, Semanticbot, googlebot-news, CCBot, cohere-ai, Diffbot, img2dataset, TimpiBot, AI2Bot Blocking No — crawling allowed
User-agent: *
Disallow: /deals/
Disallow: /test/
User-agent: googlebot-news
Disallow: /
Disallow: /magazine/*/thema/
Allow: /magazine/
Allow: /amp/
Allow: /$
User-agent: AI2Bot
User-agent: Ai2Bot
User-agent: Amazonbot
User-agent: Applebot-Extended
User-agent: CCBot
User-agent: Cincraw
User-agent: ClaudeBot
User-agent: cohere-ai
User-agent: Diffbot
User-agent: FriendlyCrawler
User-agent: GPTBot
User-agent: ImagesiftBot
User-agent: img2dataset
User-agent: Meta-ExternalAgent
User-agent: PetalBot
User-agent: Semanticbot
User-agent: TimpiBot
User-agent: VelenPublicWebCrawler
User-agent: Yandex
Disallow: /magazine/
Allow: /magazine/in-eigener-sache/
Allow: /magazine/unicef/
Allow: /magazine/so-arbeitet-die-redaktion/
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

155
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
2 A records, 8 ms lookup
PASS
2 A records, 8 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 82.165.229.83, 82.165.229.138
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-webde.ui-dns.de, ns-webde.ui-dns.biz, ns-webde.ui-dns.com, ns-webde.ui-dns.org
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: 8 ms
Got: 8 ms
A82.165.229.83, 82.165.229.138
AAAA—
CNAME—
NSns-webde.ui-dns.de, ns-webde.ui-dns.biz, ns-webde.ui-dns.com, ns-webde.ui-dns.org
MX
100 mx-ha03.web.de
100 mx-ha02.web.de
TXT
SPF v=spf1 redirect=_spf.web.de
_cddkhzzdq16uacbk5ilv3giqg9evcti
dzd5thdqpcp7f5d2p8l4vj5m5wdt21cs
g6ftbncmryg0y6h956jfd242s1z9tndk
kqpx82j1ql9zhqh54gdr8pj9f1ytvht1
facebook-domain-verification=ksd7xc6g15rm7xkdga4qcm9hasgkny
Trustpilot-Verification-kqvVskCm6JQ9Vg1qAmahpBSJ5tvZORbriFyVIk4E
google-site-verification=4kOTEODoJ0gf-gR71erruc56vEPOpyAuppJRHNC-hk0
google-site-verification=No4jlUg2OIV7IsI2UF0v792Q8HgI9Brnp7qary1nMAQ
google-site-verification=uHSKas5L2d4qGiqXVFuwvgu-In8Byl7dJXmTSLcOJuY
mindmanager-verification=1ea2fdbe5379cc0f8cfe95fa5ecfdc1ff943a7bd015aed8afb5717d...
CAALookup not available with standard resolver
Resolved in 8 ms

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://web.de

https://web.de

306 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://web.de200306 msHTTP/1.1Apache
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.web.de/
200https://web.de/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
web.de — hosted on IONOS
PASS
web.de — hosted on IONOS
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: IONOS
Got: AS8560
Domain expiry

Unknown

SSL certificate

155 days

Issued by Deutsche Telekom Security GmbH

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

IONOS

ASN AS8560

82.165.229.83

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 82.165.229.83
ASN AS8560 (IONOS-AS This is the joint network for IONOS, Fasthosts, Arsys, 1&1 Mail and Media and 1&1 Telecom. Formerly known as 1&1 Internet SE., DE)
Provider IONOS
Data source: whois (0.5s)

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

Connection waterfall

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

Send Feedback