Site profile
regional-heritage-centre.org
Built with webpack, vanta 0.5.24, @goongmaps/goong-js 1.0.9, leaflet.vectorgrid 1.3.0, plotly.js 4.1.1, gitalk 1.8.0, react-rte 0.16.5, vue-directive-tooltip 1.6.3. 1 page and 3 stored files, last crawled 2026-10-08.
rank 14,040,996 8 libraries 0 identifiers 10 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 |
|---|---|---|
| webpack | 2026-10-08 | |
| vanta | 0.5.24 | 2026-10-08 |
| @goongmaps/goong-js | 1.0.9 | 2026-10-08 |
| leaflet.vectorgrid | 1.3.0 | 2026-10-08 |
| plotly.js | 4.1.1 | 2026-10-08 |
| gitalk | 1.8.0 | 2026-10-08 |
| react-rte | 0.16.5 | 2026-10-08 |
| vue-directive-tooltip | 1.6.3 | 2026-10-08 |
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
Hosts outside regional-heritage-centre.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 |
|---|---|---|
| api.mapbox.com | connect | view source |
| login.microsoftonline.com | connect | view source |
| luoralhistoryapi.azurewebsites.net | connect | view source |
| oralhistoryblob.blob.core.windows.net | connect | view source |
| reactjs.org | connect | view source |
| redrosecollections.lancashire.gov.uk | connect | view source |
| www.googletagmanager.com | connect | view source |
| www.lancaster.ac.uk | connect | view source |
| www.mapbox.com | connect | view source |
| www.w3.org | connect | view source |
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
| File | Kind | Size | Collected | Versions |
|---|---|---|---|---|
| https://www.regional-heritage-centre.org/service-worker.js | js | 3.7 KB | 2026-10-08 | 2026-10-08 |
| https://www.regional-heritage-centre.org/static/js/main.9b8615bc.js | js | 1.2 MB | 2026-10-08 | 2026-10-08 |
| https://www.regional-heritage-centre.org/ | html | 620 B | 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.
-
first crawl
1 page, 3 files, 1.2 MB; 8 libraries, 0 identifiers, 10 third-party hosts
8 libraries added
- plotly.js 4.1.1
- leaflet.vectorgrid 1.3.0
- @goongmaps/goong-js 1.0.9
- vanta 0.5.24
- react-rte 0.16.5
- vue-directive-tooltip 1.6.3
- gitalk 1.8.0
- webpack
10 third-party hosts added
Questions about regional-heritage-centre.org
- How does PageSourceSearch know what regional-heritage-centre.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 regional-heritage-centre.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 regional-heritage-centre.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 regional-heritage-centre.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.