# Add a sending domain

Add one of your domains right inside the app — FlareMail uses your Cloudflare account to onboard sending, write the DNS, and route replies back to you. No leaving the app.

4 min read. HTML: https://sendwithflare.com/help/add-a-sending-domain/

If your domain is on **Cloudflare**, you can add it as a sending domain without leaving FlareMail. The app talks to your Cloudflare account to onboard the domain for **Email Sending**, write the required **SPF, DKIM, and DMARC** records for you, and set up inbound **Email Routing** so replies land back in your inbox. Once it's verified, you send as any address on that domain — and your recipients see your domain's name, not “FlareMail”.

> **NOTE:** Your domain must already be on the same Cloudflare account your FlareMail backend is authorized for. Cloudflare hosts the DNS, so FlareMail can add every record automatically — you never copy or paste DNS.

## Add the domain

1. **Open Sending domains** — In the app, open **Settings** (`⌘` `,`) → **Sending domains**.
2. **Enter your domain** — Under **Add a sending domain**, type your domain, e.g. `yourbrand.com`. FlareMail suggests a title-cased *sender name* from it (so `docu-coach.com` becomes “Docu Coach”). Edit the name if you like — it's what recipients see.
3. **Click Add domain** — FlareMail onboards the domain for Email Sending, and Cloudflare adds the SPF/DKIM/DMARC records automatically. It also enables Email Routing and points the catch-all at the FlareMail worker so replies come back to you.
4. **Watch the status** — The domain shows **Verified** once sending is ready and **Receiving on** once inbound routing is set up. For Cloudflare-hosted domains this is typically instant. If it's still pending, hit **Verify** to re-check.

> **TIP:** The sender name is per-domain and editable. It's the friendly name in the “From” of every message you send from that domain — pick how you want your brand to appear.

## Add sender addresses

Under a verified domain, add the specific addresses you want to send from — `hello@`, `support@`, `you@`, and so on. Each one gets the domain's sender name by default, and you can mark one as your **default**. These are the addresses that appear in the composer's “From” menu.

## Send from your domain

When you compose, pick the sender from the **From** menu at the top of the message. Mail sent from a Cloudflare-provisioned domain goes out through **Cloudflare Email Sending** and arrives showing your domain's name — e.g. “Docu Coach <hello@docu-coach.com>”. No more “FlareMail” in the sender line.

## Receiving replies

Because adding the domain also sets a catch-all route to the `flaremail-api` worker, any address on the domain can receive mail — replies to the addresses you send from land straight in FlareMail. You don't need the separate [manual routing](/help/connect-cloudflare-email-routing/) step for these domains.

> **WARNING:** Setting up the backend? The worker's Cloudflare API token needs **DNS · Edit**, **Email Sending · Edit**, **Email Routing Rules · Edit**, **Email Routing Addresses · Edit**, and **Zone · Read**. If a permission is missing, adding a domain returns a clear message telling you which one — sending can still succeed even if routing (receiving) isn't authorized yet.

Prefer to wire routing by hand, or sending through a third-party provider? See [Connect Cloudflare Email Routing](/help/connect-cloudflare-email-routing/) and [Sending from your domain](/help/sending-from-your-domain/). If a domain won't verify, check [Troubleshooting](/help/troubleshooting/).