Don't trade this token.
The wallet that sent this token's launch transaction removed liquidity from this token's pool.
Scanned 1d ago. Scan again before you trade.
- FAILDeployer pulled liquidity
- WARNHoneypot
- WARNChecks with missing data
DexProof recorded NOC as CRITICAL on Robinhood Chain under formula v2.0.1, in verdict #1539 published 29 Oct 2026 (UTC). Of 28 checks, 14 passed, 3 warned, 1 failed and 10 could not be run.
Don't trade this token.
The wallet that sent this token's launch transaction removed liquidity from this token's pool.
Scanned 1d ago. Scan again before you trade.
Price
—
Liquidity
—
Volume 24h
—
FDV
—
Buys 24h
—
Age
—
The wallet that sent this token's launch transaction removed liquidity from this token's pool.
That wallet is , and it made 1 withdrawal on Uniswap V2, and that withdrawal closed the position completely.
We couldn't finish the sell test on the other exchanges we checked.
The token's main pool did not pass a sell test, so smaller pools that did pass can't show the token can be sold.
We couldn't read some checks on this scan, so the verdict is limited.
A failed read is not a clean result. This describes what we could see, not the token.
The token contract has privileged powers (limit change, amm route change, fee change, asset rescue, a switch that can block transfers or selling), but whoever controlled them gave up control or can no longer use them.
These are gaps in what we could see, not problems found in this token.
Applies to: Funder rug history, Deployer launch history, Funding lineage, Tax manipulation
So we can't check for past rugs, because many people launch through it. The transaction that created it was sent by , but a transaction sender can be the pad's own relayer rather than the launcher, so we don't attribute any history to that address.
So we can't check its past launches. The transaction that created it was sent by , but a transaction sender can be the pad's own relayer rather than the launcher, so we don't attribute any history to that address.
So we can't trace who funded it. The transaction that created it was sent by , but a transaction sender can be the pad's own relayer rather than the launcher, so we don't attribute any history to that address.
So we can't check whether it changed fees or limits.
We could not read this token's market data, so we did not measure its pool depth.
That is a gap in what we could see, not a finding about the token.
We don't have the market data needed to compare this token's value at full supply with its liquidity.
We don't have the volume and liquidity figures needed to check turnover.
We don't have the market data needed to check for wash trading.
We could not find when this token's pool was created.
A contract deployed this token, but that contract is not in the launchpad registry.
So we can't tell where it launched.
This token does not share its name and symbol with any real tokenized share.
The explorer has not tagged this contract as a scam.
This token is not on our list of confirmed rugs.
This token has no honeypot mark in our records.
This token has no pump-and-dump mark in our records.
100.0% of this pool's liquidity is burned, so it can never be pulled.
This pair's LP tokens sit at the dead address, which no one holds the keys to. This pool is on Uniswap V2 and holds 100.0% of the liquidity we could read. 3 other pools charge a fee too large to trade through, so nothing a holder owns is at risk there.
Top 10 holders hold 19% of the tokens in circulation.
Ownership was renounced.
The owner is the zero or dead address.
This contract's code is fixed.
We found no standard upgrade setup on it.
This contract's source is verified on the explorer.
No active paid boosts.
DexScreener has paid listing services on record for this token (a token profile), which is common for a launched token.
This token's code doesn't match any code template we know of.
This contract was 101 days old at this scan.
The source is verified, so anyone can read the code.
We could not match it to a known template.