{"id":39946,"date":"2026-07-31T10:08:42","date_gmt":"2026-07-31T10:08:42","guid":{"rendered":"https:\/\/nodemaven.com\/?p=39946"},"modified":"2026-07-31T11:27:40","modified_gmt":"2026-07-31T11:27:40","slug":"how-to-look-up-an-ip-address-on-a-computer","status":"publish","type":"post","link":"https:\/\/nodemaven.com\/ru\/blog\/how-to-look-up-an-ip-address-on-a-computer\/","title":{"rendered":"How to Look Up an IP Address on a Computer (Windows, Mac & Linux)"},"content":{"rendered":"\n

Here’s the fast answer. Your own IP on a computer: ipconfig<\/code> in Command Prompt on Windows, System Settings > Network<\/strong> on Mac, ip addr show<\/code> on Linux. That’s your local address. For your public IP, or the details behind any address that isn’t yours, you paste it into a lookup tool.<\/p>\n\n\n\n

Done. You can stop reading if that’s all you needed.<\/p>\n\n\n\n

Still here? Good, because there’s a part almost every guide gets wrong, and it’s the reason people spend twenty minutes looking in the wrong place.<\/p>\n\n\n\n

\u00abLook up an IP\u00bb isn’t one task. It’s two. And they live in completely different places on your machine. One is grabbing an address you already own. Your computer. Your printer. The laptop in the other room. That’s a settings-and-commands job.<\/p>\n\n\n\n

The other is investigation. You’ve got a public IP, maybe yours, maybe a stranger’s from a log, and you want to know what’s behind it. Location. Owner. Whether it’s flagged. No menu on your computer will tell you that.<\/p>\n\n\n\n

Figure out which one you’re doing. Everything else is easy after that.<\/strong><\/p>\n\n\n\n

If it’s the second one, there’s a shortcut worth knowing up front. NodeMaven’s free IP Lookup tool<\/a> takes any IPv4 or IPv6 address and returns its location, ISP, ASN, reverse DNS, proxy\/VPN\/Tor flags, and a threat score in one shot. No signup. Runs in the browser. Works the same whether you’re checking your own IP, a suspicious one from your logs, or the exit IP your proxy is quietly presenting to the world. <\/p>\n\n\n\n

Private vs public IP<\/h2>\n\n\n\n

Every device carries two addresses. This confuses more people than it should.<\/p>\n\n\n\n

The private IP<\/strong> is what your router hands your device inside your own network. 192.168.x.x<\/code> or 10.0.x.x<\/code>. Nobody outside your walls sees it. This is your printer’s IP, your local file share, the address you need to connect two machines at home.<\/p>\n\n\n\n

The public IP<\/strong> is different. It’s the single address your entire network shows the internet, assigned by your ISP. Every device in the house shares it. It’s what websites log. It’s what leaks your rough location. It’s the one you investigate when an address looks off.<\/p>\n\n\n\n

Finding your own IP on a computer<\/h2>\n\n\n\n

Windows<\/h3>\n\n\n\n

Command Prompt is fastest.<\/p>\n\n\n\n

    \n
  1. Hit the Windows key, type cmd<\/code>, press Enter.<\/li>\n\n\n\n
  2. Type ipconfig<\/code>, press Enter.<\/li>\n\n\n\n
  3. Find the IPv4 Address<\/strong> line. That’s your local IP, usually starting 192.168<\/code>.<\/li>\n<\/ol>\n\n\n\n

    Rather click than type? Settings > Network & Internet<\/strong>, pick your active connection, and the IPv4 address sits in the properties.<\/p>\n\n\n\n

    Worth knowing: ipconfig<\/code> shows your private<\/em> IP. Not the public one. For that, scroll down to the lookup section.<\/p>\n\n\n\n

    Mac<\/h3>\n\n\n\n
      \n
    1. Open System Settings<\/strong> (System Preferences on older macOS).<\/li>\n\n\n\n
    2. Click Network<\/strong>.<\/li>\n\n\n\n
    3. Select your active connection on the left. IP’s on the right.<\/li>\n<\/ol>\n\n\n\n

      Terminal person? ipconfig getifaddr en0<\/code> for Wi-Fi, en1<\/code> for Ethernet. Returns the private IP, no menus.<\/p>\n\n\n\n

      Linux<\/h3>\n\n\n\n

      Two commands, pick either:<\/p>\n\n\n\n