Waitlist Email Deliverability & DNS Checker
Verify SPF, DMARC, MX, and optional DKIM DNS records before sending launch emails.
Deliverability score
60/100
Grade D
SPF
Pass
30/30 pts
DMARC
Fix
0/30 pts
MX
Pass
20/20 pts
SPF (Sender Policy Framework)
PassValid single SPF record (2 top-level DNS lookup mechanisms; nested includes can add lookups, enforced qualifier).
v=spf1 include:amazonses.com include:_spf.google.com ~allNo changes required. Verify your transactional provider is included.
DMARC (_dmarc policy)
FailMissing DMARC record. Gmail and Yahoo require DMARC for bulk launch broadcasts.
No TXT record at _dmarc.acme.examplePublish a starter DMARC TXT record at _dmarc.acme.example to enable alignment.
TXT _dmarc.acme.example v=DMARC1; p=quarantine; rua=mailto:dmarc@acme.exampleMX (Mail Exchange Routing)
Pass2 usable MX record(s) found for replies and bounce handling.
10 aspmx.l.google.com.
20 alt1.aspmx.l.google.com.Mail routing is active.
DKIM (resend._domainkey)
WarnA DKIM TXT record was found at resend._domainkey.acme.example, but its key material was not cryptographically verified.
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC...Confirm the key with your email provider and verify a signed test message before relying on DKIM alignment.
Pre-launch sending warm-up checklist
- Connect and verify your Resend sending domain inside Waitlyze before enabling confirmations.
- Send verification emails first (high open & click engagement builds positive domain reputation).
- Use a dedicated subdomain (mail.yourdomain.com) if sending large launch-day broadcasts.
- Send launch broadcasts only to double-opt-in verified subscribers who explicitly consented.
- Include a clear one-click unsubscribe link (handled automatically by Waitlyze broadcasts).
Ready to turn this into a live waitlist?
Carries your inspected domain into Waitlyze setup. Custom sender emails use a connected verified Resend sender.
Build and run your waitlist in Waitlyze, free up to 100 signups
Hosted launch page or embed, verified referral links, consent-aware email, and audience analytics. No credit card required.
What each DNS authentication check verifies
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.
- 1
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.
- 2
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.
- 3
MX Mail Routing (20 pts)
Verifies valid MX records exist so reply-to handling and domain legitimacy checks pass cleanly.
Formula & scoring model
Deliverability Readiness (0–100) = SPF (30) + DMARC (30) + MX Records (20) + DKIM Selector (20)
Major mailbox providers (Gmail, Yahoo, Microsoft) require valid SPF, DKIM, and DMARC alignment for bulk launch broadcasts and confirmation emails.
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
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.
- Author
- Waitlyze Product Team
- Reviewed by
- Falak Gala
- Last materially updated
- Version
- v1.0
Sources & changelog
- RFC 7208 (SPF), RFC 6376 (DKIM), RFC 7489 (DMARC)
- Cloudflare DNS-over-HTTPS JSON API (cloudflare-dns.com)
v1.0: Public DoH inspection for SPF, DMARC, MX, and optional DKIM selectors with copyable remediation.
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.
Continue your launch setup
Guide
Pre-Launch Waitlist Email Sequence: Cadence, Timing & Goals
When to email your waitlist from signup confirmation to launch day: exact cadence, consent rules, and what each pre-launch message should accomplish.
Guide
7 Waitlist Email Templates (Copy-Paste Examples for 2026)
Seven copy-paste waitlist email templates from welcome and referral reminders to launch day, with subject lines and timing you can reuse for your launch.
Recommended template
Free SaaS Beta Waitlist Landing Page Template
A screenshot-led beta page with proof and answers.