-
Notifications
You must be signed in to change notification settings - Fork 543
docs: Add page on domain verification #7247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
61 changes: 61 additions & 0 deletions
61
apps/portal/src/app/knowledge-base/how-to/verify-your-team-email-domain/page.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,61 @@ | ||
# Verify your team email domain | ||
|
||
## Why should I verify my domain? | ||
|
||
- Verified badge: Your team gets a special badge, so it’s easier to confirm you're in the right place. | ||
- Recommended team members: On the Settings → Members page, you’ll see users with emails that match your domain but aren’t in the team yet — making it super easy to invite everyone on the team. | ||
- Instant invite alerts: Team owners will get a notification (in the dashboard and optionally via email) when someone signs up with your verified domain — with a 1-click invite option. | ||
|
||
## How to verify your domain | ||
|
||
1. Navigate to [Team Settings](https://thirdweb.com/team/~/~/settings) and look for *Domain Verification*. | ||
1. Enter your domain name. | ||
- Your domain name is the part after the `@` symbol in your company email address. It is NOT a website and should not contain `https://` nor `www`. | ||
1. You should see instructions to add a `TXT record` on your domain to complete verification. | ||
- Type: TXT | ||
- Name/Host: `_tw-<YOUR_TEAM_ID>.<YOUR_DOMAIN>` | ||
- Value: `tw-verify=<YOUR_VERIFICATION_CODE>` | ||
- See below for provider-specific instructions. | ||
|
||
thirdweb will automatically detect the TXT record once it's live. DNS changes may take several hours to update. | ||
Check this dashboard page periodically to confirm when it's completed. | ||
|
||
### Verify your TXT record | ||
|
||
Use a tool like [MxToolbox](https://mxtoolbox.com/txtlookup.aspx) or `dig` in the command line to check if your TXT record is correct. | ||
|
||
```bash | ||
$ dig +short -t txt _tw-<TEAM_ID>.<YOUR_DOMAIN> | ||
|
||
# If correct, you should see this response: | ||
"tw-verify=<YOUR_VERIFICATION_CODE>" | ||
``` | ||
|
||
## Provider-specific instructions | ||
|
||
Here are instructions for common DNS providers. Please refer to the provider's documentation for further support. | ||
|
||
### Cloudflare | ||
|
||
- Navigate to the Cloudflare dashboard. | ||
- Select your zone and domain. | ||
- Select *DNS* > *Records*. | ||
- Select *Add record*. | ||
|
||
[Cloudflare documentation](https://www.cloudflare.com/learning/dns/dns-records/dns-txt-record/) | ||
|
||
### AWS Route 53 | ||
|
||
- Navigate to the Route 53 console. | ||
- Select *Hosted Zones* and select your domain. | ||
- Select *Create record*. | ||
|
||
[AWS Documentation](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-creating.html) | ||
|
||
### Google Cloud DNS | ||
- Navigate to the Google Cloud Console. | ||
- Select *Network Services* > *Cloud DNS*. | ||
- Select your zone. | ||
- Select *Add record set*. | ||
|
||
[Google Cloud documentation](https://cloud.google.com/dns/docs/records#add-rrset) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a closing code fence to the
bash
snippetThe
dig
example is opened with ```bash but isn’t closed, which will break the markdown rendering. Please add a closing backtick fence after the example output:"tw-verify=<YOUR_VERIFICATION_CODE>" +```
🤖 Prompt for AI Agents