kkh.de

Checked 21 October 2026, 23:10 UTC · via 8.8.8.8
!Passed with warnings
22 passed 3 warnings 0 failed 4 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.im-netz.de, ns1.im-netz.de, ns2.im-netz.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.im-netz.de, ns1.im-netz.de, ns2.im-netz.de
NS in the zone
ns.im-netz.de, ns1.im-netz.de, ns2.im-netz.de
NameserverAddressesNetwork (AS)Glue
ns.im-netz.de212.42.243.130AS44716 DHOSTING-NET - D-hosting die Rackspace & Connectivity GmbH, DE212.42.243.130
ns1.im-netz.de212.42.242.30AS44716 DHOSTING-NET - D-hosting die Rackspace & Connectivity GmbH, DE212.42.242.30
ns2.im-netz.de193.34.121.54AS12732 GUTCON-NET - GutCon GmbH, DE193.34.121.54

Checks

  • ✓ 3 nameservers #6
    Delegated to ns.im-netz.de, ns1.im-netz.de, ns2.im-netz.de.
  • ✓ 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 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS12732 (GUTCON-NET - GutCon GmbH, DE): 1 address; AS44716 (DHOSTING-NET - D-hosting die Rackspace & Connectivity GmbH, DE): 2 addresses.
  • 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

warn

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.im-netz.de 212.42.243.130NOERROR, 9 ms, authoritativenoyes / yesrefusedMS XP NameService 2.73
ns1.im-netz.de 212.42.242.30NOERROR, 9 ms, authoritativenoyes / yesrefused9.20.29-1~deb13u1-Debian
ns2.im-netz.de 193.34.121.54NOERROR, 10 ms, authoritativenoyes / yesrefusedMS XP NameService 2.73

Checks

  • ✓ All respond #14
    All 3 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.im-netz.de: "MS XP NameService 2.73"; ns1.im-netz.de: "9.20.29-1~deb13u1-Debian"; ns2.im-netz.de: "MS XP NameService 2.73". 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 2026100101 · primary ns.im-netz.de

Found

Primary (MNAME)
ns.im-netz.de
Contact (RNAME)
noc.im-netz.de
Serial
2026100101
Refresh / retry
10800 s / 3600 s
Expire
2592000 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns.im-netz.de (212.42.243.130)2026100101
ns1.im-netz.de (212.42.242.30)2026100101
ns2.im-netz.de (193.34.121.54)2026100101

Checks

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

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

15 records at the apex

Found

Read from
212.42.243.130:53
TypeValueTTL
SOAns.im-netz.de. noc.im-netz.de. 2026100101 10800 3600 2592000 8640086400
NSns1.im-netz.de.86400
NSns.im-netz.de.86400
NSns2.im-netz.de.86400
A87.225.251.142600
MX10 mailrelay2.kkh.de.86400
MX10 mailrelay1.kkh.de.86400
TXT"I7pQxMKgBC7Tgoh8PiQ4glApEfUzBZ6OrdHK4O0XAANkWVGfJ8nA/YMxPyxSdScgyPP3XeKIka8cF2XYF9r4wg=="3600
TXT"mindmanager-verification=61984503fedd685aa387532b798b37962a513fcf76a0d04eaf4e67322501a4a3"3600
TXT"_5mg1lpstigrumh4h6halc2daanl4a9m"3600
TXT"google-site-verification=lxvR53IZS3xQvLmsvxfaI06Jyo2DkK9csw9MBeiqgZw"3600
TXT"verifyvs=20250825090419b8d06bffe5069c1e7168e54270000372"3600
TXT"v=spf1 mx ip4:91.213.61.85 ip4:91.213.61.86 ip4:87.225.251.128/29 ip4:193.201.168.0/24 ip4:212.42.225.32/32 ip4:217.31.84.130/32 ip4:62.48.73.160/27 " "ip4:62.48.87.48/28 include:d-hosting.de include:spf.crsend.com include:spf.protection.outlook.com include:spf.mail.nacura.de include:spf.mailingress.de -all"3600
TXT"Dynatrace-site-verification=0b95cc5a-c2d2-45d1-9fda-8bcbc382934c__u7afnillv6sa49oe24s15b6ih5"3600
TXT"apple-domain-verification=W7wfUx5EMWvjP4yL"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, MX 1d, NS 1d.
  • ✓ 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