PageSourceSearch

Site profile

towers.jp

Built with jquery 3.5.1, gtm, webpack, axios, lit-html, moment, promise-polyfill, regenerator-runtime, @babel/runtime, object-fit-images, flv.js 1.6.2, papaparse and more. 6 pages and 12 stored files, last crawled 2026-10-02.

rank 522,897 17 libraries 1 identifier 9 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.

LibraryVersionSeen
jquery 3.5.1 2026-10-02
gtm 2026-10-02
webpack 2026-10-02
axios 2026-10-02
lit-html 2026-10-02
moment 2026-10-02
promise-polyfill 2026-10-02
regenerator-runtime 2026-10-02
@babel/runtime 2026-10-02
object-fit-images 2026-10-02
flv.js 1.6.2 2026-10-02
papaparse 2026-10-02
rsuite 6.2.4 2026-10-02
slick-slider 2026-10-02
nodelist-foreach-polyfill 2026-10-02
editorjs-text-alignment-blocktune 1.0.3 2026-10-02
jsoneditor 10.4.3 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.

WhatValueFound in
Google Tag Manager container (Google) GTM-KS3THJ9 view source

Third-party hosts

Hosts outside towers.jp 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.

HostLoaded asFound in
ajaxzip3.github.io script view source
bit.ly connect view source
code.jquery.com script view source
docs.google.com connect view source
towers-sub.jp connect view source
towers.goldkey.work connect view source
use.fontawesome.com stylesheet view source
www.googletagmanager.com iframe view source
www.w3.org connect view source

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 12) }. Versions are the crawls at which the file was new or its content changed; each opens the file as it was then, rebuilt from the same stored chunks.

FileKindSizeCollectedVersions
https://code.jquery.com/jquery-3.5.1.min.js js library not fetched 2026-10-02 current
https://www.towers.jp/webroot/restaurant/js/top.js js library 542.4 KB 2026-10-02 current
https://www.towers.jp/webroot/restaurant/js/common.js js 329.3 KB 2026-10-02 current
https://www.towers.jp/webroot/main/js/top.js js library 1.3 MB 2026-10-02 2026-10-02
https://www.towers.jp/webroot/main/js/common.js js 421.5 KB 2026-10-02 current
https://www.towers.jp/webroot/common/js/common.js js 343.8 KB 2026-10-02 current
https://www.towers.jp/restaurant html 134.9 KB 2026-10-02 2026-10-02
https://www.towers.jp/language html 17.3 KB 2026-10-02 current
https://www.towers.jp/contact/ html 33.1 KB 2026-10-02 2026-10-02
https://www.towers.jp/news/244 html 16.8 KB 2026-10-02 2026-10-02
https://www.towers.jp/ html 39.5 KB 2026-10-02 2026-10-02
https://www.towers.jp/news/239 html 17 KB 2026-09-24 current

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.

  1. first crawl

    5 pages, 11 files, 3.1 MB; 17 libraries, 1 identifier, 9 third-party hosts

    17 libraries added
    • gtm
    • jquery
    • nodelist-foreach-polyfill
    • object-fit-images
    • editorjs-text-alignment-blocktune 1.0.3
    • webpack
    • slick-slider
    • @babel/runtime
    • moment
    • papaparse
    • promise-polyfill
    • regenerator-runtime
    • and 5 more
    1 identifier added
    9 third-party hosts added
    11 files added

Questions about towers.jp

How does PageSourceSearch know what towers.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 towers.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 towers.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 towers.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.