Site profile
xn--20190501-up1m808b.net
Built with jquery 3.4.1, clipboard 2.0.11, recaptcha, @vitest/utils 5.0.2, chizen 1.0.0. 5 pages and 22 stored files, last crawled 2026-10-07.
rank 12,925,120 5 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 |
|---|---|---|
| jquery | 3.4.1 | 2026-10-07 |
| clipboard | 2.0.11 | 2026-10-07 |
| recaptcha | 2026-10-07 | |
| @vitest/utils | 5.0.2 | 2026-10-07 |
| chizen | 1.0.0 | 2026-10-07 |
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 xn--20190501-up1m808b.net 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 |
| assets.pinterest.com | script | view source |
| thk.kanzae.net | connect | view source |
| www.google.com | script | 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, 22 files, 727 KB; 5 libraries, 0 identifiers, 4 third-party hosts
5 libraries added
- @vitest/utils 5.0.2
- recaptcha
- clipboard 2.0.11
- chizen 1.0.0
- jquery 3.4.1
4 third-party hosts added
22 files added
- https://xn--20190501-up1m808b.net/ html
- https://xn--20190501-up1m808b.net/product/ html
- https://xn--20190501-up1m808b.net/2025/04/04/post-2281/ html
- https://xn--20190501-up1m808b.net/magatama-2/ html
- https://xn--20190501-up1m808b.net/coin/ html
- https://xn--20190501-up1m808b.net/wp/wp-content/…/js/luxe.min.js?v=1713656587 js
- https://xn--20190501-up1m808b.net/wp/wp-content/…/luxech/luxech.js?v=1791384399 js
- https://xn--20190501-up1m808b.net/wp/wp-includes/js/dist/hooks.min.js js
- https://xn--20190501-up1m808b.net/wp/wp-includes/js/dist/i18n.min.js js
- https://xn--20190501-up1m808b.net/wp/wp-content/…/includes/swv/js/index.js js
- https://xn--20190501-up1m808b.net/wp/wp-content/…/includes/js/index.js js
- https://xn--20190501-up1m808b.net/wp/wp-content/…/assets/js/prism.js js
- and 10 more
Questions about xn--20190501-up1m808b.net
- How does PageSourceSearch know what xn--20190501-up1m808b.net 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 xn--20190501-up1m808b.net 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 xn--20190501-up1m808b.net?
- 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 xn--20190501-up1m808b.net?
- 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.