puy-de-dome.fr

Checked 22 October 2026, 04:56 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 a mx ip4:212.51.186.201 ip4:51.75.192.135 ip4:4.233.125.199 ip4:57.128.113.111 include:spf.ymlp.com include:spf.mailjet.com include:spf.cap-collectif.com include:spf.cloud.vadesecure.com include:maila.m2.maas360.com include:spf.protection.outlook.com include:spf.hornetsecurity.com -all
DNS lookups
11 of 10
Void lookups
1 of 2
Problem
include:maila.m2.maas360.com does not exist or has no records

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✗
    11 DNS lookups, over the limit of 10
    SPF record needs 11 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record. Problems found: include:maila.m2.maas360.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.puy-de-dome.fr)

Found

Record
v=DMARC1; p=none; rua=mailto:contact@puy-de-dome.fr; ruf=mailto:contact@puy-de-dome.fr; fo=1; adkim=r; aspf=r; pct=100; rf=afrf; ri=86400; sp=none
Found at
_dmarc.puy-de-dome.fr
TagValueMeaning
vDMARC1Version
pnonePolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:contact@puy-de-dome.frAggregate report addresses
rufmailto:contact@puy-de-dome.frFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options
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:contact@puy-de-dome.fr
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: dkim, mail, selector1

Found

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

Checks

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

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

Found

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

  • !
    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