What token scanners can see
Automated checkers read a contract in seconds and give you a score. Understanding what produced that score is the difference between a useful tool and a false sense of safety.
Token scanners inspect a contract automatically and return a summary — usually a score, a colour, and a list of flags. They are genuinely useful. They are also the most over-trusted category of tool in this entire subject, because a green result feels like an answer and is not one.
What they can actually check
Everything a scanner reports comes from data that is on the chain and machine-readable. That gives a real but bounded list.
- Whether more tokens can be createdReading the mint authority or the equivalent function. A factual, reliable check.
- Whether your balance can be frozenSame kind of check, same reliability. Both are covered in checking a token contract.
- Whether selling appears to be blockedSome scanners simulate a buy and a sell to see whether the sell goes through. This catches the crude version of a honeypot, where the contract simply refuses transfers from anyone but the owner.
- How the supply is distributedCounting balances across holders. Arithmetic, and accurate as far as it goes.
- What state the liquidity is inWhether the pool tokens are held, burned or locked in a contract, and until when. Also readable, also factual.
A scanner reads the contract. That is its whole scope.
It is a fast, tireless reader of on-chain data. It is not an investigator, and it has no opinion on anything that is not written into the code.
What no scanner can detect
This is the part that matters, because these are the ways most people actually lose money.
Whoever holds the tokens deciding to sell. A contract can be flawless and the largest holder can exit into your buy. Nothing in the code prevents it and no scan predicts it.
Liquidity that is locked for a week. Scanners report that liquidity is locked. Whether the lock expires next month is a detail people skim past. A lock with an end date is a delay, not a guarantee.
The people. Anonymous teams, borrowed reputations, paid endorsements, a fabricated history. All of it lives outside the contract entirely.
A sophisticated honeypot. Simulation catches the obvious refusal. Contracts exist that allow small sells and block large ones, or that behave normally until a condition is met. The test transaction succeeds and tells you about the test transaction.
The token simply going to zero. The most common outcome by a wide margin, entirely legal, entirely unrelated to any contract flag.
A clean scan means one category of trap was not found
It does not mean the token is safe, that the people behind it are honest, or that the price will not be zero next week. Read it as "no obvious contract-level trap", which is exactly what it is.
How to use the score without being fooled by it
Use scanners in one direction. A bad result is a strong reason to stop — the flags they raise are factual, and a contract that can freeze your balance is going to be able to freeze your balance. A good result is not a reason to proceed. It moves you from "obviously dangerous" to "unknown", and unknown is where the ordinary risks live.
Two scanners on the same token will sometimes disagree, because each vendor decides for itself which findings deserve which weight. The underlying facts are the same; the score is an opinion about them. When they differ, read the individual flags and skip the number.
Nothing here makes a memecoin a sound idea
These tools help you avoid one specific kind of theft. They cannot make a purely speculative asset behave differently, and we do not suggest that anybody buy one — see why this site has no rankings.
Sources
Where the factual claims on this page come from. Each was read on the date shown.