Domain privacy

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Domain privacy is a service offered by a number of domain name registrars. A user buys privacy from the company, who in turn replaces the user's info in the WHOIS with the info of a forwarding service (for email and sometimes postal mail, done by a proxy server).

Level of anonymity

  • Personal information is typically collected by these registrars to provide the service. Some registrars take little persuasion to release so-called 'private' information to the world, requiring only a phone request or cease and desist letter.[1][2][3]
  • Others[who?], however, treat privacy more seriously, and host domain names offshore, even using e-gold or money orders in transactions so that the registrar has no knowledge of the domain name owner's personal information in the first place (which would otherwise be transmitted along with credit card transactions). It is debatable whether or not this practice is at odds with the domain registration requirement of the Internet Corporation for Assigned Names and Numbers (ICANN).

Privacy by default

Note that some domain extensions have privacy caveats:

  • .at, .co.at, .or.at: Since May 21, 2010, contact data (defined as phone number, fax number, e-mail address) is hidden by the registrar and must be explicitly made public.[4]
  • .ca: Since June 10, 2008, the Canadian Internet Registration Authority no longer posts registration details of individuals associated with .ca domains.
  • .de: Owner and technical contact must show their postal addresses. Phone number and e-mail address do not have to be made public.[5]
  • .eu: If the registrant is a natural person, only the e-mail address is shown in the public whois records unless specified otherwise.[6]
  • .gr: No information about the owner is disclosed.
  • .is: May hide address and phone number.
  • .nl: Since January 12, 2010, registrant postal addresses are no longer publicly available.[7][8]
  • .us: In March 2005, the National Telecommunications and Information Administration (NTIA) said that owners of .us domains will not have the option of keeping their information private, and that it must be made public.
  • .uk: Nominet, the guardian of UK domain namespace, provide inclusive domain privacy tools on their extensions (.co.uk, .me.uk etc.), providing that the registrant is not trading from the domain name.[9]

Implications

The Internet Corporation for Assigned Names and Numbers (ICANN) broadly requires that the mailing address, phone number and e-mail address of those owning or administrating a domain name be made publicly available through the "WHOIS" directories. However, that policy enables spammers, direct marketers, identity thieves, or other attackers to use the directory for personal information about those people. Although ICANN has been exploring changing WHOIS to enable greater privacy, there is a lack of consensus among major stakeholders as to what type of change should be made.[10] However, with the offer of private registration from many registrars, some of the risk has been mitigated.

Litigation

With "private registration", the private registration service can be the legal owner of the domain. This has occasionally resulted in legal problems. Ownership of a domain name is given by the organization name of the owner contact in the domain's Whois record. There are typically four contact positions in a domain's Whois record, Owner, Administrator, Billing, and Technical. Some registrars will not shield the Owner organization name in order to protect the ownership of the domain name.

Ownership of domains held by a privacy service was also an issue in the RegisterFly case, in which a registrar effectively ceased operations and then went bankrupt. Customers encountered serious difficulties in regaining control of the domains involved.[citation needed][11] ICANN has since remedied that situation by requiring all accredited registrars maintain their customers' contact data in escrow. In the event a registrar loses its accreditation, gTLD domains along with the escrowed contact data will be transferred to another accredited registrar.

There have been several lawsuits against NameCheap, Inc. for its role as owner/registrant. See http://randazza.files.wordpress.com/2009/05/solid-host-v-namecheap.pdf and also in Silverstein v. Alivemax, et al. Los Angeles Superior Court Case Number BC480994.

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.

External links

  • Lua error in package.lua at line 80: module 'strict' not found.