Short answer: INET_E_RESOURCE_NOT_FOUND means Windows could not find the server, or the proxy, for the address you opened. Almost always the name did not resolve in DNS. Check the address for typos, look the name up with nslookup, flush the DNS cache and, if the lookup still fails, switch to another DNS server. If only your own domain fails, from every network, its DNS record is missing.
nslookup example.com # ask the DNS server Windows uses now
nslookup example.com 1.1.1.1 # ask a public resolver instead
ipconfig /flushdns # drop cached answers, failed ones includedIf the first lookup fails and the second one returns an address, your DNS server is the problem. If both say Non-existent domain, the name has no address anywhere, and only whoever runs the domain can fix that. If both return an address and the page still fails, look at the proxy, VPN and hosts file sections below.
What INET_E_RESOURCE_NOT_FOUND means
The code comes from urlmon, the networking library behind Internet Explorer. Microsoft lists it among its URL moniker error codes as INET_E_RESOURCE_NOT_FOUND, value 0x800C0005: “The server or proxy was not found.” The old Edge, the one built on the EdgeHTML engine, showed this code on its “can't reach this page” error screen, which is why many people know it as an Edge error. That Edge reached the end of support on 9 March 2021. The current, Chromium-based Edge reports the same failure with Chromium's error codes, such as DNS_PROBE_FINISHED_NXDOMAIN or ERR_NAME_NOT_RESOLVED. Because the INET_E code belongs to urlmon, a Windows program that still loads web content through that library can show it as well. The fixes are the same either way, because the cause is the same: a host name that does not turn into an IP address, or a proxy that cannot be reached.
| What you see | What it points to | Where to go |
|---|---|---|
| nslookup says Non-existent domain from every resolver | The name has no record, or you mistyped it | Check the address, then the domain's records |
| nslookup says DNS request timed out | Your DNS server does not answer | Change the DNS server |
| Works with 1.1.1.1, fails with your normal server | Your resolver is broken or filters the name | Change the DNS server |
| The site moved or was set up in the last hours | Windows cached an old or failed answer | Flush the DNS cache |
| nslookup returns an address, the page still fails | Proxy, VPN, secure DNS in Edge or the hosts file | Proxy and VPN |
| Nothing loads in any program | The network stack or the connection itself | Reset Winsock and TCP/IP |
Step 1: check the address and the DNS answer
Read the address bar first. A missing letter, a wrong ending (.co instead of .com) or a stray space produces exactly this error, because the misspelt name does not exist. Then ask DNS directly, which takes the browser out of the picture. The Windows version of nslookup answers in one of three ways:
- An
Address:line under the name. DNS works for this name. Skip to proxy and VPN and the hosts file. Non-existent domain. The resolver says the name does not exist. Ask a second one (nslookup example.com 8.8.8.8); if it agrees, the domain really has no address.DNS request timed out.Your DNS server did not reply at all. That is the case covered in depth in DNS server not responding.
The nslookup guide explains the rest of its output, including Server failed and how to query a record type other than the address.
Step 2: flush the DNS cache
Windows keeps answers in its DNS client cache, failed ones too. Microsoft's ipconfig reference says /flushdns discards these negative cache entries along with the rest, which is what you want when a site was just created or moved and Windows still remembers that it did not exist. Run it, then reload the page:
ipconfig /flushdns
ipconfig /displaydns | more # what is cached now, hosts file entries includedEdge keeps a short-lived host cache of its own: open edge://net-internals/#dns and press Clear host cache. The commands for macOS, Linux and the other browsers are in how to flush the DNS cache.
Step 3: change the DNS server
If your normal server times out or claims a real site does not exist, point the network adapter at two public resolvers from different providers. In PowerShell as administrator:
Get-NetAdapter | Where-Object Status -eq 'Up' # find the adapter name
Set-DnsClientServerAddress -InterfaceAlias 'Wi-Fi' -ServerAddresses ('1.1.1.1','9.9.9.9')
Clear-DnsClientCache
Resolve-DnsName example.comSet-DnsClientServerAddress -InterfaceAlias 'Wi-Fi' -ResetServerAddresses returns to the servers your router hands out. Edge can also bypass Windows: its Use secure DNS setting (type secure DNS into the search box on edge://settings) sends lookups over HTTPS to a provider you choose. Microsoft's policy reference says the strict mode of this feature “will fail to resolve on error” instead of falling back, so in that mode a provider that does not answer breaks every name. As a test, switch the setting to your current service provider or turn it off; if it is greyed out, edge://policy shows the DnsOverHttpsMode policy that locks it.
Step 4: proxy and VPN
The “or proxy” in Microsoft's description is literal: when Windows is set to use a proxy that no longer exists, every page fails before DNS for the real site even matters. Open Settings → Network & internet → Proxy and check for a manual proxy or a setup script you do not recognise. Edge uses these system settings unless a proxy policy (listed on edge://policy) or a proxy extension overrides them. Malware and old VPN or ad-blocking tools can leave behind a proxy nobody remembers setting.
A VPN client usually pushes its own DNS servers. Disconnect it and reload: if the page opens, the VPN's resolver cannot see the name (common with split DNS in company networks), and the fix belongs in the VPN configuration.
Step 5: the hosts file
Windows reads C:\Windows\System32\drivers\etc\hosts before it asks any DNS server. A line that maps the site to 0.0.0.0, 127.0.0.1 or an address the site has since left makes it unreachable from this one computer. Search the file for the domain:
Select-String -Path C:\Windows\System32\drivers\etc\hosts -Pattern 'example.com'Remove or comment out the line (editing needs an editor started as administrator), then run ipconfig /flushdns. The hosts file guide covers editing it safely.
Step 6: reset Winsock and TCP/IP
When nothing loads in any program and the steps above changed nothing, reset the network stack. These are the commands Microsoft's Wi-Fi troubleshooting article lists, in its order. Run them in Command Prompt as administrator, then restart Windows before you test again:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdnsnetsh winsock reset returns the Winsock catalog to a clean state and removes layered service providers, the hooks that VPN and security software install.
What about the TCP Fast Open fix?
Many older guides tell you to untick Enable TCP Fast Open in about:flags. Older versions of Edge had that switch: Microsoft's Edge team introduced it behind about:flags in the EdgeHTML engine in 2016, and that Edge reached the end of support in March 2021. Today's Edge is built on Chromium, and Chromium's own list of browser flags (flag-metadata.json and about_flags.cc on the main branch, read on 11 November 2026) has no TCP Fast Open entry. If edge://flags on your machine shows no such switch either, there is nothing to turn off; spend the time on the DNS steps above.
If it is your own domain
When visitors report the error for your site from different networks, the problem is in the domain's DNS, not on their computers. Check, in this order:
- Is there an address record?
nslookup -type=a example.comandnslookup -type=a www.example.com. Thewwwname is a separate record, and forgetting it is the most common gap. - Do the nameservers match?
nslookup -type=ns example.commust list the servers where you edited the zone. Records added at the old DNS host after a nameserver change are never seen; see what nameservers are. - Is your own DNS server up? If the zone is served from a VPS of yours, a stopped DNS service or a firewall that blocks port 53 makes every lookup fail, and every visitor gets this error.
A web server that is down shows up differently. If the name resolves but the VPS behind it is stopped, firewalled or overloaded, browsers report a timeout or a refused connection instead; that path is covered in ERR_CONNECTION_TIMED_OUT.
Frequently asked
What does INET_E_RESOURCE_NOT_FOUND mean?
It is an Internet Explorer networking error, code 0x800C0005, which Microsoft describes as "The server or proxy was not found." In practice the host name in the address did not resolve in DNS, or Windows is set to use a proxy that cannot be reached. The old EdgeHTML-based Edge showed it on its error page.
How do I fix INET_E_RESOURCE_NOT_FOUND?
Check the address for typos, then run nslookup with the domain to see whether DNS returns an address. Run ipconfig /flushdns, try another DNS server such as 1.1.1.1, and check the proxy settings and the hosts file. If nothing loads in any program, reset the network stack with netsh winsock reset and netsh int ip reset, then restart.
How do I disable TCP Fast Open in Edge?
Older versions of Edge, built on EdgeHTML, had an Enable TCP Fast Open switch in about:flags; that Edge reached end of support on 9 March 2021. Current Edge is built on Chromium, whose own flag list has no TCP Fast Open entry. If edge://flags shows no such switch, there is nothing to turn off, so work through the DNS, proxy and hosts file checks instead.
Why do visitors get INET_E_RESOURCE_NOT_FOUND on my website?
Because the domain does not resolve for them. Check that the domain and the www name both have an address record, that nslookup -type=ns shows the nameservers where you edited the records, and that your own DNS server answers if you run one. A web server that is down produces a timeout or refused connection instead.