Skip to content
https://telekom.de

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
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.

B
Redirect Chain
2 redirect(s), 354 ms total
REVIEW
2 redirect(s), 354 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect

https://telekom.de

103 ms · HTTP/1.1

301

https://www.telekom.de/

145 ms · HTTP/1.1

301

https://www.telekom.de/start

107 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://telekom.de301103 msHTTP/1.1
2https://www.telekom.de/301145 msHTTP/1.1
3https://www.telekom.de/start200107 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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
TLS Certificate Expiry & Recommendations
329 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
3 A records, 115 ms lookup
PASS
3 A records, 115 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 3.67.146.210, 3.75.56.200, 63.176.75.230
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: dns1.telekom.de, ns1.telekom.net, pns.dtag.de, dns2.telekom.de
Info::
3 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: 115 ms
Got: 115 ms
A3.67.146.210, 3.75.56.200, 63.176.75.230
AAAA—
CNAME—
NSdns1.telekom.de, ns1.telekom.net, pns.dtag.de, dns2.telekom.de
MX
100 mailin.ng.telekom.net
200 mailin22.telekom.de
200 mailin42.telekom.de
TXT
Dynatrace-site-verification=96bc3bd6-5d9d-453d-be69-504b23c4e472__e2jn5ah8dr7bql...
miro-verification=089da153dee3b2bdebb4e4940c914abf39a26035
jQ5A8b2Q7E4HyW43qxNGnwFURfay0p6vHBujf8d4fdIYmySsRB2prgHkNJFXQwD+wazvOVaY2l8FpABr...
docusign=6c675f35-a345-4def-8efa-8cde758ccc7e
677d99f0f35f8908c36db37733460d077cefca982e1356c01f8dc9ab5fa3f3f
infoblox-domain-mastery=b68054e96cb7a363f678e488ce55e707d2d7745b6a2ba8caff49a238...
adobe-idp-site-verification=22f64faf827865075c1f3f1d814848b67f1e2ebe012796f5b958...
SPF v=spf1 include:_spfa.telekom.com ~all
MS=ms35884038
webexdomainverification.IPJP=5d9af4ca-0ad4-401d-a88c-4828ffcf90b5
openai-domain-verification=dv-T5JfH1eMRERJ2s29zq4XiPTR
google-site-verification=3aMWAc5xlQdD9Sr5FbjOVk5ZWcXHz3FfuT1ykz7ovF8
ZOOM_verify_jIbBUG459R326KhFKOX8uB
docusign=386bf6b9-1928-48c8-9f8a-c7b551459aa2
mongodb-site-verification=SVkEFwDo0PL5wQKGajdr2PeA7Tlr9Yn0
google-site-verification=DKA9MWpvwcF2sZXgChNZHK5K8s9GFaUJnomtQQoa83o
google-site-verification:syCIRr6VyoifbE6Wpg-dmA-LMXJwh5QE-Hm4eEDU8as
figma-domain-verification=b9c1825057675ccb105df5798a5d27c8bd20a6c5d604e47d22e13b...
webexdomainverification.BSJE=bff842e9-03f4-44ca-b219-082c41a93969
google-gws-recovery-domain-verification=43219657
WswlzVPlM/dCeERhN7//wzB6tFfJZ1XmYfNOWOrtejyjbMUHvprNl2q/aSJovjIIdeCUnaiIU+04M7Hy...
atlassian-domain-verification=RYDBmArxP6DhrshwBcIZoo3ZF26BwxWI06Enb8LaC7YfF2d8cP...
6f13fba4457ecc5c8e4a13ba55f5bcfd543188febf1506a8d1dc024621b3588
apple-domain-verification=RAsXcbTcwd0x4STR
5767dbc9e0bea7f45ca86eb79002a6da39a2b5ba6e6e6e7bfa69a4583acc2a9
atlassian-domain-verification=uGLUdpD2IVY19OJG5SQbVpV497SMTPJPSKYbkZRnWtMwczrdbH...
google-site-verification=d1yVyM6bmOcSDJXc5ot_SrOyXXKqgEu8Ep6SSCHgJb4
CAALookup not available with standard resolver
Resolved in 115 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+
Crawlability
robots.txt present, sitemap with 2661 URLs
PASS
robots.txt present, sitemap with 2661 URLs
Info::
robots.txt is present
Got: 151 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2661 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 151 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /is-bin/intershop.enfinity/BOS/

Disallow: /is-bin/intershop.static/


Sitemap: https://www.telekom.de/content/robots/sitemap
sitemap.xml 200 OK
Type URL Set URLs 2661 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.telekom.de/
200https://telekom.de/

Preferred variant: non-www

HTTP → HTTPS

301http://telekom.de/ → https://telekom.de:443/

Consistent

A+
Domain Intelligence
telekom.de — hosted on AWS
PASS
telekom.de — hosted on AWS
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: AWS
Got: AS16509
Domain expiry

Unknown

SSL certificate

329 days

Issued by Amazon

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

63.176.75.230

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 63.176.75.230
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
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

A+
HTTP Probe Timing
Total 138 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
22 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
37 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.
138 ms
Total Time Total request time from DNS lookup through full response.
138 ms

Connection waterfall

DNS Lookup 22 ms TCP Connect 37 ms TLS Handshake 39 ms Server Processing 40 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