One command to audit your own smart-home devices: who they phone home to, plaintext vs TLS, open ports, A-F grade and a local HTML/PDF report. CLI + MCP server, no cloud.
If you find this useful, you can support me by getting a SkinToScan pack, my other project. It's a one-time purchase that directly funds my open-source work.
iotaudit is for anyone who wants a straight answer about their own smart-home devices: cameras, plugs, feeders, bulbs, doorbells, and the rest. It watches what a device does on your network and gives each one an A-F grade, a one-line safety verdict, and a one-page HTML report. Everything runs locally: no account, no telemetry, no cloud.
I wrote it for the cheap gadgets that end up on a home Wi-Fi. The questions are usually the same: who does it talk to, is that traffic encrypted, are any surprising ports open, and did anything change since last time.
pipx install iotaudit
Capturing traffic needs root (sudo). An optional port scan needs nmap. PDF export and the MCP server are extras: pip install "iotaudit[pdf]" and pip install "iotaudit[mcp]". More install notes, including how to get iotaudit onto macOS sudo's PATH, are in the usage guide.
Country lookups use a bundled DB-IP Lite database; iotaudit geoip update installs a newer monthly file.
One command asks you to confirm this is your network, finds devices, runs the safe checks, captures passively, and writes the report:
sudo iotaudit auto
Files land in ~/iotaudit/YYYY-MM-DD/ as HTML and JSON (and a PDF if that extra is installed). If you already have a capture from Wireshark, your router, OpenWrt tcpdump, or PCAPdroid, analyse it without root:
iotaudit analyze capture.pcap
A step-by-step capture from an OpenWrt router (tcpdump over SSH, then iotaudit analyze) is in the OpenWrt guide.
Skip the typed confirmation with --i-own-this-network once you already know this is your network. To pull one device's traffic through this computer, use ARP or hotspot mode. See capture modes.
iotaudit profile export (see device profiles).iotaudit diff (and --compare) to see what changed since the last audit.--summary-json prints a compact grade summary on stdout, and --fail-under B exits 1 when the worst grade is worse than B.--redact when you want to share a report without local addresses.--ha-mqtt, with discovery so sensors appear without YAML) or as a JSON file (--ha-json). See the Home Assistant guide.Current release is 0.1.25. A sample report and a short demo are on the report page. A full vulnerability feed is still on the roadmap.
pip install "iotaudit[mcp]"
iotaudit-mcp
This starts a local MCP server (stdio) so a client on your machine can run the same audit tools. diff_results compares two saved JSON audits the same way iotaudit diff does. The server is listed on mcpservers.org and the official MCP Registry. Tool list and options: MCP server.
iotaudit only audits your own network and your own devices. It refuses non-private targets and requires --i-own-this-network or an interactive I OWN THIS NETWORK confirmation. ARP or NDP spoofing on a network you do not own may be illegal. All data stays local. There is no telemetry.
Findings are indicators based on observed traffic, not proof of wrongdoing by any vendor. IP geolocation by DB-IP. MIT licensed.
auto, PDF, diff, cron, export, credcheck, UPnP, and the web UI