ntz.de

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

ns2.ntz.de, ns4.ntz.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns2.ntz.de, ns4.ntz.de
NS in the zone
ns2.ntz.de, ns4.ntz.de
NameserverAddressesNetwork (AS)Glue
ns2.ntz.de217.237.178.12AS3320 DTAG - Deutsche Telekom AG, DE217.237.178.12
ns4.ntz.de78.46.218.24AS24940 HETZNER-AS - Hetzner Online GmbH, DE78.46.218.24

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns2.ntz.de, ns4.ntz.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: ns2.ntz.de, ns4.ntz.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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 1 address; AS3320 (DTAG - Deutsche Telekom AG, 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
ns2.ntz.de 217.237.178.12NOERROR, 7 ms, authoritativenoyes / yesrefused-
ns4.ntz.de 78.46.218.24NOERROR, 4 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 2026102102 · primary ns2.ntz.de

Found

Primary (MNAME)
ns2.ntz.de
Contact (RNAME)
root.ns2.ntz.de
Serial
2026102102
Refresh / retry
28800 s / 7200 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns2.ntz.de (217.237.178.12)2026102102
ns4.ntz.de (78.46.218.24)2026102102

Checks

  • ✓ Serial 2026102102 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns2.ntz.de is one of the listed nameservers.
  • ✓ Contact root@ns2.ntz.de #25
    The SOA RNAME root.ns2.ntz.de means root@ns2.ntz.de.
  • ✓ Date-based serial #26
    The serial 2026102102 follows the YYYYMMDDnn convention (2026-10-21).

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

10 records at the apex

Found

Read from
217.237.178.12:53
TypeValueTTL
SOAns2.ntz.de. root.ns2.ntz.de. 2026102102 28800 7200 604800 8640060
NSns2.ntz.de.60
NSns4.ntz.de.60
A217.237.178.2660
MX10 fml.ntz.de.60
MX20 dsl.ntz.de.60
TXT"MS=2DE8E9D1BD30CAD87202C0D4493FDD2F9B222468"60
TXT"google-site-verification=bGXiEsSGMpE4LeyM7Pl7uR7Gus6JhQZvdr6YcM0dnGg"60
TXT"v=spf1 mx ip4:217.237.178.0/24 ip4:217.237.179.0/24 ip4:217.7.208.110/32 include:amazonses.com include:spf.ntz-de.cloud.nospamproxy.com ~all"60
TXT"J6Qu3SBKLQpG4HLprYmg9OCf6jGmcfwmbF3P6nqCjBw="60

Checks

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