dbfk.de

SPF record published

Found

Record

v=spf1 ip4:212.87.44.36/30 ip4:212.87.44.44/30 ip4:85.158.1.64/27 ip4:87.106.15.197 include:_spf.kundenserver.de include:_spf.zimpel.de include:spf.protection.outlook.com include:_spf_eucentral1.prod.hydra.sophos.com include:vpn-rz.dbfk.de a:mail01.mailservices-sc.de include:spf-de.emailsignatures365.com a:mail02.mailservices-sc.de a:mail01.mailservices-fw.de a:mail02.mailservices-fw.de -all

DNS lookups

10 of 10

Void lookups

1 of 2

Problem

include:vpn-rz.dbfk.de does not exist or has no records

Checks

• ✓ No deprecated ptr mechanism #1

  No ptr mechanism found in SPF record.
• !

  10 of 10 DNS lookups, with problems

  SPF record needs 10 DNS lookups (limit is 10). Problems found: include:vpn-rz.dbfk.de does not exist or has no records.

  #2
• ✓ 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.
• !

  1 void lookup

  1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.

  #26
• ✓ No overly broad IP ranges #27

  All ip4/ip6 ranges are narrow enough.

p=quarantine (_dmarc.dbfk.de)

Found

Record

v=DMARC1; p=quarantine; rua=mailto:dmarc@dbfk.de

Found at

_dmarc.dbfk.de

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:dmarc@dbfk.de
• ✓ Subdomain policy: quarantine #20

  Subdomains are covered by policy 'quarantine'.
• ✓ Report addresses in own domain #29

  All report addresses are in your own organizational domain.

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

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: mx-01-eu-central-1.prod.hydra.sophos.com, mx-02-eu-central-1.prod.hydra.sophos.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