Site profile
efficient-balloon.surge.sh
Built with @segment/vimeo-analytics 2.0.0, mdbootstrap 4.20.0, @widgetbot/crate 3.9.1, supafolio-sdk 1.4.1, filterizr 2.2.4, @kwaeri/user-experience 0.1.13, @pdftron/pdfjs-express-viewer 8.7.5, @linways/table-to-excel 1.0.4. 1 page and 4 stored files, last crawled 2026-10-03.
8 libraries 0 identifiers 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 |
|---|---|---|
| @segment/vimeo-analytics | 2.0.0 | 2026-10-03 |
| mdbootstrap | 4.20.0 | 2026-10-03 |
| @widgetbot/crate | 3.9.1 | 2026-10-03 |
| supafolio-sdk | 1.4.1 | 2026-10-03 |
| filterizr | 2.2.4 | 2026-10-03 |
| @kwaeri/user-experience | 0.1.13 | 2026-10-03 |
| @pdftron/pdfjs-express-viewer | 8.7.5 | 2026-10-03 |
| @linways/table-to-excel | 1.0.4 | 2026-10-03 |
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 efficient-balloon.surge.sh 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 |
|---|---|---|
| min-api.cryptocompare.com | connect | view source |
| reactjs.org | connect | view source |
| rocky-bayou-96357.herokuapp.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) {
| File | Kind | Size | Collected | Versions |
|---|---|---|---|---|
| https://efficient-balloon.surge.sh/asset-manifest.json | js | 196 B | 2026-10-03 | 2026-10-03 |
| https://efficient-balloon.surge.sh/service-worker.js | js | 3.1 KB | 2026-10-03 | 2026-10-03 |
| https://efficient-balloon.surge.sh/static/js/main.02d114e2.js | js | 473.3 KB | 2026-10-03 | 2026-10-03 |
| https://efficient-balloon.surge.sh/ | html | 548 B | 2026-10-03 | 2026-10-03 |
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
1 page, 4 files, 477.1 KB; 8 libraries, 0 identifiers, 4 third-party hosts
8 libraries added
- @kwaeri/user-experience 0.1.13
- filterizr 2.2.4
- @pdftron/pdfjs-express-viewer 8.7.5
- @widgetbot/crate 3.9.1
- @segment/vimeo-analytics 2.0.0
- @linways/table-to-excel 1.0.4
- mdbootstrap 4.20.0
- supafolio-sdk 1.4.1
4 third-party hosts added
Questions about efficient-balloon.surge.sh
- How does PageSourceSearch know what efficient-balloon.surge.sh 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 efficient-balloon.surge.sh 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 efficient-balloon.surge.sh?
- 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 efficient-balloon.surge.sh?
- 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.