uzgent.be

Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: uzg11.uzgent.be. ns1.belnet.be, ns2.belnet.be, ns3.belnet.be, uzg11.uzgent.be, uzg22.uzgent.be, uzg44.uzgent.be report NS ns1.belnet.be ns2.belnet.be ns3.belnet.be uzg11.uzgent.be uzg22.uzgent.be uzg44.uzgent.be.

SOA · The serial 2026103163 looks like a date (YYYYMMDDnn) in the future (2026-10-31). It can only grow, so a wrong date can't be undone without a serial wrap-around.

Records · These records have a TTL below 5m, causing extra queries and slower lookups: MX (1m39s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 2h; resolvers may use either.

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: mail9.uzgent.be, mail10.uzgent.be

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