Skip to content

Domain verification — statistics without a Provider ID

Verify the domain serving your subscriptions to see its users in the provider portal, including subscriptions without a Provider ID.

Open Domains and choose a verification method. You can paste a full subscription URL; the portal extracts the host.

DNS TXT: parent domain and subdomains

  1. Add the domain in the portal.
  2. Create the TXT record with the exact name and value shown there.
  3. Press Check. If DNS has not propagated, wait and try again.

For Cloudflare, Add via Cloudflare creates the record automatically after you grant permission. The record stays in DNS after verification.

DNS verification of example.com covers sub.example.com, eu.sub.example.com and other subdomains. Multi-level suffixes are handled correctly: example.co.uk is registrable, while co.uk is not. evil-example.com does not match example.com.

HTML file: exact host only

Use this method when you can upload a file to the website but cannot edit DNS.

  1. Select HTML file and add the exact host, such as sub.example.com.
  2. Download smproxy-verify.html from the portal. Keep its generated <meta> verification token unchanged.
  3. Place it at https://sub.example.com/smproxy-verify.html, accessible without authentication.
  4. Ensure the server returns the file itself, rather than a placeholder, login page or redirect to another host.
  5. Press Check in the portal. Success shows the verified status and exact-host scope.

Verification tries HTTPS with a valid certificate first, then HTTP if retrieval fails. If the token does not match, download the current file from the portal and replace the old one.

HTML verification of sub.example.com does not cover example.com, other.example.com or subdomains below sub.example.com. Verify other hosts separately, or use DNS TXT for the parent domain.

Provider ID and management scope

If a subscription specifies an existing Provider ID, its users belong to that provider. A verified domain helps identify the owner when the ID is absent or unknown; it does not override an explicitly specified existing ID.

A verified domain belongs to one provider. A domain already assigned to an account cannot be claimed by another account.

Where domains are used

  • Statistics: subscription-domain breakdown and a host in the device row. sub.example.com and sub3.example.com remain distinct.
  • Messages: target a specific host; DNS verification also supports *.example.com and its subdomains. HTML verification supports the exact host only.
  • Client settings: per-domain overrides in addition to shared values.
  • Migrations and backup addresses: rules for your own verified domains.

The domain list shows the host, not a secret token from a subscription URL. See Provider portal for settings and Moving users to another domain for migrations.