snafu.de

Checked 22 October 2026, 00:22 UTC · via 8.8.8.8
!Passed with warnings
26 passed 6 warnings 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx ip4:84.23.254.128/25 ip6:2001:1560:3:255::/64 ip6:2001:1560:3:254::/64 ip4:213.73.113.34/32 ip6:2001:1560:a000:2:50:ff:fe00:27ed/128 include:_spf.snafu.de -all
DNS lookups
5 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 5 of 10 DNS lookups #2
    SPF record needs 5 DNS lookups (limit is 10).
  • ✓ Ends with -all #3
    SPF record properly uses -all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

warn

p=quarantine (_dmarc.snafu.de)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:dmarcreport@team.snafu.de; ruf=mailto:dmarcreport@team.snafu.de; sp=none; fo=0:1:s;
Found at
_dmarc.snafu.de
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spnoneSubdomain policy
ruamailto:dmarcreport@team.snafu.deAggregate report addresses
rufmailto:dmarcreport@team.snafu.deFailure report addresses
fo0:1:sFailure reporting options

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarcreport@team.snafu.de
  • !
    Subdomains unprotected (sp=none)
    DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: mail

Found

Selectors
mail
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits

Checks

  • ✓ Keys found: mail #7
    DKIM keys found for this domain with selectors: mail
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mailin.snafu.deA 84.23.254.51service.snafu.de (does not resolve back)
50secondary.snafu.deA 84.23.254.17no PTR

Checks

  • ✓ 2 MX records #9
    Found 2 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: mailin.snafu.de, secondary.snafu.de
    #11
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 MX records, which is within the recommended range (1-5).
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • !
    Addresses without reverse DNS
    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

TLS

info

MTA-STS enforce · TLS-RPT · DANE on 0 of 2 MX hosts

Found

MTA-STS record
v=STSv1;id=202602181430
Policy URL
https://mta-sts.snafu.de/.well-known/mta-sts.txt
Mode
enforce
Allowed MX
mailin.snafu.de, secondary.snafu.de
Max age
15552000 seconds
TLS-RPT record
v=TLSRPTv1;rua=mailto:dmarcreport@team.snafu.de

DANE (TLSA records)

MX hostTLSADNSSEC
mailin.snafu.denone-
secondary.snafu.denone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 202602181430.
  • ✓ Policy enforced #33
    The MTA-STS policy is enforced and cached for 4320h0m0s.
  • ✓ All MX hosts covered #34
    Every MX host matches an mx: line of the MTA-STS policy.
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:dmarcreport@team.snafu.de
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38