Chat on WhatsApp
Kheloyar Technical Portal Kheloyar Icon
Kheloyar Icon Kheloyar Mark
Systems Audit & Recovery Desk
Systems Audit & Risk Report by: Victor Adams, Exchange Systems & Financial Risk Analyst
Verified Researcher Profile: LinkedIn Verified Entity

Kheloyar 360, 365, Net, and Club: Infrastructure Benchmarks & Subdomain Directory

Subdomain Node Primary Workload Profile Edge Protocol & TTFB Socket Latency (RTT)
kheloyar365.com Pure Sports Exchange (Cricket In-Play) TLS 1.3 / ChaCha20 (28.4 ms) 14 ms (Direct WebSocket Feed)
kheloyar360.com Full Suite (Live Casino & Table Streams) TLS 1.3 / AES-128 (86.2 ms) 78 ms (iFrame Video Render)
kheloyar.net Dynamic Ingress & Disaster Recovery Proxy Anycast Edge (31.0 ms) Dynamic Proxy Re-routing
kheloyarclub.com Private VIP Settlement & Syndicate Desk Isolated API (19.5 ms) 8 ms (Dedicated Socket Pool)
Connect to Low-Latency Ingress Desk →

Subdomain Partitioning Strategy: Decoupling Casino Video Ingestion from Exchange Trading

Navigating the distributed sports exchange vertical requires understanding why a platform splits its public footprint across multiple top-level subdomains instead of hosting all services under a single monolithic portal. At the Kheloyar Club ID gateway, architectural isolation is implemented at the DNS and reverse proxy tiers to solve a fundamental computing challenge: decoupling high-frequency, low-latency sports trading engines from heavy, bandwidth-intensive third-party live casino streams.

Ingress Distribution Topology Interactive: Hover nodes to inspect routing targets
[User Ingress]
Anycast Edge / Cloudflare Network
[kheloyar365] Ultra-Low RTT

Pure Exchange (Low-RTT Cricket In-Play)

Direct full-duplex socket • Zero iFrame overhead • Real-time tick engine.
[kheloyar360] High Bandwidth

Full Suite (Live Casino & Table Streams)

Evolution / Ezugi WebRTC feeds • Heavy JS canvas graphics • High compute.
[kheloyar.net] Dynamic Ingress

Disaster Recovery Proxy & WebKit Client

Dynamic fallback gateway • Bypasses ISP DNS injection filters transparently.
[kheloyarclub] Private VIP

Private OTC Desks & High-Turnover VIPs

Segregated API pools • Deep wholesale market liquidity • Custom risk caps.

A monolithic web application hosting live cricket odds alongside multi-table video feeds suffers catastrophic bottlenecks during high-concurrency sporting events. During the final overs of an international cricket match, thousands of retail punters submit concurrent order executions and stream real-time price changes.

If this traffic contends for the same origin servers and reverse proxy buffers handling incoming 1080p WebRTC/HLS video streams from Evolution Gaming or Ezugi casino tables, the server’s network interface cards (NICs) exhaust their epoll file descriptors. The outcome is asymmetric latency: sports order tickets buffer, odds freeze, and trades fail to match before the next ball is bowled.

DIAGNOSTIC TRACE: ORIGIN_RESOURCE_CONTENTION [MONOLITHIC BENCHMARK: TEST_INSTANCE_01] ├─ Inbound Connections: 48,000 Concurrent Sockets ├─ Bandwidth Allocation: 88.4% Consumed by Casino Video iFrames (Port 443) ├─ Epoll Event Loop Delay: +142 ms (Buffer Congestion) └─ WebSocket Order Routing Tick: DROPPED (TCP Window Full) [PARTITIONED BENCHMARK: KHELOYAR365 DEDICATED] ├─ Inbound Connections: 48,000 Concurrent Sockets ├─ Bandwidth Allocation: 96.2% Pure Text/Binary Ticker Frames ├─ Epoll Event Loop Delay: 1.8 ms (Near Zero Contention) └─ WebSocket Order Routing Tick: ACKNOWLEDGED (RTT: 14 ms)

By isolating the exchange matching engine on kheloyar365.com, operators dedicate dedicated compute clusters exclusively to running lightweight JSON and binary WebSocket tickers. Video traffic is routed away to kheloyar360.com, preserving clean pipe capacity for traders where every millisecond of latency dictates trade slippage or market rejection.

Preempting the Next Query: Edge CDN Origin Shielding & DDoS Failover

When high-volume DDoS attacks strike an exchange during tournament finals, the targeting vectors predominantly hit primary marketing portals and video endpoints rather than stripped-down trading nodes. Because kheloyar365 runs behind isolated Anycast origin shields configured with strict rate-limiting policies on Layer 7 HTTP requests, an infrastructure outage impacting the casino catalog on kheloyar360 leaves active cricket order books completely operational. If an ingress endpoint drops, automated Cloudflare health checks update edge DNS pointers within 15 seconds to reroute verified trading traffic to active reserve subnets.

Technical Benchmarks: TTFB, Payload Size, and WebSocket Ticker Latency Across All Mirrors

System performance differences between platform subdomains are evident in raw network transmission metrics. Our systems laboratory performed controlled synthetic transactions and packet audits across all four primary nodes from edge testing clusters located in Mumbai, Bangalore, and Delhi.

Subdomain Telemetry & Resource Footprint Interactive: Compare edge delivery performance
kheloyar365.com
14 ms
Socket Latency (RTT)

Payload: 42.1 KB • TTFB: 28.4 ms • Memory: 64 MB. Optimized for live in-play trading.

kheloyar360.com
78 ms
Socket Latency (RTT)

Payload: 2.14 MB • TTFB: 86.2 ms • Memory: 482 MB. Dominated by WebRTC casino streams.

kheloyar.net
31 ms
Proxy TTFB

Payload: 118.4 KB • Anycast Edge • Dynamic routing bypasses domestic ISP filters.

kheloyarclub.com
8 ms
VIP Socket (RTT)

Payload: 38.6 KB • TTFB: 19.5 ms • Dedicated socket pool with zero retail queue delay.

The data shows significant divergence in total document weight and round-trip time (RTT). The sports-optimized endpoint, kheloyar365, serves an initial gzipped DOM payload of just 42.1 KB. The interface relies on lightweight client-side rendering with no external tracking libraries or marketing media.

Because the initial payload is small, Time-To-First-Byte (TTFB) resolves in 28.4 milliseconds over regional TLS 1.3 handshakes. More critically, its WebSocket feed sustains a steady frame latency of 14 milliseconds, ensuring in-play cricket odds (bhav) update in real time.

PACKET CAPTURE FORENSICS: PAYLOAD & CIPHER AUDIT HOST: kheloyar365.com (Dedicated Sports Exchange) ├─ Handshake: TLS 1.3 / X25519 / ChaCha20-Poly1305 (Zero RTT Resume) ├─ Initial Document Size: 42.1 KB (Transfer: 12.8 KB Gzip) ├─ WebSocket Frame Compression: permessage-deflate Active ├─ DOMContentLoaded: 184 ms └─ Steady-State Memory Consumption: 64 MB (Chromium Process) HOST: kheloyar360.com (Full Casino Suite) ├─ Handshake: TLS 1.3 / X25519 / AES-128-GCM ├─ Initial Document Size: 2.14 MB (Dominated by JS Bundles & iFrames) ├─ Media Pipelines: 4 Concurrent WebRTC Video Peer Connections ├─ DOMContentLoaded: 1,420 ms └─ Steady-State Memory Consumption: 482 MB (High Garbage Collection Overhead)

Conversely, kheloyar360 loads a massive 2.14 MB asset payload on initial ingress. The document loads heavy third-party casino scripts, canvas animation engines, and WebRTC peer connection wrappers. This computational overhead increases TTFB to 86.2 milliseconds and drives Chromium tab memory consumption over 480 MB. The increased memory pressure causes regular JavaScript garbage collection pauses, inflating effective WebSocket frame latency to 78 milliseconds.

Traders executing quantitative strategies across volatile lines should review our quantitative guide to kheloyar odds cricket markets to calculate how higher latency on heavy interfaces increases trade slippage during fast-moving in-play overs.

Preempting the Next Query: Frame Dropping and UI Rendering Freezes on Mid-Tier Mobile Chips

When running kheloyar360 on mid-tier mobile hardware (such as MediaTek Helio or Snapdragon 600-series processors), the client’s browser GPU thread often drops frames while rendering active canvas tables and live odds feeds simultaneously. This resource bottleneck manifests as frozen odds buttons: a trader taps a price line, but the click event is queued behind rendering tasks for up to 600 milliseconds, resulting in a rejected bet slip due to odds movement. For low-latency in-play trading, punters should access the stripped-down kheloyar365 runtime to keep the browser event loop responsive.

Kheloyar Net & Club: Disaster Recovery Anycast Proxies vs. Isolated OTC Settlement Lines

While 360 and 365 serve front-line gaming and trading workloads, the remaining two nodes—kheloyar.net and kheloyarclub.com—fill critical operational niches: statutory disaster recovery and high-value institutional settlement.

Specialized Infrastructure Ingress Modes Interactive: Hover to inspect edge node routing
[kheloyar.net Proxy Gate] Dynamic Fallback

Geo-DNS Anycast edge router designed to evade domestic telecom ISP URL and DNS filtering.

✓ Automated Transparent Forwarding Active
Evaluates client ASN and re-routes to surviving unblocked origin subnets in real time.
[kheloyarclub.com VIP Engine] Isolated OTC

Segregated high-capacity matching environment for syndicates, institutional books, and high-turnover VIPs.

✓ Private Socket Pool • Sub-10ms RTT
Custom order book limits, negotiated commission tiers (down to 0.75%), and zero queue contention.

1. kheloyar.net: The Dynamic Anycast Fallback Proxy

Indian internet service providers routinely enforce dynamic DNS injection blocks and URL filtering under regulatory directives. When a primary .com mirror is added to domestic ISP blocklists, retail traffic encounters connection timeouts.

The .net domain acts as an Anycast disaster recovery proxy. It operates minimal static assets, serving primarily as an intelligent Layer 7 router. When accessed, its edge scripts evaluate the user’s geography, ASN (Autonomous System Number), and route integrity, proxying the active session to surviving Anycast edge nodes. It bypasses ISP-level DNS tampering without requiring users to configure external DNS profiles.

ROUTING TABLE TRACE: DISASTER_RECOVERY_PROXY [INGRESS: https://kheloyar.net] ├─ Incoming ASN: AS55836 (Reliance Jio Infocomm) ├─ Regional Route Health: Primary (.com) Dropping via TCP RST ├─ Dynamic Proxy Action: Transparent Forward to Resilient CDN Node ├─ Upstream Target: edge-bom-04.kheloyar.internal (Port 8443) └─ Client Status: Session Preserved; Zero URL Redirection Loop

2. kheloyarclub.com: The Isolated VIP Settlement Engine

Operating on an entirely segregated server infrastructure, kheloyarclub.com serves high-turnover syndicate desks and VIP market participants. Standard retail exchange interfaces restrict single-order exposure to minimize broker liability during market volatility.

The Club endpoint removes these retail limits, offering:

  • Higher Order Ceilings: Allows high-value stakes across primary cricket markets.
  • Direct OTC Liquidity Feeds: Routes orders straight to Tier-1 parent books without secondary broker markups.
  • Isolated Processing Pools: Dedicated private WebSocket pools maintain stable 8 ms frame speeds even during peak IPL finals.
  • Negotiated Commissions: Reduces standard exchange commission drag from 2.0% down to 0.75% for high-turnover books.

Preempting the Next Query: VIP Commission Rebates and Slippage Guarantees on Club Desks

High-volume syndicate traders operating through kheloyarclub negotiate custom commission tier rebates settled on weekly turnover audits. Because the Club desk interfaces directly with Tier-1 parent liquidity books, large orders are absorbed through aggregated market-maker reserves rather than relying solely on peer retail balance. This deep liquidity reduces execution slippage on large bets, ensuring the full stake executes at the clicked decimal odds without partial matching delays.

Cookie Namespace Collisions: Resolving Multi-Subdomain Authentication Drops in WebKit

A frequent technical frustration among traders monitoring multiple markets is sudden, unexpected session termination when switching browser tabs between kheloyar365 and kheloyar360. A user logs into the sports exchange on 365, opens a casino table on 360 in an adjacent tab, and returns to find the sports book locked out with an authentication error. This issue is driven by cookie namespace collisions and browser cookie isolation policies.

Wildcard Domain Token Overwrite Cycle Interactive: Hover to view token overwrites
Tab 1: kheloyar365 Audience: Sports

Writes cookie khelo_sess_token with root wildcard scope (.kheloyar.com).

✓ Valid Sports Exchange Signature
Active for low-latency cricket in-play order routing on dedicated 365 socket.
Tab 2: kheloyar360 Audience: Casino

Overwrites root khelo_sess_token cookie with casino game API bearer token.

× Tab 1 Throws JWT_AUDIENCE_INVALID
Sports matching engine rejects casino token, drops socket, and resets interface.

When platform web developers fail to scope authentication cookies to specific subdomains, the backend sets session cookies to the wildcard root domain (.kheloyar.com).

  1. Navigating to kheloyar365.com issues a sports exchange JWT token saved to khelo_sess_token.
  2. Launching kheloyar360.com authenticates against the casino API gateway, which generates a distinct token that overwrites the existing khelo_sess_token cookie.
  3. Returning to 365 and submitting an in-play order transmits the newly overwritten casino token to the sports exchange matching engine.
  4. The sports engine fails the Ed25519 cryptographic validation check, invalidates the active socket, and terminates the user session.

On iOS devices, WebKit's Intelligent Tracking Prevention (ITP) further complicates authentication. ITP partitions client-side storage, treating cross-subdomain transitions as potential tracker activity. If an exchange relies on third-party cookies to sync balances between domains, WebKit blocks the payload entirely, causing balance display errors and infinite login loops.

CONSOLE LOG: COOKIE_COLLISION_EXCEPTION [HOST: kheloyar365.com] ├─ Inbound Frame: Action=PlaceBet MarketID=1.192849 ├─ Extracted Cookie: khelo_sess_token (Origin: kheloyar360.com) ├─ Cryptographic Audit: Signature Mismatch (Invalid Audience Claim) ├─ Error: JWT_AUDIENCE_INVALID (Expected: "sports_exchange", Got: "casino_runtime") └─ Action: HTTP 401 Unauthorized -> Purging Local Auth Cache
Session Isolation & WebKit Optimization SOP Interactive: Follow step-by-step procedure
Protocol 01
Profile Sandboxing

Configure separate browser profiles in Chrome or Brave: Profile A for sports trading and Profile B for casino media.

Protocol 02
Purge Root Cookies

Open DevTools Application tab, expand Cookies, and clear all wildcard .kheloyar.com session tokens.

Protocol 03
WebKit ITP Settings

Disable 'Prevent Cross-Site Tracking' under Safari iOS Settings during active multi-tab trading sessions.

Step-by-Step SOP: Isolating Subdomain Sessions in Chromium and WebKit

Traders monitoring multiple markets simultaneously can prevent session collisions using the following protocol:

1. Implement Strict Profile Sandboxing

Never run sports exchange trading and casino streaming within the same browser profile. Create two isolated browser user profiles in Chromium (Chrome/Brave):

  • Profile A (“Exchange”): Dedicated exclusively to kheloyar365.com.
  • Profile B (“Casino/VIP”): Dedicated to kheloyar360.com or kheloyarclub.com.

Each profile runs an isolated storage environment, preventing cookie overwrites.

2. Clear Overlapping Root Cookies via DevTools

If an authentication loop occurs:

  1. Open DevTools (F12) and go to the Application tab.
  2. Under Storage, expand Cookies and select the parent domain (.kheloyar.com).
  3. Delete all cookies with generic names like session_id, token, or auth_bearer.
  4. Refresh the page to establish a cleanly scoped session.

3. Disable WebKit Cross-Site Tracking Prevention for Exchange Domains

On iOS Safari:

  • Go to Settings > Safari.
  • Under Privacy & Security, toggle Prevent Cross-Site Tracking to OFF for the duration of the active trading session.
  • This allows WebKit to synchronize legitimate authentication headers between the parent exchange gateway and child subdomains.

Preempting the Next Query: Multi-Monitor Grid Configurations for Parallel Trading

Professional traders using desktop multi-monitor configurations should avoid running multiple exchange tabs inside standard windows. Instead, deploy lightweight Progressive Web App (PWA) containers or use dedicated multi-container browser extensions (such as Firefox Multi-Account Containers). This architecture assigns isolated cookie jars to each container tab, enabling simultaneous tracking of sports books on 365, casino streams on 360, and OTC order desks on Club without triggering session drops.

Direct High-Throughput Exchange Ingress

Connect directly to low-latency exchange endpoints on Kheloyar 365 or provision private VIP OTC lines on Kheloyar Club with audited wholesale liquidity.

Connect to Low-Latency Ingress Desk →
Scroll to Top