IP addresses, explained.

Your IP address is the unique number that identifies your connection on the internet, shown at the top of this page. It's how websites and servers know where to send the data you request. The address you see here is your public IP, assigned by your internet provider.

They're the same thing — “IP” is short for Internet Protocol, and an “IP address” is the numeric label it assigns to your connection. When people say “my IP,” they mean their public IP address, the one this page displays.

You already have — this page detects and displays your public IP automatically the moment it loads, with no setup. To see it again, just refresh. For your full connection details, expand the “Full connection details” panel below your IP.

A public IP address is the internet-facing address your whole network shares, assigned by your ISP. It's visible to any website you visit and is what this page shows. It's different from the private IP your router gives each device inside your home.

Your public IP reveals your approximate region (often just the city or your ISP's hub) and the name of your internet provider — not your name, street address, or identity. It's roughly comparable to knowing someone's neighborhood and phone company, not their front door.

If they're on different networks, they have different public IPs — your phone on mobile data uses your carrier's address, your laptop on Wi-Fi uses your home router's. On the same Wi-Fi they share one public IP but each has its own private internal IP.

You can look up the public details of any IP — its country, region, ISP, and network owner — using a lookup tool, including the reverse DNS and bulk audit tools on this site. You cannot get a person's name or exact home address from an IP; that information isn't public.

Your IPv4 address is the classic four-number format like 203.0.113.45, the original internet addressing scheme. This page shows it when your connection uses IPv4. It's still the most common type, though the internet is gradually adding IPv6 alongside it.

Your IPv6 address is the newer, longer format like 2001:0db8:85a3::8a2e:0370:7334, made of hexadecimal groups separated by colons. It exists because the world ran out of IPv4 addresses. This page shows your IPv6 when your network provides one.

IPv4 uses 32-bit addresses (about 4.3 billion total, now exhausted), written as four numbers. IPv6 uses 128-bit addresses (a practically unlimited supply), written as eight hex groups. IPv6 also simplifies routing and removes the need for some address-sharing workarounds.

If no IPv6 appears, your network or ISP likely isn't routing IPv6 to you yet — many connections are still IPv4-only, which is completely normal. It can also be disabled on your router or device. Your connection works fine either way.

An IPv4 address has four numbers separated by dots, each from 0 to 255 — for example 192.168.1.1. Each of those four parts is called an octet because it represents eight bits, for 32 bits total.

Not noticeably in most cases. IPv6 can route slightly more efficiently and avoids some address-sharing overhead, but raw speed is usually the same. The real benefit of IPv6 is the vastly larger address space, not faster downloads.

Having multiple IPv6 addresses is normal and expected. Devices typically hold a stable address plus a temporary “privacy” address that rotates to make tracking harder, along with a link-local address used only on your local network.

You can turn off IPv6 in your operating system's network adapter settings or your router's admin page, though it's rarely necessary. Disabling it can occasionally fix a misbehaving connection, but most networks run better with IPv6 left on.

A good VPN either routes your IPv6 through its servers or disables it to prevent leaks. A poorly configured one may let your real IPv6 slip through while masking only IPv4 — an “IPv6 leak.” Check both protocols on this page with your VPN on to be sure.

For your public IP, just open this page. For your private (local) IP, open Command Prompt and type “ipconfig,” then look for the IPv4 Address, or check Settings → Network & Internet → properties of your active connection.

Your public IP shows on this page. For your local IP on macOS, open System Settings → Network, select your active connection, and the IP address is listed there — or hold Option and click the Wi-Fi icon for quick details.

Your public IP appears on this page in Safari. For the device's local IP, go to Settings → Wi-Fi, tap the (i) next to your network, and read the IP Address field. That local address is private to your home network.

Open this page in your browser for the public IP. For the local IP, go to Settings → Network/Wi-Fi, tap your connected network or About Phone → Status, and find the IP address. Exact menu names vary slightly by manufacturer.

Your router's local IP — its “default gateway” — is usually 192.168.1.1 or 192.168.0.1. On Windows, run “ipconfig” and read the Default Gateway line; on Mac, check Network settings. Typing that address into a browser opens the router login.

In Windows Command Prompt, “ipconfig” shows your local IPv4 and gateway. Note that CMD shows your private/local address, not your public one — for the public IP your ISP assigns, use this page. On Mac or Linux, the equivalent is “ifconfig” or “ip addr.”

In a Linux terminal, run “ip addr” (or the older “ifconfig”) to see your local addresses. For your public IP, open this page, or from the terminal run “curl checkmyipnow.com/ip” for a plain-text answer — see our developer page for more endpoints.

Most devices show their local IP in network or connection settings: on a printer, print a network config page or check the display menu; on a smart TV, Xbox, PlayStation, or Roku, open Settings → Network → connection status. That IP is local to your home network.

On the Pi itself, run “hostname -I” or “ip addr” in the terminal. From another computer on the same network, you can scan for it or check your router's connected-devices list. That gives the Pi's local IP for SSH or hosting.

These are common private IP addresses, almost always your router's local address (the default gateway). Typing one into your browser opens your router's login page. They're not reachable from the public internet — millions of home networks use the same ones.

Your public IP is the single internet-facing address your whole network shares, assigned by your ISP and shown on this page. Private IPs (like 192.168.x.x) are assigned by your router to each device inside your home and aren't visible to the outside internet.

A local IP is the private address your router gives a device on your home network, such as 192.168.1.20. Devices use it to talk to each other and the router. It's reused on countless networks worldwide and never appears to outside websites.

Because they do different jobs. Your router uses one public IP to represent your whole home on the internet, then hands out private internal IPs to each device behind it. This is called NAT — it lets many devices share a single public address.

10.0.0.1 is private. The ranges 10.x.x.x, 172.16–31.x.x, and 192.168.x.x are reserved for private networks and never routed on the public internet. 10.0.0.1 is often a router's gateway address on networks that use the 10.x range.

Your default gateway is your router's local IP — the address your devices send traffic to in order to reach the internet, commonly 192.168.1.1. Find it with “ipconfig” on Windows or in your network settings. A blank gateway usually means a connection problem.

An address beginning 169.254 is an APIPA “self-assigned” address, which a device gives itself when it can't reach a DHCP server to get a real one. It usually signals a connection fault — a bad cable, a router issue, or DHCP not responding.

127.0.0.1 is the loopback address — it always means “this device itself.” Traffic sent to it never leaves your computer. Developers use it to test servers locally; it's not a real network address and is the same on every machine.

Two devices can share the same public IP — that's normal for everything behind one router. But two devices on the same local network can't share the same private IP without causing an “IP conflict” error that breaks connectivity for both until resolved.

A subnet mask (like 255.255.255.0) defines which part of an IP identifies the network versus the individual device. It tells your device which other addresses are on the same local network. For working with masks and ranges, see our CIDR and subnet tools.

No. IP geolocation points to your ISP's regional routing, usually your city or a nearby hub — not your street or home. It's an approximation, often miles off. Only your ISP, with a legal request, can connect an IP to a physical service address.

IP geolocation is generally accurate to the country, often to the city or metro area, and unreliable below that. It maps to where your provider routes the address, not your GPS position, so the city shown can be wrong by a long way — that's normal.

Not directly — knowing your IP alone doesn't let someone into your devices. Real risks are indirect: targeting your connection with a denial-of-service flood, or probing for unpatched, exposed services. Keeping devices updated and behind a router's firewall covers the everyday risks.

With just your IP, someone can estimate your region and ISP, attempt to flood your connection (a DoS attack), or include it in a server's logs. They cannot read your files, see your name, or access accounts from the IP by itself. It's low-stakes for normal users.

For most people, sharing your public IP is low-risk — it's visible to every site you visit anyway. The main downsides are exposure to denial-of-service attempts or being logged. If you want to avoid sharing it, a VPN replaces it with the VPN server's IP.

The common ways to mask your IP are a VPN (which substitutes the VPN server's address), the Tor browser, or a proxy. Free options exist but often log data or sell it, so choose carefully — see our guide to choosing a VPN for what to check.

No. Incognito mode only stops your browser from saving history and cookies locally — it does nothing to your IP, which websites still see normally. To actually change the IP sites see, you need a VPN, proxy, or Tor.

Browser fingerprinting identifies you by combining lots of small, individually-harmless details your browser exposes — things like your screen size, time zone, installed fonts, language, and how your device renders graphics — into a profile distinctive enough to recognise you again, even with cookies cleared or in private mode. It's harder to block than cookies because the signals are part of normal browsing. You can reduce it with a privacy-focused browser (Tor Browser, Brave) or anti-fingerprinting extensions, though no method is perfect. Your User-Agent is one of the inputs — our user-agent parser shows that piece — and our guide on canvas fingerprinting explains one of the more powerful techniques in detail.

An antidetect browser is a specialised browser that lets a user present a different, self-contained set of browser and device characteristics rather than their real ones — going further than ordinary anti-fingerprinting tools, which mostly just block or randomise signals. They're used legitimately by privacy researchers and by agencies that manage many separate client accounts, but they're also widely associated with running multiple accounts on platforms that don't allow it, so many sites treat them as a red flag. For ordinary privacy — reducing how much you're tracked — a mainstream privacy browser like Tor Browser or Brave is the more appropriate and lower-risk choice.

Through Discord directly, no — it proxies connections so other users can't see your IP. A phone number won't reveal it either. An email can in some cases expose the sender's IP via headers, but modern webmail usually hides it. Clicking unknown links is the real exposure to avoid.

Law enforcement can request connection logs from a VPN provider; whether that traces back depends on whether the provider keeps logs. Audited no-log VPNs have little to hand over. This is a key reason a VPN's logging policy matters more than its speed.

Use a blocklist (DNSBL) checker — like the Blacklist Check tool on this site — which queries the major lists mail servers consult. Note that results are indicative, since some lists rate-limit shared lookups, but it flags whether your IP appears on common blocklists.

In theory, someone with your IP could aim a denial-of-service flood at your connection to disrupt it temporarily — the “booting” seen in some gaming circles. A VPN hides your real IP behind the provider's, and most home routers and ISPs absorb minor attempts.

A static IP is a fixed public address that doesn't change over time. It's useful for hosting a server, remote access, or services that need a stable address to point at. ISPs usually charge extra for one, since most home connections use changing dynamic IPs.

A dynamic IP is assigned from your ISP's pool and can change — on reconnection, a lease renewal, or periodically. Most home connections use dynamic IPs because they're cheaper for ISPs and slightly better for privacy, since your address isn't a permanent identifier.

Check your IP here, restart your router, wait, and check again — if it changed, it's dynamic; if it's identical over days and reboots, it may be static. The certain way is to ask your ISP, since static IPs are usually a paid add-on you'd have ordered.

Often, yes — on a dynamic connection, a reboot can make your ISP assign a new address from its pool, though sometimes you get the same one back. On a static IP, it never changes. Our IP history log on the homepage lets you watch for changes over time.

It varies by ISP — some change every few days, some only on reconnection or after the device is offline for a while, and some keep the same address for months (a “sticky” dynamic IP). There's no fixed schedule; it depends on your provider's policy.

Frequent changes mean you have a dynamic IP with a short lease, so your ISP reassigns it regularly. This is normal and usually harmless. If you need a constant address for hosting or remote access, ask your ISP about a static IP or use a dynamic-DNS service.

Not really — gaming performance depends on ping and stability, not whether your IP is static. A static IP only helps if you host a game server and need a fixed address to share. For just playing online, a normal dynamic IP is completely fine.

A truly static public IP comes from your ISP, usually as a paid option — contact them to add it. For a free workaround that gives a stable hostname pointing at your changing IP, a dynamic-DNS (DDNS) service is the common alternative for home hosting.

DHCP (Dynamic Host Configuration Protocol) is the system that automatically hands out IP addresses. Your router runs a DHCP server that gives each device a private IP “lease” when it joins, and your ISP's DHCP assigns your public IP. It's why devices usually “just work” on a network.

Port forwarding works with a dynamic public IP, but you'll need to update wherever you reference the address whenever it changes. A static IP or a dynamic-DNS hostname makes it reliable, which is why people hosting servers or game lobbies often set one up.

Turn on your VPN, then load this page — the IP and location shown should be the VPN server's, not your real ones. If your true IP or country still appears, the VPN isn't masking properly. Also run the WebRTC leak test to catch leaks the main display might miss.

Usually a leak: WebRTC can expose your real IP through the browser even behind a VPN, or your IPv6 may bypass a VPN that only covers IPv4. Enable your VPN's leak protection, disable WebRTC, and re-test both protocols here to confirm it's sealed.

An IP leak is when your real address escapes despite a VPN being on — commonly via WebRTC in the browser, an unprotected IPv6 connection, or DNS requests going outside the tunnel. Our WebRTC leak test and this page's IPv4/IPv6 display help you spot one.

Enable your VPN's built-in leak protection and kill switch, turn on IPv6 leak protection (or disable IPv6), and disable WebRTC in your browser or use an extension that blocks it. Then verify with the WebRTC leak test and the IP shown on this page.

A proxy is a middle server your traffic passes through on its way to a website, so the site sees the proxy's IP instead of yours. It's similar to a VPN in masking your address, but a plain proxy usually doesn't encrypt your traffic the way a VPN does, so it offers less privacy. Either way, the public IP this page shows is whichever address your connection currently exits from.

A web proxy is a website that loads other sites on your behalf — you visit the proxy, type a URL, and it fetches and re-serves the page so the destination sees the proxy's IP instead of yours. It's the easiest way to get around a network or content block since there's nothing to install. The honest caveat: because every page you load passes through the proxy's own server, that operator can see and potentially log everything you do through it, and many free web proxies inject ads or trackers. They're fine for casually unblocking a harmless site, but don't use one for logins, banking, or anything private — a reputable VPN is the safer choice when privacy actually matters.

Paste it into our link expander, which follows the link on our server and shows you the full redirect chain and final destination — your browser never opens it. That lets you check a bit.ly or tinyurl link, or a suspected IP-logger link, without revealing your own IP or loading anything risky on your device. We show the facts and flag things worth a closer look, rather than a fake “safe/unsafe” verdict.

Your User-Agent is a short text string your browser sends to every website, describing your browser and version, operating system, and rendering engine so the site can serve a layout that fits your device. It reveals roughly what you're browsing with — not your name or identity — and modern browsers are deliberately reducing its detail for privacy. Our user-agent parser breaks yours down into readable parts and checks whether it's consistent with your browser's other signals.

The VPN is routing you through a server in that country — which is the point — but geolocation databases sometimes have the server's IP mapped to a stale or different location, so the city or country shown can lag reality. Switching VPN servers usually corrects it.

Your ISP assigns your real IP, so they always know it — a VPN hides your activity and destination from them, and hides your real IP from the websites you visit, not from the ISP itself. What a VPN protects is what sites and trackers downstream can see.

A free VPN does change the IP websites see, but many fund themselves by logging or selling user data, and some have leaked real IPs. The masking may work while the privacy doesn't. If privacy is the goal, scrutinize the provider — see our VPN-choosing guide.

Tor routes your traffic through several relays, so sites see a Tor exit node's IP, not yours — strong IP masking. It's slower than a VPN and doesn't protect non-browser traffic. Load this page in Tor and you'll see the exit node's address, not your own.

Sites block known VPN and datacenter IP ranges to fight fraud, abuse, and region-locked content sharing. Because many users share each VPN IP, one bad actor can get the whole address flagged. Switching to a less-used VPN server often gets around a block.

Only on devices where the VPN is actually running. Installing it on your laptop doesn't change your phone's IP. To cover everything, run the VPN on each device, or set it up on your router so all connected devices use it at once.

Load this page on your Jio Fiber connection and it shows the public IP Jio assigned you. Note that many Jio connections use CGNAT, so your public IP is shared with other customers — which is why hosting or port forwarding can need extra steps.

CGNAT (carrier-grade NAT) means your ISP shares one public IP among many customers to conserve addresses. It's invisible for normal browsing, but it complicates hosting servers, port forwarding, and some peer-to-peer apps, because you don't have a dedicated public address.

Mobile networks including Airtel typically place users behind CGNAT, so the address your device gets is effectively shared, not a dedicated public IP. This page shows the public IP the carrier presents you with; whether it's truly yours alone depends on the plan.

Carriers route traffic through regional gateways, so your IP can geolocate to wherever that gateway sits — often a different city or state than you. It's a normal artifact of how mobile networks aggregate traffic, not an error in your connection.

Often yes — toggling airplane mode or flight mode drops and re-establishes your mobile connection, and the carrier frequently assigns a new IP from its pool when you reconnect. It's a quick way to get a fresh mobile IP on a dynamic carrier network.

A dedicated public (static) IP is usually a paid add-on — contact your ISP to request one, often aimed at business or hosting use. Without it, you're typically on CGNAT with a shared address. Confirm what you currently have by checking this page and asking support.

Most ISP-provided routers use 192.168.1.1 or 192.168.0.1 as the admin login address — type it into a browser to reach the settings. The exact address and login are printed on a sticker on the router; check there if the common ones don't open.

Many mobile carriers have moved to IPv6 as the primary protocol, providing IPv4 only through translation when needed. So on mobile data you may see an IPv6 address while Wi-Fi shows IPv4. Both work; it just reflects how your carrier provisions addresses.

Usually not directly. Most Indian broadband and mobile connections now use CGNAT, where many households share one public IP, so there's no unique address the internet can route an incoming connection back to — which is what port forwarding needs. The honest options are: ask your ISP for a dedicated public or static IP (often a paid add-on), use a service that provides port forwarding through its own server (some VPNs and tunnelling tools do this), or use a relay/reverse-tunnel setup so the connection is initiated from your side. You can confirm you're behind CGNAT by comparing the IP shown on this page with the WAN IP in your router's admin panel — if they differ, you're sharing a carrier address.

An ASN (Autonomous System Number) is a unique number identifying a network operator on the internet — each major ISP has one, for example AS55836 for Reliance Jio and AS9498 for Bharti Airtel. It's how networks announce which IP ranges they control for global routing. Your connection's ASN and the network operator behind it are shown on this page alongside your IP, so you can see which provider's network you're actually exiting from — useful when a connection is routed through a parent network or a carrier hub.

Use a DNS lookup — our Reverse DNS tool, or the command “nslookup example.com” — to resolve a domain to its server IP. Note that sites behind a CDN like Cloudflare will show the CDN's IP, not the true origin server, which stays hidden by design.

A reverse lookup goes from an IP back to the hostname registered for it — the opposite of a normal domain lookup. It's useful for identifying what's behind an address. Try it with our Reverse DNS tool, which returns the PTR record for any IPv4 address.

It's a basic legitimacy check called forward-confirmed reverse DNS (FCrDNS): the IP's reverse record (PTR) should point to a hostname, and that hostname's forward record should point back to the same IP. When both agree, it signals the sender controls both ends and isn't a random or spoofed host, so mail is far less likely to be flagged as spam. A missing or mismatched pair is one reason legitimate mail gets rejected. Our Reverse DNS tool now checks this for you — it shows the PTR hostname and tells you whether it's forward-confirmed back to the original IP.

An SPF (Sender Policy Framework) record is a TXT record in your domain's DNS that lists which mail servers are allowed to send email for your domain. When a message arrives, the receiving server checks whether the sending IP is on that list; if not, the message can be marked as spam or rejected, which is how SPF blocks others from forging mail in your name. The record ends in a rule like -all (reject anything not listed) or ~all (soft-fail). Our Email DNS checker looks up your SPF record and explains what that ending rule means.

DKIM (DomainKeys Identified Mail) adds a cryptographic signature to the headers of the mail you send. The receiving server fetches your public key — published as a DNS record — and uses it to confirm the message really came from your domain and wasn't altered in transit. Unlike SPF and DMARC, a DKIM record lives at a name that includes a selector (<selector>._domainkey.yourdomain.com), so you need to know the selector to look it up; you'll find it in your mail provider's DKIM settings or in a sent message's DKIM-Signature header. Our Email DNS checker looks up DKIM once you supply the selector, alongside SPF and DMARC.

An IP address is the actual numeric location of a server; a domain name (like example.com) is the human-friendly label that points to it. DNS translates the domain into the IP so you don't have to remember numbers. One server can host many domains.

In your domain's DNS settings, create an “A record” for IPv4 (or “AAAA” for IPv6) with the server's IP as its value. After DNS propagates, the domain resolves to that server. This is the core step in connecting a domain you own to hosting you control.

An A record maps a domain or subdomain to an IPv4 address — it's the basic “this name lives at this IP” entry. The IPv6 equivalent is an AAAA record. When you point a site to a server, the A record is usually what you set.

An AAAA record is the IPv6 version of an A record — it maps a domain to a 128-bit IPv6 address instead of a 32-bit IPv4 one. A site can have both: the A record for IPv4 visitors and the AAAA record for IPv6, which is how dual-stack hosting lets each visitor connect over whichever protocol their network supports. It's named with four A's simply because an IPv6 address is four times the size of IPv4.

TTL (time-to-live) is a timer, in seconds, attached to each DNS record that tells resolvers and ISPs how long they may cache it before checking again. When you change a record — say, point a domain to a new IP — anyone whose cache still holds the old value keeps seeing it until the TTL expires, which is why a change can take minutes to a couple of days to be seen everywhere (often called DNS propagation). Lowering a record's TTL a day before a planned change makes the switch take effect faster.

Ports are numbered channels a server uses to separate different kinds of traffic on the same IP. Port 80 is the default for plain, unencrypted HTTP, while port 443 is the default for HTTPS — the same web traffic wrapped in TLS encryption so it can't be read or tampered with in transit. When you visit a site that starts with https://, your browser connects on 443 and performs a TLS handshake before any page data is exchanged; an http:// site uses 80. Most sites now redirect 80 to 443 so everything is encrypted by default.

Open our request headers tool, which shows the exact HTTP headers your browser sends, then use the “Export as code” panel to copy them as a ready-to-run request in Python, Node.js, cURL, or fetch(). It includes only the headers a client should actually send — the CDN-added and IP-bearing ones are left out — so the snippet works cleanly in a scraper or API client.

A 301 is a permanent redirect — it tells browsers and search engines the page has moved for good, and search engines pass the old page's ranking to the new one. A 302 is temporary, so the original address stays indexed and authority isn't transferred. The practical difference matters most for SEO: use 301 when a move is permanent, 302 when it's genuinely temporary. Our link expander shows the status code at each step of a redirect chain, so you can see which type a link uses.

Both are temporary redirects, but they differ in how they handle the request method. With a 302, many browsers historically changed a POST into a GET when following it — useful sometimes, but not always what you want. A 307 was introduced to remove that ambiguity: it explicitly preserves the original method and body, so a POST stays a POST. For a simple link that's always a GET, the two behave the same; the distinction matters mainly for forms and API calls. Our link expander shows the exact status code at each hop, so you can see which a server returns.

A 403 Forbidden means the server understood your request but refuses to serve the page — it's a permissions or policy block, not a “page missing” error like 404. Common causes are needing to be logged in, the content being restricted by region, a firewall or rate-limit rule reacting to too many requests, or the IP having a poor reputation. Quick things to try: clear cookies and sign in if required, switch networks (for example Wi-Fi to mobile data) to rule out an IP-level block, or wait if it's rate-limiting. If you suspect reputation, our blacklist check shows whether your IP is on a known blocklist, which is one of several inputs sites use.

Multi-hop redirect chains are common with marketing and affiliate links: each hop is usually a tracking domain that logs the click, attributes the sale, or drops a cookie before handing you to the real destination. It's mostly harmless but it's also how some links hide where they really lead. Our link expander follows the whole chain on our server and shows every hop and the final URL, so you can see exactly where a link goes before clicking it.

Cloudflare and similar CDNs sit in front of your server, so visitors and DNS lookups see Cloudflare's IP, not your origin's. This protects the real server from direct attacks and hides its address. It's why a normal lookup of a Cloudflare-protected site won't reveal the origin IP.

From a terminal, “ping example.com” sends test packets and reports replies and latency — no reply can indicate the host is down or blocking pings. Combine it with “traceroute” to see where along the path the connection stops.

Mail server IPs land on blocklists when they send spam, get compromised, or inherit a bad reputation from a previous user of the address. Check the IP against blocklists — our Blacklist Check tool does this — and follow each list's delisting process after fixing the cause.

WHOIS and regional registry (RIR) records show which organization owns an IP block and its abuse contacts. Our bulk audit and reverse DNS tools surface the network owner (ASN organization) for an address, which covers the most common reason people look this up.

Sometimes — if the server hosts a single site on that IP, typing the IP may load it. But most servers host many sites on one IP and rely on the domain name in your request to know which to serve, so the bare IP often won't work or shows a default page.

This means your device couldn't get a working IP from the router. Try, in order: reconnect to the network, restart your router, run “ipconfig /release” then “ipconfig /renew” on Windows, and reset the network adapter. It usually points to a DHCP or driver hiccup, not a broken connection.

It means two devices on your network ended up with the same private IP, so neither can communicate reliably. Restarting the affected device or your router usually resolves it by reassigning addresses. Assigning static local IPs outside the DHCP range prevents repeat conflicts.

That's normal — each active network interface gets its own IP. A typical machine might have one for Wi-Fi, another for a wired Ethernet connection, plus virtual addresses created by software like Docker, VirtualBox, or a VPN client. They coexist without conflict because they're separate interfaces. The address that matters for reaching the internet is the one tied to your active connection; the public IP the wider internet sees is shown at the top of this page.

It means the device asked your router for an IP and got no answer, so it can't join the network. Restart the router and device, check Wi-Fi signal, and make sure the router's DHCP server is enabled and hasn't run out of addresses to hand out.

On Windows, open Command Prompt and run “ipconfig /release” to drop your current local IP, then “ipconfig /renew” to request a fresh one from the router. This fixes many “no valid IP” and connection-stuck issues without a full reboot.

A MAC address is a permanent hardware ID burned into a network adapter; an IP address is assigned by the network and can change. The MAC identifies the physical device on the local network; the IP identifies it for routing across networks. Both work together to deliver data.

Paste it into our MAC lookup tool, which reads the first half of the address (the OUI prefix) and matches it against the IEEE registry to show the maker of the network adapter — useful for identifying an unfamiliar device in your router's client list. Note that modern phones use randomized MAC addresses for privacy, so a “no vendor found” result is normal and not a sign of an intruder; the tool flags those for you.

A 0.0.0.0 or empty gateway means your device has no route to the internet — it didn't receive valid network settings, usually a DHCP or connection failure. Renewing the IP (release/renew), restarting the router, and checking the cable or Wi-Fi link typically restores it.

Run “tracert example.com” on Windows or “traceroute example.com” on Mac/Linux. It lists each network hop between you and the destination with timing, so you can see where delays or failures occur along the route — useful for diagnosing where a connection breaks down.

On Windows, run “ipconfig /flushdns” in Command Prompt; on Mac, “sudo dscacheutil -flushcache” in Terminal. This clears stored domain-to-IP lookups, fixing pages that won't load due to outdated records. It doesn't change your IP or connection speed, just name resolution.

It varies by location and connection, so the honest answer is to measure it — our DNS speed test times the major resolvers (Cloudflare, Google, Quad9, OpenDNS, AdGuard, Mullvad) from your network and shows which responds quickest for you. Switching to a faster resolver can shave milliseconds off loading new sites, but DNS is only a small part of total page-load time, so it's a modest improvement rather than a bandwidth boost. People also switch for reliability, privacy, or built-in filtering.

Yes — 1.1.1.1 is a widely used public DNS resolver run by Cloudflare, and it's a legitimate, mainstream choice. Cloudflare states it doesn't sell your data and purges the query logs it keeps for operational reasons within 24 hours. Using it changes only which service translates domain names into IP addresses; it doesn't hide your IP from the websites you visit, and it isn't a VPN. Google's 8.8.8.8 and Quad9's 9.9.9.9 are comparable alternatives — our DNS speed test shows which is quickest from your connection.

An anycast IP is a single address announced from many locations at once, so your request is routed to the nearest one. DNS resolvers like 8.8.8.8 and 1.1.1.1 use it for speed and resilience. It's why one IP can “be” in many cities — and why geolocation of such IPs is unreliable.

Geolocation maps an IP to where its owner registers or routes it, which is often a regional hub, not the user's location. ISPs, mobile carriers, VPNs, and anycast services all cause this. Country is usually right; city is a best guess and frequently off — that's expected, not a fault.