Yes - this domain is set up to receive email.
Fix your custom domain email setup.
Check MX, SPF, DKIM, and DMARC records for Google Workspace, Cloudflare, Vercel, Namecheap, Microsoft 365, and more.
example.com
6/1/2026, 9:00:00 AM
What this means for your email
At risk - mail from this domain is likely to be junked or rejected until this is fixed.
The current setup lets anyone on the internet send email that claims to be from your domain.
Authentication is the part of junk filtering you control in DNS. Sending habits and content also matter - no tool can guarantee the inbox.
Exact fixes
The current setup lets anyone on the internet send email that claims to be from your domain.
For Google Workspace, keep include:_spf.google.com and replace +all with ~all while testing or -all after every sender is confirmed.
Read the SPF guideFix step-by-stepAuto-fix on CloudflareAdvanced details
v=spf1 include:_spf.google.com +allSpoofing protection is in watch-only mode; nothing is blocked yet, and that can be fine while testing.
After reviewing reports, move gradually from p=none to p=quarantine and then p=reject.
Read the DMARC guideAdvanced details
v=DMARC1; p=none; rua=mailto:dmarc@example.comYour website and your DNS settings appear to live at different companies; that is normal, just edit records at the right one.
Add MX, SPF, DKIM, and DMARC records at the active DNS host, not necessarily where the website is hosted or where the domain was purchased.
Advanced details
Cloudflare DNS | Vercel HostingRaw DNS evidence
{
"ns": [
"ada.ns.cloudflare.com",
"ben.ns.cloudflare.com"
],
"mx": [
{
"priority": 1,
"exchange": "aspmx.l.google.com"
},
{
"priority": 5,
"exchange": "alt1.aspmx.l.google.com"
}
],
"txt": [
{
"name": "@",
"value": "v=spf1 include:_spf.google.com +all"
},
{
"name": "_dmarc",
"value": "v=DMARC1; p=none; rua=mailto:dmarc@example.com"
},
{
"name": "google._domainkey",
"value": "v=DKIM1; k=rsa; p=abc"
}
],
"cname": {
"www": [
"cname.vercel-dns.com"
]
},
"a": {
"@": [
"76.76.21.21"
]
},
"aaaa": {}
}1 / 10
SPF lookup count: 1 / 10 - within the SPF limit.
Lookup-causing mechanisms
- include _spf.google.com - 1 direct, 0 nested
Advanced email security
Advanced protections and reporting - optional, not required for basic email to work, and they do not change or prove inbox placement.
No BIMI record found. BIMI is optional branding - email works without it.
Details
- BIMI points supporting mailbox providers at a brand logo. It is not required for email delivery.
No MTA-STS record found. MTA-STS is optional - email works without it.
Details
- MTA-STS asks sending servers to require TLS when delivering to this domain. It needs both a _mta-sts TXT record and an https policy file.
No TLS-RPT record found. TLS-RPT is optional reporting - email works without it.
Details
- TLS-RPT asks sending servers to report TLS delivery problems to an address you choose. It does not change how mail is delivered.
Common problems
What the app checks
Who it is for
Built for people who need exact DNS fixes without learning every mail-authentication acronym first.
Practical next steps
Each report separates DNS hosting, website hosting, and email hosting so you know where to add or change records.
View guides