I recently built a small browser‑only tool that analyzes how risky an email address looks based on structural patterns, domain heuristics, and behavior‑based scoring.
It’s called NOT GET HACKED, and the entire thing runs on static HTML/CSS/JS — no backend, no logging, no network requests.
In this post I’ll walk through the core ideas behind the scoring model and how the tool works under the hood.
Why analyze email addresses at all?
Even without sending a single request to a server, an email address contains a surprising amount of signal:
the local part (before the @)
the domain
the TLD
the character patterns
the entropy
the presence of known spammer patterns
I hope it will help a lot of people to NOT GET HACKED !
URL adress : https://notgethacked.netlify.app
Top comments (1)
I made this, because I had problems with spam letters in the past. I hope it will help for a lot of people!🤖