SurfaceMap › s › schwarzwaelder-bote.de

schwarzwaelder-bote.de

Checked 2026-10-22 00:02 UTC · first added 2026-10-21
✗Problems found Score 44 of 100

Domain & DNS

fail

19 passed 5 warn 1 failed

Areas

iRegistration !Delegation !Nameservers ✗SOA !DNSSEC !Records

Problems

  • ✗
    Invalid contact address
    SOA · The SOA RNAME "hostmaster\\@sbm-int.de" contains an @; it must be written with a dot instead (hostmaster.example.com).
    #25
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Software version disclosed
    Nameservers · 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
  • !
    Serials differ
    SOA · 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
  • !
    Not signed
    DNSSEC · 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
  • !
    Very low TTLs
    Records · 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

Recent checks

✗

Full report

Domain & DNS report for schwarzwaelder-bote.de ›

Mail

fail

18 passed 7 warn 1 failed

Areas

!SPF ✗DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    6 of 10 DNS lookups, with problems
    SPF · SPF record needs 6 DNS lookups (limit is 10). Problems found: include:de._netblocks.mimecast.com\009include:amazonses.com does not exist or has no records.
    #2
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), selector2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    1 void lookup
    SPF · 1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.
    #26
  • !
    Not configured
    TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32

Recent checks

✗

Full report

Mail report for schwarzwaelder-bote.de ›