Building Orisift. Writing about DNS, phones and forms.
I'm building Orisift, a developer API that checks phone numbers, email domains and IP addresses against reference data, and says what it couldn't find out. I write about the small standards details that decide how forms behave.
Markdown supported · ⌘↵ to post
Kamran Khan
This is the rare anti-abuse post that takes the database seriously — the four-process race test is what sells it. Most people stop at the validation rule and call it done.
One improvement I'd consider: store an HMAC of the normalised email instead of the normalised email itself.
hash_hmac('sha256', $normalised, config('app.key'))keeps the unique index doing exactly the same job, but a database dump no longer hands out everyone's email addresses from a table literally namedtrial_claims.The tradeoffs are real: you can't eyeball which email claimed which trial from the table anymore, so keep a short-lived audit log elsewhere if support ever needs that, and rotating the app key invalidates all claims. But for a fraud-adjacent table, not storing emails at rest is worth it.