mairie-seysses.fr

Checked 22 October 2026, 04:12 UTC · via 8.8.8.8
!Passed with warnings
26 passed 6 warnings 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:57.131.23.175 include:spf.cloud.vadesecure.com include:spf.brevo.com include:mailgun.org include:spf.hornetsecurity.com include:spf.mailjet.com -all
DNS lookups
9 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=quarantine; pct=100; rua=mailto:informatique@mairie-seysses.fr; ruf=mailto:informatique@mairie-seysses.fr; sp=quarantine; adkim=r; aspf=r
Found at
_dmarc.mairie-seysses.fr
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spquarantineSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:informatique@mairie-seysses.frAggregate report addresses
rufmailto:informatique@mairie-seysses.frFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF 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.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:informatique@mairie-seysses.fr
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: mail, selector1, selector2, s1

Found

Selectors
mail, selector1, selector2, s1
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits
selector1RSA 1024 bits
selector2RSA 2048 bits
s1RSA 1024 bits

Checks

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

4 mail servers

Found

PriorityHostRecordsReverse DNS
10vade-mx-fr01.hornetsecurity.comA 94.100.138.100hsmx01-hz12.hornetsecurity.com ✓
10vade-mx-fr02.hornetsecurity.comA 94.100.138.100hsmx01-hz12.hornetsecurity.com ✓
20vade-mx-eu-fallback01.hornetsecurity.comA 94.100.132.8mx01.hornetsecurity.com ✓
20vade-mx-eu-fallback02.hornetsecurity.comA 94.100.132.8mx01.hornetsecurity.com ✓

Checks

  • ✓ 4 MX records #9
    Found 4 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: vade-mx-fr01.hornetsecurity.com, vade-mx-fr02.hornetsecurity.com, vade-mx-eu-fallback01.hornetsecurity.com, vade-mx-eu-fallback02.hornetsecurity.com
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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 4 MX addresss have a PTR record that resolves back to them.

TLS

warn

MTA-STS testing · TLS-RPT · DANE on 0 of 4 MX hosts

Found

MTA-STS record
v=STSv1; id=20250514
Policy URL
https://mta-sts.mairie-seysses.fr/.well-known/mta-sts.txt
Mode
testing
Allowed MX
mx01.cloud.vadesecure.com, mx02.cloud.vadesecure.com, mx03.cloud.vadesecure.com, mx04.cloud.vadesecure.com
Max age
86400 seconds
TLS-RPT record
v=TLSRPTv1; rua=mailto:informatique@mairie-seysses.fr

DANE (TLSA records)

MX hostTLSADNSSEC
vade-mx-fr01.hornetsecurity.comnone-
vade-mx-fr02.hornetsecurity.comnone-
vade-mx-eu-fallback01.hornetsecurity.comnone-
vade-mx-eu-fallback02.hornetsecurity.comnone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20250514.
  • !
    Policy in testing mode
    With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.
    #33
  • !
    MX hosts missing from policy
    These MX hosts are not listed in the MTA-STS policy (mx: mx01.cloud.vadesecure.com, mx02.cloud.vadesecure.com, mx03.cloud.vadesecure.com, mx04.cloud.vadesecure.com): vade-mx-fr01.hornetsecurity.com, vade-mx-fr02.hornetsecurity.com, vade-mx-eu-fallback01.hornetsecurity.com, vade-mx-eu-fallback02.hornetsecurity.com. This will break delivery once the policy is enforced.
    #34
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:informatique@mairie-seysses.fr
  • 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