This guide helps you figure out why a smart device (like a thermostat, camera, or speaker) is sending data you didn’t expect, and what to do about it. You’ll learn how to check network traffic, review device logs, and use free tools to see exactly what your device is communicating. You’ll need basic access to your router’s settings and a computer on the same network.
What You’ll Need
- Access to your router’s admin page (usually via a web browser at an IP like 192.168.1.1 or 10.0.0.1)
- A computer (Windows, Mac, or Linux) on the same Wi-Fi or Ethernet network as the smart device
- Admin rights on that computer to install and run network tools
- A free network analysis tool: Wireshark (for deep packet inspection) or a simpler one like Fing or GlassWire (for basic traffic monitoring)
- The smart device’s app and login credentials
- Optional: a second router or a mobile hotspot to isolate the device
Step-by-Step
- Identify the device’s IP address. Open your router’s admin page, find the list of connected devices (often under “DHCP Client List” or “Attached Devices”), and note the IP address and MAC address of the smart device you’re investigating. If you have many devices, look for the one that matches the device’s manufacturer (the MAC prefix can help).
- Set up a network monitoring tool. Install Wireshark on your computer. If you’re not comfortable with packet analysis, start with a simpler tool like GlassWire (Windows/Android) or Fing (iOS/Android) that shows per-device data usage and connections. For this guide, we’ll use Wireshark for the most detail.
- Capture traffic from the device. In Wireshark, select the network interface that connects to your network (usually Wi-Fi or Ethernet). Start a capture, then trigger the smart device: turn it on, use its app, or wait for its normal background activity. Let it run for 10-15 minutes to catch periodic “phone home” signals.
- Filter for the device’s traffic. In Wireshark, type a filter like
ip.addr == [device IP](replace with the actual IP) to see only packets to and from your device. You’ll see a list of connections—each row shows source, destination, protocol, and length. - Examine the destinations. Look at the “Destination” column. Note any IP addresses or domain names that appear repeatedly. Right-click a packet and choose “Copy > Copy as Printable Text” to see details. Use a service like IPinfo or whois to see which organization owns those IPs. If you see addresses in countries where the manufacturer doesn’t operate, or IPs that belong to advertising or tracking companies (like Google Analytics, Facebook, or Amazon), that’s unexpected.
- Check the protocol and payload. In Wireshark, click on a packet to see the protocol breakdown. Common protocols: DNS, HTTPS (encrypted), HTTP (unencrypted), MQTT (IoT messaging), or proprietary. If you see unencrypted HTTP traffic, you can read the actual data sent. For HTTPS, you can’t read the content easily, but you can still see the destination domain via the TLS handshake (look for “Client Hello” packets and the “Server Name Indication” field).
- Look for unusual patterns. Does the device send data at odd times (e.g., every few seconds)? Does it send data when you’re not using it? Does it send large amounts of data even when idle? These patterns suggest background telemetry or possible compromise.
- Cross-reference with the device’s privacy policy. Check the device’s privacy policy or the app’s settings. Many devices send usage statistics, crash reports, or firmware update checks. If the destinations match those, the data is probably expected. If not, you have a lead.
- Isolate the device. If you suspect malicious activity, disconnect the device from your main network. Put it on a separate guest network or a VLAN (if your router supports it). This prevents any compromised device from accessing your other devices.
- Update firmware and change credentials. Check for firmware updates in the device’s app. Change the device’s password and disable any features you don’t use, like remote access or voice assistants.
Common Mistakes
- Capturing the wrong interface. If you’re on Wi-Fi, you must capture on the Wi-Fi interface, not Ethernet. On Windows, you might need to install Npcap correctly.
- Filtering incorrectly. Using the wrong IP address (e.g., the router’s IP instead of the device’s) will show you all traffic, not just the device’s.
- Ignoring DNS lookups. The destination IP might be a CDN (like Cloudflare) that hosts many domains. Always check the DNS query to see the actual domain name being resolved.
- Assuming HTTPS is safe. Just because traffic is encrypted doesn’t mean it’s not sending your personal data. The destination domain can still be revealing.
- Forgetting to note the baseline. You need to know what “normal” looks like. Run a capture when you’re not using the device, then again when you are, to compare.
Tips
- Use a dedicated network monitoring tool like Pi-hole (a DNS-level blocker) to log all DNS requests from all devices. This gives you a simple list of domains each device queries, without needing to analyze packets.
- On your router, enable logging if available. Some routers can log outbound connections.
- For HTTPS traffic, you can use a proxy like mitmproxy to decrypt traffic, but you’ll need to install its certificate on the device—this is advanced and may break the device’s functionality.
- Take screenshots of your findings. If you need to contact the manufacturer or a security professional, evidence is crucial.
- Check the device’s app permissions. Sometimes the app itself sends data, not the device. The app might be sending your location or contacts.
Troubleshooting
- No traffic shows up in Wireshark. Make sure you started the capture before triggering the device. Also, check that the device is actually on the same network. If you’re using a mesh system, the device might be on a different access point but still on the same subnet—that should be fine.
- The device’s IP changes. Smart devices often use DHCP, so the IP can change. Set a static IP reservation in your router for the device’s MAC address to keep it constant during your investigation.
- Too much traffic to analyze. Use Wireshark’s “Statistics > Conversations” to see a summary of top talkers. Or use a filter like
dnsto see only DNS queries, which often reveal the domains the device is contacting. - Can’t identify the destination IP. Use the “nslookup” command on your computer to reverse-lookup the IP, or use an online IP geolocation service. If the IP is in a cloud provider’s range (like AWS or Azure), that’s normal for many IoT devices.
- The device stops working when you block traffic. That’s a sign the blocked destination is essential for the device’s core function. Try blocking only non-essential destinations (like analytics) and see if the device still works.
Frequently Asked Questions
Q: Is it normal for a smart device to send data to the manufacturer?
A: Yes, many devices send usage statistics, error reports, and firmware update checks. This is usually disclosed in the privacy policy. The data is typically minimal and used to improve the product.
Q: What if I see traffic to a country like China or Russia?
A: It could be normal if the manufacturer is based there, but it’s also a red flag. Check the manufacturer’s stated server locations. If you’re concerned, block that IP range on your router and see if the device still works.
Q: Can I decrypt HTTPS traffic from my smart device?
A: Yes, but it’s complex. You’d need to set up a proxy like mitmproxy, install its root certificate on the device, and configure the device to use the proxy. This may void warranties and could break the device’s security features.
Q: Should I return the device if it sends unexpected data?
A: Not necessarily. First, determine if the data is actually personal or just telemetry. If it’s sending your location or voice recordings without consent, that’s a serious privacy issue. Contact the manufacturer and consider returning it if you’re not satisfied.
Q: How can I block a smart device from accessing the internet altogether?
A: On your router, you can usually find MAC address filtering or parental controls. Add the device’s MAC address to a block list, or put it on a guest network with no internet access. This will stop all outbound traffic, but the device may lose remote access features.
Q: What’s the difference between a smart device sending data and being hacked?
A: Sending data is normal for IoT devices. Being hacked usually means the device is sending data to unknown servers, behaving erratically, or being used in a botnet. If you see traffic to random IPs on unusual ports (like 6667 for IRC), that’s a strong sign of compromise.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Tongue Escape Codes: What They Are0.20 movements/s
- Claude Code Workflow Habits Worth Trying
- HDMI 2.1 Explained: Why It Matters for Gaming
- Veeam Plugin for VMware Cloud Director: How It Works
- Best Path of Titans Server Hosting: Top Picks
- Oppo First Foldable: 120Hz Display & Snapdragon 888