fridaysforfuture.de

Checked 21 October 2026, 22:31 UTC · via 8.8.8.8
!Passed with warnings
19 passed 4 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

info

ferrylane.rzone.de, shamlegger.rzone.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ferrylane.rzone.de, shamlegger.rzone.de
NS in the zone
ferrylane.rzone.de, shamlegger.rzone.de
NameserverAddressesNetwork (AS)Glue
ferrylane.rzone.de81.169.146.6 2a01:238:20a:930:6653::6AS6724 STRATO - Strato GmbH, DE AS6724 STRATO - Strato GmbH, DE-
shamlegger.rzone.de85.214.0.254 2a01:238:20b:43:6653::524AS6724 STRATO - Strato GmbH, DE AS6724 STRATO - Strato GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ferrylane.rzone.de, shamlegger.rzone.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 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS6724 (STRATO - Strato GmbH, DE): 4 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 .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
ferrylane.rzone.de 81.169.146.6NOERROR, 10 ms, authoritativenoyes / norefuseddbmd-mt-lua 2.0
ferrylane.rzone.de 2a01:238:20a:930:6653::6NOERROR, 8 ms, authoritativenoyes / norefuseddbmd-mt-lua 2.0
shamlegger.rzone.de 85.214.0.254NOERROR, 13 ms, authoritativenoyes / norefuseddbmd-mt-lua 2.0
shamlegger.rzone.de 2a01:238:20b:43:6653::524NOERROR, 13 ms, authoritativenoyes / norefuseddbmd-mt-lua 2.0

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: ferrylane.rzone.de: "dbmd-mt-lua 2.0"; shamlegger.rzone.de: "dbmd-mt-lua 2.0". 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.
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ferrylane.rzone.de (81.169.146.6), ferrylane.rzone.de (2a01:238:20a:930:6653::6), shamlegger.rzone.de (85.214.0.254), shamlegger.rzone.de (2a01:238:20b:43:6653::524).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2024101200 · primary ferrylane.rzone.de

Found

Primary (MNAME)
ferrylane.rzone.de
Contact (RNAME)
hostmaster.strato-rz.de
Serial
2024101200
Refresh / retry
86400 s / 7200 s
Expire
604800 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ferrylane.rzone.de (81.169.146.6)2024101200
ferrylane.rzone.de (2a01:238:20a:930:6653::6)2024101200
shamlegger.rzone.de (85.214.0.254)2024101200
shamlegger.rzone.de (2a01:238:20b:43:6653::524)2024101200

Checks

  • ✓ Serial 2024101200 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 2h, expire 7d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ferrylane.rzone.de is one of the listed nameservers.
  • ✓ Contact hostmaster@strato-rz.de #25
    The SOA RNAME hostmaster.strato-rz.de means hostmaster@strato-rz.de.
  • ✓ Date-based serial #26
    The serial 2024101200 follows the YYYYMMDDnn convention (2024-10-12).

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

7 records at the apex

Found

Read from
81.169.146.6:53
TypeValueTTL
SOAferrylane.rzone.de. hostmaster.strato-rz.de. 2024101200 86400 7200 604800 300150
NSshamlegger.rzone.de.150
NSferrylane.rzone.de.150
A185.165.171.132150
AAAA2a06:1700:0:32::1150
MX20 forfuture.email.150
TXT"v=spf1 a mx ip4:185.247.224.95/32 include:spf.smtp.net -all"150

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (2m30s), AAAA (2m30s), MX (2m30s), NS (2m30s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 2m30s; resolvers may use either.
    #32
  • ✓ 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