Nothing erodes a developer's trust faster than a documented endpoint that does not resolve. In September 2026 EmpoorioChain's documentation was audited host by host against DNS and TLS. This is what was found and what the ecosystem does about it now.
What resolves
| Host | Serves | Verified |
|---|---|---|
rpc.testnet.empooriochain.org | JSON-RPC over HTTPS and WSS, node 1, port 9944 behind nginx, own valid TLS | 2026-09-12 |
rpc2.testnet.empooriochain.org | Same, node 2 | 2026-09-12 |
empooscan.com | EmpooScan explorer (site live; indexer database pending) | 2026-09-12 |
www.empooriochain.org | Chain website (the bare apex does not serve) | 2026-09-12 |
api.ailoos.com | The Ailoos API — /health returns healthy | 2026-09-08 |
Five. That is the complete list of network-facing hosts a document may cite.
What never existed
ws.empooriochain.org— used 21 times in developer guides as the WebSocket endpoint. NXDOMAIN.api.testnet.empoorio.org,api.devnet.empoorio.org,api.mainnet.empoorio.org,api.mainnet-beta.empoorio.org— the RPC page listed all four. None resolve; there is no devnet and no mainnet.explorer.empooriochain.org,scan.empooriochain.org,explorer.empoorio.org— cited as the explorer, including in the wallet's chain configuration. The explorer isempooscan.com.telemetry.empooriochain.org— the validator guide told operators to report to it. Dropped.faucet.empoorio.org— the quick start sent developers to it. There is no faucet.docs.empoorio.org,status.empoorio.org,forums.,platform.,podcast.,mcp.,climate.,launch.— all under the official domain, none resolving.empoorio.io— the entire domain is unregistered. The grants programme, the hackathon plan and the exchange-integration guide gave their RPC, explorer and faucet URLs under it.
Why it happened
The documentation was written ahead of the infrastructure, and hostnames were invented to fill slots in templates. When the infrastructure arrived it used different names, and nothing reconciled the two. A developer following the docs could not connect, and a developer who did connect could not tell which document to believe.
The rule
RED.json holds the five hosts and states: only these may appear in code, configuration and documentation as endpoints. A host that does not resolve is not cited — not even as an example. Hosts that resolve but serve nothing are listed separately so nobody "fixes" a document by pointing it at one. A tree-wide sweep on 12 September confirmed no live citation of a non-resolving host remains; historical mentions are annotated as historical.
For integrators
If a document — this blog included — gives you a hostname not in the table above, the document is wrong and RED.json is right. The two RPC endpoints rate-limit at roughly 10 requests per second per IP with a one-hour ban; run a node for anything heavier.
Based on RED.json v1.2.0 hosts section and the September 2026 documentation audit.