fortuneo.fr

Checked 22 October 2026, 03:06 UTC · via 8.8.8.8
!Passed with warnings
25 passed 4 warnings 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 a mx include:mx.arkea.com include:spf.quicksign.fr ip4:83.206.208.128/25 ip4:81.252.92.0/23 ip4:86.64.210.0/23 ip4:195.2.74.0/23 -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

pass

p=reject (_dmarc.fortuneo.fr)

Found

Record
v=DMARC1; p=reject; rua=mailto:fortuneo@rua.netcraft.com; ruf=mailto:fortuneo@ruf.netcraft.com; aspf=s; adkim=s;
Found at
_dmarc.fortuneo.fr
External report address
mailto:fortuneo@rua.netcraft.com (authorized)
External report address
mailto:fortuneo@ruf.netcraft.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:fortuneo@rua.netcraft.comAggregate report addresses
rufmailto:fortuneo@ruf.netcraft.comFailure report addresses
adkimsDKIM alignment (r = relaxed, s = strict)
aspfsSPF alignment (r = relaxed, s = strict)

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.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:fortuneo@rua.netcraft.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

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
10mx5.arkea.comA 195.101.71.8mx5.arkea.com ✓
10mx6.arkea.comA 93.20.45.8mx6.arkea.com ✓
10mx7.arkea.comA 93.20.41.8mx7.arkea.com ✓
10mx8.arkea.comA 80.124.164.135mx8.arkea.com ✓

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: mx5.arkea.com, mx6.arkea.com, mx7.arkea.com, mx8.arkea.com
    #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
mx5.arkea.comnone-
mx6.arkea.comnone-
mx7.arkea.comnone-
mx8.arkea.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

pass

https://vmc.digicert.com/daf91cd1-0239-43ff-b229-d86ccd27cc02.svg

Found

Record
v=BIMI1; l=https://vmc.digicert.com/daf91cd1-0239-43ff-b229-d86ccd27cc02.svg; a=https://vmc.digicert.com/daf91cd1-0239-43ff-b229-d86ccd27cc02.pem
Found at
default._bimi.fortuneo.fr
Logo
https://vmc.digicert.com/daf91cd1-0239-43ff-b229-d86ccd27cc02.svg
Certificate
https://vmc.digicert.com/daf91cd1-0239-43ff-b229-d86ccd27cc02.pem

Checks

  • ✓ Logo and certificate published #38
    BIMI logo: https://vmc.digicert.com/daf91cd1-0239-43ff-b229-d86ccd27cc02.svg; certificate: https://vmc.digicert.com/daf91cd1-0239-43ff-b229-d86ccd27cc02.pem
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.