Skip to content
SecurityNew techTop 13% of today's analysed ideas

Bulk breach-notification tool for security researchers

Build a mass-notification tool for security researchers and CERTs who discover large batches of compromised or vulnerable websites. It should ingest a list of domains/IPs, auto-resolve abuse contacts via WHOIS, security.txt, hosting-provider lookups and DNS records, generate templated disclosure emails, send them in bulk while respecting rate limits and deliverability rules, and track opens/responses/remediation status on a dashboard.

Original post

What to build

A CLI/web tool for security researchers that ingests a CSV of domains or IPs, auto-resolves abuse contacts via WHOIS, security.txt, hosting-provider lookups and DNS, then sends templated disclosure emails in rate-limited batches with a dashboard tracking opens, replies, and remediation status.

Researchers who find thousands of compromised sites at once have no fast way to notify owners beyond manual WHOIS lookups and one-off emails, turning disclosure into the actual bottleneck after the hard part (finding the bugs) is already done.

Demand

Independent security researchers and small CERT teams who regularly uncover mass compromises (malware campaigns, exposed CVEs, leaky configs) want this now because the 'finding' step has been automated by scanners for years while the 'telling' step is still manual.

  • Hacker NewsEngagement

    'We know 15k websites are infected. how do we tell them?' — 144 points, 125 comments on HN, indicating high engagement with the disclosure-at-scale problem.

  • Signal titleNews

    Signal framed as a direct, unresolved operational question from a researcher sitting on a list of 15k infected sites with no efficient notification path.

Stack

  • WHOIS API (e.g. WhoisXML API)
  • security.txt parser
  • Python + Django/FastAPI
  • Postmark or SendGrid for rate-limited transactional email
  • Postgres for contact/status tracking
  • Shodan/Censys API for hosting-provider identification

Solo + AI difficulty

The scraping/lookup pipeline (WHOIS, security.txt, hosting ASN/DNS resolution) is straightforward with existing APIs and an AI-assisted build; the hard parts are email deliverability (avoiding spam/phish flags at bulk volume) and keeping a reasonably current abuse-contact dataset. A usable MVP (CSV in, contact resolution, templated send, basic dashboard) is realistically 1-2 weeks solo; production-grade deliverability and contact-data freshness take much longer.

Entry threshold
No licences needed; core build is scraping/contact-resolution plus bulk email and a tracking dashboard, doable solo with AI in a few weeks, though deliverability (avoiding spam filters) and data sourcing (WHOIS privacy, abuse APIs) take iteration.
Window
12+ months

Where to find first users

  • r/netsec
  • Hacker News (Show HN)
  • DEFCON/BSides villages and CERT mailing lists
  • Direct outreach to independent bug-bounty researchers on Twitter/X security community

Competitors

Counter-signals & risks

  • Abuse-contact data from WHOIS and security.txt is frequently outdated, privacy-redacted under GDPR, or simply unmonitored, which caps how many of the 15k site owners the tool can actually reach.

  • Bulk automated outreach emails risk being flagged as spam or phishing by receiving mail servers, which can damage the sender's (and the tool's) deliverability reputation over time.

  • No prior market validation exists for this exact tool category, and CERTs/researchers may continue relying on free manual channels or existing CERT infrastructure rather than paying for a dedicated product.

Original title: We know 15k websites are infected. how do we tell them?

  • Security#1

    LLM Prompt Privacy Monitor for Multi-Provider API Users

    Build a lightweight LLM prompt privacy auditor and routing compliance dashboard for developers using multi-provider AI gateways like OpenRouter. The tool monitors which providers actually retain or forward prompt data, flags zero-data-retention claims against known incidents, and alerts users when their chosen provider's data handling status changes. Target solo developers and small teams who route sensitive prompts through aggregator APIs and need a simple trust layer without reading every provider's privacy policy manually.

    Demand
    3/10
    measured
    Buildability
    7/10
    est.
    Competition
    7/10
    est.
    via Hacker News
    22 competitors
  • Security#1

    Plain-English Scam Link Checker for Everyday Users

    Build a web tool or browser extension where users paste a suspicious URL, SMS, email text, or message and instantly receive a plain-English verdict on whether it is a scam or phishing attempt. Target everyday consumers, elderly users, and small business employees who regularly encounter phishing links and smishing texts. Monetize via freemium API access, a Pro tier with bulk checks, or a white-label API sold to telecom and email security companies.

    Demand
    8/10
    est.
    Buildability
    9/10
    est.
    Competition
    5/10
    est.
    via Product Hunt
    44 competitors
  • Security#5

    Windows AI Evidence Scanner for Privacy and Compliance

    Build a lightweight Windows desktop tool (or SaaS with an agent) that scans a PC for AI-generated content artifacts, cached model outputs, prompt logs, and telemetry retention timelines, then presents a clear dashboard showing what evidence exists and when it auto-deletes. Target privacy-conscious users, HR/legal teams conducting e-discovery, and IT compliance officers who need to audit AI tool usage on corporate machines.

    Demand
    1/10
    measured
    Buildability
    7/10
    est.
    Competition
    8/10
    est.
    via Hacker News
    11 competitor
Bulk breach-notification tool for security researchers — Nichr