See every detail about your network connection in one place. Public and private IP addresses, DNS servers with a privacy rating, gateway, subnet mask, and active interfaces.
Download Free on the App StoreNetwork Info and all 19 tools are free. No ads, no account required.
iOS buries most network details across multiple settings screens, and some details it doesn't show at all. PingKit's My Network screen puts everything on a single screen: your public and private IP addresses, DNS configuration with a resolver privacy rating, default gateway, subnet mask, ISP, and every active network interface on your device. It does not show signal strength, channel or band, because iOS gives those to no app, and it shows your WiFi network's name only if you turn on the optional Use the Wi-Fi name to tell networks apart switch in the History tab and allow location access, because iOS shares the name only with apps that have that permission.
See your private IPv4, IPv6, and public IP address together. Know exactly how your device identifies itself on your local network and on the internet.
See exactly which DNS resolvers your device is using right now, with a privacy rating showing whether that resolver logs your queries, plus whether that provider supports encrypted DNS. This is how you confirm that a custom setting like Cloudflare on 1.1.1.1 or Google on 8.8.8.8 is genuinely in use, and how you catch a VPN or a mobile profile that has quietly overridden the servers you chose.
View all active network interfaces, including Wi-Fi, cellular and VPN, each with its connection type, status, and IPv4 and IPv6 address. The gateway and subnet mask appear once, in the Local Network section.
When your internet isn't working, the first step is understanding what your device can see. Is it connected to WiFi? Does it have an IP address? Is the gateway reachable? Can it reach DNS? PingKit's Network Info answers all of these questions at a glance, so you can narrow down the problem before trying random fixes.
Switched to a faster DNS provider but pages still load slowly? Check Network Info to confirm your device is actually using the DNS servers you configured. Sometimes VPNs, mobile profiles, or DHCP settings override your choices. PingKit shows you exactly which DNS servers are active right now.
iOS doesn't let apps read which WiFi channel or frequency band you're connected to, that's a platform restriction, not a PingKit limitation, so check your router's admin page for that number. The same applies to signal strength, which iOS withholds from third-party apps entirely. What you can do instead is point Live Connection, on the Monitor tab, at your router and watch latency, jitter and packet loss room by room. If those degrade in one spot, that's a coverage problem worth fixing with router placement or a mesh extender, regardless of which channel is involved.
IT professionals and home network enthusiasts need to record IP assignments, gateway addresses, and DNS configurations. PingKit gives you all of this on one screen without having to dig through iOS Settings or run commands in a terminal. Useful for documenting configurations before making changes.
The local address is the field people glance past, and it usually answers the question on its own.
192.168.x.x, 10.x.x.x, or 172.16 to 172.31.[source] A normal private address from your router. Everything is working as intended.
169.254.x.x.[source] Your device asked for an address and nothing answered, so it made one up. DHCP has failed. The Wi-Fi is associated but the network is not giving you a lease, and nothing beyond your own device will work. Restart the router before anything else.
100.64.x.x through 100.127.x.x.[source] Carrier-grade NAT. Your ISP has put you behind a shared address rather than giving you one of your own. This is increasingly common, especially on mobile broadband, and it is the reason port forwarding silently does not work and a home server cannot be reached from outside no matter how correctly it is configured. You can confirm it by comparing this with the public address on the same screen: if they are in different worlds, you are behind carrier NAT, and the fix is to ask your ISP for a public address rather than to keep changing router settings.
The public and private addresses are the same. Unusual at home. It means your device is directly on the internet with no NAT between, which is normal for a server and worth thinking about on a phone.
No gateway listed. Your device has an address and no route off the local network. Local devices will answer and nothing else will.
The subnet mask beside it tells you how much of the network your device believes it can reach directly. If it disagrees with what your router hands other devices, some machines will be reachable and others will not, in a pattern that looks random until you compare the masks. The Subnet Calculator will expand any of this into a range.
Every DNS query you make tells whoever answers it which site you are about to visit. That resolver sees your entire browsing pattern by hostname, whether or not the traffic itself is encrypted, which makes the choice of resolver one of the more consequential privacy settings on a device and one almost nobody sets deliberately.
PingKit names the resolvers your device is currently using rather than leaving them as addresses, recognises the major public providers, and rates each on four levels from Excellent to Poor. The rating reflects the operator's stated policy on logging and retention, and beside it PingKit shows whether that provider supports encrypted DNS.
The default for most people is their ISP's resolver, handed out by the router over DHCP, chosen by nobody. That is the case worth knowing about: it is the resolver with the most commercial interest in the data and the least likely to have been picked on merit.
The other thing this screen is good for is catching a resolver you did not choose. A VPN will normally push its own. A configuration profile from an employer or a school can set one silently. A router firmware update can reset custom entries back to the ISP's. In each case the setting you carefully changed months ago is no longer in effect, and nothing tells you until you look.
Connected to Wi-Fi, nothing loads. Read the local address first. 169.254 means DHCP failed. A normal private address with no gateway means no route. A normal address and a gateway means addressing is fine and the problem is further out, so check the resolver next and then run a ping to the gateway.
Some sites work and others do not. Usually DNS. Check which resolver is actually in use here, then look the failing name up with DNS Lookup.
Your VPN might not be on. The public address and the ISP name are the check. If they still show your home ISP, the tunnel is not carrying your traffic whatever the VPN app claims. If the address changed but the resolver did not, you have a DNS leak.
Port forwarding will not work. Compare the public address here with the address your router shows on its own WAN interface. If they differ, there is another layer of NAT between you and the internet, and forwarding a port on your own router cannot help.
You need your router's address. The gateway field is it. That is the address to type into a browser to reach the admin page, and the address to point Live Connection at when you want to test the Wi-Fi hop alone.
What this screen cannot show is the Wi-Fi signal strength, channel and band: iOS gives none of these to any app. The network's name appears only if you turn on the optional Use the Wi-Fi name to tell networks apart switch in the History tab and allow location access; it stays on your iPhone, PingKit never reads your location, and even then iOS does not say whether a secured network uses WPA2 or WPA3. A Mac does more: the free PingKit Agent reads the signal and security type off the radio, and the network's name once you allow Location Services; the WiFi Analyzer page explains the split.
A phone is rarely on one network. Wi-Fi and cellular are usually both up, a VPN adds another, and iOS decides per connection which to use. The interface list shows every one that currently holds an address, which is what makes it possible to tell what your traffic is actually doing rather than what the status bar implies.
The common surprise is that Wi-Fi being connected does not mean Wi-Fi is being used. When a Wi-Fi network stops passing traffic but stays associated, iOS quietly moves data to cellular and leaves the Wi-Fi symbol showing. Everything works, your data allowance drains, and nothing announces it. Two interfaces with addresses and a public IP belonging to your mobile carrier is that situation, visible in one glance.
A VPN appears as its own interface. If you expect one and it is absent, the tunnel is not up regardless of what the VPN app says.
On IPv6. You will often see IPv6 addresses alongside IPv4, and several of them on one interface is normal rather than a fault: a device typically holds a link-local address that never leaves the segment, a routable one, and often a temporary privacy address that rotates specifically so your traffic is harder to correlate over time. Having IPv6 does not mean you are using it for a given connection; that depends on whether the destination has it too. It is worth knowing which addresses exist, because a service reachable over one protocol and not the other is a real and confusing failure mode, and the first step is knowing you have both.
Every IPv6 address, and both public addresses. The Network Interfaces tool in the Tools tab lists every IPv6 address of each interface with its prefix length and its kind, such as link-local or global. My Network shows your public IPv4 and public IPv6 address side by side, with "Not available" for a version your connection does not have, so you can see at a glance whether your provider gives you IPv6 at all.
PingKit doesn't just display raw network data. It shows you what matters in context. Your public IP is resolved with geo-location so you can verify your VPN is routing traffic through the expected country. Your DNS provider comes with a privacy rating, so you can see at a glance whether you're on a resolver that logs your queries. And with 18 other tools in the same app, you can immediately follow up Network Info with a ping test, DNS lookup, or speed test without switching apps.
Cert Monitor for 50 domains (5 on Guardian, 1 free), a signed ISO 27001 PDF export, and scheduled, branded reports. $9.99/mo on iPhone and iPad, $4.99/mo on Mac.
Learn about Guardian Plus →Yes, in the Local Network section of My Network, beside your local IP and subnet mask. PingKit reads the actual default route out of the system routing table rather than assuming the router is the .1 address, which matters on the many European networks where it is .254. It is the address to type into a browser to reach your router's admin page, and the first thing worth pinging when the internet is down but local devices still answer.
Open PingKit, go to Tools and open My Network. Your local IPv4 address sits in the Local Network section with the gateway and subnet mask, and your public address sits in the Internet section together with the ISP that owns it and the city it geolocates to. IPv6 addresses appear further down beside the IPv4 address of the same interface, so you can tell which connection each one belongs to. Your public IPv4 and public IPv6 addresses are shown side by side, with Not available for a version your connection does not have.
No, and no iPhone app can. iOS does not expose signal strength, channel or frequency band to third-party apps, so PingKit shows no signal reading on an iPhone; the most My Network can add is the Wi-Fi network's name, and only once you turn on the optional Use the Wi-Fi name to tell networks apart switch in the History tab. What you get instead is your addressing, gateway, subnet, DNS resolvers and ISP, plus Live Connection on the Monitor tab, which measures latency, jitter and packet loss on the link itself, the thing a signal bar is only a proxy for. Your router's admin page is where the channel number lives, and on a Mac it is different again: macOS does permit it, so the PingKit Agent reports signal and noise in dBm, the signal-to-noise ratio, the band and the channel.
My Network has a DNS section that reads the resolvers your device is configured with and lists up to three of them. Where it recognises the provider it names it, so Cloudflare, Google, Quad9, OpenDNS and AdGuard appear by name rather than as a bare address, alongside whether that provider supports encrypted DNS and a privacy rating. A private address there means your router is handing out its own resolver, which is the usual sign that a custom DNS setting is not reaching your device.
Your private IP address (like 192.168.x.x or 10.x.x.x) is assigned by your router and only works within your local network. Your public IP address is assigned by your ISP and is how the internet identifies your connection. Multiple devices on your home network share the same public IP. PingKit shows both so you can see your complete network identity.
Download PingKit free and check your network info instantly.
Download Free on the App StoreRequires iOS 17.0 or later.