Detection matrix
Every competitor against every spoofing technique we test for. Click any cell to see the underlying findings.
Live · GeoComply Internal
What we know about every competitor — kept fresh, searchable, shareable.
Every competitor against every spoofing technique we test for. Click any cell to see the underlying findings.
16 misses and 2 partials ready to use in a sales conversation.
Confirmed compliance vulnerabilities at FanDuel WV: users can bypass geographical restrictions from Tennessee via iOS app resigning, virtualised environment emulation via VMOS, and sideloading via PlayCover on ARM-based macOS. Each technique successfully facilitated out-of-state betting.
Confirmed provider transition: DraftKings has moved its New Jersey DFS web product from GeoComply to Radar. Sportsbook and mobile apps stay on GeoComply. Dual-vendor compliance testing underway.
May 5 monthly brief: location verification failures dominate end-user complaints (38% of all findings), with DraftKings (11) and FanDuel (9) generating the highest complaint volumes across March 30 – April 27.
Saracen AR proximity testing: success rates remained high beyond 350m from the state line, but at 100m Mac devices only cleared 44% of verifications. Windows users experienced a persistent lockout after a single failure, complicated by an atypical 'fraud_jumped_single_device' flag during betting attempts.
Fanatics TN flagship deployment: HopToDesk + iPhone screen mirroring both bypassed OpenBet Locator's RDP protocols. Out-of-Tennessee wagering succeeded on both iOS and Android.
Underdog DFS browser-based Radar deployment: location-spoofing via the free Location Guard Chrome extension was not detected. Free, no technical skill required.
Michigan-based user placed remote wagers on a Delaware-localised iOS device via FaceTime RDP — both casino and sportsbook. Same gap previously confirmed in AZ. Cross-region structural failure, not an operator-specific bug.
Brazil operator Todos Querem Jogar (Bet do Milhão) switched OpenBet off — described as 'worked poorly and caused UX issues'. Now using IP only as primary geolocation, with no proper geo-enforcement.
Reddit, X, and Play Store / App Store review chatter about operators we track. Intel — not test proof; the matrix doesn't rely on these.
The 20 most recent test results and intel updates. Filter below — or open the full feed for paginated history.
Source-of-truth documents the team keeps in Drive. Portal data is seeded from these and refreshed via the import script.