How does PageSourceSearch know what thestraleyproject.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 thestraleyproject.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 thestraleyproject.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 thestraleyproject.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.

Site profile

thestraleyproject.org

Built with gtm, facebook-pixel, @vitest/utils 5.0.2, stackedboost-shopify-assets 0.2.0. 5 pages and 6 stored files, last crawled 2026-10-08.

rank 13,836,580 4 libraries 8 identifiers 2 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
gtm		2026-10-08
facebook-pixel		2026-10-08
@vitest/utils	5.0.2	2026-10-08
stackedboost-shopify-assets	0.2.0	2026-10-08

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
Bing site verification (Microsoft)	23B984DFF8E80C562D4920F2F5A8DAA6	view source
Facebook domain verification (Meta)	gs087uk4rdujiuf452ddqrf13a6hh4	view source
Facebook domain verification (Meta)	vj9qua1pb6oyaz5hc5lg8uxspm9kje	view source
Meta pixel id (Meta)	1782128095891176	view source
Google site verification (Google)	hatjar4IN-AXKivd_FDHvHpAn1i4LrPew83qNrmgGno	view source
Google Tag Manager container (Google)	GTM-MZQ4HXZB	view source
Pinterest site verification (Pinterest)	ce9ee1ad563ceafb9f81421e6c01a834	view source
Yandex site verification (Yandex)	79a385e7f7354a10	view source

Third-party hosts

Hosts outside thestraleyproject.org 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
maps.google.com	iframe	view source
www.googletagmanager.com	iframe	view source

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 6) }. Versions are the crawls at which the file was new or its content changed; each opens the file as it was then, rebuilt from the same stored chunks.

File	Kind	Size	Collected	Versions
https://thestraleyproject.org/wp-content/plugins…/js/lazyload.min.js?ver=6.5.0	js	9.1 KB	2026-10-08	2026-10-08
https://thestraleyproject.org/programs/	html	465.5 KB	2026-10-08	2026-10-08
https://thestraleyproject.org/impact/	html	461.3 KB	2026-10-08	2026-10-08
https://thestraleyproject.org/contact-us/	html	486.4 KB	2026-10-08	2026-10-08
https://thestraleyproject.org/about-us/	html	483.7 KB	2026-10-08	2026-10-08
https://thestraleyproject.org/	html	480.2 KB	2026-10-08	2026-10-08

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.

2026-10-08 first crawl

5 pages, 6 files, 2.3 MB; 4 libraries, 8 identifiers, 2 third-party hosts
4 libraries added
- @vitest/utils 5.0.2
- stackedboost-shopify-assets 0.2.0
- gtm
- facebook-pixel
8 identifiers added
- GTM-MZQ4HXZB Google Tag Manager container
- 1782128095891176 Meta pixel id
- hatjar4IN-AXKivd_FDHvHpAn1i4LrPew83qNrmgGno Google site verification
- 23B984DFF8E80C562D4920F2F5A8DAA6 Bing site verification
- 79a385e7f7354a10 Yandex site verification
- vj9qua1pb6oyaz5hc5lg8uxspm9kje Facebook domain verification
- gs087uk4rdujiuf452ddqrf13a6hh4 Facebook domain verification
- ce9ee1ad563ceafb9f81421e6c01a834 Pinterest site verification
2 third-party hosts added
- www.googletagmanager.com
- maps.google.com
6 files added

Questions about thestraleyproject.org

How does PageSourceSearch know what thestraleyproject.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 thestraleyproject.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 thestraleyproject.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 thestraleyproject.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.