[{"data":1,"prerenderedAt":10},["ShallowReactive",2],{"article:en:public-vs-private-ip":3},{"locale":4,"slug":5,"path":6,"title":7,"description":8,"html":9},"en","public-vs-private-ip","\u002Flearn\u002Fpublic-vs-private-ip\u002F","Public vs. private IP addresses: what's the difference?","Understand address scope, private IPv4 ranges and NAT, and why several devices can share one public internet address.","\u003Ch2>Where the address is used\u003C\u002Fh2>\n\u003Cp>A public IP address belongs to address space used for routing on the public internet. A private address is used inside a network, such as a home or office. Separate homes can reuse the same private IPv4 addresses because their local networks are distinct. Public addressing does not automatically make a device reachable: routes, firewalls and whether an application accepts incoming connections still determine what can connect.\u003C\u002Fp>\n\u003Ch2>Recognizing private IPv4 ranges\u003C\u002Fh2>\n\u003Cp>The private IPv4 ranges are \u003Ccode>10.0.0.0\u002F8\u003C\u002Fcode>, \u003Ccode>172.16.0.0\u002F12\u003C\u002Fcode> and \u003Ccode>192.168.0.0\u002F16\u003C\u002Fcode>. A computer might use \u003Ccode>192.168.1.20\u003C\u002Fcode> to communicate with a home router. This is an example, not a measurement of your connection. Not every address beginning with 172 is private: the reserved range runs from 172.16 through 172.31. Loopback and link-local addresses have separate purposes, so all non-public addresses should not be treated as one category.\u003C\u002Fp>\n\u003Ch2>How a shared exit works\u003C\u002Fh2>\n\u003Cp>Network address translation, or NAT, commonly lets several devices use one public IPv4 address. Address and port mappings help replies reach the connection that requested them. Providers may add another translation layer, known as carrier-grade NAT. The shared range \u003Ccode>100.64.0.0\u002F10\u003C\u002Fcode> was reserved for such arrangements and is distinct from the three private ranges above. Whether a subscriber receives a dedicated public address depends on the access service.\u003C\u002Fp>\n\u003Ch2>What this changes in practice\u003C\u002Fh2>\n\u003Cp>Ordinary browsing and messaging usually work without manual address configuration. Hosting a service or accessing equipment remotely requires more care: a local forwarding rule alone cannot remove every upstream restriction. IPv6 also has address scopes, including global and local uses. A globally addressed device still needs appropriate access controls. Determine which address and network boundary you are discussing before deciding whether remote access is possible.\u003C\u002Fp>\n\u003Ch2>Does a router WAN address guarantee a dedicated public IPv4?\u003C\u002Fh2>\n\u003Cp>WAN describes the upstream interface, not the allocation type. Its address may still be private or shared by an ISP. Even if it matches a lookup result, inbound access depends on firewall rules, mappings and provider policy. For remote access, confirm both allocation and incoming-connection restrictions rather than relying on an address match.\u003C\u002Fp>\n\u003Ch2>Further reading\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc1918\" rel=\"nofollow noopener noreferrer\">RFC 1918\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc6598\" rel=\"nofollow noopener noreferrer\">RFC 6598\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc4291\" rel=\"nofollow noopener noreferrer\">RFC 4291\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n",1793192130554]