www.aotf.info
“American Oil Trust Fund”
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).
What it is
- The Internet Archive first saved this site on 2018-02-03 (3193 days ago).E29
- The site describes itself as: “Scale, movement, and continuity across the world's largest trade. The world runs on oil.”E2
- It's built with React and Next.js (common tools for building web apps).E14E15
- Notable building blocks in its code: Three.js (3D graphics) and Monaco code editor.E16E17
- In your browser it can copy text to your clipboard, stores data in your browser's built-in database, saves small bits of data in your browser, keeps a live two-way connection open to a server and 1 more.E19E20E21E22E23
Where your data goes
Not identifiedServices we don't have in our list yet. 9
| www.tradingview-widget.com | not identified | 235×E6 |
| s3.tradingview.com | not identified | 3×E5 |
| s3-symbol-logo.tradingview.com | not identified | 2×E8 |
| pushstream.tradingview.com | not identified | 1×E13 |
| scanner-backend.tradingview.com | not identified | 1×E7 |
| scanner.tradingview.com | not identified | 1×E9 |
| telemetry.tradingview.com | not identified | 1×E11 |
| widget-sheriff.tradingview-widget.com | not identified | 1×E10 |
| widgetdata.tradingview.com | not identified | 1×E12 |
How key features work
Sign-in and accounts
Sign-in and account features show up in its code or traffic (/api/v1/user/profile).E27
/api/v1/user/profileLive updates
It keeps live connections open (WebSockets, server-sent events, pushstream.tradingview.com and widgetdata.tradingview.com) so content updates without reloading.E22E23E13E12
websocketevent_sourcepushstream.tradingview.comwidgetdata.tradingview.comDrawing and editing in the browser
The page draws and edits graphics in your browser using Three.js (3D graphics), Monaco code editor and the canvas.E16E17E24
Three.js (3D graphics)Monaco code editorcanvasMeasuring what you do
Visits and clicks are measured with Google tag (gtag.js) (found in its traffic or its code).E18
Google tag (gtag.js)Pages and API calls
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.
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 65 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 GjywgyF0.