zaventem.be

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns.bnamed.uk: "Knot DNS 3.5.3"; ns.bnamed.us: "Knot DNS 3.5.3". Hide or replace the version string.

DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

MX · The following MX hosts could not be resolved to IPv6 addresses: antispam.zaventem.be

MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.

DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: email (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.

MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 77.67.54.41 (antispam.zaventem.be). Ask your hosting provider to set one.

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.