zenecn.net
At risk, with 4 things to fix
zenecn.net scored 32/100 (grade F). The main issues are no MX records and no DKIM key found for the common selectors, plus 2 more.
Checked 2026-10-04 02:20 UTC · fresh check
All checks
MXCan servers find your inbox?No MX recordsFailing
- Fail: No MX records
zenecn.net has no MX records and no A/AAAA fallback, so it cannot receive mail, including bounces and DMARC reports. Publish an MX record pointing at your mail provider.
SPFWho may send as you?No issues foundPass
Nothing to report.
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 zenecn.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 zenecn.net.
DMARCWhat happens to fakes?External DMARC report address is not authorizedNeeds attention
- Warning: External DMARC report address is not authorized
Reports go to zenlayer.com, which is outside zenecn.net. RFC 7489 requires that domain to publish a valid v=DMARC1 TXT record at zenecn.net._report._dmarc.zenlayer.com; without it receivers will not send you aggregate reports. Your report provider normally publishes this for you.
- Info: DMARC uses strict alignment
With adkim=s or aspf=s the DKIM d= domain or the bounce domain must equal the From domain exactly; a subdomain is not enough. Third-party senders that sign or bounce from a subdomain (or their own domain) will then fail DMARC unless they are configured to use your exact domain.
AlignmentDoes it match your From?DKIM alignment is unlikely under adkim=sNeeds attention
- Warning: DKIM alignment is unlikely under adkim=s
This is a heuristic. No DKIM key was found at zenecn.net under the selectors we probed, and adkim=s requires the signing d= domain to equal zenecn.net exactly. If your mail is signed with a provider's domain or a subdomain, DKIM will not align. A key may exist under a selector we did not try; send a test message to confirm.
BIMICan inboxes show your logo?No BIMI recordInfo
- Info: No BIMI record
No BIMI record at default._bimi.zenecn.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.zenecn.net. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.
TLS-RPTWill you hear about failures?No TLS-RPT recordInfo
- Info: No TLS-RPT record
No TLS reporting record at _smtp._tls.zenecn.net. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.
How to fix this
How to fix it
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to zenecn.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.zenecn.net
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@zenecn.net, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.zenecn.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.zenecn.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://zenecn.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.zenecn.net with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.