snafu.de

Checked 22 October 2026, 00:22 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

ns01.snafu.de, ns02.snafu.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns01.snafu.de, ns02.snafu.de
NS in the zone
ns01.snafu.de, ns02.snafu.de
NameserverAddressesNetwork (AS)Glue
ns01.snafu.de213.73.103.2AS34171 SNAFU-LIG-AS - snafu Gesellschaft fuer interaktive Netzwerke mbH, DE213.73.103.2
ns02.snafu.de78.46.25.196AS24940 HETZNER-AS - Hetzner Online GmbH, DE78.46.25.196

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns01.snafu.de, ns02.snafu.de.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns01.snafu.de, ns02.snafu.de.
  • ✓ 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; AS34171 (SNAFU-LIG-AS - snafu Gesellschaft fuer interaktive Netzwerke mbH, 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

info

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns01.snafu.de 213.73.103.2NOERROR, 16 ms, authoritativenoyes / yesrefusedsnafu_dns
ns02.snafu.de 78.46.25.196NOERROR, 2 ms, authoritativenoyes / yesrefusedsnafu_dns

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: ns01.snafu.de: "snafu_dns"; ns02.snafu.de: "snafu_dns".
    #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 2026102102 · primary ns01.snafu.de

Found

Primary (MNAME)
ns01.snafu.de
Contact (RNAME)
domain.team.snafu.de
Serial
2026102102
Refresh / retry
86400 s / 7200 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns01.snafu.de (213.73.103.2)2026102102
ns02.snafu.de (78.46.25.196)2026102102

Checks

  • ✓ Serial 2026102102 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 2h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns01.snafu.de is one of the listed nameservers.
  • ✓ Contact domain@team.snafu.de #25
    The SOA RNAME domain.team.snafu.de means domain@team.snafu.de.
  • ✓ Date-based serial #26
    The serial 2026102102 follows the YYYYMMDDnn convention (2026-10-21).

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

11 records at the apex

Found

Read from
213.73.103.2:53
TypeValueTTL
SOAns01.snafu.de. domain.team.snafu.de. 2026102102 86400 7200 604800 8640086400
NSns02.snafu.de.86400
NSns01.snafu.de.86400
A213.73.84.47200
MX50 secondary.snafu.de.7200
MX10 mailin.snafu.de.7200
TXT"v=spf1 mx ip4:84.23.254.128/25 ip6:2001:1560:3:255::/64 ip6:2001:1560:3:254::/64 ip4:213.73.113.34/32 ip6:2001:1560:a000:2:50:ff:fe00:27ed/128 include:_spf.snafu.de -all"7200
TXT"google-site-verification=-7Np3Ryk6KtCruyp2P7MrT0NLHF90QKD1apbLfM-0yo"7200
TXT"google-site-verification=-5pOvMfNG-FyGe_zRZY19YZ8HArOiQnp70ZREO2S9mc"7200
TXT"abuseipdb-verification=A9V1E1iS"7200
TXT"yahoo-verification-key=2R/ekLlEuqaaSO5vVzc7DUUxhZDNE9ucHWxUyQdf1yk="7200

Checks

  • ✓ TTLs within range #32
    TTLs: A 2h, MX 2h, 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