[Fwd: Important ICANN Notice Regarding Your Domain Name(s)]
Is this a GoDaddy specific thing? I've owned and/or managed an untold number domain names since 1995 and never seen a notification of this sort before (primary registrar to this date was Gandi.net, and before that Network Solutions back in the bad old days). Regards, Thomas Leavitt -------- Original Message -------- Subject: Important ICANN Notice Regarding Your Domain Name(s) Date: Wed, 4 Oct 2006 13:36:13 -0700 From: <icann@securepaynet.net> To: <bofh@godmoma.com> ***************************************** Important ICANN Notice Regarding Your Domain Name(s) ***************************************** Dear B OFH, It's that time of year again. ICANN (the Internet Corporation for Assigned Names and Numbers) annually requires that all accredited registrars ask their domain administrators/registrants to review domain name contact data, and make any changes necessary to ensure accuracy. To review/update your contact data, simply: + Go to http://www.securepaynet.net/gdshop/rhp/default.asp?prog_id=godmomasforge&isc=ICANN06b + Click on the "ICANN" text link at the top left side of the page + You will be taken to a landing page and asked to enter your Domain Information key: + Enter your key and click "Go." Next, simply review the contact information for each domain name. To make a correction, log in to "My Account" with your customer number or log in name and password. Click "Manage Domains" and then "Contacts." If you find that your domain contact data is accurate, there's no need to take action. If, however, your domain contact information is inaccurate, you must correct it. (Under ICANN rules and the terms of your registration agreement, providing false contact information can be grounds for domain name cancellation.) To review the ICANN policy, visit: http://www.icann.org/registrars/wdrp.htm Should you have any questions, please email us at mailto:support@secureserver.net or call our customer support line at (480) 624-2500. Thanks for your attention and thank you for being a Godmoma's Forge, LLC customer. Sincerely, Godmoma's Forge, LLC If you are the domain administrator of more than one Godmoma's Forge, LLC domain account, you may receive this notice multiple times. --------------------------------------------------------------------------------------------- Copyright 2006 Godmoma's Forge, LLC. All rights reserved.
On Wed, 2006-10-04 at 14:27 -0700, Thomas Leavitt wrote:
Is this a GoDaddy specific thing? I've owned and/or managed an untold number domain names since 1995 and never seen a notification of this sort before (primary registrar to this date was Gandi.net, and before that Network Solutions back in the bad old days).
While, of course, the message is worded a bit different, we get the same thing for our domains registered under OpenSRS also every year. Chris
On Wed, 4 Oct 2006, Chris Stone wrote:
On Wed, 2006-10-04 at 14:27 -0700, Thomas Leavitt wrote:
Is this a GoDaddy specific thing? I've owned and/or managed an untold number domain names since 1995 and never seen a notification of this sort before (primary registrar to this date was Gandi.net, and before that Network Solutions back in the bad old days).
While, of course, the message is worded a bit different, we get the same thing for our domains registered under OpenSRS also every year.
ICANN *does* have a requirement for accurate information in WHOIS and while I don't know how strongly the requirement is enforced, they *can* pull your domain registration if you don't have accurate information. That's the reason for those notifications. -- Steve Sobol, Professional Geek ** Java/VB/VC/PHP/Perl ** Linux/*BSD/Windows Apple Valley, California PGP:0xE3AE35ED It's all fun and games until someone starts a bonfire in the living room.
On 4-Oct-2006, at 19:04, Steve Sobol wrote:
ICANN *does* have a requirement for accurate information in WHOIS and while I don't know how strongly the requirement is enforced, they *can* pull your domain registration if you don't have accurate information.
While I'm not familiar with the precise enforcement mechanisms or policy, I do know of one ISP who had the delegation for their (.com) domain name unexpectedly pulled by the registry in response to a complaint about inaccurate whois information directed at ICANN. It was painful for the ISP, especially since it happened during the time that Verisign's sitefinder was live, which caused e-mail to ISP customers to be hard bounced from Verisign and people looking for their web page to be presented with a "this domain is not registered" page instead of a browser error. It's well worth avoiding, even without the additional sitefinder complications :-) Joe
Are you sure it's genuine? Those WWD domains (especially secureserver.net) account for a large fraction of the spam and phishing attempts I receive. On 10/5/06, Joe Abley <jabley@ca.afilias.info> wrote:
On 4-Oct-2006, at 19:04, Steve Sobol wrote:
ICANN *does* have a requirement for accurate information in WHOIS and while I don't know how strongly the requirement is enforced, they *can* pull your domain registration if you don't have accurate information.
While I'm not familiar with the precise enforcement mechanisms or policy, I do know of one ISP who had the delegation for their (.com) domain name unexpectedly pulled by the registry in response to a complaint about inaccurate whois information directed at ICANN.
It was painful for the ISP, especially since it happened during the time that Verisign's sitefinder was live, which caused e-mail to ISP customers to be hard bounced from Verisign and people looking for their web page to be presented with a "this domain is not registered" page instead of a browser error.
It's well worth avoiding, even without the additional sitefinder complications :-)
Joe
On Thu, 5 Oct 2006, Alexander Harrowell wrote:
Are you sure it's genuine? Those WWD domains (especially secureserver.net) account for a large fraction of the spam and phishing attempts I receive.
SecureServer.net is GoDaddy. If you have domains hosted at GoDaddy or a reseller, your customer notifications come from that domain. They also do web and email hosting, which is probably why you're seeing the abusive behavior, but they do have a working abuse desk, so if you see stuff from there, definitely report it. -- Steve Sobol, Professional Geek ** Java/VB/VC/PHP/Perl ** Linux/*BSD/Windows Apple Valley, California PGP:0xE3AE35ED It's all fun and games until someone starts a bonfire in the living room.
On Thu, 5 Oct 2006, Steve Sobol wrote:
On Thu, 5 Oct 2006, Alexander Harrowell wrote:
Are you sure it's genuine? Those WWD domains (especially secureserver.net) account for a large fraction of the spam and phishing attempts I receive.
SecureServer.net is GoDaddy.
If you have domains hosted at GoDaddy or a reseller, your customer notifications come from that domain.
Following up to myself: I understand that you can still get phishes purporting to be from them. But if you can verify that the message came from secureserver, don't write it off as a phish without doing some further checking. -- Steve Sobol, Professional Geek ** Java/VB/VC/PHP/Perl ** Linux/*BSD/Windows Apple Valley, California PGP:0xE3AE35ED It's all fun and games until someone starts a bonfire in the living room.
GoDaddy's abuse desk is not so easy to work with...I have had two different times that a whole /24 was blocked even though parts of the address space were split between different providers (and customers), but GoDaddy would hardly relent. Took over a week to get that resolved. Frank -----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Steve Sobol Sent: Thursday, October 05, 2006 10:05 AM To: Alexander Harrowell Cc: Joe Abley; Chris Stone; nanog@nanog.org Subject: Re: [Fwd: Important ICANN Notice Regarding Your Domain Name(s)] On Thu, 5 Oct 2006, Alexander Harrowell wrote:
Are you sure it's genuine? Those WWD domains (especially secureserver.net) account for a large fraction of the spam and phishing attempts I receive.
SecureServer.net is GoDaddy. If you have domains hosted at GoDaddy or a reseller, your customer notifications come from that domain. They also do web and email hosting, which is probably why you're seeing the abusive behavior, but they do have a working abuse desk, so if you see stuff from there, definitely report it. -- Steve Sobol, Professional Geek ** Java/VB/VC/PHP/Perl ** Linux/*BSD/Windows Apple Valley, California PGP:0xE3AE35ED It's all fun and games until someone starts a bonfire in the living room.
Once upon a time, Frank Bulk <frnkblk@iname.com> said:
GoDaddy's abuse desk is not so easy to work with...I have had two different times that a whole /24 was blocked even though parts of the address space were split between different providers (and customers), but GoDaddy would hardly relent. Took over a week to get that resolved.
Heh. We had an IP (of a customer's mail server) that GoDaddy blocked. They told us it had been blocked for something like 8 months (at which time it had not been assigned to any customer); we had zero complaints on record for that IP. They couldn't tell us why it was blocked or how to get the block removed. When we asked to speak with a supervisor, they told us that their supervisors didn't have phones. -- Chris Adams <cmadams@hiwaay.net> Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble.
On Fri, 6 Oct 2006, Chris Adams wrote:
Heh. We had an IP (of a customer's mail server) that GoDaddy blocked. They told us it had been blocked for something like 8 months (at which time it had not been assigned to any customer); we had zero complaints on record for that IP. They couldn't tell us why it was blocked or how to get the block removed. When we asked to speak with a supervisor, they told us that their supervisors didn't have phones.
I must be dumb, but how does a registrar 'block an ip' in a manner that affects anyone but themselves? --matt@snark.net------------------------------------------<darwin>< Moral indignation is a technique to endow the idiot with dignity. - Marshall McLuhan
On 10/7/06, Matt Ghali <matt@snark.net> wrote:
I must be dumb, but how does a registrar 'block an ip' in a manner that affects anyone but themselves?
Godaddy also hosts a sizeable number of vanity domains registered with them If you register with them you have the option of also buying NS, mail and webhosting -- Suresh Ramasubramanian (ops.lists@gmail.com)
On Wed, Oct 04, 2006 at 03:38:02PM -0600, Chris Stone wrote:
On Wed, 2006-10-04 at 14:27 -0700, Thomas Leavitt wrote:
Is this a GoDaddy specific thing? I've owned and/or managed an untold number domain names since 1995 and never seen a notification of this sort before (primary registrar to this date was Gandi.net, and before that Network Solutions back in the bad old days).
While, of course, the message is worded a bit different, we get the same thing for our domains registered under OpenSRS also every year.
I receive these sorts-of notices from our OpenSRS-based registrar numerous times a year (usually once a month, for multiple domains). It may have something to do with the fact that I refuse to comply with ICANN's mandatory regulation demanding legitimate public contact information in WHOIS records. (If someone wants to hear my reasoning, I'll be more than happy to share.) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Jeremy Chadwick wrote:
I receive these sorts-of notices from our OpenSRS-based registrar numerous times a year (usually once a month, for multiple domains). It may have something to do with the fact that I refuse to comply with ICANN's mandatory regulation demanding legitimate public contact information in WHOIS records.
This reason is almost guaranteed. I'd been watching this thread with some mild curiosity, since I have never received such a notification, for any domain. All my data is accurate (nothing is hidden, everything is there). Interesting. I had no idea that anyone ever really checked, or cared, but apparently they do. -- In April 1951, Galaxy published C.M. Kornbluth's "The Marching Morons". The intervening years have proven Kornbluth right. --Valdis Kletnieks
On Wed, Oct 04, 2006 at 05:06:16PM -0700, Etaoin Shrdlu wrote: ...
This reason is almost guaranteed. I'd been watching this thread with some mild curiosity, since I have never received such a notification, for any domain. All my data is accurate (nothing is hidden, everything is there). Interesting. I had no idea that anyone ever really checked, or cared, but apparently they do. ...
I check and care when there is a problem in that network or domain. I find it extremely frustrating when the contact people are no longer there, or never were. -- Joe Yao ----------------------------------------------------------------------- This message is not an official statement of OSIS Center policies.
On Wed, 4 Oct 2006, Etaoin Shrdlu wrote:
This reason is almost guaranteed. I'd been watching this thread with some mild curiosity, since I have never received such a notification, for any domain. All my data is accurate (nothing is hidden, everything is there). Interesting. I had no idea that anyone ever really checked, or cared, but apparently they do.
It may depend on your registrar. I get them, since I am a WildWestDomains (GoDaddy) reseller and that's where my domains are registered. TuCows/OpenSRS does it too, but I don't think there's any global requirement for the registrars to do it, and the "valid info" requirement itself is only a few years old. -- Steve Sobol, Professional Geek ** Java/VB/VC/PHP/Perl ** Linux/*BSD/Windows Apple Valley, California PGP:0xE3AE35ED It's all fun and games until someone starts a bonfire in the living room.
Steve Sobol wrote:
It may depend on your registrar. [...] I don't think there's any global requirement for the registrars to do it
Actually, there is these days: http://www.icann.org/registrars/wdrp.htm Registrars have to annually "provide" a copy of that info to the customer, although "provide" is a flexible term. In our case we prefer to provide it as an occasional "please verify your..." notice when they login to their control panel, since that avoids an annoying (and possibly misdirected) e-mail message. But if a customer doesn't login for a year, we have to send an e-mail message. -- Robert L Mathews "The trouble with doing something right the first time is that nobody appreciates how difficult it was."
On Wed, 4 Oct 2006 (16:41 -0700), Jeremy Chadwick wrote:
Date: Wed, 4 Oct 2006 16:41:21 -0700 From: Jeremy Chadwick <nanog@jdc.parodius.com> To: nanog@nanog.org Subject: Re: [Fwd: Important ICANN Notice Regarding Your Domain Name(s)]
I receive these sorts-of notices from our OpenSRS-based registrar numerous times a year (usually once a month, for multiple domains). It may have something to do with the fact that I refuse to comply with ICANN's mandatory regulation demanding legitimate public contact information in WHOIS records.
(If someone wants to hear my reasoning, I'll be more than happy to share.)
OK... I'll nibble. I don't think you get this more than anyone else because of your stance. But perhaps that will change now that you've publically declared your resistance. ;-) It's incredibly important that there be accurate contact information for a domain. If you don't want to list any one person, for a particular role, you may opt to use role accounts. Unless I've misread and misunderstood the policy, neither the contacts nor the registrant need be a natural person. Contacts can be role accounts and the registrant can certainly be a legal entity instead of an individual. Additionally, if you have privacy concerns (which I can certainly understand and respect), many Registrars offer proxy contact options for a nominal fee. - Christopher ======================
participants (14)
-
Alexander Harrowell -
Chris Adams -
Chris Stone -
Christopher Chin -
Etaoin Shrdlu -
Frank Bulk -
Jeremy Chadwick -
Joe Abley -
Joseph S D Yao -
Matt Ghali -
Robert L Mathews -
Steve Sobol -
Suresh Ramasubramanian -
Thomas Leavitt