dkms.de

Checked 21 October 2026, 22:14 UTC · via 8.8.8.8
!Passed with warnings
21 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, 11 ms, authoritativenoyes / yesrefuseddns
ns2.telekom-domains.de 212.185.24.1NOERROR, 3 ms, authoritativenoyes / yesrefuseddns
ns2.telekom-domains.de 2003:180:a::53NOERROR, 8 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 2026100601 · primary ns1.telekom-domains.de

Found

Primary (MNAME)
ns1.telekom-domains.de
Contact (RNAME)
dns.telekom.de
Serial
2026100601
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)2026100601
ns1.telekom-domains.de (2003:2:6:137:80:157:195:92)2026100601
ns2.telekom-domains.de (212.185.24.1)2026100601
ns2.telekom-domains.de (2003:180:a::53)2026100601

Checks

  • ✓ Serial 2026100601 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 2026100601 follows the YYYYMMDDnn convention (2026-10-06).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

info

22 records at the apex

Found

Read from
80.157.195.92:53
TypeValueTTL
SOAns1.telekom-domains.de. dns.telekom.de. 2026100601 10800 3600 2419200 4320043200
NSns2.telekom-domains.de.43200
NSns1.telekom-domains.de.43200
A217.110.157.443600
MX10 mx02.dkms.de.40000
MX10 mx01.dkms.de.40000
TXT"bw=XeNDxb0hrXNerTWG9cIYVZtLxlgN8QSP9MnZ5GgkDuDI"3600
TXT"MS=ms78330314"3600
TXT"google-site-verification=I05SNGLb0Ythg4vI2QM3YT2t5VV4woIfu5fGBJRiMdI"3600
TXT"brevo-code:dca8d20af6205f8e3621732bae444dca"3600
TXT"JZzRKSuOPNv01dTmw1wCbJ/tF2/I2Gqd5vwr5ZpvFnbg16UT/iOtCVtTmt5l7e6wxWPfAM07dDAbYJcCxULYaA=="3600
TXT"ftapi-domain-verification=96mIP3ToeWZzs5hB0PtNpGkJQIkYN6SM"3600
TXT"google-site-verification=IzzhIrWfsR_WTl5TdpgHY_E_SGUFQSDRx3msw9ml-_g"3600
TXT"openai-domain-verification=dv-KPnB6AwgBCmWWbMHFTlxO3yE"3600
TXT"v=spf1 mx ip4:40.92.0.0/15 ip4:52.100.0.0/15 ip4:40.107.0.0/16 ip4:52.102.0.0/16 ip4:104.47.0.0/17 ip4:52.103.0.0/17 ip4:204.220.160.0/19 ip4:143.55.224.0/20 ip4:159.112.240.0/20 ip4:159.135.224.0/20 ip4:161.38.192.0/20 ip4:198.244.48.0/20 ip4:69.72.32.0/" "20 ip4:46.183.40.0/21 ip4:80.241.56.0/21 ip4:87.253.232.0/21 ip4:166.78.68.0/22 ip4:185.189.236.0/22 include:_spf.salesforce.com include:spf.protection.outlook.com include:_spf.jpberlin.de include:_spf.zimpel.de ~all"3600
TXT"miro-verification=96cbcc1f2d6706242abe1071b7dee3fab5edfab7"3600
TXT"figma-domain-verification=ed760d7cce67e73055bc2113a73e0f85892051bc59844f675006546fc4d33503-1784620890"3600
TXT"canva-site-verification=I_Pwc8zQ4PxjZmyMM97O3g"3600
TXT"google-site-verification=XNP7fbyfrEiJ4BlXrJJO3KWlEfJz1Sa5qkXfzpjQhgI"3600
TXT"cisco-ci-domain-verification=602a105e7cbd8db1255153902f0ac146cb438c93915681e08a450ca76b3aa5f8"3600
TXT"atlassian-domain-verification=3ViSaCZ4ICJTgLCcHmLAyJvbljfSK6f8HIZSg3mHuZFf7YT21Sps2c3rFa82tIPH"3600
TXT"MEKn+V7z4ncr0yc+LNQv3Tg6b1Yk2YcGCUxxRKTtYrfY8E3/hELwx4EFXQGTlgxfiGsbKQfNnkgbefKIkRaMRA=="3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 11h6m40s, 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