Asks once, remembers
The first time an app tries to connect, you see who made it, where it's going and on which port. Click Allow or Block, for the whole app or just one address, host or domain, and keep it forever or only until the app quits.
Most firewalls only watch what comes in. PacketHound sniffs out what goes out: the first time an app tries to connect to the internet, it asks you to Allow or Block, and remembers your answer.
PacketHound turns Windows Firewall into an "ask me first" firewall for outgoing connections, without drowning you in questions about Windows itself.
The first time an app tries to connect, you see who made it, where it's going and on which port. Click Allow or Block, for the whole app or just one address, host or domain, and keep it forever or only until the app quits.
Windows' own components are allowed automatically, so you're only asked about the apps you installed, not about hundreds of system services.
A program only counts as Windows if it lives in a Windows folder, is owned by the system and carries a valid Microsoft Windows signature. Copying malware into System32 doesn't get it a free pass.
Malware loves PowerShell, curl, certutil, mshta and rundll32 for downloading payloads. PacketHound still asks before those connect, even though they're part of Windows.
No kernel driver, nothing hidden. Every decision is an ordinary Windows Firewall rule you can see in wf.msc, and it keeps working even when PacketHound is closed.
Prompts appear on top without taking keyboard focus, so you can't answer one by accident while you're typing.
Flip any app between Allow and Block with one switch. Search, sort, see when each decision was made, and clear out rules for programs you've uninstalled.
The activity log shows every blocked attempt with its hostname, port and what happened next. Not sure yet? Decide later, and come back to it from the Rules tab.
Click any picture to see it full size.
No drivers, no background service of its own: PacketHound builds on the firewall that's already part of Windows.
PacketHound switches Windows Firewall's outgoing default to block, so a program without a rule can't reach the internet.
Windows logs each blocked attempt. PacketHound watches that log, checks whether the program is part of Windows, and allows it quietly if so.
For everything else you get a prompt showing the app, its publisher and where it's connecting. Your answer becomes a firewall rule, for the whole app or one destination, kept forever or until the app quits.
Yes. There's no trial, no account and no adverts. If you find it useful, you can buy me a coffee.
Yes. The full source code is on GitHub, under the GNU General Public License v3. You don't have to take our word for what PacketHound does: you (or someone you trust) can read exactly how it works, or build it yourself.
No. PacketHound doesn't collect anything and has no analytics. It looks up the names of the servers apps try to reach (a normal DNS lookup), so it can show you "example.com" instead of a bare IP address, and once a week it asks this website whether there's a newer version. That request contains nothing about you or your PC, and you can turn it off. See the privacy page.
That's Microsoft SmartScreen's warning for programs it hasn't seen many people download yet. Click More info, then Run anyway. You can check the file is exactly the one published here by comparing its SHA-256 checksum with the one on the download page.
Changing Windows Firewall settings and reading the Security event log both require them, so Windows asks you to confirm when you start PacketHound. If you let it start when you sign in, it starts without asking.
Your rules keep working: they're ordinary Windows Firewall rules. When you exit, PacketHound asks whether to keep blocking apps that don't have a rule yet. Either way, apps you blocked stay blocked.
Open PacketHound from the notification area, find the app on the Rules tab and flip its switch to Allow. Or delete the rule, and PacketHound will ask about the app again next time.
Yes. Right-click the tray icon and choose Pause protection, for 5 minutes, 15 minutes, an hour, or until you turn it back on. A timed pause turns protection back on by itself. While paused, apps without a rule can connect freely; your Block rules still apply.
Its first connection was blocked before you could answer, and some installers give up straight away. Click the notification PacketHound shows after you allow it (or right-click the tray icon › Pause protection › For 5 minutes) and run the installer again. Protection turns back on by itself. Next time, PacketHound recognises that installer and lets it through before it starts.
The app stays blocked and is listed on the Rules tab under Waiting for your decision, where you can decide any time. PacketHound also asks again after 10 minutes if the app is still running, or the next time it connects.
Yes. PacketHound uses Windows Firewall, which works alongside Microsoft Defender and most antivirus software. If a third-party security suite has replaced Windows Firewall with its own, PacketHound can't work, because there's no Windows Firewall to manage.
From Windows Settings › Apps. The uninstaller asks whether to delete PacketHound's firewall rules, then puts Windows Firewall's settings back the way they were before you installed it.
Open an issue on PacketHound's GitHub page (you'll need a free GitHub account). For a bug, say which version of PacketHound and Windows you're using and what happened. The log in C:\ProgramData\PacketHound often helps.
Free for Windows 10 and 11. Installs in a minute, uninstalls cleanly.