lescrous.fr

SPF record published

Found

Record

v=spf1 include:spf.protection.outlook.com include:spf.mailing.crous-rouen.fr include:spf.vtech.fr include:spf.iroquois.fr a:mxo-out6.utc.fr -all

DNS lookups

6 of 10

Void lookups

1 of 2

Problem

include:spf.mailing.crous-rouen.fr does not exist or has no records

Checks

• ✓ No deprecated ptr mechanism #1

  No ptr mechanism found in SPF record.
• !

  6 of 10 DNS lookups, with problems

  SPF record needs 6 DNS lookups (limit is 10). Problems found: include:spf.mailing.crous-rouen.fr 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.

p=reject (_dmarc.lescrous.fr)

Found

Record

v=DMARC1;p=reject;pct=20;adkim=r;aspf=r;fo=0;ri=3600;rua=mailto:dmarc@mxmail.nuonet.fr;ruf=mailto:dmarc.ruf@mxmail.nuonet.fr

Found at

_dmarc.lescrous.fr

External report address

mailto:dmarc@mxmail.nuonet.fr (authorized)

External report address

mailto:dmarc.ruf@mxmail.nuonet.fr (authorized)

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 20% of mail

  DMARC policy only applies to 20% of failing mail (pct=20). Raise pct to 100 once you are confident in your setup.

  #18
• ✓ Aggregate reports enabled #19

  Aggregate reports are sent to: mailto:dmarc@mxmail.nuonet.fr
• ✓ Subdomain policy: reject #20

  Subdomains are covered by policy 'reject'.
• ✓ External report addresses authorized #29

  Report addresses in other domains have published their authorization.

Selectors: selector2

Found

Selectors

selector2

_domainkey

NOERROR

Checks

• ✓ Keys found: selector2 #7

  DKIM keys found for this domain with selectors: selector2
• !

  1024-bit DKIM key

  1024-bit RSA keys are the minimum and are considered weak today: selector2 (1024 bits). Rotate to a 2048-bit key.

  #23
• ✓ No problematic flags #24

  No keys in test mode, revoked, or limited to SHA-1.

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

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