Before NANOTESTING runs a full external scan, it makes you prove you own the target. Unverified targets only get a passive preview. This is not bureaucracy; it is the line that keeps the platform from being a free scanner pointed at strangers.
Method 1: DNS TXT record
Add a TXT record to the target domain with the value the dashboard gives you. This proves control of the domain itself, which is the strongest signal. It is the right choice when you manage DNS and want the verification to persist across subdomains and paths. Propagation usually clears within a minute or two, and the dashboard has a one-click recheck.
Method 2: HTML file
Drop a small file at a fixed path on the site. This proves control of that specific host. It is handy when you do not own DNS for the domain but you do control the web root, or when you want to verify a single app quickly without touching DNS.
Which to pick
If you control DNS, use the TXT record; it is cleaner and covers more. If you only control the web server, use the file. Either way, verification is a one-time step per target, and it unlocks the full external baseline scan. Lose control of the target later and re-verification protects you and everyone else, which is exactly the point.