Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I deleted a site from IIS7 and even deleted its physical path. But the site is still accessible. Could anybody provide theory (caching?) and a solution to clear the IIS cache?

share|improve this question

Just a guess: maybe a copy of your files is in the Default Web Sites' (standard: C:\Inetpub\wwwroot)?

In that case, if IIS' Default Web Site is enabled it will accept all host headers and answer to requests of your deleted web site.

I would to try to stop the IIS and see if you still get the site. If you still get pages, the site is probably on a different server.

share|improve this answer

I would check IIS logfiles to verify if the site is still been served from the same server. If you have deleted the site from IIS, there is no ways the site is accessable. I would also check if there is any device in between the client and server that would have cached the pages.

share|improve this answer
And make sure that you are not seeing browser cached pages or Proxy pages as well. – Larry Smithmier Nov 7 '10 at 14:24
maybe it is something different. I deleted index.html of the first created website (was a duplicate as the mentioned above). Now I cant access the deleted domain as wanted. I don't know why every request tries to access my first created website. Need to know more theory. – user47521 Nov 7 '10 at 14:44
The reason is Default Web Site has * for Bindings and which means all IP's, so even though you deleted the site the request would still be served by the DWS as it was able to handle the requests. – Vivek Kumbhar Nov 8 '10 at 2:26
Thank you. It is something with this related. Now I have to find out why my website1 (i.e. is treated as the Default Website – user47521 Nov 8 '10 at 9:57
As an addendum, I also had the problem mentioned in that previous comment; in my case, the answer was that the website "" had no host name defined and was set up on all available IP addresses, so it was being used for requests to recently removed websites. It was easy to fix by right clicking the site, going into "Edit Bindings…," specifying an IP address and adding a host name to the http binding. – Jordan Gray Dec 17 '12 at 18:04

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.