kilu.de

Checked 21 October 2026, 23:02 UTC · via 8.8.8.8
!Passed with warnings
16 passed 5 warnings 0 failed 8 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

ns1.subdomain.net, ns2.subdomain.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.subdomain.net, ns2.subdomain.net
NS in the zone
ns1.subdomain.net, ns2.subdomain.net
NameserverAddressesNetwork (AS)Glue
ns1.subdomain.net168.119.122.44AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
ns2.subdomain.net168.119.122.43AS24940 HETZNER-AS - Hetzner Online GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.subdomain.net, ns2.subdomain.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 one network
    all IPv4 addresses are in 168.119.122.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • 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 .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

info

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.subdomain.net 168.119.122.44NOERROR, 7 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns2.subdomain.net 168.119.122.43NOERROR, 5 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.subdomain.net: "Served by PowerDNS - https://www.powerdns.com/"; ns2.subdomain.net: "Served by PowerDNS - https://www.powerdns.com/".
    #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

warn

serial 2026091602 · primary ns1.subdomain.net

Found

Primary (MNAME)
ns1.subdomain.net
Contact (RNAME)
hostmaster.kilu.de
Serial
2026091602
Refresh / retry
10800 s / 1800 s
Expire
604800 s
Negative TTL
180 s

Serial per nameserver

NameserverSerial
ns1.subdomain.net (168.119.122.44)2026091602
ns2.subdomain.net (168.119.122.43)2026091602

Checks

  • ✓ Serial 2026091602 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 3h, retry 30m, expire 7d, negative TTL 3m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.subdomain.net is one of the listed nameservers.
  • ✓ Contact hostmaster@kilu.de #25
    The SOA RNAME hostmaster.kilu.de means hostmaster@kilu.de.
  • ✓ Date-based serial #26
    The serial 2026091602 follows the YYYYMMDDnn convention (2026-09-16).

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

warn

5 records at the apex

Found

Read from
168.119.122.44:53
TypeValueTTL
SOAns1.subdomain.net. hostmaster.kilu.de. 2026091602 10800 1800 604800 1803600
NSns1.subdomain.net.1800
NSns2.subdomain.net.1800
A95.217.58.10894
TXT"v=spf1 a mx -all"3600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m34s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 30m; resolvers may use either.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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