rnz.de

Checked 22 October 2026, 00:00 UTC · via 8.8.8.8
!Passed with warnings
20 passed 1 warning 0 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

info

ns1.hd-it.eu, ns2.hd-it.eu, ns3.hd-it.eu

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.hd-it.eu, ns2.hd-it.eu, ns3.hd-it.eu
NS in the zone
ns1.hd-it.eu, ns2.hd-it.eu, ns3.hd-it.eu
NameserverAddressesNetwork (AS)Glue
ns1.hd-it.eu81.89.192.67 2a04:c940:0:5::67AS25081 HDiT-AS - Heidelberg IT Management GmbH & Co.KG, DE AS25081 HDiT-AS - Heidelberg IT Management GmbH & Co.KG, DE-
ns2.hd-it.eu217.69.239.12 2a02:238::217:69:239:cAS16097 HLKOMM - HL komm Telekommunikations GmbH, DE AS16097 HLKOMM - HL komm Telekommunikations GmbH, DE-
ns3.hd-it.eu5.45.111.167AS197540 netcup-AS - netcup GmbH, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.hd-it.eu, ns2.hd-it.eu, ns3.hd-it.eu.
  • ✓ 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 3 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS16097 (HLKOMM - HL komm Telekommunikations GmbH, DE): 2 addresses; AS197540 (netcup-AS - netcup GmbH, DE): 1 address; AS25081 (HDiT-AS - Heidelberg IT Management GmbH & Co.KG, DE): 2 addresses.
  • i
    All nameserver names under .eu
    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: ns3.hd-it.eu.
    #13

Nameservers

info

5 of 5 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.hd-it.eu 81.89.192.67NOERROR, 6 ms, authoritativenoyes / yesrefusedDNS
ns1.hd-it.eu 2a04:c940:0:5::67NOERROR, 9 ms, authoritativenoyes / yesrefusedDNS
ns2.hd-it.eu 217.69.239.12NOERROR, 12 ms, authoritativenoyes / yesrefusedDNS
ns2.hd-it.eu 2a02:238::217:69:239:cNOERROR, 12 ms, authoritativenoyes / yesrefusedDNS
ns3.hd-it.eu 5.45.111.167NOERROR, 1 ms, authoritativenoyes / yesrefusedDNS

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: ns1.hd-it.eu: "DNS"; ns2.hd-it.eu: "DNS"; ns3.hd-it.eu: "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

info

serial 2026100900 · primary web8.hd-it.eu

Found

Primary (MNAME)
web8.hd-it.eu
Contact (RNAME)
root.hd-it.eu
Serial
2026100900
Refresh / retry
7200 s / 3600 s
Expire
604800 s
Negative TTL
3840 s

Serial per nameserver

NameserverSerial
ns1.hd-it.eu (81.89.192.67)2026100900
ns1.hd-it.eu (2a04:c940:0:5::67)2026100900
ns2.hd-it.eu (217.69.239.12)2026100900
ns2.hd-it.eu (2a02:238::217:69:239:c)2026100900
ns3.hd-it.eu (5.45.111.167)2026100900

Checks

  • ✓ Serial 2026100900 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h, retry 1h, expire 7d, negative TTL 64m.
  • i
    Hidden master
    The primary nameserver web8.hd-it.eu 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 root@hd-it.eu #25
    The SOA RNAME root.hd-it.eu means root@hd-it.eu.
  • ✓ Date-based serial #26
    The serial 2026100900 follows the YYYYMMDDnn convention (2026-10-09).

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

11 records at the apex

Found

Read from
81.89.192.67:53
TypeValueTTL
SOAweb8.hd-it.eu. root.hd-it.eu. 2026100900 7200 3600 604800 38407200
NSns2.hd-it.eu.7200
NSns1.hd-it.eu.7200
NSns3.hd-it.eu.7200
A213.182.13.53300
MX10 mx2.rnz.de.7200
TXT"google-site-verification=9Uq7xqNsQ8sa5HEUxnfyKDpNADfM4p07K1S1o1-sGT0"300
TXT"MS=75DD24B0A4D9950F0B8B9082FA4E3D0E3DF92158"300
TXT"v=spf1 mx ip4:213.182.18.214 ip4:213.182.18.215 ip4:213.182.18.216 ip4:194.195.3.64/27 include:spf.protection.outlook.com include:amazonses.com include:sendgrid.net include:_spf.perfora.net include:_spf.kundenserver.de include:agenturserver.de include:ses" ".echobox.com -all"300
TXT"apple-domain-verification=d3Ibvwc0Jc6Jkoye"300
TXT"552-TXT-108"300

Checks

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