Site profile
btcpayserver.org
Built with vue 3.6.5, @wix/design-system 1.328.0, mermaid 12.0.0, dashjs 5.2.1, @marimo-team/frontend 0.25.0, medium-zoom 1.1.0, redoc 2.0.0-rc.54, @commonlit/commonlit-frontend 0.1.0, @mermaid-js/layout-elk 1.0.0, json-db-admin 0.0.1, @epigraph/configurator 2.7.0, supafolio-sdk 1.4.1 and more. 5 pages and 11 stored files.
rank 392,221 15 libraries 0 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 |
|---|---|---|
| vue | 3.6.5 | 2026-09-24 |
| @wix/design-system | 1.328.0 | 2026-09-24 |
| mermaid | 12.0.0 | 2026-09-24 |
| dashjs | 5.2.1 | 2026-09-24 |
| @marimo-team/frontend | 0.25.0 | 2026-09-24 |
| medium-zoom | 1.1.0 | 2026-09-24 |
| redoc | 2.0.0-rc.54 | 2026-09-24 |
| @commonlit/commonlit-frontend | 0.1.0 | 2026-09-24 |
| @mermaid-js/layout-elk | 1.0.0 | 2026-09-24 |
| json-db-admin | 0.0.1 | 2026-09-24 |
| @epigraph/configurator | 2.7.0 | 2026-09-24 |
| supafolio-sdk | 1.4.1 | 2026-09-24 |
| biel-search | 0.1.89 | 2026-09-24 |
| vditor | 4.0.0 | 2026-09-24 |
| latex.js | 0.12.6 | 2026-09-24 |
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
The stored pages and scripts reference no host outside btcpayserver.org.
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
| File | Kind | Size | Collected | Versions |
|---|---|---|---|---|
| https://cdn.jsdelivr.net/npm/[email protected]/bundles/redoc.standalone.js | js library | not fetched | 2026-09-24 | current |
| https://docs.btcpayserver.org/vendor/mermaid.min.js | js | 3.4 MB | 2026-09-24 | current |
| https://docs.btcpayserver.org/assets/js/3.5750a22f.js | js | 10.6 KB | 2026-09-24 | current |
| https://docs.btcpayserver.org/assets/js/82.c7d18a30.js | js | 7.5 KB | 2026-09-24 | current |
| https://docs.btcpayserver.org/assets/js/app.9ae4abfb.js | js | 403.3 KB | 2026-09-24 | current |
| https://btcpayserver.org/bg/ | html | 71 KB | 2026-09-24 | current |
| https://btcpayserver.org/js/scripts.js | js | 4.7 KB | 2026-09-24 | current |
| https://btcpayserver.org/ar/ | html | 70.1 KB | 2026-09-24 | current |
| https://docs.btcpayserver.org/API/Greenfield/v1/ | html | 780 B | 2026-09-24 | current |
| https://docs.btcpayserver.org/Apps/ | html | 37 KB | 2026-09-24 | current |
| https://btcpayserver.org/ | html | 68 KB | 2026-09-24 | current |
Timeline
No crawl has recorded a snapshot of this site yet; snapshots are written by every crawl from now on.
Questions about btcpayserver.org
- How does PageSourceSearch know what btcpayserver.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 btcpayserver.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 btcpayserver.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 btcpayserver.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.