How to check a Solana token's risks
A practical sequence for checking mint identity, authorities, distribution and liquidity without treating a risk score as a safety guarantee.
RugSignal editorial notes · Published 16 October 2026 · Source-based, not investment advice.
Start with the mint address
A ticker or token name is not an identity. Copy the Solana mint address from the source you intend to investigate, then compare it with an explorer and the trading pair. Anyone can create a similarly named token. A verification badge helps with discovery but does not guarantee legitimacy or future value. Keep the address exactly as written: Solana addresses are case-sensitive.
Read permissions before price charts
Check whether mint and freeze authorities remain active, then inspect token extensions and transfer-fee settings. These are capabilities, not proof of intent. An active mint authority permits additional supply; revoked authority removes that particular permission. Other risks remain. RugSignal reports missing evidence as unknown, rather than treating an unavailable response as a passed check.
Compare ownership with executable liquidity
Inspect large holders, identifiable pool accounts and the deployer's share. A cluster of wallets may share funding without sharing an operator. Review the evidence behind a link instead of assuming every connected address is malicious. Liquidity and market capitalization describe different things: a quoted valuation does not tell you how much you could sell at the displayed price.
Treat the result as an observation
A saved report describes evidence at its timestamp. Authorities, holdings and liquidity can change after that observation. Recheck before relying on an old report. RugSignal's Low, Elevated, High and Severe categories are deterministic warnings, not calibrated fraud probabilities. No on-chain scanner can establish a team's future commitment, promise an exit price or detect every form of abandonment. The current accuracy gate remains unverified.
Sources and further reading
Official protocol documentation explains capabilities; it does not certify an individual token. RugSignal-specific statements describe our current implementation.