Site profile
i-can-not-react.netlify.app
Built with bowser 2.14.1, graphql-playground-react 1.7.28, filterizr 2.2.4, react-quill 2.0.0, idle-js 1.2.0, staffbase-widget-dacast 1.0.5. 5 pages and 14 stored files, last crawled 2026-10-03.
6 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 |
|---|---|---|
| bowser | 2.14.1 | 2026-10-03 |
| graphql-playground-react | 1.7.28 | 2026-10-03 |
| filterizr | 2.2.4 | 2026-10-03 |
| react-quill | 2.0.0 | 2026-10-03 |
| idle-js | 1.2.0 | 2026-10-03 |
| staffbase-widget-dacast | 1.0.5 | 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 i-can-not-react.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 |
|---|---|---|
| embed.disqus.com | 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, 14 files, 427.3 KB; 6 libraries, 0 identifiers, 5 third-party hosts
6 libraries added
- idle-js 1.2.0
- bowser 2.14.1
- filterizr 2.2.4
- graphql-playground-react 1.7.28
- staffbase-widget-dacast 1.0.5
- react-quill 2.0.0
5 third-party hosts added
14 files added
- https://i-can-not-react.netlify.app/ html
- https://i-can-not-react.netlify.app/real-world-example/ html
- https://i-can-not-react.netlify.app/react-and-firebase/ html
- https://i-can-not-react.netlify.app/use-effect/ html
- https://i-can-not-react.netlify.app/react-hooks/ html
- https://i-can-not-react.netlify.app/webpack-runtime-5351705a20f4e037b9ef.js js
- https://i-can-not-react.netlify.app/styles-c4a20fcea6343ad7f3ac.js js
- https://i-can-not-react.netlify.app/app-ea03fb5ad4ad46fccf45.js js
- https://i-can-not-react.netlify.app/0-1481869309ae5f010b6c.js js
- https://i-can-not-react.netlify.app/component---…ndex-js-5a423fb0338ac9582f27.js js
- https://i-can-not-react.netlify.app/9-07f6b81ea3b9cc4a5221.js js
- https://i-can-not-react.netlify.app/component---…post-js-8732d64a6dd29962e91e.js js
- and 2 more
Questions about i-can-not-react.netlify.app
- How does PageSourceSearch know what i-can-not-react.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 i-can-not-react.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 i-can-not-react.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 i-can-not-react.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.