Site profile
bridgingdictionary.org
Built with @popperjs/core 2.11.8, gtag, swagger-ui-dist 5.33.0, @feathery/react 2.96.0, @cognigy/webchat 3.50.0, paymob-pixel 1.2.7, rsuite 6.2.4, formiojs 4.21.7, @stlite/mountable 0.75.0, @tolgee/web 7.2.1, @vueform/multiselect 2.6.11, @sledge-app/js 2.0.114 and more. 2 pages and 11 stored files.
rank 6,716,285 16 libraries 1 identifier 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 |
|---|---|---|
| @popperjs/core | 2.11.8 | 2026-09-28 |
| gtag | 2026-09-28 | |
| swagger-ui-dist | 5.33.0 | 2026-09-28 |
| @feathery/react | 2.96.0 | 2026-09-28 |
| @cognigy/webchat | 3.50.0 | 2026-09-28 |
| paymob-pixel | 1.2.7 | 2026-09-28 |
| rsuite | 6.2.4 | 2026-09-28 |
| formiojs | 4.21.7 | 2026-09-28 |
| @stlite/mountable | 0.75.0 | 2026-09-28 |
| @tolgee/web | 7.2.1 | 2026-09-28 |
| @vueform/multiselect | 2.6.11 | 2026-09-28 |
| @sledge-app/js | 2.0.114 | 2026-09-28 |
| @okta/okta-signin-widget | 7.49.1 | 2026-09-28 |
| @joyfill/components | 4.0.0-rc26 | 2026-09-28 |
| @story-telling-reporter/react-embed-code-generator | 2.2.20 | 2026-09-28 |
| @solace-health/solace-entry-widget | 2.0.5 | 2026-09-28 |
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-D7MJ1ELBE2 | view source |
Third-party hosts
The stored pages and scripts reference no host outside bridgingdictionary.org.
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 bridgingdictionary.org
- How does PageSourceSearch know what bridgingdictionary.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 bridgingdictionary.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 bridgingdictionary.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 bridgingdictionary.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.