Sign in

Help centreSecurity work

Security scans and proving you own a domain

Utah only scans domains you have proved you own. Exactly what it checks, and which scans you can run.

Checked against the product · 14 November 2026

Utah runs security scans only against domains you have proved you own. Every scan, including the posture check, needs a verified domain. Without one you see “Verify ownership in Target & tools before running a scan.”

Prove you own a domain

  1. Add the domain as a target with Add target. Utah gives you a verification value that begins with utah-verification=.
  2. Publish that value in one of two places: a DNS TXT record named _project-utah. followed by your domain (for example.com, that is _project-utah.example.com), or a file at https://example.com/.well-known/project-utah-verification.txt.
  3. Verify. When it passes you see “Domain ownership verified”.

What the check looks for

  • The TXT record, or a line of the file, must equal the value exactly.
  • The file must be served directly over HTTPS, because redirects are not followed, and be no larger than 4 KB.
  • The file is only fetched if every address your domain resolves to is public.

If the check does not pass, the message reads “Ownership was not verified. Publish the exact verification token as the TXT record or HTTPS file, check public DNS and HTTPS availability, then retry.”

In an Attack chat you can do the same with /target example.com and then /verify.

Scans you can run

ScanWhat it covers
Full toolchain10 tools · web + source
SubfinderPassive subdomain map
HTTPXHTTP · tech · TLS probe
Nmap1,000 ports · services · scripts
testsslProtocols · ciphers · certificates
NucleiFull CVEs · exposures · misconfig
ffufHidden routes · files
sqlmapInjection validation. Needs a URL with a query parameter.
SemgrepReachable source defects. Needs source code.
TrivyDependencies · config · secrets. Needs source code.
GitleaksCredential exposure · redacted. Needs source code.

Check posture is a lighter check. It reads public pages of your site and reports on security headers, cookies, security.txt and error pages. Its report says these are observed configuration checks, not a certification.

Where scans can go

  • Scans stay on the verified domain and its subdomains, on ports 80, 443, 8080 or 8443.
  • The target has to resolve only to public addresses.

Still stuck?

Check the status page for a known problem, or send a message to support.