Free tools
Three small tools for the moments people search for help: working out what a hacked site’s symptoms point at, reading a suspicious .htaccess or PHP snippet without running it, and checking whether you could answer a cyber-insurance questionnaire with evidence. Nothing you enter leaves your browser.
The tools
Tool · Triage
Four questions about what the site is doing, where it runs and whether it has come back. The answer lists the exact files, tables and commands to check first, and the likely size of the cleanup.
Open the symptom checkerTool · Decoder
Paste a suspicious .htaccess, .user.ini, wp-config.php line, PHP or JavaScript snippet. It unwraps base64, gzinflate, rot13, hex and fromCharCode layers without executing anything, and explains what each pattern does.
Open the decoderTool · Readiness
Eight controls insurers ask about, answered by whether you could show evidence rather than whether you believe it is in place. The result is a score and the gaps to close before renewal.
Open the readiness checkWhat they are not
Each tool works only from what you tell it or paste into it. The symptom checker cannot see your server; the decoder reads one snippet, not the site it came from; the readiness check scores your answers, not your controls. They are built to point you at the right next step quickly, and to be honest about where that step needs someone with access.
If a tool turns up an active loader, a persistence layer, or a control you cannot evidence, the guides linked from each result explain how to confirm it safely — and where a cleanup or an audit is the right answer, the result says so plainly.