secourspopulaire.fr

Checked 22 October 2026, 05:10 UTC · via 8.8.8.8
✗Problems found
20 passed 4 warnings 2 failed 3 info

SPF

fail

SPF record published

Found

Record
v=spf1 ip4:145.239.186.107 ip4:145.239.186.108 ip4:145.239.186.109 ip4:145.239.186.98 ip4:145.239.186.99 ip4:213.215.13.210 ip4:217.115.168.193 ip4:51.254.92.10 ip4:51.254.92.13 ip4:51.254.92.15 ip4:51.254.92.16 ip4:51.254.92.2 ip4:51.254.92.3 ip4:51.254.92.9 include:spf-de.emailsignatures365.com include:spf.ess.barracudanetworks.com include:spf.mailjet.com include:spf.mandrillapp.com include:spf.protection.outlook.com include:spf-relai.relai-smtp.net
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).
  • ✗
    No 'all' mechanism
    SPF record doesn't have an 'all' mechanism. Add -all or ~all at the end of your SPF record.
    #3
  • ✓ 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.secourspopulaire.fr)

Found

Record
v=DMARC1;p=none
Found at
_dmarc.secourspopulaire.fr
TagValueMeaning
vDMARC1Version
pnonePolicy

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.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19

DKIM

pass

Selectors: mail, selector1

Found

Selectors
mail, selector1
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 2048 bitsh=sha256
selector1RSA 2048 bits

Checks

  • ✓ Keys found: mail, selector1 #7
    DKIM keys found for this domain with selectors: mail, selector1
  • ✓ Strong keys #23
    DKIM keys are strong enough: mail: RSA 2048 bits; selector1: RSA 2048 bits.
  • ✓ 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

2 mail servers

Found

PriorityHostRecordsReverse DNS
10d310423a.ess.barracudanetworks.comA 209.222.82.255 A 209.222.82.253 A 209.222.82.252mail.ess.barracuda.com ✓ mail.ess.barracuda.com ✓ mail.ess.barracuda.com ✓
20d310423b.ess.barracudanetworks.comA 209.222.82.252 A 209.222.82.255 A 209.222.82.253mail.ess.barracuda.com ✓ mail.ess.barracuda.com ✓ mail.ess.barracuda.com ✓

Checks

  • ✓ 2 MX records #9
    Found 2 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: d310423a.ess.barracudanetworks.com, d310423b.ess.barracudanetworks.com
    #11
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 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 6 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
d310423a.ess.barracudanetworks.comnone-
d310423b.ess.barracudanetworks.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