Are you ready to warm up?

This tool checks the TECHNICAL prerequisites you can see in DNS: a valid, non-permissive SPF record with no PermError; a published DMARC record (p=none is fine to start); DKIM signing on your sending selector; and — for cold or scaled outbound — a dedicated sending subdomain. Passing those means you're technically set up to start. It does not mean your reputation is ready: DNS can't see your sending IP's reputation, complaint and bounce history, or Google Postmaster data — only your live sending data can tell you that.

It depends on what you send. For cold or scaled prospecting, yes — isolate it on a dedicated subdomain so a bad run can't poison your primary mail. For transactional or one-to-one mail, sending from your primary domain is normal and often better for alignment. For marketing it's recommended but not a blocker. This tool asks what you're sending and classifies the subdomain as required, recommended, or optional accordingly — it doesn't treat the root domain as universally “not ready.”

Start low and ease up, and treat the schedule as advance / hold / roll back rather than a fixed calendar: step volume up only after a clean sending window, hold flat if signals wobble, and roll back to your last healthy volume after a bad window. This tool generates a starting shape from your domain's age — a slow start with no abrupt jump into the cap — but the real ramp should follow your live bounce, complaint and deferral signals, not a promise that week N hits your target.

It depends on your infrastructure, not a per-mailbox math trick. On a shared ESP IP pool there's no IP to warm — you ramp the domain and stream while the ESP manages IP reputation. On a dedicated IP you warm the IP, ideally with the ESP's managed warmup (Amazon SES ramps a new IP over ~45 days). If you send from provider mailboxes (Google/Microsoft), warmup is bounded by the provider's own per-account limits — spreading one campaign across many accounts is mailbox rotation, which providers detect and penalize. For legitimate scaled volume, use an ESP with real sending infrastructure rather than more mailboxes.

Suppress hard-bounced addresses immediately. Keep spam complaints under 0.1% and never let them approach 0.3% — that's where Gmail and Yahoo act. Don't wait for a 5% bounce cliff: slow or hold the moment bounces or provider deferrals trend upward, and roll back to your last healthy volume after a bad window. Distinguish hard bounces, soft bounces, rate-limit deferrals, reputation deferrals, complaints and blocks — they mean different things and call for different responses.

Yes. A freshly registered domain has zero sending reputation, so mailbox providers throttle it aggressively. If your domain is under ~90 days old, start at a lower daily volume and stretch the ramp out longer. This tool detects the domain's age and adjusts the starting volume and length automatically.

No — and you shouldn't either. Warmup here means ramping real mail to real, opted-in recipients so your domain earns genuine reputation. Fake-engagement networks, seed-list open/reply bots, and inbox rotation are detected by mailbox providers and set your reputation back. This tool never sends mail; it only reads public DNS.

Yes, fully read-only. It queries public DNS (SPF, DKIM, DMARC, MX) and looks up your domain's registration date via public RDAP over HTTPS — those two, and nothing else. It then reports your technical readiness and a starting ramp shape with infrastructure-specific guidance. It never changes your DNS, never sends mail, and needs no credentials.