runs-at.dev
runs-at.dev // documentation

Docs / Guides / Discord verification

Discord verification

Proving you own you.runs-at.dev to Discord, via a TXT record.

What you'll end up with

Discord verifies domain ownership (for a linked-role application, or a domain attached to your profile) by checking for a TXT record at _discord.you.runs-at.dev containing a token it generates for you.

The record

domains/you.json

"subdomains": {
  "_discord": { "TXT": ["dh=0f817e9945292eb7eaba294fbba9b6f50d74a885"] }
}

The dh=... value is generated per domain by Discord, shown when you start verification. Replace it with your own; the one above is only an example of the shape.

Steps

Note

Two ways to apply this. The quickest is runs-at.dev/manage: sign in, pick the record type, paste the value, save. It writes the same commit to the registry and DNS follows within seconds. The steps below do it by pull request instead, which is what you want if you would rather review the change first. Either way handles subdomains entries.

  1. In Discord's domain verification flow (Developer Portal, for a linked-role application, or your user settings for a profile domain), enter you.runs-at.dev and copy the dh=... value it gives you.
  2. Fork the registry and edit domains/you.json to the record above, using that value.
  3. Open a pull request. Once merged, the TXT record is synced to DNS automatically.
  4. Back in Discord, click Verify.

How to tell it worked

Discord confirms verification as soon as it can resolve the _discord TXT record and the token matches, usually within a minute of the pull request merging.