| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No data | Transfer simulation | 18 Nov 2026 |
| Buy tax | 0% | Contract | 18 Nov 2026 |
| Sell tax | 0% | Contract | 18 Nov 2026 |
| Admin mint | No data | Contract | 18 Nov 2026 |
| Transfers pausable | No data | Contract | 18 Nov 2026 |
| Address blacklist | No data | Contract | 18 Nov 2026 |
| Upgradeable proxy | No data | Contract | 18 Nov 2026 |
| Source verified | No | Block explorer | 18 Nov 2026 |
This automated check returned almost nothing usable, and that absence of data is itself the headline finding here. The contract's source code is not verified on the block explorer, which means the check could only look at raw bytecode rather than readable code — it's a bit like trying to assess a building by looking at a locked box instead of the blueprints. Because of this, the functions that normally reveal whether an owner can mint new tokens, pause transfers, blacklist specific addresses, or upgrade the contract to different logic entirely could not be read or scored. The sellability simulation also returned no data, meaning it was not possible to confirm whether a holder could actually sell this token back into the market. The 0% buy and sell tax figures came directly from the contract, but with source unverified and core functions unreadable, that figure should be treated as incomplete rather than reassuring — a 0% tax shown in one place doesn't rule out mechanisms elsewhere in the bytecode that affect what happens when you try to transfer or sell.
It's worth being clear about what this score of 0 out of 4 does and doesn't cover. This check only examines contract mechanics: the code-level permissions an owner could theoretically use against holders. It says nothing about who the team is, whether they're anonymous, how tokens are distributed among wallets, whether there's a lock-up on team or liquidity tokens, or whether the project has any legal structure or stated purpose. A contract can have clean-looking mechanics and still sit inside a project with no real backing, and conversely unverified source code doesn't by itself confirm bad intent — it simply means this automated process couldn't verify the behaviour either way.
Given the lack of verified source and the missing data across nearly every check, there are concrete steps worth taking before going further. Look up the contract address on a block explorer like Etherscan and check directly whether "Contract Source Code" shows as verified — if it's still unverified, that limitation will apply to any similar tool, not just this one. Check the holder distribution tab to see how concentrated ownership is among a handful of wallets. Look for whether liquidity is locked and for how long, and whether the contract owner address has renounced ownership or still holds admin control. Because no sellability data was returned, no transfer activity — test or otherwise — should be read as confirmation that selling works; unverified sell mechanics with no simulation data is a gap, not a green light.
Contracts change after they are checked. Tell us where to reach you and we will say when this one does. Free for three contracts, no account.
We checked 4 points out of 100.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.