How does PageSourceSearch know what tafuki.com 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 tafuki.com 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 tafuki.com?

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 tafuki.com?

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.

Site profile

tafuki.com

Built with jquery 1.9.1, gtm, twitter-widgets, @vitest/utils 5.0.2. 5 pages and 7 stored files, last crawled 2026-10-05.

rank 10,991,204 4 libraries 6 identifiers 11 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	1.9.1	2026-10-05
gtm		2026-10-05
twitter-widgets		2026-10-05
@vitest/utils	5.0.2	2026-10-05

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.

What	Value	Found in
AdSense publisher id (Google)	ca-pub-7919374939084234	view source
Bing site verification (Microsoft)	59DBF343B88EF3697DC7F68ED2091029	view source
Bing site verification (Microsoft)	73F837F3DB6A84DCC6553D1084388A01	view source
Google site verification (Google)	J1PVPxDDq4trrvoTXMXF4J9AHs2IwyYhh-UQ86JGFd0	view source
Google site verification (Google)	thbjnUMMGz9gCeKPM5Pii4fi1yWAsf7u9A6xe8Cb7bA	view source
Google Tag Manager container (Google)	GTM-P4CXTW	view source

Third-party hosts

Hosts outside tafuki.com 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
b.st-hatena.com	script	view source
cdn.blog.st-hatena.com	script stylesheet	view source
cdn7.www.st-hatena.com	script	view source
code.jquery.com	script	view source
cse.google.com	script	view source
hatenablog-parts.com	iframe	view source
kit.fontawesome.com	script	view source
pagead2.googlesyndication.com	script	view source
platform.twitter.com	script	view source
s.hatena.ne.jp	script	view source
usercss.blog.st-hatena.com	stylesheet	view source

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 7) }. Versions are the crawls at which the file was new or its content changed; each opens the file as it was then, rebuilt from the same stored chunks.

File	Kind	Size	Collected	Versions
https://code.jquery.com/jquery-1.9.1.min.js	js library	not fetched	2026-10-05	2026-10-05
https://platform.twitter.com/widgets.js	js library	not fetched	2026-10-05	2026-10-05
https://tafuki.com/archive/2026/09/21	html	25.9 KB	2026-10-05	2026-10-05
https://tafuki.com/archive/category/%E3%83%A9%E3%82%A4%E3%83%95	html	102.8 KB	2026-10-05	2026-10-05
https://tafuki.com/contact	html	26.6 KB	2026-10-05	2026-10-05
https://tafuki.com/about	html	25.2 KB	2026-10-05	2026-10-05
https://tafuki.com/	html	47.1 KB	2026-10-05	2026-10-05

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.

2026-10-05 first crawl

5 pages, 7 files, 227.6 KB; 4 libraries, 6 identifiers, 11 third-party hosts
4 libraries added
- gtm
- @vitest/utils 5.0.2
- jquery 1.9.1
- twitter-widgets
6 identifiers added
- GTM-P4CXTW Google Tag Manager container
- ca-pub-7919374939084234 AdSense publisher id
- J1PVPxDDq4trrvoTXMXF4J9AHs2IwyYhh-UQ86JGFd0 Google site verification
- thbjnUMMGz9gCeKPM5Pii4fi1yWAsf7u9A6xe8Cb7bA Google site verification
- 73F837F3DB6A84DCC6553D1084388A01 Bing site verification
- 59DBF343B88EF3697DC7F68ED2091029 Bing site verification
12 third-party hosts added
7 files added

Questions about tafuki.com

How does PageSourceSearch know what tafuki.com 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 tafuki.com 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 tafuki.com?: 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 tafuki.com?: 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.