Radar / DraftKings DFS NJ: full integration validation — RDP inconsistent, cross-border lag, generic UX
Source. May 19, 2026 weekly sync.
Ticket. CIV-65: DraftKings DFS — validate the competitor's integration.
Migration context. DraftKings DFS NJ migrated from GeoComply to Radar (May 11).
What we tested
A full integration validation of DraftKings' New Jersey web DFS product following its confirmed migration from GeoComply to Radar. The Sportsbook and the mobile apps (iOS / Android) remain on GeoComply. Compliance and security testing focused on the gaps from running two providers in parallel.
What happened
1. RDP detection: inconsistent
| Tool | May 8 baseline | May 13 retest | May 14 retest |
|---|---|---|---|
| TeamViewer | ✓ Blocked | ✗ Undetected | ✗ Undetected |
| Zoom | ✗ Undetected | ✗ Undetected | ✗ Undetected |
| AnyDesk | ✗ Undetected | ✗ Undetected | ✗ Undetected |
TeamViewer's flip from blocked-to-undetected across consecutive retests is the headline — detection is unreliable rather than absent.
2. Cross-border session lag: ~100–150m past the PA→NJ line
After physically crossing from Pennsylvania into New Jersey with an active session, bet placement remained blocked for approximately 100–150 metres past the state border — significantly wider than GeoComply's 2–5m range.
Users entering NJ without a prior PA session were unaffected, pointing to a session-state issue on the provider side rather than a geofence-geometry issue. The session carries the prior-state restriction across the line instead of cleanly re-evaluating.
3. UX: generic error messaging
Both RDP-triggered blocks and cross-border blocks surface the same "Account Locked" message with no diagnostic data or guidance on next steps. Players cannot self-correct; operators take the support load.
Why it matters
DraftKings DFS NJ is Radar's first major US live-traffic win on a Tier-1 operator (confirmed May 11). This validation is the first post-migration look at how the integration is performing in production. Findings:
- The dual-vendor concern was real. DFS-web is on Radar; the rest of DraftKings stays on GeoComply. Cross-product UX is divergent, and the DFS-web side is the weaker integration.
- The RDP gap is the new sales pivot. Zoom + AnyDesk consistently undetected on a regulated US DFS product is the cleanest possible "Radar is not ready for Tier-1" example.
- The 100–150m post-border lag is a category miss. GeoComply measures in single-digit metres on the same line.
- Generic Account-Locked is operator pain. Sales conversations should bring this up alongside compliance: every false-positive block is a support ticket DraftKings owns.
Cross-reference
- DraftKings DFS NJ migration confirmation (May 11) — the underlying provider transition.
- Bet365 NJ (Radar) Tailscale + RealVNC undetected this week — same provider, same state, comparable RDP gap.
- Bet Saracen AR (Radar) resigned iOS bypass this week — three live Radar deployments (Bet365 NJ, DraftKings DFS NJ, Bet Saracen AR), three independent failure modes, one test cycle.