SurfaceMap › d › ddnss.de

ddnss.de

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

Domain & DNS

warn

18 passed 5 warn 0 failed

Areas

iRegistration !Delegation iNameservers !SOA !DNSSEC !Records

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: ns2.ddnss.de. ns1.ddnss.de, ns2.ddnss.de, ns3.ddnss.de report NS ns1.ddnss.de ns2.ddnss.de ns3.ddnss.de.
    #7
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns3.ddnss.de (glue 78.31.65.41, 2001:4ba0:cafe:15a2::1, zone 188.65.149.12, 2a00:1aa0:1000:12::1). Update the glue at your registrar.
    #8
  • !
    Unusual SOA timers
    SOA · retry 2h should be shorter than refresh 1h. Current values: refresh 1h, retry 2h, expire 7d, negative TTL 30m.
    #23
  • !
    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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), AAAA (1m), MX (1m), NS (10s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 10s; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for ddnss.de ›

Mail

fail

17 passed 5 warn 1 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
  • !
    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: mail.mc-p.de
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    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
  • !
    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 ddnss.de ›