No URI supplied
This page resolves the iqa URI scheme. Pass a URI in the uri query parameter:
Or, if the iqa:// protocol handler is registered on this machine, open it directly from your operating system.
This page resolves the iqa URI scheme. Pass a URI in the uri query parameter:
Or, if the iqa:// protocol handler is registered on this machine, open it directly from your operating system.
iqa:// is the URI scheme of RFC-009 — IQA (Identity Quality Assurance), the Authority Layer of the Aicent Stack. Its authority field is not a hostname: it names a subject under attestation and the Organ that reports on it, written as three dot-separated labels.
| subject | The AID under attestation — 8, 32 or 64 lowercase hex digits (32-bit routing hash / 128-bit AID / 256-bit AID), or a readable label matching [a-z0-9-]+ |
| organ | Which Authority Organ answers — forge (RFC-009-A) · tss (RFC-009-B) · gateway (RFC-009-C). Closed set. |
| root | The sovereign root label — iqa. The scheme itself does not resolve via DNS |
| action | Optional verb — verify · audit · attest · revoke. Closed set. When omitted, the default operation applies: a standing read, which the specification classifies as safe |
This resolver only displays what it parsed. The uri parameter is never used as a navigation target — see “Security” below.
| organ | RFC | role |
|---|---|---|
| forge | RFC-009-A | Imperial Forge — forges the 256-bit Radiant Seal; manages 12-Cycle Shard rotation |
| tss | RFC-009-B | Temporal Self-Supervision — real-time bit-drift analysis against the Genesis Codex |
| gateway | RFC-009-C | Certification Gateway — renders the final standing verdict; runs the 10,000-pulse Baptism |
organ is a closed set: a label outside these three is not a valid iqa URI, and this resolver rejects the whole URI rather than warning about one field.
Stated by the specification (RFC-009 §11.3):
| action | semantics | class |
|---|---|---|
| (omitted) | Read the current standing | Safe read-only |
| verify | Verify a presented Seal against the subject | Safe read-only comparison |
| audit | Request a TSS fidelity measurement | Not safe may trigger Authority Ischemia |
| attest | Request the Imperial Forge to issue a Seal | Not safe state transition |
| revoke | Withdraw standing | Not safe state transition |
Normative rule (§11.2): Dereferencing an iqa URI, by itself, MUST NOT transition any subject's standing state. The three non-safe verbs MUST be requested explicitly and MUST NOT be reachable by dereferencing a URI that omits action.
A standing read returns the subject's current verdict as reported by the named Organ — one of:
Ghost · Probation · Radiant · Genesis
This page does not compute standing. It lists the four possible values so that the shape of an answer is clear; the value itself can only come from the answering Organ. Parsing a URI establishes nothing about any subject — see §10.4, “Parsing is not attestation”.
Stated by the specification (RFC-009 §12, abridged):
iqa URI is a claim about the attestation standing of a named subject. The hex subject is a routing hint, not evidence; identity is bound by the 256-bit Seal, never by the URI.iqas and no protocol fallback: user agents that do not implement this scheme fail closed.userinfo is not defined, credentials cannot appear in an iqa URI.About this page (not part of the specification): the uri parameter is validated and displayed, never followed, and the only outbound links from this page are the fixed footer destinations — so it cannot be used as an open redirect. A URI that arrives through a browser protocol handler carries the browser's reserved prefix; this resolver folds that prefix away before displaying anything, on every path, so one address is always stated one way. Client-side protocol-handler registration requires explicit user consent in every browser, and the list of registered handlers is not exposed to the network.
Typing iqa://… into the address bar only works on a machine where the scheme has been registered.
On any other machine the browser will simply run a web search. That is expected behaviour — not a failure of this page.
You do not need to register anything to use this page: put any URI in the uri parameter and it will be parsed above. For example
?uri=iqa://3f9a1b2c.gateway.iqa.
| how the address reaches this page | what it takes |
|---|---|
| iqa:// | Either a one-time per-user registration of the scheme with your operating system — no administrator rights, removable with one command — or nothing installed at all, if a web page has asked this browser to open IQA links and you approved it once. The same address either way: the prefix a page must use is the browser's own reserved one, not a different protocol. |
A browser can only launch a scheme it knows about; typing an unregistered one just runs a web search. Registering iqa:// is always an operating-system-level action taken by the user on their own machine — no web page can do it for you.
On Windows: a per-user registry entry under HKCU\Software\Classes\iqa. Separate means apply on macOS and Linux. Browser coverage is per machine and per browser — the sibling rttp handler, which has the same shape, was measured on Windows Chrome and Edge; the iqa handler should be measured the same way on each machine before any claim is made about it.
The iqa scheme registration is in preparation for IANA. This page implements the syntax as specified in RFC-009 §10; it is not a statement about any future revision of that specification.