berliner-feuerwehr.de

Checked 21 October 2026, 21:38 UTC · via 8.8.8.8
!Passed with warnings
20 passed 2 warnings 0 failed 7 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

ns3.stratoserver.net, ns4.stratoserver.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns3.stratoserver.net, ns4.stratoserver.net
NS in the zone
ns3.stratoserver.net, ns4.stratoserver.net
NameserverAddressesNetwork (AS)Glue
ns3.stratoserver.net185.132.34.159 2607:f1c0:fe:53:185:132:34:159AS15418 IONOS-ANYCAST - Fasthosts Internet Limited, GB AS15418 IONOS-ANYCAST - Fasthosts Internet Limited, GB-
ns4.stratoserver.net217.160.80.159 2001:8d8:fe:53:5747:2a74:d:32AS8560 IONOS-AS - IONOS SE, DE AS8560 IONOS-AS - IONOS SE, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns3.stratoserver.net, ns4.stratoserver.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 different networks #10
    The nameservers are spread over 2 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS15418 (IONOS-ANYCAST - Fasthosts Internet Limited, GB): 2 addresses; AS8560 (IONOS-AS - IONOS SE, DE): 2 addresses.
  • 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns3.stratoserver.net 185.132.34.159NOERROR, 3 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns3.stratoserver.net 2607:f1c0:fe:53:185:132:34:159NOERROR, 4 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns4.stratoserver.net 217.160.80.159NOERROR, 9 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns4.stratoserver.net 2001:8d8:fe:53:5747:2a74:d:32NOERROR, 9 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/

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

pass

serial 2020052087 · primary ns4.stratoserver.net

Found

Primary (MNAME)
ns4.stratoserver.net
Contact (RNAME)
hostmaster.strato-rz.de
Serial
2020052087
Refresh / retry
86400 s / 7200 s
Expire
604800 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns3.stratoserver.net (185.132.34.159)2020052087
ns3.stratoserver.net (2607:f1c0:fe:53:185:132:34:159)2020052087
ns4.stratoserver.net (217.160.80.159)2020052087
ns4.stratoserver.net (2001:8d8:fe:53:5747:2a74:d:32)2020052087

Checks

  • ✓ Serial 2020052087 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 ns4.stratoserver.net 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 2020052087 follows the YYYYMMDDnn convention (2020-05-20).

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

11 records at the apex

Found

Read from
185.132.34.159:53
TypeValueTTL
SOAns4.stratoserver.net. hostmaster.strato-rz.de. 2020052087 86400 7200 604800 300150
NSns3.stratoserver.net.150
NSns4.stratoserver.net.150
A85.214.39.183150
MX10 mgw01.berliner-feuerwehr.de.150
MX20 berlinerfeuerwehr-de02b.mail.protection.outlook.com.150
TXT"v=spf1 a mx a:mgw01.berliner-feuerwehr.de include:spf.protection.outlook.com include:_spf.strato.com include:_spf.rexx-suite.com -all"150
TXT"MS=ms36036296"150
TXT"google-site-verification=B-LiM0t_E6dbLEVkMdv_FIFtRKAa_9LF4YSJeEtMc-Q"150
TXT"apple-domain-verification=hEynhuPVwjzbwobJ"150
TXT"apple-domain-verification=6wzyA5VSlD72sTKt"150

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (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.
  • 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