How to Find My IP Address on Android (Public & Private)
This guide covers: How to Find My IP Address on Android (Public & Private).
Android phones can show a local Wi-Fi IP easily, but the public IP that websites see depends on whether you are on Wi-Fi, mobile data, a VPN, or another privacy path. That is why "find my IP" on Android is really two different tasks: reading the local address inside the phone's network settings and checking the public internet-facing address in the browser. This guide covers both on modern Android versions and explains the most common sources of confusion.
Public IP and private IP on Android are not the same thing
Your private/local IP is assigned by the Wi-Fi router inside the local network. Your public IP is the address visible to websites and outside services. On Wi-Fi, the public IP is usually shared with the rest of the devices on that network. On mobile data, it comes from the carrier infrastructure.
This matters because many Android users check the Wi-Fi details page and assume that number is what websites see. It is not. The local address is useful for router, LAN, or printer troubleshooting. The public address is useful for VPN checks, geolocation, and outside-network questions.
How to find your public IP on Android
The fastest method is to open the homepage IP checker in Chrome or another browser. That shows the visible IP, ISP, city estimate, and ASN immediately.
If you switch from Wi-Fi to mobile data and reload the page, the result often changes because the outside-facing network changed. That is normal and is one of the easiest ways to understand the difference between public and local scope on a phone.
How to find your local IP on Android
Stock Android / Pixel-style path
- Open Settings.
- Go to Network & internet or Internet.
- Open the connected Wi-Fi network details.
- Read the IP Address field, sometimes under an expanded Advanced section.
Samsung One UI path
- Open Settings > Connections > Wi-Fi.
- Tap the gear icon for the connected network.
- Read the IP address and gateway details on the network page.
Advanced terminal-style checks
If you use Termux or a similar shell environment:
ip addr show wlan0
ip routeThat can help advanced users see interface-level detail, though most Android users will be better served by the settings screens.
Wi-Fi, cellular, and VPN all change the answer differently
- Wi-Fi: the local IP is assigned by the router, while the public IP is shared at the network edge.
- Cellular: the carrier provides the visible network path and often uses shared gateways and CGNAT.
- VPN: the public IP should change to the VPN exit address, even while the local Wi-Fi IP may stay the same.
- Hotspot/tethering: your phone can act as the access device while still using the carrier or upstream Wi-Fi path underneath.
This is why Android can appear inconsistent if you switch networks while testing. The phone is not wrong; the path and therefore the visible identity changed.
Carrier gateways and CGNAT explain many odd Android results
Android users on mobile data often see more surprising location or provider results than Wi-Fi users. That is because carriers commonly use shared gateway infrastructure and CGNAT. The visible IP may represent a central mobile network exit rather than anything close to the phone's immediate radio location.
This is one reason mobile geolocation can feel coarse or inconsistent. The phone is mobile, the carrier path is shared, and the visible public identity is designed for scale rather than stable one-user-to-one-IP behavior.
Android randomized MAC address is a different privacy feature
Android uses randomized MAC addresses on many networks by default. That helps reduce device tracking across different Wi-Fi environments, but it does not serve the same purpose as changing the public IP. It affects the hardware identity presented to the local network, not necessarily the outside-facing internet identity.
This matters because users sometimes think enabling randomized MAC or "privacy" settings will change what websites see. It usually will not unless some other network path also changed.
Where this matters in practice
- VPN testing. You need the public IP and often DNS context too, not just the Wi-Fi-assigned local address.
- Printer and smart-home setup. Local IP and gateway matter when devices need to find each other on the LAN.
- Mobile-carrier troubleshooting. Public IP behavior can shift as carrier routing changes.
- Hotspot and tethering support. It helps to know whether the public path belongs to Wi-Fi upstream or cellular service.
- Router access. The gateway shown in Wi-Fi details is the address for router login, not the public internet identity.
Common mistakes and edge cases
- Reading the Wi-Fi page and assuming that is the public IP. That is usually the local LAN address.
- Forgetting whether Wi-Fi or cellular is active. The visible public path depends heavily on which network is in use.
- Ignoring VPN state. A VPN can change the public IP while leaving the local address unchanged.
- Confusing MAC privacy with IP changes. They affect different layers of network identity.
- Expecting one settings path across all Android skins. OEMs move labels and menus around, even when the underlying concept is the same.
Useful IP Trackers tools for Android checks
- IP Address Lookup is the best first public-IP check in the browser.
- IP Location Lookup explains where that address appears to be and which provider owns it.
- DNS Leak Test helps confirm Android VPN setups.
- VPN verification checklist gives a fuller path than checking the IP alone.
- Find My Router IP matters when your real goal is gateway or router access.
Hotspot users should care about both the phone and downstream devices
If the Android device is acting as a hotspot, it becomes both a client of the upstream network and a gateway for other devices. That makes IP troubleshooting more layered. One question is what public network the phone itself is using. Another is what private addresses the tethered devices receive behind it. Understanding both sides helps a lot when laptops or tablets behave differently behind a phone hotspot.
Android settings vary by manufacturer, but the network logic is the same
Pixel, Samsung, Xiaomi, Motorola, OnePlus, and other Android vendors all move settings around a bit. That can make one screenshot-heavy guide feel wrong on another device. But the underlying model stays stable: the Wi-Fi details page shows local network information, and a browser-based check shows the public internet-facing result.
Battery saver, Doze mode, and background data shape what IP checks return
Android aggressively manages background network activity to save battery. When the phone is in Doze mode (extended idle with screen off) or running with Battery Saver enabled, background apps can be suspended from network access entirely. That does not change the IP the phone has, but it does change which apps can actually see or report it.
This matters in practice when an IP-tracking app, a VPN client, or a connectivity widget seems to "freeze" on an old IP while a browser opened fresh shows the correct current one. The app was throttled, not the network. Bringing the app to the foreground or whitelisting it from battery optimization usually resolves the mismatch. If you are relying on a VPN's always-on toggle to keep the public IP consistent, also enable Block connections without VPN in the VPN settings so the system does not briefly fall back to the carrier path during sleep transitions.
Per-network MAC randomization controls on Android
Android lets you choose, per Wi-Fi network, whether the device uses a randomized MAC address or its real one. The control lives in the same Wi-Fi details page where you read the local IP. On Pixel, look for Privacy > Use device MAC or Use randomized MAC. On Samsung One UI, the field is usually labeled MAC address type.
Why does this matter for "find my IP"? Because some routers tie DHCP reservations to MAC addresses. If you turn randomization on for a home network you previously had reserved by MAC, the phone's local IP will change, and any port forwards or smart-home rules pointed at the old local address stop working. The fix is either to turn randomization off for that one trusted network or to recreate the DHCP reservation against the new randomized MAC.
Private DNS, DNS over HTTPS, and what they change for IP visibility
Android has had a Private DNS (DNS over TLS) setting since version 9. It lives in Settings > Network & internet > Private DNS. When enabled with a provider like Cloudflare (1dot1dot1dot1.cloudflare-dns.com) or Quad9, the phone sends all DNS queries encrypted through that provider regardless of which Wi-Fi network you are on.
This is worth knowing because Android users sometimes assume Private DNS hides their IP. It does not. The DNS queries are encrypted, so the local Wi-Fi network or the carrier cannot see which hostnames you are resolving, but the IP you connect to afterwards is still your public IP. Private DNS is a privacy improvement for DNS metadata, not an IP-hiding feature. For an IP-hiding feature, you want a VPN — see How to Hide My IP.
Dual SIM and eSIM make the answer more ambiguous
Modern Android phones increasingly run dual SIM, often one physical SIM and one eSIM, sometimes two eSIMs. That introduces a question previous phones did not have: which SIM is carrying mobile data right now? The public IP you see depends on the answer, because each carrier gives you a different CGNAT-shared public address out of its own infrastructure.
In Settings, look for SIM management or Mobile network and check which SIM is set as the Mobile Data SIM. If you switch the data SIM mid-session and reload the homepage IP checker, the public IP often changes, sometimes by city or even country. That is not the phone being wrong; it is the network path genuinely changing.
Forgetting and re-joining a Wi-Fi network to refresh the lease
Android does not expose a "release and renew DHCP" button the way Windows and macOS do. The closest equivalent is forgetting the network and reconnecting. Open the Wi-Fi network details, tap Forget, then reconnect with the password. The phone will perform a fresh DHCP handshake and receive a new lease from the router. This is the fastest way to fix a stuck local IP, a private DNS glitch, or a captive-portal page that will not load again.
Toggling airplane mode on and off also resets carrier and Wi-Fi state without losing saved network credentials, which is handy when the public IP looks wrong but the local IP looks fine. Try airplane mode first; reach for forget-and-rejoin only when that does not help.
Tethered devices see your hotspot address, not your public IP
When you turn on the Android hotspot, the laptop or tablet you tether gets a private IP from your phone, typically in the 192.168.43.x range on stock Android or 192.168.49.xon some Samsung devices. That tethered device's "local IP" is the address your Android handed out, not the address Android itself is using on the carrier network.
This trips up users debugging hotspot connectivity. The laptop's local IP is one private number, the phone's local IP from the carrier is a second private or CGNAT number, and the public IP visible to websites is a third address owned by the carrier. All three exist at the same time and all three are real. The public IP check in a browser is the only one that tells you what the open internet sees.
Frequently asked questions
How do I see my public IP on Android? Open the homepage checker in a browser.
How do I see my local IP on Android? Open the Wi-Fi network details in Settings and read the IP address field.
Why does my Android IP change on mobile data? Because the carrier path and shared public identity can change over time.
Does a VPN change my Android local IP? Usually no. It mainly changes the outside-facing public path.
Does randomized MAC address change my public IP? No. It affects local device identity, not the same thing as public IP exposure.
Where do I find the router IP on Android? In the Wi-Fi network details, often labeled Gateway or Router.
Related reading: Public vs Private IP, Find My Router IP, How to Hide My IP, and What Is My IP?.
