Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.brew.new/llms.txt

Use this file to discover all available pages before exploring further.

To send emails through Brew, verify a sending domain you own. This is a one-time setup that takes about five minutes. Once verified, every email comes from your own domain.

​
How to verify

1

Add your sending domain

Go to Settings → Domains and click Add sending domain.Use a subdomain, not your root domain. For example, updates.acme.com instead of acme.com.
If you send from your root domain and run into deliverability problems, every other sending stream on that domain can be affected. Isolating email on a subdomain keeps issues contained.
Good subdomain options:
  • mail.yourdomain.com
  • updates.yourdomain.com
  • news.yourdomain.com
Click Add Domain to start verification.
2

Set default sender details

Configure how your emails appear in recipients’ inboxes:
  • Sender name. Appears next to your email address. Keep it personal (a real name works well).
  • From email. The address in the “From” field.
  • Reply-to email. Where replies land. Use a monitored address, never no-reply. Replies signal value to inbox providers and improve your deliverability.
You can override any of these per email when you send.
3

Add DNS records

Authorize Brew to send on your behalf by adding DNS records to your domain.
Download the zone file from the Brew dashboard and upload it to your DNS provider. This adds every record in a few clicks.

​
Records you’ll add

A cryptographic key that proves your email wasn’t altered in transit. Added as a TXT record.
Tells receiving inboxes which servers are allowed to send for you. Added as both an MX and a TXT record.
GoDaddy. Sign in, open your domain’s DNS settings, click Add, and create each record. For MX records, set priority to 10. If you see an “invalid hostname” error, try adding a period (.) at the end of the value. GoDaddy helpCloudflare. Sign in, select your domain, go to DNS, click Add record. Set proxy status to DNS Only (gray cloud) for every record, proxying breaks email authentication. Cloudflare helpGoogle Domains. Sign in, select your domain, go to DNS, and use the Custom resource records area. Google may add quotes to TXT records. That’s normal. Google helpNamecheap. Sign in, go to Advanced DNS. If you use Gmail/Google Workspace, switch Mail Settings to Custom MX before adding Brew’s MX records, then re-add Gmail’s MX record. Namecheap helpAWS Route 53. Sign in, select your hosted zone, click Create record. For MX records, put priority and value together. Use only the subdomain part for record names. AWS helpSquarespace. Sign in, go to Domains, pick your domain, scroll to Custom Records. Remove trailing periods if you see errors. Squarespace helpVercel. Sign in, open your domain’s DNS settings. Use only the subdomain part for record names. Vercel helpWix. Wix DNS doesn’t support MX records for subdomains if nameservers point to Wix. Use the “Pointing” method or manage DNS externally (e.g. Cloudflare). Wix helpDreamhost. Currently unsupported for custom subdomain MX records. Use an external DNS provider or contact Dreamhost support. Dreamhost help
  • Add a teammate with DNS access to your Brew account
  • Share this guide with your IT team
If you already have an MX record for the same hostname (e.g. mail.yourdomain.com), remove it before adding Brew’s.The MX record is for your sending subdomain, not your root domain. It won’t affect existing email on your root domain.If you need to keep the existing MX record, pick a different subdomain (e.g. newsletter.yourdomain.com), update Settings → Domains, and re-run verification.
Not sure who hosts your DNS? Look up your nameservers at whois.domaintools.com.
4

Verify your records

Return to Brew and click Verify records. Records turn green as they verify; the domain status badge turns green when all records pass. Each record shows a color-coded status, so you can spot stragglers at a glance.
DNS propagation can take up to 72 hours. If verification doesn’t happen immediately, check back later. That’s normal.

​
Best practices

Sending from a subdomain like mail.yourdomain.com instead of your root domain protects your main domain’s reputation. If deliverability issues happen on a subdomain, you can isolate the problem without affecting the rest of your business.The subdomain you choose appears in the From field, so pick something recognizable.
Use addresses like hello@company.com or support@company.com and have someone monitor them. Replies signal to inbox providers that your content is valuable.

​
FAQ

Yes. Go to Settings → Domains and update at any time. You’ll need to re-verify the new domain, and we recommend ramping up sending volume gradually so the new domain builds reputation cleanly.
Another Brew account has already verified this domain or a related one. Once verified, a domain and all its subdomains are protected.What to do:
  • Find who set up the original Brew account on your team
  • Ask them to invite you
  • If you believe this is wrong, email support@brew.new with proof of domain ownership
Buy one from a registrar like GoDaddy, Namecheap, or Google Domains.
You’ll need to re-verify if you switch subdomains, change your root domain, switch DNS providers, or change nameservers.

​
Need Help?

Our team is ready to support you at every step of your journey with Brew. Choose the option that works best for you:

Search Documentation

Type in the “Ask any question” search bar at the top left to instantly find relevant documentation pages.

ChatGPT/Claude Integration

Click “Open in ChatGPT” at the top right of any page to analyze documentation with ChatGPT or Claude for deeper insights.