fefe.de

Checked 21 October 2026, 22:20 UTC · via 8.8.8.8
✗Problems found
19 passed 4 warnings 1 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

a.ns.fefe.de, b.ns.fefe.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
a.ns.fefe.de, b.ns.fefe.de
NS in the zone
a.ns.fefe.de, b.ns.fefe.de
NameserverAddressesNetwork (AS)Glue
a.ns.fefe.de176.9.92.195AS24940 HETZNER-AS - Hetzner Online GmbH, DE176.9.92.195
b.ns.fefe.de31.15.64.162AS31333 VOLLMAR-AS - Hosting.de GmbH, DE31.15.64.162

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: a.ns.fefe.de, b.ns.fefe.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: a.ns.fefe.de, b.ns.fefe.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; AS31333 (VOLLMAR-AS - Hosting.de 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

fail

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
a.ns.fefe.de 176.9.92.195NOERROR, 3 ms, authoritativenono / norefused-
b.ns.fefe.de 31.15.64.162NOERROR, 8 ms, authoritativenono / norefused-

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.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: a.ns.fefe.de (176.9.92.195): dial tcp 176.9.92.195:53: connect: connection refused; b.ns.fefe.de (31.15.64.162): dial tcp 31.15.64.162:53: connect: connection refused.
    #19
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: a.ns.fefe.de (176.9.92.195), b.ns.fefe.de (31.15.64.162).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 1788614188 · primary a.ns.fefe.de

Found

Primary (MNAME)
a.ns.fefe.de
Contact (RNAME)
hostmaster.fefe.de
Serial
1788614188
Refresh / retry
16384 s / 2048 s
Expire
1048576 s
Negative TTL
2560 s

Serial per nameserver

NameserverSerial
a.ns.fefe.de (176.9.92.195)1788614188
b.ns.fefe.de (31.15.64.162)1792034876

Checks

  • !
    Serials differ
    The nameservers serve different versions of the zone: 1788614188 on a.ns.fefe.de (176.9.92.195); 1792034876 on b.ns.fefe.de (31.15.64.162). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • ✓ Timers within recommendations #23
    SOA refresh 4h33m4s, retry 34m8s, expire 291h16m16s, negative TTL 42m40s.
  • ✓ Primary is a public nameserver #24
    The primary nameserver a.ns.fefe.de is one of the listed nameservers.
  • ✓ Contact hostmaster@fefe.de #25
    The SOA RNAME hostmaster.fefe.de means hostmaster@fefe.de.
  • ✓ Timestamp serial #26
    The serial 1788614188 is a Unix timestamp (2026-09-05 13:16 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

5 records at the apex

Found

Read from
176.9.92.195:53
TypeValueTTL
SOAa.ns.fefe.de. hostmaster.fefe.de. 1788614188 16384 2048 1048576 25602560
NSa.ns.fefe.de.259200
NSb.ns.fefe.de.259200
MX12801 a.mx.fefe.de.86400
TXT"v=spf1 ip4:31.15.64.162 -all"86400

Checks

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