herpa.de

Checked 21 October 2026, 22:50 UTC · via 8.8.8.8
!Passed with warnings
22 passed 2 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

ns.herpa.de, ns2.herpa.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.herpa.de, ns2.herpa.de
NS in the zone
ns.herpa.de, ns2.herpa.de
NameserverAddressesNetwork (AS)Glue
ns.herpa.de116.203.54.135AS24940 HETZNER-AS - Hetzner Online GmbH, DE116.203.54.135
ns2.herpa.de2.207.151.74AS3209 VODANET - Vodafone GmbH, DE2.207.151.74

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.herpa.de, ns2.herpa.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: ns.herpa.de, ns2.herpa.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; AS3209 (VODANET - Vodafone 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
ns.herpa.de 116.203.54.135NOERROR, 2 ms, authoritativenoyes / yesrefused-
ns2.herpa.de 2.207.151.74NOERROR, 29 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 2026091410 · primary ns.herpa.de

Found

Primary (MNAME)
ns.herpa.de
Contact (RNAME)
goebelt.herpa.de
Serial
2026091410
Refresh / retry
86400 s / 10800 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns.herpa.de (116.203.54.135)2026091410
ns2.herpa.de (2.207.151.74)2026091410

Checks

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

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

12 records at the apex

Found

Read from
116.203.54.135:53
TypeValueTTL
SOAns.herpa.de. goebelt.herpa.de. 2026091410 86400 10800 1209600 36003600
NSns2.herpa.de.3600
NSns.herpa.de.3600
A159.69.95.2403600
MX10 mail.herpa.de.3600
MX20 ext1.herpa.de.3600
TXT"v=spf1 mx -all"3600
TXT"sw-domain-hash=2c49b0cc13fbe4ea158bd83d7b7c96f4"3600
TXT"brevo-code:441a0cfdfbb1b4f9d2c5882489c55d79"3600
TXT"sw-domain-hash=249f53583e28e9d97bd407dc4df267bc"3600
TXT"MS=193B40E05B451063BD07995F1BDFF00E58DE4ACF"3600
TXT"sw-domain-hash=93f198ee25dbea7dc196265bfb19fad2"3600

Checks

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