zpath.net
Good, with 2 things to fix
zpath.net scored 80/100 (grade B). The main issues are no DKIM key found for the common selectors and no DMARC aggregate report address. Detected senders: Google Workspace.
Checked 2026-10-04 02:20 UTC · fresh check
Set up a DMARC report address
Without a rua address nobody receives aggregate reports, so you cannot see who sends as zpath.net or tell when it is safe to tighten the policy. Adding reporting does not change how receivers treat your mail.
Applies to: _dmarc.zpath.net
- Get an address that collects DMARC aggregate reports: add zpath.net to MailVakt to receive one, or sign up with any DMARC report service. 2. Edit the TXT record at _dmarc.zpath.net and add rua=mailto:<that address>, keeping every other tag (p=reject, sp=reject) as it is. 3. A report service on another domain must authorize zpath.net; most publish that record for you.
All checks
MXCan servers find your inbox?No issues foundPass
Nothing to report.
SPFWho may send as you?SPF ends in softfail (~all)Info
- Info: SPF ends in softfail (~all)
"~all" is common and works well with DMARC. "-all" is stricter; switch when you are sure every sender is listed.
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 zpath.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 zpath.net.
DMARCWhat happens to fakes?No DMARC aggregate report addressNeeds attention
- Warning: No DMARC aggregate report address
Without a rua address you receive no aggregate reports, so you cannot see who sends as your domain or safely tighten the policy.
How to fix this - 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?SPF alignment is unknownInfo
- Info: SPF alignment is unknown
The SPF record of zpath.net authorizes no sender (no +ip4, +ip6, +a, +mx, +exists or +ptr term, include of a record that has one, or +all before all), so SPF never passes and cannot align. That is correct for a domain that sends no mail; otherwise DMARC depends on DKIM alone.
BIMICan inboxes show your logo?No BIMI recordInfo
- Info: No BIMI record
No BIMI record at default._bimi.zpath.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.zpath.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.zpath.net. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.
How to fix this
Other fixes
Enable DKIM for Google Workspaceinstruction
Google Workspace generates the DKIM key for each account, so the exact record must come from Google Workspace. Without DKIM, mail it sends for zpath.net cannot pass DMARC through DKIM.
Applies to: google._domainkey.zpath.net
- In Google Workspace, enable DKIM signing for zpath.net: Generate the key in Admin console > Apps > Gmail > Authenticate email, then publish the TXT record shown there. Publish exactly the record Google Workspace shows (TXT or CNAME) at the host name it gives, then turn signing on. Instructions: https://support.google.com/a/answer/174124
Publish the MTA-STS recordTXT
Tells sending servers that zpath.net publishes an MTA-STS policy at https://mta-sts.zpath.net/.well-known/mta-sts.txt. Change the id whenever the policy file changes.
_mta-sts.zpath.net
Some DNS providers want just “_mta-sts” here.
v=STSv1; id=202610040220
Host the MTA-STS policy filepolicy-file
Serve this file over HTTPS with a valid certificate for mta-sts.zpath.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.zpath.net/.well-known/mta-sts.txt
version: STSv1 mode: testing mx: aspmx.l.google.com mx: alt1.aspmx.l.google.com mx: alt2.aspmx.l.google.com mx: aspmx2.googlemail.com mx: aspmx3.googlemail.com max_age: 604800
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to zpath.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.zpath.net
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@zpath.net, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.zpath.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.zpath.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://zpath.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.zpath.net with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.