wonderbox.fr

Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns01.wonderbox.fr, ns02.wonderbox.fr; only in the zone: ns01.wonderbox.com, ns02.wonderbox.com. ns01.wonderbox.com, ns01.wonderbox.fr, ns02.wonderbox.com, ns02.wonderbox.fr report NS ns01.wonderbox.com ns02.wonderbox.com.

Delegation · all IPv4 addresses are in 213.182.35.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.

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: mx-mibc-fr-11.mailinblack.com, mx-mibc-fr-11.mailinblack.com

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits). Rotate to a 2048-bit key.

MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 4.176.17.204 (mx-mibc-fr-11.mailinblack.com), 4.176.17.204 (mx-mibc-fr-11.mailinblack.com). Ask your hosting provider to set one.

TLS · With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.

TLS · These MX hosts are not listed in the MTA-STS policy (mx: wonderbox-fr.mail.protection.outlook.com): mx-mibc-fr-11.mailinblack.com, mx-mibc-fr-11.mailinblack.com. This will break delivery once the policy is enforced.