henkel.de

Checked 21 October 2026, 22:50 UTC · via 8.8.8.8
!Passed with warnings
14 passed 3 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 -all
DNS lookups
0 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 0 of 10 DNS lookups #2
    SPF record needs 0 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=reject (_dmarc.henkel.de)

Found

Record
v=DMARC1; p=reject; sp=none; aspf=s; adkim=s
Found at
_dmarc.henkel.de
TagValueMeaning
vDMARC1Version
prejectPolicy
spnoneSubdomain policy
adkimsDKIM alignment (r = relaxed, s = strict)
aspfsSPF alignment (r = relaxed, s = strict)

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ 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.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    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

DKIM

info

Selectors: dkim

Found

Selectors
dkim
_domainkey
NOERROR
SelectorKeyFlags
dkimrevoked

Checks

  • ✓ Keys found: dkim #7
    DKIM keys found for this domain with selectors: dkim
  • i
    All keys revoked
    All found keys are revoked (empty p=): dkim. That is fine if this domain no longer signs mail.
    #24

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

info

Null MX: domain accepts no mail

Checks

  • i
    Null MX: accepts no mail
    Domain publishes a null MX (RFC 7505): it explicitly accepts no email.
    #9
  • ✓ Locked down against spoofing #28
    The domain publishes a null MX and publishes SPF "v=spf1 -all" and DMARC p=reject, so nobody can send mail as this domain.

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