Site profile
driving-records-ui.vercel.app
Built with chart.js 4.5.1, @amplitude/amplitude-js-gtm 3.25.0, paymob-pixel 1.2.7, @feedmepos/mf-report 5.29.2, @vamlabs/vam-chatbot 0.1.82, react-bootstrap 2.10.10, vue3-sfc-loader 0.9.5, cil-dropin-components 1.2.10, @3t-transform/threeteeui 1.12.1, wonder-image 2.1.2-alpha.4, vf-widgets 0.2.48, @solace-health/solace-entry-widget 2.0.5. 1 page and 3 stored files, last crawled 2026-10-03.
12 libraries 0 identifiers 18 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 |
|---|---|---|
| chart.js | 4.5.1 | 2026-10-03 |
| @amplitude/amplitude-js-gtm | 3.25.0 | 2026-10-03 |
| paymob-pixel | 1.2.7 | 2026-10-03 |
| @feedmepos/mf-report | 5.29.2 | 2026-10-03 |
| @vamlabs/vam-chatbot | 0.1.82 | 2026-10-03 |
| react-bootstrap | 2.10.10 | 2026-10-03 |
| vue3-sfc-loader | 0.9.5 | 2026-10-03 |
| cil-dropin-components | 1.2.10 | 2026-10-03 |
| @3t-transform/threeteeui | 1.12.1 | 2026-10-03 |
| wonder-image | 2.1.2-alpha.4 | 2026-10-03 |
| vf-widgets | 0.2.48 | 2026-10-03 |
| @solace-health/solace-entry-widget | 2.0.5 | 2026-10-03 |
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 driving-records-ui.vercel.app 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 |
|---|---|---|
| bgv-order-service.azurewebsites.net | connect | view source |
| cdn1.iconfinder.com | connect | view source |
| drivingrecord.com | connect | view source |
| encrypted-tbn0.gstatic.com | connect | view source |
| example.com | connect | view source |
| github.com | connect | view source |
| help.example.com | connect | view source |
| picsum.photos | connect | view source |
| reactjs.org | connect | view source |
| reactrouter.com | connect | view source |
| tailwindcss.com | connect | view source |
| upload.wikimedia.org | connect | view source |
| www.clipartmax.com | connect | view source |
| www.google.com | connect | view source |
| www.gstatic.com | script stylesheet | view source |
| www.svgrepo.com | connect | view source |
| www.trafficdepartment.gov | 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://driving-records-ui.vercel.app/asset-manifest.json | js | 1.8 KB | 2026-10-03 | 2026-10-03 |
| https://driving-records-ui.vercel.app/static/js/main.832f441c.js | js | 1.2 MB | 2026-10-03 | 2026-10-03 |
| https://driving-records-ui.vercel.app/ | html | 838 B | 2026-10-03 | 2026-10-03 |
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; 12 libraries, 0 identifiers, 18 third-party hosts
12 libraries added
- react-bootstrap 2.10.10
- @solace-health/solace-entry-widget 2.0.5
- vf-widgets 0.2.48
- paymob-pixel 1.2.7
- @vamlabs/vam-chatbot 0.1.82
- cil-dropin-components 1.2.10
- vue3-sfc-loader 0.9.5
- @amplitude/amplitude-js-gtm 3.25.0
- wonder-image 2.1.2-alpha.4
- @feedmepos/mf-report 5.29.2
- @3t-transform/threeteeui 1.12.1
- chart.js 4.5.1
19 third-party hosts added
Questions about driving-records-ui.vercel.app
- How does PageSourceSearch know what driving-records-ui.vercel.app 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 driving-records-ui.vercel.app 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 driving-records-ui.vercel.app?
- 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 driving-records-ui.vercel.app?
- 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.