# domain\_verify

Source: <https://telegafirst.com/docs/mcp-tool-domain-verify>
Locale: ru
releaseGitSha: 0bb11ef116e17ec64c802d5476eaff442e53d252
sourceContentDigest: 0b55da5f5f0524fe43093b40fc16aa6d85c53056e0709c2eb1704dc50de9bedf
Version: 8

# domain\_verify

Check the ownership TXT record for a connected domain RIGHT NOW and, if it matches, move the domain to VERIFIED (the certificate is then issued on the first HTTPS request). Call it after telling the owner to publish the record from \`domain\_add\_request\`. Safe to call repeatedly: an already-verified domain answers \`verified: true\` and nothing moves. When it is not verified yet, \`pendingReason\` says WHY in the owner's terms — \`nxdomain\` (the record is not there at all), \`mismatch\` (a record with the wrong value — usually a truncated paste), \`ambiguous\` (several records, none ours — usually an old token left behind), \`timeout\` / \`resolver\_error\` (their nameserver did not answer). DNS propagation is bounded by the owner's own TTL and is routinely hours, so \`nxdomain\` shortly after they publish is normal — nothing is broken. The platform also re-checks in the background, so an unattended domain still completes on its own.

## Права и условия

required\_scopes: ALL.

| Поле | Значение |
| - | - |
| description | "Check the ownership TXT record for a connected domain RIGHT NOW and, if it matches, move the domain to VERIFIED (the certificate is then issued on the first HTTPS request). Call it after telling the owner to publish the record from \`domain\_add\_request\`. Safe to call repeatedly: an already-verified domain answers \`verified: true\` and nothing moves. When it is not verified yet, \`pendingReason\` says WHY in the owner's terms — \`nxdomain\` (the record is not there at all), \`mismatch\` (a record with the wrong value — usually a truncated paste), \`ambiguous\` (several records, none ours — usually an old token left behind), \`timeout\` / \`resolver\_error\` (their nameserver did not answer). DNS propagation is bounded by the owner's own TTL and is routinely hours, so \`nxdomain\` shortly after they publish is normal — nothing is broken. The platform also re-checks in the background, so an unattended domain still completes on its own." |
| domain | "domain" |
| name | "domain\_verify" |
| platform\_version | "1.0.20" |
| required\_scopes | \["domain:write"] |
| risk | "write" |
| scope | "domain:write" |
| title | "Domain Verify" |

## Входные параметры

[domain\_verify: inputSchema](https://telegafirst.com/docs/schema-a3f731773b01935be29bb022334a36890f8ce3e5f17c4c9c4e4bce2f1dde285b)

## Результат

null