Site profile
sima.ai
Built with gsap 3.12.5, gtm, prismjs 1.30.0, owl.carousel 2.3.4, typed.js 3.0.0, @inkeep/cxkit-js 0.5.119, klaro 0.7.21, recaptcha, @silvermine/videojs-quality-selector 1.3.1, ima-ad-player 0.5.7, docsify 5.0.0, jsxgraph 1.13.3 and more. 5 pages and 32 stored files.
rank 1,845,335 21 libraries 1 identifier 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 |
|---|---|---|
| gsap | 3.12.5 | 2026-09-25 |
| gtm | 2026-09-25 | |
| prismjs | 1.30.0 | 2026-09-25 |
| owl.carousel | 2.3.4 | 2026-09-25 |
| typed.js | 3.0.0 | 2026-09-25 |
| @inkeep/cxkit-js | 0.5.119 | 2026-09-25 |
| klaro | 0.7.21 | 2026-09-25 |
| recaptcha | 2026-09-25 | |
| @silvermine/videojs-quality-selector | 1.3.1 | 2026-09-25 |
| ima-ad-player | 0.5.7 | 2026-09-25 |
| docsify | 5.0.0 | 2026-09-25 |
| jsxgraph | 1.13.3 | 2026-09-25 |
| @jupyter-widgets/html-manager | 1.0.15 | 2026-09-25 |
| vditor | 4.0.0 | 2026-09-25 |
| @json-editor/json-editor | 2.17.2 | 2026-09-25 |
| jquery.flipster | 1.1.6 | 2026-09-25 |
| bootstrap3 | 3.3.5 | 2026-09-25 |
| bootstrap337 | 3.3.7 | 2026-09-25 |
| @grigorov-it/mazer | 2.2.0 | 2026-09-25 |
| react-grid-layout | 2.2.4 | 2026-09-25 |
| @pydantic/ai-chat-ui | 2.3.0 | 2026-09-25 |
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 Tag Manager container (Google) | GTM-N6T69SQL | view source |
Third-party hosts
The stored pages and scripts reference no host outside sima.ai.
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
Timeline
No crawl has recorded a snapshot of this site yet; snapshots are written by every crawl from now on.
Questions about sima.ai
- How does PageSourceSearch know what sima.ai 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 sima.ai 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 sima.ai?
- 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 sima.ai?
- 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.