Resend · Domain Verification
Connect a Custom Sending Domain in Resend
This guide explains how to connect and verify a custom sending domain in Resend by adding the DNS records generated in your dashboard. A correctly configured domain helps you send email with a branded identity and a more reliable technical setup.
Why verify a custom domain
Branded sender identity
A verified custom domain lets you send from addresses aligned with your brand instead of relying on a generic sender setup. This supports a more professional presentation across marketing and transactional email.
Authorization and trust
A verified custom domain helps align your email infrastructure with your brand and confirms that the sending environment is properly authorized through DNS. It also creates a cleaner foundation for transactional email, newsletters, and outbound campaign setups.
Cleaner separation of infrastructure
Many senders prefer using a dedicated sending subdomain so that their main website identity and their campaign infrastructure stay clearly separated and easier to manage. This also limits the blast radius if a sending subdomain ever needs remediation.
DNS records Resend typically requires
A correct Resend setup usually includes DNS records for SPF, DKIM, and related routing or bounce handling. These records help mailbox providers validate the sending source. Resend shows the exact live values inside your own dashboard, and those values can vary by region or account configuration — the table below shows the common structure only.
| Record Type | Purpose | Host / Name | Value Format |
|---|
| TXT | SPF authorization on sending subdomain | send.yourdomain.com | v=spf1 include:amazonses.com ~all |
| TXT or CNAME | DKIM signing configuration | resend._domainkey.send.yourdomain.com | provider-generated DKIM value |
| MX or CNAME | Return-Path or bounce handling | send.yourdomain.com or custom path | provider-generated target |
| TXT | DMARC policy | _dmarc.yourdomain.com | v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com |
v=spf1 include:amazonses.com ~all
Step-by-step setup
- Log in to Resend. Go to the area where custom sending domains are managed.
- Add your domain. Many senders choose a dedicated subdomain (e.g.
send.yourdomain.com) for better organization and brand separation.
- Copy the generated records. Open the records section for the new domain and copy each DNS value exactly as shown in your account.
- Publish the records. Add the SPF, DKIM, and any routing or bounce-related records in the DNS panel where your domain is managed.
- Add a DMARC policy. This strengthens your email authentication setup and supports better domain protection.
- Verify in Resend. After the records propagate, return to Resend and complete the verification process before starting your campaigns or transactional sends.
Common host examples: send · resend._domainkey.send · _dmarc
Common pitfalls
- DNS authentication works only when record names and values are entered exactly — copy and paste directly instead of typing manually.
- Some domains verify quickly, while others take longer depending on the DNS provider and global propagation timing.
- If verification is delayed, inspect the public DNS results to confirm all records are visible and published exactly as expected.
- Some DNS panels automatically append the root domain, so review the saved hostname carefully after each record is added.
- Example records are useful for learning, but real production values should always come from the live Resend dashboard.
Frequently asked questions
- Should I use a dedicated subdomain for sending?
- Yes. A dedicated sending subdomain is often a practical choice for cleaner email infrastructure and better operational separation from your main brand domain.
- How long does verification take?
- It can be quick, but it may also take longer depending on DNS propagation and your provider's refresh timing.
- What records make up a typical setup?
- A typical setup includes SPF, DKIM, DMARC, and sometimes routing or bounce-related records depending on the sending configuration.
- What should I do if verification fails?
- Double-check every host and value, confirm the records are visible publicly, and retry after allowing more time for propagation.
Contact ontiscal.com if you want to rent quality and aged domain names configured through custom DNS records working for email platforms like Resend or Brevo.