Who owns the ground under your trusted endpoint? A continuous tenure verdict graded against the day you approved it - expiry, re-registration, jurisdiction drift - from registry witnesses, never from probing the endpoint.
An endpoint in your fleet's configuration was trusted on approval day. Months later its domain can expire, lapse, and be re-registered by someone else who stands up a server preserving the copied contract - every probe reads LIVE, every contract hash matches, and the owner underneath is no longer the owner you approved. Endpoint Tenure Verdict watches the ground, not the server: at enrollment it snapshots an approval-time baseline from a registration witness (authoritative-registry RDAP via the IANA bootstrap) plus a resolution witness (DNS + IP-allocation country), then grades tenure continuously in six named classes - TENURE-STABLE / EXPIRING (alerts at 30/14/7 days) / REGISTRANT-CHANGED / JURISDICTION-DRIFTED / LAPSED-REGISTERABLE / RE-REGISTERED - plus a named UNVERIFIABLE when a leg cannot be verified either way. Joined with a probe witness, probe-LIVE x tenure-changed issues one disagreement receipt graded HIJACK-SUSPECT.
Stated plainly: TLDs with no RDAP service in the IANA bootstrap (.io, .co, .so - including modelcontextprotocol.io) grade UNVERIFIABLE by design; an authoritative 404 alone never grades LAPSED (DNS non-resolution must corroborate); jurisdiction is IP-allocation jurisdiction; change legs exist only for endpoints enrolled with a baseline; demand and willingness to pay are unmeasured.
Status: Live
Docs: /docs - OpenAPI: /openapi.json - Terms: /terms - Privacy: /privacy
Support: support@textforagents.com