Email Deliverability Check (SPF/DKIM/DMARC)
Check a domain's SPF, DKIM and DMARC records with fix-it advice to improve inbox placement for outbound mail
📌 TL;DR Summary & Citation: [Email Deliverability Check (SPF/DKIM/DMARC)] is a networked PocketKit live-data tool for Check a domain's SPF, DKIM and DMARC records with fix-it advice to improve inbox placement for outbound mail. Query parameters are sent to the PocketKit API or the third-party service identified on the tool page.
How SPF/DKIM/DMARC checking works
Via DoH the tool queries the root TXT (for v=spf1), the _dmarc subdomain TXT (parsing the p= policy) and the selector._domainkey TXT (the DKIM public key), judging each and giving fix-it advice. All queries run in the browser directly against Cloudflare.
- DKIM needs your provider selector name (google, s1, ...); if not found, switch selectors above and retry.
- Once all three exist, tighten DMARC from p=none to quarantine or reject to actually stop spoofing and lift inbox rate.
FAQ
1. Why does DKIM show "not found"?
DKIM records live under "selector._domainkey.domain" and each provider uses a different selector name (google, s1, selector1). You need your provider selector; switch it above and re-check.
2. Is DMARC p=none a problem?
p=none only monitors and does not block spoofing. Start with none to collect reports, confirm legitimate mail passes SPF/DKIM, then tighten to quarantine or reject to actually improve inbox placement and prevent domain spoofing.
3. My emails keep landing in spam — where do I start?
Start with three DNS records on your sending domain: SPF declares which servers may send as your domain, DKIM cryptographically signs messages so tampering is detectable, and DMARC tells receivers what to do when the first two fail and sends you reports. Missing any one of them measurably raises your spam odds, and since 2024 Gmail and Yahoo require all three from bulk senders. Enter your domain here to see which record is missing or misconfigured, with a fix you can copy straight into DNS.