Discord lets you connect a domain to your profile the same way you connect a game or music account. Instead of logging in somewhere, you prove ownership by adding a DNS record. It is a small trust signal: people who see yourname.com on your profile know the person behind that site is you.
What you need
- A domain or subdomain you control, such as
yourname.comorme.yourname.com. - Access to its DNS settings at your registrar or DNS host.
- Discord on desktop or in a browser, where the Connections page is easiest to use.
Step by step
- Open User Settings and go to Connections.
- Open the full list of services (View more) and choose the domain option, shown with a globe icon.
- Type your domain and continue. Discord shows a verification string. Leave that window open.
- In your DNS host, create a TXT record. The name is
_discordin front of the domain you entered, for example_discord.yourname.com. Paste the string as the value. - Save the record, go back to Discord and press Verify.
| Field at your DNS host | What to enter |
|---|---|
| Type | TXT |
| Name / Host | _discord (many hosts add the domain for you; some want the full _discord.yourname.com) |
| Value | The string Discord showed you, exactly as shown |
| TTL | Default is fine |
When it says "Unable to verify your domain"
- DNS has not spread yet. New records can take a few minutes, sometimes up to 24 hours. Wait and press Verify again.
- Doubled name. If your host adds the domain automatically and you typed the full name, the record ends up at
_discord.yourname.com.yourname.com. Use just_discord. - Changed value. Some hosts add quotes or trim characters. Compare the saved value with what Discord shows.
- Wrong domain. The record must be on the exact domain you typed in Discord. A record on
yourname.comdoes not verifywww.yourname.com.
Using a subdomain or a free domain
You do not have to connect your main domain. A subdomain such as me.yourname.com works the same way, with the record at _discord.me.yourname.com. Some free subdomain services, such as community projects that hand out names on a shared domain, document this exact setup: you submit a _discord TXT record for your name and wait for it to go live. If your provider does not let you add TXT records, the connection cannot be verified.
Keeping it verified
Leave the TXT record in place after verifying. If you move DNS hosts, copy the record over before you switch, and re-check the connection afterwards. If the domain expires or changes hands, remove the connection from your profile, because whoever controls the domain next could set up their own record. You can show or hide the connection on your profile from the same Connections page, like any other linked account.
What it does not do
The connection sits on your user profile. Discord does not offer domain verification for servers, and the connection does not change your server's invite, name or look. It also does not put anything on your website; Discord only reads the one TXT record.
Putting your server on your domain
If what you want is your server tied to your domain, the useful place is the verification page every new member opens. With VaultCord on Premium or Plus, that page can run at an address like verify.yourname.com. It uses the same DNS skills: you add one record for the subdomain and the dashboard does the rest. See verification on your own domain, or plan the rest of your server's web presence with how to make a website for your Discord server.