Home › Blog › Monitor a 100-Domain Fleet: Auth, Expiry, and Postmaster in One Dashboard
Monitor a 100-Domain Cold Email Fleet: Auth Health, Expiry Dates, and Postmaster in One Dashboard
A fleet you cannot see is a fleet that fails silently: a DKIM record someone fat-fingered, a domain that expired on a card that changed, a Postmaster property nobody registered. Here is the monitoring layer that checks SPF, DKIM, and DMARC across every domain automatically, tracks renewals in one place, and gets Postmaster onto every domain.
Quick Answer: One Inventory, Three Scheduled Checks
Extend your fleet inventory (the CSV from the provisioning pipeline) with three scheduled checks: daily DNS health (SPF singular and under 10 lookups, DKIM resolving, DMARC present, via DoH queries), expiry tracking (registrar APIs + RDAP, alert at 60/30 days without auto-renew), and Postmaster on every domain (plant verification TXTs in bulk via Cloudflare). Red states page Slack; trends wait for the weekly review.
The Dashboard Schema
domain | registrar | expiry | auto_renew
| dns_provider | spf_status | dkim_status
| dmarc_policy | blacklist_hits | postmaster_reg
| campaign/client | inboxes | pool (batch-1/2)
| last_checked
DAILY JOB (DoH queries, ~seconds per domain):
spf: exists once, ≤10 lookups → 🟢/🟡/🔴
dkim: selector resolves, valid → 🟢/🔴
dmarc: exists, policy as set → 🟢/🟡
blacklists: spot rotation → 🟢/🔴
ALERTS: any 🔴 on an active domain → Slack now
WEEKLY: Postmaster spam/reputation, seed grid,
expiry horizon, drift review- •The checks are the same ones our free tools run, looped: SPF with recursive lookup counting, DKIM selector resolution, DMARC policy, blacklists. Use the tools for spot checks and incident drills; the fleet job is for coverage.
- •Expiry via RDAP is free and registrar-agnostic (it is what powers our Domain Expiry Checker); registrar APIs add the auto-renew flag, which is the field that actually predicts disasters.
- •Postmaster registration is a provisioning step, not an afterthought: token TXTs go out with the same pipeline that plants SPF, and the weekly review reads every property's spam rate against the 0.1%/0.3% lines.
- •Tie rows to campaigns and pools so an alert instantly answers the only question that matters at 9am: what is affected and who do I tell.
Why Daily, and Why It Pays
DNS breaks sideways: a teammate cleaning up "unused" TXT records, a registrar migration dropping a zone, a mailbox provider rotating DKIM keys with an email nobody read. Every one of those failures is invisible from the sending side, campaigns keep sending, auth starts failing, placement decays, and the first human-visible symptom is a reply-rate sag two weeks later that looks like a copy problem. A daily check collapses that two-week discovery lag to one morning. The same logic covers expiry: nobody notices a domain lapsing until every inbox on it goes dark, and the resting pool makes it worse, a resting domain can be expired for weeks before its rotation turn exposes it.
Frequently Asked Questions
How do I automatically check SPF, DKIM, and DMARC on many domains?
A scheduled job (n8n, a cron script, or Apps Script) loops your fleet inventory and queries each domain's records over DNS-over-HTTPS: SPF exists, is singular, and is under the 10-lookup limit; the DKIM selector resolves with a valid key; DMARC exists with the intended policy. Each check writes red/yellow/green per domain per day into a sheet or table, and anything non-green alerts to Slack. Daily catches the classic silent failures: a record deleted during unrelated DNS work, a duplicated SPF, or a provider-side DKIM rotation nobody applied.
How do I track domain expiration dates across registrars in one dashboard?
Two sources: registrar APIs (Namecheap, Porkbun, Cloudflare Registrar all expose expiry and auto-renew status) for domains you can query directly, and RDAP as the universal fallback for anything else, the same free protocol our Domain Expiry Checker uses. The dashboard row per domain: registrar, expiry date, auto-renew flag, DNS provider, and which campaigns or client it serves. Alert at 60 and 30 days for anything without auto-renew, and audit the auto-renew payment method quarterly, expired cards are how domains with auto-renew still die.
Can I register domains in Google Postmaster Tools in bulk?
Partially. Adding a property is API-less clicking, but the DNS verification step is automatable: Postmaster hands you a TXT token per domain, and your Cloudflare pipeline can plant all hundred tokens in one run, after which verification is a pass through the UI confirming each. Organize properties in a dedicated Google account (not someone's personal login), and make Postmaster registration a line item in domain provisioning so new domains never skip it.
What should alert immediately versus sit in a weekly review?
Page-now: any auth record disappearing or breaking on an actively sending domain, a blacklist hit, and an expiry inside 30 days without auto-renew. Weekly review: Postmaster spam-rate and reputation trends, seed placement grids, and the slow drifts. The split matters because a monitoring system that pages for everything trains you to ignore it, and one that pages for nothing is decoration.
Is this overkill for a smaller fleet?
Scale the ceremony, keep the checks. At 10 domains the whole system is one sheet and a daily script; at 100 it is the same design with more rows. What does not scale down is skipping it: a single silently broken DKIM record on your best domain costs more replies in a week than the monitoring build takes to ship. Our free checkers cover the one-domain spot checks; the fleet layer is those same checks, looped and scheduled.
Get FREE .com Domains
Prewarmed Inboxes So You Can Send Cold Emails Today
Get Prewarmed & Fresh InboxesPrewarmed & Fresh Inboxes
Google, Microsoft 365 and Azure inboxes with free prewarmed domains and DNS configured before you log in. Prewarmed inboxes send the day they land; every order is delivered within 48 to 72 hours.
Get Prewarmed & Fresh Inboxes