adsafeprotected.com
At risk, with 5 things to fix
adsafeprotected.com scored 22/100 (grade F). The main issues are no SPF record and MX host does not resolve, plus 3 more.
Checked 2026-10-04 02:06 UTC · fresh check
Publish an SPF record
No sending service was detected, so this record says no server may send as adsafeprotected.com. If you do send mail, add your provider's include before publishing.
adsafeprotected.com
Some DNS providers want “@” here instead of the full domain.
v=spf1 -all
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?MX host does not resolveFailing
- Fail: MX host does not resolve
mx1.integralads.com, mx2.integralads.com has no A or AAAA record, so senders cannot deliver to it. Fix the hostname or remove the MX record.
SPFWho may send as you?No SPF recordFailing
- Fail: No SPF record
adsafeprotected.com publishes no TXT record starting with "v=spf1", so receivers cannot tell which servers may send mail for it. Publish one SPF record listing every service that sends as adsafeprotected.com.
How to fix this
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 adsafeprotected.com 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 adsafeprotected.com.
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?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 adsafeprotected.com under the selectors we probed, and adkim=s requires the signing d= domain to equal adsafeprotected.com 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.adsafeprotected.com. 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.adsafeprotected.com. 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.adsafeprotected.com. 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 adsafeprotected.com or tell when it is safe to tighten the policy. Adding reporting does not change how receivers treat your mail.
Applies to: _dmarc.adsafeprotected.com
- Get an address that collects DMARC aggregate reports: add adsafeprotected.com to MailVakt to receive one, or sign up with any DMARC report service. 2. Edit the TXT record at _dmarc.adsafeprotected.com and add rua=mailto:<that address>, keeping every other tag (p=reject) as it is. 3. A report service on another domain must authorize adsafeprotected.com; most publish that record for you.
Publish the MTA-STS recordTXT
Tells sending servers that adsafeprotected.com publishes an MTA-STS policy at https://mta-sts.adsafeprotected.com/.well-known/mta-sts.txt. Change the id whenever the policy file changes.
_mta-sts.adsafeprotected.com
Some DNS providers want just “_mta-sts” here.
v=STSv1; id=202610040206
Host the MTA-STS policy filepolicy-file
Serve this file over HTTPS with a valid certificate for mta-sts.adsafeprotected.com. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.
https://mta-sts.adsafeprotected.com/.well-known/mta-sts.txt
version: STSv1 mode: testing mx: mx1.integralads.com mx: mx2.integralads.com max_age: 604800
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to adsafeprotected.com, 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.adsafeprotected.com
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@adsafeprotected.com, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.adsafeprotected.com 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.adsafeprotected.com
- 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://adsafeprotected.com/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.adsafeprotected.com with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.