Anyone able to access who.is website?

I often use <http://who.is> as a convenient domain lookup tool.

But it hasn't worked for me for a week or two, though according to
<http://isup.me/who.is> it's working.

I've tried alternate browsers, disabled adblocker, I don't use a hosts
file for blocking.

Traceroute seems to get to New York, then Washington, then give up

C:\WINDOWS\system32>tracert -4 who.is

Tracing route to who.is [174.36.202.235]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms firewall.lan [192.168.1.1]
2 17 ms 17 ms 17 ms lo0.10.central10.pcl-bng01.plus.net
[195.166.130.138]
3 18 ms 17 ms 17 ms irb.10.PCL-CR01.plus.net [84.93.249.81]
4 18 ms 18 ms 18 ms ae1.ptw-cr01.plus.net [195.166.129.0]
5 20 ms 17 ms 17 ms ae2.ptw-cr02.plus.net [195.166.129.5]
6 * * * Request timed out.
7 86 ms 86 ms 85 ms ae1.bbr02.tl01.nyc01.networklayer.com
[50.97.18.204]
8 86 ms 86 ms 86 ms ae7.bbr01.tl01.nyc01.networklayer.com
[173.192.18.176]
9 92 ms 91 ms 91 ms ae1.bbr01.eq01.wdc02.networklayer.com
[173.192.18.156]
10 92 ms 92 ms 92 ms ae0.dar01.wdc01.networklayer.com
[173.192.18.197]
11 92 ms 93 ms 93 ms po1.fcr03.sr02.wdc01.networklayer.com
[208.43.118.157]
12 * * * Request timed out.

Anyone else (either with Plusnet as I am, or with another ISP) able to
access it?

 

Works find for me - both the initial page and then looking up bbc.co.uk -
and I'm with Plusnet.

 

NY says...

I'm with BT and it works fine using Chrome browser with AdBlock plus
enabled.

 

Worked perfectly here, via Zen.

 

Why use the web to do something which is trivial from the command line?

 

What are you expecting to get and how do you do who-is (or the
equeivalent) from the command line?

 

because windows doesn't come with a whois.exe by default, and I don't
happen to have one installed ...

 

Thanks, does a traceroute reach the server for you? Does it resolve to
the same IP address as for me (174.36.202.235)?

I'm on FTTC, but AFAIK using baby jumbo packets between modem and router
to get a "normal" 1500 byte MTU, struggling to think what else might be
going on ...

 

I just type 'whois'!

The output is all the same data that a web whois produces as far as I
know.

 

Works for me.

Traceroute stops at the same place as yours, but that appears to
be the last-but-one host, so it's probably not an error:

$ traceroute who.is
traceroute to who.is (174.36.202.235), 64 hops max, 52 byte packets
[...]
10 po2.fcr03.sr02.wdc01.networklayer.com (208.43.118.159) 91.685 ms 92.628 ms
po1.fcr03.sr02.wdc01.networklayer.com (208.43.118.157) 91.746 ms

$ ping -m 11 who.is
PING who.is (174.36.202.235): 56 data bytes
64 bytes from 174.36.202.235: icmp_seq=0 ttl=53 time=91.981 ms

$ ping -m 10 who.is
PING who.is (174.36.202.235): 56 data bytes
36 bytes from po2.fcr03.sr02.wdc01.networklayer.com (208.43.118.159): Time to live exceeded

Note that the web page redirects to https:

$ telnet who.is 80
Trying 174.36.202.235...
Connected to who.is.
Escape character is '^]'.
GET / HTTP/1.0

HTTP/1.1 301 Moved Permanently
Date: Sun, 15 Nov 2015 18:32:18 GMT
Server: Apache
Location: https://who.is/
[...]

What happens if you try the https version directly?

-- Richard

 

ping never responds for me (what is the implication of your
mark10/mark11 pings behaving differently?)

still browser timeout

odd.

 

Time to live exceeded[/QUOTE]

The -m argument specifies the TTL (Time To Live) of the packets.
It gets there with a TTL of 11 but not 10, so it is 11 hops away.
The last host in my traceroute was 10 hops away.

Yes.

You could try using a public web proxy, but there's clearly something
that needs fixing...

-- Richard

 

I suspect this is related to a problem we've been having from the office
recently.

Seems some activity on the network has blocked some of our IP's from
accessing the site in question.

If you don't have a static IP, try a disconnect/reconnect and see if
that helps.

FWIW, I can access the site assigned an IP from 80.229.0.0/16

 

unfortunately I have fixed addresses in the 84.92.25 range, thanks
though, I'll see if it gets unblocked eventually ...

 

Fine here from 87.113.164.3 - which is of course one of yours.

Andy

 

Or use a public web proxy.

-- Richard