indigenes-republique.fr

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.

SPF · SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.

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 · Found 9 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.

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

DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:multitudesiskra@gmail.com (needs indigenes-republique.fr._report._dmarc.gmail.com). Ask the report provider to publish the record, or check the address.

MX · The PTR name of these addresses does not resolve back to the same address: 2001:4b98:dc4:8::215 -> spool6.mail.gandi.net, 2001:4b98:dc4:8::216 -> spool7.mail.gandi.net, 2001:4b98:dc4:8::217 -> spool8.mail.gandi.net.

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.