This page has a cookie banner.
A real one — with the reject button hidden one step deeper, the way most of them are built. If you can see it, BannerBye isn't running. If you can't, it just refused it for you.
Watching the banner…
It's at the bottom of the page. Don't touch it.
- 0 ms page started, banner in the HTML
What the banner does
It's wired like the ones you meet in the wild. Accept all is one click and sets a cookie that says you agreed to everything. Reject all isn't on the first screen: you have to open Manage settings first, then find it. That extra step is the whole business model — most people click the blue button.
BannerBye doesn't. On this page it finds the banner, opens the settings step, clicks Reject all and clears the banner — before the page has finished painting, if it can. Then it tells you so in the popup, under this site.
Which layer did the work
This banner is deliberately dumb: no consent platform, no IAB TCF, no handler to recognise it. So the first four layers have nothing to grab. What refuses it is the fifth: the pattern-based fallback that reads the buttons the way you would — and knows that "Manage settings" is a door, not an answer. On most real sites one of the earlier layers gets there first and the banner never draws at all. All five layers, explained.
Try it on something harder
The signal check decodes the consent string BannerBye hands to every TCF site, field by field. And any site in the wild that still shows you a banner: open BannerBye, hit Report broken site, and it lands on the public fix log.