1. Check whether holders can sell
Honeypot behaviour or sell restrictions can trap buyers in a token. A successful simulation is useful evidence, but contract settings can still change later.
Check rug pull risk before you buy. Paste the token contract to run a free rug check: we flag common warning signs, including honeypots, mint functions, liquidity risk, high taxes and concentrated supply, with evidence and timestamps.
Start with the exact token you intend to investigate. A matching name or ticker is not enough to distinguish contracts with similar branding.
For more help identifying the input, read the free crypto token checker's contract address guidance.
A rug pull checker should help you investigate several independent signals. No single result proves that a token is safe, so read the findings together and scan again before making a decision.
Honeypot behaviour or sell restrictions can trap buyers in a token. A successful simulation is useful evidence, but contract settings can still change later.
A mint function may let an authorised address create more supply. Pause, blacklist or balance controls can also restrict transfers or affect selected holders.
Low or unlocked liquidity can make exits difficult and may let liquidity providers withdraw trading depth. Consider the amount, lock status and lock duration together.
High or changeable taxes can make a token expensive or impossible to exit. Treat an unusually high sell tax as a serious warning, even when buying remains possible.
A creator, owner or small group of wallets holding a large share of supply may be able to cause severe price pressure by selling. Wallet labels also need careful interpretation.
Contract data changes. Check which data source produced each finding, when it was collected and whether the scan was limited by missing security data.
For a broader contract review, use the free token risk scanner. You can also review our security and data-handling approach or inspect a sample token safety report before ordering the full evidence report.
Start with the evidence behind the result. The score summarises detected signals; it does not measure the probability that a token will rug or predict its price.
The scale runs from 0 to 100, with higher values indicating more risk. Read the individual findings to see what contributed to the result. A low score does not establish that every relevant risk has been checked.
An unavailable sell tax, liquidity figure or holder value is a gap in the evidence. If the scan reports that no security data is available, confirm the contract address and network, then retry. Do not interpret incomplete coverage as a clean result.
Use the last-checked timestamp to understand when the data was retrieved. Running a scan does not automatically alert you to later changes. Keep the findings and their limitations together when sharing a result.
To see how findings are presented in a written assessment, read the sample Token Safety Report.
A liquidity lock concerns the liquidity provider tokens for a particular trading pool. To understand a lock finding, check the pool it refers to, the amount covered and the expiry date. A small or short lock offers different evidence from one covering most of the pool.
Locked liquidity does not prevent a large holder from selling, and it does not remove mint, pause or tax controls from the token contract. Read those findings alongside the lock. If the scan cannot verify lock details, record them as unknown instead of assuming the pool is locked or unlocked.
Use the token contract address on the network you want to check. Compare the full address in the project documentation with the token entry on that network’s block explorer. A wallet address or liquidity-pool address identifies something different, even if it has the same format.
The score runs from 0 to 100, with higher values indicating more detected risk signals. It is not a percentage probability of a rug pull. Read the individual findings and data limitations alongside the score.
No. A limited result means the scanner could not retrieve enough security data for a full assessment. A missing tax, liquidity or holder value is unknown, not zero. Confirm the contract address and selected network before trying again.
A rug pull is when a token's creators drain liquidity or dump their supply, leaving buyers unable to sell or with worthless tokens. Common signals include unlocked liquidity, mint functions, honeypot behaviour and concentrated holdings.
We query live on-chain security data (via GoPlus Security) for the contract you enter: source verification, honeypot simulation, mint/pause functions, buy/sell taxes, liquidity locks and holder distribution. Each finding cites a concrete signal and is timestamped.
No. Check which pool is locked, how much liquidity is covered and when the lock ends. A lock does not prevent large holders from selling or remove other contract controls. If lock data is missing, treat its status as unknown.
Yes. A clean scan lowers risk but is never a guarantee. Liquidity can be pulled or taxes changed after launch. Always re-scan immediately before buying and never invest more than you can lose.
Order a Token Safety Report ($29): the owner, creator and holder breakdown with explorer links, liquidity and LP lock detail, a plain-English explanation of every signal and a follow-up rescan a day or two later. Or watch the token with Pro rescans and email alerts.