Been building a free email deliverability toolkit around my day job. Can't tell if it's actually useful for others; want a gut check
I work in tech support for nearly 10-plus years; I've watched the same thing happen over and over. Someone sends a campaign, half of it lands in spam, and nobody can tell them why. The answer is always buried in DNS records or blacklists or email headers that normal people shouldn't have to decode.
So I started building a free tool to check DNS initially, but step by step after hearing feedback from my team members, it has grown into a full product now. Right now it does SPF/DKIM/DMARC checks, blacklist lookups, header analysis, spam scoring, and bulk list verification. No signup, no email required for the free tools.
One thing I cared about: when you check a list, I don't store the actual emails. They get hashed before they ever touch the database, so even I can't read them. Building a "privacy" tool that quietly harvests everyone's lists felt gross.
It's early. I do this around a full-time job, so it moves slowly, and the paid tier isn't even live yet. I'm not selling anything. I just genuinely can't tell if this is useful or if I'm the only person who cares about it.
Honest question: if you send any real volume of email, would you actually use something like this? Or do you already get all of this from your sending platform, and am I reinventing the wheel?
Because of the flow I have set in my current tool, i feel something is off, or the flow is wrong. I have checked with a few of my peers but got mixed feedback. A few said the flow is correct. a few said its not.
Here is the link [https://emailsheriff.com\](https://emailsheriff.com) . I'd rather hear the hard stuff now than after another six months.
Note: Its still in beta and there may be bugs as well, since this is my first product. Feel free share your opinions, please.