Site profile
go-gain.com
Built with gtm, @vitest/utils 5.0.2. 5 pages and 55 stored files, last crawled 2026-10-09.
2 libraries 0 identifiers 13 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 |
|---|---|---|
| gtm | 2026-10-09 | |
| @vitest/utils | 5.0.2 | 2026-10-09 |
Tracking, tag and verification IDs
No analytics property, tag manager container, pixel or site-verification token was found in the stored source.
Third-party hosts
Hosts outside go-gain.com 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.framer.com | connect | view source |
| app.framerstatic.com | connect | view source |
| apps.apple.com | connect | view source |
| assets.mixkit.co | connect | view source |
| calendly.com | connect | view source |
| fonts.googleapis.com | stylesheet | view source |
| fonts.gstatic.com | connect | view source |
| framer.com | connect | view source |
| framerusercontent.com | connect | view source |
| play.google.com | connect | view source |
| www.googletagmanager.com | connect | view source |
| www.instagram.com | connect | view source |
| www.w3.org | connect | 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, 55 files, 2.2 MB; 2 libraries, 0 identifiers, 13 third-party hosts
2 libraries added
- @vitest/utils 5.0.2
- gtm
13 third-party hosts added
55 files added
- https://go-gain.com/en html
- https://go-gain.com/en/contact?subject=entreprise html
- https://go-gain.com/en/particuliers html
- https://go-gain.com/en/qr html
- https://go-gain.com/en/programmes html
- https://go-gain.com/assets/framer/en/Bg0537Zl6_9…3WR5qSjIPiS4N8EmOU.BASE0y_P.mjs js
- https://go-gain.com/assets/framer/en/Blf0sjosZ.lyDK_3VZ.mjs js
- https://go-gain.com/assets/framer/en/Cookies.C9dDrLqu.mjs js
- https://go-gain.com/assets/framer/en/E7ecUaoeTNG…1JNdk4fU15qoxzZd2o.DZ68XVw0.mjs js
- https://go-gain.com/assets/framer/en/FRK5IbQGh.7CzxUD6C.mjs js
- https://go-gain.com/assets/framer/en/FvhlNGBcNSy…UZ_DbyRveSpL-06SrI.CNzIYfnH.mjs js
- https://go-gain.com/assets/framer/en/HYStK69aB.BWvkLZpU.mjs js
- and 43 more
Questions about go-gain.com
- How does PageSourceSearch know what go-gain.com 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 go-gain.com 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 go-gain.com?
- 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 go-gain.com?
- 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.