Verified domains
Allow the AI surface scan’s active port checks on a host you control, and nowhere else.
Before you start
Section titled “Before you start”- A Keryn Cloud account (sign in).
- Control of the domain: either its DNS, or the web server that answers on it.
- In Cloud, under Domains, type the domain (
example.com) and press Add domain. Keryn shows a token. - Publish the proof in either place:
- a DNS TXT record
keryn-verification=<token>on the domain, or on_keryn.<domain>; or - a file at
https://<domain>/.well-known/keryn-verification.txtthat containskeryn-verification=<token>.
- a DNS TXT record
- Press Check proof. The row shows the domain as verified.
- In AI surface, enter a host under that domain. The Active port checks switch is now available. A scan with the switch on costs 1 credit.
Rules the proof follows
Section titled “Rules the proof follows”- The proof must still be in place. A verification counts for 30 days, and at scan time Keryn looks for the TXT record or file again. If you removed it, or the domain changed hands, the active scan is refused: re-verify.
- Subdomains of a verified domain count; the limits below are keyed on the verified domain.
- Active scans are rationed. At most 3 a day per verified domain, and at most 3 a day per resolved address across all accounts, so a domain pointed at someone else’s server cannot be used to hammer it.
- Ports other than 80 and 443 are scanned (trust scan, MCP scan) only on a verified domain.
- A single account holds at most 20 domains, and 10 verification checks an hour. Checking the proof counts against the scan budget.
Everything that needs no proof stays passive: reading public pages, reading well-known paths, an MCP handshake and lists.
What you just proved
Section titled “What you just proved”You can show that a probe only ever touched a name whose owner asked for it: the proof is in the domain’s own DNS or web root, it expires, and it is checked again at scan time.