How does PageSourceSearch know what daisydiskapp.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 daisydiskapp.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 daisydiskapp.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 daisydiskapp.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

daisydiskapp.com

No known library was recognised in its stored source. 5 pages and 9 stored files, last crawled 2026-10-02.

rank 397,587 0 libraries 1 identifier 3 third-party hosts 1 crawl open the site

Technologies and libraries

No library file or bundled library code was recognised in the stored source. The site may use code of its own, load its libraries from a host the crawler does not fetch, or be too new in the index.

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
Facebook app id (Meta)	314198019882	view source

Third-party hosts

Hosts outside daisydiskapp.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
d1f8f9xcsvx3ha.cloudfront.net	connect	view source
daisydisk.onfastspring.com	connect	view source
www.youtube.com	connect	view source

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 9) }. 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://daisydiskapp.com/js/support/search.min.j…e7d5f0fe2ea7591ba5397cb91d4b1bf	js	2.8 KB	2026-10-02	current
https://daisydiskapp.com/js/home.min.js?hash=ff926f48a3648b2174f0bbea855a99b2	js	9.1 KB	2026-10-02	current
https://daisydiskapp.com/js/store/fastspring.min…d230cfae8b6bb232b7044605011c5bd	js	4.8 KB	2026-10-02	current
https://daisydiskapp.com/js/static-page.min.js?h…15a6a638fb9ad2958cf9c25c9a7d682	js	30.9 KB	2026-10-02	current
https://daisydiskapp.com/about	html	56.6 KB	2026-10-02	current
https://daisydiskapp.com/support/pricing	html	17 KB	2026-10-02	current
https://daisydiskapp.com/blog	html	23.9 KB	2026-10-02	current
https://daisydiskapp.com/support/search	html	19.4 KB	2026-10-02	current
https://daisydiskapp.com/	html	125.5 KB	2026-10-02	current

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-02 first crawl

5 pages, 9 files, 290 KB; 0 libraries, 1 identifier, 3 third-party hosts
1 identifier added
- 314198019882 Facebook app id
3 third-party hosts added
9 files added

Questions about daisydiskapp.com

How does PageSourceSearch know what daisydiskapp.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 daisydiskapp.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 daisydiskapp.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 daisydiskapp.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.