Splitworthy documentation
Domain verification
DNS TXT, HTTPS files and the difference between verified and connected.
DNS TXT challenge
From Websites → your website, generate a DNS challenge. Publish the exact returned value at _testwell.your-registered-domain. Use the host-name format your DNS provider expects; some append the domain automatically. Preserve other TXT records.
Value format: testwell-verify=<the token generated for this website>. Copy the real value from your account, not this placeholder. Challenges expire after 60 minutes and are one-use. Wait for DNS propagation, then request verification in the website page.
HTTPS file challenge
Generate an HTTPS challenge and publish the exact returned text at /.well-known/testwell-verification.txt on the registered domain. It must be publicly readable over HTTPS as a small plain-text response, not your app’s HTML fallback, an authenticated page or a redirect.
The verifier rejects redirects, unsafe hosts and oversized responses. The request has an eight-second timeout and 4KB response cap. If it fails, check the hostname, response body, certificate, public routing and token expiry. Do not move the file to a different domain.
Verified is not the same as installed
Verification proves domain ownership. Installation is established through the verified website’s SDK configuration request. A snippet or public ID does not independently prove ownership. WordPress pairing performs its own domain callback.
Ensure the platform returns configuration for the registered origin, the website is not disabled and your consent requirements are satisfied. An enabled response with no experiments can still be a correct connected installation.