Site profile
tdc-net.co.jp
Built with jquery 3.4.1, intersection-observer 0.12.2, lazysizes 5.3.2, smooth-scroll 16.1.3, jquery-match-height 0.7.2, webfont 1.6.26, @vitest/utils 5.0.2. 5 pages and 14 stored files, last crawled 2026-10-07.
rank 12,342,130 7 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 |
| intersection-observer | 0.12.2 | 2026-10-07 |
| lazysizes | 5.3.2 | 2026-10-07 |
| smooth-scroll | 16.1.3 | 2026-10-07 |
| jquery-match-height | 0.7.2 | 2026-10-07 |
| webfont | 1.6.26 | 2026-10-07 |
| @vitest/utils | 5.0.2 | 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 tdc-net.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 |
|---|---|---|
| ajax.googleapis.com | script connect | view source |
| api.docodoco.jp | script | view source |
| cdn.jsdelivr.net | stylesheet | view source |
| code.jquery.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, 14 files, 105.9 KB; 8 libraries, 0 identifiers, 4 third-party hosts
8 libraries added
- @vitest/utils 5.0.2
- jquery-match-height 0.7.2
- intersection-observer 0.12.2
- smooth-scroll 16.1.3
- lazysizes 5.3.2
- jquery 3.7.1
- jquery 3.4.1
- webfont 1.6.26
5 third-party hosts added
14 files added
- https://www.tdc-net.co.jp/ html
- https://www.tdc-net.co.jp/item/ html
- https://www.tdc-net.co.jp/news/%E4%BA%AC%E9%83%B…%8A%E7%9F%A5%E3%82%89%E3%81%9B/ html
- https://www.tdc-net.co.jp/sitemap/ html
- https://www.tdc-net.co.jp/privacypolicy/ html
- https://www.tdc-net.co.jp/js/fcc2.js js
- https://www.tdc-net.co.jp/js/jquery.matchHeight-min.js js
- https://www.tdc-net.co.jp/js/polyfill.js js
- https://www.tdc-net.co.jp/js/smooth-scroll.polyfills.min.js js
- https://www.tdc-net.co.jp/js/lazysizes.min.js js
- https://www.tdc-net.co.jp/js/common.js js
- https://code.jquery.com/jquery-3.7.1.min.js js
- and 2 more
Questions about tdc-net.co.jp
- How does PageSourceSearch know what tdc-net.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 tdc-net.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 tdc-net.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 tdc-net.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.