Begin with the address and its scope
An address only makes sense with context. Ask whether it is public or local, IPv4 or IPv6, and which interface or network assigned it. A phone can legitimately hold several addresses while websites see a shared address from a router, carrier, office, or VPN. Start here if two IP values appear not to match.
Follow what happens before a site opens
DNS is usually the directory step between entering a name and connecting to a service. Learn how an app asks a recursive resolver, why the resolver you see may belong to an ISP, custom provider, browser, or VPN, and what a DNS leak test can actually observe. Start here when names fail but direct connections still work, or when checking an expected VPN DNS path.
Match a symptom to the right measurement
A slow response, broken voice call, and stalled download are not the same symptom. Ping describes round-trip delay, jitter describes changing delay, and packet loss counts missing replies. Learn how target, time, radio conditions, congestion, and filtering affect the numbers before deciding where the problem is.
Understand the first part of the route
The private address, gateway, subnet, and local DNS settings describe how a device reaches the nearby network. They help explain why one device cannot reach the router or why Wi-Fi differs from mobile data, but they do not describe the entire internet path. Start here when the issue appears before traffic leaves the home or office network.