clikeo.fr

Checked 22 October 2026, 02:20 UTC · via 8.8.8.8
!Passed with warnings
21 passed 5 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:mx.ovh.com ip4:5.196.78.121 ip4:164.132.167.204 ip4:5.196.77.194 ip4:149.202.72.22 ip4:57.128.116.219 ip4:149.202.83.91 ip4:149.202.89.111 ip4:51.68.39.35 ip4:149.202.82.192 ip4:37.187.8.124 ip4:51.255.35.174 ip4:151.80.34.216 ip4:5.135.189.194 ip4:51.83.3.63 ip4:151.80.19.42 ip4:141.94.74.120 ip4:94.23.250.118 ip4:164.132.202.153 ip4:37.187.28.24 ip4:176.31.226.209 ip4:51.75.241.22 ip4:46.105.111.137 ip4:51.75.243.200 ip4:152.228.175.118 ip4:185.175.151.168 ip4:152.228.224.86 ip4:162.19.102.21 ip4:54.36.103.229 ip4:91.134.34.194 ip4:141.94.141.94 ip4:164.132.167.204 mx a -all
DNS lookups
5 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 5 of 10 DNS lookups #2
    SPF record needs 5 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=reject (_dmarc.clikeo.fr)

Found

Record
v=DMARC1;p=reject;
Found at
_dmarc.clikeo.fr
TagValueMeaning
vDMARC1Version
prejectPolicy

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ 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.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.

DKIM

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

  • !
    No key under common selectors
    The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #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

4 mail servers

Found

PriorityHostRecordsReverse DNS
1mx0.mail.ovh.netA 178.33.252.245mx0.mail.ovh.net ✓
5mx1.mail.ovh.netA 188.165.36.237mx1.mail.ovh.net ✓
50mx2.mail.ovh.netA 87.98.160.167mx2.mail.ovh.net ✓
100mx3.mail.ovh.netA 91.121.53.175mx3.mail.ovh.net ✓

Checks

  • ✓ 4 MX records #9
    Found 4 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: mx0.mail.ovh.net, mx1.mail.ovh.net, mx2.mail.ovh.net, mx3.mail.ovh.net
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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 4 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx0.mail.ovh.netnone-
mx1.mail.ovh.netnone-
mx2.mail.ovh.netnone-
mx3.mail.ovh.netnone-

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