bruaylabuissiere.fr

Checked 22 October 2026, 02:02 UTC · via 8.8.8.8
✗Problems found
15 passed 5 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf.cloud.vadesecure.com include:mx.ovh.com ~all
DNS lookups
4 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 4 of 10 DNS lookups #2
    SPF record needs 4 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

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

13 mail servers

Found

PriorityHostRecordsReverse DNS
0mx0.mail.ovh.netA 178.33.252.245mx0.mail.ovh.net ✓
10mx01.cloud.vadesecure.comA 163.172.240.110mx01.cloud.vadesecure.com ✓
10mx02.cloud.vadesecure.comA 163.172.240.111mx02.cloud.vadesecure.com ✓
10mx03.cloud.vadesecure.comA 135.125.122.66mx03.cloud.vadesecure.com ✓
10mx04.cloud.vadesecure.comA 135.125.122.67mx04.cloud.vadesecure.com ✓
10mx1.mail.ovh.netA 188.165.36.237mx1.mail.ovh.net ✓
10vade-mx-fr01.hornetsecurity.comA 94.100.138.100hsmx01-hz12.hornetsecurity.com ✓
10vade-mx-fr02.hornetsecurity.comA 94.100.138.100hsmx01-hz12.hornetsecurity.com ✓
20mx2.mail.ovh.netA 87.98.160.167mx2.mail.ovh.net ✓
20vade-mx-eu-fallback01.hornetsecurity.comA 94.100.132.8mx01.hornetsecurity.com ✓
20vade-mx-eu-fallback02.hornetsecurity.comA 94.100.132.8mx01.hornetsecurity.com ✓
30mx3.mail.ovh.netA 91.121.53.175mx3.mail.ovh.net ✓
40mx4.mail.ovh.netA 178.32.124.207mx4.mail.ovh.net ✓

Checks

  • ✓ 13 MX records #9
    Found 13 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, mx01.cloud.vadesecure.com, mx02.cloud.vadesecure.com, mx03.cloud.vadesecure.com, mx04.cloud.vadesecure.com, mx1.mail.ovh.net, vade-mx-fr01.hornetsecurity.com, vade-mx-fr02.hornetsecurity.com, mx2.mail.ovh.net, vade-mx-eu-fallback01.hornetsecurity.com, vade-mx-eu-fallback02.hornetsecurity.com, mx3.mail.ovh.net, mx4.mail.ovh.net
    #11
  • ✓ Redundant MX hosts #12
    Found 13 MX records, which provides redundancy for email delivery.
  • !
    More than 5 MX records
    Found 13 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • ✓ 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 13 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx0.mail.ovh.netnone-
mx01.cloud.vadesecure.comnone-
mx02.cloud.vadesecure.comnone-
mx03.cloud.vadesecure.comnone-
mx04.cloud.vadesecure.comnone-
mx1.mail.ovh.netnone-
vade-mx-fr01.hornetsecurity.comnone-
vade-mx-fr02.hornetsecurity.comnone-
mx2.mail.ovh.netnone-
vade-mx-eu-fallback01.hornetsecurity.comnone-
vade-mx-eu-fallback02.hornetsecurity.comnone-
mx3.mail.ovh.netnone-
mx4.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