SurfaceMap › s › sz-online.de

sz-online.de

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

Domain & DNS

fail

18 passed 5 warn 2 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC !Records

Problems

  • ✗
    Lame delegation
    Nameservers · These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns2.sz-online.de (193.254.185.232): REFUSED, authoritative=false; pns.sz-online.de (195.74.47.32): REFUSED, authoritative=false.
    #15
  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns2.sz-online.de (193.254.185.232): ; pns.sz-online.de (195.74.47.32): .
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns0.niedersachsen.com, pns.dtag.de, secondary006.dtag.net; only in the zone: ns2.sz-online.de, pns.sz-online.de. ns0.niedersachsen.com, pns.dtag.de, secondary006.dtag.net report NS ns2.sz-online.de pns.sz-online.de.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns0.niedersachsen.com: "9.20.29"; ns2.sz-online.de: "9.16.27-Debian". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 2m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 4h, retry 1h, expire 21d, negative TTL 2m.
    #23
  • !
    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 (2m), MX (2m), NS (2m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 2m; resolvers may use either.
    #32

Recent checks

✗

Full report

Domain & DNS report for sz-online.de ›

Mail

warn

20 passed 7 warn 0 failed

Areas

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

Problems

  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    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
  • !
    Broad IP ranges
    SPF · These ranges authorize tens of thousands of addresses or more: ip4:172.16.0.0/12. Check that you really own and send from all of them.
    #27
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc@ddv-mediengruppe.de (needs sz-online.de._report._dmarc.ddv-mediengruppe.de). Ask the report provider to publish the record, or check the address.
    #29
  • !
    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 sz-online.de ›