Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

WhoIs lookup shows him as the domain owner

Registrant Contact: ThisWebHost Jules Robinson ()

Fax: South Building Upper Farm Basingstoke, HAMPSHIRE RG23 8PE GB

Administrative Contact: ThisWebHost Jules Robinson (domains@thiswebhost.com) +1.5555555555 Fax +1.5555555555 South Building Upper Farm Basingstoke, HAMPSHIRE RG23 8PE GB

Technical Contact: ThisWebHost Jules Robinson (domains@thiswebhost.com) +1.5555555555 Fax +1.5555555555 South Building Upper Farm Basingstoke, HAMPSHIRE RG23 8PE GB

Also he appears to be using a fake phone number on the WhoIs, am I right in thinking you're not allowed to do that?



Technically you are not allowed to provide fake information, although you may use an identity proxy as long as they provide the means to contact you in case of a dispute. In reality, enforcement of valid identity information is essentially non-existent.


I'm personally aware of at least one incident in which someone who had their domain revoked for 'joke' contact details in the whois db. Then again, istr they did piss off an old-school sysadmin (in the a.s.r sense).


As a Brit, it doesn't surprise me at the British address here. I work primarily with US companies but the most obnoxious service I get tends to be from the British ones. An idea of "honor above money" seems to be more prevalent here in the UK, whereas in the US it seems you're more likely to just get ignored.


It's against the rules to use false info so feel free to email contact@namecheap.com with that little bit of info.


[deleted]


What?!? This information was on the PUBLIC WhoIs database, it's avaliable to anyone. I did this to show the contact information for the site, anyone could have done this but I did it so no-one else had to.

http://www.whois.net/whois/thiswebhost.com


[deleted]


There was no intention to track him down, someone posted a comment asking to check on the WhoIs to find out the owner. I do not want to figure out their phone number, I merely noticed it's clearly incorrect (against the ICANN T's & C's)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: