chanteloup-les-vignes.fr

SPF record published

Found

Record

v=spf1 a mx a:webmail.chanteloup-les-vignes.fr a:mail.chanteloup-les-vignes.fr ptr:mail.chanteloup-les-vignes.fr ptr:mail2026.chanteloup-les-vignes.fr ip4:176.162.160.133 ip4:195.96.152.150 include:spf.cloud.vadesecure.com include:spf.interstis.fr -all

DNS lookups

8 of 10

Void lookups

0 of 2

Checks

• !

  Uses deprecated ptr mechanism

  The ptr mechanism in SPF records is deprecated due to performance issues and should be avoided.

  #1
• ✓ 8 of 10 DNS lookups #2

  SPF record needs 8 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.

p=reject (_dmarc.chanteloup-les-vignes.fr)

Found

Record

v=DMARC1;p=reject;pct=100;sp=none;aspf=s;

Found at

_dmarc.chanteloup-les-vignes.fr

Checks

• ✓ Policy: reject #4

  DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
• ✓ 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
• !

  Subdomains unprotected (sp=none)

  DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.

  #20

No keys found under the checked selectors

Found

Selectors

None found

_domainkey

NOERROR

Checks

• !

  No key under common selectors

  The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.

  #7

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

2 mail servers

Found

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: antispam.vpc2.osc.interstis.fr, antispam.vpc2.osc.interstis.fr

  #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 4 MX addresss have a PTR record that resolves back to them.

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

Found

DANE (TLSA records)

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