.ws Whois?

[Name Trader]

Looking up .ws domains is a real PITA. The registry restricts you to just 12 slow whois lookup per day. Is there a Registrar whois lookup which gets around these limitations?

 

[N-A]

It's not bulk, but it should get you past 12 searches per day (and it's a live record).

https://gwhois.org/

 

[Kate]

Perhaps you could get round the limitation by querying the whois server from the command line (on port 43):
whois.website.ws

 

[Domainstore]

dynadot, I guess

 

[Name Trader]

Thanks David for reminding me about gwhois.org. I've used it before for other whois lookups. I'd forgotten about it because I never bookmarked anything and just had open windows with lots of tabs open, and then relied on Session Manager to work properly, which invariably didn't do, with so many open windows and tabs. But I just spent the best part of today, converting all my tabs to bookmarks (in a logical fashion, of course). I'm going to go ahead and bookmark gwhois, right now

Thanks Domainstore. This is what I actually used because most of my domains are with Dynadot, so I was able to interpret whether I still owned the domain or not.

I also found this whois, http://samoanic.ws/whois.dhtml for .ws websites. It was able to fill in the gaps where I had any doubt using Dynadot. It was lightweight and quick.

Although I was primarily looking for a whois port lookup that I could change the .ws whois port lookup to.

 

[Hypersot]

Maybe a stupid question but,
is there a way to use proxies for whois lookups?

 

[Name Trader]

I think it's possible, but I have never explored that route.

 

[Hypersot]

no matter what proxy I use they all time out if I use them for whois
despite working fine with port80 it seems they have problems when used via port43

funny thing is that, no matter how hard I have looked on the net, I have found no info on that subject

 

[Name Trader]

Perhaps all the proxies only work on Port 80?

 

[Hypersot]

Yeah, that's what I also thought but then again, I'm not sure