How does PageSourceSearch know what beavertonmazda.com 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 beavertonmazda.com 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 beavertonmazda.com?

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 beavertonmazda.com?

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

beavertonmazda.com

Built with gtm, gtag, facebook-pixel, @vitest/utils 5.0.2. 4 pages and 8 stored files, last crawled 2026-10-09.

4 libraries 7 identifiers 6 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-09
gtag		2026-10-09
facebook-pixel		2026-10-09
@vitest/utils	5.0.2	2026-10-09

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 Ads conversion id (Google)	AW-18184097919	view source
Meta pixel id (Meta)	782136604977501	view source
Google Analytics 4 measurement id (Google)	G-20X9D8RBD1	view source
Google Analytics 4 measurement id (Google)	G-Q76F0QP19P	view source
Google Analytics 4 measurement id (Google)	G-R86HMFVNVP	view source
Google site verification (Google)	EO1uv6iIUfjoLNdTETD1J513zplDuyx6ZnPKesi-fD8	view source
Google Tag Manager container (Google)	GTM-W3PGX6JD	view source

Third-party hosts

Hosts outside beavertonmazda.com 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
cdn.complyauto.com	script	view source
content-container.edmunds.com	script	view source
prod.cdn.secureoffersites.com	script stylesheet	view source
scripts.foureyes.io	script	view source
snapshot.carfax.com	script	view source
www.googletagmanager.com	script iframe	view source

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 8) }. 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://www.beavertonmazda.com/inventory/cpo	html	377 KB	2026-10-09	2026-10-09
https://www.googletagmanager.com/gtag/js?id=AW-18184097919	js library	not fetched	2026-10-09	2026-10-09
https://www.googletagmanager.com/gtag/js?id=G-20X9D8RBD1	js library	not fetched	2026-10-09	2026-10-09
https://www.googletagmanager.com/gtag/js?id=G-Q76F0QP19P	js library	not fetched	2026-10-09	2026-10-09
https://www.googletagmanager.com/gtag/js?id=G-R86HMFVNVP	js library	not fetched	2026-10-09	2026-10-09
https://www.beavertonmazda.com/inventory/used	html	861.2 KB	2026-10-09	2026-10-09
https://www.beavertonmazda.com/inventory/new	html	455.5 KB	2026-10-09	2026-10-09
https://www.beavertonmazda.com/	html	112.5 KB	2026-10-09	2026-10-09

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-09 first crawl

4 pages, 8 files, 1.8 MB; 4 libraries, 7 identifiers, 6 third-party hosts
4 libraries added
- gtm
- gtag
- facebook-pixel
- @vitest/utils 5.0.2
7 identifiers added
- GTM-W3PGX6JD Google Tag Manager container
- AW-18184097919 Google Ads conversion id
- G-R86HMFVNVP Google Analytics 4 measurement id
- G-20X9D8RBD1 Google Analytics 4 measurement id
- G-Q76F0QP19P Google Analytics 4 measurement id
- 782136604977501 Meta pixel id
- EO1uv6iIUfjoLNdTETD1J513zplDuyx6ZnPKesi-fD8 Google site verification
8 third-party hosts added
8 files added

Questions about beavertonmazda.com

How does PageSourceSearch know what beavertonmazda.com 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 beavertonmazda.com 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 beavertonmazda.com?: 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 beavertonmazda.com?: 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.