• Guide
Domain verification: prove you own the target
PandaONE requires domain ownership verification before vulnerability scans and AI pentest phases run. You verify with a DNS TXT record and/or an HTML file in /.well-known/.
Or scan your domain. Stuck on Unverified? See the troubleshooting blog.
What verification is
When you add a domain, PandaONE issues a unique token shaped like pandaone-verify=<token>. You publish that token where only the domain owner can — DNS or the web root — then click Verify Domain. Until the check succeeds, the target stays Unverified / Pending and offensive work stays locked.
This is authorization hygiene, not busywork: continuous AI testing without ownership proof would risk scanning third-party sites.
Method 1
DNS TXT
Publish at
_pandaone-verify— best when you control DNS.Method 2
HTML file
Serve
/.well-known/pandaone-verify.txtwhen DNS changes are harder.
• Method 1 · recommended
DNS TXT step-by-step
1. Copy your token
From the dashboard under Targets / Domains → Verification details.
2. Create a TXT record
- Type: TXT
- Host / Name:
_pandaone-verify(Cloudflare, Route53, GoDaddy often append the zone) or the FQDN_pandaone-verify.yourdomain.com - Value:
"pandaone-verify=<YOUR_TOKEN>" - TTL: Auto or 300 seconds
3. Confirm public DNS
dig +short _pandaone-verify.yourdomain.com TXT
4. Click Verify Domain
Retry after dig returns the token. Do not place the TXT on apex
@instead of_pandaone-verify.
• Method 2
HTML file method
Host a static text file so PandaONE can fetch it over HTTPS:
- URL:
https://yourdomain.com/.well-known/pandaone-verify.txt - Body:
"pandaone-verify=<YOUR_TOKEN>" - Status: HTTP 200 OK (no auth wall, no redirect loop to login)
WAF / bot rules that block automated GET to /.well-known/ will leave the domain unverified.
Troubleshooting
Propagation
Empty dig output means the record is not public yet — wait and recheck; do not assume the dashboard is wrong.
Wrong host
TXT on
@or a typo in_pandaone-verifyfails. Match provider host vs FQDN conventions.www vs apex
Verify the exact hostname you added. Scanning www does not auto-verify the apex (and vice versa).
Token formatting
No trailing spaces; keep the
pandaone-verify=prefix exactly as shown in the dashboard.
Longer walkthrough: Why is my domain unverified? · DNS TXT walkthrough