hellpad.app
“Hell”
Tech check
What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.
What it is
- The Internet Archive first saved this site on 2026-10-09 (17 days ago).E26
- The site describes itself as: “Hell, the anti pump.fun launchpad. Launch a coin for 0.15 SOL. Coins launch on pump.fun for now, and Hell moves to Meteora soon.”E2
- It's built with Next.js and React (common tools for building web apps).E7E8
- Notable building blocks in its code: Supabase client.E9
- In your browser it saves small bits of data in your browser.E11
- It has sections such as /coins, /create, /playbook, /token, /terms-of-service and /privacy-policy.E21E22
- While loading, it called 1 endpoint on its own servers, such as /api/auth/me.E13
Where your data goes
Backend & data servicesDatabases, search and APIs the app runs on. 1
| uihaesbegynaiidchynw.supabase.co | Supabase: app database and API | 2×E6 |
Crypto and wallets
How key features work
What it can ask your wallet to sign
Its code can ask your wallet for signTransaction. Each of these opens a wallet pop-up you must approve; read it before you click.E23
signTransactionConnecting your wallet
It connects to crypto wallets using Phantom, signTransaction and signMessage. Connecting shows the site your wallet address; it doesn't move funds by itself.E10
PhantomsignTransactionsignMessageSign-in and accounts
Sign-in and account features show up in its code or traffic (/api/auth/me and /api/auth).E13E14
/api/auth/me/api/authLoading its content
Its content loads from its own API while you browse (/api/auth/me).E13
/api/auth/meDrawing and editing in the browser
The page draws and edits graphics in your browser using the canvas.E12
canvasSaving data on your device
It saves data in your browser (localStorage), so some things persist between visits.E11
local_storagePages and API calls
Pages it links to
//coins/create/playbook/token/terms-of-service/privacy-policy/_next/imageEvidence
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).
- The tech check compares the site's own words with what its public page loads. Work done on servers, in private code or in separate apps isn't visible here, so 'nothing found' means not visible on the public page, not that it doesn't exist.
- This text was written from fixed templates because no AI writer was available. It uses exactly the same evidence.
- REA hit its size budget on parts of 11 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 uuckdvfD.