) designed for "unblocking" to route your traffic through a different server. These are commonly used to access web apps hosted on Vercel. Change DNS Settings

She added a hidden kill switch: a request header X-Secret-Egg: true that would log the user's intent. Most never used it. But one did—a teacher in a remote town who wrote in the logs: "Thank you. My students saw the world today."

With data in hand, she wrote the final piece of the puzzle: a small README that explained the behavior, a set of instructions for users stuck behind the same filters, and an offer — not to provide a magical unblocker, but to share the relay she’d built and the safe, transparent techniques for diagnosing blocks. The README started with a line that felt like a promise: "If your browser shows Access Denied for vercel.app, here's how to figure out whether the problem is yours, theirs, or somewhere in between."

At first, lighthouse did nothing. The browser still spat "Access Denied." But the logs told a different story: her relay was receiving the site just fine. The HTTP responses carried the app's HTML, the CSS, the tiny SVGs of color swatches — mirrored faithfully. The network that blocked vercel.app hadn't blocked her relay. That suggested the denial lived in the valley between domain and human: a corporate gateway keyed to domain names, or a browser extension with a blacklist, or some walled garden she could not see.