Original Summary

Side project turned product. The problem: when you verify an email, catch-all domains (and inboxes behind Proofpoint/Mimecast) accept everything, so most tools return "unknown" — or worse, proxy-hop until they get a "valid" that isn't true. What skink does differently: - Tries to resolve catch-alls using out-of-band signals + SMTP behavior fingerprinting - Every result ships a calibrated confidence score and reasons[], not just a status - When it genuinely can't tell, it says so, and you're not charged for it - MCP server, so you can verify a list from Claude or Cursor directly Stack for the curious: Go verification engine, Node/TS gateway, Python scoring service, Redis Streams worker pool, Postgres, self-hosted on Hetzner (port 25 is the whole game for SMTP probing). One question: if a result says "72% likely deliverable, reason: accepts-all + mailbox signal found", would you send to it or not? Trying to figure out where people draw the line. Try yourself at www.skink.dev   submitted by   /u/ManyNeedleworker9409 [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/1 02:26:09