levoyageanantes.fr

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

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf.mailjet.com include:_spf.datapressepremium.com include:spf.secutix.com include:spf.cloud.vadesecure.com include:spf.hornetsecurity.com a mx a:spf-senders.oceamail.com ip4:46.247.130.170/28 ip4:213.41.75.42 ip4:95.128.73.57 ~all
DNS lookups
8 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=quarantine; sp=quarantine; rf=afrf; pct=100; ri=86400; rua=mailto:informatique@lvan.fr
Found at
_dmarc.levoyageanantes.fr
External report address
mailto:informatique@lvan.fr (not authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spquarantineSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:informatique@lvan.frAggregate report addresses
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:informatique@lvan.fr
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • !
    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:informatique@lvan.fr (needs levoyageanantes.fr._report._dmarc.lvan.fr). Ask the report provider to publish the record, or check the address.
    #29

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

8 mail servers

Found

PriorityHostRecordsReverse DNS
11vade-mx-fr01.hornetsecurity.comA 94.100.138.100hsmx01-hz12.hornetsecurity.com ✓
11vade-mx-fr02.hornetsecurity.comA 94.100.138.100hsmx01-hz12.hornetsecurity.com ✓
20vade-mx-eu-fallback01.hornetsecurity.comA 94.100.132.8mx01.hornetsecurity.com ✓
20vade-mx-eu-fallback02.hornetsecurity.comA 94.100.132.8mx01.hornetsecurity.com ✓
50mx01.cloud.vadesecure.comA 163.172.240.110mx01.cloud.vadesecure.com ✓
50mx02.cloud.vadesecure.comA 163.172.240.111mx02.cloud.vadesecure.com ✓
50mx03.cloud.vadesecure.comA 135.125.122.66mx03.cloud.vadesecure.com ✓
50mx04.cloud.vadesecure.comA 135.125.122.67mx04.cloud.vadesecure.com ✓

Checks

  • ✓ 8 MX records #9
    Found 8 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: vade-mx-fr01.hornetsecurity.com, vade-mx-fr02.hornetsecurity.com, vade-mx-eu-fallback01.hornetsecurity.com, vade-mx-eu-fallback02.hornetsecurity.com, mx01.cloud.vadesecure.com, mx02.cloud.vadesecure.com, mx03.cloud.vadesecure.com, mx04.cloud.vadesecure.com
    #11
  • ✓ Redundant MX hosts #12
    Found 8 MX records, which provides redundancy for email delivery.
  • !
    More than 5 MX records
    Found 8 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 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
vade-mx-fr01.hornetsecurity.comnone-
vade-mx-fr02.hornetsecurity.comnone-
vade-mx-eu-fallback01.hornetsecurity.comnone-
vade-mx-eu-fallback02.hornetsecurity.comnone-
mx01.cloud.vadesecure.comnone-
mx02.cloud.vadesecure.comnone-
mx03.cloud.vadesecure.comnone-
mx04.cloud.vadesecure.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