Site profile
digifoundation.io
Built with gtag, cloudflare-email-decode, sticky-kit 1.1.3, @vitest/utils 5.0.2, @teipublisher/pb-components 3.6.8, xgplayer-hls 3.0.0-next.1. 5 pages and 15 stored files, last crawled 2026-10-10.
6 libraries 14 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 |
|---|---|---|
| gtag | 2026-10-10 | |
| cloudflare-email-decode | 2026-10-10 | |
| sticky-kit | 1.1.3 | 2026-10-10 |
| @vitest/utils | 5.0.2 | 2026-10-10 |
| @teipublisher/pb-components | 3.6.8 | 2026-10-10 |
| xgplayer-hls | 3.0.0-next.1 | 2026-10-10 |
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.
Third-party hosts
Hosts outside digifoundation.io 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 |
|---|---|---|
| fonts.googleapis.com | stylesheet | view source |
| unpkg.byted-static.com | script stylesheet | view source |
| unpkg.com | script | view source |
| www.googletagmanager.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, 15 files, 406.6 KB; 6 libraries, 14 identifiers, 4 third-party hosts
6 libraries added
- gtag
- cloudflare-email-decode
- @vitest/utils 5.0.2
- @teipublisher/pb-components 3.6.8
- sticky-kit 1.1.3
- xgplayer-hls 3.0.0-next.1
14 identifiers added
- G-TM77WL0G13 Google Analytics 4 measurement id
- G-V8GXMSME5N Google Analytics 4 measurement id
- RkNQdWUiaq9RUBW-ceQMIyFxaB7EoYw2VnDr--C1zNA Google site verification
- AqOxR17jDuGMdOgJ84NZY02YhvkOoXPRUqZ-b7Tbih8 Google site verification
- u65Xh6_o0nNltfvM9TBVu2LLy0R2Pw4tHofUwbwKdZU Google site verification
- hoP96qirypbgNGyM7HspR9xeBOC2A3LpXrS1jg8U2Js Google site verification
- C5dk_BEKtzCLBGBMhBjahN80EzavuAa_4N8xmBhAMxQ Google site verification
- 16xhosQhsqPC4oODZYUSNr4gjxQZBopnBwvMc-9KRHg Google site verification
- cQVr60j8-hxZrLOJXChW8nuSF1g5wjQMJ31w1yXpXw4 Google site verification
- M0Jerj-t0Uk2QCjIA0qRMm9g70Q5n_BeM4E66rQCVXc Google site verification
- z-9VR5JA-V2rYeT8XxL-b0uOKdU14ZqsKmqoLIuco7A Google site verification
- QfmiMyXY0B7799uHwJpDnQ6O3o0C4dvfiecu2Jh-50M Google site verification
- and 2 more
5 third-party hosts added
15 files added
- https://www.digifoundation.io/ html
- https://www.digifoundation.io/bang-xep-hang/ html
- https://www.digifoundation.io/ket-qua-bong-da/ html
- https://www.digifoundation.io/lich-thi-dau/ html
- https://www.digifoundation.io/tin-tuc/ html
- https://www.digifoundation.io/cdn-cgi/scripts/5c…/email-decode.min.js js
- https://cdn.digifoundation.io/wp-content/themes/cakhiatv/assets/js/main.js js
- https://www.digifoundation.io/js/websocket-client.js js
- https://cdn.digifoundation.io/wp-content/plugins…smooth_scroll.min.js?ver=2.0.73 js
- https://cdn.digifoundation.io/wp-content/plugins…/js.cookie.min.js?ver=2.2.1 js
- https://cdn.digifoundation.io/wp-content/plugins…ery.sticky-kit.min.js?ver=1.9.2 js
- https://cdn.digifoundation.io/wp-content/plugins…?ver=2.0.73-1745927554 js
- and 3 more
Questions about digifoundation.io
- How does PageSourceSearch know what digifoundation.io 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 digifoundation.io 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 digifoundation.io?
- 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 digifoundation.io?
- 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.