Skip to main content

Guides

How to set up Resend for sending email

Resend sends the emails your app or shop triggers, like receipts and password resets. Setup is mostly a domain and a few DNS records. Here are the steps.

Steps checked against the vendor's documentation on October 21, 2026.

Resend is a plain email-sending service. It does not write anything. You give it a domain you control, and it delivers your messages from that domain.

The steps

  1. Choose a subdomain to send from

    Resend suggests sending from a subdomain, such as updates.yourdomain.com, rather than your main domain. That keeps the sending reputation of your main address separate. Pick a name that fits what you will send.
    Resend docs: Domains(opens the vendor's page in a new tab)
  2. Add the domain in the dashboard

    Open the Domains page in the Resend dashboard and click "Add Domain". Enter your subdomain and choose a sending region. You can leave the optional settings as they are for now.
    Resend docs: Add a domain(opens the vendor's page in a new tab)
  3. Add the DNS records Resend shows you

    Open the "Records" tab. Resend lists the DKIM and SPF records to add. Copy them into your domain provider's DNS settings exactly as shown. If a record is a CNAME, do not turn on proxying, such as Cloudflare's orange cloud, or verification will not finish.
    Resend docs: Add a domain(opens the vendor's page in a new tab)
  4. Wait for verification

    Verification often finishes within about 15 minutes of adding the records, and can take longer for DNS to spread. If it has not completed after a long wait, use the "Restart verification" button after checking the records.
    Resend docs: Add a domain(opens the vendor's page in a new tab)
  5. Add a DMARC record after verification

    Once the domain is verified, Resend recommends adding a DMARC record to build trust and protect against people faking your address. Resend has a separate guide on it.
    Resend docs: Add a domain(opens the vendor's page in a new tab)
  6. Create an API key with sending access

    Open the "API keys" page and click "Create API Key". Give it a name and choose "Sending access", optionally limited to your domain. Use full access only if the key must manage other things.
    Resend docs: Create an API key(opens the vendor's page in a new tab)
  7. Copy the key once and keep it safe

    Resend shows the key only one time. Copy it straight away and store it as a secret, for example as an environment variable. Do not paste it into a chat or commit it to a public repository.
    Resend docs: API keys(opens the vendor's page in a new tab)

Common questions

Do I need a domain to use Resend?

Yes. You must add and verify at least one domain you control before Resend will send emails for you.

Why use a subdomain?

Resend's documentation recommends it so the sending reputation of your main domain stays separate. Each subdomain is set up and verified on its own.

Can AI do this setup for me?

AI can explain what a DNS record is. You should copy the exact values from the Resend dashboard into your DNS provider yourself, and never share the API key in a chat.

Not sure this is the right tool?

The free plan finder sorts your jobs and shows the tools that fit your budget.