herder-institut.de

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

info

dns104.ovh.net, ns104.ovh.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
dns104.ovh.net, ns104.ovh.net
NS in the zone
dns104.ovh.net, ns104.ovh.net
NameserverAddressesNetwork (AS)Glue
dns104.ovh.net5.196.39.113 2001:41d0:d00:fe00::2AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-
ns104.ovh.net5.135.60.17 2001:41d0:b00:f800::2AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns104.ovh.net, ns104.ovh.net.
    #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 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS16276 (OVH - OVH SAS, FR): 4 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 .net
    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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns104.ovh.net 5.196.39.113NOERROR, 18 ms, authoritativenoyes / yesrefused-
dns104.ovh.net 2001:41d0:d00:fe00::2NOERROR, 17 ms, authoritativenoyes / yesrefused-
ns104.ovh.net 5.135.60.17NOERROR, 17 ms, authoritativenoyes / yesrefused-
ns104.ovh.net 2001:41d0:b00:f800::2NOERROR, 16 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 4 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

warn

serial 2091191169 · primary dns104.ovh.net

Found

Primary (MNAME)
dns104.ovh.net
Contact (RNAME)
tech.ovh.net
Serial
2091191169
Refresh / retry
86400 s / 3600 s
Expire
3600000 s
Negative TTL
60 s

Serial per nameserver

NameserverSerial
dns104.ovh.net (5.196.39.113)2091191169
dns104.ovh.net (2001:41d0:d00:fe00::2)2091191169
ns104.ovh.net (5.135.60.17)2091191169
ns104.ovh.net (2001:41d0:b00:f800::2)2091191169

Checks

  • ✓ Serial 2091191169 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 1h, expire 1000h, negative TTL 1m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns104.ovh.net is one of the listed nameservers.
  • ✓ Contact tech@ovh.net #25
    The SOA RNAME tech.ovh.net means tech@ovh.net.
  • ✓ Timestamp serial #26
    The serial 2091191169 is a Unix timestamp (2036-04-07 14:26 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

10 records at the apex

Found

Read from
5.196.39.113:53
TypeValueTTL
SOAdns104.ovh.net. tech.ovh.net. 2091191169 86400 3600 3600000 603600
NSdns104.ovh.net.3600
NSns104.ovh.net.3600
A116.203.15.2473600
MX10 c2111.mx.srv.dfn.de.3600
MX10 b2111.mx.srv.dfn.de.3600
MX10 a2111.mx.srv.dfn.de.3600
TXT"brevo-code:bd7b80dd0068ee7a315aae25b3b89561"3600
TXT"v=spf1 include:_spf.uni-marburg.de ~all"3600
TXT"cisco-ci-domain-verification=541552cad3f2a78e6dd3d090180a393b0f3eb2bece695878b67e7d4e070c3ec7"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