Spamova flags disposable emails, domain typos, and suspicious infrastructure in one API call, about 150ms response time. Combines an actively maintained blocklist with machine learning to catch new disposable domains early, plus domain reputation checks. Returns both a true/false and a 0-100 risk score, so you decide how strict to be. Zero maintenance on your end, nothing to download or update. Free for 30 days, plans start at $9/month for 10k checks.
No reviews yetBe the first to leave a review for Spamova
Maker
📌
Hey everyone, Steven here.
I've been working online for about 18 years, mostly on the content and affiliate side of things. My main project gives away resources in exchange for an email signup, and dealing with fake or throwaway addresses has been a headache for years. I built an in-house tool to handle it a long time ago, just for myself.
A few years ago, my main project took a real hit from AI search eating a lot of my organic traffic, which left me with more free time than I wanted. An old friend asked why I'd never sold any of the tools I'd built over the years just for my own use, and I didn't have a good answer. So I decided to turn a few of them into standalone products. Spamova is the first one out the door.
I looked closely at the free disposable email blocklists that are already out there before building this, and a lot of them are a mess. Some haven't been updated in years, and some have entries that seem to have been added for reasons that have nothing to do with actually catching spam. For example, qq.com gets blocked on more than one popular list even though it's a mainstream email provider.
Spamova keeps its own actively maintained list, adds a layer of machine learning to catch new disposable infrastructure early, and gives you both a simple yes/no and a risk score so you can decide how strict to be.
Would love any feedback, especially if you throw an edge case at it that breaks things. Happy to answer questions about the detection approach or pricing.
Report
Plugged it into a signup form and it caught a typo'd gmail address instantly, way faster than the validation script I was running. The risk score feels like a nice touch for tweaking how aggressive you want to be.
Report
Maker
@esmanurutaxdjh Appreciate you testing it live, that's the kind of catch it's built for.
Report
Love that it returns both a boolean and a score, gives way more flexibility than most tools i've tried. One thing that would be clutch: let me submit a disposable domain i come across straight through the dashboard so it gets added to the blocklist faster instead of waiting for the next model update.
Report
Maker
@nimettavanatmo Really glad the score plus boolean combo is useful, that flexibility is exactly why I built it that way instead of a flat block or allow.
I actually went back and forth on user submitted domains early on. The issue I kept running into is that if anyone can submit a domain and have it added system wide, it turns into an easy way for someone to get a competitor's legitimate domain blacklisted for everyone, not just flagged for their own account. Even with review, a flood of bad faith submissions gets hard to filter fast enough to be useful.
What I might do instead is let submissions apply only to your own account first, so you get the faster blocking you're asking for without it affecting other users, and only promote it to the global list after it's been verified. Would that solve what you're running into, or were you thinking of something more immediate than that?
Plugged it into a signup form and it caught a typo'd gmail address instantly, way faster than the validation script I was running. The risk score feels like a nice touch for tweaking how aggressive you want to be.
@esmanurutaxdjh Appreciate you testing it live, that's the kind of catch it's built for.
Love that it returns both a boolean and a score, gives way more flexibility than most tools i've tried. One thing that would be clutch: let me submit a disposable domain i come across straight through the dashboard so it gets added to the blocklist faster instead of waiting for the next model update.
@nimettavanatmo Really glad the score plus boolean combo is useful, that flexibility is exactly why I built it that way instead of a flat block or allow.
I actually went back and forth on user submitted domains early on. The issue I kept running into is that if anyone can submit a domain and have it added system wide, it turns into an easy way for someone to get a competitor's legitimate domain blacklisted for everyone, not just flagged for their own account. Even with review, a flood of bad faith submissions gets hard to filter fast enough to be useful.
What I might do instead is let submissions apply only to your own account first, so you get the faster blocking you're asking for without it affecting other users, and only promote it to the global list after it's been verified. Would that solve what you're running into, or were you thinking of something more immediate than that?