PageSourceSearch

Site profile

qrp.jp

No known library was recognised in its stored source. 4 pages and 5 stored files, last crawled 2026-10-07.

rank 12,613,832 0 libraries 0 identifiers 24 third-party hosts 1 crawl open the site

Technologies and libraries

No library file or bundled library code was recognised in the stored source. The site may use code of its own, load its libraries from a host the crawler does not fetch, or be too new in the index.

Tracking, tag and verification IDs

No analytics property, tag manager container, pixel or site-verification token was found in the stored source.

Third-party hosts

Hosts outside qrp.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
7k1cpt.cocolog-nifty.com connect view source
blog.livedoor.jp connect view source
gcd00322.cocolog-nifty.com connect view source
ja1nlx.blog109.fc2.com connect view source
ja2nlt.cocolog-nifty.com connect view source
ja3avo.blog81.fc2.com connect view source
ja5cqh.air-nifty.com connect view source
jf2sqb.cocolog-tnc.com connect view source
jh2cmh.cocolog-nifty.com connect view source
ji1izr.air-nifty.com connect view source
jj8gfl.air-nifty.com connect view source
jl1mwi.exblog.jp connect view source
jm1ekm.cocolog-nifty.com connect view source
jn1bpm.exblog.jp connect view source
jo2asq.air-nifty.com connect view source
jp1lrt.asablo.jp connect view source
jq1ndh.cocolog-nifty.com connect view source
jq1ocr.exblog.jp connect view source
jr6ikd.cocolog-nifty.com connect view source
nuttycellist.blog77.fc2.com connect view source
susuwatari.cocolog-nifty.com connect view source
ttsunoda.cocolog-nifty.com connect view source
www.zcr.jp connect view source
yuurakus.exblog.jp connect view source

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 5) }. 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
http://qrp.jp/cgi-bin/sitelist.cgi?num=30/ js 6.4 KB 2026-10-07 2026-10-07
http://qrp.jp/cgi-bin/newscategory.cgi?Key=Report html 131 B 2026-10-07 2026-10-07
https://qrp.jp/rss/hotrss50.shtml html 77.9 KB 2026-10-07 2026-10-07
https://qrp.jp/ html 15.5 KB 2026-10-07 2026-10-07
https://qrp.jp/blog/2012/08/25-001.shtml html 7.7 KB 2026-10-07 2026-10-07

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

    4 pages, 5 files, 107.5 KB; 0 libraries, 0 identifiers, 24 third-party hosts

    24 third-party hosts added
    5 files added

Questions about qrp.jp

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