Site profile
hikari-g.co.jp
Built with jquery 2.1.4, gtag, bxslider 4.2.17, magnific-popup 1.2.0, jquery.cookie 1.4.1, onetrust, google-apis, jquery-visible 1.2.0, x-editable 1.5.1, @vitest/utils 5.0.2, stackedboost-shopify-assets 0.2.0, mobius1-selectr 2.4.13 and more. 5 pages and 16 stored files, last crawled 2026-10-04.
rank 10,194,812 14 libraries 1 identifier 18 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 | 2.1.4 | 2026-10-04 |
| gtag | 2026-10-04 | |
| bxslider | 4.2.17 | 2026-10-04 |
| magnific-popup | 1.2.0 | 2026-10-04 |
| jquery.cookie | 1.4.1 | 2026-10-04 |
| onetrust | 2026-10-04 | |
| google-apis | 2026-10-04 | |
| jquery-visible | 1.2.0 | 2026-10-04 |
| x-editable | 1.5.1 | 2026-10-04 |
| @vitest/utils | 5.0.2 | 2026-10-04 |
| stackedboost-shopify-assets | 0.2.0 | 2026-10-04 |
| mobius1-selectr | 2.4.13 | 2026-10-04 |
| @okta/okta-signin-widget | 7.49.1 | 2026-10-04 |
| jcarouselswipe | 0.3.7 | 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 |
|---|---|---|
| Universal Analytics property id (Google) | UA-108435963-1 | view source |
Third-party hosts
Hosts outside hikari-g.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 |
|---|---|---|
| apis.google.com | connect | view source |
| b.st-hatena.com | connect | view source |
| cdn.cookielaw.org | script | view source |
| job.mynavi.jp | connect | view source |
| js.ptengine.jp | script | view source |
| kocchake.com | connect | view source |
| line.naver.jp | connect | view source |
| maps.google.com | script | view source |
| media.line.naver.jp | connect | view source |
| twitter.com | connect | view source |
| widgets.getpocket.com | connect | view source |
| www.cn.nikon.com | connect | view source |
| www.facebook.com | connect | view source |
| www.google.com | connect | view source |
| www.googletagmanager.com | script | view source |
| www.nikon.co.jp | connect | view source |
| www.nikon.com | connect | view source |
| www.w3.org | connect | 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, 664.4 KB; 14 libraries, 1 identifier, 18 third-party hosts
14 libraries added
- stackedboost-shopify-assets 0.2.0
- gtag
- @vitest/utils 5.0.2
- mobius1-selectr 2.4.13
- jquery-visible 1.2.0
- bxslider 4.2.17
- x-editable 1.5.1
- jcarouselswipe 0.3.7
- jquery.cookie 1.4.1
- magnific-popup 1.2.0
- @okta/okta-signin-widget 7.49.1
- jquery 2.1.4
- and 2 more
1 identifier added
- UA-108435963-1 Universal Analytics property id
18 third-party hosts added
16 files added
- https://www.hikari-g.co.jp/ html
- https://www.hikari-g.co.jp/products/ html
- https://www.hikari-g.co.jp/news/ html
- https://www.hikari-g.co.jp/products/board/ html
- https://www.hikari-g.co.jp/products/reheat_p/ html
- https://www.hikari-g.co.jp/common/js/include.js js
- https://www.hikari-g.co.jp/common2/js/google-maps.js js
- https://www.hikari-g.co.jp/common/js/jquery.bxslider.min.js js
- https://www.hikari-g.co.jp/common2/js/resolution_detection.js js
- https://www.hikari-g.co.jp/common2/js/modernizr.custom.js js
- https://www.hikari-g.co.jp/common2/js/lib.min.js js
- https://www.hikari-g.co.jp/common2/js/script.min.js js
- and 4 more
Questions about hikari-g.co.jp
- How does PageSourceSearch know what hikari-g.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 hikari-g.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 hikari-g.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 hikari-g.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.