**TL;DR:** Launch a new sending domain without burning it: authenticate, warm, clean the list, seed-test, and monitor, in that order. Authenticate: domain auth (SPF/DKIM/DMARC) validated in the console before any real volume. Clean the list before the first send: remove stale addresses, typos, and anyone without consent.

## The fix

Goal: a new domain reaching the inbox from day one.

Step 1. Authenticate: domain auth (SPF/DKIM/DMARC) validated in the console before any real volume.

Step 2. Clean the list before the first send: remove stale addresses, typos, and anyone without consent. A new domain's first impression is its most important.

Step 3. Warm gradually on a dedicated IP, starting with the most engaged recipients.

Step 4. Seed-test every campaign to major providers for the first weeks; check spam-folder placement, not just delivery.

Step 5. Monitor the loop from day one: Event Webhook for bounces, spamreports, and deferrals; suppress hard bounces and spam reporters immediately.

Step 6. Keep the identity clean: every message identifies the sender, carries the physical address, and offers a working opt-out.

Verify: seed tests land in inboxes, spamreport rates stay near zero, and deferrals stay low through the ramp. Pitfall: importing an old uncleaned list on day one undoes all of the above.

## When to use this

- This covers exactly what the title says: SendGrid new-domain deliverability launch checklist.
- You are setting this up for the first time, or auditing an existing setup.
- You want the key gotchas in one place before you start.

## When not to use this

- You are doing a different workflow with SendGrid; these steps are specific to the title above.
- You need the full reference docs; this is the short path, not the manual.

## Compatibility

- Not pinned to a specific version; follows current SendGrid behavior.