A GitHub user or organisation verified the domain for GitHub Pages, which stops anyone else’s repository from publishing on it — including its immediate subdomains. GitHub says to keep the record so the domain stays verified.
Name: _github-pages-challenge-<user> Type: TXT Value: 9f8e7d6c5b4a
| Added by | GitHub — GitHub Pages verified domains |
| Can it be deleted? | Keep it — the service checks it again, and removing it undoes the verification |
| Name | _github-pages-challenge-USER.example.com — the account’s name is in it |
| Protects | The domain and its immediate subdomains |
Look for it on your domain
Enter a domain: we look up its TXT records and say whether this one is there — naming every other record we recognise.
What it is for
Verifying a custom domain for GitHub Pages prevents a takeover: without it, if the site were deleted while DNS still pointed at GitHub, anyone could publish on the domain.
Why it is on your domain
- A GitHub account that publishes a Pages site on the domain verified it.
Can you delete it?
Keep it. GitHub says to keep the TXT record in the domain’s DNS so the custom domain remains verified.
Sources
Checked on 26 September 2026 against these official sources:
- Verifying your custom domain for GitHub Pages — docs.github.com