saint-brevin.fr

Checked 22 October 2026, 05:05 UTC · via 8.8.8.8
!Passed with warnings
21 passed 7 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:178.22.2.108 ip4:81.255.218.73 ip4:37.59.244.17 ip4:81.255.218.77 ip4:176.9.183.150 ip4:176.9.183.151 ip4:176.9.183.152 ip4:176.9.183.153 ip4:80.12.242.18 ip4:185.7.39.6 ip4:185.7.39.7 ip4:77.32.154.99 include:spf.mailjet.com include:spf.mailinblack.com include:spf.ouiresa.fr include:spf.sendingservice.net ~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

warn

p=quarantine (_dmarc.saint-brevin.fr)

Found

Record
v=DMARC1;p=quarantine;aspf=s
Found at
_dmarc.saint-brevin.fr
TagValueMeaning
vDMARC1Version
pquarantinePolicy
aspfsSPF alignment (r = relaxed, s = strict)

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ 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.
  • !
    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
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.

DKIM

pass

Selectors: dkim

Found

Selectors
dkim
_domainkey
NOERROR
SelectorKeyFlags
dkimRSA 2048 bits

Checks

  • ✓ Keys found: dkim #7
    DKIM keys found for this domain with selectors: dkim
  • ✓ Strong keys #23
    DKIM keys are strong enough: dkim: 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

3 mail servers

Found

PriorityHostRecordsReverse DNS
5mx26.mailinblack.comA 52.143.171.137no PTR
100mx26b.mailinblack.com(does not resolve)
1000mail.saint-brevin.frA 81.255.218.76mail.saint-brevin.fr ✓

Checks

  • ✓ 3 MX records #9
    Found 3 MX records for this domain.
  • !
    Hosts without IP addresses
    The following MX hosts could not be resolved to IP addresses: mx26b.mailinblack.com
    #10
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: mx26.mailinblack.com, mx26b.mailinblack.com, mail.saint-brevin.fr
    #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.
  • !
    Addresses without reverse DNS
    These MX addresses have no PTR record, which many receivers treat as a spam signal: 52.143.171.137 (mx26.mailinblack.com). Ask your hosting provider to set one.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx26.mailinblack.comnone-
mx26b.mailinblack.comnone-
mail.saint-brevin.frnone-

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