Site profile
uni-info.co.jp
Built with @marimo-team/frontend 0.25.0, react-router 7.18.0, universalviewer 4.4.4, mirador 4.2.4, @orbitellabs/chatbot-sdk 2.0.5, frankenstyle 0.3.8, @prefecthq/prefab-ui 0.20.2, @pydantic/ai-chat-ui 2.3.0. 1 page and 2 stored files, last crawled 2026-10-06.
rank 11,749,443 8 libraries 0 identifiers 13 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 |
|---|---|---|
| @marimo-team/frontend | 0.25.0 | 2026-10-06 |
| react-router | 7.18.0 | 2026-10-06 |
| universalviewer | 4.4.4 | 2026-10-06 |
| mirador | 4.2.4 | 2026-10-06 |
| @orbitellabs/chatbot-sdk | 2.0.5 | 2026-10-06 |
| frankenstyle | 0.3.8 | 2026-10-06 |
| @prefecthq/prefab-ui | 0.20.2 | 2026-10-06 |
| @pydantic/ai-chat-ui | 2.3.0 | 2026-10-06 |
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 uni-info.co.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 |
|---|---|---|
| cdnjs.cloudflare.com | stylesheet | view source |
| elaws.e-gov.go.jp | connect | view source |
| fonts.googleapis.com | stylesheet | view source |
| react.dev | connect | view source |
| uniinformation.sharepoint.com | connect | view source |
| www.chuukei.jp | connect | view source |
| www.google.com | connect | view source |
| www.meti.go.jp | connect | view source |
| www.mhlw.go.jp | connect | view source |
| www.ppc.go.jp | connect | view source |
| www.sys-d.co.jp | connect | view source |
| www.w3.org | connect | view source |
| www.wise-lab.co.jp | connect | view source |
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
| File | Kind | Size | Collected | Versions |
|---|---|---|---|---|
| https://www.uni-info.co.jp/ | html | 867 B | 2026-10-06 | 2026-10-06 |
| https://www.uni-info.co.jp/assets/index-CadsGLo5.js | js | 500.2 KB | 2026-10-06 | 2026-10-06 |
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
1 page, 2 files, 501.1 KB; 8 libraries, 0 identifiers, 13 third-party hosts
8 libraries added
- @prefecthq/prefab-ui 0.20.2
- universalviewer 4.4.4
- @pydantic/ai-chat-ui 2.3.0
- @marimo-team/frontend 0.25.0
- @orbitellabs/chatbot-sdk 2.0.5
- frankenstyle 0.3.8
- mirador 4.2.4
- react-router 7.18.0
13 third-party hosts added
2 files added
Questions about uni-info.co.jp
- How does PageSourceSearch know what uni-info.co.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 uni-info.co.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 uni-info.co.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 uni-info.co.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.