SurfaceMap › m › maldegem.be

maldegem.be

Checked 2026-10-22 06:50 UTC · first added 2026-10-21

✗Problems found Score 65 of 100

Domain & DNS

warn

27 passed 2 warn 0 failed

Areas

iRegistration ✓Delegation !Nameservers ✓SOA !DNSSEC iRecords

Problems

!

Software version disclosed

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: dns1.level27.eu: "9.18.18-0ubuntu0.22.04.1-Ubuntu"; dns2.level27.eu: "9.18.39-0ubuntu0.24.04.5-Ubuntu"; dns3.level27.net: "9.18.39-0ubuntu0.24.04.3-Ubuntu". Hide or replace the version string.

#17
!

Deprecated algorithm

DNSSEC · SHA-1 based algorithms are deprecated and rejected by some validators: RSASHA1-NSEC3-SHA1 (7). Roll over to ECDSAP256SHA256 (13).

#29

Recent checks

!

Full report

Domain & DNS report for maldegem.be ›

Mail

fail

23 passed 3 warn 2 failed

Areas

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

Problems

✗

11 DNS lookups, over the limit of 10

SPF · SPF record needs 11 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.

#2
✗

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
!

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), mta (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 maldegem.be ›