Site profile
sanga-fc.jp
Built with jquery 1.11.1, gtm, facebook-sdk, twitter-widgets, kenwheeler/slick 1.8.1, @vitest/utils 5.0.2. 5 pages and 16 stored files, last crawled 2026-10-02.
rank 406,560 6 libraries 2 identifiers 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.11.1 | 2026-10-02 |
| gtm | 2026-10-02 | |
| facebook-sdk | 2026-10-02 | |
| twitter-widgets | 2026-10-02 | |
| kenwheeler/slick | 1.8.1 | 2026-10-02 |
| @vitest/utils | 5.0.2 | 2026-10-02 |
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 site verification (Google) | eRDw5LG-1L7Q1EYgh_QOg_aZDgjT35putdatkrBhzck | view source |
| Google Tag Manager container (Google) | GTM-MD55J7V | view source |
Third-party hosts
Hosts outside sanga-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 |
|---|---|---|
| ajax.googleapis.com | script | view source |
| cdn.jsdelivr.net | script stylesheet | view source |
| connect.facebook.net | script | view source |
| fonts.googleapis.com | connect | view source |
| miibo.jp | connect | view source |
| platform.twitter.com | script | view source |
| www.google.com | iframe | view source |
| www.googletagmanager.com | iframe | view source |
| www.jleague.jp | iframe | view source |
| www.line-website.com | script | view source |
| www.w3.org | connect | 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, 437.8 KB; 6 libraries, 2 identifiers, 12 third-party hosts
6 libraries added
- gtm
- @vitest/utils 5.0.2
- jquery 1.11.1
- kenwheeler/slick 1.8.1
- facebook-sdk
- twitter-widgets
2 identifiers added
- GTM-MD55J7V Google Tag Manager container
- eRDw5LG-1L7Q1EYgh_QOg_aZDgjT35putdatkrBhzck Google site verification
13 third-party hosts added
16 files added
- https://sanga-fc.jp/ html
- https://sanga-fc.jp/club/shop html
- https://www.sanga-fc.jp/news/detail/17176 html
- https://sanga-fc.jp/sponsor html
- https://www.sanga-fc.jp/ticket/english_ticket_page html
- https://sanga-fc.jp/assets/js/common.js js
- https://sanga-fc.jp/assets/js/top.js js
- https://sanga-fc.jp/assets/js/chatbot.js js
- https://sanga-fc.jp/assets/js/shop.js js
- https://www.sanga-fc.jp/assets/js/common.js js
- https://www.sanga-fc.jp/assets/js/news.js js
- https://www.sanga-fc.jp/assets/js/top.js js
- and 4 more
Questions about sanga-fc.jp
- How does PageSourceSearch know what sanga-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 sanga-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 sanga-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 sanga-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.