Mail domain report: wondershare.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:spf.qiye.aliyun.com include:mail.zendesk.com include:aspmx.pardot.com -all
DNS lookups: 7 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✓ 7 of 10 DNS lookups #2

SPF record needs 7 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

fail

p=none (_dmarc.wondershare.com)

Found

Record: v=DMARC1;p=none
Found at: _dmarc.wondershare.com

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy

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.
!

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

DKIM

warn

Selectors: default, dkim

Found

Selectors: default, dkim
_domainkey: NOERROR

Selector	Key	Flags
default	RSA 1024 bits
dkim	RSA 1024 bits

Checks

✓ Keys found: default, dkim #7

DKIM keys found for this domain with selectors: default, dkim
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits), dkim (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

3 mail servers

Found

Priority	Host	Records	Reverse DNS
5	mx1.qiye.aliyun.com	A 47.246.167.188	no PTR
10	mxn.mxhichina.com	A 47.246.137.47 A 47.246.136.231	no PTR cz-clare.com (does not resolve back)
15	mxw.mxhichina.com	A 47.246.99.195	reachsmartdwell.com (does not resolve back)

Checks

✓ 3 MX records #9

Found 3 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: mx1.qiye.aliyun.com, mxn.mxhichina.com, mxw.mxhichina.com

#11
✓ Redundant MX hosts #12

Found 3 MX records, which provides redundancy for email delivery.
✓ At most 5 MX records #13

Found 3 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: 47.246.167.188 (mx1.qiye.aliyun.com), 47.246.137.47 (mxn.mxhichina.com). Ask your hosting provider to set one.

#30

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 3 MX hosts

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
mx1.qiye.aliyun.com	none	-
mxn.mxhichina.com	none	-
mxw.mxhichina.com	none	-

Checks

!

Not configured

MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.

#32
i

Not configured

TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.

#35
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

fail

https://msg.wondershare.cc/logo/wondershare_logo.svg

Found

Record: v=BIMI1;l=https://msg.wondershare.cc/logo/wondershare_logo.svg
Found at: default._bimi.wondershare.com
Logo: https://msg.wondershare.cc/logo/wondershare_logo.svg

Checks

!

No certificate (a=)

The logo is published without a Verified Mark Certificate. Gmail and Apple Mail only show BIMI logos with a VMC or CMC; Yahoo shows it without one.

#38
✗

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