How to Find Your IP Address on Your Laptop or Computer
Trying to figure out your IP address? Yeah, I’ve been there. Whether you’re troubleshooting a network glitch or just curious about what number your device is broadcasting, knowing where to look helps a lot. It’s really not that complicated, but honestly, the settings can be buried or look different depending on your setup, Windows version, or even what brand of PC you have. I remember spending a good chunk of time trying to find it on my older ASUS, only to realize the IP info was hidden in some Advanced menu deep in BIOS. So, I figured I’d share what finally worked for me—maybe it helps someone else too.
Understanding the Types of IP Addresses
First, a quick note: there are two main types of IP addresses you might care about:
- Private IP Address: That’s the IP your device gets assigned from your router within your home or local network. It’s the one that changes when you restart your device or the router, thanks to DHCP. You can find it using ipconfig in Command Prompt or through your Network & Internet Settings.
- Public IP Address: This is what the entire internet sees. Basically, your router’s faceout on the web. If you’re trying to get banned from a website or figure out what your ISP has assigned, it’s that one. The easiest way? Just Google “what is my IP” or visit a site like whatismyip.com.
Knowing the difference is useful, because the steps to find each aren’t exactly the same, and sometimes sites just auto-show your public IP. Heads up: if you’re using a VPN or proxy, the public IP you see online might be different than what your local network reports.
How to Find Your Private IP Address
Using Command Prompt on Windows
This was my go-to. To get your device’s local IP quickly, open Command Prompt. Here’s how:
-
Open Start or hit Windows + S: Just click the Windows icon or tap the Windows key + S to bring up the search bar.
-
Search for Command Prompt: Type
cmdin the search box. When “Command Prompt” shows up, just click it. If it doesn’t open right away, right-click and pick Run as administrator. Sometimes, you need admin rights, especially if you’re messing with advanced network settings or using certain commands likenetsh. -
Run
ipconfig: In the black window, typeipconfigand hit Enter. It spits out a lot of details, but what you’re after is the IPv4 Address. Looks something like192.168.x.xor10.x.x.x. That’s your local IP. -
A little caution: This address is dynamic, so it can change if your router resets or after a DHCP lease renewal. Not necessarily permanent, but it’s the easiest way to grab it.
Using Windows Network Settings
If digging through command line isn’t your thing, you can also get this info graphically:
- Open Settings: Hit Win + I or go through Start > Settings.
- Navigate to Network & Internet: Choose Ethernet if wired, or Wi-Fi if wireless.
- Select Your Connection: Click on your current network connection and look for a section titled Properties or Details.
- Find IPv4 address: It should be listed, something like
192.168.x.x. That’s your private IP.
Honestly, I found this method a lot less intimidating after I got used to it. Still, I sometimes prefer Command Prompt because it’s quicker once you know where to go.
How to Find Your Public IP Address
Using a Browser
For your public IP—basically the number your internet connection shows to the outside world—this is easiest:
-
Open your browser: Chrome, Firefox, Edge, doesn’t matter.
-
Type “what is my IP” into Google: Seriously, it’s that simple. Google will highlight your public IP right at the top. Like magic, but also, just using Google’s search result.
-
Check the highlighted box: Your IP should pop up, for example,
203.0.113.45. Easy as that. -
Optional—Use an IP lookup site: If you want more detail, sites like whatismyip.com or ipinfo.io can tell you your IP, your approximate location, ISP, and other stuff. Helpful if you’re troubleshooting or just curious.
Note on Dynamic IPs
If your ISP uses dynamic IPs—which most do—your public IP can change after you restart your modem/router or at random intervals. That threw me off initially, thinking I was doing something wrong. Nope, it’s normal. They often lease these IPs for a short period, so don’t be surprised if it shifts around.
Wrap-up & Tips
Honestly, once you get it down, it’s straightforward—just a couple little tools and steps. ipconfig in Command Prompt nailed my local IP in seconds, and a quick Google or IP lookup gives your public IP in less than a minute. The tricky part is sometimes the settings are hidden or look different depending on your device or Windows version. I’ve seen cases where certain network options were grayed out or disabled, especially on laptops with OEM restrictions or if a BIOS security feature like Secure Boot or TPM was enabled, which can also hide or change some options related to network security.
One thing to watch out for: Clearing your TPM (Trusted Platform Module) can be risky. It might turn off BitLocker encryption if you’re using it, so make sure you’ve backed up any recovery keys first. Also, with newer Intel-based systems, there might be a setting called Intel PTT (Platform Trust Technology), which sometimes is labeled differently—like AMD’s fTPM if you’re on AMD hardware. These settings can disable or enable certain security features, but they shouldn’t affect basic IP info.
And yeah, if you’re stuck because options are grayed out, sometimes a BIOS update from your OEM or motherboard maker can help. It’s worth checking if your BIOS is the latest. Otherwise, some features might be simply locked down by manufacturer policies.
Hope this helps — it took me way too long to figure out some of these things myself. Now I can whip out my local IP or public IP in minutes, and I won’t spend ages hunting for the info next time. Double-check: if you’re trying to find your private IP, use ipconfig or your network settings. For the public IP, Google or a dedicated site is fine. And be aware of security: changing those BIOS settings or clearing TPM should be done with caution, especially if you’re using BitLocker or other encryption.
Anyway, hope this saves someone else a weekend of fumbling around. Good luck troubleshooting!