SurfaceMap › s › snafu.de

snafu.de

Checked 2026-10-22 00:22 UTC · first added 2026-10-21
!Passed with warnings Score 76 of 100

Domain & DNS

warn

21 passed 2 warn 0 failed

Areas

iRegistration !Delegation iNameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    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 snafu.de ›

Mail

warn

26 passed 6 warn 0 failed

Areas

✓SPF !DMARC !DKIM !DNSSEC !MX iTLS iBIMI

Problems

  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    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: mailin.snafu.de, secondary.snafu.de
    #11
  • !
    Subdomains unprotected (sp=none)
    DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 84.23.254.17 (secondary.snafu.de). Ask your hosting provider to set one.
    #30

Recent checks

!

Full report

Mail report for snafu.de ›