# Waitlist Email Deliverability & DNS Checker

> Check your launch domain's public SPF, DMARC, MX, and optional DKIM DNS records via DNS-over-HTTPS. Spot multi-SPF conflicts, >10 lookup limits, and get copyable fixes.

Canonical: https://waitlyze.com/tools/email-deliverability-checker
Last updated: 2026-11-22


The Waitlist Email Deliverability & DNS Checker queries public DNS records for your launch domain via DNS-over-HTTPS to inspect SPF syntax and lookup limits, DMARC policy enforcement, MX mail routing, and optional DKIM selectors. It returns a pass/warn/fail scorecard with copyable DNS TXT fixes before you send launch broadcasts.

## What each DNS authentication check verifies
Major mailbox providers (Gmail, Yahoo, Microsoft) require valid SPF, DKIM, and DMARC alignment for bulk launch broadcasts and confirmation emails.

**Formula / Model:** `Deliverability Readiness (0–100) = SPF (30) + DMARC (30) + MX Records (20) + DKIM Selector (20)`

- **SPF (Sender Policy Framework, 30 pts)**: Confirms exactly one v=spf1 TXT record exists, checks mechanism lookup count (RFC 7208 max 10 DNS lookups), and validates ~all or -all qualifier.
- **DMARC (_dmarc.domain, 30 pts)**: Checks for v=DMARC1, distinguishes monitoring (p=none) from enforcement (p=quarantine / p=reject), and checks for rua aggregate reporting.
- **MX Mail Routing (20 pts)**: Verifies valid MX records exist so reply-to handling and domain legitimacy checks pass cleanly.
- **DKIM Selector Check (20 pts)**: When you enter a selector (such as resend, google, or s1), checks <selector>._domainkey.<domain> for a valid v=DKIM1 public key.

## Worked Example: Sample inspection: acme.com preparing a Resend launch broadcast
Valid MX + single SPF record (4 lookups, ~all), missing _dmarc record.
- **SPF**: Pass (1 record, 4/10 lookups)
- **DMARC**: Fail: missing _dmarc TXT record
- **MX**: Pass (valid mail exchangers)
- **Copyable fix**: v=DMARC1; p=quarantine; rua=mailto:dmarc@acme.com

## How to Interpret Your Result
- **Multiple SPF records detected**: Never publish two separate v=spf1 TXT records: RFC 7208 treats duplicate SPF records as a PermError. Merge all include: mechanisms into one TXT record.
- **SPF lookup count > 10**: Remove unused email vendors from your SPF record or use a dedicated sending subdomain (e.g., mail.yourdomain.com) for launch broadcasts.
- **Start DMARC with p=none, then tighten**: Publish p=none with a rua address first to monitor alignment, then move to p=quarantine or p=reject once your Resend sender is verified.

## Methodology & Privacy
- **Author**: Waitlyze Product Team (Reviewed by Falak Gala)
- **Last updated**: 2026-11-22
- **Privacy**: Only public DNS records for the domain you enter are queried over HTTPS. Queries are rate-limited and not persisted beyond short-lived rate-limit counters.

## Frequently Asked Questions
### Should I send waitlist emails from my root domain or a subdomain?
Using a dedicated subdomain such as mail.yourdomain.com isolates bulk broadcast reputation from your team's corporate inbox and keeps SPF lookup counts clean.

### Why does DKIM require a selector name?
DNS does not allow listing all DKIM keys on a domain. Each email provider publishes its key at <selector>._domainkey.<domain> (for example, 'resend' or 'google').

### How long do DNS updates take to show up here?
Most modern DNS providers (Cloudflare, Route 53, Vercel DNS) propagate TXT changes within 1 to 10 minutes, though older registrars may take longer depending on TTL.

## Related Links
- [Waitlyze Launch Lab](https://waitlyze.com/tools) - All 14 free pre-launch tools
- [Recommended Template](https://waitlyze.com/templates/saas) - Preview matching waitlist layout
