saoneetloire71.fr

p=quarantine (_dmarc.saoneetloire71.fr)

Found

Record

v=DMARC1; p=quarantine; sp=quarantine; pct=100; adkim=r; aspf=r; rua=mailto:bzn7c3au@ag.eu.dmarcian.com,mailto:rua@saoneetloire71.fr; ruf=mailto:bzn7c3au@fr.eu.dmarcian.com,mailto:ruf@saoneetloire71.fr; rf=afrf; ri=86400; fo=1;

Found at

_dmarc.saoneetloire71.fr

External report address

mailto:bzn7c3au@ag.eu.dmarcian.com (authorized)

External report address

mailto:bzn7c3au@fr.eu.dmarcian.com (authorized)

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:bzn7c3au@ag.eu.dmarcian.com, mailto:rua@saoneetloire71.fr
• ✓ Subdomain policy: quarantine #20

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

  Report addresses in other domains have published their authorization.

Selectors: default, dkim, mail, email, k1, selector1, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2

Found

Selectors

default, dkim, mail, email, k1, selector1, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2

_domainkey

NOERROR

Checks

• ✓ Keys found: default, dkim, mail, email, k1, selector1, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2 #7

  DKIM keys found for this domain with selectors: default, dkim, mail, email, k1, selector1, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2
• !

  1024-bit DKIM key

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

  #23
• ✓ No problematic flags #24

  No test mode or SHA-1-only keys. Revoked keys (empty p=), which is fine after a key rotation: default, dkim, email, k1, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2.

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: mx1.hc1359-86.eu.iphmx.com, mx2.hc1359-86.eu.iphmx.com

  #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 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