avignon.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.

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 IP addresses: avignon.fr.avignon.fr

MX · The following MX hosts could not be resolved to IPv6 addresses: avignon.fr.avignon.fr

DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.

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.

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

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.