Site profile
one-keeper.co.kr
Built with fancybox 3.0.1, recaptcha, selectize 0.12.6, vide 0.5.1, stackedboost-shopify-assets 0.2.0, jquery-ui-bundle.1.12.1 1.12.1. 5 pages and 12 stored files, last crawled 2026-10-02.
rank 277,651 6 libraries 0 identifiers 4 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 |
|---|---|---|
| fancybox | 3.0.1 | 2026-10-02 |
| recaptcha | 2026-10-02 | |
| selectize | 0.12.6 | 2026-10-02 |
| vide | 0.5.1 | 2026-10-02 |
| stackedboost-shopify-assets | 0.2.0 | 2026-10-02 |
| jquery-ui-bundle.1.12.1 | 1.12.1 | 2026-10-02 |
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 one-keeper.co.kr 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 |
|---|---|---|
| cdn.megadata.co.kr | script | view source |
| wcs.naver.net | script | view source |
| www.google.com | script | view source |
| www.mozilla.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, 12 files, 743.7 KB; 6 libraries, 0 identifiers, 4 third-party hosts
6 libraries added
- stackedboost-shopify-assets 0.2.0
- recaptcha
- selectize 0.12.6
- vide 0.5.1
- jquery-ui-bundle.1.12.1 1.12.1
- fancybox 3.0.1
4 third-party hosts added
12 files added
- https://one-keeper.co.kr/ html
- https://one-keeper.co.kr/index.aspx html
- https://one-keeper.co.kr/service/service.aspx html
- https://one-keeper.co.kr/service/useinfo.aspx html
- https://one-keeper.co.kr/customer/cs.aspx html
- https://one-keeper.co.kr/js/jquery.min.js js
- https://one-keeper.co.kr/js/global.js js
- https://one-keeper.co.kr/js/web.util.js js
- https://one-keeper.co.kr/WebResource.axd?d=yYQrR…&t=638901865900000000 js
- https://one-keeper.co.kr/ScriptResource.axd?d=1N…obLv1mo4iGqkQbFM4DY1&t=5c0e0825 js
- https://one-keeper.co.kr/ScriptResource.axd?d=Hk…6Vpf8Qdz7scUXZnqFuI0&t=5c0e0825 js
- https://www.google.com/recaptcha/api.js?onload=onloadCallback&render=explicit js
Questions about one-keeper.co.kr
- How does PageSourceSearch know what one-keeper.co.kr 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 one-keeper.co.kr 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 one-keeper.co.kr?
- 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 one-keeper.co.kr?
- 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.