ville-gravelines.fr

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

SPF

pass

SPF record published

Found

Record
v=spf1 mx ip4:185.30.208.146 ip4:178.32.1.63 ip4:46.29.124.150 ip4:212.129.23.233 ip4:185.66.232.173 ip4:185.66.232.175 ip4:37.235.94.136 ip4:185.161.45.19 ip4:185.161.45.18 ip4:51.210.212.123 ip4:137.74.255.53 ip4:87.98.185.114 ip4:176.149.235.226 ip4:212.51.188.166 ip4:91.134.252.178 include:spf.protection.outlook.com include:spf.hornetsecurity.com include:_spf.afi-sa.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.ville-gravelines.fr)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:dmarc@maihost.ville-gravelines.fr; fo=1; pct=25; adkim=r; aspf=r
Found at
_dmarc.ville-gravelines.fr
TagValueMeaning
vDMARC1Version
pquarantinePolicy
pct25Percentage of mail the policy applies to
ruamailto:dmarc@maihost.ville-gravelines.frAggregate report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options

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 25% of mail
    DMARC policy only applies to 25% of failing mail (pct=25). Raise pct to 100 once you are confident in your setup.
    #18
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc@maihost.ville-gravelines.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

pass

Selectors: selector1, selector2

Found

Selectors
selector1, selector2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits
selector2RSA 2048 bits

Checks

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

4 mail servers

Found

PriorityHostRecordsReverse DNS
1vade-mx-fr01.hornetsecurity.comA 94.100.138.100hsmx01-hz12.hornetsecurity.com ✓
1vade-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