avignon.fr

Checked 22 October 2026, 01:51 UTC · via 8.8.8.8
!Passed with warnings
21 passed 8 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf.protection.outlook.com -all
DNS lookups
1 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 1 of 10 DNS lookups #2
    SPF record needs 1 DNS lookups (limit is 10).
  • ✓ Ends with -all #3
    SPF record properly uses -all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

warn

p=quarantine (_dmarc.avignon.fr)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:jean-baptiste.dri@mairie-avignon.com; ruf=mailto:jean-baptiste.dri@mairie-avignon.com; fo=0; adkim=r; aspf=r; pct=100; rf=afrf; ri=86400; sp=none
Found at
_dmarc.avignon.fr
External report address
mailto:jean-baptiste.dri@mairie-avignon.com (not authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:jean-baptiste.dri@mairie-avignon.comAggregate report addresses
rufmailto:jean-baptiste.dri@mairie-avignon.comFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
fo0Failure reporting options
rfafrfFailure report format
ri86400Report interval (seconds)

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:jean-baptiste.dri@mairie-avignon.com
  • !
    Subdomains unprotected (sp=none)
    DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • !
    Report address not authorized
    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.
    #29

DKIM

warn

Selectors: dkim, mail, selector1, selector2

Found

Selectors
dkim, mail, selector1, selector2
_domainkey
NOERROR
SelectorKeyFlags
dkimRSA 1024 bits
mailRSA 1024 bits
selector1RSA 2048 bits
selector2RSA 2048 bits

Checks

  • ✓ Keys found: dkim, mail, selector1, selector2 #7
    DKIM keys found for this domain with selectors: dkim, mail, selector1, selector2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: dkim (1024 bits), mail (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
10avignon.fr.avignon.fr(does not resolve)
20avignon-fr.mail.protection.outlook.comA 52.101.68.29 A 52.101.68.8 A 52.101.185.114 A 52.101.103.39 AAAA 2a01:111:f403:ca25:: AAAA 2a01:111:f403:ca25::1 AAAA 2a01:111:f403:ca1e:: AAAA 2a01:111:f403:ca25::2mail-dbapr03cu00105.inbound.protection.outlook.com ✓ mail-du0pr03cu00100.inbound.protection.outlook.com ✓ mail-zrxpr04cu00102.inbound.protection.outlook.com ✓ mail-miypr05cu00207.inbound.protection.outlook.com ✓ mail-pa5p264cu00200.inbound.protection.outlook.com ✓ mail-pr0p264cu01301.inbound.protection.outlook.com ✓ mail-mrzp264cu00100.inbound.protection.outlook.com ✓ mail-paup264cu00202.inbound.protection.outlook.com ✓

Checks

  • ✓ 2 MX records #9
    Found 2 MX records for this domain.
  • !
    Hosts without IP addresses
    The following MX hosts could not be resolved to IP addresses: avignon.fr.avignon.fr
    #10
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: avignon.fr.avignon.fr
    #11
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 MX records, which is within the recommended range (1-5).
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 2 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
avignon.fr.avignon.frnone-
avignon-fr.mail.protection.outlook.comnone-

Checks

  • !
    Not configured
    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.
    #32
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38