ApkTie

Home / Shared platforms / The invite-roulette apps

Invite Roulette: Half Visible, Half Behind a Bot Check

This four-app family split cleanly in our check: two sites showed us a full game catalogue and a scrolling withdrawal ticker, two returned nothing but a Cloudflare security check.

4 apps on this template

New 81CC app icon 81CC PK-only 92e 6PPP app icon 6PPP PK-only M91
On this page
  1. The four apps in this family
  2. What we could see on two of the four
  3. What blocked us on the other two
  4. A 16-day-old domain in the same family as a 145-day-old one
  5. What this spread tells us
  6. The game catalogue behind the guessing mechanic
  7. A Cloudflare check looks different from a plain access wall, but the effect is the same
  8. Why two blocked members still belong in the same write-up as two visible ones
  9. What we'd revisit this page for

Every platform family in our directory looks a little different once you actually try to view all its members. This one split down the middle: two of the four apps rendered a full page for us, and two didn't get past a bot check.

The four apps in this family

AppDomainDomain age (26 Sep 2026)What we saw
81CC81cc4.com16 daysFull page
6PPP6ppp9.com110 daysFull page
92e92epk2.com82 daysBlocked
M91m91.store145 daysBlocked

What we could see on two of the four

On 81CC and 6PPP, the homepage carried a scrolling ticker of masked account numbers "successfully withdrawing" specific rupee amounts, a Deposit/Withdraw pair of buttons, and a long list of game providers and titles spanning slots, an Aviator-style crash game, and sports odds. 6PPP's page also showed a live "Guess Number Big/Small/Odd/Even" and "Guess Number Green/Red/Purple" panel, the core colour-prediction mechanic this whole category is built around.

What blocked us on the other two

92e and M91 both returned a Cloudflare security-check page instead of any app content, the standard "verifying you are not a bot" interstitial, on every attempt. We could not get past that screen to see either app's actual registration flow, bonus wording, or game list.

A 16-day-old domain in the same family as a 145-day-old one

81CC's domain was registered just 16 days before our check, one of the youngest in our entire 115-app sample. M91, in the same four-app family, is nearly ten times older at 145 days. A shared template clearly gets deployed on fresh domains and older ones side by side, so domain age alone doesn't tell you which member of a family is the "original."

What this spread tells us

Two visible members show us exactly what the mechanic and marketing look like; the two blocked members might match or might differ, and we're not going to guess. See our methodology page for why we report a block rather than filling in assumed content, and our colour-prediction category page for how this guessing mechanic compares across the wider set.

The game catalogue behind the guessing mechanic

On the two visible sites, the colour and number guessing panel sits alongside a long secondary catalogue: named slot and live-casino providers, an Aviator-style crash title, and a sports-odds section listing multiple sportsbook brands. The guessing game is the headline feature, but it's bundled inside a much wider betting menu rather than standing alone as a single simple app.

A Cloudflare check looks different from a plain access wall, but the effect is the same

Our records flag both 92e and M91 as geoblocked, the same classification we give the fully-restricted agency center family. Here, though, the mechanism showing up on our end was a Cloudflare "verifying you are not a bot" challenge rather than a plain-text access-restricted message. We report each block as we actually encountered it rather than treating every one as identical, even when the end result, a page we couldn't get past, is the same.

Why two blocked members still belong in the same write-up as two visible ones

We could have skipped 92e and M91 entirely and only written about the two sites that rendered for us, but that would understate what this family actually is. Grouping all four together, and being explicit about which two we could see, gives a more accurate picture of the template as a whole than quietly reviewing only the half that cooperated with our check.

What we'd revisit this page for

A future check that gets past the Cloudflare challenge on 92e or M91 would let us confirm whether their registration screen, bonus wording, and game catalogue actually match what 81CC and 6PPP showed us, or whether the shared template diverges once you're inside it. Until then, we're treating the two visible sites as representative of the family's surface, not as proof of what the other two contain.

Common questions

Why does the name mention 'roulette' when the game is a colour guess, not a wheel?

It's our internal label for this shared template family, based on the shared page structure we found; it isn't a claim about a specific game mechanic.

Can withdrawal tickers on the homepage be verified?

No. A visitor has no way to confirm that any of the masked withdrawal amounts scrolling on the homepage are real, and we don't treat them as evidence either way.

Why were two of the four apps blocked and not the others?

We can't say for certain; a Cloudflare bot-check challenge can trigger based on traffic patterns, region, or site-side settings that vary between domains even inside one template family.

Is 81CC's 16-day-old domain a bigger concern than the others?

It means that specific domain has no track record yet, which is worth factoring in, though the underlying template itself is shared with a domain nearly ten times older.