Domain Verification
Prove you own a domain with a single DNS TXT record.
Why verify?
Verification proves you own the domain so nobody else can route traffic for it through RenderBeam. It's a one-time, ~5 minute step.
Adding the DNS record
Add a TXT record at the subdomain _renderbeam:
| Field | Value |
|---|---|
| Type | TXT |
| Name | _renderbeam |
| Value | Your verification token (shown in the dashboard) |
| TTL | Auto / 300 |
We resolve the record via Google Public DNS, so cached answers from your local resolver don't matter.
Common DNS providers
Cloudflare
DNS → Add record → TXT → Name _renderbeam → paste token → Save.
GoDaddy
My Products → DNS → Add → TXT → Host _renderbeam → paste token → Save.
Namecheap
Domain List → Manage → Advanced DNS → Add New Record → TXT → Host _renderbeam → paste token → Save.
Vercel / Netlify
DNS settings for the apex domain → Add record → TXT → Name _renderbeam → paste token.
Verification time
- Cloudflare: 1–5 minutes
- Most providers: 5–15 minutes
- Some providers: up to 24 hours
You can check propagation at dnschecker.org.
After verification
The verified badge unlocks the edge setup for that domain. Continue to Cloudflare Worker Setup or the Non-Cloudflare path.
Troubleshooting
- Verification failed — confirm the record is at exactly
_renderbeam.yourdomain.com(not the apex), no extra spaces in the token, and waited at least 5 minutes. - Some providers auto-append the domain — entering
_renderbeam.yourdomain.comwould result in_renderbeam.yourdomain.com.yourdomain.com. Use just_renderbeam.
Was this page helpful?