Site profile
iotool.io
Built with gtm, gtag, plausible, stackedboost-shopify-assets 0.2.0. 5 pages and 8 stored files.
rank 6,985,247 4 libraries 2 identifiers 0 third-party hosts 0 crawls 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-09-28 | |
| gtag | 2026-09-28 | |
| plausible | 2026-09-28 | |
| stackedboost-shopify-assets | 0.2.0 | 2026-09-28 |
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-2G9J9WERDC | view source |
| Google Tag Manager container (Google) | GTM-5RPF2PXK | view source |
Third-party hosts
The stored pages and scripts reference no host outside iotool.io.
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
| File | Kind | Size | Collected | Versions |
|---|---|---|---|---|
| https://iotool.io/web/assets/14/f07bc99/web.assets_frontend_minimal.min.js | js | 29.6 KB | 2026-09-28 | current |
| https://plausible.io/js/script.file-downloads.ha…-props.revenue.tagged-events.js | js library | not fetched | 2026-09-28 | current |
| https://www.googletagmanager.com/gtag/js?id=G-2G9J9WERDC | js library | not fetched | 2026-09-28 | current |
| https://iotool.io/extensions/sensors | html | 46.2 KB | 2026-09-28 | current |
| https://iotool.io/extensions | html | 26.5 KB | 2026-09-28 | current |
| https://iotool.io/shop/cart | html | 23.9 KB | 2026-09-28 | current |
| https://iotool.io/web/login | html | 21.7 KB | 2026-09-28 | current |
| https://iotool.io/ | html | 174.5 KB | 2026-09-28 | current |
Timeline
No crawl has recorded a snapshot of this site yet; snapshots are written by every crawl from now on.
Questions about iotool.io
- How does PageSourceSearch know what iotool.io 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 iotool.io 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 iotool.io?
- 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 iotool.io?
- 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.