Site profile
ayaka-fc.jp
Built with gtm, gtag, silvermine-videojs-quality-selector 1.1.2, recaptcha, sa-sdk-javascript 1.27.14, kore-web-sdk 11.28.1, bootstrap-filestyle 1.2.1, slick-slider 1.8.2, slick-carousel-browserify 1.6.12, layui-src 2.6.8. 5 pages and 12 stored files, last crawled 2026-10-04.
rank 10,607,924 10 libraries 2 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 |
|---|---|---|
| gtm | 2026-10-04 | |
| gtag | 2026-10-04 | |
| silvermine-videojs-quality-selector | 1.1.2 | 2026-10-04 |
| recaptcha | 2026-10-04 | |
| sa-sdk-javascript | 1.27.14 | 2026-10-04 |
| kore-web-sdk | 11.28.1 | 2026-10-04 |
| bootstrap-filestyle | 1.2.1 | 2026-10-04 |
| slick-slider | 1.8.2 | 2026-10-04 |
| slick-carousel-browserify | 1.6.12 | 2026-10-04 |
| layui-src | 2.6.8 | 2026-10-04 |
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-D8M4H57TKF | view source |
| Google Tag Manager container (Google) | GTM-WR85XP3M | view source |
Third-party hosts
Hosts outside ayaka-fc.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 |
|---|---|---|
| 3gs.veritrans.co.jp | connect | view source |
| api3.veritrans.co.jp | connect | view source |
| player-api.p.uliza.jp | connect | view source |
| www.google.com | script | view source |
| www.googletagmanager.com | script 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, 12 files, 621.2 KB; 10 libraries, 2 identifiers, 5 third-party hosts
10 libraries added
- gtm
- gtag
- recaptcha
- kore-web-sdk 11.28.1
- sa-sdk-javascript 1.27.14
- layui-src 2.6.8
- bootstrap-filestyle 1.2.1
- silvermine-videojs-quality-selector 1.1.2
- slick-slider 1.8.2
- slick-carousel-browserify 1.6.12
2 identifiers added
- GTM-WR85XP3M Google Tag Manager container
- G-D8M4H57TKF Google Analytics 4 measurement id
6 third-party hosts added
12 files added
- https://ayaka-fc.jp/ html
- https://ayaka-fc.jp/signin html
- https://ayaka-fc.jp/contents/topics/shop html
- https://ayaka-fc.jp/contents/blog html
- https://ayaka-fc.jp/about/account html
- https://ayaka-fc.jp/assets/ayaka/app/application…e39650b8fde4f9f66d65c4aea38a.js js
- https://ayaka-fc.jp/assets/ayaka/app/separate_fi…f94dd953ee4c755461c9ad559723.js js
- https://ayaka-fc.jp/assets/app/application_selec…b1046a9bc354aa9850dec380a4c0.js js
- https://ayaka-fc.jp/assets/ayaka/app/separate_fi…739db34ced3c099703b415097532.js js
- https://www.googletagmanager.com/gtag/js?id=G-D8M4H57TKF js
- https://www.google.com/recaptcha/api.js js
- https://www.googletagmanager.com/gtm.js?id=GTM-WR85XP3M js
Questions about ayaka-fc.jp
- How does PageSourceSearch know what ayaka-fc.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 ayaka-fc.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 ayaka-fc.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 ayaka-fc.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.