TXT verification guide
When SMS verification is not available, confirm your redirect target mobile number by adding a DNS TXT record on your bound domain. Once verified, phone redirect works the same as after SMS verification.
What is TXT verification?
We look up a specific TXT record under your domain. If its value matches the redirect phone number in E.164 form (with a leading +), verification succeeds.
- What is verified: redirect target mobile (not your login ID phone)
- Which domain: the primary domain bound to your site
- How we check: read TXT on your bound domain and compare to your redirect phone
- Deadline: within 10 days after payment or after changing redirect mobile
When should I use TXT verification?
TXT is a fallback. Prefer SMS verification in the customer portal when it works.
SMS code never arrives: Carrier filtering or delay, phone off/airplane mode, wrong redirect number, rate limits, etc. Action: Sign in / Register → open Phone verification → tab “No SMS · TXT verification” → add the DNS record → click Check TXT and verify.
Alibaba Cloud international SMS does not cover your region: If international SMS is not enabled or not available for your country, the portal directs you to TXT verification. As long as you control DNS for the bound domain, TXT still works.
Steps (summary)
- Sign in and open Phone verification; note the TXT host and value
- Add the TXT record in your DNS panel (section below)
- Wait for DNS propagation (minutes to hours)
- Return to the portal and click Check TXT and verify
| Item | Value |
|---|---|
| Host / name | 302tel |
| Type | TXT |
| Record value | Redirect phone shown at the top of the portal verify page (must include +) |
Adding TXT in your DNS panel
| Field | Enter | Notes |
|---|---|---|
| Type | TXT | Not A / CNAME |
| Host | 302tel | Usually without .example.com suffix |
| Value | Portal redirect phone at top of verify page | Leading +, no spaces |
| TTL | Default / 600 | Default is fine |
Full name queried on the internet:
Provider examples (value = redirect phone at top of portal verify page)
- Alibaba Cloud DNS: Type TXT, Host
302tel, Value = portal phone. - Tencent DNSPod: Host
302tel, Type TXT, Value = portal phone. - Cloudflare: Type TXT, Name
302tel, Content = portal phone, Proxy DNS only. - GoDaddy and others: Host
302tel, Type TXT, Value = portal phone. - Dynadot App (two fields only): Type
TXT, Value = portal phone on the root domain (no302telhost).
Common mistakes and checking propagation
| Wrong | Correct |
|---|---|
Host @ | 302tel |
Value with +86 or spaces | Digits only |
| Type A / CNAME | TXT |
| TXT on wrong domain | On the domain shown in the portal |
- Use the portal button Check TXT and verify (recommended)
- Or a third-party DNS TXT lookup for host
302telor root TXT on your domain - Or click Check TXT and verify in the portal
Delete TXT after success? Changed redirect mobile?
Delete TXT after success? Optional — verified status stays even if you remove the record.
Changed redirect mobile? Update TXT to the new value and verify again within 10 days.
Format? Use the redirect phone at the top of the portal verify page — E.164 with a leading +.
Landline numbers? No TXT needed — landlines are entered by your agent.