dnspod.net
Poor, with 3 things to fix
dnspod.net scored 58/100 (grade D). The main issues are no DMARC record and no DKIM key found for the common selectors, plus 1 more.
Checked 2026-10-04 02:08 UTC · fresh check
Publish a DMARC record
Starts DMARC in monitoring mode (p=none), so you can see who sends as dnspod.net before enforcing a policy. Move to quarantine once the reports show only your own services.
_dmarc.dnspod.net
Some DNS providers want just “_dmarc” here.
v=DMARC1; p=none; adkim=r; aspf=r
How to apply it
- Sign in where your domain’s DNS is managed. This is often where you bought the domain, such as Cloudflare, GoDaddy or Namecheap.
- Add a new TXT record with the name and value above.
- Save, then come back and re-check. DNS changes can take up to a few hours to show.
All checks
MXCan servers find your inbox?No issues foundPass
Nothing to report.
SPFWho may send as you?Some SPF lookups could not be completedNeeds attention
- Warning: Some SPF lookups could not be completed
1 address lookup needed to evaluate the SPF record of dnspod.net failed or timed out (for example MX mail-sl.weisuo.net for mx:mail-sl.weisuo.net: SERVFAIL), so whether those terms match a sender is unknown. Try again later; if it persists, check the nameservers involved.
DKIMAre your emails signed?No DKIM key found for the common selectorsNeeds attention
- Warning: No DKIM key found for the common selectors
None of the 47 selectors probed under dnspod.net publish a DKIM key. DNS cannot list selectors, so a key under a custom selector may exist: find the s= value in the DKIM-Signature header of a message you sent and check that selector. If DKIM is not set up, enable it at each service that sends mail for dnspod.net.
DMARCWhat happens to fakes?No DMARC recordFailing
- Fail: No DMARC record
There is no v=DMARC1 TXT record at _dmarc.dnspod.net. Without DMARC, receivers have no policy for mail that fails SPF and DKIM, and Gmail and Yahoo require one for bulk senders. Start with p=none and a rua address to collect reports.
How to fix this
AlignmentDoes it match your From?SPF alignment is unknownInfo
- Info: SPF alignment is unknown
Part of the SPF evaluation for dnspod.net failed to resolve or timed out (spf.lookup-failed), so whether SPF can pass and align is unknown. Try again later.
BIMICan inboxes show your logo?No BIMI recordInfo
- Info: No BIMI record
No BIMI record at default._bimi.dnspod.net. BIMI is optional: it shows your logo next to your mail in supporting inboxes once DMARC is enforced.
How to fix this
MTA-STSIs mail to you encrypted?No MTA-STS recordInfo
- Info: No MTA-STS record
No MTA-STS record at _mta-sts.dnspod.net. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.
How to fix this
TLS-RPTWill you hear about failures?No TLS-RPT recordInfo
- Info: No TLS-RPT record
No TLS reporting record at _smtp._tls.dnspod.net. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.
How to fix this
Other fixes
Publish the MTA-STS recordTXT
Tells sending servers that dnspod.net publishes an MTA-STS policy at https://mta-sts.dnspod.net/.well-known/mta-sts.txt. Change the id whenever the policy file changes.
_mta-sts.dnspod.net
Some DNS providers want just “_mta-sts” here.
v=STSv1; id=202610040208
Host the MTA-STS policy filepolicy-file
Serve this file over HTTPS with a valid certificate for mta-sts.dnspod.net. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.
https://mta-sts.dnspod.net/.well-known/mta-sts.txt
version: STSv1 mode: testing mx: mxbiz1.qq.com mx: mxbiz2.qq.com max_age: 604800
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to dnspod.net, which you need before enforcing MTA-STS. The address must accept TLS reports; a DMARC report address does not necessarily do so.
Applies to: _smtp._tls.dnspod.net
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@dnspod.net, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.dnspod.net with the value v=TLSRPTv1; rua=mailto:<that address>.
Prepare BIMIinstruction
BIMI shows your logo next to messages in supporting inboxes, but only for mail that passes DMARC under an enforced policy.
Applies to: default._bimi.dnspod.net
- Enforce DMARC first: p=quarantine or p=reject at 100% (no pct below 100). 2. Convert your logo to an SVG Tiny PS file and host it over HTTPS, for example https://dnspod.net/bimi/logo.svg. 3. For Gmail and Apple Mail, obtain a VMC or CMC certificate for the logo. 4. Publish a TXT record at default._bimi.dnspod.net with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.