gizmodo.fr

SPF record published

Found

Record

v=spf1 include:_mailcust.gandi.net ?all

DNS lookups

2 of 10

Void lookups

0 of 2

Checks

• ✓ No deprecated ptr mechanism #1

  No ptr mechanism found in SPF record.
• ✓ 2 of 10 DNS lookups #2

  SPF record needs 2 DNS lookups (limit is 10).
• !

  Ends with ?all (neutral)

  SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.

  #3
• ✓ 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.

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

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.
• ✓ All hosts have IPv6 #11

  All MX records resolve to IPv6 addresses.
• ✓ 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 does not match

  The PTR name of these addresses does not resolve back to the same address: 2001:4b98:dc4:8::215 -> spool6.mail.gandi.net, 2001:4b98:dc4:8::217 -> spool8.mail.gandi.net, 2001:4b98:dc4:8::216 -> spool7.mail.gandi.net.

  #30

no MTA-STS · no TLS-RPT · DANE on 0 of 2 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