Find your address
Find network devices using your router and read-only local commands, identify unfamiliar entries, and distinguish cached records from connected equipment.
Published:
Sources checked
Checking…
To find network devices on a home connection, start with the router's connected-client view or its supported management app. It can show equipment associated with the network it manages, often including an address, connection type and device label. Then compare unfamiliar entries with the settings on equipment you own. A public IP website cannot enumerate your household from one browser request.
MyIP.dog shows public connection information and explains addresses; it does not scan your local network devices or access your router account. You will perform the checks below in your own network's management interface or operating system. For work, school or another managed network, use the administrator's inventory process rather than treating local visibility as permission to investigate everything connected.
Connect to the network you want to inspect. Use the provider's documented app or the router's normal local administration path. If you need to identify the gateway, follow find your router IP. Avoid assuming that every router uses one universal address. A mesh access point and the device that assigns addresses can also have different management roles.
Look for a page called Devices, Clients, Connected devices or an equivalent label. Read its scope before counting network devices. Some views list currently associated wireless clients, while others include wired clients, DHCP leases or equipment seen earlier. Select the appropriate network and connection status if the interface offers those controls.
For example, Google's Home and Nest instructions describe the Home app's Wi-Fi Devices view and note that it can include devices seen within the previous thirty days. That historical window matters: a row is not necessarily proof of a connection happening now. Other vendors have their own retention and status rules.
For an entry you need to investigate, privately note its current label, local address, link-layer identifier, connection type, status and last-seen time when available. A label such as “unknown” usually means the interface lacks a friendly name. It does not establish that the device is hostile. Build an explanation from several matching observations.
DHCP leases show assignments to network devices, not a complete live census. A sleeping device can retain a lease, while a manually configured device may not appear in that particular lease list. Wireless association lists answer another question. Keep the source of the network devices list with your notes so later comparisons do not mix unlike measurements.
An operating system maintains information about neighbors on attached networks. These caches help it deliver traffic; they are not authoritative inventories of every connected machine. Reading them is useful when comparing an address you already know. Do not interpret an empty cache as evidence that no other network devices exist.
In PowerShell, the following read-only command lists neighbor-cache entries:
MyIP.dogGet-NetNeighbor
You can restrict the view to one family with Get-NetNeighbor -AddressFamily IPv4 or Get-NetNeighbor -AddressFamily IPv6. Note the interface and state along with the address. Microsoft documents the returned information in Get-NetNeighbor. The command reports cached neighbors, not every network device reachable through a router.
For a familiar IPv4 view, Command Prompt also supports:
arp -a
Microsoft's ARP command documentation describes this display. Network devices communicating beyond your local link are normally reached through a gateway, so the gateway's cache entry does not expose a separate link-layer entry for every internet host. Do not count broadcast or multicast rows as individual household machines.
In Terminal, use these display commands for locally known network devices:
arp -an
ndp -an
The first displays IPv4 ARP entries numerically; the second displays existing IPv6 neighbor entries numerically. Consult man arp and man ndp on the Mac for the version's output fields. The examples omit add, delete and flush options. They inspect existing information without rewriting the cache or launching a sweep across the subnet.
Keep the interface name and entry state when comparing network devices. The same Mac can have Wi-Fi, Ethernet and virtual interfaces. Network devices visible through one attachment need not appear through another. Use the Mac address guide to identify which connection you are actually examining before drawing conclusions from an unfamiliar interface label.
The iproute2 display commands are:
ip neigh show
ip -6 neigh show
The ip-neighbour manual explains neighbor objects and states. A stale entry can simply lack recent reachability confirmation; an incomplete entry lacks a completed address resolution. Neither word, on its own, identifies a malicious machine. Compare network devices using the relevant interface and the actual symptom.
If the command is run inside a container or network namespace, its view can differ from the host's view. A virtual adapter may also have its own neighbors. The Linux guide provides interface and routing context. Reading the wrong namespace's cache can make expected network devices appear missing even when the physical network is functioning normally.
Start with network devices you can inspect directly: phones, computers, printers, televisions, speakers, consoles and smart-home hubs. Open the relevant device's network details and compare the address and wireless identifier used on that particular connection. Do not compare a phone's cellular information with a router entry from its Wi-Fi session.
Private or randomized Wi-Fi identifiers can make familiar network devices appear under unfamiliar entries. Apple explains this behavior in its private Wi-Fi address documentation. The identifier used for a particular wireless network can differ from a hardware label. Check the active network's setting before deciding that two identifiers must represent two different physical devices.
A manufacturer label is a clue rather than proof of ownership. A component vendor's name may differ from the product brand, and a locally administered identifier may not produce a useful manufacturer match. Likewise, a hostname can be user-chosen, missing or stale. Network devices should be identified through corroborating observations, not one attractive label.
If you still cannot match an entry in the list of network devices, compare one known device at a time while preserving the rest of the setup. For example, deliberately disconnect your own phone from that Wi-Fi network, refresh the router view and observe whether its status changes. Allow for the interface's update interval and historical rows. A controlled change is more useful than rebooting every device together.
Do not interrupt equipment whose purpose you do not understand, such as a managed gateway, alarm or another person's active workstation. Ask the responsible owner first. For shared households, a simple inventory of network devices and recognizable labels can prevent repeated confusion without collecting unrelated activity histories or inspecting private application traffic.
Guest isolation, separate wireless networks, VLANs, sleep states and different subnets can limit what one device sees. A phone on a guest network may have internet access while being unable to reach a printer on the main network. That is a policy boundary to understand, not automatically a fault to remove. Check which segment each device actually uses.
Caches are also selective. They reflect information needed or learned by that host, not every possible address in a range. Multiple IPv6 addresses can belong to one interface, while a single visible gateway can serve many downstream network devices. Dividing the number of rows by a guessed address count does not produce a reliable inventory.
If an inventory remains incomplete, compare the router or access-point views responsible for each segment and the device's own settings. A dedicated discovery tool can actively probe an authorized local range, but sleeping equipment and filtering can still limit results. This guide does not promise that any one scan will find all network devices, and MyIP.dog does not perform that scan from your browser.
Preserve the relevant status and time, check the router's current access settings, and consult its official support instructions. If you confirm unauthorized access to your own Wi-Fi, use the supported process to update credentials and reconnect authorized equipment. An unfamiliar name alone is insufficient evidence; corroborate the entry before making changes that disconnect everyone.
Does the public IP list everyone at home? No. Several devices can share a public exit while keeping separate local addresses. The public versus private guide explains why the homepage's observation is not a roster of network devices.
Can network devices appear several times? Yes. Different interfaces, address families, historical records and private identifiers can produce multiple entries. Keep the list type and timestamps with the values before treating each row as a separate physical object.
Does no response mean offline? Not conclusively. A particular discovery request can be filtered, ignored or sent from the wrong segment. To investigate network devices, combine the appropriate management view with local configuration and a test suited to the service you actually need.
What should I share with support? Describe the expected device, network segment, list or command used, entry state and symptom. Redact unrelated addresses and identifiers from public screenshots. A focused report about network devices gives support a reproducible question without publishing the whole household inventory.