To get a Cloudflare domain verified in Resend, create a free Resend account and add your domain. Resend sees that the domain is on Cloudflare and opens a popup where you approve the DNS changes. It then adds the records itself, and the domain is verified a few minutes later. After that, you connect the verified domain in your site's email settings.
What you're setting up and why your rewards site needs it
Your Get Paid To (GPT) site sends emails to its users for things like sign-ups and account verification. Those emails should come from your own address, such as support@yourbrand.com, not from a generic one. A new user who gets a verification email from a name they don't recognize is much less likely to click it.
Your site needs an email sending service to do that, and Resend is the easiest one to use here. The reason is Cloudflare. Your domain is already there because Custom Domains requires it, and Resend can write its own records into Cloudflare for you.
In the GPT Builder setup, this is step 5. Before you start, you should have created your site in GPT Sites, set up your domain in Custom Domains, waited for it to show as active, and assigned it to the site. If you're not there yet, finish the GPT Builder setup steps first and come back.
Resend Cloudflare setup: the automatic way
Have your Cloudflare login ready, then work through this:
- Create a free Resend account.
- Open the Domains page in Resend and add your domain. If your site lives at yourbrand.com, type yourbrand.com. You can pick a sending region here too.
- Resend notices the domain is on Cloudflare and offers a "Sign in to Cloudflare" button. Click it, and a popup opens.
- Log in to Cloudflare in that popup and authorize the DNS changes. Resend adds the records to your domain itself.
- Wait a few minutes for Resend to show the domain as verified.
- Go to your GPT site's email settings and connect the verified domain.
Once the domain is verified, you can send from any address on it without any extra setup. So support@yourbrand.com works, and so would hello@yourbrand.com if you like that better.
While adding the domain, you may see Resend suggest a subdomain such as updates.yourbrand.com. That's its general advice on domains, and the idea is to keep your email reputation separate from your main domain. This walkthrough stays on yourbrand.com itself, because that matches the support@yourbrand.com address you're aiming for.
If the popup never appears, or your browser blocks it, you can add the same records yourself. It takes about five minutes.
Adding the records by hand
Resend shows you the records to add after you add your domain. Keep that page open in one tab and open Cloudflare in another. In Cloudflare, choose yourbrand.com, go to the DNS section, and add each one. The usual set is three records, like this:
| Type | Name | Value | Other |
|---|---|---|---|
| MX | send |
The MX value Resend shows | Priority 10, TTL Auto |
| TXT | send |
The SPF value Resend shows | TTL Auto |
| TXT | resend._domainkey |
The DKIM value Resend shows | TTL Auto |
In Cloudflare's form, the value goes in the "Mail server" box for the MX record and in the "Content" box for the two TXT records. Use the copy button next to each value in Resend instead of selecting the text with your mouse.
Two of the records share the name send. That's normal, because one is an MX record and the other is a TXT record.
Your list may look different. For a domain added recently, Resend may show CNAME records in place of the two send records. Add whatever Resend shows you, exactly as shown. For each CNAME record from Resend, click the orange cloud in Cloudflare so it turns gray and says "DNS only". If one is left orange, the domain never verifies.
When all three are saved, go back to Resend and click "Verify DNS Records". Resend's own Cloudflare guide has screenshots of each field if you want to compare them with your screen.
Why your domain still shows as unverified
When a domain stays unverified, the cause is usually one of four small things.
The full domain is in the Name field
This is the most common one. Cloudflare fills in the yourbrand.com part for you, so the Name field should hold only send or resend._domainkey. If you typed send.yourbrand.com, edit the record and cut it back to the short name.
Priority 10 is already taken
If your domain already has an MX record using priority 10, give the Resend record 20 or 30 instead. Nothing else about the record changes.
The DKIM value got cut off
The DKIM value is a very long string, and it's easy to miss the last few characters when you copy it. Open the record in Cloudflare and compare its ending with what Resend shows. If they differ, delete what's in the Content box and paste it again.
You checked too soon
DNS changes can take a while to take effect. If everything looks right, give it some time and then run the check again before you change anything.
If none of these is the cause, Resend keeps a longer list of reasons a domain won't verify.
Keeping your site record and your email records apart
After this step, your Cloudflare DNS page holds two groups of records that do different jobs.
The first group is a single record: the CNAME you added when you set up Custom Domains. Its name is @, and it points your domain at your rewards site. Its proxy status has to stay on, which Cloudflare shows as an orange cloud.
The second group is the Resend records. Cloudflare gives MX and TXT records no proxy switch at all, so they have no cloud to turn on or off. If Resend gave you CNAME records, those do have a cloud, and it has to stay gray.
So the only orange cloud belongs to your site's @ record. If email isn't working, leave that one alone. Turning it off won't help Resend, and it can take your site offline. The reverse is true as well. If your site stops loading, the fix isn't in the Resend rows.
There's one more trap. When you first set up a brand-new domain, the instructions say you can delete all the records already sitting in Cloudflare. That's fine on day one, when nothing there matters yet. If you ever redo your domain setup after email is working, don't clear the list again. Every record Resend gave you has to stay, or your sign-up emails will stop going out.
FAQ
How long does Resend take to verify a Cloudflare domain?
With the automatic route, it takes a few minutes. If you added the records by hand, it can take longer, because DNS changes need some time to take effect.
Is Resend free to start?
Yes. You create a free Resend account, and that's enough to add and verify your domain.
Is Resend the only way to send email from my rewards site?
The setup step is to connect email sending so that users get emails from your own domain. Resend is the easiest way to do that, mainly because it can add the Cloudflare records for you.
Which email address will my users see?
They'll see whichever address you choose on your verified domain. Verification covers the whole domain, so you don't have to register each address one by one.