Neobotnet

What it does

Neobotnet aggregates infrastructure data for companies that run public bug bounty programs. It collects subdomains, DNS records, web servers with HTTP status codes, crawled URLs, JavaScript files, and partial data on exposed secrets and paths. The data comes from HackerOne and Bugcrowd listings rather than fresh scans. A security researcher can log in and browse this pre-compiled intelligence across tracked targets.

Who it is for

Security researchers and bug bounty hunters who want a central place to study the attack surface of known bug bounty targets. Instead of running their own reconnaissance tools, they can see what infrastructure is already documented and indexed across multiple companies.

Pricing

The site does not show prices.

How it stands out

Neobotnet's main advantage is convenience. It consolidates reconnaissance data that researchers would normally have to gather themselves using separate tools like Shodan, Censys, or manual subdomain enumeration. The homepage shows 5 tracked companies, 12,000 web servers, and 500,000 URLs in the public demo, suggesting the dataset is non-trivial. By focusing only on authorized bug bounty targets from official platforms, it avoids legal friction that might arise from scanning non-consenting companies. The display of "vulnerability signals"—examples like unprotected redirect URIs, numeric user IDs, and exposed JWT tokens—shows the tool highlights common weakness patterns researchers care about.

What a founder should check

First, verify the moat. Bug bounty programs already list their scope on HackerOne and Bugcrowd; Neobotnet essentially repackages publicly available metadata. Competitors could build similar aggregators relatively quickly, and larger bug bounty platforms might offer this feature natively to retain users. Second, examine switching costs and stickiness. If researchers find the data useful but discover they still need to supplement it with their own scans and tools, adoption may plateau. The value prop depends on coverage breadth and freshness—if the tool only tracks 5 companies, many researchers will need other options anyway. Third, understand pricing pressure. Security professionals often have tight budgets and access to free tools; a paid product needs to demonstrate clear time savings or significantly better data quality than free alternatives.