SurfaceMap › m › munzinger.de

munzinger.de

Checked 2026-10-21 23:31 UTC · first added 2026-10-21
✗Problems found Score 49 of 100

Domain & DNS

fail

18 passed 4 warn 3 failed

Areas

iRegistration ✗Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    Nameserver names don't resolve
    Delegation · These nameservers have no A or AAAA record, so they can't be reached (lame delegation): sedat1.sedat.de.
    #9
  • ✗
    Lame delegation
    Nameservers · These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns1.sedat.de (193.141.67.53): REFUSED, authoritative=false; ns2.key-systems.net (194.50.187.229): REFUSED, authoritative=false; ns2.key-systems.net (2a04:2b00:14dd::229): REFUSED, authoritative=false; ns2.rrpproxy.net (194.50.187.226): REFUSED, authoritative=false; ns2.rrpproxy.net (2a04:2b00:14dd::226): 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: ns1.sedat.de (193.141.67.53): ; ns2.key-systems.net (194.50.187.229): ; ns2.key-systems.net (2a04:2b00:14dd::229): ; ns2.rrpproxy.net (194.50.187.226): ; ns2.rrpproxy.net (2a04:2b00:14dd::226): .
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns2.key-systems.net, sedat1.sedat.de; only in the zone: ns1.sedat.de, ns2.rrpproxy.net. ns2.sedat.de, ns3.sedat.de report NS ns1.sedat.de ns2.rrpproxy.net ns2.sedat.de ns3.sedat.de.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.sedat.de: "9.20.29"; ns2.sedat.de: "9.8.4-rpz2+rl005.12-P1"; ns3.sedat.de: "9.9.5-9+deb8u15-Debian". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · refresh 10m is outside 20m–1d; retry 10m should be shorter than refresh 10m; expire 1h is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 10m, retry 10m, expire 1h, negative TTL 1h.
    #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

Recent checks

✗

Full report

Domain & DNS report for munzinger.de ›

Mail

warn

28 passed 3 warn 0 failed

Areas

✓SPF !DMARC ✓DKIM !DNSSEC !MX iTLS iBIMI

Problems

  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mx0.munzinger.de, mx1.munzinger.de
    #11
  • !
    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

Recent checks

!

Full report

Mail report for munzinger.de ›