localhost, a staging host or a
teammate’s machine — use the test snippet instead: it needs no
verification.
Verify a domain
1
Open Domains
Go to Dashboard → Install → 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. A workspace on the Free plan verifies one domain; paid plans verify
as many as you need.3
Publish the token one way
The dashboard shows a token that starts with
gp-verify-, unique to your domain. Publish
it in any one of these places:The tag and the file must be served by the domain itself over HTTPS. A redirect between
the apex and its
www host is followed; a redirect to any other host is not.4
Run verification
Return to Dashboard → Install → Domains and choose Verify now. Puntego checks the
DNS record, then the file, then the tag, and marks the domain verified as soon as one
matches. DNS changes can take time to propagate; the tag and the file count as soon as
your site serves them.
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
The production snippet never boots onhttp://localhost:3000, and localhost cannot be
verified. Use the test snippet from Dashboard → Install instead: it boots on any page,
localhost included, shows a visible “Test mode” label, keeps its traffic out of your analytics
and usage, and runs under hourly, daily and monthly limits. See local development.
Your website and your domains
Settings → General keeps your workspace’s website: the page Preview mirrors and Record on your site opens. Owners and admins can change it there, after confirming with two-factor authentication. Changing it doesn’t add, verify or remove a domain, and your production snippet keeps working where it already did. If the new website is on a hostname you haven’t verified, add it here so the guide runs there too.Sub-apps in frames
If parts of your product load in an iframe from another of your domains, the guide can work inside them too (Sub-apps in iframes). In Dashboard → Install → Sub-apps in frames, owners and admins allow each sub-app’s exact origin, likehttps://billing.example.com. It must be on a domain you verified here, or a
subdomain of one; adding it asks for your second factor, like adding a domain. The
guide never contacts an iframe from any other origin. It acts inside an allowed
sub-app only where you turn on Allow actions in this frame for it (off by default).
When a boot is refused
Puntego records why it refused a widget (for example “that domain is not verified for this workspace” or “the page uses http://”) and shows the latest refusal on Dashboard → Install, so an unverified host never fails silently.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.