Site profile
lexus.jp
Built with swiper 11, jquery 3.7.1, gtm, simplebar, addsearch-search-ui 0.10.9, fomantic-ui 2.9.4, dashjs 5.2.1, @tensorflow/tfjs 4.22.0, @studio-freight/lenis 1.0.42, kore-web-sdk 11.28.1, papaparse 5.7.0, @truex/ctv-ad-renderer 1.10.1 and more. 5 pages and 56 stored files.
rank 396,250 18 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 |
|---|---|---|
| swiper | 11 | 2026-09-24 |
| jquery | 3.7.1 | 2026-09-24 |
| gtm | 2026-09-24 | |
| simplebar | 2026-09-24 | |
| addsearch-search-ui | 0.10.9 | 2026-09-24 |
| fomantic-ui | 2.9.4 | 2026-09-24 |
| dashjs | 5.2.1 | 2026-09-24 |
| @tensorflow/tfjs | 4.22.0 | 2026-09-24 |
| @studio-freight/lenis | 1.0.42 | 2026-09-24 |
| kore-web-sdk | 11.28.1 | 2026-09-24 |
| papaparse | 5.7.0 | 2026-09-24 |
| @truex/ctv-ad-renderer | 1.10.1 | 2026-09-24 |
| adaptivecards | 3.0.6 | 2026-09-24 |
| reverie-stt-sdk | 0.24.0 | 2026-09-24 |
| image-compare-viewer | 1.6.2 | 2026-09-24 |
| face-age | 2.4.6 | 2026-09-24 |
| @alaskaairux/auro-icon | 3.4.4 | 2026-09-24 |
| @pdftron/webviewer | 12.1.0 | 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 Tag Manager container (Google) | GTM-T9NWLH | view source |
Third-party hosts
The stored pages and scripts reference no host outside lexus.jp.
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 lexus.jp
- How does PageSourceSearch know what lexus.jp 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 lexus.jp 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 lexus.jp?
- 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 lexus.jp?
- 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.