uvcw.be

Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.thgnet.net: "9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.9"; ns2.thgnet.net: "9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.16". Hide or replace the version string.

SOA · retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 14d, negative TTL 1d.

DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.

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

DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

MX · The following MX hosts could not be resolved to IPv6 addresses: uvcw-be-1.fortimailcloud.com, uvcw-be-2.fortimailcloud.com

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.