SurfaceMap › o › omroep.nl

omroep.nl

Checked 2026-10-21 21:24 UTC · first added 2026-10-21
✗Problems found Score 68 of 100

Domain & DNS

warn

29 passed 1 warn 0 failed

Areas

iRegistration ✓Delegation iNameservers !SOA ✓DNSSEC iRecords

Problems

  • !
    Serial date in the future
    SOA · The serial 2026102816 looks like a date (YYYYMMDDnn) in the future (2026-10-28). It can only grow, so a wrong date can't be undone without a serial wrap-around.
    #26

Recent checks

!

Full report

Domain & DNS report for omroep.nl ›

Mail

fail

20 passed 3 warn 2 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
  • ✗
    No DKIM keys published
    DKIM · _domainkey.omroep.nl does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    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
  • !
    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 omroep.nl ›