Site profile
luckystar-game.in
Built with gtag, intl-tel-input 29.5.2, @roadtrip/components 3.59.0, cloudflare-insights, sas-ui 0.8.283. 5 pages and 11 stored files, last crawled 2026-10-07.
rank 12,653,814 5 libraries 1 identifier 4 third-party hosts 1 crawl open the site
Technologies and libraries
Recognised by fingerprinting the stored files and bundles against known releases; a version is the release the bytes match.
| Library | Version | Seen |
|---|---|---|
| gtag | 2026-10-07 | |
| intl-tel-input | 29.5.2 | 2026-10-07 |
| @roadtrip/components | 3.59.0 | 2026-10-07 |
| cloudflare-insights | 2026-10-07 | |
| sas-ui | 0.8.283 | 2026-10-07 |
Tracking, tag and verification IDs
Public identifiers read out of the source. Each links to every other site in the index that carries the same one.
| What | Value | Found in |
|---|---|---|
| Google Analytics 4 measurement id (Google) | G-VLNBJ9NGLV | view source |
Third-party hosts
Hosts outside luckystar-game.in that its pages load scripts, frames or stylesheets from, and that its own scripts name in absolute URLs (connect). Each links to every site loading from the same host.
| Host | Loaded as | Found in |
|---|---|---|
| api.country.is | connect | view source |
| script.google.com | connect | view source |
| static.cloudflareinsights.com | script | view source |
| www.googletagmanager.com | script | view source |
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
Timeline
One entry per crawl, newest first, with what changed since the crawl before: libraries, identifiers, third-party hosts and files. Historical versions stay viewable because the stored chunks are shared between versions, never copied.
-
first crawl
5 pages, 11 files, 490.8 KB; 5 libraries, 1 identifier, 4 third-party hosts
5 libraries added
- gtag
- sas-ui 0.8.283
- intl-tel-input 29.5.2
- @roadtrip/components 3.59.0
- cloudflare-insights
1 identifier added
- G-VLNBJ9NGLV Google Analytics 4 measurement id
4 third-party hosts added
11 files added
- https://luckystar-game.in/ html
- https://luckystar-game.in/login/ html
- https://luckystar-game.in/app/ html
- https://luckystar-game.in/slots/ html
- https://luckystar-game.in/aviator/ html
- https://luckystar-game.in/wp-content/themes/them…8e6dfc4bcb7b12b38667cc9cb863.js js
- https://luckystar-game.in/wp-content/themes/them…a260e33d4373a38b650b9e7b596f.js js
- https://luckystar-game.in/wp-content/themes/them…99a003918e6150130268cca5fd0f.js js
- https://luckystar-game.in/wp-content/themes/theme/dist/js/utils.js js
- https://www.googletagmanager.com/gtag/js?id=G-VLNBJ9NGLV js
- https://static.cloudflareinsights.com/beacon.min…85bb4c19e7a9bdbcba1788362987495 js
Questions about luckystar-game.in
- How does PageSourceSearch know what luckystar-game.in is built with?
- From the site's own source code. The crawler stores the exact bytes of its pages and first-party scripts; the libraries are recognised by fingerprinting that code against known releases, the identifiers are read out of the tag snippets, and the third-party hosts are the script, iframe and stylesheet sources in the HTML and the absolute URLs inside the scripts. Nothing is inferred from headers or guessed.
- How far back does the history of luckystar-game.in go?
- To the first crawl the timeline lists. Every crawl records what the site looked like; when a file's content changes, its earlier version stays viewable because the stored chunks are never deleted, only mapped. A crawl that finds a file unchanged adds no copy.
- Can I see an older version of a script from luckystar-game.in?
- Yes. In the stored files list, every date under a file opens the version that was live at that crawl, with the same viewer as the current one. The raw bytes can be downloaded from there.
- Which other websites use the same tracking IDs as luckystar-game.in?
- Each identifier links to its reverse lookup, the list of every site in the index whose source carries the same id: the sites one analytics property or tag manager container is shared across.
Look up another site, browse sites by tracking ID, third-party host or technology. Site owners: see the crawler page for how stored pages are removed.