clauses-abusives.fr

Checked 22 October 2026, 02:18 UTC · via 8.8.8.8
✗Problems found
15 passed 4 warnings 2 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

fail

No DMARC record found

Checks

  • ✗
    No DMARC record
    No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5

DKIM

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _domainkey.clauses-abusives.fr does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7

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

3 mail servers

Found

PriorityHostRecordsReverse DNS
0clausesabusives-fr01i.mail.protection.outlook.comA 52.101.166.1 A 52.101.166.2 A 52.101.164.0 A 52.101.166.0 AAAA 2a01:111:f403:ca04::d AAAA 2a01:111:f403:ca04::a AAAA 2a01:111:f403:ca09::a AAAA 2a01:111:f403:ca48::8mail-pr0p264cu01301.inbound.protection.outlook.com ✓ mail-paup264cu00202.inbound.protection.outlook.com ✓ mail-mrzp264cu00100.inbound.protection.outlook.com ✓ mail-pa5p264cu00200.inbound.protection.outlook.com ✓ mail-db6pr03cu00105.inbound.protection.outlook.com ✓ mail-du0pr03cu00102.inbound.protection.outlook.com ✓ mail-am7pr02cu00202.inbound.protection.outlook.com ✓ mail-miypr02cu00100.inbound.protection.outlook.com ✓
1mx1-eu.emailsecurity.appA 132.164.188.153mx2-eu.emailsecurity.app (does not resolve back)
10mx2-eu.emailsecurity.appA 4.245.183.72mx1-eu.emailsecurity.app (does not resolve back)

Checks

  • ✓ 3 MX records #9
    Found 3 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: mx1-eu.emailsecurity.app, mx2-eu.emailsecurity.app
    #11
  • ✓ Redundant MX hosts #12
    Found 3 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 3 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 does not match
    The PTR name of these addresses does not resolve back to the same address: 132.164.188.153 -> mx2-eu.emailsecurity.app, 4.245.183.72 -> mx1-eu.emailsecurity.app.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
clausesabusives-fr01i.mail.protection.outlook.comnone-
mx1-eu.emailsecurity.appnone-
mx2-eu.emailsecurity.appnone-

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