TorHound is a small Go service that fetches Tor Project exit relay data, caches the latest sighting time for each IPv4 exit address in BoltDB, and emits plain-text blocklists for servers and firewalls.
The project now wears a quirky 1970s service-desk coat: grainy photoshoot texture, bulky steel car energy, a shaggy dog hanging out the window, and still a technical instrument at the center.
Pass a minute window in the URL. TorHound returns every Tor exit address seen inside that window.
| Target | Endpoint |
|---|---|
| Apache 2.4 compat rules | /compat/minutes/15 |
| Nginx deny rules | /nginx/minutes/15 |
| iptables shell script | /iptables/minutes/15 |
| Palo Alto external dynamic list | /paloalto/minutes/15 |
| Windows firewall PowerShell | /powershell/minutes/15/firewall.ps1 |
Example:
https://www.torhound.com/compat/minutes/15
That returns IPs used by Tor exit relays in the last 15 minutes.
go test ./...
go build ./...
TORHOUND_ADDR=:3005 ./torhoundIf TORHOUND_ADDR is not set, TorHound listens on :3005.
The tracker refreshes from https://check.torproject.org/exit-addresses every five minutes. It validates IPv4 addresses, stores only normalized IP bytes, and generates deterministic sorted output for downstream configs.
Start the service somewhere your web servers or firewalls can reach:
go build -o torhound .
TORHOUND_ADDR=:3005 ./torhoundPull a format-specific blocklist by choosing a time window in minutes:
curl -fsS http://localhost:3005/nginx/minutes/1440
curl -fsS http://localhost:3005/iptables/minutes/60 -o tor-iptables.sh
curl -fsS http://localhost:3005/powershell/minutes/1440/firewall.ps1 -o firewall.ps1For Apache or Nginx, have a scheduled job write the generated config into an included file, then reload the service after a successful download:
*/5 * * * * curl -fsS http://localhost:3005/nginx/minutes/1440 -o /etc/nginx/conf.d/tor.conf && nginx -s reloadFor firewall targets, review the generated output first, then wire the same pull pattern into your change-management or scheduled task flow.
www.yourdomain.com {
tls youremail@example.com
reverse_proxy localhost:3005
}The generated files are intended to be pulled by your own cron, scheduler, firewall, or config-management job. Review the output format in a staging environment before wiring it into production reloads.