ffspeleo.fr

Checked 22 October 2026, 03:03 UTC · via 8.8.8.8
✗Problems found
24 passed 3 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 a:ffspeleo.fr a:speleos.fr mx:mx1.speleos.fr ip4:188.165.238.67 include:mx.ovh.com include:spf.speleos.fr ip4:193.70.18.144 ~all
DNS lookups
7 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=none; rua=mailto:intranet@ffspeleo.fr; pct=100
Found at
_dmarc.ffspeleo.fr
TagValueMeaning
vDMARC1Version
pnonePolicy
pct100Percentage of mail the policy applies to
ruamailto:intranet@ffspeleo.frAggregate report addresses

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:intranet@ffspeleo.fr
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: mail, mx

Found

Selectors
mail, mx
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 2048 bitsh=sha256
mxRSA 1024 bits

Checks

  • ✓ Keys found: mail, mx #7
    DKIM keys found for this domain with selectors: mail, mx
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: mx (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

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
52686, 48659
Signatures valid until
14 November 2026, 11:57 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • ✓ Signatures valid until 2026-11-14 #21
    DNSKEY signatures are valid until 2026-11-14T11:57:40Z.

MX

warn

3 mail servers

Found

PriorityHostRecordsReverse DNS
1mx3.ovh.netA 91.121.56.64mx3.ovh.net ✓
5mx4.ovh.netA 178.32.105.189mx4.ovh.net ✓
100mxb.ovh.netA 46.105.45.21mxb.ovh.net ✓

Checks

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

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx3.ovh.netnone-
mx4.ovh.netnone-
mxb.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