CheckWebsiteNow

Address lookup (DNS) errors

DNS_PROBE_POSSIBLE

Chrome had a lookup problem and was about to check your DNS.

Quick answer

This code appears briefly while Chrome investigates a failed address lookup. If it stays on screen, the extra check did not finish. Treat it like a general DNS problem.

When to wait: Often yes; reload after a minute.

If you are visiting the website

  1. Wait and reload Wait a minute, then reload the page once. Often the code changes to a clearer one, or the page simply loads.
  2. Try a private window Open an incognito window (Ctrl+Shift+N on Windows, Command+Shift+N on Mac) and visit the site. Extensions do not run there unless you allowed them, so a working page points to an extension.
  3. Turn off extensions one at a time Ad blockers, privacy tools, VPN extensions and security add-ons can block lookups. Open chrome://extensions, switch them off one by one to find the cause, then turn the others back on.
  4. Clear Chrome's lookup memory Chrome keeps its own list of recent lookups and open connections. Clearing both gives the next attempt a clean start.
    Windows
    Open chrome://net-internals/#dns and click Clear host cache. Then open chrome://net-internals/#sockets and click Flush socket pools. In Edge use edge:// instead of chrome://.
    macOS
    Open chrome://net-internals/#dns and click Clear host cache. Then open chrome://net-internals/#sockets and click Flush socket pools.
    Linux
    Open chrome://net-internals/#dns and click Clear host cache. Then open chrome://net-internals/#sockets and click Flush socket pools.
    ChromeOS
    Open chrome://net-internals/#dns and click Clear host cache. Then open chrome://net-internals/#sockets and click Flush socket pools.
  5. Clear the device's DNS cache The operating system keeps a separate lookup memory as well.
    Windows
    Open Command Prompt and run: ipconfig /flushdns.
    macOS
    In Terminal run: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Enter your Mac password when asked.
    Android
    Turn Airplane mode on and off again, or restart the phone.
    iPhone and iPad (iOS)
    Turn Airplane Mode on and off in Control Center, or restart the iPhone.
  6. Restart your router Turn your router off, wait about 30 seconds and turn it on again. This renews your connection and its address lookup.
  7. Test your security software briefly Firewalls and antivirus tools with web filtering can stop lookups. Pause the web protection for a minute to test, then turn it back on right away. If that was the cause, add Chrome as an allowed app instead.

What this code means

Chrome shows DNS_PROBE_POSSIBLE while it prepares a quick test of your DNS service (the lookup that turns names into addresses). Normally the page then switches to a clearer code, such as NXDOMAIN or NO_INTERNET. If it stays, the test itself did not finish.

Is it the website or me?

Usually it is your device or network. Security tools, VPNs and extensions that filter traffic can stop the lookup or the test. Try the site on another device: if it works there, focus on this computer.

For developers: what happens technically

The DNS probe is a feature of Chromium's error pages. Its states, from POSSIBLE and STARTED to the FINISHED results, are listed in net_error_info.h. A page stuck on POSSIBLE means no final probe result replaced the first code.

Common questions

Why does the code change after a few seconds?

That is normal. Chrome finished its DNS test and replaced the code with the result, which tells you more about the cause.

Is DNS_PROBE_POSSIBLE a sign of a virus?

No. It is a normal Chrome status. Security software that filters web traffic can trigger it, but the code itself is not a sign of infection.

Which extensions usually cause it?

Any extension that filters or redirects traffic can, such as ad blockers, VPN or proxy extensions and some security add-ons. Turn them off one by one to find the one involved.

Do I need to reinstall Chrome?

Rarely. Try the steps above first. Reinstalling only helps if Chrome's own files are damaged, which is uncommon.

Will a different DNS server help?

Sometimes. If the code later turns into a DNS problem on your network, a public resolver such as 1.1.1.1 or 8.8.8.8 is a good test. Write down your current DNS settings first so you can switch back.

Likely causes

  • Common A temporary DNS or network problem. (Your side)
  • Sometimes An extension, firewall or security tool blocks the lookup. (Your side)

Is the website down? Check it now

One measurement point. Results explain what we saw, not a worldwide verdict.

Sources

Last reviewed: