Muhammad Hamid.

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

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.

← All notes