Five bonus pages that did not open, and what stood in front of each one
Stake, MyStake, Jackbit, BetFury and Gamdom. Eleven attempts between them, the longest thirty seconds. Not one of the five pages rendered, so not one figure from them appears anywhere on this site.
Eleven operator pages were opened on 28 September 2026 from a single address. Six of them rendered. This page is about the other five.
It exists because of a rule: a figure reaches this site only from the operator's own page, with the address and the date printed beside it. When the page does not open, the rule produces a blank — and a blank on a site about bonus codes looks like a failure unless somebody explains it. So here is the explanation, in full, attempt by attempt.
Schedule B — the five pages that did not open
| Casino | Address | What stood in the way | Attempts |
|---|---|---|---|
| Stake | stake.com/promotions | Security verification screen | 3, longest 30 s |
| MyStake | mystake.com/en/promotions | Security verification screen | 2, longest 25 s |
| Jackbit | jackbit.com/promotions | Security verification screen | 3, longest 30 s |
| BetFury | betfury.io/bonus | Region refusal, then “Page is not found” | 1 |
| Gamdom | gamdom.com/promotions | Country refusal naming the Netherlands | 1 |
The three verification screens
Stake, MyStake and Jackbit were each stopped by the same kind of obstacle: a security service checking whether the visitor is a browser or a script, displayed as an interstitial page while the check runs.
We tried Stake three times. The first attempt went straight to stake.com/promotions with a fifteen-second wait. The second and third loaded stake.com/ first — so that an ordinary browsing session and its cookies could be established the way a real visit does — and then the promotions path, thirty seconds each. The screen held on all three.
MyStake, twice: mystake.com/en/promotions directly, then the site root first, twenty-five seconds each. Same outcome.
Jackbit, three times, the longest wait thirty seconds. Its interstitial printed a Ray ID, which is a useful detail — it confirms a security service is doing the checking rather than the site simply being broken.
All three readings were made with a real browser, at a real screen size, with an ordinary desktop user agent and English as the accepted language, from the same machine that read the six pages that did open. Nothing was disguised, and nothing about the requests was unusual.
Why we stopped there
A verification screen can be defeated. There are patched browsers, fingerprint spoofers and paid services that solve challenges on request. We are not going to use any of them, and the reason is not squeamishness.
A defeated check produces the wrong reading. The point of opening an operator's page is to see what an ordinary visitor sees. A page fetched by something pretending to be something else is not evidence about an ordinary visitor; it is evidence about the pretence. A figure obtained that way would have a date and an address beside it and would still be worth less than the blank.
The blank is the more useful output. “Stake's promotions page did not render for an ordinary browser on 28 September 2026, three attempts” is a true, dated, checkable statement. Anyone can repeat it. “Stake's promo code is XYZ123, worth a 200% match” is a claim with no verifiable source at all, and it is what the rest of the first page of results consists of.
The two refusals
BetFury and Gamdom did not challenge us; they declined us.
Gamdom's page was a single notice: ”Gamdom Is not Available In your Country”, with the country named — the Netherlands — a short explanation about regulatory restrictions, a support address and a cookie banner. That was the entire page.
BetFury's was stranger: a panel reading ”Unfortunately, BetFury is not available in your region”, and behind it the bonus path itself returning ”Ooops… Page is not found.” Its footer did render, and gave us a company and a licence number, which is the whole content of the BetFury sheet.
A refusal of this kind is not something a code, a promotion or a reading technique changes. It is the operator's answer to the question of whether it will do business with an address, and the answer arrived before any question about bonuses could be asked.
What we will not print, and what that costs
Between them, Stake, MyStake and Jackbit account for more searches for a promo code than everything else on this site except Roobet. Every one of them has pages of results offering a specific string with a specific offer attached.
We cannot confirm any of it. We also cannot deny any of it — which is worth saying clearly, because a page that reads as an accusation would be as dishonest as one that reads as a recommendation. The codes may well be real. Operators routinely issue codes to partners without printing them publicly, and that is an ordinary commercial arrangement, not a deception.
What we can say is narrow and, we think, more useful than a guess: on 28 September 2026 an ordinary browser could not open these operators' own promotions pages, so nobody reading a code for them from us or anyone else can check it against the source. Treat the string as a claim, open the cashier before depositing, and give the percentage, the ceiling and the playthrough more weight than the string.
When this page changes
Each row here keeps the date of its last attempt until there is something to replace it with. If a page opens on a later reading, it gets a sheet of its own like the five operators that did render, and it leaves this list. A figure never appears here by being borrowed in the meantime.
The pages that did open are Roobet, BitStarz, Rainbet, BC.Game and TrustDice. The rule that produced all of this is set out on how we read a bonus code.