schmorp.de

Checked 22 October 2026, 00:01 UTC · via 8.8.8.8
✗Problems found
16 passed 4 warnings 1 failed 8 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

warn

ns1.schmorp.de, ns2.schmorp.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.schmorp.de, ns2.schmorp.de
NS in the zone
ns1.schmorp.de, ns2.schmorp.de
NameserverAddressesNetwork (AS)Glue
ns1.schmorp.de5.9.56.12AS24940 HETZNER-AS - Hetzner Online GmbH, DE5.9.56.12
ns2.schmorp.de135.181.62.96AS24940 HETZNER-AS - Hetzner Online GmbH, DE135.181.62.96

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.schmorp.de, ns2.schmorp.de.
    #6
  • ✓ 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: ns1.schmorp.de, ns2.schmorp.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 2 IPv4 /24s and 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 2 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.schmorp.de 5.9.56.12NOERROR, 3 ms, authoritativenoyes / yesALLOWED (136 records)Kruma Windows DNS Server 7.5/2006
ns2.schmorp.de 135.181.62.96NOERROR, 23 ms, authoritativenoyes / yesALLOWED (136 records)Kruma Windows DNS Server 7.5/2006

Checks

  • ✓ All respond #14
    All 2 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.schmorp.de: "Kruma Windows DNS Server 7.5/2006"; ns2.schmorp.de: "Kruma Windows DNS Server 7.5/2006". Hide or replace the version string.
    #17
  • ✗
    Zone transfer allowed
    These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns1.schmorp.de (5.9.56.12): 136 records; ns2.schmorp.de (135.181.62.96): 136 records. Restrict zone transfers to your secondary servers.
    #18
  • ✓ 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

warn

serial 2000001238 · primary ns.schmorp.de

Found

Primary (MNAME)
ns.schmorp.de
Contact (RNAME)
hostmaster.schmorp.de
Serial
2000001238
Refresh / retry
86400 s / 21600 s
Expire
2592000 s
Negative TTL
60 s

Serial per nameserver

NameserverSerial
ns1.schmorp.de (5.9.56.12)2000001238
ns2.schmorp.de (135.181.62.96)2000001238

Checks

  • ✓ Serial 2000001238 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 6h, expire 30d, negative TTL 1m.
    #23
  • i
    Hidden master
    The primary nameserver ns.schmorp.de is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact hostmaster@schmorp.de #25
    The SOA RNAME hostmaster.schmorp.de means hostmaster@schmorp.de.
  • ✓ Timestamp serial #26
    The serial 2000001238 is a Unix timestamp (2033-05-18 03:53 UTC).

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

9 records at the apex

Found

Read from
5.9.56.12:53
TypeValueTTL
SOAns.schmorp.de. hostmaster.schmorp.de. 2000001238 86400 21600 2592000 6086400
NSns2.schmorp.de.604800
NSns1.schmorp.de.604800
A135.181.62.963600
AAAA2a01:4f9:4b:4160::23600
MX20 mail20.schmorp.de.86400
MX10 mail10.schmorp.de.86400
TXT"contact Marc Lehmann <schmorp-domain@schmorp.de> for more info"604800
TXT"v=spf1 redirect=spf.schmorp.de"604800

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, AAAA 1h, MX 1d, NS 7d. The NS TTL at the parent is 1d and in the zone 7d; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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