Site profile
signal.org
Built with fomantic-ui 2.9.4, @lottiefiles/lottie-player 2.0.12, sa-sdk-javascript 1.27.14, kore-web-sdk 11.28.1, p5 2.3.3, cloudflare-email-decode. 5 pages and 8 stored files.
rank 1,950 6 libraries 0 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 |
|---|---|---|
| fomantic-ui | 2.9.4 | 2026-09-24 |
| @lottiefiles/lottie-player | 2.0.12 | 2026-09-24 |
| sa-sdk-javascript | 1.27.14 | 2026-09-24 |
| kore-web-sdk | 11.28.1 | 2026-09-24 |
| p5 | 2.3.3 | 2026-09-24 |
| cloudflare-email-decode | 2026-09-24 |
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
The stored pages and scripts reference no host outside signal.org.
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
| File | Kind | Size | Collected | Versions |
|---|---|---|---|---|
| https://signal.org/assets/javascripts/vendor/lottie-player-2.0.3.min.js | js | 371.3 KB | 2026-09-24 | current |
| https://signal.org/assets/javascripts/vendor/jquery-3.7.1.min.js | js | 85.5 KB | 2026-09-24 | current |
| https://signal.org/cdn-cgi/scripts/5c5dd728/clou…/email-decode.min.js | js | 1.2 KB | 2026-09-24 | current |
| https://signal.org/workworkwork/ | html | 9.1 KB | 2026-09-24 | current |
| https://signal.org/download/ | html | 25.9 KB | 2026-09-24 | current |
| https://signal.org/docs/ | html | 10.5 KB | 2026-09-24 | current |
| https://signal.org/blog/ | html | 214.8 KB | 2026-09-24 | current |
| https://signal.org/ | html | 21.7 KB | 2026-09-24 | current |
Timeline
No crawl has recorded a snapshot of this site yet; snapshots are written by every crawl from now on.
Questions about signal.org
- How does PageSourceSearch know what signal.org 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 signal.org 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 signal.org?
- 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 signal.org?
- 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.