schwarzwaelder-bote.de

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

ns1.sbm-int.de, ns2.sbm-int.de, ns3.sbm-int.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.sbm-int.de, ns2.sbm-int.de, ns3.sbm-int.de
NS in the zone
ns1.sbm-int.de, ns2.sbm-int.de, ns3.sbm-int.de
NameserverAddressesNetwork (AS)Glue
ns1.sbm-int.de195.5.99.100AS200374 schwabo - Schwarzwaelder Bote Mediengesellschaft mbH, DE195.5.99.100
ns2.sbm-int.de194.53.64.100AS200374 schwabo - Schwarzwaelder Bote Mediengesellschaft mbH, DE194.53.64.100
ns3.sbm-int.de81.169.181.94AS6724 STRATO - Strato GmbH, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.sbm-int.de, ns2.sbm-int.de, ns3.sbm-int.de.
  • ✓ 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 3 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS200374 (schwabo - Schwarzwaelder Bote Mediengesellschaft mbH, DE): 2 addresses; AS6724 (STRATO - Strato 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

warn

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.sbm-int.de 195.5.99.100NOERROR, 9 ms, authoritativenoyes / yesrefused9.18.49-1~deb12u2-Debian
ns2.sbm-int.de 194.53.64.100NOERROR, 9 ms, authoritativenoyes / yesrefused9.20.29-1~deb13u1-Debian
ns3.sbm-int.de 81.169.181.94NOERROR, 12 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3

Checks

  • ✓ All respond #14
    All 3 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: ns1.sbm-int.de: "9.18.49-1~deb12u2-Debian"; ns2.sbm-int.de: "9.20.29-1~deb13u1-Debian"; ns3.sbm-int.de: "PowerDNS Authoritative Server 4.7.3". 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

fail

serial 2026201305 · primary ns1.sbm-int.de

Found

Primary (MNAME)
ns1.sbm-int.de
Contact (RNAME)
hostmaster\@sbm-int.de
Serial
2026201305
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.sbm-int.de (195.5.99.100)2026201305
ns2.sbm-int.de (194.53.64.100)2026102101
ns3.sbm-int.de (81.169.181.94)2026101300

Checks

  • !
    Serials differ
    The nameservers serve different versions of the zone: 2026101300 on ns3.sbm-int.de (81.169.181.94); 2026102101 on ns2.sbm-int.de (194.53.64.100); 2026201305 on ns1.sbm-int.de (195.5.99.100). 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 3h, retry 1h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.sbm-int.de is one of the listed nameservers.
  • ✗
    Invalid contact address
    The SOA RNAME "hostmaster\\@sbm-int.de" contains an @; it must be written with a dot instead (hostmaster.example.com).
    #25
  • ✓ Timestamp serial #26
    The serial 2026201305 is a Unix timestamp (2034-03-17 09:41 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

warn

17 records at the apex

Found

Read from
195.5.99.100:53
TypeValueTTL
SOAns1.sbm-int.de. hostmaster\@sbm-int.de. 2026201305 10800 3600 604800 864003600
NSns1.sbm-int.de.3600
NSns3.sbm-int.de.3600
NSns2.sbm-int.de.3600
A208.82.75.15460
MX10 schwarzwaelderbote-de03e.mail.protection.outlook.com.300
TXT"d365mktkey=SKIPJ3sxuR8H459Bo6SxTAzdq8FpRMWx1YtSoZNOwjkx"3600
TXT"MS=ms49704289"3600
TXT"zj9xfk94jmtspftmyck3fzmn1krvm5zg"3600
TXT"facebook-domain-verification=208hy8d5michm7mmtyumhdf5torr9p"3600
TXT"v=spf1 a mx ip4:195.5.98.0/23 ip4:208.82.73.190 ip4:213.198.99.0/24 ip4:54.240.3.0/24 ip4:81.169.149.0/24 include:spf.protection.outlook.com include:spf.swmh.de include:spf.msh.de include:de._netblocks.mimecast.com\009include:amazonses.com ~all"3600
TXT"atlassian-domain-verification=LmhbOFlPaFZGD6QBkVhcQgaAZnNJpu6TSN/ooZ4Uz4oSRysmViCxBklmtqGxhgtD"3600
TXT"202102031503085i2g01dm4wna6va5snmqy8adplf3nxcf0n2ycrwl0hzsv7rgha"3600
TXT"67g1q3d61g1hz4pkrh41bzwdxks46wgc"3600
TXT"google-site-verification=YUal8fQqF7rKGv5xqsiNXoCXtG5Jh-i4hv-7tlKr53g"3600
TXT"google-site-verification=n6jXS5K-saQykmYLf9quyupzNneSvwkN7bkCbqP8BDU"3600
TXT"MS=ms36816578"3600

Checks

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