stadetoulousain.fr

SPF record published

Found

Record

v=spf1 mx include:spf.mailjet.com include:25046424.spf10.hubspotemail.net ptr ip4:217.108.145.157 ip4:91.121.109.198 include:spf.protection.outlook.com ip4:52.232.104.46 ip4:52.178.100.47 ip4:31.210.2.21 ip4:31.210.6.21 ~all

DNS lookups

5 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
• ✓ 5 of 10 DNS lookups #2

  SPF record needs 5 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=quarantine (_dmarc.stadetoulousain.fr)

Found

Record

v=DMARC1; p=quarantine; pct=100; rua=mailto:spam@stadetoulousain.fr

Found at

_dmarc.stadetoulousain.fr

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:spam@stadetoulousain.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.

Selectors: dkim, selector1, google

Found

Selectors

dkim, selector1, google

_domainkey

NOERROR

Checks

• ✓ Keys found: dkim, selector1, google #7

  DKIM keys found for this domain with selectors: dkim, selector1, google
• !

  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.

1 mail server

Found

Checks

• ✓ 1 MX record #9

  Found 1 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.
• !

  Single MX host, no backup

  Only one MX record found. For better email reliability, consider adding at least one backup MX server.

  #12
• ✓ At most 5 MX records #13

  Found 1 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 8 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