#018Tutorial2 min

Prove you own or may test a domain

The two accepted methods, DNS or HTTPS file, and how to choose the easier one for you.

Hackaiz team · updated 20/11/2026

Illustration: a person sets up an account on a laptop.
Illustration: a person sets up an account on a laptop. Illustrative photo, not a screenshot.

01Why proof is required

Analyzing a site without its owner’s consent can be illegal and harmful. Hackaiz therefore requires proof that you control the exact domain before sending any request to it. Until the proof is validated, the Analyze button stays disabled for that site.

Proof applies to one host: www.example.com and app.example.com are two separate proofs.

02Three ways, from easiest to most technical

All three give the same proof. On Connect, Hackaiz highlights the one that fits your address: on a builder-provided address (for example myapp.lovable.app) only ways 1 and 2 work, because the platform owns the DNS.

  1. 11. Copy the instruction for your AI: click “Copy the instruction for my AI” and paste it into Lovable, Bolt, Replit, v0, Cursor, Codex, Claude Code or any AI that edits your project. It creates public/.well-known/hackaiz-verification.txt with the exact value; then publish, and Hackaiz rechecks on its own every 30 seconds for 15 minutes. ChatGPT or Claude as a plain chat, without project access, cannot do it: use way 2 instead.
  2. 22. Create the file yourself: on Vercel, Netlify, GitHub Pages, Cloudflare Pages or your own server, create that file, paste only the value (it starts with hackaiz-verification=), then publish.
  3. 33. DNS TXT: for a custom domain whose site cannot serve the file (WordPress, Wix, Shopify, site behind sign-in), add a TXT record named _hackaiz at your registrar with the same value.

03Validate the proof

From Connect, choose the method, copy the value, publish it, then click Verify now. Once validated, the proof shows an expiry date; you are reminded before it expires.

04If the site is not yours

For a client’s site, get their written authorization and ask them to publish the proof or give you access to the DNS settings. To test an external component you do not own, use the “Check an external component” path, which does not analyze any site.

Tip: The HTTPS file is often easier with Vercel, Netlify, Lovable or Bolt: put it in public/.well-known/ and redeploy.

Frequently asked questions

Was this article helpful?

Related articles