chaospott.de

Checked 21 October 2026, 22:06 UTC · via 8.8.8.8
!Passed with warnings
21 passed 3 warnings 0 failed 5 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.chaospott.de, ns2.chaospott.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.chaospott.de, ns2.chaospott.de
NS in the zone
ns1.chaospott.de, ns2.chaospott.de
NameserverAddressesNetwork (AS)Glue
ns1.chaospott.de148.251.138.141 2a01:4f8:210:428c::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE148.251.138.141
ns2.chaospott.de89.238.65.121 2a00:1828:2000:801::2AS34240 MANITU - manitu GmbH, DE AS34240 MANITU - manitu GmbH, DE89.238.65.121

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.chaospott.de, ns2.chaospott.de.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: ns1.chaospott.de (glue 148.251.138.141, zone 148.251.138.141, 2a01:4f8:210:428c::1); ns2.chaospott.de (glue 89.238.65.121, zone 89.238.65.121, 2a00:1828:2000:801::2). Update the glue at your registrar.
    #8
  • ✓ 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 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 2 addresses; AS34240 (MANITU - manitu 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.chaospott.de 148.251.138.141NOERROR, 3 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.2
ns1.chaospott.de 2a01:4f8:210:428c::1NOERROR, 3 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.2
ns2.chaospott.de 89.238.65.121NOERROR, 10 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.2.0-alpha0.1317.master.g4630dd155 (built Oct 21 2026 04:30:57 by root@localhost)
ns2.chaospott.de 2a00:1828:2000:801::2NOERROR, 11 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.2.0-alpha0.1317.master.g4630dd155 (built Oct 21 2026 04:30:57 by root@localhost)

Checks

  • ✓ All respond #14
    All 4 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: ns1.chaospott.de: "PowerDNS Authoritative Server 5.0.2"; ns2.chaospott.de: "PowerDNS Authoritative Server 5.2.0-alpha0.1317.master.g4630dd155 (built Oct 21 2026 04:30:57 by root@localhost)". 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 2019061725 · primary ns1.chaospott.de

Found

Primary (MNAME)
ns1.chaospott.de
Contact (RNAME)
noc.chaospott.de
Serial
2019061725
Refresh / retry
21600 s / 3600 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.chaospott.de (148.251.138.141)2019061725
ns1.chaospott.de (2a01:4f8:210:428c::1)2019061725
ns2.chaospott.de (89.238.65.121)2019061725
ns2.chaospott.de (2a00:1828:2000:801::2)2019061725

Checks

  • ✓ Serial 2019061725 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 6h, retry 1h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.chaospott.de is one of the listed nameservers.
  • ✓ Contact noc@chaospott.de #25
    The SOA RNAME noc.chaospott.de means noc@chaospott.de.
  • ✓ Date-based serial #26
    The serial 2019061725 follows the YYYYMMDDnn convention (2019-06-17).

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

9 records at the apex

Found

Read from
148.251.138.141:53
TypeValueTTL
SOAns1.chaospott.de. noc.chaospott.de. 2019061725 21600 3600 604800 864003600
NSns1.chaospott.de.300
NSns2.chaospott.de.300
A148.251.138.141300
AAAA2a01:4f8:210:428c::d300
MX10 mail.chaospott.de.300
TXT"v=spf1 mx a ip4:148.251.138.141/32 -all"300
CAA0 issue "letsencrypt.org"300
CAA0 iodef "mailto:noc@chaospott.de"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, AAAA 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.
  • 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org.