ohse.de

Checked 21 October 2026, 23:41 UTC · via 8.8.8.8
✗Problems found
18 passed 3 warnings 2 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

a.ns.ohse.de, b.ns.ohse.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
a.ns.ohse.de, b.ns.ohse.de
NS in the zone
a.ns.ohse.de, b.ns.ohse.de
NameserverAddressesNetwork (AS)Glue
a.ns.ohse.de135.181.36.34AS24940 HETZNER-AS - Hetzner Online GmbH, DE135.181.36.34
b.ns.ohse.de213.239.204.137AS24940 HETZNER-AS - Hetzner Online GmbH, DE213.239.204.137

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: a.ns.ohse.de, b.ns.ohse.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: a.ns.ohse.de, b.ns.ohse.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.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 2 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 .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

fail

1 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
a.ns.ohse.de 135.181.36.34NOERROR, 24 ms, authoritativenono / norefused-
b.ns.ohse.de 213.239.204.137no responsenono / no--

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: b.ns.ohse.de (213.239.204.137): read udp 46.225.38.91:41425->213.239.204.137:53: i/o timeout.
    #14
  • ✓ 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.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: a.ns.ohse.de (135.181.36.34): dial tcp 135.181.36.34:53: connect: connection refused.
    #19
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: a.ns.ohse.de (135.181.36.34).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2020011801 · primary a.ns.ohse.de

Found

Primary (MNAME)
a.ns.ohse.de
Contact (RNAME)
uwe.ohse.de
Serial
2020011801
Refresh / retry
86400 s / 7200 s
Expire
604800 s
Negative TTL
86400 s

Checks

  • ✓ Serial 2020011801 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 2h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver a.ns.ohse.de is one of the listed nameservers.
  • ✓ Contact uwe@ohse.de #25
    The SOA RNAME uwe.ohse.de means uwe@ohse.de.
  • ✓ Date-based serial #26
    The serial 2020011801 follows the YYYYMMDDnn convention (2020-01-18).

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

7 records at the apex

Found

Read from
135.181.36.34:53
TypeValueTTL
SOAa.ns.ohse.de. uwe.ohse.de. 2020011801 86400 7200 604800 8640086400
NSa.ns.ohse.de.259200
NSb.ns.ohse.de.259200
A213.239.204.1373600
AAAA2a01:4f8:222:b58:9:0:109:1600
MX600 xmtp.ohse.de.86400
TXT"v=spf1 a mx a:mail.ohse.de a:xmtp.ohse.de ~all"600

Checks

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