Blog · Basics

Static vs dynamic IP address

Direct answer: A dynamic IP can change over time (typical home internet). A static IP is fixed—often used for business, hosting, or special ISP plans. Check your current public address anytime on What Is My IP Address IP.

Which do I have?

If you did not pay for a static IP product, you almost certainly have a dynamic public IP. It may still look stable for weeks until your ISP renews the lease or you reboot your modem.

Cost and who sells static

Residential ISPs sometimes offer a static IPv4 add-on; prices vary by market. Business fiber often includes static options or larger blocks. Before you pay, ask whether you need a truly fixed number or just a stable hostname—dynamic DNS plus a dynamic address solves many remote-access cases.

IPv6 nuance

Some providers delegate a stable IPv6 prefix even when IPv4 is dynamic, which changes firewall design. If you enable IPv6 on the LAN, read IPv4 vs IPv6 and why IPv6 might not show.

Hosting and port forwarding

If you open ports to the internet, a changing public IP breaks naive bookmarks unless you use DDNS. See port forwarding and how to change your public IP when you rotate on purpose.

People also ask

How do I know if I am static? You paid for a static SKU or your contract explicitly lists a fixed address. Otherwise assume dynamic.

Does static mean safer? Not inherently—security comes from patching, firewalls, and credentials, not from address permanence.

Can I get static IPv6 only? Some ISPs delegate stable prefixes while IPv4 remains dynamic—ask your provider about prefix stability.

Extended guide: business vs home

Small businesses sometimes pay for static IPv4 to simplify remote access or VPN landing zones. Homes rarely need it unless they self-host with brittle legacy clients that cannot handle DDNS.

Dynamic addresses can still be stable for long periods—stability is observational until it isn’t. Automate hostname updates if you rely on inbound connections.

When migrating ISPs, expect both static and dynamic assignments to change; update firewall rules and DNS accordingly.

IPv6 prefix stability may differ from IPv4 behavior on the same line—verify both if you publish AAAA records.

How ISPs actually assign and renew addresses

Most residential customers receive a lease from a large pool. The lease has a time-to-live. While the modem stays online and renews quietly, your address can remain unchanged for a long time—sometimes months. People mistakenly call that “static behavior,” but it is still dynamic; the ISP can reclaim or rotate it after maintenance or policy changes.

Power-cycling your modem often triggers a new lease negotiation. If your ISP uses aggressive pooling, you might get a different public IP after each reboot. That surprises gamers and self-hosters who expected yesterday’s number to return. Document your pattern: if reboots always rotate you, plan around DDNS or a static product before building fragile inbound rules.

Business circuits frequently include service-level agreements that mention fixed addressing or stable routing. Read the fine print: “business” branding does not automatically mean static IPv4. Ask whether the address is guaranteed, how failover works, and whether IPv6 prefix delegation is stable for reverse DNS or VPN endpoints.

Carrier-grade NAT (CGNAT) complicates the picture for some mobile and budget fiber plans. You might share a public IPv4 with neighbors while still receiving a unique private lease on your CPE. In those cases, “my public IP” from a checker is the shared carrier address, not a 1:1 map to your apartment—port forwarding and inbound hosting often require a different ISP tier or IPv6.

If you need email servers or reputation-sensitive workloads, static IPv4 is sometimes marketed as a deliverability aid. Modern best practice still relies on authentication (SPF, DKIM, DMARC) and provider reputation—not merely a fixed IP—so weigh cost against real deliverability audits before buying.

When moving house, expect a new assignment even if you keep the same ISP brand: DHCP pools are regional. Update DDNS, firewall allowlists, and any third-party dashboards that stored the old digits.

Recording changes for your own documentation

Keep a simple log: date, WAN IP, whether VPN was used, and any outages. Future you will thank present you when diagnosing “it broke after Tuesday.”

Home labbers naming servers by IP literals should switch to DNS names internally—retyping numbers after DHCP churn is error-prone.

Tax and compliance rarely care about dynamic vs static for consumers; business users should consult accountants only if they deduct connectivity—outside our scope, but a common misconception worth naming.

Summary checklist

Decide requirements: remote access, email deliverability, gaming, or curiosity. Match product to requirement: static IP, DDNS, or VPN hub. Re-evaluate after ISP price changes.

Log your WAN IP weekly if you suspect instability; data beats memory.

Related guides