rodekruis.be

Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns.be.hostbasket.com, ns.fr.hostbasket.com, ns.nl.hostbasket.com; only in the zone: ns1.cloud.telenet.be, ns2.cloud.telenet.be, ns3.cloud.telenet.be. ns.be.hostbasket.com, ns.fr.hostbasket.com, ns.nl.hostbasket.com, ns1.cloud.telenet.be, ns2.cloud.telenet.be, ns3.cloud.telenet.be report NS ns1.cloud.telenet.be ns2.cloud.telenet.be ns3.cloud.telenet.be.

DNSSEC · NSEC3 uses 10 iterations and a 16-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.

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

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

DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

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

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.

TLS · MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".