DNS setup

Set up cold email domains so readiness checks can pass before launch.

Domain setup is not just buying domains. Operators need authentication records, mailbox routing, conservative capacity assumptions, and a clear path to readiness evidence.

Verify routing and authentication first

A domain should have the basic records needed for mail routing and authentication before inboxes are counted as usable. MX shows where mail receives, SPF identifies authorized senders, DKIM signs mail, and DMARC defines how receivers evaluate alignment.

Use the DNS checker to inspect MX, SPF, DKIM, and DMARC posture.
Use one SPF record and avoid lookup-limit drift.
Publish DKIM selectors for the systems that will actually sign mail.

Connect records to readiness

Clean DNS is necessary but not sufficient. GTM readiness also looks at managed MTA assignment, SMTP host and username metadata, IMAP host and username metadata, stored encrypted credentials, hashes, and recent smoke-test results.

Fix DNS before running readiness checks at scale.
Treat missing SMTP or IMAP metadata as export blockers.
Keep customer-facing output redacted when a domain or inbox fails checks.

Use capacity limits conservatively

A domain with valid DNS can still be overloaded. Use the domain calculator to plan how many domains are needed for the expected prospect volume, touches, and send days, then keep launch approval tied to readiness and seed-placement evidence.

Common questions

Does a passing DNS check mean the domain is ready for prospect traffic?

No. DNS checks are advisory. First prospect traffic should still wait for SMTP and IMAP readiness, seed-placement evidence, and launch-gate approval.

Should DMARC start at reject for a new domain?

Not automatically. DMARC policy should be rolled out after legitimate sources are authenticated and aligned. The public generators provide planning guidance, not a guarantee.

Next step

Start with an advisory domain authentication check before readiness review.

Run a DNS check