#019Tutorial4 min

Verify a domain with a DNS TXT record

Publish the current Hackaiz challenge at the exact DNS name, check it, and record your authorization.

Hackaiz team · updated 21/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.

01Check who manages the exact hostname

DNS is the directory that associates a domain with technical records. A TXT record stores text alongside those records. Hackaiz uses a specific text value to establish that you can control the hostname you want to analyze. Adding that proof is not a website security analysis and does not grant permission to inspect other domains belonging to the same organization.

Before starting, identify the provider that actually hosts the domain’s DNS zone. It may be different from the company hosting your application. You need permission to add a TXT record there. If the site uses an address owned by an application builder, you may not control its DNS at all. In that case the interface favors file proof: publish the HTTPS verification file yourself or ask the project’s AI assistant to create it. Do not try to edit the builder’s parent domain.

02Create the record from the current challenge

In Connect, enter the intended site address and find “Prove you own this domain”. Select “Via DNS (TXT)”. Hackaiz displays a full record name such as _hackaiz.app.example.com and a value beginning with hackaiz-verification=. Copy the current value with “Copy”; the example name in this article is not a usable challenge.

In your DNS provider’s editor, choose the TXT record type. Some editors ask for a full name; others automatically append the zone name. If the zone is example.com and the requested full name is _hackaiz.app.example.com, an editor that appends the zone usually expects _hackaiz.app. Check the resulting full name before saving so that example.com is not accidentally appended twice. Put the Hackaiz challenge in the text-value field, not in the record-name field.

  1. 1Keep the Hackaiz page open so you can compare the exact hostname and current challenge.
  2. 2Add a new TXT record at the displayed name without replacing unrelated mail or domain-verification records.
  3. 3Paste the complete challenge value without adding explanatory text, then save the DNS change.

03Wait for publication and verify deliberately

Return to Hackaiz and click “Verify now”. The verifier looks for the TXT record at _hackaiz followed by the exact hostname, and compares its text with your current challenge. A record for _hackaiz.example.com does not validate app.example.com. DNS publication and caching can delay visibility, so a successful save in your provider’s editor does not necessarily mean the public record can already be read.

If the interface says “Value not found”, compare the full record name and the copied value before creating more records. Remove accidental spaces or extra words in the submitted value and make sure you edited the authoritative DNS provider. If the challenge has expired, begin a new verification and publish the newly displayed value. Do not keep retrying an old challenge after replacing it. A service-unavailable message calls for a later retry rather than changing your site configuration.

04Separate control proof from permission to test

When the panel shows “Domain verified”, it also displays the proof’s validity date. You still need to tick the declaration that you have the right to authorize Hackaiz to analyze the website within this domain without destructive tests. The analysis remains a separate action: publishing the TXT record does not launch a scan. Review the selected checks before confirming; analyses consume credits, and unticked checks are not run or billed.

For a client domain, ask the domain administrator to publish the record and make sure the necessary mandate is in place. A technical change in DNS cannot establish the legal scope of your engagement. If access should end, use “Revoke authorization” in Hackaiz rather than assuming deletion of the TXT record is an immediate revocation of a previously validated proof. That control revokes the recorded proof and website authorization. Plan a fresh verification if you later need to analyze the hostname again.

Frequently asked questions

Was this article helpful?

Related articles