SurfaceMap › p › pennergame.de

pennergame.de

Checked 2026-10-21 23:42 UTC · first added 2026-10-21
✗Problems found Score 57 of 100

Domain & DNS

warn

20 passed 2 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: pranab.ns.cloudflare.com: "2026.10.2"; sonia.ns.cloudflare.com: "2026.10.2". Hide or replace the version string.
    #17
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Recent checks

!

Full report

Domain & DNS report for pennergame.de ›

Mail

fail

17 passed 9 warn 1 failed

Areas

!SPF ✗DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    6 of 10 DNS lookups, with problems
    SPF · SPF record needs 6 DNS lookups (limit is 10). Problems found: include:spf.remintrex.com does not exist or has no records.
    #2
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · 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
  • !
    More than 5 MX records
    MX · Found 7 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • !
    Hosts are CNAMEs
    MX · 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
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    1 void lookup
    SPF · 1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.
    #26
  • !
    Reverse DNS does not match
    MX · 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
  • !
    Not configured
    TLS · 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

Recent checks

✗

Full report

Mail report for pennergame.de ›