SurfaceMap › d › ddr-museum.de

ddr-museum.de

Checked 2026-10-21 22:12 UTC · first added 2026-10-21
✗Problems found Score 53 of 100

Domain & DNS

warn

22 passed 3 warn 0 failed

Areas

iRegistration !Delegation !Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns.jpberlin.de (glue 91.198.250.3, 2001:67c:2050:1::53:1, zone 91.198.250.3, 2001:67c:2050:103:53:0:1:1); ns3.jpberlin.de (glue 88.198.52.15, zone 88.198.52.15, 2a01:4f8:221:4381::1). Update the glue at your registrar.
    #8
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns.jpberlin.de: "9.18.33"; ns2.jpberlin.de: "9.18.33"; ns3.jpberlin.de: "PowerDNS Authoritative Server 4.3.1". 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 ddr-museum.de ›

Mail

fail

15 passed 6 warn 2 failed

Areas

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

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • ✗
    TLSA records not DNSSEC-validated
    TLS · These MX hosts publish TLSA records that the resolver could not validate with DNSSEC, so senders ignore them or, if validation fails, may refuse delivery: mx1.heinlein-support.de, mx2.heinlein-support.de.
    #36
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    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: mx1.heinlein-support.de, mx2.heinlein-support.de, mx03.mailhost.online
    #11
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 94.135.231.162 (mx03.mailhost.online). Ask your hosting provider to set one.
    #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
  • !
    Not configured
    TLS · 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

Recent checks

✗

Full report

Mail report for ddr-museum.de ›