calaos.fr

Delegation · all IPv4 addresses are in 193.168.146.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).

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.calaos.fr: "PowerDNS Authoritative Server 4.7.3"; ns2.calaos.fr: "PowerDNS Authoritative Server 4.7.3". Hide or replace the version string.

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.

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

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: mx1.calaos.fr

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

DMARC · DMARC policy only applies to 50% of failing mail (pct=50). Raise pct to 100 once you are confident in your setup.

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