Skip to content
AdminKit

Dynamic IP vs CGNAT vs static: what it means for long-term monitoring

A dynamic IP changes periodically but is yours alone while assigned; a CGNAT IP is shared with other customers right now and may also change; a static IP is yours and stable. AdminKit explains why the difference matters: any security check tied to 'your IP address' only describes a single moment, not an ongoing state, unless something keeps re-checking it.

By AdminKit team, Netbase JSC · Updated

Key takeaways

  • “Dynamic or static” and “shared (CGNAT) or exclusive” are two separate properties. Your connection has one answer to each.
  • A dynamic address is still yours alone while it is assigned. A CGNAT address is shared with other customers at the same moment.
  • Any check tied to an IP address (blocklist, open ports, a DNS record that points at it) describes one moment. It goes stale when the address changes, and on a shared address it may describe someone else’s traffic.
  • You can tell which kind of address you have by comparing the WAN address on your router with the public address AdminKit’s what is my IP tool shows.
  • Dynamic DNS keeps a name pointing at your current address. It does not tell you whether that address is clean or exposed.

Which three questions does “what’s my IP” really ask?

This guide is part of AdminKit’s DNS cluster, which covers the broader set of checks worth running alongside an IP-address lookup. “What’s my IP, and does it change?” is really three distinct questions that get run together:

  • Is my address dynamic or static? Dynamic means your ISP can reassign it periodically; static means it stays the same indefinitely.
  • Is my address shared (CGNAT) or exclusive? Shared means other customers are behind the same public address at the same time as you; exclusive means it’s yours alone, whether or not it changes.
  • Is my address reachable from outside, or behind another layer of translation entirely? This is a separate, related question about inbound connectivity, covered in our CGNAT guide. It also matters for real-time peer-to-peer apps (video calls, VoIP), which rely on STUN/TURN to find a working path and fall back to a relay when a direct connection isn’t possible.

Most home internet connections are dynamic and may or may not also be CGNAT, depending on the ISP and plan tier; most business connections are static and not CGNAT, because business customers typically pay for the stability. None of these combinations is inherently more or less “secure” — they’re different operational properties that change what a given check result actually means and for how long.

Address typeWho uses the public addressHow long a check result stays meaningful
Static, exclusiveOnly you, indefinitelyUntil something on your side changes (a new service, a new record, your own sending behaviour)
Dynamic, exclusiveOnly you, while the lease or session lastsUntil the next reassignment, then it describes whoever holds that address next
Static or dynamic, shared (CGNAT)You and other customers of the same ISP, at the same timeOnly partly yours even today: other customers’ traffic shapes the result

How do you tell which kind of address you have?

Two numbers answer most of it: the WAN (internet-side) address your router reports on its status page, and the public address a website sees when you connect. AdminKit’s what is my IP tool shows the second one, read directly from your request, together with the network (ASN) it belongs to. It also shows a hint when the address looks shared, for example when the network belongs to a mobile carrier.

Compare the two numbers:

Example (illustrative values, not a real connection)

Router status page    WAN IPv4 address: 100.72.14.9
AdminKit my-ip tool   Your IP: 203.0.113.57   Network (ASN): Example ISP

-> The router's WAN address sits inside 100.64.0.0/10, and the public
   address is different: the ISP translates your traffic again (CGNAT).
  • The router’s WAN address matches the public address. You have your own public IPv4 address. It may still be dynamic.
  • The WAN address is in 100.64.0.0/10. That block is the shared address space RFC 6598 reserves for carrier-grade NAT, and the IANA special-purpose registry lists it as not globally reachable. Your ISP is translating your traffic to a shared public address.
  • The WAN address is a private address (10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16). Something upstream, often a second router or the ISP’s own equipment, is doing NAT in front of yours. It may or may not be CGNAT, so ask your ISP.

Whether the address is dynamic is harder to see in one look: check your plan description, or note the public address and compare it over a few weeks.

Why does a dynamic address change, and how often?

There is no single interval. Many ISPs hand out the router’s WAN address with DHCP, which RFC 2131 describes as a lease: the address is yours for a set period, the router renews it before it runs out, and the server “attempts to return the same network address each time the client requests an address”. That is why a dynamic address can stay the same for months and then change after a long outage, a router replacement or a change on the ISP’s side. Other ISPs assign the address per connection session, so it can change at every reconnect.

The same idea applies to IPv6. A home router typically receives a whole prefix from the ISP through DHCPv6 prefix delegation, and that prefix can also be renewed or replaced. When it changes, every device address on your network changes with it. The RIPE community’s operator guidance, RIPE-690, considers non-persistent IPv6 prefixes harmful and recommends persistent prefixes as the default, so how often yours changes depends on whether your ISP follows that advice. The practical rule is the same for both: treat any dynamic address as something that will change at a time you didn’t choose.

Why does a point-in-time check have a shelf life?

Imagine running a blacklist check today and getting a clean result. If your IP is static and exclusively yours, that result stays meaningful until something about your traffic changes it — a reasonably stable signal. Blocklist operators such as the Spamhaus Project list and delist individual IP addresses based on observed sending behavior, not a fixed assignment, which is exactly why a reassigned or shared address inherits whatever reputation already attaches to it rather than starting clean. Now imagine the same clean result on a dynamic, CGNAT-shared address: tomorrow your ISP could reassign you to a different pool entirely, putting you behind a different shared address with its own, unrelated reputation — one you had no part in creating and no way to have checked in advance. The check wasn’t wrong when you ran it; it just described a situation that may no longer exist by the time you’d want to rely on it.

The same logic applies to a port-exposure check, such as AdminKit’s open ports on my IP tool. A port that’s closed today on your current address tells you nothing about whether the next address your ISP assigns you — or the next device joining your current CGNAT pool — has anything exposed, since neither of those is something a single check from last week can see.

Check tied to your IPWhat makes the old result staleWhen to run it again
Blocklist statusA new address, or other customers’ traffic on a shared oneAfter any address change; on a schedule if you send mail
Open portsA new address, a router or firmware update, a new device or appAfter any of those changes
DNS records pointing at your IPThe address changes and the record still points at the old oneEvery time the public address changes
Allowlists that name your IP (VPN, admin panels, cloud firewalls)The address changes and access breaks, or the old address goes to someone elseEvery time the public address changes

On a shared address there is a second catch: some results are not about you at all. AdminKit’s Check API reflects this. When its my-IP check classifies the caller’s address as shared (inside 100.64.0.0/10, on a mobile carrier’s network, or flagged by another shared-address signal), it hides the per-list blocklist detail, because a listing on that address may belong to a different customer.

What does CGNAT change about logs and abuse reports?

When many customers leave through one public address, that address alone no longer identifies a subscriber. The ISP can only tell customers apart by the public address plus the source port plus the exact time. That is why RFC 6302 recommends that internet-facing servers which log client IP addresses also log the source port and a timestamp accurate to the second from a traceable clock, preferably in UTC. Its stated reason: carrier-grade NATs may reuse ports almost immediately, so a log line without a port and a precise time cannot be traced back to one customer.

Example log line (illustrative, documentation addresses)

2026-11-10T08:14:03Z  src=203.0.113.57:41822  dst=198.51.100.20:443  proto=tcp

Without ":41822" and the second-accurate UTC time, the ISP cannot tell
which of the customers sharing 203.0.113.57 made this connection.

This cuts both ways. If you run a server, log the port so an abuse report you send is actionable. If you sit behind CGNAT, an abuse report or a rate limit aimed only at your public address also hits everyone else on it. RFC 7021, which measured CGN impacts in a test network, notes reports that anti-abuse measures limiting connections per address can misread address sharing as too many connections from a single device. It also recorded peer-to-peer applications failing behind CGN when two users needed the same port on one shared address.

RFC 6888 requires carrier-grade NATs to use “paired” address pooling by default, so all of one customer’s sessions share one external address at a given time. It says nothing about which address you get tomorrow.

Does a static IP remove the need to re-check?

A static IP removes one entire variable: you’re always checking the same address, so results accumulate meaning over time instead of resetting with every reassignment. That’s a genuine simplification, especially for anyone running a server, a mail system, or anything else where consistent identity matters. But it doesn’t replace the need to re-check other things that can change independently of the address itself — new ports opened by a software update, a newly published DNS record, a certificate approaching expiry. Static addressing narrows what you need to keep watching; it doesn’t eliminate the need to watch.

What does dynamic DNS solve, and what doesn’t it?

If you’ve set up dynamic DNS (DDNS) to keep a hostname pointed at your home server despite a changing IP, it’s worth being clear about what that does and doesn’t cover: DDNS keeps a name-to-address mapping current, which is genuinely useful for reaching your own server by a stable name. It has no opinion on whether the current address behind that name has an open port it shouldn’t, or sits on a blacklist — it’s solving the addressing problem, not the monitoring problem, and treating the two as the same thing is a common gap.

DDNS also only helps when inbound connections can reach you. Behind CGNAT, the public address the name points to is shared, and the ISP’s NAT drops unsolicited inbound connections unless it offers port forwarding. A DDNS name that resolves correctly but leads nowhere is a common sign of CGNAT; our CGNAT guide covers the workarounds.

How do you move from “check once” to “watch continuously”?

The practical takeaway isn’t that dynamic or CGNAT addressing is dangerous — it’s that any check tied to an IP address is only as current as the last time you ran it, and an address that can change (or was never exclusively yours to begin with) makes that staleness arrive faster. Start by confirming your current situation with AdminKit’s what is my IP tool, and check whether any DNS records you maintain, via DNS lookup, still point at the address you think they do. If your address has changed in a way you didn’t expect, it’s also worth ruling out that your router’s own DNS settings weren’t tampered with in the process — see is my router’s DNS hijacked? for how to check. From there, the durable fix for anything that changes over time is something that re-checks on an ongoing basis rather than once. Where a compromised device on a changing address is the bigger worry, Netbase builds and runs Protective DNS for your network as a custom engagement — a filtering resolver that blocks known-malicious domains per device and logs every block; talk to our team about your setup.

A simple routine covers most small setups:

  1. Write down your current public address and whether it is shared.
  2. Re-run the checks in the table above whenever that address changes, and after any router, firmware or firewall change.
  3. If you rely on your address being stable (mail, remote access, allowlists), ask your ISP for a static, non-shared address rather than working around changes.

This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.

Frequently asked questions

How is a dynamic IP different from CGNAT?

They're independent properties that can combine in any way. A dynamic IP means your ISP can reassign you a different address periodically (on router reboot, lease renewal, or at their discretion), but while assigned, it's exclusively yours. CGNAT means your address is shared with other customers at the same time, which may or may not also change periodically — our [CGNAT guide](/guides/what-is-cgnat/) covers that distinction in more depth. The specific address block ISPs use for this, 100.64.0.0/10, is reserved in [IANA's IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml) precisely so it's never also assigned as an ordinary public address.

Why does a changing IP matter for security checks specifically?

A blacklist check, a port scan, or a DNS record pointing at 'your IP' are all snapshots of a single moment. If your address changes next week, that blacklist result, open-port finding, or DNS record is now describing a different situation — possibly a different customer entirely if you were on a CGNAT pool — and nobody re-checks it unless you do, or something automated does it for you.

Doesn't a static IP solve all of this?

It removes the address-change variable, but not the need for ongoing checks — a static IP can still end up on a blacklist, gain a newly exposed port after a configuration change, or have a stale DNS record, all independent of whether the address itself ever changes. A static IP makes monitoring simpler to reason about, not unnecessary.

If I use a dynamic DNS (DDNS) service, does that solve the dynamic-IP problem?

DDNS solves the specific problem of a hostname needing to keep pointing at your current address as it changes — useful for reaching a home server by name. It doesn't by itself tell you whether that current address has a security issue; it just keeps the pointer accurate, which is a different (and narrower) job than ongoing monitoring.

What does 'something watching continuously' actually look like in practice?

Rather than running a manual check and trusting the result indefinitely, a continuous approach re-runs the relevant checks on a schedule or in response to a detected change, so a new exposure, a new blacklist entry, or a changed IP gets flagged close to when it happens rather than whenever someone next thinks to look.

Want AdminKit to watch this for you?

Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.

Huy Nguyen (David), Founder and CEO of Netbase JSC

Talk to an expert

Huy Nguyen (David), Founder & CEO, Netbase JSC

Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.