kanu.de

Checked 21 October 2026, 23:02 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

warn

ns7.sealnet.de, ns8.sealnet.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns7.sealnet.de, ns8.sealnet.de
NS in the zone
ns7.sealnet.de, ns8.sealnet.de
NameserverAddressesNetwork (AS)Glue
ns7.sealnet.de159.69.138.41AS24940 HETZNER-AS - Hetzner Online GmbH, DE159.69.138.41
ns8.sealnet.de80.74.54.149AS60294 DE-DGW - Deutsche Glasfaser Wholesale GmbH, DE80.74.54.149

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns7.sealnet.de, ns8.sealnet.de.
    #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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 1 address; AS60294 (DE-DGW - Deutsche Glasfaser Wholesale 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
ns7.sealnet.de 159.69.138.41NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns8.sealnet.de 80.74.54.149NOERROR, 9 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

info

serial 1654166900 · primary ns.sealnet.de

Found

Primary (MNAME)
ns.sealnet.de
Contact (RNAME)
webservices.sealnet.de
Serial
1654166900
Refresh / retry
86400 s / 3600 s
Expire
2419200 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns7.sealnet.de (159.69.138.41)1654166900
ns8.sealnet.de (80.74.54.149)1654166900

Checks

  • ✓ Serial 1654166900 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 1h, expire 28d, negative TTL 1d.
  • i
    Hidden master
    The primary nameserver ns.sealnet.de is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact webservices@sealnet.de #25
    The SOA RNAME webservices.sealnet.de means webservices@sealnet.de.
  • ✓ Timestamp serial #26
    The serial 1654166900 is a Unix timestamp (2022-06-02 10:48 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

7 records at the apex

Found

Read from
159.69.138.41:53
TypeValueTTL
SOAns.sealnet.de. webservices.sealnet.de. 1654166900 86400 3600 2419200 8640086400
NSns8.sealnet.de.40000
NSns7.sealnet.de.20000
A178.104.227.1443600
MX1 kanu-de.mail.protection.outlook.com.300
TXT"v=spf1 include:spf.protection.outlook.com ip4:167.235.178.108 a:server.selltec.com redirect=_spf.sealnet.de"300
TXT"MS=ms20101844"300

Checks

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