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

pivotpointsecurity.com

Built with gtm, gtag, hotjar. 5 pages and 6 stored files, last crawled 2026-10-03.

rank 1,888,788 3 libraries 9 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-03
gtag		2026-10-03
hotjar		2026-10-03

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)	7F1831E599A2167F6ECDCCF59C339F44	view source
Google Analytics 4 measurement id (Google)	G-CR6D7RN4XP	view source
Google Analytics 4 measurement id (Google)	G-DLK5F8LFHD	view source
Google site verification (Google)	IEaUFvU3JQaVH5Fn4mbwFH-FeBpsDB9EE184bPSqus4	view source
Google site verification (Google)	mU9VNALTTDHxx5T9eEpWy92bAEihlAXWdTGvgZgYGsM	view source
Google site verification (Google)	ykU8RtBQqBgq0lTGr-SmRGSpJuGjhZ4SMOfz9pvgwOA	view source
Google Tag Manager container (Google)	GTM-KPJBTJ	view source
Hotjar site id (Hotjar)	2942323	view source
LinkedIn Insight Tag partner id (LinkedIn)	153890	view source

Third-party hosts

Hosts outside pivotpointsecurity.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-ileccep.nitrocdn.com	stylesheet	view source
cdn.omniconvert.com	script	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://www.pivotpointsecurity.com/wp-includes/j…?ver=7496969728ca0f95732d	js	4.9 KB	2026-10-03	current
https://www.pivotpointsecurity.com/services/	html	590.4 KB	2026-10-03	2026-10-03
https://www.pivotpointsecurity.com/podcasts/epis…nd-best-practices-with-chatgpt/	html	541.9 KB	2026-10-03	2026-10-03
https://www.pivotpointsecurity.com/company/contact/	html	518.2 KB	2026-10-03	2026-10-03
https://www.pivotpointsecurity.com/blog/	html	710.5 KB	2026-10-03	2026-10-03
https://www.pivotpointsecurity.com/	html	649.8 KB	2026-10-03	2026-10-03

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

5 pages, 6 files, 2.9 MB; 3 libraries, 9 identifiers, 2 third-party hosts
3 libraries added
- gtm
- gtag
- hotjar
9 identifiers added
- GTM-KPJBTJ Google Tag Manager container
- G-DLK5F8LFHD Google Analytics 4 measurement id
- 2942323 Hotjar site id
- G-CR6D7RN4XP Google Analytics 4 measurement id
- IEaUFvU3JQaVH5Fn4mbwFH-FeBpsDB9EE184bPSqus4 Google site verification
- ykU8RtBQqBgq0lTGr-SmRGSpJuGjhZ4SMOfz9pvgwOA Google site verification
- mU9VNALTTDHxx5T9eEpWy92bAEihlAXWdTGvgZgYGsM Google site verification
- 7F1831E599A2167F6ECDCCF59C339F44 Bing site verification
- 153890 LinkedIn Insight Tag partner id
2 third-party hosts added
- cdn.omniconvert.com
- cdn-ileccep.nitrocdn.com
6 files added

Questions about pivotpointsecurity.com

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