integratie-inburgering.be

Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns1.combell.eu, ns3.combell.net, ns4.combell.net; only in the zone: ns1.register.be, ns2.register.be, ns3.register.be. ns1.combell.eu, ns1.register.be, ns2.register.be, ns3.combell.net, ns3.register.be, ns4.combell.net report NS ns1.register.be ns2.register.be ns3.register.be.

DNSSEC · The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.

DNSSEC · NSEC3 uses 5 iterations and a 4-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.

DNSSEC · The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.

MX · The following MX hosts could not be resolved to IPv6 addresses: integratieinburgering-be02e.mail.protection.outlook.com

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

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector1 (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.