Site profile
burgundywave.com
Built with swiper 6.4.15, sweetalert2 11.4.4, gtag, webpack, flatpickr 4.6.13, @zonos/elements 1.3.289, vue 1.0.0-beta.19, @covet-pics/covet-pics-widget 0.179.0, chart.js 4.5.1, @wix/design-system 1.328.0, @pine-ds/core 4.0.0, summernote 0.9.1 and more. 5 pages and 32 stored files.
rank 57,117 37 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 |
|---|---|---|
| swiper | 6.4.15 | 2026-09-24 |
| sweetalert2 | 11.4.4 | 2026-09-24 |
| gtag | 2026-09-24 | |
| webpack | 2026-09-24 | |
| flatpickr | 4.6.13 | 2026-09-24 |
| @zonos/elements | 1.3.289 | 2026-09-24 |
| vue | 1.0.0-beta.19 | 2026-09-24 |
| @covet-pics/covet-pics-widget | 0.179.0 | 2026-09-24 |
| chart.js | 4.5.1 | 2026-09-24 |
| @wix/design-system | 1.328.0 | 2026-09-24 |
| @pine-ds/core | 4.0.0 | 2026-09-24 |
| summernote | 0.9.1 | 2026-09-24 |
| mobile-detect | 1.4.5 | 2026-09-24 |
| core-js-bundle | 3.50.0 | 2026-09-24 |
| stripe-js | v3 | 2026-09-24 |
| kore-web-sdk | 11.28.1 | 2026-09-24 |
| @mezereon/ui-shopify | 2.0.9 | 2026-09-24 |
| @constructor-io/constructorio-ui-autocomplete | 1.30.1 | 2026-09-24 |
| @truex/ctv-ad-renderer | 1.10.1 | 2026-09-24 |
| @roadtrip/components | 3.58.0 | 2026-09-24 |
| sticksy | 0.2.0 | 2026-09-24 |
| isotope-layout | 3.0.6 | 2026-09-24 |
| @coreui/coreui-pro | 5.27.1 | 2026-09-24 |
| @speechkit/speechkit-audio-player | 3.18.30 | 2026-09-24 |
| pdf-parse | 2.4.5 | 2026-09-24 |
| @desivocal/agents-cdn | 1.0.21 | 2026-09-24 |
| v-calendar | 2.4.2 | 2026-09-24 |
| @justifi/webcomponents | 6.14.3 | 2026-09-24 |
| @goodgamestudios/cxf-runtime | 0.3.2 | 2026-09-24 |
| json-db-admin | 0.0.1 | 2026-09-24 |
| vue-multiselect | 3.5.0 | 2026-09-24 |
| jsxgraph | 1.13.3 | 2026-09-24 |
| @feedmepos/mf-report | 5.29.2 | 2026-09-24 |
| vis-timeline | 8.5.4 | 2026-09-24 |
| @govbr-ds/core | 3.7.0 | 2026-09-24 |
| @epigraph/configurator | 2.7.0 | 2026-09-24 |
| inclusive-dates | 0.1.10 | 2026-09-24 |
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 Analytics 4 measurement id (Google) | G-2W2JZE5H5T | view source |
| Google tag id (Google) | GT-M6BBBWJ | view source |
Third-party hosts
The stored pages and scripts reference no host outside burgundywave.com.
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 burgundywave.com
- How does PageSourceSearch know what burgundywave.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 burgundywave.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 burgundywave.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 burgundywave.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.