leipzig.de

Checked 21 October 2026, 23:11 UTC · via 8.8.8.8
!Passed with warnings
21 passed 2 warnings 0 failed 6 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

dns1.leipzig.de, dns2.leipzig.de, dns3.leipzig.de, pns.dtag.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
dns1.leipzig.de, dns2.leipzig.de, dns3.leipzig.de, pns.dtag.de
NS in the zone
dns1.leipzig.de, dns2.leipzig.de, dns3.leipzig.de, pns.dtag.de
NameserverAddressesNetwork (AS)Glue
dns1.leipzig.de62.156.180.130AS3320 DTAG - Deutsche Telekom AG, DE62.156.180.130
dns2.leipzig.de62.156.180.133AS3320 DTAG - Deutsche Telekom AG, DE62.156.180.133
dns3.leipzig.de212.122.61.130AS16097 HLKOMM - HL komm Telekommunikations GmbH, DE212.122.61.130
pns.dtag.de194.25.0.125 2003:40:8000::100AS3320 DTAG - Deutsche Telekom AG, DE AS3320 DTAG - Deutsche Telekom AG, DE194.25.0.125 2003:40:8000::100

Checks

  • ✓ 4 nameservers #6
    Delegated to dns1.leipzig.de, dns2.leipzig.de, dns3.leipzig.de, pns.dtag.de.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: dns1.leipzig.de, dns2.leipzig.de, dns3.leipzig.de.
  • ✓ 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 3 IPv4 /24s and 1 IPv6 /48.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS16097 (HLKOMM - HL komm Telekommunikations GmbH, DE): 1 address; AS3320 (DTAG - Deutsche Telekom AG, DE): 4 addresses.
  • 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: dns1.leipzig.de, dns2.leipzig.de, dns3.leipzig.de.
    #13

Nameservers

info

5 of 5 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.leipzig.de 62.156.180.130NOERROR, 10 ms, authoritativenoyes / yesrefused[NONE]
dns2.leipzig.de 62.156.180.133NOERROR, 9 ms, authoritativenoyes / yesrefused[NONE]
dns3.leipzig.de 212.122.61.130NOERROR, 11 ms, authoritativenoyes / yesrefused[NONE]
pns.dtag.de 194.25.0.125NOERROR, 9 ms, authoritativenoyes / yesrefusedDomainNameServer
pns.dtag.de 2003:40:8000::100NOERROR, 7 ms, authoritativenoyes / yesrefusedDomainNameServer

Checks

  • ✓ All respond #14
    All 5 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: dns1.leipzig.de: "[NONE]"; dns2.leipzig.de: "[NONE]"; dns3.leipzig.de: "[NONE]"; pns.dtag.de: "DomainNameServer".
    #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 2026101602 · primary dns1.leipzig.de

Found

Primary (MNAME)
dns1.leipzig.de
Contact (RNAME)
hostmaster.leipzig.de
Serial
2026101602
Refresh / retry
10800 s / 1800 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
dns1.leipzig.de (62.156.180.130)2026101602
dns2.leipzig.de (62.156.180.133)2026101602
dns3.leipzig.de (212.122.61.130)2026101602
pns.dtag.de (194.25.0.125)2026101602
pns.dtag.de (2003:40:8000::100)2026101602

Checks

  • ✓ Serial 2026101602 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 30m, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns1.leipzig.de is one of the listed nameservers.
  • ✓ Contact hostmaster@leipzig.de #25
    The SOA RNAME hostmaster.leipzig.de means hostmaster@leipzig.de.
  • ✓ Date-based serial #26
    The serial 2026101602 follows the YYYYMMDDnn convention (2026-10-16).

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

warn

14 records at the apex

Found

Read from
62.156.180.130:53
TypeValueTTL
SOAdns1.leipzig.de. hostmaster.leipzig.de. 2026101602 10800 1800 1209600 36003600
NSpns.dtag.de.3600
NSdns2.leipzig.de.3600
NSdns1.leipzig.de.3600
NSdns3.leipzig.de.3600
A49.12.171.3460
A88.198.35.860
A49.12.171.3360
MX10 mailin.lecos-gmbh.de.3600
TXT"MS=ms83213498"3600
TXT"swisssign-check=AS5Qko3OaiqOZ6BbajnOX6oRzj4"3600
TXT"v=spf1 a:leipzig.de mx ip4:212.122.61.0/24 include:spf.protection.outlook.com -all"3600
TXT"apple-domain-verification=fmeph6kuxOFzLKon"3600
TXT"google-site-verification=9HCcnLHmRbUOiZ-xu21I6gkAHva19y8QJ_YjJqPUNd4"3600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1h; resolvers may use either.
    #32
  • ✓ 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