Docs · Features
3 min readA scan visits the link on your behalf: a throwaway browser on our server, a test wallet with gas only, and a decoder reading everything the page asks for.
What happens during a check
- Start a clean-room browser. A fresh browser with nothing saved, destroyed at the end.
- Make a test wallet. A brand new address, gas only. It never signs anything.
- Open the site and click through. Proxen clicks the main actions: connect, claim, mint, continue.
- Record and read. Every wallet request, signature, approval and outgoing request is captured and decoded.
- Report and wipe. You get a verdict with the evidence, then the browser and the test wallet are destroyed.
You watch it live: screenshots stream into the app while the check runs.
What a scan reads
SignalWhat is flagged
ApprovalsAllowances with no cap, the most common way wallets get emptied
PermitsOff-chain Permit and Permit2 signatures that hand spending rights to someone else
NFT approvalssetApprovalForAll on a whole collection
TransfersDirect sends of tokens or ETH to another address
SpenderContract or plain wallet, and verified source code on Sourcify or not
DomainRegistration date from RDAP, brand look-alikes and bait words like claim or reward
Data leaksThird-party servers receiving the test wallet address
Scores
ScoreLabelWhat to do
85 to 100ClearNothing harmful showed up
60 to 84CautionUsable with a burner holding only what you need
0 to 59AvoidKeep every wallet away
Limits
A clean score lowers the risk. It never removes it. Proxen clicks the main buttons, not every path through a site, and pages behind a captcha or a login may show less. For anything new, use a burner with only what you need.
To keep the service up for everyone, each visitor can run six checks every ten minutes.
