Site profile
rising-pro.jp
Built with jquery 1.3.2, gtag, google-apis, twitter-widgets, @vitest/utils 5.0.2, stackedboost-shopify-assets 0.2.0, super-slide 2.1.4, @chakra-ui/theme 3.4.6. 5 pages and 23 stored files, last crawled 2026-10-02.
rank 1,146,112 8 libraries 1 identifier 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 |
|---|---|---|
| jquery | 1.3.2 | 2026-10-02 |
| gtag | 2026-10-02 | |
| google-apis | 2026-10-02 | |
| twitter-widgets | 2026-10-02 | |
| @vitest/utils | 5.0.2 | 2026-10-02 |
| stackedboost-shopify-assets | 0.2.0 | 2026-10-02 |
| super-slide | 2.1.4 | 2026-10-02 |
| @chakra-ui/theme | 3.4.6 | 2026-09-25 |
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 Analytics 4 measurement id (Google) | G-QVG8ZF22WL | view source |
Third-party hosts
Hosts outside rising-pro.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 |
|---|---|---|
| apis.google.com | iframe connect | view source |
| mixi.jp | connect | view source |
| platform.twitter.com | script iframe | view source |
| plugins.mixi.jp | iframe | view source |
| search.twitter.com | connect | view source |
| share.gree.jp | iframe connect | view source |
| sp.visioncast.jp | iframe | view source |
| static.mixi.jp | script connect | view source |
| twitter.com | connect | view source |
| www.facebook.com | iframe connect | view source |
| www.googleadservices.com | script | view source |
| www.googletagmanager.com | script | 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, 23 files, 1.5 MB; 7 libraries, 1 identifier, 12 third-party hosts
7 libraries added
- gtag
- stackedboost-shopify-assets 0.2.0
- @vitest/utils 5.0.2
- jquery 1.3.2
- super-slide 2.1.4
- twitter-widgets
- google-apis
1 identifier added
- G-QVG8ZF22WL Google Analytics 4 measurement id
17 third-party hosts added
23 files added
- https://rising-pro.jp/ html
- https://www.rising-pro.jp/news/news_archives/new…?aid=fourcarat&nID=VF5uhLRxu2 html
- https://rising-pro.jp/index.html html
- https://rising-pro.jp/artist/index.html html
- https://rising-pro.jp/artist/oginome/index.html html
- https://rising-pro.jp/js/site.js js
- https://rising-pro.jp/js/jquery1.3.2.js js
- https://rising-pro.jp/js/jquery.lightbox-0.5.js js
- https://rising-pro.jp/js/flach_check.js js
- https://rising-pro.jp/js/jquery.tweet.js js
- https://rising-pro.jp/js/jquery.fixedUI.js js
- https://rising-pro.jp/js/jquery-1.4.2.min.js js
- and 11 more
Questions about rising-pro.jp
- How does PageSourceSearch know what rising-pro.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 rising-pro.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 rising-pro.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 rising-pro.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.