Verify a domain
Domain verification confirms that you control a hostname before it can be used in a scenario. Permission to test connected third-party services is separate.
Choose a method
| Method | Access needed | What UserLimit checks |
|---|---|---|
| DNS verification | Permission to edit DNS for the hostname | An exact TXT value at the domain you added. |
| Meta tag verification | Permission to edit the publicly served homepage | The issued meta tag in the HTML returned from the HTTPS homepage. |
Open Domains → Add domain, enter the hostname and copy the account-specific value from its verification dialog. Never reuse a value from an example or another account.
Publish a DNS TXT record
- Choose DNS verification and copy the entire TXT value, including its verification key.
- At your DNS provider, add a TXT record for the exact hostname shown. For a root domain the provider may call this @; follow its host-field convention.
- Check the publicly returned TXT records. Saving in a DNS dashboard is not the same as the record being visible to resolvers.
- Return to UserLimit and select Verify now. A verified domain no longer asks you to prove ownership. Keep the record for future administration.
Publish a meta tag
- Choose Meta tag verification and copy the complete tag supplied by UserLimit.
- Add it to the homepage HTML. Publish the site and clear any stale page cache as needed.
- Inspect the served HTML at the HTTPS root URL. The verifier fetches HTML; adding the tag only through client-side JavaScript is insufficient.
- Select Verify now and confirm the verified state.
Hostnames and redirects
A verified domain covers itself and its subdomains in the current account. Verifying shop.example.invalid does not cover example.invalid or a sibling hostname. Every explicit Open URL in a scenario must fall within a verified domain. That eligibility check is not permission for unlisted redirect destinations or third parties.
Meta-tag verification starts at the HTTPS homepage and follows up to three redirects to publicly resolvable hosts. Check the final served document if your homepage redirects. The meta-tag fetch refuses private, loopback and link-local addresses. DNS verification only checks the TXT record; it does not prove that the target is reachable from the load browsers. Verification is saved to your account; ownership is not continuously rechecked.
If verification fails
- Wrong hostname: compare the added domain with the DNS record or published homepage.
- Wrong value: copy the currently issued value exactly, without added spaces or a different account’s token.
- Missing tag: inspect served HTML, redirects and caching rather than only the editor preview.
- DNS not visible: check the public record and allow your provider’s propagation interval before retrying.
- Inaccessible homepage: check HTTPS, public DNS, access controls and redirect loops; coordinate a scoped access rule with the owner.
If someone else manages the site, they can publish the issued TXT record or meta tag for you. Only the hostname and verification details need to be shared; hosting passwords are not required. Further help is available in troubleshooting.