Why Is My Domain Unverified on PandaONE? (Domain Ownership & Verification Guide)

Why Is My Domain Unverified on PandaONE? (Domain Ownership & Verification Guide)

2 min read

pandaone · dns · domain-verification · security-testing · troubleshooting

Authors

PandaONE Security & Engineering Team

Learn why PandaONE requires domain ownership verification before running vulnerability scans, how to configure TXT or HTML verification records at your DNS provider, and how to resolve pending verification issues.

You added the TXT record an hour ago. The dashboard still shows Unverified. That usually means the checker cannot see your token yet — propagation, wrong host name, or a WAF in front of the HTML file path.

PandaONE blocks offensive scans until it can confirm you control the hostname. Scans, subdomain discovery, and proof packs run only after verification succeeds.

Token format

When you add a domain, the dashboard issues a token like:

pandaone-verify=a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6

You can prove control two ways.

FieldValue
TypeTXT
Host_pandaone-verify or _pandaone-verify.yourdomain.com (provider UI varies)
TTLAuto or 300
Value"pandaone-verify=<YOUR_TOKEN>"

HTML file

Serve plain text at:

https://yourdomain.com/.well-known/pandaone-verify.txt

Body is the same pandaone-verify=<YOUR_TOKEN> string. Response must be HTTP 200 with no redirect to login.

More detail: Learn → Domain verification and the DNS TXT walkthrough.

Still Unverified?

DNS not visible yet

TTL and provider caching mean public DNS can lag from a few minutes to about 24 hours.

dig +short _pandaone-verify.yourdomain.com TXT

Empty output → wait, fix the record, or both. Click Verify Domain only after dig shows the token.

Wrong host name

  • Cloudflare, Route53, GoDaddy, and similar: host field _pandaone-verify only; the UI appends the zone.
  • FQDN-only UIs: use _pandaone-verify.yourdomain.com.
  • Common mistake: TXT on apex @ instead of _pandaone-verify.

Token typos

Match the dashboard string exactly — keep the pandaone-verify= prefix, no trailing spaces.

HTTP path blocked

For the file method: WAF or bot rules that block GETs to /.well-known/pandaone-verify.txt, or redirects (301/302) and 403 responses, will fail verification.

Fix it in order

  1. Copy the token from Dashboard → Targets / Domains → Verification Details.
  2. Publish TXT at _pandaone-verify or deploy the .well-known file.
  3. Confirm with dig (DNS) or curl -sSI on the file URL (HTTP).
  4. Click Verify Domain.

Checklist

  • TXT on _pandaone-verify, not @
  • Value is pandaone-verify=<token> with no extra characters
  • dig returns the TXT (or the well-known URL returns 200)
  • Verify Domain clicked after the record is public

Sources & further reading

Featured on ScrollLaunchFeatured on CodeHype