How to put Discord verification on your own domain

A step-by-step walkthrough for moving your RestoreCord verify page from the default address to a subdomain you own, without breaking anything along the way.

Short answer

In Dashboard → Bots, open your bot's advanced settings, click Add Custom Domain and enter a subdomain on the Custom Domain tab. Create the CNAME to fallback.restorecord.com plus any TXT records shown, add your-domain/api/callback in the Discord Developer Portal, then republish your verify message with /setup.

What you need first

Custom domains are part of RestoreCord custom bots and available on every plan, Free included. You'll need access to your domain's DNS settings at your registrar or DNS provider, and to your bot's application in the Discord Developer Portal. Set aside ten minutes, plus whatever time DNS takes to propagate.

  • A RestoreCord custom bot that your server already verifies through
  • Login access to the DNS zone of a domain you own
  • Owner access to the bot's application in the Discord Developer Portal
  • A spare Discord account for the final test

1. Pick a subdomain

Use a subdomain of a domain you already own, such as verify.yourserver.gg or join.yourserver.gg. It keeps your main website untouched and only needs one CNAME record. Enter it in lowercase, without https:// or a trailing path; RestoreCord only accepts a plain hostname. Choose a name members will recognise as yours at a glance, because that recognition is the whole point.

2. Add it in the dashboard

Open Dashboard → Bots, choose the bot your server runs on and scroll to its advanced settings. Click Add Custom Domain, switch to the Custom Domain tab and enter the full subdomain. RestoreCord registers the hostname, marks it pending and shows the DNS records it wants to see.

Advanced Settings

Additional configuration options for your bot

Domain Configuration

Customize your verification page with a custom domain

Custom DomainFree
aurora.restorecord.app
Remove Domain

Guild Management

View and manage Discord servers your bot is currently in

Manage Bot Guilds

3. Create the DNS records

The dialog lists exactly what to add. Copy each value straight from it:

TypeNameValueWhy
CNAMEYour subdomain, for example verifyfallback.restorecord.comRoutes the hostname to RestoreCord
TXTAs shown in the dialogAs shown in the dialogProves you control the domain
TXTAs shown in the dialogAs shown in the dialogValidates the SSL certificate

If your provider lets you edit the zone as text, the finished records look roughly like this:

yourserver.gg zone (illustrative)dns
verify              CNAME  fallback.restorecord.com.
<name from dialog>  TXT    "<value from dialog>"
<name from dialog>  TXT    "<value from dialog>"

Validated TXT records drop off the list once RestoreCord has checked them. DNS changes can take up to 24 hours to propagate, and SSL is set up automatically as soon as validation passes. The CNAME is the one record you keep for good.

4. Add the new callback in Discord

In the Discord Developer Portal, open your application, go to OAuth2 and add your domain followed by /api/callback under Redirects, for example https://verify.yourserver.gg/api/callback. Keep the existing callback listed for now.

Add the new callback before the domain goes live. Otherwise members who verify on the new domain hit an Invalid Redirect URL error right after authorizing.

5. Republish the verification message

The post in your verify channel still links to the old address. Run /setup in Discord, confirm the destination channel and republish so the Verify button points at your domain. RestoreCord reminds you of this step in the dashboard when the domain is ready.

6. Test it end to end

  1. Open the republished message with a spare account and click Verify.
  2. Watch the address bar: it should show your subdomain from start to finish.
  3. Check the padlock shows a valid certificate for that exact hostname.
  4. Confirm the verified role is given and your log channel receives the event.
  5. Once you're confident, remove the old callback from the Developer Portal.

One bot, one domain

The domain belongs to the custom bot, not to a single server. If several of your servers run on the same bot, they all verify through the same address. Want different domains for different communities? Give each community its own custom bot, within your plan's bot limit: 1 on Free, 5 on Premium, 25 on Business and 50 on Enterprise.

Optional: a homepage for the domain

On Business and higher plans, Custom Domain Profile in your server settings shows your server on your custom domain homepage. Visitors who type the bare domain land on your server's page instead of an empty site.

No domain of your own yet? Read about free verification domains. Stuck on pending? See why a custom domain stays pending, or go back to RestoreCord Domains.

Custom domain setup, condensed

  1. Choose a subdomain

    Pick something members will recognise, like verify. or join. on a domain you already own.

  2. Add it in the bot's settings

    Open Dashboard → Bots, go to advanced settings, click Add Custom Domain and enter it on the Custom Domain tab.

  3. Create the DNS records

    Add the CNAME pointing to fallback.restorecord.com and every TXT record the dialog shows.

  4. Update Discord and republish

    Add the new callback in the Developer Portal, wait until the domain is active, then republish with /setup.

Bot management in the RestoreCord docs

Setup questions

Your domain, RestoreCord's protection

Members see your address while RestoreCord handles verification, backups and security behind it.