SurfaceMap › b › bezreg-muenster.de

bezreg-muenster.de

Checked 2026-10-21 21:40 UTC · first added 2026-10-21
!Check could not complete

Domain & DNS

error

18 passed 0 warn 2 failed 2 errors

lookups failed for dnssec, records; results are incomplete

Areas

iRegistration iDelegation ✗Nameservers ✓SOA iDNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: a.it.nrw (93.184.132.50): read udp 46.225.38.91:34945->93.184.132.50:53: i/o timeout.
    #14
  • ✗
    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: b.nrw.de (93.184.128.141): read tcp 46.225.38.91:49314->93.184.128.141:53: i/o timeout.
    #19

Recent checks

!

Full report

Domain & DNS report for bezreg-muenster.de ›

Mail

fail

0 passed 2 warn 3 failed

Areas

✗SPF ✗DMARC ✗DKIM !DNSSEC !MX iBIMI

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • ✗
    No SPF record
    SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6
  • ✗
    No DKIM keys published
    DKIM · _domainkey.bezreg-muenster.de does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    No MX records
    MX · No MX records found. If this domain is used for email, add MX records to specify mail servers. If it never receives mail, publish a null MX ("MX 0 .").
    #9

Recent checks

✗

Full report

Mail report for bezreg-muenster.de ›