Site profile
tea-culture.top
Built with dashjs 5.2.1, zooming 2.1.1, @genpact/genome.mfe.solidify-app 3.15.1, lucid-ui 8.16.0, @unbabel/ui 5.19.0, @antv/data-set 0.11.8, bkl-request-demo 1.0.8. 5 pages and 13 stored files, last crawled 2026-10-08.
rank 14,195,299 7 libraries 0 identifiers 10 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 |
|---|---|---|
| dashjs | 5.2.1 | 2026-10-08 |
| zooming | 2.1.1 | 2026-10-08 |
| @genpact/genome.mfe.solidify-app | 3.15.1 | 2026-10-08 |
| lucid-ui | 8.16.0 | 2026-10-08 |
| @unbabel/ui | 5.19.0 | 2026-10-08 |
| @antv/data-set | 0.11.8 | 2026-10-08 |
| bkl-request-demo | 1.0.8 | 2026-10-08 |
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 tea-culture.top 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 |
|---|---|---|
| beian.miit.gov.cn | connect | view source |
| c1.1024vip.cn | connect | view source |
| github.com | connect | view source |
| hm.baidu.com | connect | view source |
| shike-web.vercel.app | connect | view source |
| tools.1024vip.cn | connect | view source |
| weibo.com | connect | view source |
| www.npmjs.com | connect | view source |
| www.swiper.com.cn | 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, 13 files, 1.1 MB; 7 libraries, 0 identifiers, 10 third-party hosts
7 libraries added
- bkl-request-demo 1.0.8
- @unbabel/ui 5.19.0
- dashjs 5.2.1
- lucid-ui 8.16.0
- @antv/data-set 0.11.8
- @genpact/genome.mfe.solidify-app 3.15.1
- zooming 2.1.1
10 third-party hosts added
13 files added
- https://tea-culture.top/ html
- https://tea-culture.top/about/ html
- https://tea-culture.top/shike-catalog/ html
- https://tea-culture.top/shike-web-catalog/ html
- https://tea-culture.top/css/ html
- https://tea-culture.top/assets/js/app.fcf823aa.js js
- https://tea-culture.top/assets/js/3.66dc930b.js js
- https://tea-culture.top/assets/js/1.3cdd9294.js js
- https://tea-culture.top/assets/js/336.7394d8ec.js js
- https://tea-culture.top/assets/js/337.d472779b.js js
- https://tea-culture.top/assets/js/59.af8093e9.js js
- https://tea-culture.top/assets/js/58.ba000ea3.js js
- and 1 more
Questions about tea-culture.top
- How does PageSourceSearch know what tea-culture.top 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 tea-culture.top 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 tea-culture.top?
- 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 tea-culture.top?
- 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.