agglo-pau.fr

p=quarantine (_dmarc.agglo-pau.fr)

Found

Record

v=DMARC1;p=quarantine;pct=100;adkim=s;aspf=s;sp=quarantine;ruf=mailto:dmarc@agglo-pau.fr;fo=1;rua=mailto:re+aagopp8czwx@dmarc.postmarkapp.com, mailto:dmarc@agglo-pau.fr

Found at

_dmarc.agglo-pau.fr

External report address

mailto:re+aagopp8czwx@dmarc.postmarkapp.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:re+aagopp8czwx@dmarc.postmarkapp.com, mailto:dmarc@agglo-pau.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: mail, selector2

Found

Selectors

mail, selector2

_domainkey

NOERROR

Checks

• ✓ Keys found: mail, selector2 #7

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

  1024-bit DKIM key

  1024-bit RSA keys are the minimum and are considered weak today: mail (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

4 mail servers

Found

Checks

• ✓ 4 MX records #9

  Found 4 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: vade-mx-fr01.hornetsecurity.com, vade-mx-fr02.hornetsecurity.com, vade-mx-eu-fallback01.hornetsecurity.com, vade-mx-eu-fallback02.hornetsecurity.com

  #11
• ✓ Redundant MX hosts #12

  Found 4 MX records, which provides redundancy for email delivery.
• ✓ At most 5 MX records #13

  Found 4 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.

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

Found

MTA-STS record

v=STSv1; id=202608261230;

Policy URL

https://mta-sts.agglo-pau.fr/.well-known/mta-sts.txt

Mode

enforce

Allowed MX

vade-mx-fr01.hornetsecurity.com, vade-mx-fr02.hornetsecurity.com, vade-mx-eu-fallback01.hornetsecurity.com, vade-mx-eu-fallback02.hornetsecurity.com

Max age

604800 seconds

DANE (TLSA records)

Checks

• ✓ Record published #32

  MTA-STS record found with id 202608261230.
• ✓ Policy enforced #33

  The MTA-STS policy is enforced and cached for 168h0m0s.
• ✓ All MX hosts covered #34

  Every MX host matches an mx: line of the MTA-STS policy.
• !

  Not configured

  MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".

  #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