Verify You're Using Cutline
After configuring your DNS, follow these steps to confirm you're using the cut path.
Automatic DNS Check
Click the button below to check if this device is using Cutline DNS:
How this check works
This page is served via public DNS, so it always loads. When you click "Check Now," your browser attempts to fetch https://on.thecutline.org/ok. That hostname is notin public DNS—only Cutline resolvers answer it.
If the fetch succeeds, this device used Cutline DNS to resolve the name. If it fails, this device either did not query Cutline DNS, or another service (Private Relay, Secure DNS, or a VPN) overrode your configuration.
You are not sent to a hostname that fails. The check is performed silently in JavaScript, and any error is caught by this page.
Test Steps
Quit and Restart Safari (macOS/iOS)
Safari caches DNS aggressively. On macOS, fully quit Safari (⌘Q), then reopen it. On iOS, swipe up to close Safari completely, then reopen.
Other browsers may also cache DNS. If testing in Chrome or Firefox, restart them as well.
Test Normal Sites Work
Visit a normal website to confirm DNS is working:
- example.com — Should load
- wikipedia.org — Should load
- github.com — Should load
If these sites don't load, your DNS configuration may be incorrect. Double-check the settings.
Run the Automatic Check
Use the Automatic DNS Check button at the top of this page to verify you're on the cut path. This is the easiest and most reliable verification method.
Use the Canary (Connection Proof, Not DNS Proof)
Visit the HTTP canary by IP address to confirm you can reach the resolver infrastructure:
Important: This canary proves you can connect to this path, NOTthat you're using these DNS servers. It is connectivity verification only.
The hostname canary on.narge.test exists but is weak in Safari (may be bypassed by search).
Command-Line DNS Check (Advanced)
If you're comfortable with terminal/command prompt, you can directly query Cutline DNS:
macOS/Linux
dig @64.176.200.99 example.comShould return an address for example.com.
Windows
nslookup example.com 64.176.200.99Should return an address for example.com.
Test a Blocked Domain
Query a domain from the StevenBlack list. It should return NXDOMAIN (no such domain).
Troubleshooting
Normal sites don't load
- Double-check the DNS server IPs:
64.176.200.99and149.28.79.49 - Restart your device or renew DHCP
- Try flushing DNS cache (see below)
- On Windows, make sure you selected "Manual" DNS, not "Automatic"
Blocked sites still load
- Fully quit and restart your browser (especially Safari)
- Check that your device isn't using another DNS source (VPN, proxy, corporate network)
- On iOS, verify DNS is set for the specific Wi-Fi network you're on
- The site may not be in the block list (the list is an approximation)
Flush DNS Cache
macOS:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderWindows:
ipconfig /flushdnsLinux:
sudo systemd-resolve --flush-caches