broetje.de

Checked 21 October 2026, 21:54 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

info

dns1.safenames.com, dns2.safenames.net, dns3.safenames.org

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
dns1.safenames.com, dns2.safenames.net, dns3.safenames.org
NS in the zone
dns1.safenames.com, dns2.safenames.net, dns3.safenames.org
NameserverAddressesNetwork (AS)Glue
dns1.safenames.com162.159.48.132 2400:cb00:2049:1::a29f:3084AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
dns2.safenames.net162.159.49.170 2400:cb00:2049:1::a29f:31aaAS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
dns3.safenames.org172.64.48.23 2400:cb00:2049:1::ac40:3017AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-

Checks

  • ✓ 3 nameservers #6
    Delegated to dns1.safenames.com, dns2.safenames.net, dns3.safenames.org.
  • ✓ 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.
  • i
    One address family in one network
    all IPv6 addresses are in 2400:cb00:2049::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 6 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 3 TLDs #12
    Nameserver names use the TLDs .com, .net, .org.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.safenames.com 162.159.48.132NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.8
dns1.safenames.com 2400:cb00:2049:1::a29f:3084NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.8
dns2.safenames.net 162.159.49.170NOERROR, 27 ms, authoritativenoyes / yesrefused2026.10.8
dns2.safenames.net 2400:cb00:2049:1::a29f:31aaNOERROR, 26 ms, authoritativenoyes / yesrefused2026.10.8
dns3.safenames.org 172.64.48.23NOERROR, 28 ms, authoritativenoyes / yesrefused2026.10.8
dns3.safenames.org 2400:cb00:2049:1::ac40:3017NOERROR, 30 ms, authoritativenoyes / yesrefused2026.10.8

Checks

  • ✓ All respond #14
    All 6 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: dns1.safenames.com: "2026.10.8"; dns2.safenames.net: "2026.10.8"; dns3.safenames.org: "2026.10.8". 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 2026100100 · primary dns1.safenames.com

Found

Primary (MNAME)
dns1.safenames.com
Contact (RNAME)
hostmaster.safenames.net
Serial
2026100100
Refresh / retry
28800 s / 1800 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
dns1.safenames.com (162.159.48.132)2026100100
dns1.safenames.com (2400:cb00:2049:1::a29f:3084)2026100100
dns2.safenames.net (162.159.49.170)2026100100
dns2.safenames.net (2400:cb00:2049:1::a29f:31aa)2026100100
dns3.safenames.org (172.64.48.23)2026100100
dns3.safenames.org (2400:cb00:2049:1::ac40:3017)2026100100

Checks

  • ✓ Serial 2026100100 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 30m, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns1.safenames.com is one of the listed nameservers.
  • ✓ Contact hostmaster@safenames.net #25
    The SOA RNAME hostmaster.safenames.net means hostmaster@safenames.net.
  • ✓ Date-based serial #26
    The serial 2026100100 follows the YYYYMMDDnn convention (2026-10-01).

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

17 records at the apex

Found

Read from
162.159.48.132:53
TypeValueTTL
SOAdns1.safenames.com. hostmaster.safenames.net. 2026100100 28800 1800 604800 360035186
NSdns1.safenames.com.49148
NSdns2.safenames.net.49148
NSdns3.safenames.org.49148
A217.19.248.132147
MX10 mxb-001e2d01.gslb.pphosted.com.227
MX10 mxa-001e2d01.gslb.pphosted.com.227
TXT"_4bsjwzufnunuxefs6y7kpkvxa2wzkde"600
TXT"box-domain-verification=f9ba229e62e2d2c9d72472992af9c4eb33717f2f6159824b31a6f35f3d7c338a"600
TXT"v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com include:spf-001e2d01.pphosted.com include:spf.protection.outlook.com include:spf-westeu.emailsignatures365.com include:spf.crsend.com a:o1.ptr7040.bdrthermeagroup.com ip4:149.72.73.101 ip4:149.72.222.3 i" "nclude:spf1.kunden.livingbytes.de ~all"600
TXT"_da4dj6u3m1h1n5effz5acnpejum4fkf"600
TXT"_ln6o95fpzol6zcoqvydmw24y90wxlng"600
TXT"google-site-verification=gs1B1_O89aT2yDzYqhsNkT1-UczhFj2a8n1guhAmCOQ"600
TXT"sc-bdr-prd-cd.azurewebsites.net"600
TXT"1password-site-verification=Z64XRSGUZNCL7CIZDMTBIVFFPA"600
TXT"miro-verification=6ad6809b4730bf377974922cb60052de681f03dc"600
TXT"rovag_verification_token=A7A1D0C89DC742D792C6E16E5536028E"600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (2m27s), MX (3m47s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 13h39m8s; 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