Synthetic
06-18-2002, 06:43 PM
The WHOIS information of one of my domains at Stargate.com has not been appearing for the past week.
What could be the problem?
What could be the problem?
![]() | View Full Version : Problem viewing WHOIS info... Synthetic 06-18-2002, 06:43 PM The WHOIS information of one of my domains at Stargate.com has not been appearing for the past week. What could be the problem? Axel Teflon 06-18-2002, 07:07 PM Contact support at Stargate.com. I can;t say I've came across this kind thing before.. :confused: The Prohacker 06-18-2002, 07:45 PM Stargate's outside whois hasn't been working, only their internal one has... Goto their site and at the bottom there should be a whois link... Synthetic 06-18-2002, 07:53 PM Ugh! Now I can't even access their website... Axel Teflon 06-18-2002, 08:02 PM I can access their site ok, must be your computer... TheOp 06-18-2002, 08:57 PM I can access the stargateinc.com port 43 whois and the web based. no problems. RotoHost 06-19-2002, 09:21 AM I've had problems with using the WHOIS for Stargate for as long as I can remember. Sometimes it works..sometime not. It's a crapshoot everytime. I use SamSpade, however, for WHOIS checks so that may be a factor. As far as actually registering domains, no problems at all with Stargate. StarGate 06-19-2002, 07:46 PM If this is a .biz domain then it is probably not their fault. I get errors from the NeuLevel WhoIs all the time :( Jorge 06-19-2002, 08:39 PM same story here. I had to wait about 14 days to "propagate" through their whois. Their whois does not usually work on third party servers, and sometimes time-outs on their site as well. Except this bug, friendly service. TheOp 06-19-2002, 09:20 PM most registrars have started to block third party servers accessing whois due to abuse and data mining. I was told by Stargate that they have blocking technology in place for excessive requests. thewitt 06-19-2002, 10:05 PM Stargate's whois is notorious for being unavailable on port 43 - regardless of how often you query it. They are in breach of their ICANN contract requirements. Complaints have been logged with ICANN, however since ICANN is toothless these days, little will result. -t TheOp 06-19-2002, 11:10 PM Actually ICANN's agreement states that a port 43 must be offered at the registrars expense. It does not state that an SLA must be offered or that it has to be up a specific % of time. I don't have any difficulty accessing their whois via port 43. thewitt 06-20-2002, 01:39 PM A dysfunctional Port 43 whois is not meeting the spirit of the contract. I don't need an SLA to know that no service on port 43 is not acceptable. -t |