Verify a domain
1
Open Domains
Go to Dashboard → Settings → Domains.
2
Add the hostname
Enter the exact hostname you plan to ship on, such as
app.example.com. Add each host
you serve separately.3
Publish the DNS TXT record
The dashboard shows a DNS TXT record for the domain. Add it at your DNS provider using
the host and value below.
The host is
_gp-verify. followed by your domain, and the value always starts with
gp-verify-. Copy the exact value shown in the dashboard — it is unique to your domain.4
Run verification
Return to Dashboard → Settings → Domains and run verification. Puntego looks up the
TXT record over DNS and marks the domain verified once it matches. DNS changes can take
time to propagate, so re-run verification if it does not pass on the first try.
Add and verify every production hostname before you launch — including preview or staging
hosts where the boot script runs. The runtime checks the origin when it loads, so an
unverified host will not mount the guide.
Why this matters
- Puntego refuses to boot on origins you have not verified, so the guide never appears on a site you do not control.
- Verified domains keep your app ID from being reused on another site under someone else’s control.
- One clear allowlist gives you a single place to see — and trust — exactly where the guide can run.
Local development
Local development origins are allowed outside production, so your test harness and local builds boot without a verified domain. Production traffic must come from a hostname you have added and verified here.Next steps
Install Puntego
Add the boot script, then copy the canonical snippet for a verified domain.
Content Security Policy
Allow the worker and runtime under a strict CSP with a nonce.
Security
See how origin checks fit the wider security model.
Boot errors
Read the boot responses, including origin_not_allowed for an unverified host.