How the report is assembled.
The lookup organizes indexed public records. Its labels describe what the named source returned; they do not produce a safety score or certify a contract.
Current coverage
| Network | Chain ID | Explorer |
|---|---|---|
| Ethereum | 1 | Etherscan |
| BNB Smart Chain | 56 | BscScan |
| Polygon | 137 | PolygonScan |
| Arbitrum One | 42161 | Arbiscan |
| Base | 8453 | BaseScan |
The report currently covers ERC-20 approvals returned by GoPlus Security’s Token Approval Security API. It does not claim complete coverage of NFTs, operator permissions, native assets, every token implementation, every chain or records not yet indexed.
A report with zero records does not prove that a wallet is safe or has no other permissions.
Exactly what each label means
Identified
The source provides a project tag or contract name for the spender address. A name association is context, not a safety endorsement.
Not identified
The source provides neither a project tag nor a contract name. This alone does not mean the address is harmful.
Source code verified
The spender metadata reports open-source or verified source code. Published code can still contain errors or behave in ways a user does not expect.
Maximum allowance
The provider returns the allowance value as Unlimited. The page does not create a separate “very high” threshold. This label describes the recorded limit, not the trustworthiness of the spender.
Approval date
The latest approval timestamp supplied by the source, shown in UTC. The page does not classify older approvals as risky. A missing timestamp is shown as unavailable.
Request and response process
- Your browser submits a public EVM address and selected chain ID to the same-origin endpoint.
- The server validates the address and sends a read-only query to the listed provider.
- The server keeps only objective token, spender, allowance, timestamp and source-metadata fields.
- The browser renders the returned records and links to the relevant explorer for independent verification.
No wallet connection, signature, transaction preparation, transaction broadcast or recovery phrase is part of this process. Responses are not cached by the application, and provider delays or partial indexing can affect results.
Primary references
- GoPlus Token Approval Security API documentation
- Ethereum.org security and scam prevention
- Ethereum.org wallet guidance
- MetaMask guidance on token approvals
- Etherscan token approval explainer
Links are references, not partnership claims. Wallet Field Guide is not endorsed by the named organizations.
Methodology updated: 8 October 2026