I use: www.whois.net.
They seem to be very accurate.
Or just whoever his hosting is through, it should tell him there or they should have their own whois [www.hostdomain.com/whois]..
My bet is that the registrar has failed to do this.
Edit: a little more research: http://www.icann.org/faq/.
So the registrar is responsible for maintaining the contact information, but I'm not sure who is ultimately responsible for the maintaining the expiry info. It may be the registrar.
"Only the registrar would know exactly why it hasn't yet deleted a particular name." - seems to indicate to me that the registrar is the authority on the expiry. http://resellers.tucows.com/whois/newwhois.
Looks like the registrar is indeed the authority on the expiry, but they may have broken their ICANN accreditation agreement by not updating the registry in time...
Ideally, the Registry. But they're dependent on the registrar providing correct.
Information to begin with...
Thank you for all your help everybody.. This is a very interesting situation.
It is 100% clear to me, that Parava.net has NOT reported the domain name renewal to Verisign (.com Registry) since they renewed it nearly 2 months ago.
Here is another thing to chew on, but is how I see it works.
Process 1.) End user registers a domain name at a ICANN Accredited Registrar.
Process 2.) Registrar submits domain name fees to Verisign (.com, .net, .tv etc).
Process 3.) This info submitted also tells verisign the Creation Date, Expire Date and Domain Name Servers.
Process 4.) Domain is due up for renewal, customer pays renewal fee to Registrar.
Process 5.) Registrar submits fees to Verisign and updates to new expiry date.
Any update to DNS or expiry date is sent to Verisign for updating the zone files.
In this case, the customer paid for renewal but Parava.net did not pay verisign, so the the expiry date did not update. That's why Parava.net's whois shows 2017 and Verisign whois and zone files shows 4-18-2008 for the expired date.
Now is Parava.net just "Holding" the renewal money until just before the domain expires? Could be, but as stated above, a registrar only has 5 days to submit the payment to Verisign...
The registry data is authoritative but it is not uncommon that whois records on the registar end are out of sync..
Also, when a name expires the registrar will often make a preemptive renewal with verisign so the registry expiry date will be registrar expiry date +1 year. The discrepancy can be confusing... the registrar has up to 45 days to nullify the renewal request so they get the money back from verisign...
I should have an answer from my friend sometime next week as to what Parava.net's reason behind not sending the info/money to Verisign or whatever the registrar claims. I have all screen shots of Verisign whois and 10-domains.com whois to show the difference and verification from Verisign that the domain will expire on 4-18-2008.
I also looked at whois again at parava.net/10-domains.com and it shows Creation Date of 12/26/2007 which gives me the idea of when he most likely renewed it and seems to be around that time.
The thing is... It was first created back in 1995 as the Verisign whois shows and never dropped. This is a Gem of domain we are talking about, so that's why I am making such a stink about it, plus a friend owns it. CCCP(.)com is the domain btw...
Just saw your post that your friend's taking it up with Parava. Compared the.
Two and it's exactly what you said.
Just have to wait but consistently followup at this point...
Yep, I told him to take that approach first as it could be a clerical error or something like that. Keep in mind he renewed it 12/26/2007. A little past the 5 days allowed by ICANN. If no luck, Report it to ICANN. Then, get the EPP and transfer out to another registrar. That will solve it, but most likely be missing the $ he spent on the renewal to 2017 already.
Just another reason to use Big Registrars like Godaddy, NetSol etc...
Sounds pretty illegal to me. Reminds me of one of those american greed tv shows where the stock broker tells everyone their money is safe and invested wisely printing out fake reports to keep them on board...
LOL, I think it is funny that your username is"broker" LOL.
(didn't wan't to hijack your thread yofie!!).
Yes, I agree.... Why did I say that. It was a long day yesterday.
Moniker, Godaddy, eNom etc...
That's on initial registrations, not renewals.
Verisign will auto-renew at the end of a registration term, and not charge the registrar unless the name is renewed within 30 days.
Parava may simply be holding the multi-year payment until the end of the current term and then applying it when the current registry term comes up for renewal - i.e. submitting all renewals in batches when due, instead of paying in advance...
I just bought a Register.com name in the drops a few weeks ago.
Domaintools whois.sc shows.
Top section under Registry Data.
^ Which looks correct.
Below the whois record shows.
Created on..............: Wed, Dec 27, 2006.
Expires on..............: Tue, Feb 19, 2019 << 2019 ?????.
It shows the same using allwhois.com.
Any ideas ?
I also has some unsynchronized whois records between the registrar and registry before that were a different problem. In my case, the registrar accepted payment and updates and forwarded to the registry. However, the registry rejected it because a field such as state or country was left blank in the whois record. Once support figured this out, I completed the blank fields in the whois data and the record was accepted into the registry database.
As JB said, it may also just be the registrar working the float on the cash. If it isn't due for renewal for several months and they can earn interest on holding the money to the last minute, they make more money for the same transaction. Not really ethical since they didn't update your expiration record, but plausible...
It's good that your friend realized the domain does not show the renewal at the Registry.
Whether by intent or omission, if the Registrar does not report the renewal then the domain will go through the deletion process after the current expiration date.
This could (and has) easily happen if you own lots of domains.
Are are not running a tight ship.
I noticed it, but I have been watching it for sometime now. He just kept telling me he renewed it and I kept asking.... Are you sure? Then I looked into it deeper and noticed the registrar never sent in the renewal to the registry.
We should find out more tomorrow after contacting the registrar. Thank you for the heads up John. Maybe ICANN needs to place another time limit on renewals as well. No reason for them to "Hold" the money and renew when they want!.
If I renew a domain, I want it renewed via the registry as well...
Originally Posted by tricolorro.
It's good that your friend realized the domain does not show the renewal at the Registry..
Your friend is lucky he has you watching his (domain) back.
DomainTools has a free domain monitoring service.
You have to create an account but it's otherwise free.
If any changes are made to the status of the domain(s) you are monitoring,.
You will be sent an email.
There is usually a couple of days lag time, but it's better than nothing.
Go here: http://www.domaintools.com/monitor/.
Thats terrible - you could miss renewing it or even worse - they could have got the expiry date shorter and it could have dropped before natural date...
I've run into the same problem at various registrars both big and small - sync problems most often are not due to "floating" the money or whatnot, but rather simply due to poorly coded renewal scripts that sometime flake out and don't update the registry; new registrations are sometimes affected in a similar way - person regs a new domain, but the registry doesn't know that, and then sometime later the "registrant" discovers someone else has their domain despite getting renewal notices from their registrar - the .com/.net thin registry model is a mess, but I digress.
Just email the registrar (in your friend's situation Parava; http://www.internic.net/registrars/registrar-94.html ) to fix the registry date.
Often no need to go in much detail beyond explaining the registrar and registry expiration dates don't match.
Most often registrars with sync problems have already received numerous similar trouble-tickets in the past, and thus they already understand the issue and know how to fix it.
Using domain monitoring services, such as DomainTools, greatly reduces the risk of unknowingly losing domains - on a related note, using one's own unique name servers and monitoring those (a premium service at DomainTools) adds another level of protection for those holding numerous domains - many registrars automatically update the DNS to their own immediately upon expiration.