Site profile
futabaya-inn.jp
Built with bxslider 4.2.17, jsxgraph 1.13.3, slick-lightbox 0.2.12, jquery.flipster 1.1.6, @grigorov-it/mazer 2.2.0. 5 pages and 16 stored files, last crawled 2026-10-05.
rank 10,935,816 5 libraries 0 identifiers 5 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 |
|---|---|---|
| bxslider | 4.2.17 | 2026-10-05 |
| jsxgraph | 1.13.3 | 2026-10-05 |
| slick-lightbox | 0.2.12 | 2026-10-05 |
| jquery.flipster | 1.1.6 | 2026-10-05 |
| @grigorov-it/mazer | 2.2.0 | 2026-10-05 |
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 futabaya-inn.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 |
|---|---|---|
| maxcdn.bootstrapcdn.com | stylesheet | view source |
| webfonts.sakura.ne.jp | script | view source |
| www.google.com | iframe | view source |
| www.npr.org | 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
5 pages, 16 files, 384.8 KB; 5 libraries, 0 identifiers, 5 third-party hosts
5 libraries added
- jquery.flipster 1.1.6
- @grigorov-it/mazer 2.2.0
- jsxgraph 1.13.3
- bxslider 4.2.17
- slick-lightbox 0.2.12
5 third-party hosts added
16 files added
- https://futabaya-inn.jp/ html
- https://futabaya-inn.jp/blog html
- https://futabaya-inn.jp/archives/category/news html
- https://futabaya-inn.jp/about html
- https://futabaya-inn.jp/link html
- https://futabaya-inn.jp/wp/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 js
- https://futabaya-inn.jp/wp/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1 js
- https://futabaya-inn.jp/wp/wp-content/cache/auto…49ed5089677ed3d7e2f11fc8942.php js
- https://futabaya-inn.jp/wp/wp-content/cache/auto…2cbf2fe204f5a7317.php?ver=4.3.2 js
- https://futabaya-inn.jp/wp/wp-content/cache/auto…14c9c3bbd05ead0c6.php?ver=4.3.2 js
- https://futabaya-inn.jp/wp/wp-content/cache/auto…ed6183db5f20708d4.php?ver=4.3.2 js
- https://futabaya-inn.jp/wp/wp-content/cache/auto…291e38b45ef490e56.php?ver=4.3.2 js
- and 4 more
Questions about futabaya-inn.jp
- How does PageSourceSearch know what futabaya-inn.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 futabaya-inn.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 futabaya-inn.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 futabaya-inn.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.