seignosse.fr

Checked 22 October 2026, 05:11 UTC · via 8.8.8.8
✗Problems found
21 passed 5 warnings 1 failed 3 info

SPF

warn

SPF record published

Found

Record
v=spf1 include:_spf.fortimailcloud.com ip4:51.91.239.231 ip4:154.52.13.93 ip4:94.23.222.134 ip4:91.134.161.130 ip4:51.255.13.196 ip4:154.52.13.125 ip4:154.52.13.79 ip4:176.31.200.45 a:smtp1.digital-max.fr ip4:37.59.5.99 ip4:185.111.18.30 include:spf.amazonses.com ~all
DNS lookups
3 of 10
Void lookups
1 of 2
Problem
include:spf.amazonses.com does not exist or has no records

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • !
    3 of 10 DNS lookups, with problems
    SPF record needs 3 DNS lookups (limit is 10). Problems found: include:spf.amazonses.com does not exist or has no records.
    #2
  • ✓ 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.
  • !
    1 void lookup
    1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.
    #26
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

fail

p=none (_dmarc.seignosse.fr)

Found

Record
v=DMARC1; p=none; rua=mailto:rua@dmarc.brevo.com
Found at
_dmarc.seignosse.fr
External report address
mailto:rua@dmarc.brevo.com (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:rua@dmarc.brevo.comAggregate 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:rua@dmarc.brevo.com
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

pass

Selectors: mail

Found

Selectors
mail
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 2048 bitsh=sha256

Checks

  • ✓ Keys found: mail #7
    DKIM keys found for this domain with selectors: mail
  • ✓ Strong keys #23
    DKIM keys are strong enough: mail: 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
10cc-macs-net-1.fortimailcloud.comA 154.52.13.56proxypa34.fortimailcloud.com ✓
20cc-macs-net-2.fortimailcloud.comA 154.52.2.132proxyfra7.fortimailcloud.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: cc-macs-net-1.fortimailcloud.com, cc-macs-net-2.fortimailcloud.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 2 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
cc-macs-net-1.fortimailcloud.comnone-
cc-macs-net-2.fortimailcloud.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