raksha

Raksha (Sanskrit रक्षा: protection, guarding, the keeping-safe of something entrusted). One question — how many known breaches does this password appear in — and three answers: a number, 0 for clean, and NULL for "could not check", which is never "breached". NEVER IMPLEMENT THE PRIMITIVE, DECLARE A HOST SURFACE: it computes no hash and opens no socket. Two verbs name the machine that does, a SHA-1 over bytes and a fetch of one five-character range, and the tool supplies neither; reference hosts on two different mechanisms ship as separate files so the same answer can be shown coming off two machines. FAIL-OPEN ALWAYS: a host that returns null, throws, times out, answers a short digest or answers rubbish yields null, because a checker that locked someone out of their own vessel while a third party was down would be doing the opposite of protection — and there is no parameter anywhere that turns that off. K-ANONYMITY: exactly five uppercase hex characters of the digest leave the machine, twenty bits of one hundred and sixty, one bucket in 1,048,576, and the remaining thirty-five are compared LOCALLY against the list the host brings back; the full hash and the plaintext reach the host never, and the proofs record every string the host was handed to check it rather than describe it. IT COMPARES AND IT DOES NOT ADVISE: no verb blocks a sign-up, scores a password or measures strength. A lookup is not a judgement — a password absent from every breach list can still be terrible. Nothing is stored, remembered or logged, and a log line about a password check is a log line about a password. No clock, no disk, zero imports.