pennergame.de

SPF record published

Found

Record

v=spf1 include:spf.remintrex.com a mx mx:pennermail.de include:aspmx.googlemail.com ~all

DNS lookups

6 of 10

Void lookups

1 of 2

Problem

include:spf.remintrex.com does not exist or has no records

Checks

• ✓ No deprecated ptr mechanism #1

  No ptr mechanism found in SPF record.
• !

  6 of 10 DNS lookups, with problems

  SPF record needs 6 DNS lookups (limit is 10). Problems found: include:spf.remintrex.com 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.

Selectors: default

Found

Selectors

default

_domainkey

NOERROR

Checks

• ✓ Keys found: default #7

  DKIM keys found for this domain with selectors: default
• !

  1024-bit DKIM key

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

7 mail servers

Found

Checks

• ✓ 7 MX records #9

  Found 7 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: mail2.pennermail.de, mail1.pennermail.de, mail3.pennermail.de, mail.pennermail.de, mail4.pennermail.de

  #11
• ✓ Redundant MX hosts #12

  Found 7 MX records, which provides redundancy for email delivery.
• !

  More than 5 MX records

  Found 7 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.

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

  Hosts are CNAMEs

  MX records must point to a host name with A/AAAA records, not to a CNAME: mail2.pennermail.de -> cname-112370.park-my-domain.net, mail1.pennermail.de -> cname-112370.park-my-domain.net, mail3.pennermail.de -> cname-112370.park-my-domain.net, mail.pennermail.de -> cname-112370.park-my-domain.net, mail4.pennermail.de -> cname-112370.park-my-domain.net

  #22
• !

  Reverse DNS does not match

  The PTR name of these addresses does not resolve back to the same address: 157.90.33.74 -> v2.park-my-domain.net, 157.90.33.73 -> v1.park-my-domain.net, 157.90.33.73 -> v1.park-my-domain.net, 157.90.33.74 -> v2.park-my-domain.net, 157.90.33.73 -> v1.park-my-domain.net, 157.90.33.74 -> v2.park-my-domain.net, 157.90.33.73 -> v1.park-my-domain.net, 157.90.33.74 -> v2.park-my-domain.net, 157.90.33.73 -> v1.park-my-domain.net, 157.90.33.74 -> v2.park-my-domain.net.

  #30

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