dkms.de

SPF record published

Found

Record

v=spf1 mx ip4:40.92.0.0/15 ip4:52.100.0.0/15 ip4:40.107.0.0/16 ip4:52.102.0.0/16 ip4:104.47.0.0/17 ip4:52.103.0.0/17 ip4:204.220.160.0/19 ip4:143.55.224.0/20 ip4:159.112.240.0/20 ip4:159.135.224.0/20 ip4:161.38.192.0/20 ip4:198.244.48.0/20 ip4:69.72.32.0/20 ip4:46.183.40.0/21 ip4:80.241.56.0/21 ip4:87.253.232.0/21 ip4:166.78.68.0/22 ip4:185.189.236.0/22 include:_spf.salesforce.com include:spf.protection.outlook.com include:_spf.jpberlin.de include:_spf.zimpel.de ~all

DNS lookups

6 of 10

Void lookups

0 of 2

Checks

• ✓ No deprecated ptr mechanism #1

  No ptr mechanism found in SPF record.
• ✓ 6 of 10 DNS lookups #2

  SPF record needs 6 DNS lookups (limit is 10).
• ✓ 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.
• ✓ No void lookups #26

  All include/redirect targets exist.
• !

  Broad IP ranges

  These ranges authorize tens of thousands of addresses or more: ip4:40.92.0.0/15, ip4:52.100.0.0/15. Check that you really own and send from all of them.

  #27

p=quarantine (_dmarc.dkms.de)

Found

Record

v=DMARC1; p=quarantine; rua=mailto:x2wm6vhw@rua.eu.dmarcmanager.app; ruf=mailto:x2wm6vhw@ruf.eu.dmarcmanager.app; fo=1

Found at

_dmarc.dkms.de

External report address

mailto:x2wm6vhw@rua.eu.dmarcmanager.app (authorized)

External report address

mailto:x2wm6vhw@ruf.eu.dmarcmanager.app (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:x2wm6vhw@rua.eu.dmarcmanager.app
• ✓ Subdomain policy: quarantine #20

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

  Report addresses in other domains have published their authorization.

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: mx01.dkms.de, mx02.dkms.de

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