fitnesspark.fr

Checked 22 October 2026, 03:04 UTC · via 8.8.8.8
✗Problems found
25 passed 4 warnings 1 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:mx.ovh.com include:spf.mailjet.com include:mail.zendesk.com include:_spf.google.com ~all
DNS lookups
6 of 10
Void lookups
0 of 2

Checks

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

p=none (_dmarc.fitnesspark.fr)

Found

Record
v=DMARC1; p=none; rua=mailto:qnv5swa2@ag.eu.dmarcian.com; ruf=mailto:qnv5swa2@fr.eu.dmarcian.com; fo=1;
Found at
_dmarc.fitnesspark.fr
External report address
mailto:qnv5swa2@ag.eu.dmarcian.com (authorized)
External report address
mailto:qnv5swa2@fr.eu.dmarcian.com (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:qnv5swa2@ag.eu.dmarcian.comAggregate report addresses
rufmailto:qnv5swa2@fr.eu.dmarcian.comFailure report addresses
fo1Failure reporting options

Checks

  • ✗
    Policy: none (monitoring only)
    DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:qnv5swa2@ag.eu.dmarcian.com
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: google, s1, s2

Found

Selectors
google, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
googleRSA 2048 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: google, s1, s2 #7
    DKIM keys found for this domain with selectors: google, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

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
0mx0.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

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

Found

MTA-STS record
v=STSv1; id=202408140000;
Policy URL
https://mta-sts.fitnesspark.fr/.well-known/mta-sts.txt
Mode
testing
Allowed MX
mx0.mail.ovh.net, mx1.mail.ovh.net, mx2.mail.ovh.net, mx3.mail.ovh.net
Max age
86400 seconds
TLS-RPT record
v=TLSRPTv1; rua=mailto:qnv5swa2@tls.eu.dmarcian.com

DANE (TLSA records)

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

Checks

  • ✓ Record published #32
    MTA-STS record found with id 202408140000.
  • !
    Policy in testing mode
    With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.
    #33
  • ✓ All MX hosts covered #34
    Every MX host matches an mx: line of the MTA-STS policy.
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:qnv5swa2@tls.eu.dmarcian.com
  • 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