Site profile
wells.pt
Built with gtm, @zonos/elements 1.3.289, @growthbook/growthbook 1.7.0, @findify/bundle 7.1.108, recaptcha, vuex 4.1.0, cleave.js 1.6.0, reverie-stt-sdk 0.24.0, cloudflare-insights, dom-mutator 0.7.0, cookiebot, json-db-admin 0.0.1 and more. 3 pages and 26 stored files.
rank 1,888,862 18 libraries 2 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 |
|---|---|---|
| gtm | 2026-09-25 | |
| @zonos/elements | 1.3.289 | 2026-09-25 |
| @growthbook/growthbook | 1.7.0 | 2026-09-25 |
| @findify/bundle | 7.1.108 | 2026-09-25 |
| recaptcha | 2026-09-25 | |
| vuex | 4.1.0 | 2026-09-25 |
| cleave.js | 1.6.0 | 2026-09-25 |
| reverie-stt-sdk | 0.24.0 | 2026-09-25 |
| cloudflare-insights | 2026-09-25 | |
| dom-mutator | 0.7.0 | 2026-09-25 |
| cookiebot | 2026-09-25 | |
| json-db-admin | 0.0.1 | 2026-09-25 |
| universalviewer | 4.4.4 | 2026-09-25 |
| sp-supermarquee | 3.1.2 | 2026-09-25 |
| vue3-sfc-loader | 0.9.5 | 2026-09-25 |
| extra-map-card | 1.8.0 | 2026-09-25 |
| @flittpayments/checkout | 1.17.2 | 2026-09-25 |
| react-grid-layout | 2.2.4 | 2026-09-25 |
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 Tag Manager container (Google) | GTM-WQ66VSX | view source |
| reCAPTCHA site key (Google) | 6LfIbS0aAAAAABGsujxd25J5qndQ-vzOwOJFzi6r | view source |
Third-party hosts
The stored pages and scripts reference no host outside wells.pt.
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
Timeline
No crawl has recorded a snapshot of this site yet; snapshots are written by every crawl from now on.
Questions about wells.pt
- How does PageSourceSearch know what wells.pt 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 wells.pt 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 wells.pt?
- 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 wells.pt?
- 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.