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

wewasa.org

Built with shaka-player 5.2.11, google-apis. 5 pages and 6 stored files.

rank 4,088,870 2 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
shaka-player	5.2.11	2026-09-27
google-apis		2026-09-27

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 wewasa.org.

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://apis.google.com/js/client.js?onload=gapiLoaded	js library	not fetched	2026-09-27	current
https://www.wewasa.org/camp-ensign-ranch/camp-photo-memories	html	193.6 KB	2026-09-27	current
https://www.wewasa.org/camp-ensign-ranch/campground-maps	html	133.7 KB	2026-09-27	current
https://www.wewasa.org/camp-ensign-ranch/conferences	html	399.5 KB	2026-09-27	current
https://www.wewasa.org/	html	140.2 KB	2026-09-27	current
https://www.wewasa.org/home	html	140.4 KB	2026-09-27	current

Timeline

No crawl has recorded a snapshot of this site yet; snapshots are written by every crawl from now on.

Questions about wewasa.org

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