The Open-Source Smart Home Telemetry Matrix & IP Directory

This is the reference directory: a definitive, open-source catalog indexing the explicit outbound telemetry domains, hardcoded IP subnets, and tracking ports utilized by major consumer IoT hardware. Use it to configure your local firewalls, or let EdgeDefenseAI handle it automatically via packet inspection. For the step-by-step method of applying these blocks, see the companion guide on stopping IoT devices uploading data.

How to Use This Matrix for Home Network Isolation

Consumer IoT manufacturers frequently update device firmware to include fallback IP addresses that bypass local DNS servers (such as Pi-hole or AdGuard Home). When a device detects a blocked DNS resolution, it switches to direct IP socket connections over hardcoded destination subnets. Network administrators and home security enthusiasts can utilize the directory parameters below in three primary ways:

• Static Router Firewall Rules (ACLs): Copy the destination CIDR blocks into outbound drop rules on pfSense, OPNsense, UniFi, or OpenWrt firewalls.
• Automated Edge Enforcement: EdgeDefenseAI automatically ingests this matrix as an active baseline signature database, applying Layer 4 packet dropping dynamically when matching telemetry bursts are observed on local interfaces.
• Network Policy Tiers: Apply Hard Drop (complete TCP/UDP reset), Quarantine (containment to local LAN broadcast only), or VLAN Isolation (segregation onto a isolated non-routed network segment) based on the device's privacy threat rating.

Mapping Device Beacons to Sandboxing Profiles

Every consumer IoT brand exhibits unique behavioral beaconing signatures when attempting to transmit analytical data back to corporate ingest nodes. For example, Amazon Ring devices rely heavily on encrypted MQTT heartbeats over TCP port 8883 paired with periodic HTTPS telemetry pushes to AWS CIDR blocks (52.21.14.0/24). When matched, EdgeDefenseAI applies a Hard Drop profile, immediately dropping port 8883/80 egress while leaving local RTSP video streaming functional for Home Assistant.

Conversely, Samsung and LG Smart TVs execute persistent Automatic Content Recognition (ACR) queries against ad-serving domain clusters (such as samsungqbe.com and lgtvsdp.com). These beacons are assigned a Quarantine profile, blocking outbound tracking calls without disrupting CDN video delivery from Netflix, Hulu, or Prime Video. Tuya smart plugs and Eufy HomeBases map to VLAN Isolation and Local Only profiles, severing cloud control channels while preserving local TCP port 6668 and RTSP LAN feeds natively.

Brand-Specific Isolation Guides

Each entry in the matrix above has a dedicated walkthrough covering the manual firewall rules and the automated EdgeDefenseAI policy for that hardware:

• Ring (Amazon) telemetry kill guide
• LG & Samsung smart TV telemetry blocking
• Tuya Smart Life sandboxing
• Eufy cloud bypass containment
• The full network isolation & signature directory

Frequently Asked Questions

How do I use the IoT telemetry kill list to block a device? Copy the destination CIDR blocks into outbound drop rules on your router firewall (pfSense, OPNsense, UniFi, or OpenWrt), or let EdgeDefenseAI ingest the matrix automatically and apply Layer 4 packet dropping when matching traffic is observed.

Why do different IoT brands need different isolation policies? Each brand beacons differently. Ring uses MQTT heartbeats over port 8883, Samsung and LG TVs run ACR queries against ad domains, and Tuya or Eufy devices use their own control channels, so the drop policy has to match the specific ports and destinations each one uses.