Drippy

See where each app's traffic goes

An app that only needs to check for updates might also be talking to analytics, ad and crash-reporting servers. Here's how to see them, and block the ones you don't want.

Updated November 2026

Download for macOSPricing

This is Drippy, with made-up usage. Click around: the switches and rules work.

In Terminal

lsof lists open connections with the app and the remote address. nettop -m tcp adds byte counts per connection. Both show addresses rather than names, and only for connections open right now.

lsof -i -n -P | grep ESTABLISHED
nettop -m tcp

In Drippy

Each app's page has a Where it goes list: the domains the app talked to, how much it sent and received from each, and the company that runs each domain. It keeps the history, so you can see what an app connected to last week.

Turn on blocking and the names get more exact.

Block a domain

Each domain in the list has a switch. Block an analytics or ad domain and leave the rest of the app alone. The Firewall room's summary shows the top domains across all apps.

Questions

Why do I see domains I don't recognise?

Most apps use content delivery networks and cloud hosts, such as Akamai, Cloudflare or AWS. Drippy shows the company behind each domain to help sort them out.

Will blocking a domain break the app?

Sometimes. Block one domain at a time, and turn it back on from the app's page if something stops working.

Download Drippy

Download for macOS