Status
Checked from your browser.
Each row below is one request your browser makes when this page loads, with the time it took. No photograph is sent. A row stays grey until its answer comes back.
Checking from your browser…
-
The site GET /docs.html — must answer 200, be HTML, and be the API reference. On this deployment a status code proves nothing: any path answers 200 with the homepage, so only the body counts.not checked yet
-
The door's handler OPTIONS /api/triage — proves the handler is on this deployment and ran its preflight. It runs before the rate limit and spends nothing.not checked yet
-
The door's error table GET /api/triage — proves the module loaded and its designed refusals are intact: a wrong method gets a 405 in JSON, not a page.not checked yet
-
The engine None of the rows above reads a photograph. A green here would be a lie. The only browser-side proofs are the tap below and a real photo dropped on the card.not checked from your browser
-
Our own five-minute probe The box that watches the door from outside writes to a place a static page cannot read. Not on this page yet.not on this page yet
This spends one of the 20 requests an address is allowed per hour (a floor: each warm instance counts on its own). It sends no photograph; the door should refuse it. Nothing is sent until you press it.
not sent