cispa.de

p=reject (_dmarc.cispa.de)

Found

Record

v=DMARC1; p=reject; rua=mailto:dmarc@gwdg.de; ruf=mailto:dmarc-ruf@gwdg.de; pct=10; adkim=r; aspf=r

Found at

_dmarc.cispa.de

External report address

mailto:dmarc@gwdg.de (not authorized)

External report address

mailto:dmarc-ruf@gwdg.de (not 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 10% of mail

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

  #18
• ✓ Aggregate reports enabled #19

  Aggregate reports are sent to: mailto:dmarc@gwdg.de
• ✓ Subdomain policy: reject #20

  Subdomains are covered by policy 'reject'.
• !

  Report address not authorized

  These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc@gwdg.de (needs cispa.de._report._dmarc.gwdg.de); mailto:dmarc-ruf@gwdg.de (needs cispa.de._report._dmarc.gwdg.de). Ask the report provider to publish the record, or check the address.

  #29

No keys found under the checked selectors

Found

Selectors

None found

_domainkey

NOERROR

Checks

• !

  No key under common selectors

  The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.

  #7

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

3 mail servers

Found

Checks

• ✓ 3 MX records #9

  Found 3 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: a1232.mx.srv.dfn.de, b1232.mx.srv.dfn.de, c1232.mx.srv.dfn.de

  #11
• ✓ Redundant MX hosts #12

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

  Found 3 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 3 MX addresss have a PTR record that resolves back to them.

no MTA-STS · no TLS-RPT · DANE on 3 of 3 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
• !

  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
• ✓ DANE on all MX hosts #36

  All 3 MX hosts publish DNSSEC-validated TLSA records.