What is a Static IP?

Why Fixed IP Addresses Simplify DNS Filtering

A static IP address is one that doesn't change. Static IPs are ideal for DNS filtering because your filter profile is always matched to the same address — no synchronization needed.

Set Up DNS Filtering

Step 1: What is a Static IP?

A static IP address is a permanently assigned address that doesn't change over time. Your ISP assigns it to your connection, and it remains the same every time you connect — across reboots, power outages, and router resets.

Static IPs are typically available from ISPs as a paid add-on for business accounts. Residential connections usually receive dynamic IP addresses that can change periodically.

Step 2: Static vs Dynamic IP Addresses

  • Static IP: Never changes. Ideal for servers, DNS filtering, remote access, and any service that needs a consistent address. Typically costs extra from your ISP
  • Dynamic IP: Assigned by DHCP and can change at any time (though many ISPs rarely rotate them). Standard for residential connections. Free

From a DNS filtering perspective, static IPs are preferred because the association between your IP and your filter profile never breaks. With dynamic IPs, you need a mechanism to keep your profile updated when the IP changes.

Step 3: Static IPs and DNS Filtering

CleanBrowsing uses your public IP to identify your account and apply your filter settings. With a static IP:

  • One-time setup: Register your static IP with your CleanBrowsing account once — it works forever
  • Reliable filtering: No risk of filtering gaps when an IP change isn't detected
  • Multiple profiles: Static IPs can be associated with specific filter profiles for different networks
  • API integration: The CleanBrowsing API supports registering static IPs and subnets for large deployments

Step 4: Working with Dynamic IPs

If you don't have a static IP, CleanBrowsing still works — you just need to keep your registered IP current:

  • Dynamic IP scheduler: CleanBrowsing provides scripts that automatically update your registered IP via API when it changes
  • Encrypted DNS: DoH and DoT connections authenticate using credentials rather than source IP, making them immune to dynamic IP issues
  • Device-level deployment: Per-device DNS profiles bypass IP-based identification entirely

If your ISP uses CGNAT (shared public IP), encrypted DNS with per-device credentials is the recommended approach.

Set up DNS filtering on your network

Get Started