SurfaceMap › b › baarle-hertog.be

baarle-hertog.be

Checked 2026-10-22 06:04 UTC · first added 2026-10-21
✗Problems found Score 49 of 100

Domain & DNS

warn

20 passed 3 warn 0 failed

Areas

iRegistration !Delegation ✓Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 193.190.121.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    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 baarle-hertog.be ›

Mail

fail

16 passed 4 warn 3 failed

Areas

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

Problems

  • ✗
    No 'all' mechanism
    SPF · SPF record doesn't have an 'all' mechanism. Add -all or ~all at the end of your SPF record.
    #3
  • ✗
    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
  • ✗
    Syntax errors
    SPF · Receivers reject the whole SPF record (permerror) because of: unknown mechanism "\\226\\128\\139\\226\\128\\139\\226\\128\\139\\226\\128\\139\\226\\128\\139\\226\\128\\139\\226\\128\\139include:mailgun.org\\194\\160-all".
    #25
  • !
    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
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), s1 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 baarle-hertog.be ›