hohner.de

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

warn

ns.i-st.net, ns2.i-st.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.i-st.net, ns2.i-st.net
NS in the zone
ns.i-st.net, ns2.i-st.net
NameserverAddressesNetwork (AS)Glue
ns.i-st.net80.148.51.2AS3320 DTAG - Deutsche Telekom AG, DE-
ns2.i-st.net80.148.52.66AS3320 DTAG - Deutsche Telekom AG, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.i-st.net, ns2.i-st.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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS3320 (DTAG - Deutsche Telekom AG, 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 .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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.i-st.net 80.148.51.2NOERROR, 9 ms, authoritativenoyes / yesrefused9.18.30-0ubuntu0.20.04.2-Ubuntu
ns2.i-st.net 80.148.52.66NOERROR, 8 ms, authoritativenoyes / yesrefused9.18.30-0ubuntu0.20.04.2-Ubuntu

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns.i-st.net: "9.18.30-0ubuntu0.20.04.2-Ubuntu"; ns2.i-st.net: "9.18.30-0ubuntu0.20.04.2-Ubuntu". Hide or replace the version string.
    #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

pass

serial 1791891566 · primary ns.i-st.net

Found

Primary (MNAME)
ns.i-st.net
Contact (RNAME)
eschnell.hohner.de
Serial
1791891566
Refresh / retry
1200 s / 120 s
Expire
1209600 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns.i-st.net (80.148.51.2)1791891566
ns2.i-st.net (80.148.52.66)1791891566

Checks

  • ✓ Serial 1791891566 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 20m, retry 2m, expire 14d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.i-st.net is one of the listed nameservers.
  • ✓ Contact eschnell@hohner.de #25
    The SOA RNAME eschnell.hohner.de means eschnell@hohner.de.
  • ✓ Timestamp serial #26
    The serial 1791891566 is a Unix timestamp (2026-10-13 11:39 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

8 records at the apex

Found

Read from
80.148.51.2:53
TypeValueTTL
SOAns.i-st.net. eschnell.hohner.de. 1791891566 1200 120 1209600 300300
NSns.i-st.net.300
NSns2.i-st.net.300
A157.97.46.154300
MX10 hohner-de.mail.protection.outlook.com.300
TXT"v=spf1 ip4:92.79.92.210 ip4:157.97.46.154 ip4:78.47.8.13 ip4:85.13.152.225 include:spf.protection.outlook.com include:agenturserver.de include:servers.mcsv.net include:spf.mandrillapp.com include:spf.cloud.ci-solution.com -all"300
TXT"google-site-verification=uNohOpg36DsaasY5EU5a8xvTlhh6vjY1jqq-Bqt9aF8"300
TXT"apple-domain-verification=TiyJq1ZQUtLtB7lo"300

Checks

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