www.rockstargames.com
“Rockstar Games”
Tech check
What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.
The page doesn't make tech claims we check for (AI, on-chain, wallets, trading, own chain, staking, live data, an app).
What it is
- The site describes itself as: “The official home of Rockstar Games”E2
- It's built with React and Remix / React Router (common tools for building web apps).E20E21
- Notable building blocks in its code: GraphQL client.E22
- In your browser it runs compiled WebAssembly code in your browser.E25
- It has sections such as /newswire, /videos, /downloads, /rockstar-games-launcher, /VI and /games.E31
- While loading, it called 3 endpoints on its own servers, such as /auth/ping-bearer.json, /connect/cors/check/rsg and /graphql.E28E29E30
Where your data goes
Analytics & trackingCount visits and record what you do on the page. 2
| www.google-analytics.com | Google Analytics / Tag Manager: Google's visitor analytics and tag loader | 3×E14 |
| www.googletagmanager.com | Google Analytics / Tag Manager: Google's visitor analytics and tag loader | 2×E7 |
Error & performance monitoringReport crashes and speed to the developers. 1
| o432808.ingest.sentry.io | Sentry: crash and error reports | 2×E6 |
Consent & bot protectionCookie banners, CAPTCHAs and bot checks. 2
| cdn.cookielaw.org | OneTrust: cookie consent banner | 12×E8 |
| geolocation.onetrust.com | OneTrust: cookie consent banner | 1×E9 |
CDNs & hostingDeliver files (scripts, images) quickly from servers near you. 1
| media-rockstargames-com.akamaized.net | Akamai: CDN | 174×E5 |
Not identifiedServices we don't have in our list yet. 1
| s.rsg.sc | not identified | 1×E15 |
How key features work
Sign-in and accounts
Sign-in and account features show up in its code or traffic (/auth/ping-bearer.json).E28
/auth/ping-bearer.jsonLoading its content
Its content loads from its own API while you browse (/auth/ping-bearer.json, /connect/cors/check/rsg and /graphql).E28E29E30
/auth/ping-bearer.json/connect/cors/check/rsg/graphqlCookies and storage
Names only. We never store the values.
Pages and API calls
Pages it links to
//newswire/videos/downloads/rockstar-games-launcher/VI/games/gta-online/gta-plus/reddeadonline/grand-theft-auto-vi-collection/search/contact/careers/community-resources/account/corpinfo/privacy/cookies/legal/ccpaEvidence
Every sentence above points to one of these. Code references show the file, line:column and the short identifier that matched, never the site's code itself.
Limits
- We only see what your browser sees: code and requests on a first visit, without logging in or accepting cookie banners. What the servers do with data is invisible from outside.
- Site code is usually minified (compressed), so names are partly lost and some code may be only partly analysed.
- Some trackers only load after you accept cookies or log in, so the real list can be longer.
- We visited from a server in the United States. Sites load different trackers and cookie banners in different countries (visitors in the EU usually get a consent banner first).
- This text was written from fixed templates because no AI writer was available. It uses exactly the same evidence.
- REA hit its size budget on parts of 58 large bundle file(s); those parts weren't fully analysed.
Facts, not judgements: this page describes what the code and traffic show, not anyone's intent. Not financial advice. Case id rlxydyrC.