aboutamazon.de

Checked 21 October 2026, 21:27 UTC · via 8.8.8.8
!Passed with warnings
16 passed 3 warnings 0 failed 2 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.aboutamazon.de)

Found

Record
v=DMARC1; p=reject; rua=mailto:report@dmarc.amazon.com; ruf=mailto:report@dmarc.amazon.com
Found at
_dmarc.aboutamazon.de
External report address
mailto:report@dmarc.amazon.com (not authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:report@dmarc.amazon.comAggregate report addresses
rufmailto:report@dmarc.amazon.comFailure report addresses

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.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:report@dmarc.amazon.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • !
    Report address not authorized
    These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:report@dmarc.amazon.com (needs aboutamazon.de._report._dmarc.dmarc.amazon.com). Ask the report provider to publish the record, or check the address.
    #29

DKIM

info

Selectors: default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2

Found

Selectors
default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2
_domainkey
NXDOMAIN
SelectorKeyFlags
defaultrevoked
dkimrevoked
mailrevoked
emailrevoked
k1revoked
selector1revoked
selector2revoked
googlerevoked
zohorevoked
mxrevoked
keyrevoked
mtarevoked
pmrevoked
dkim-smtprevoked
s1revoked
s2revoked

Checks

  • ✓ Keys found: default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2 #7
    DKIM keys found for this domain with selectors: default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2
  • i
    All keys revoked
    All found keys are revoked (empty p=): default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2. 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

warn

No MX records found

Checks

  • !
    No MX records
    No MX records found. If this domain is used for email, add MX records to specify mail servers. If it never receives mail, publish a null MX ("MX 0 .").
    #9
  • ✓ Locked down against spoofing #28
    The domain has no MX records 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