woodworker.de

Checked 22 October 2026, 01:01 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

warn

ns1.de-nserver.de, ns2.de-nserver.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.de-nserver.de, ns2.de-nserver.de
NS in the zone
ns1.de-nserver.de, ns2.de-nserver.de
NameserverAddressesNetwork (AS)Glue
ns1.de-nserver.de109.237.143.9AS45012 CLOUDPIT - dogado GmbH, DE109.237.143.9
ns2.de-nserver.de5.9.190.96AS24940 HETZNER-AS - Hetzner Online GmbH, DE5.9.190.96

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.de-nserver.de, ns2.de-nserver.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 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 1 address; AS45012 (CLOUDPIT - dogado GmbH, DE): 1 address.
  • 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

pass

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.de-nserver.de 109.237.143.9NOERROR, 16 ms, authoritativenoyes / yesrefused-
ns2.de-nserver.de 5.9.190.96NOERROR, 2 ms, authoritativenoyes / yesrefused-

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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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 2024102601 · primary ns1.de-nserver.de

Found

Primary (MNAME)
ns1.de-nserver.de
Contact (RNAME)
hostmaster.ns1.de-nserver.de
Serial
2024102601
Refresh / retry
14400 s / 3600 s
Expire
604800 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns1.de-nserver.de (109.237.143.9)2024102601
ns2.de-nserver.de (5.9.190.96)2024102601

Checks

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

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

6 records at the apex

Found

Read from
109.237.143.9:53
TypeValueTTL
SOAns1.de-nserver.de. hostmaster.ns1.de-nserver.de. 2024102601 14400 3600 604800 600300
NSns2.de-nserver.de.300
NSns1.de-nserver.de.300
A85.158.183.73300
MX10 mail.woodworker.de.300
TXT"v=spf1 a mx ~all"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5m, NS 5m. The NS TTL at the parent is 1d and in the zone 5m; 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