thueringen-entdecken.de

Checked 22 October 2026, 00:40 UTC · via 8.8.8.8
!Passed with warnings
25 passed 1 warning 0 failed 7 info

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
NameserverAddressesNetwork (AS)Glue
ns1.telekom-domains.de80.157.195.92 2003:2:6:137:80:157:195:92AS3320 DTAG - Deutsche Telekom AG, DE AS3320 DTAG - Deutsche Telekom AG, DE80.157.195.92 2003:2:6:137:80:157:195:92
ns2.telekom-domains.de212.185.24.1 2003:180:a::53AS3320 DTAG - Deutsche Telekom AG, DE AS3320 DTAG - Deutsche Telekom AG, DE212.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

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.telekom-domains.de 80.157.195.92NOERROR, 7 ms, authoritativenoyes / yesrefuseddns
ns1.telekom-domains.de 2003:2:6:137:80:157:195:92NOERROR, 7 ms, authoritativenoyes / yesrefuseddns
ns2.telekom-domains.de 212.185.24.1NOERROR, 3 ms, authoritativenoyes / yesrefuseddns
ns2.telekom-domains.de 2003:180:a::53NOERROR, 7 ms, authoritativenoyes / yesrefuseddns

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 2026092903 · primary ns1.telekom-domains.de

Found

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

Serial per nameserver

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

Checks

  • ✓ Serial 2026092903 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 2026092903 follows the YYYYMMDDnn convention (2026-09-29).

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 tagAlgorithmDigestMatches a key
44959RSASHA256 (8)SHA256 3AE7370C0B8254F3…yes

DNSKEY in the zone

Key tagRoleAlgorithm
44959KSK (257)RSASHA256 (8)
17613ZSK (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 44959 (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

15 records at the apex

Found

Read from
80.157.195.92:53
TypeValueTTL
SOAns1.telekom-domains.de. dns.telekom.de. 2026092903 10800 3600 2419200 4320043200
NSns1.telekom-domains.de.43200
NSns2.telekom-domains.de.43200
A20.240.240.1053600
AAAA2603:1020:1001:6::cb3600
MX10 thueringenentdecken-de02e.mail.protection.outlook.com.3600
TXT"canva-site-verification=LLSJbfiwY_m4CBe2d-j3xA"3600
TXT"v=spf1 a mx ip4:217.237.184.228/29 ip4:185.98.184.0/24 ip4:193.53.247.252 include:spf.protection.outlook.com include:ispgateway.de include:spf.mailjet.com include:sendgrid.net include:_spf.psm.knowbe4.com -all"3600
TXT"apple-domain-verification=fnTHin3wnhCMvZmL"3600
TXT"LdBhUXsCnYouAd5S+fM3J1Pwr5CfJ9SwNdLxp05Nul85ES7IfPUd8xhE4A1tixYOfprmRF+pAPWoJbeOttk2eg=="3600
TXT"facebook-domain-verification=3258l6xp1whvx85wx1vxmwniinmm69"3600
TXT"92139a7efa4a2c4d83794fb9a1109455"3600
TXT"MS=ms68275076"3600
TXT"pinterest-site-verification=9f16c6c566cb956ee6017e86d3080cd2"3600
TXT"google-site-verification=_Z6U8adjYEuLSiIF2JGNogq2eTS_YsosAyDVg9mgQH4"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