SurfaceMap › c › chiemgau24.de

chiemgau24.de

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

Domain & DNS

fail

20 passed 2 warn 2 failed

Areas

iRegistration iDelegation ✗Nameservers ✓SOA !DNSSEC ✗Records

Problems

  • ✗
    Lame delegation
    Nameservers · These nameservers don't answer authoritatively for the zone, so resolvers ignore them: dns.dns1.de (95.130.16.246): NOERROR, authoritative=true; dns.dns2.de (95.130.17.218): NOERROR, authoritative=true.
    #15
  • ✗
    CNAME at the apex
    Records · The zone apex is a CNAME to cbNimgdjmgdbiecj1.chiemgau24.de. A CNAME can't coexist with the SOA and NS records (RFC 1034); use your provider's ALIAS/flattening feature instead.
    #33
  • !
    No EDNS
    Nameservers · These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: dns.dns1.de (95.130.16.246), dns.dns2.de (95.130.17.218).
    #20
  • !
    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 chiemgau24.de ›

Mail

fail

14 passed 3 warn 2 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
  • ✗
    No SPF record
    SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    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 chiemgau24.de ›