Surfaces

A status code is not a state. Two hostnames returning an identical 404 can mean completely different things: one was switched off on purpose and is behaving correctly, the other is an accident nobody has noticed. Collapsing that distinction into a single "404" cell once cost this fleet a P0 incident — a master was dispatched to "restore" a surface that had been deliberately retired ten days earlier, and it did exactly as it was told.

So every row below carries a class, and the class is the durable fact. The status code is evidence for the class, not a substitute for it.

A fourth label, NEVER-EXISTED, is used at the bottom of the page for names that appear in the fleet's own documents but have never resolved in DNS. They are not surfaces; they are citations of surfaces that were never built.

All codes below were measured by the run that wrote this page, 2026-08-16, from novaserver. They are evidence with a date on them, not a live reading — for current codes, see /live.

A dated table decays, so this one is re-measured rather than trusted: /live parses the class column straight out of this page and probes every host in it on each request, which means adding a surface here adds a check with no edit anywhere else. Two rows have gone stale that way. creatives.utopiamodels.ai was recorded as 200 until the 5am domain landed and the migration redirect fired — stale because the world moved, not because it was measured wrong, which is the failure a re-measure catches and a careful first reading cannot. And docs.utopiamodels.ai — this host — has now changed root shape twice: a 307 to /docs when this page was written, then a 301 off the host entirely while it was retired, and today a plain 200 (see its row below).

LIVE

RETIRED-BY-DECISION

BROKEN

NEVER-EXISTED

These names are referenced in the fleet's own documents and have never resolved. A citation is not a surface: each of these exists only as a string in a markdown file.

How this table is kept honest

Three rules, learned the expensive way:

1. A hostname with no registry row cannot be monitored, so it cannot be noticed. Several of the LIVE rows above have no entry in the fleet's component registry — including one serving on the company's own domain. No row means no check, and no check means the day it breaks is the day someone happens to look.
2. A 200 does not prove a page is public — and neither does redirects=0. An SSO gate redirects to a login page that itself returns 200, so a check has to report redirects= and the final URL, not the status code alone. The converse is the trap this page shipped with: an app that renders its login in page answers 200 with redirects=0 and is completely gated. credentials.utopiamodels.ai, two tables up, is exactly that — and a stranger's agent reading this rule correctly concluded from 200 redirects=0 that our secret store was open to the world. A status line only ever supports the claim "something answered". Read the body.
3. Which edge served it matters. cf-ray means Cloudflare; x-vercel-id means Vercel; both together means Cloudflare in front of a Vercel origin. A doc that says a hostname "does not touch the tunnel" is a claim about routing, and routing is checkable in one curl -sI.