<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On 20 Feb 2014, at 8:48 pm, McTim <<a href="mailto:mctimconsulting@gmail.com">mctimconsulting@gmail.com</a>> wrote:<br><div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi David,<div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 20, 2014 at 7:09 AM, David Cake <span dir="ltr"><<a href="mailto:dave@difference.com.au" target="_blank">dave@difference.com.au</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><br>
On 20 Feb 2014, at 12:52 am, Jefsey <<a href="mailto:jefsey@jefsey.com">jefsey@jefsey.com</a>> wrote:<br>
<br>
> At 01:24 19/02/2014, Don Blumenthal wrote:<br>
</div><div class="">>> Assuming that ICE refers to US Immigration and Customs Enforcement,<br>
>> domain-related court orders that it has obtained from judges generally<br>
</div><div class="">>> contain redirects at the name server level<br>
><br>
> Hosts can be accessed by their IP.<br>
<br>
</div> In theory. In practice, it would likely require specialised browsing software to simultaneously access a server via its IP (not using the DNS) while passing the server name (expressed as a URL containing a domain name) via http, so that the multi-homed web browser knew which of the multiple hosted web sites to serve. Housing multiple web sites on the same IP address isn't always done, but it is so common as to be ubiquitous. I'm not aware of a way to do this using a common browser.<br>
</blockquote><div><br></div><div><br></div><div>I just tested this, as it has always worked for me in the past. Doing a "dig" for the A record of <a href="http://icann.org/">icann.org</a> gave me 176.9.131.126 (i had spelled it <a href="http://ivann.org/">ivann.org</a>, but put it in the browser bar any way and got a website in german!</div>
<div><br></div><div><a href="http://176.9.131.126/de/">http://176.9.131.126/de/</a><br></div><div><br></div><div>so in practice it works for me using Chrome.</div></div></div></div></blockquote><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Oh, using the IP address will generally get you *something*, and if the server at that IP# is dedicated to that site, it may well be something useful and related to what you expected. </div><div><span class="Apple-tab-span" style="white-space:pre"> </span>But it is common for those using cheap commercial web hosting to have many websites hosted at the same IP address, quite likely unrelated except via choice of hosting provider, and decide which is served based on the HTTP Request Host header. There is generally a default response that will be served if the web server gets a request without a Host header it recognises (which is probably </div><div><span class="Apple-tab-span" style="white-space:pre"> </span>While It is in theory possible to separate the process of DNS resolution and the creation of the HTTP request such that you can do the former directly via IP address, I'm not aware of any browser that does this. </div><div><span class="Apple-tab-span" style="white-space:pre"> </span>So, I'm just pointing out that many, though not all, websites are not practically accessed by IP address. If a commercial web host had, say, 100+ sites on it, only one of those sites at most would be practically accessible via direct IP address. So while removing sites from the DNS is in theory something that can be worked around, it practice it is often considerably more complex than just accessing it via IP address. </div><div><span class="Apple-tab-span" style="white-space:pre"> </span></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>David</div></body></html>