zuerich.com

p=quarantine (_dmarc.zuerich.com)

Found

Record

v=DMARC1; p=quarantine; sp=none; pct=100; ri=86400; rua=mailto:15ad42f72965443e8c2764ef1b1d6594@dmarc-reports.cloudflare.net,mailto:dmarc-reports@zuerich.com; ruf=mailto:dmarc-reports@zuerich.com; fo=1

Found at

_dmarc.zuerich.com

External report address

mailto:15ad42f72965443e8c2764ef1b1d6594@dmarc-reports.cloudflare.net (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:15ad42f72965443e8c2764ef1b1d6594@dmarc-reports.cloudflare.net, mailto:dmarc-reports@zuerich.com
• !

  Subdomains unprotected (sp=none)

  DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.

  #20
• ✓ External report addresses authorized #29

  Report addresses in other domains have published their authorization.

Selectors: selector1, selector2

Found

Selectors

selector1, selector2

_domainkey

NOERROR

Checks

• ✓ Keys found: selector1, selector2 #7

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

  1024-bit DKIM key

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

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: d303118.a.ess.de.barracudanetworks.com, d303118.b.ess.de.barracudanetworks.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 6 MX addresss have a PTR record that resolves back to them.

MTA-STS testing · no TLS-RPT · DANE on 0 of 2 MX hosts

Found

MTA-STS record

v=STSv1; id=17678766234ZT;

Policy URL

https://mta-sts.zuerich.com/.well-known/mta-sts.txt

Mode

testing

Allowed MX

d303118.a.ess.de.barracudanetworks.com, d303118.b.ess.de.barracudanetworks.com

Max age

604800 seconds

DANE (TLSA records)

Checks

• ✓ Record published #32

  MTA-STS record found with id 17678766234ZT.
• !

  Policy in testing mode

  With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.

  #33
• ✓ 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