What is a return-path or bounce domain?

When you send an email, there are actually two sender addresses in play. The one your subscribers see in their inbox is your From address. Hidden in the technical envelope is a second address: the return-path, sometimes called the bounce domain or envelope-from. This is where undeliverable mail bounces back to, and it's what receiving servers use to run your SPF check.

The mechanics work like this: your ESP routes mail through their servers, so by default the return-path is something like bounces.youresp.com. Every time a message hard-bounces, the notification goes to that address and your ESP processes it automatically. That's fine for basic sending, but it means your SPF record is technically aligned to your ESP's domain, not yours. For DMARC alignment, you'll usually want your return-path on a subdomain you control. Something like bounce.yourbrand.com.

Setting up a custom bounce domain means adding a CNAME record in your DNS that points to your ESP's bounce processing infrastructure. Most major ESPs, SendGrid, Mailchimp, Klaviyo, support this in their account settings under sending domains or authentication. The CNAME does the actual routing, so your ESP still handles the bounce processing. You're just claiming the domain for your brand.

But It's worth distinguishing hard bounces from soft bounces here. Hard bounces (addresses that don't exist) come back via the return-path as permanent failures. Soft bounces are temporary (mailbox full, server timeout) and may route through the return-path but typically trigger retry logic before returning a failure. Your ESP handles both, but the custom bounce domain affects how DMARC alignment is evaluated across your authentication setup.

So if If you want to verify your current setup, paste your sending domain into the free SPF checker at Review My Emails. You'll see immediately whether your return-path domain is aligned, and if it isn't, the checker will point you to exactly what's missing in your DNS configuration.