zodio.fr

SOA · The nameservers serve different versions of the zone: 2026030319 on ns-cloud-b1.googledomains.com (216.239.32.107), ns-cloud-b1.googledomains.com (2001:4860:4802:32::6b), ns-cloud-b2.googledomains.com (216.239.34.107), ns-cloud-b2.googledomains.com (2001:4860:4802:34::6b), ns-cloud-b3.googledomains.com (216.239.36.107), ns-cloud-b3.googledomains.com (2001:4860:4802:36::6b), ns-cloud-b4.googledomains.com (216.239.38.107), ns-cloud-b4.googledomains.com (2001:4860:4802:38::6b); 2026100211 on nsa.perf1.fr (81.92.94.100), nsa.perf1.fr (2a01:c8:100::100), nsb.perf1.com (81.92.95.100), nsb.perf1.com (2a01:c8:101::100), nsc.perf1.com (152.89.172.100), nsc.perf1.com (2a09:35c0:102::100). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.

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 1 iteration and a 8-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.

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

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 · No MX records found. If this domain is used for email, add MX records to specify mail servers. If it never receives mail, publish a null MX ("MX 0 .").