wpguardian.io
Poor, with 3 things to fix
wpguardian.io scored 57/100 (grade D). The main issues are DMARC policy is none and no DKIM key found for the common selectors, plus 2 more. Detected senders: HubSpot.
Checked 2026-10-04 02:15 UTC · fresh check
Strengthen the DMARC policy
Quarantines 25% of mail that fails DMARC, a safe first step: check the reports for legitimate senders that fail before going further. There is no report address yet: set one up first (see the DMARC reporting fix) so you can confirm your legitimate mail passes before enforcing.
_dmarc.wpguardian.io
Some DNS providers want just “_dmarc” here.
v=DMARC1; p=quarantine; pct=25; adkim=r; aspf=r
v=DMARC1; p=none;
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.
- Find the existing TXT record with that name and replace its value.
- 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?Mail relies on implicit A recordNeeds attention
- Warning: Mail relies on implicit A record
wpguardian.io has no MX records, so senders fall back to its A/AAAA address (RFC 5321 implicit MX). Publish an explicit MX record, or a null MX ("0 .") if the domain should not receive mail.
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 wpguardian.io 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 wpguardian.io.
DMARCWhat happens to fakes?DMARC policy is noneNeeds attention
- Warning: DMARC policy is none
A none policy only monitors: mail that fails DMARC is still delivered, so anyone can spoof the domain. Once reports show your legitimate senders pass, move to quarantine and then reject.
How to fix this - 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
AlignmentDoes it match your From?SPF alignment depends on a custom Return-PathInfo
- Info: SPF alignment depends on a custom Return-Path
This is a heuristic. Your SPF record only authorizes third-party senders (1784136.spf01.hubspotemail.net). By default they bounce from their own Return-Path domain, and SPF then passes for that domain, not wpguardian.io. Even relaxed alignment needs the Return-Path's organizational domain to be wpguardian.io, so set up a custom Return-Path (bounce) domain under wpguardian.io with each provider, and sign with DKIM as wpguardian.io.
BIMICan inboxes show your logo?No BIMI recordInfo
- Info: No BIMI record
No BIMI record at default._bimi.wpguardian.io. 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.wpguardian.io. 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.wpguardian.io. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.
How to fix this
Other fixes
Set up a DMARC report addressinstruction
Without a rua address nobody receives aggregate reports, so you cannot see who sends as wpguardian.io or tell when it is safe to tighten the policy. Adding reporting does not change how receivers treat your mail.
Applies to: _dmarc.wpguardian.io
- Get an address that collects DMARC aggregate reports: add wpguardian.io to MailVakt to receive one, or sign up with any DMARC report service. 2. Edit the TXT record at _dmarc.wpguardian.io and add rua=mailto:<that address>, keeping every other tag (p=none) as it is. 3. A report service on another domain must authorize wpguardian.io; most publish that record for you.
Enable DKIM for HubSpotinstruction
HubSpot generates the DKIM key for each account, so the exact record must come from HubSpot. Without DKIM, mail it sends for wpguardian.io cannot pass DMARC through DKIM.
Applies to: hs1._domainkey.wpguardian.io
- In HubSpot, enable DKIM signing for wpguardian.io: account-specific: copy the CNAME/TXT from the HubSpot dashboard. Publish exactly the record HubSpot shows (TXT or CNAME) at the host name it gives, then turn signing on. Instructions: https://knowledge.hubspot.com/domains-and-urls/connect-your-email-sending-domain
Enable DKIM for HubSpotinstruction
HubSpot generates the DKIM key for each account, so the exact record must come from HubSpot. Without DKIM, mail it sends for wpguardian.io cannot pass DMARC through DKIM.
Applies to: hs2._domainkey.wpguardian.io
- In HubSpot, enable DKIM signing for wpguardian.io: account-specific: copy the CNAME/TXT from the HubSpot dashboard. Publish exactly the record HubSpot shows (TXT or CNAME) at the host name it gives, then turn signing on. Instructions: https://knowledge.hubspot.com/domains-and-urls/connect-your-email-sending-domain
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to wpguardian.io, 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.wpguardian.io
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@wpguardian.io, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.wpguardian.io 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.wpguardian.io
- 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://wpguardian.io/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.wpguardian.io with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.