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

xomopay.fun

“explore · xomopay”

Template-written 17 evidence items Code reader analysed 3 scripts
What this means for you

xomopay only talked to its own servers while we watched.E1

  • We saw no known analytics or advertising services load on the first visit.E1
  • Its code can ask your wallet to sign transactions. Read every wallet pop-up before approving.E16

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 /api/platform, /api/coins, /api/feedE8E9E10E11
Wallet code signTransactionE16
Contract calls in its code none seen
Talks to AI services none seen
Live connections none seen

What it is

  • The Internet Archive has never saved this site, so it is probably new.E17
  • The site describes itself as: “launch a pump.fun coin whose creator fees go to a fomo username. proof on-chain.”E2
  • In your browser it can copy text to your clipboard and saves small bits of data in your browser.E6E7
  • It has sections such as /launch, /payouts, /burns, /docs and /coin.E15
  • While loading, it called 5 endpoints on its own servers, such as /api/platform, /api/coins, /api/feed and 2 more.E8E9E10E11

Where your data goes

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

Crypto and wallets

  • signTransaction: asks a wallet to sign transactions (often Solana wallets).E16

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.E16

signTransaction

Loading its content

Its content loads from its own API while you browse (/api/platform, /api/coins, /api/feed, /api/config and 1 more).E8E9E10E11E12

/api/platform/api/coins/api/feed/api/config/api/wall

Saving data on your device

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

local_storage

Pages and API calls

Pages it links to

//launch/payouts/burns/docs/coin

Endpoints

Called while loading (seen) or named in the code (code).

xomopay.fun/api/platformseenE8
xomopay.fun/api/coinsseenE9
xomopay.fun/api/feedseenE10
xomopay.fun/api/configseenE11
xomopay.fun/api/wallseenE12
/api/metacodeE13
/apicodeE14

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: explore · xomopay
page title · https://xomopay.fun/
E2
Page description: launch a pump.fun coin whose creator fees go to a fomo username. proof on-chain.
page description · https://xomopay.fun/
E3
Site name: xomopay
page site_name · https://xomopay.fun/
E4
Main heading: launch a coin. pay a trader.
page h1 · https://xomopay.fun/
E5
16 request(s) to xomopay.fun
types: 6 fetch, 3 script, 3 image
GET https://xomopay.fun/ · fetch · 16 requests · network recording
E6
Uses the browser ability: clipboard_write
can copy text to your clipboard
xomopay.fun/app.js @ 68:38 · “clipboard.writeText(” · pattern scan
E7
Uses the browser ability: local_storage
saves small bits of data in your browser
xomopay.fun/app.js @ 105:242 · “localStorage.setItem(” · pattern scan
E8
The page called /api/platform on xomopay.fun (GET)
GET https://xomopay.fun/api/platform · fetch · network recording
E9
The page called /api/coins on xomopay.fun (GET)
GET https://xomopay.fun/api/coins · fetch · network recording
E10
The page called /api/feed on xomopay.fun (GET)
GET https://xomopay.fun/api/feed · fetch · network recording
E11
The page called /api/config on xomopay.fun (GET)
GET https://xomopay.fun/api/config · fetch · network recording
E12
The page called /api/wall on xomopay.fun (GET)
GET https://xomopay.fun/api/wall · fetch · network recording
E13
The code names the endpoint /api/meta
xomopay.fun/ (page HTML) @ 62:91 · “/api/meta” · pattern scan
E14
The code names the endpoint /api
xomopay.fun/app.js @ 10:63 · “/api” · pattern scan
E15
6 links to pages on the same site
page links · https://xomopay.fun/ · /, /launch, /payouts, /burns, /docs, /coin
E16
Wallet request in code: signTransaction
asks a wallet to sign transactions (often Solana wallets)
xomopay.fun/app.js @ 116:129 · “signTransaction” · pattern scan
E17
The Internet Archive has no saved copy of xomopay.fun
page web archive · https://web.archive.org/web/*/xomopay.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.

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