Skip to content
https://telekom.net

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
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.

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
Crawlability
Action
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 10240 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

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 10240 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
<!doctype html>
<html lang="en" class="colorscheme-light no-js"   >

<head >
<script>document.documentElement.className = document.documentElement.className.replace(/\bno-js\b/,'') + ' js';</script>
<script>
window.dtinfo={};
window.dtinfo.id="64";
window.dtinfo.type="CMChannel";
</script> <meta charset="UTF-8"/>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<meta http-equiv="content-language" content="en">
<meta http-equiv="x-ua-compatible" content="ie=edge">
<title >Corporate Website: Information about the Group | Deutsche Telekom</title>
<meta name="description" content="Deutsche Telekom is one of the world&#39;s leading integrated telecommunications companies. Find information about the Group on our corporate website." />
<meta name="date" content="2025-10-30">
<meta name="page-topic" content="Home">
<meta property="og:type" content="website"/>
<meta property="og:title" content="Home"/>
<meta property="og:url" content="https://www.telekom.com/en"/>
<meta property="og:locale" content="en_DE"/>
<meta property="og:description" content="The corporate website of Deutsche Telekom Group."/>
<meta property="og:image" content="https://www.telekom.com/resource/image/433106/landscape_ratio2x1/3000/1500/2f29011d7414bf84a653c7d10de6e943/1B9C77FA7C47CA5E913F6DC08584DAA9/bi-t-logo-0056-en.jpg"/>
<meta name="twitter:image" content="https://www.telekom.com/resource/image/433106/landscape_ratio2x1/3000/1500/2f29011d7414bf84a653c7d10de6e943/1B9C77FA7C47CA5E913F6DC08584DAA9/bi-t-logo-0056-en.jpg" />
<meta property="og:image:secure_url" content="https://www.telekom.com/resource/image/433106/landscape_ratio2x1/3000/1500/2f29011d7414bf84a653c7d10de6e943/1B9C77FA7C47CA5E913F6DC08584DAA9/bi-t-logo-0056-en.jpg"/>
<meta name="twitter:site" content="https://www.telekom.com/en">
<meta property="fb:app_id" content="883623201814224">
<meta name="google-site-verification" content="KhQ_D6R3_X3JLXi087ytogFDfiYGg_utnA9RWJ8xdUU">
<meta name="google-site-verification" content="DEK_sTKNLoaEIRfOL9aN4YkodXCjHRB9dKDFR2oVfJU">
<meta name="author" content="Deutsche Telekom AG">
<meta name="publisher" content="Deutsche Telekom AG">
<meta name="company" content="Deutsche Telekom AG">
<meta name="reply-to" content="medien@telekom.de">
<meta name="distribution" content="global">
<meta name="revisit-after" content="period">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:creator" content="Deutsche Telekom AG">
<meta property="og:type" content="article">
<meta name="viewport" content="width=device-width, initial-scale=1"/>
<link rel="icon" href="/resource/crblob/1093970/f58449c3f626c8c3337949bfdfab0fab/favicon-ico-data.ico" sizes="any">
<link rel="icon" href="/resource/crblob/1021450/05272d789be738a790edff915a075ec4/favicon-svg-data.svg" type="image/svg+xml">
<link rel="apple-touch-icon" href="/resource/crblob/1021452/ad5c28cdbc4e452445cb1bb232b860c1/favicon-180x180-png-data.png">
<link rel="icon" type="image/png" sizes="192x192" href="/resource/crblob/1021454/ba522dc5a47eb048178994efa77205c5/favicon-192x192-png-data.png">
<link rel="icon" type="image/png" sizes="512x512" href="/resource/crblob/1021456/f0a9ea5e908c2fa6b4cce29a5b2f8425/favicon-512x512-png-data.png">
<link rel="canonical" href="https://www.telekom.com/en"/>
<link rel="alternate" hreflang="de" href="https://www.telekom.com/de"/>
<link rel="alternate" hreflang="en" href="https://www.telekom.com/en"/>
<link rel="preload" href="/resource/crblob/1021682/ad396e353ff1ea0eccc2c156e663238e/teleneo-thin-woff-data.woff" as="font" type="font/woff" crossorigin="anonymous">
<link rel="prefetch" href="/resource/crblob/1021680/2fc1bb68d9930f87ea79e48f87238a60/teleneo-regularitalic-woff-data.woff" as="font" type="font/woff" crossorigin="anonymous">
<link rel="preload" href="/resource/crblob/1021674/cef4875f104fc282b3b458b2dcb80be9/teleneo-medium-woff-data.woff" as="font" type="font/woff" crossorigin="anonymous">
<link rel="prefetch" href="/resource/crblob/1021676/b467d6cdb9e76abd49532ecebfbe940b/teleneo-mediumitalic-woff-data.woff" as="font" type="font/woff" crossorigin="anonymous">
<link rel="preload" href="/resource/crblob/1021666/4700ef9398ecb245df8891cadae919ab/teleneo-bold-woff-data.woff" as="font" type="font/woff" crossorigin="anonymous">
<link rel="preload" href="/resource/crblob/1021670/9479a1f7ee32d142c54bb28c800b21f5/teleneo-extrabold-woff-data.woff" as="font" type="font/woff" crossorigin="anonymous">
<style type="text/css">
@font-face {
font-family: "TeleNeo";
font-style: normal;
font-weight: 200;
font-display: swap;
src: url("/resource/crblob/1021682/ad396e353ff1ea0eccc2c156e663238e/teleneo-thin-woff-data.woff") format("woff");
}
@font-face {
font-family: "TeleNeo";
font-style: italic;
font-weight: 400;
font-display: swap;
src: url("/resource/crblob/1021680/2fc1bb68d9930f87ea79e48f87238a60/teleneo-regularitalic-woff-data.woff") format("woff");
}
@font-face {
font-family: "TeleNeo";
font-style: normal;
font-weight: 600;
font-display: swap;
src: url("/resource/crblob/1021674/cef4875f104fc282b3b458b2dcb80be9/teleneo-medium-woff-data.woff") format("woff");
}
@font-face {
font-family: "TeleNeo";
font-style: italic;
font-weight: 600;
font-display: swap;
src: url("/resource/crblob/1021676/b467d6cdb9e76abd49532ecebfbe940b/teleneo-mediumitalic-woff-data.woff") format("woff");
}
@font-face {
font-family: "TeleNeo";
font-style: normal;
font-weight: 700;
font-display: swap;
src: url("/resource/crblob/1021666/4700ef9398ecb245df8891cadae919ab/teleneo-bold-woff-data.woff") format("woff");
}
@font-face {
font-family: "TeleNeo";
font-style: normal;
font-weight: 800;
font-display: swap;
src: url("/resource/crblob/1021670/9479a1f7ee32d142c54bb28c800b21f5/teleneo-extrabold-woff-data.woff") format("woff");
}
</style>
<link rel="stylesheet" href="/resource/themes/com/css/com-1021854-20.css" >
<script src="/resource/themes/com/js/chunkPathById-1021764-40.js" defer="false" ></script>
<script type="text/javascript">
window.onload = function () {
var xhr = new XMLHttpRequest();
xhr.open('GET', "/dynamic/service/guid/64", true);
xhr.send();
};
</script>
</head>
<body id="top" class="">
<header class="site-header">
<div class="header-wrapper">
<com-header class="header-navarea">
<div class="container">
<div class="navarea-wrapper">
<div class="navarea-content">
<div class="logo-area">
<div class="logo-area__inner">
<a href="/en" title="Home">
<svg focusable="false" role="img">
<use href="#brand__logo"></use>
</svg>
</a>
</div>
</div>
<nav class="nav-main desktop" aria-label="Main Navigation" data-subnav-label="Overview" data-level-up-label="go back one level of navigation">
<ul class="nav-list">
<li><a href="/en/company" class="level-1"><span>Company</span></a>
<nav class="subnav"><div class="subnav-wrapper">
<div class="items">
<a class="newCol level-2" href="/en/company/companyprofile/company-profile-625808" title="Company profile" ><span>Company profile</span></a><a class="level-2" href="/en/company/worldwide" title="Worldwide" ><span>Worldwide</span></a><a class="level-2" href="/en/company/topic-specials" title="Topic specials" ><span>Topic specials</span></a><a class="level-2" href="/en/company/data-privacy-and-security" title="Data privacy and security" ><span>Data privacy and security</span></a><a class="level-2" href="/en/company/digital-responsibility" title="Digital Responsibility" ><span>Digital Responsibility</span></a><a class="level-2" href="/en/company/management-unplugged" title="Management unplugged" ><span>Management unplugged</span></a><a class="newCol level-2" href="/en/company/strategy" title="Strategy" ><span>Strategy</span></a><a class="level-2" href="/en/company/management-and-corporate-governance" title="Management and Corporate Governance" ><span>Management and Corporate Governance</span></a><ul class="nav-list">
<li><a class="level-3" href="/en/company/management-and-corporate-governance/board-of-management" title="Board of Management" ><span>Board of Management</span></a></li>
<li><a class="level-3" href="/en/company/management-and-corporate-governance/supervisory-board" title="Supervisory Board" ><span>Supervisory Board</span></a></li>
<li><a
class="external external--module level-3"
target="_blank"
href="https://report.telekom.com/remuneration"
title="Link to external website: Remuneration"
><span>Remuneration</span></a></li>
<li><a class="level-3" href="/en/company/management-and-corporate-governance#1086370" title="Management and Corporate Governance" ><span>Reports and declarations</span></a></li>
</ul><a class="level-2" href="/en/company/works-council" title="Works council" ><span>Works council</span></a><a class="newCol level-2" href="/en/company/compliance" title="Compliance" ><span>Compliance</span></a><ul class="nav-list">
<li><a class="level-3" href="/en/company/compliance/code-of-conduct" title="Code of Conduct" ><span>Code of Conduct</span></a></li>
<li><a class="level-3" href="/en/company/compliance/whistleblowerportal" title="Whistleblowerportal - TellMe" ><span>Whistleblowerportal - TellMe</span></a></li>
</ul><a class="level-2" href="/en/company/human-resources" title="Human resources" ><span>Human resources</span></a><ul class="nav-list">
<li><a class="level-3" href="/en/company/human-resources/diversity" title="Diversity" ><span>Diversity</span></a></li>
</ul><a class="newCol level-2" href="/en/company/sponsoring" title="Sponsoring" ><span>Sponsoring</span></a><a class="level-2" href="/en/company/brand" title="Brand" ><span>Brand</span></a><a class="level-2" href="/en/company/global-procurement" title="Procurement" ><span>Procurement</span></a> </div> <a title="close menu" class="layer-close" href="#"></a>
</div></nav></li>
<li><a href="/en/corporate-responsibility" class="level-1"><span>Corporate Responsibility</span></a>
<nav class="subnav"><div class="subnav-wrapper">
<div class="items">
<a class="newCol level-2" href="/en/corporate-responsibility/our-approach" title="Our approach" ><span>Our approach</span></a><ul class="nav-list">
<li><a class="level-3" href="/en/corporate-responsibility/governance/details/our-approach-353746" title="CR Strategy" ><span>CR Strategy</span></a></li>
<li><a class="level-3" href="/en/company/digital-responsibility/cdr" title=
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
40 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

40
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
1 A records, 46 ms lookup
PASS
1 A records, 46 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 80.158.66.24
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns1.telekom.net, pns.dtag.de, dns2.telekom.de, dns1.telekom.de
Info::
1 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: 46 ms
Got: 46 ms
A80.158.66.24
AAAA—
CNAME—
NSns1.telekom.net, pns.dtag.de, dns2.telekom.de, dns1.telekom.de
MX
100 mailin.ng.telekom.net
TXT
SPF v=spf1 include:_spf.telekom.com ~all
zone-ownership-verification-2d626db757890f5f9f21d110fcb306dd9b7f1ff49c771a59b056...
_telesec-domain-validation=2A35BF51C9A82F471E369CFA1FF09FED163FC3F97C71A85785CB8...
CAALookup not available with standard resolver
Resolved in 46 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
1 redirect(s), 526 ms total
PASS
1 redirect(s), 526 ms total
Info::
Single redirect
Got: https://telekom.net → https://www.telekom.com (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 526 ms total
Got: 526 ms
Info::
Cross-domain redirect detected

https://telekom.net

140 ms · HTTP/1.1

301

https://www.telekom.com

385 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://telekom.net301140 msHTTP/1.1Apache
2https://www.telekom.com200385 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

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.net/
200https://telekom.net/

Preferred variant: non-www

HTTP → HTTPS

301http://telekom.net/ → https://www.telekom.com

Consistent

A
Domain Intelligence
telekom.net — via Deutsche Telekom AG, 29 years, 3 months old, hosted on SCZN-AS, DE
PASS
telekom.net — via Deutsche Telekom AG, 29 years, 3 months old, hosted on SCZN-AS, DE
Warning::
Domain expires in 41 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires May 28, 2026
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Deutsche Telekom AG
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: SCZN-AS, DE
Got: AS34086
Domain expiry

EXPIRED

May 28, 2026

SSL certificate

40 days

Issued by Let's Encrypt

Domain age

29 years, 3 months

Registered May 29, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

SCZN-AS, DE

ASN AS34086

80.158.66.24

Registrar

Deutsche Telekom AG

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Deutsche Telekom AG
Created May 29, 1997 (29 years, 3 months ago)
Expires May 28, 2026 (1 months)
Last Updated May 28, 2025
Name Servers dns1.telekom.de, dns2.telekom.de, ns1.telekom.net, pns.dtag.de
DNSSEC Not enabled
Hosting
IP Address 80.158.66.24
ASN AS34086 (SCZN-AS, DE)
Provider SCZN-AS, DE
Data source: rdap (0.4s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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

Connection waterfall

DNS Lookup 46 ms TCP Connect 33 ms TLS Handshake 37 ms Server Processing 64 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