Tools
Five small things that help before and after a voice scam. Each runs entirely in your browser. Nothing is uploaded, nothing is saved, and closing the tab clears it.
None of these detects anything. The detector is at /check/ and it needs a file. These are preparation and response tools — a passphrase, a card on a wall, a policy, a checklist — which is where most of the protection actually comes from.
Family safe-word generator
Builds a memorable multi-word passphrase using your browser’s cryptographic random source, for a household to use as a callback challenge. Explains why it must never be sent by message or kept in a phone.
Audio file inspector
Reads an audio file in your browser and reports duration, sample rate, channel count and size, then says what those numbers imply for a detection attempt. The file never leaves your device. Not a detector.
Callback verification card
A printable one-page card of the callback rule. Type your own names and numbers into it before printing, then put it where the phone is answered.
Payment verification policy
A short policy a finance team can adapt and copy in one click, written so that verifying is the rule rather than an employee’s personal doubt about a senior voice.
Incident checklist
A tick-list for the first hour after a suspected voice fraud, in the order that matters, with a live count of what is done. Not legal or financial advice.
Help guides
Longer written guidance: whether you can tell an AI voice by ear, how to read a result, how to preserve a recording, and what to do if the voice taken was yours.
How these behave
Every tool on this page is plain client-side JavaScript. There are no network calls, no analytics inside the tools, no accounts and no browser storage — what you type stays in the page you typed it into and is gone when you leave. That is also the limitation: nothing is remembered for you, so print or write down anything you want to keep.
Reviewed