Learn what address exposure means.
Bitcoin risk depends on whether a public key has been exposed on-chain, address reuse, and the actual evolution of cryptographic threats—not a single address label.
Review address typesDOMAIN OPS // PUBLIC SAFETY LAB
Public-chain safety research for Bitcoin quantum exposure, reported scams, and rekt intelligence. This is a screening aid, not financial or custody advice.
INTELLIGENCE POSTURE
LIVE — PUBLIC DATABTC exposure, ETH/SOL lookups, and the incident feed use free public data sources. Scam-report lookup requires an API key that is not configured.Bitcoin risk depends on whether a public key has been exposed on-chain, address reuse, and the actual evolution of cryptographic threats—not a single address label.
Review address typesUse this lane for a public Bitcoin address, public EVM address, or public contract only. It never requests account access.
Open check laneA live incident feed and ETH/SOL contract lookup help customers identify what needs independent verification.
Open scannerCONNECTOR MAP
Scam reports and address/domain screening
Exploit, loss, and protocol incident monitoring
Address-type and public-key exposure posture
Public-chain movement signals and watchlists
REKT / EXPLOIT INTELLIGENCE
Fetching recent exploit records from DeFiLlama.
Paste public address or contract only. Never paste seed phrases, private keys, or wallet backups.
Chainabuse-style scam/abuse reports require an API key that is not configured on this server. This lane instead shows real public on-chain data — address type, balance, and activity — for Bitcoin, Ethereum, and Solana addresses.
Paste a public wallet address or public contract. It does not request signatures, approvals, or connections.
This checks whether the address is a deployed contract/program and shows its real balance and activity. Automatic correlation with the incident feed above is not available — cross-reference protocol names manually.
BTC ADDRESS-TYPE EDUCATION
The public key is directly present in the locking script.
A public key revealed by spending remains observable when an address is reused.
The public key is generally revealed when the output is spent.
Taproot uses an x-only public key; treatment depends on the output and threat model.