|
| 1 | +# Verify your team email domain |
| 2 | + |
| 3 | +## Why should I verify my domain? |
| 4 | + |
| 5 | +- Verified badge: Your team gets a special badge, so it’s easier to confirm you're in the right place. |
| 6 | +- 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. |
| 7 | +- 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. |
| 8 | + |
| 9 | +## How to verify your domain |
| 10 | + |
| 11 | +1. Navigate to [Team Settings](https://thirdweb.com/team/~/~/settings) and look for *Domain Verification*. |
| 12 | +1. Enter your domain name. |
| 13 | + - 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`. |
| 14 | +1. You should see instructions to add a `TXT record` on your domain to complete verification. |
| 15 | + - Type: TXT |
| 16 | + - Name/Host: `_tw-<YOUR_TEAM_ID>.<YOUR_DOMAIN>` |
| 17 | + - Value: `tw-verify=<YOUR_VERIFICATION_CODE>` |
| 18 | + - See below for provider-specific instructions. |
| 19 | + |
| 20 | +thirdweb will automatically detect the TXT record once it's live. DNS changes may take several hours to update. |
| 21 | +Check this dashboard page periodically to confirm when it's completed. |
| 22 | + |
| 23 | +### Verify your TXT record |
| 24 | + |
| 25 | +Use a tool like [MxToolbox](https://mxtoolbox.com/txtlookup.aspx) or `dig` in the command line to check if your TXT record is correct. |
| 26 | + |
| 27 | +```bash |
| 28 | +$ dig +short -t txt _tw-<TEAM_ID>.<YOUR_DOMAIN> |
| 29 | + |
| 30 | +# If correct, you should see this response: |
| 31 | +"tw-verify=<YOUR_VERIFICATION_CODE>" |
| 32 | +``` |
| 33 | + |
| 34 | +## Provider-specific instructions |
| 35 | + |
| 36 | +Here are instructions for common DNS providers. Please refer to the provider's documentation for further support. |
| 37 | + |
| 38 | +### Cloudflare |
| 39 | + |
| 40 | +- Navigate to the Cloudflare dashboard. |
| 41 | +- Select your zone and domain. |
| 42 | +- Select *DNS* > *Records*. |
| 43 | +- Select *Add record*. |
| 44 | + |
| 45 | +[Cloudflare documentation](https://www.cloudflare.com/learning/dns/dns-records/dns-txt-record/) |
| 46 | + |
| 47 | +### AWS Route 53 |
| 48 | + |
| 49 | +- Navigate to the Route 53 console. |
| 50 | +- Select *Hosted Zones* and select your domain. |
| 51 | +- Select *Create record*. |
| 52 | + |
| 53 | +[AWS Documentation](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-creating.html) |
| 54 | + |
| 55 | +### Google Cloud DNS |
| 56 | +- Navigate to the Google Cloud Console. |
| 57 | +- Select *Network Services* > *Cloud DNS*. |
| 58 | +- Select your zone. |
| 59 | +- Select *Add record set*. |
| 60 | + |
| 61 | +[Google Cloud documentation](https://cloud.google.com/dns/docs/records#add-rrset) |
0 commit comments