Site profile
naruto-kabuki.com
Built with gtag, twitter-widgets, stackedboost-shopify-assets 0.2.0, hideseek 0.8.0, jcarouselswipe 0.3.7. 5 pages and 16 stored files, last crawled 2026-10-05.
rank 10,865,427 5 libraries 1 identifier 4 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 |
|---|---|---|
| gtag | 2026-10-05 | |
| twitter-widgets | 2026-10-05 | |
| stackedboost-shopify-assets | 0.2.0 | 2026-10-05 |
| hideseek | 0.8.0 | 2026-10-05 |
| jcarouselswipe | 0.3.7 | 2026-10-05 |
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 |
|---|---|---|
| Universal Analytics property id (Google) | UA-116756824-1 | view source |
Third-party hosts
Hosts outside naruto-kabuki.com 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 |
|---|---|---|
| api.html5media.info | script | view source |
| platform.twitter.com | script | view source |
| www.googletagmanager.com | script | 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
5 pages, 16 files, 682.9 KB; 5 libraries, 1 identifier, 4 third-party hosts
5 libraries added
- gtag
- stackedboost-shopify-assets 0.2.0
- jcarouselswipe 0.3.7
- hideseek 0.8.0
- twitter-widgets
1 identifier added
- UA-116756824-1 Universal Analytics property id
4 third-party hosts added
16 files added
- https://naruto-kabuki.com/ html
- https://naruto-kabuki.com/index.html html
- https://naruto-kabuki.com/tokyo.html html
- https://naruto-kabuki.com/minamiza.html html
- https://naruto-kabuki.com/english2/ html
- https://naruto-kabuki.com/js/jquery-2.1.4.js js
- https://naruto-kabuki.com/js/smoothScroll.js js
- https://naruto-kabuki.com/js/jquery.meanmenu.js js
- https://naruto-kabuki.com/umodal/umodal.min.js js
- https://naruto-kabuki.com/js/megamenu.js js
- https://naruto-kabuki.com/english2/js/jquery.js js
- https://naruto-kabuki.com/english2/js/smoothScroll.js js
- and 4 more
Questions about naruto-kabuki.com
- How does PageSourceSearch know what naruto-kabuki.com 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 naruto-kabuki.com 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 naruto-kabuki.com?
- 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 naruto-kabuki.com?
- 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.