Site profile
up-t.jp
Built with swiper 11, gtm, @accessible360/accessible-slick 1.0.1, twitter-widgets, json-db-admin 0.0.1, slick-slider 1.8.2, stickyfilljs 2.1.0, sweetalert2-neutral 11.22.2-neutral, @vitest/utils 5.0.2, files.photo.gallery 0.15.3, lazysizes-umd 3.0.1, @grigorov-it/mazer 2.2.0 and more. 5 pages and 31 stored files, last crawled 2026-10-02.
rank 451,987 14 libraries 3 identifiers 12 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 |
|---|---|---|
| swiper | 11 | 2026-10-02 |
| gtm | 2026-10-02 | |
| @accessible360/accessible-slick | 1.0.1 | 2026-10-02 |
| twitter-widgets | 2026-10-02 | |
| json-db-admin | 0.0.1 | 2026-10-02 |
| slick-slider | 1.8.2 | 2026-10-02 |
| stickyfilljs | 2.1.0 | 2026-10-02 |
| sweetalert2-neutral | 11.22.2-neutral | 2026-10-02 |
| @vitest/utils | 5.0.2 | 2026-10-02 |
| files.photo.gallery | 0.15.3 | 2026-10-02 |
| lazysizes-umd | 3.0.1 | 2026-10-02 |
| @grigorov-it/mazer | 2.2.0 | 2026-10-02 |
| is-in-viewport | 3.0.4 | 2026-09-24 |
| wc-datepicker | 0.13.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 |
|---|---|---|
| AdSense publisher id (Google) | ca-pub-6953105985591206 | view source |
| Facebook domain verification (Meta) | pfzzsaxv218qdjcnf74qilb66n5has | view source |
| Google Tag Manager container (Google) | GTM-TKSCFQJ | view source |
Third-party hosts
Hosts outside up-t.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.
| Host | Loaded as | Found in |
|---|---|---|
| 9250690.fls.doubleclick.net | iframe | view source |
| b.yjtag.jp | iframe | view source |
| cdn.jsdelivr.net | script stylesheet | view source |
| dynamic.criteo.com | script | view source |
| flag-gimn.ru | connect | view source |
| pagead2.googlesyndication.com | script | view source |
| pixel.mathtag.com | script | view source |
| platform.twitter.com | connect | view source |
| s.yimg.jp | script | view source |
| statics.a8.net | script | view source |
| up-t.net | connect | view source |
| www.googletagmanager.com | iframe | view source |
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
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
5 pages, 31 files, 1.3 MB; 12 libraries, 3 identifiers, 12 third-party hosts
12 libraries added
- gtm
- @vitest/utils 5.0.2
- json-db-admin 0.0.1
- stickyfilljs 2.1.0
- @accessible360/accessible-slick 1.0.1
- slick-slider 1.8.2
- lazysizes-umd 3.0.1
- sweetalert2-neutral 11.22.2-neutral
- files.photo.gallery 0.15.3
- @grigorov-it/mazer 2.2.0
- swiper 11
- twitter-widgets
3 identifiers added
- GTM-TKSCFQJ Google Tag Manager container
- ca-pub-6953105985591206 AdSense publisher id
- pfzzsaxv218qdjcnf74qilb66n5has Facebook domain verification
13 third-party hosts added
31 files added
- https://up-t.jp/ html
- https://up-t.jp/login.php html
- https://up-t.jp/search.php?type=voices html
- https://up-t.jp/item-detail/sub-category/%E5%8D%…%96T%E3%82%B7%E3%83%A3%E3%83%84 html
- https://up-t.jp/news html
- https://up-t.jp/common/js/utm-tracker.js js
- https://up-t.jp/common/lib/jquery/jquery-3.2.1.min.js js
- https://up-t.jp/common/js/pc/nobody_home.min.js?v=2.47 js
- https://up-t.jp/common/design/user/js/slick/slick.min.js js
- https://up-t.jp/common/js/pc/files/template-pc-h…ign-nobody-base-index.js?v=1.17 js
- https://up-t.jp/common/design/user/js/lightbox-2.6.min.js js
- https://up-t.jp/common/js/new-lazyload.min.js?v=1.4 js
- and 19 more
Questions about up-t.jp
- How does PageSourceSearch know what up-t.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 up-t.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 up-t.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 up-t.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.