Domain report: telekom-stiftung.de

Registration

info

.de country-code

Found

TLD: .de (country-code)
ICANN policies apply: no

Checks

i

.de is a country-code TLD (ccTLD)

Country-code TLD: governed by its local registry under national policy, not by an ICANN contract. Registrar accreditation, dispute resolution and RDAP/WHOIS rules are set by the registry.

#1
✓ TLD delegated and signed #2

.de is delegated in the root zone and DNSSEC-signed.
i

Registration data not available

No registration data via RDAP: the registry of .de offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.

#3

Delegation

info

ns1.telekom-domains.de, ns2.telekom-domains.de

Found

Parent zone: de
Delegation from: a.nic.de (194.0.0.53)
NS at the parent: ns1.telekom-domains.de, ns2.telekom-domains.de
NS in the zone: ns1.telekom-domains.de, ns2.telekom-domains.de

Nameserver	Addresses	Network (AS)	Glue
ns1.telekom-domains.de	80.157.195.92 2003:2:6:137:80:157:195:92	AS3320 DTAG - Deutsche Telekom AG, DE AS3320 DTAG - Deutsche Telekom AG, DE	80.157.195.92 2003:2:6:137:80:157:195:92
ns2.telekom-domains.de	212.185.24.1 2003:180:a::53	AS3320 DTAG - Deutsche Telekom AG, DE AS3320 DTAG - Deutsche Telekom AG, DE	212.185.24.1 2003:180:a::53

Checks

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.telekom-domains.de, ns2.telekom-domains.de.

#6
✓ Parent and zone agree #7

The parent delegation and the zone's NS records list the same nameservers.
✓ No glue needed #8

All nameservers are outside the zone, so no glue records are needed.
✓ All names resolve #9

Every nameserver name has an address and is not an alias.
✓ Nameservers in different networks #10

The nameservers are spread over 2 IPv4 /24s and 2 IPv6 /48s.
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS3320 (DTAG - Deutsche Telekom AG, DE): 4 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.

#11
i

All nameserver names under .de

All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.

#12
✓ All reachable over IPv6 #13

Every nameserver has an IPv6 address.

Nameservers

info

4 of 4 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.telekom-domains.de 80.157.195.92	NOERROR, 7 ms, authoritative	no	yes / yes	refused	dns
ns1.telekom-domains.de 2003:2:6:137:80:157:195:92	NOERROR, 11 ms, authoritative	no	yes / yes	refused	dns
ns2.telekom-domains.de 212.185.24.1	NOERROR, 4 ms, authoritative	no	yes / yes	refused	dns
ns2.telekom-domains.de 2003:180:a::53	NOERROR, 4 ms, authoritative	no	yes / yes	refused	dns

Checks

✓ All respond #14

All 4 nameserver addresses answered.
✓ All authoritative #15

Every responding nameserver answers authoritatively for the zone.
✓ No recursion #16

The nameservers do not answer recursive queries for other domains.
i

Identifying string disclosed

These nameservers answer version queries with a string that is not a version number: ns1.telekom-domains.de: "dns"; ns2.telekom-domains.de: "dns".

#17
✓ Zone transfers refused #18

No nameserver allows a zone transfer to the public.
✓ TCP supported #19

All nameservers answer over TCP.
✓ EDNS supported #20

All nameservers support EDNS(0).
✓ Public addresses #21

All nameserver addresses are publicly routable.

SOA

pass

serial 2026082003 · primary ns1.telekom-domains.de

Found

Primary (MNAME): ns1.telekom-domains.de
Contact (RNAME): dns.telekom.de
Serial: 2026082003
Refresh / retry: 10800 s / 3600 s
Expire: 2419200 s
Negative TTL: 43200 s

Serial per nameserver

Nameserver	Serial
ns1.telekom-domains.de (80.157.195.92)	2026082003
ns1.telekom-domains.de (2003:2:6:137:80:157:195:92)	2026082003
ns2.telekom-domains.de (212.185.24.1)	2026082003
ns2.telekom-domains.de (2003:180:a::53)	2026082003

Checks

✓ Serial 2026082003 everywhere #22

All nameservers serve the same version of the zone.
✓ Timers within recommendations #23

SOA refresh 3h, retry 1h, expire 28d, negative TTL 12h.
✓ Primary is a public nameserver #24

The primary nameserver ns1.telekom-domains.de is one of the listed nameservers.
✓ Contact dns@telekom.de #25

The SOA RNAME dns.telekom.de means dns@telekom.de.
✓ Date-based serial #26

The serial 2026082003 follows the YYYYMMDDnn convention (2026-08-20).

DNSSEC

warn

Signed, DS published at parent

Found

Validated by resolver: yes
Denial of existence: NSEC3
NSEC3: 0 iterations, 0-byte salt
Signatures valid until: 29 October 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
41191	RSASHA256 (8)	SHA256 7568E26538B514AF…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
41191	KSK (257)	RSASHA256 (8)
53893	ZSK (256)	RSASHA256 (8)

Checks

✓ Signed and validated #27

The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
✓ DS matches a key #28

The DS record at the parent matches a key in the zone: key tag 41191 (SHA256).
✓ Modern algorithms #29

Key algorithms: RSASHA256 (8).
!

Signatures expire soon

The earliest signature expires at 2026-10-29 00:00 UTC (in 167h0m0s). Check that automatic re-signing works.

#30
✓ NSEC3 as recommended #31

The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

10 records at the apex

Found

Read from: 80.157.195.92:53

Type	Value	TTL
SOA	ns1.telekom-domains.de. dns.telekom.de. 2026082003 10800 3600 2419200 43200	43200
NS	ns2.telekom-domains.de.	43200
NS	ns1.telekom-domains.de.	43200
A	85.215.47.164	3600
AAAA	2a02:247a:231:6400::1	3600
MX	10 mail.bw-tech.org.	3600
TXT	"miro-verification=bc8e52558a4530683e3f476eb9365cdfbb003c8c"	3600
TXT	"google-site-verification=AcC41cI0stfUyPmkbLnXueDxMlc0wYRYwIgNZJiHBnU"	3600
TXT	"MS=ms56116703"	3600
TXT	"v=spf1 a mx -all"	3600

Checks

✓ TTLs within range #32

TTLs: A 1h, AAAA 1h, MX 1h, NS 12h. The NS TTL at the parent is 1d and in the zone 12h; resolvers may use either.
✓ No CNAME at the apex #33

The zone apex has no CNAME record.
✓ No wildcard #34

Names that don't exist return NXDOMAIN.
i

No CAA records

Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.

#35