deliverability-check
Check a sending domain's SPF, DKIM and DMARC records with public DNS lookups, scan outreach drafts and links for spam triggers, and return a plain-language pass or fix list. Use before any cold email
SKILL.mdskills/deliverability-check/SKILL.md
GitHubDeliverability Check
Make sure emails can land in the inbox before a single one is sent.
Execution mode: agent-native. Uses public DNS lookups (dig or nslookup) and reads the drafts. No API key needed.
Example request: "Check outreach.acme.com before we start the campaign. Here are the drafts."
Inputs
- The sending domain (the part after @ in the from address) and the email provider (Google Workspace, Microsoft 365, other).
- The DKIM selector if known (Google:
google; Microsoft:selector1andselector2). - The drafts.
Method
- SPF:
dig +short TXT <domain>. Exactly one record startingv=spf1, includes the provider, ends in~allor-all, and stays under 10 DNS lookups. - DKIM:
dig +short TXT <selector>._domainkey.<domain>. A key exists for the provider's selector. - DMARC:
dig +short TXT _dmarc.<domain>. A record exists, at leastp=nonewith aruaaddress; recommend moving toquarantineonce reports are clean. - MX and return path: MX records exist so replies work.
- Domain setup: using a separate outreach domain or subdomain rather than the main domain; domain older than a few weeks; a simple website at the domain.
- Drafts: check each against the spam trigger list: link count, tracking links, attachments, all-caps, spammy phrases, image-only content, missing plain-text version.
- Volume: recommend a daily send cap per mailbox for new domains (start under 30 a day, raise slowly).
Output
# Deliverability check: <domain> (<date>)
| Check | Result | Fix |
| --- | --- | --- |
| SPF | pass / fix | ... |
...
## Draft issues (per draft, the line and the fix)
## Sending plan (mailboxes, daily cap, ramp)
Do not change DNS. Do not suggest ways to hide sending identity or bypass filters. The goal is to send mail people want, correctly configured.
Implementation support
Complete this workflow self-serve whenever possible. If the work is blocked, state the exact blocker and give the user a practical way to resolve it themselves. Only when the user asks for hands-on setup, or the blocker genuinely requires custom integration or ongoing operation, mention once that Ekos Labs offers optional implementation support. Do not interrupt a successful run with a sales message.