Site profile
fx-jp.jp
Built with jquery 1.6.0, gtm, fancybox 3.0.1, twitter-widgets, flexslider 2.7.2, skrollr 0.6.26, jquery-slim 3.0.0, jquery.repeater 1.2.1, jquery.flot 0.8.3, @vitest/utils 5.0.2, lightbox 0.5.0, oauthio-web 0.6.2 and more. 4 pages and 15 stored files, last crawled 2026-10-02.
rank 541,852 16 libraries 1 identifier 14 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 |
|---|---|---|
| jquery | 1.6.0 | 2026-10-02 |
| gtm | 2026-10-02 | |
| fancybox | 3.0.1 | 2026-10-02 |
| twitter-widgets | 2026-10-02 | |
| flexslider | 2.7.2 | 2026-10-02 |
| skrollr | 0.6.26 | 2026-10-02 |
| jquery-slim | 3.0.0 | 2026-10-02 |
| jquery.repeater | 1.2.1 | 2026-10-02 |
| jquery.flot | 0.8.3 | 2026-10-02 |
| @vitest/utils | 5.0.2 | 2026-10-02 |
| lightbox | 0.5.0 | 2026-10-02 |
| oauthio-web | 0.6.2 | 2026-10-02 |
| lightbox2 | 2.12.0 | 2026-09-24 |
| tablesaw | 3.1.2 | 2026-09-24 |
| headjs | 1.0.3 | 2026-09-24 |
| @commercelayer/drop-in.js | 2.27.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-PPL77P | view source |
Third-party hosts
Hosts outside fx-jp.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 |
|---|---|---|
| ajax.googleapis.com | script | view source |
| api.bit.ly | connect | view source |
| avex.jp | script | view source |
| img.mixi.jp | connect | view source |
| mixi.jp | connect | view source |
| platform.twitter.com | connect | view source |
| plugins.mixi.jp | connect | view source |
| static.ak.fbcdn.net | connect | view source |
| static.mixi.jp | connect | view source |
| twitter-badges.s3.amazonaws.com | connect | view source |
| twitter.com | connect | view source |
| www.facebook.com | connect | view source |
| www.googletagmanager.com | iframe | view source |
| www.youtube.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
4 pages, 15 files, 457.3 KB; 12 libraries, 1 identifier, 14 third-party hosts
12 libraries added
- @vitest/utils 5.0.2
- gtm
- jquery.repeater 1.2.1
- jquery-slim 3.0.0
- lightbox 0.5.0
- jquery.flot 0.8.3
- oauthio-web 0.6.2
- fancybox 3.0.1
- skrollr 0.6.26
- flexslider 2.7.2
- jquery 1.6.0
- twitter-widgets
1 identifier added
- GTM-PPL77P Google Tag Manager container
14 third-party hosts added
15 files added
- https://fx-jp.jp/ html
- https://fx-jp.jp/discography/shop.php?id=1024325 html
- https://fx-jp.jp/news/detail.php?id=1075004 html
- https://fx-jp.jp/schedule/?c=&year=&page=1 html
- https://fx-jp.jp/js/jquery.js js
- https://fx-jp.jp/js/jquery.hoverfade.js js
- https://fx-jp.jp/js/smoothScroll.js js
- https://fx-jp.jp/js/shareSoc.js js
- https://fx-jp.jp/js/heightLine.js js
- https://fx-jp.jp/js/jquery.ticker.js js
- https://fx-jp.jp/js/jquery.fancybox.js js
- https://fx-jp.jp/js/skrollr.min.js js
- and 3 more
Questions about fx-jp.jp
- How does PageSourceSearch know what fx-jp.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 fx-jp.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 fx-jp.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 fx-jp.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.