famillechretienne.fr

Checked 22 October 2026, 03:01 UTC · via 8.8.8.8
✗Problems found
20 passed 5 warnings 2 failed 3 info

SPF

fail

SPF record published

Found

Record
v=spf1 include:mx.ovh.com -all
DNS lookups
3 of 10
Void lookups
0 of 2
Records published
2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 3 of 10 DNS lookups #2
    SPF record needs 3 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.
  • ✗
    Multiple SPF records
    Found 2 SPF records. Publishing more than one v=spf1 record causes a permerror; merge them into a single record.
    #16
  • ✓ 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.famillechretienne.fr)

Found

Record
v=DMARC1; p=none; sp=none; rua=mailto:dmarc-reports@pluriad.fr, mailto:dmarc@mailinblue.com!10m; ruf=mailto:dmarc@mailinblue.com!10m; rf=afrf; pct=100; ri=86400
Found at
_dmarc.famillechretienne.fr
External report address
mailto:dmarc-reports@pluriad.fr (not authorized)
External report address
mailto:dmarc@mailinblue.com!10m (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:dmarc-reports@pluriad.fr, mailto:dmarc@mailinblue.com!10mAggregate report addresses
rufmailto:dmarc@mailinblue.com!10mFailure report addresses
rfafrfFailure report format
ri86400Report interval (seconds)

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:dmarc-reports@pluriad.fr, mailto:dmarc@mailinblue.com!10m
  • !
    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:dmarc-reports@pluriad.fr (needs famillechretienne.fr._report._dmarc.pluriad.fr). Ask the report provider to publish the record, or check the address.
    #29

DKIM

warn

Selectors: mail, selector1

Found

Selectors
mail, selector1
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits
selector1RSA 2048 bits

Checks

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

5 mail servers

Found

PriorityHostRecordsReverse DNS
10de-smtp-inbound-1.mimecast.comA 194.104.108.22 A 194.104.110.22de-smtp-inbound-2.mimecast.com ✓ de-smtp-inbound-2.mimecast.com ✓
10de-smtp-inbound-2.mimecast.comA 194.104.108.22 A 194.104.110.22de-smtp-inbound-2.mimecast.com ✓ de-smtp-inbound-1.mimecast.com ✓
80mx1.mail.ovh.netA 188.165.36.237mx1.mail.ovh.net ✓
90mx2.mail.ovh.netA 87.98.160.167mx2.mail.ovh.net ✓
100mx3.mail.ovh.netA 91.121.53.175mx3.mail.ovh.net ✓

Checks

  • ✓ 5 MX records #9
    Found 5 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: de-smtp-inbound-1.mimecast.com, de-smtp-inbound-2.mimecast.com, mx1.mail.ovh.net, mx2.mail.ovh.net, mx3.mail.ovh.net
    #11
  • ✓ Redundant MX hosts #12
    Found 5 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 5 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 7 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
de-smtp-inbound-1.mimecast.comnone-
de-smtp-inbound-2.mimecast.comnone-
mx1.mail.ovh.netnone-
mx2.mail.ovh.netnone-
mx3.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