SendGrid Warm Up: Domain, SMTP and IP Setup

For SendGrid warm up, authenticate the sending domain first, then start around 10–20 real outbound emails per day unless your SendGrid limits are lower. If you skip DNS alignment or jump volume, Gmail, Yahoo and Outlook can treat the sender as unknown or risky. This guide gives the records, SMTP setup, warm-up schedule and monitoring checks.

SendGrid can send high volume, but it does not create reputation for you. A new domain, subdomain or dedicated IP still needs predictable sending before heavier campaigns. If you need mailbox-level placement data, pair SendGrid with a receiving inbox and BobWork Email Warm-up, which supports SendGrid SMTP credentials plus an IMAP inbox.

This guide assumes you send from a domain or subdomain through SendGrid. It covers transactional-style sending and cautious outbound patterns. It does not replace SendGrid’s current plan limits, policy rules, suppression settings or compliance requirements.

What must be set first?

Start with domain authentication. Do not warm up an unauthenticated SendGrid sender unless you are only testing inside your own team. Authentication tells mailbox providers that SendGrid is allowed to send for your domain.

In SendGrid, go to Settings → Sender Authentication → Authenticate Your Domain. SendGrid asks for your DNS host, domain and automated security preference. The usual setup creates CNAME records for DKIM and return-path alignment. Use the exact hostnames and values shown inside your account.

SendGrid’s primary source is the Twilio SendGrid domain authentication documentation. Use that over any blog post if the interface changes.

You should also have SPF and DMARC on the sending domain. With SendGrid domain authentication, SendGrid normally handles the SPF alignment it needs through the generated DNS records. Your domain can still use SPF for other services, but keep only one SPF TXT record per domain.

DMARC should exist before you ramp. Many teams start warm-up with p=none so they can monitor authentication results without rejecting legitimate mail. Tighten the policy later, after you know every valid sender for the domain.

Use a subdomain if your main domain reputation matters. For example, send from mail.example.com or news.example.com, not the root domain. Keep the visible From address, authenticated domain and reply handling consistent.

For DNS checks, use our SPF checker, DKIM checker and DMARC checker. Check the exact domain or subdomain used in the visible From address.

Which SMTP settings does SendGrid use?

SendGrid SMTP uses an API key, not your account password. This is a common setup mistake.

Go to Settings → API Keys → Create API Key. Give the key a clear name, such as warmup-sendgrid-domain or outbound-mailer. Grant the smallest permissions your sending setup needs. For SMTP sending, Mail Send is the core permission.

Use these SMTP values:

SendGrid documents this in its SMTP API key guide. The username is literally apikey. Do not use your SendGrid account email address as the SMTP username.

Store the API key when you create it. SendGrid will not show the full value again. If you lose it, create a new key and revoke the old one.

Do not share one API key across every product, environment and domain. Separate keys make revocation safer. They also help you identify which system caused a volume spike, bounce issue or policy problem.

Before warm-up, send a few internal test emails. Open the full headers in Gmail, Yahoo or another mailbox. SPF, DKIM and DMARC should pass. The visible From domain should match the domain you plan to build reputation for.

What are you warming?

SendGrid warm-up can mean domain warm-up, IP warm-up or mailbox-level warm-up. Keep them separate or you will optimize the wrong layer.

Domain warm-up builds reputation for the domain or subdomain in your From address. Mailbox providers watch whether recipients accept, ignore, delete, report or reply to mail from that identity.

IP warm-up applies when you use a dedicated IP address. You increase traffic through that IP gradually so receiving providers see a predictable sending pattern.

Mailbox-level warm-up uses real receiving inboxes to send, receive, reply and detect spam placement. It is common in cold outbound because it measures inbox behavior directly.

SendGrid’s automated IP warm-up is for dedicated IPs. It controls traffic sent through the dedicated IP according to SendGrid’s system. Read the current SendGrid IP warm-up documentation before enabling it.

If you use shared IPs, you usually cannot warm the IP yourself. You can still warm the domain by sending low, steady, wanted mail with correct authentication.

Do not assume a dedicated IP is safer. A dedicated IP starts with little or no reputation. If your volume is low or inconsistent, a shared IP can sometimes be easier. If your volume is high and stable, a dedicated IP gives more control.

For the mailbox side, read what an email warm-up network does. Inbox placement data is different from a platform’s sending allowance.

What sendgrid warm up schedule is safe?

Use a boring ramp. Mailbox providers should see a sender that behaves predictably.

For a new domain, plan 3–4 weeks. For an existing domain with good sending history, use at least 14 days. If the domain has previous spam issues, treat it like a new reputation and move slower.

This starting schedule is for one SendGrid sending domain. Adjust downward if your SendGrid plan, policy or account limits are lower. Increase only after delivery is stable, bounces stay low and complaints do not rise.

These numbers are cautious outbound guidance, not SendGrid’s maximum technical capacity. SendGrid may allow more sending than your domain reputation can safely handle. Reputation usually fails before the platform limit.

Send more only when the previous step is clean. If bounces rise, fix the list. If complaints rise, fix targeting and consent. If spam placement rises, pause or step back.

Do not send the same template to every recipient. Avoid link-heavy first emails, image-only messages, URL shorteners and misleading subjects. Plain text or simple HTML is safer while you establish reputation.

Send during business hours for the audience where possible. Spread messages across the day. A sharp batch looks less natural than steady office-hour sending.

Which signals should you watch?

There are two kinds of limits.

The first is SendGrid’s account, plan, rate and policy limit. Check your SendGrid account and current SendGrid documentation. Do not rely on a number copied from an old article.

The second is reputation capacity. This is not shown as one number. You infer it from bounces, blocks, spam placement, replies, unsubscribes and complaints.

Google’s sender guidance says to keep spam complaint rates below 0.1% and avoid reaching 0.3%. Use the current Google email sender guidelines as a primary source, especially if you send to Gmail or Google Workspace users.

Watch these signals daily during warm-up:

Keep SendGrid suppression handling active for bounces, blocks, spam reports and unsubscribes unless you have a specific reason and understand the consequence.

Warm-up cannot repair a bad list. If recipients did not expect your message, the domain will show it eventually. Authentication helps providers identify you. It does not make unwanted mail wanted.

If you send from multiple domains, warm each one separately. Reputation does not fully transfer. If you add a new subdomain, treat it as a new sender until it proves otherwise.

How does mailbox warm-up work?

SendGrid is a sending platform. It is not usually the receiving inbox where warm-up replies land. For mailbox-level warm-up, you need SendGrid SMTP for sending and a real inbox that can receive over IMAP.

This differs from Gmail or Zoho warm-up. With Gmail, the mailbox can send and receive. With SendGrid, the sending side is SendGrid SMTP. The receiving side is usually Google Workspace, Zoho, Yahoo, iCloud, Lark or another IMAP provider.

BobWork Email Warm-up supports this setup: SendGrid SMTP credentials for sending plus the receiving inbox over IMAP. The free pool starts at 3 emails/day, adds 2 per day and caps at 30/day unless you edit the cap. It uses a shared warm-up network by default, or a private pool per account if you prefer.

Keep the receiving mailbox real. It should receive prospect replies and system messages. Its reply-to behavior should match your campaign setup.

BobWork only touches warm-up mail carrying the engine’s hidden header, or a known warm-up subject for specific provider routes. Real mail is not read, moved or answered. Warm-up mail found in Spam is moved to Inbox, marked read, labelled Warm-up and archived after 24 hours.

You still need to read campaign replies yourself. A warm-up tool does not handle objections, unsubscribes or support messages.

For the exact BobWork ramp, read the engine strategy. For a broader daily plan, use the email warm-up schedule guide.

Do this now

Use this checklist before you send more than a small test batch. Each step depends on the one before it.

Do not skip verification. The worst warm-up plan is one that sends for a week before anyone checks headers.

If DNS is not passing, fix DNS. If the list is bouncing, fix the list. If recipients complain, fix targeting. Sending more will not solve those problems.

A safe SendGrid domain warm-up has a simple shape: authenticated domain, valid SMTP key, small daily sends, no sudden jumps and daily monitoring. The hard part is resisting the urge to scale as soon as the first test works.

If you also run cold outreach from normal mailboxes, compare this with Gmail warm-up, Zoho warm-up or Amazon SES warm-up. The setup changes by provider, but the reputation logic is similar.

For SendGrid, keep warm-up traffic and campaign traffic consistent. Do not warm one domain and switch to another for the actual campaign. Do not authenticate one domain and send from a different visible From identity.

If a mailbox or sender crosses a 5% warm-up spam rate, pause it for a few days. Resume at a lower level after placement improves. If a domain repeatedly lands in spam, check DNS, list source, content and prior reputation before blaming SendGrid.

When you are ready to add mailbox-level warm-up, connect SendGrid SMTP and a receiving IMAP inbox in the free warm-up tool. It is free, needs no credit card, supports up to 20 mailboxes per account, and can use the shared warm-up network or a private pool per account. Keep the ramp steady, then scale by adding clean sending identities instead of forcing one domain too hard.

Frequently asked questions