Site profile
shifter-gatsby-wp-example.netlify.app
Built with bootstrap 4.4.1, bromcom-ui 2.12.3, graphql-playground-react 1.7.28, kifu-for-js 5.5.0. 5 pages and 16 stored files, last crawled 2026-10-03.
4 libraries 0 identifiers 5 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 |
|---|---|---|
| bootstrap | 4.4.1 | 2026-10-03 |
| bromcom-ui | 2.12.3 | 2026-10-03 |
| graphql-playground-react | 1.7.28 | 2026-10-03 |
| kifu-for-js | 5.5.0 | 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 shifter-gatsby-wp-example.netlify.app 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 |
|---|---|---|
| github.blog | connect | view source |
| github.com | connect | view source |
| reactjs.org | connect | view source |
| storage.googleapis.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, 16 files, 1 MB; 4 libraries, 0 identifiers, 5 third-party hosts
4 libraries added
- bootstrap 4.4.1
- graphql-playground-react 1.7.28
- kifu-for-js 5.5.0
- bromcom-ui 2.12.3
5 third-party hosts added
16 files added
- https://shifter-gatsby-wp-example.netlify.app/ html
- https://shifter-gatsby-wp-example.netlify.app/blogs/hello-world/ html
- https://shifter-gatsby-wp-example.netlify.app/blogs/post-format-standard/ html
- https://shifter-gatsby-wp-example.netlify.app/about/ html
- https://shifter-gatsby-wp-example.netlify.app/blogs/scheduled/ html
- https://shifter-gatsby-wp-example.netlify.app/we…runtime-6dcbad437be28893f4cf.js js
- https://shifter-gatsby-wp-example.netlify.app/styles-b729c27faa6284e9ff45.js js
- https://shifter-gatsby-wp-example.netlify.app/app-347e81d5f2d87050f344.js js
- https://shifter-gatsby-wp-example.netlify.app/1e…032704d-9b39918e45f9d5057ba1.js js
- https://shifter-gatsby-wp-example.netlify.app/co…dex-tsx-ca60c42d13aa0e79b601.js js
- https://shifter-gatsby-wp-example.netlify.app/8b…b614969-b9e1ad39df4ea64d2c64.js js
- https://shifter-gatsby-wp-example.netlify.app/framework-38299d20c7ca7a3581d4.js js
- and 4 more
Questions about shifter-gatsby-wp-example.netlify.app
- How does PageSourceSearch know what shifter-gatsby-wp-example.netlify.app 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 shifter-gatsby-wp-example.netlify.app 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 shifter-gatsby-wp-example.netlify.app?
- 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 shifter-gatsby-wp-example.netlify.app?
- 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.