trenchcoat
Free · no sign-up
Website report · 7 h ago

www.sahilfiles.fun

“Sahil Files — Every File Has a Story.”

Template-written 13 evidence items Code reader analysed 48 scripts
What this means for you

Sahil Files only talked to its own servers while we watched.E1

  • What loads is a page only: no calls to its own backend, no wallet code, no contract calls, no AI services and no live connections.E12
  • We saw no known analytics or advertising services load on the first visit.E1

Tech check

What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.

The page doesn't make tech claims we check for (AI, on-chain, wallets, trading, own chain, staking, live data, an app).

Calls its own backend none seen
Wallet code none seen
Contract calls in its code none seen
Talks to AI services none seen
Live connections none seen

What loads is a page only: no own backend calls, wallet code, contract calls, AI services or live connections.E12

What it is

  • The Internet Archive has never saved this site, so it is probably new.E13
  • The site describes itself as: “An independent archive of reporting, public records, onchain research, and documented events surrounding Sahil Arora.”E2
  • It's built with Next.js and React (common tools for building web apps).E7E8
  • In your browser it saves small bits of data in your browser.E9
  • It has sections such as /files, /timeline, /intelligence, /membership, /dashboard and /login.E10E11

Where your data goes

On a first visit the page only talked to its own servers (www.sahilfiles.fun).

How key features work

Saving data on your device

It saves data in your browser (localStorage), so some things persist between visits.E9E6

local_storagelocalStorage

Cookies and storage

Names only. We never store the values.

localStorageE6: fr-book-page

Pages and API calls

Pages it links to

//files/timeline/intelligence/membership/dashboard/login/volume/packages/billing/about/methodology/corrections/submit/journalists/legal/privacy/terms/contact/_next/image

Evidence

Every sentence above points to one of these. Code references show the file, line:column and the short identifier that matched, never the site's code itself.

E1
Page title: Sahil Files — Every File Has a Story.
page title · https://www.sahilfiles.fun/
E2
Page description: An independent archive of reporting, public records, onchain research, and documented events surrounding Sahil Arora.
page description · https://www.sahilfiles.fun/
E3
Site name: Sahil Files
page site_name · https://www.sahilfiles.fun/
E4
Main heading: OPEN THE FILES.
page h1 · https://www.sahilfiles.fun/
E5
56 request(s) to www.sahilfiles.fun
types: 30 fetch, 11 script, 7 font
GET https://www.sahilfiles.fun/ · fetch · 56 requests · network recording
E6
localStorage: 1 key(s) saved in your browser
localStorage keys: fr-book-page · values not stored
E7
Next.js detected by the code reader (next-runtime)
confidence: high
www.sahilfiles.fun/ · “next-runtime” · the code reader
E8
React detected by the code reader (react-runtime)
confidence: medium
www.sahilfiles.fun/_next/static/immutable/chunks/38ohuqpgall6t.js · “react-runtime” · the code reader
E9
Uses the browser ability: local_storage
saves small bits of data in your browser
www.sahilfiles.fun/_next/static/immutable/chunks/1nnpwjzryp-sd.js @ 1:51172 · “localStorage.setItem(” · pattern scan
E10
27 links to pages on the same site
page links · https://www.sahilfiles.fun/ · /, /files, /timeline, /intelligence, /membership, /dashboard, /login, /volume, /packages, /billing, /about, /methodology
E11
Code reader found the route /_next/image
www.sahilfiles.fun/_next/static/immutable/chunks/2-alk5pyztpb1.js @ 1:4759 · “/_next/image” · the code reader
E12
56 requests on load: no own backend calls, wallet code, contract calls, AI services or live connections
GET https://www.sahilfiles.fun/ · summary · 56 requests · network recording
E13
The Internet Archive has no saved copy of sahilfiles.fun
page web archive · https://web.archive.org/web/*/sahilfiles.fun

Limits

  • We only see what your browser sees: code and requests on a first visit, without logging in or accepting cookie banners. What the servers do with data is invisible from outside.
  • Site code is usually minified (compressed), so names are partly lost and some code may be only partly analysed.
  • Some trackers only load after you accept cookies or log in, so the real list can be longer.
  • We visited from a server in the United States. Sites load different trackers and cookie banners in different countries (visitors in the EU usually get a consent banner first).
  • This text was written from fixed templates because no AI writer was available. It uses exactly the same evidence.
  • The code reader hit its size budget on parts of 5 large bundle file(s); those parts weren't fully analysed.

Facts, not judgements: this page describes what the code and traffic show, not anyone's intent. Not financial advice. Case id 2xqiVth1.