No URI supplied
This page resolves the rttp URI scheme. Pass a URI in the uri query parameter:
Or, if the rttp:// protocol handler is registered on this machine, open it directly from your operating system.
This page resolves the rttp URI scheme. Pass a URI in the uri query parameter:
Or, if the rttp:// protocol handler is registered on this machine, open it directly from your operating system.
rttp:// is the URI scheme of RFC-002 — RTTP (Resonant Time Transfer Protocol), the neural layer of the Aicent Stack. Its authority field is not a hostname: it is a claim of intent against an AID, written as three dot-separated labels.
| intent | The AID's routing hash — exactly 8 lowercase hex digits — or a readable organ token such as brain |
| pillar | A registered pillar label — one of the seventeen of the Aicent Stack (see the table below) |
| root | The sovereign root label — aicent. The scheme itself does not resolve via DNS |
| action | Optional intent verb. When omitted, the default operation applies: one pulse — the specification states it is safe, creating no obligations and mutating no substrate state |
This resolver only displays what it parsed. The uri parameter is never used as a navigation target — see “Security” below.
Stated by the specification (RFC-002 §10.5):
rttp URI is a claim of intent against an AID. The routing hash is an entry fingerprint, not a proof of identity; identity is carried by the AID (RFC-001) and attested in-band by the RPKI tensor watermark (RFC-003).rttps and no protocol fallback: user agents that do not implement this scheme fail closed.userinfo is not defined, credentials cannot appear in an rttp URI.authority component is pseudonymous, not anonymous, and appears in logs.About this page (not part of the specification): the uri parameter is validated and displayed, never followed, and every outbound link comes from the fixed pillar table above — so this page cannot be used as an open redirect. 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 rttp://… 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=rttp%3A%2F%2Freturn.guixu.aicent.
| path | what it takes | verified on |
|---|---|---|
| rttp:// | a one-time per-user registration of the scheme with your operating system — no administrator rights, reversible with one command | Windows: Chrome & Edge |
| web+rttp:// | nothing installed — you approve this site's request to handle web+rttp once, in your browser |
Windows: Chrome only, so far |
A browser can only launch a scheme it knows about; typing an unregistered one just runs a web search. Registering rttp:// 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\rttp. On macOS / Linux: a URL-scheme declaration in an application bundle / a .desktop file with x-scheme-handler/rttp. Browser extensions and installed PWAs can also claim a custom scheme themselves — note that web-platform registration is limited to web+rttp: for schemes not on the browser's own list.
The rttp scheme registration is in progress with IANA. This page implements the syntax as specified in RFC-002; it is not a statement about any future revision of that specification.