Verify domain ownership

Endpoint Discovery works on any public domain, but a few of its more powerful options (your plan's real check interval, and creating monitors for write-method API operations) are gated behind proving you actually control the domain. This page walks through both verification methods.

HowlOps supports two methods. They're equivalent, pick whichever is easier for you:

• DNS TXT record — best if you control DNS for the domain. Covers the whole domain, including subdomains.
• .well-known file — best if you can publish a file on the web server but don't manage DNS yourself.

Where to start

1. Run a scan on your domain from Monitors → Discover from a domain.
2. If the domain isn't verified yet, a Verify <domain> to unlock panel appears above the results.
3. Choose a method and click Start verification. HowlOps generates a token and shows you exactly what to publish.

Verification is scoped to your workspace and the exact domain you scanned; it doesn't affect other tenants and other tenants can't verify or unverify a domain on your behalf.

Method 1: DNS TXT record

1. In the verification panel, select DNS TXT record and click Start verification.

2. HowlOps shows you a TXT record to add:

   Field	Value
   Type	TXT
   Host / name	_howlops-verify.<yourdomain>
   Value	howlops-verify=<token>

   The exact value (with your real token filled in) is also shown as copyable text in the panel.

3. Add this record in your DNS provider's control panel.

4. Back in HowlOps, click Check now.

DNS propagation can take anywhere from a few seconds to a few minutes depending on your provider; if the check doesn't succeed right away, wait a bit and click Check now again.

Method 2: .well-known file

1. In the verification panel, select Well-known file and click Start verification.

2. HowlOps shows you the exact URL to publish the file at:

   https://<yourdomain>/.well-known/howlops-verification.txt
   

3. Create that file on your web server so it serves your token as plain text, and nothing else (leading/trailing whitespace is fine; the content otherwise has to match exactly).

4. Back in HowlOps, click Check now.

This method proves you control that specific host, not the whole domain's DNS.

What each method checks

Both methods work off the same token; HowlOps checks whichever method you started with and flips the domain to verified as soon as it finds a match. Re-starting verification for a domain that's still pending reuses the same token, so instructions you already published stay valid; once a domain is verified, starting verification again just shows its current status rather than resetting anything.

What verifying unlocks

	Unverified domain	Verified domain
Minimum check interval for discovered monitors	60 seconds, even on plans that normally allow faster checks	Your plan's real minimum check interval
HTTP method on discovered monitors	GET or HEAD only	GET or HEAD; OpenAPI write operations (POST/PUT/PATCH/DELETE) can also be created, one at a time, after you explicitly confirm each one
Monitors created per "Create" step	Up to 20	No extra cap beyond your plan's monitor limit

Scanning itself, and creating the recommended (read-only) monitors, works the same either way — verification only raises these specific ceilings; it never blocks the basic discover-and-create flow.

See also

• Discover monitors from a domain
• Plans & capabilities