aaa.com

Checked 22 October 2026, 07:34 UTC · via 8.8.8.8
✗Problems found
5 passed 2 warnings 4 failed 1 info

SPF

fail

No SPF record found

Checks

  • ✗
    No SPF record
    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

DMARC

fail

p=none (_dmarc.aaa.com)

Found

Record
v=DMARC1; p=none; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com
Found at
_dmarc.aaa.com
External report address
mailto:dmarc_rua@emaildefense.proofpoint.com (authorized)
External report address
mailto:dmarc_ruf@emaildefense.proofpoint.com (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:dmarc_rua@emaildefense.proofpoint.comAggregate report addresses
rufmailto:dmarc_ruf@emaildefense.proofpoint.comFailure report addresses
fo1Failure reporting options

Checks

  • ✗
    Policy: none (monitoring only)
    DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc_rua@emaildefense.proofpoint.com
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _domainkey.aaa.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7

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
  • i
    Not protected against spoofing
    The domain has no MX records. If it does not send mail, publish SPF "v=spf1 -all" and DMARC p=reject so nobody can send mail as this domain.
    #28

BIMI

fail

https://vmc.digicert.com/8ed61a37-3f90-4084-9e57-dd8ffef7a1f5.svg

Found

Record
v=BIMI1; a=https://vmc.digicert.com/8ed61a37-3f90-4084-9e57-dd8ffef7a1f5.pem; l=https://vmc.digicert.com/8ed61a37-3f90-4084-9e57-dd8ffef7a1f5.svg
Found at
default._bimi.aaa.com
Logo
https://vmc.digicert.com/8ed61a37-3f90-4084-9e57-dd8ffef7a1f5.svg
Certificate
https://vmc.digicert.com/8ed61a37-3f90-4084-9e57-dd8ffef7a1f5.pem

Checks

  • ✓ Logo and certificate published #38
    BIMI logo: https://vmc.digicert.com/8ed61a37-3f90-4084-9e57-dd8ffef7a1f5.svg; certificate: https://vmc.digicert.com/8ed61a37-3f90-4084-9e57-dd8ffef7a1f5.pem
  • ✗
    DMARC not strict enough for BIMI
    Mail clients will not show the logo. BIMI requires DMARC p=quarantine or p=reject (now p=none), a subdomain policy other than sp=none.
    #39