A 404 that was really a provisioning gap
Three paths returned 404 on a Firebase Hosting domain while DNS resolved cleanly to an anycast address. The instinct is to look for a deleted release. That instinct is wrong about the mechanism.
Why the DNS check is useless here
*.web.app resolves whether or not a site exists in any project. A resolving hostname therefore says nothing about deployment state. Only an HTTP status on a real path does.
The check order that worked
- HTTP status on /, /robots.txt and /sitemap.xml — three 404s rule out a single missing page.
- hosting:sites:list against the project — the site name was already claimed and attached to a placeholder.
- Compare with the target and targets block in .firebaserc — the deploy target pointed at the right site, so the gap was content, not routing.
What this changes about deployment reviews
"The domain is live" and "the domain serves the application" are different claims. A hosting slot with a placeholder answers 200 and still delivers nothing. The verification that matters is content parity: fetch the deployed page and diff it against the repository HEAD, not against the deploy log.