SurfaceMap › n › neumuenster.de

neumuenster.de

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

Domain & DNS

fail

17 passed 2 warn 2 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Zone transfer allowed
    Nameservers · These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns.neumuenster.de (2001:1438:1018:101::53): 277 records; ns2.neumuenster.de (2001:1438:1018:102::53): 277 records. Restrict zone transfers to your secondary servers.
    #18
  • ✗
    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: ns.neumuenster.de (212.93.31.115): dial tcp 212.93.31.115:53: i/o timeout; ns2.neumuenster.de (94.135.229.149): dial tcp 94.135.229.149:53: i/o timeout.
    #19
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns.neumuenster.de (glue 212.93.31.115, zone 212.93.31.115, 2001:1438:1018:101::53); ns2.neumuenster.de (glue 94.135.229.149, zone 94.135.229.149, 2001:1438:1018:102::53). Update the glue at your registrar.
    #8
  • !
    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 neumuenster.de ›

Mail

fail

23 passed 3 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
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Reverse DNS does not match
    MX · The PTR name of these addresses does not resolve back to the same address: 212.93.31.114 -> mx2.neumuenste.de.
    #30
  • !
    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 neumuenster.de ›