Weekly DNS watchdog
Run this check on a schedule for every domain you send from. When a record breaks, your team hears about it before your open rates do.
Schedule · API · Slack
SPF · DKIM · DMARC · MX · BIMI
Will your emails reach the inbox?
Enter your domain. In about three seconds you get a score out of 100, the exact records you publish today, and what to change so Gmail, Outlook and Yahoo trust your mail.
Or try one:
Asking 1.1.1.1 about your domain…
What gets checked
Five records. 100 points. About three seconds.
-
30 pts
DMARC
Your policy for mail that fails authentication, and the reports that show who sends as you.
-
25 pts
SPF
The list of servers allowed to send as your domain — including the 10-lookup limit most tools miss.
-
25 pts
DKIM
Signing keys under 38 common selectors (or yours), with key strength.
-
15 pts
MX records
Where replies and bounces land, and which provider runs your mail.
-
5 pts
BIMI
The optional logo-in-inbox record for brands that have DMARC enforced.
Run this check while you sleep.
Every check here is also a free JSON API. Drop it into a Pabbly Connect workflow and your domains get audited every week — with an alert only when something breaks.
- Schedule Every Monday, 9:00
- API request GET /api/check
- Filter score is below 80
- Alert Slack, Gmail or WhatsApp
{
"domain": "yourcompany.com",
"score": 72,
"grade": "C",
"verdict": "At risk of the spam folder",
"checks": {
"spf": { "status": "pass", "score": 22 },
"dkim": { "status": "pass", "score": 25 },
"dmarc": { "status": "warn", "score": 12 },
"mx": { "status": "pass", "score": 15 }
}
}
https://email-deliverability-checker-ab8e.pabbly.app/api/check
Three workflows every email sender should have.
Audit every new client
Agencies: when a lead fills your form, check their domain automatically, log the score to Google Sheets and email them their report — a ready-made sales opener.
Typeform · API · Sheets · Gmail
Route bounces and complaints
Catch bounce and spam-complaint webhooks from your email tool and suppress those contacts in your CRM, so bad addresses stop hurting your sender score.
Email service · Filter · CRM
Questions senders ask
What changed with Gmail and Yahoo in 2024?
Since February 2024, anyone sending 5,000 or more emails a day to Gmail or Yahoo addresses must authenticate with both SPF and DKIM, publish a DMARC record (p=none at minimum), offer one-click unsubscribe and keep spam complaints under 0.3%. Smaller senders still need SPF or DKIM. Mail that misses these is junked or rejected.
My SPF passes — why am I still in spam?
SPF on its own is not enough. Receivers look for DKIM signing and a DMARC policy that ties both to the domain in your From address. Content, list quality and complaint rates matter too, but missing authentication is the most common — and the easiest — thing to fix.
What is a DKIM selector, and how do I find mine?
DKIM keys are published under a name your provider chooses, like google._domainkey or selector1._domainkey. We try 38 common ones automatically. To find yours, open any email you sent, show the original message and look for s= in the DKIM-Signature header. Enter it under 'Add a DKIM selector'.
Can I use this check inside my own automations?
Yes. Every check is available as a free JSON API at /api/check?domain=yourdomain.com. Call it from a Pabbly Connect API step, filter on the score and send the result anywhere.
What do you store?
Only the domain you checked, its score and the time — so we can see which checks people run. Lookups go through Cloudflare's public 1.1.1.1 resolver, and we never send email to your domain.