Public Interest Registry

From Infogalactic: the planetary knowledge core
(Redirected from .ong)
Jump to: navigation, search
Public Interest Registry
Non-profit
Industry Internet, Domain registry
Founded 2002 in Reston, Virginia
Key people
Brian Cute, David Maher, Maarten Botterman, Marc Saitta, Paul Diaz, Tom Correia, Kim Van Wyngaardt, Tony Connor, Lauren Price, Dave Stewart, Elizabeth Finberg, Hal Lubsen (Afilias), Ram Mohan (Afilias)
Website pir.org

The Public Interest Registry is a Reston, Virginia-based not-for-profit created by the Internet Society (ISOC) in 2002 to manage the .ORG top-level domain. It took over operation of .ORG in January 2003 and launched the .NGO and .ONG domain names in March 2015.[1] The organization is involved in internet policy, education and security issues, like the Domain Name System Security Extensions (DNSSEC) protocol, domain tasting, DNS filtering and internet adoption in third world countries.

History

The Internet Corporation for Assigned Names and Numbers (ICANN) circulated a request for proposals in May 2002 for a new organization to manage the .ORG domain. The Internet Society (ISOC) put forth one of eleven proposals ICANN received.[2][3] ISOC won an endorsement within ICANN and was recommended to the selection committee in a preliminary report.[4] At a public ICANN meeting in Bucharest in 2002, ISOC CEO Lynn St. Amour and Afilias CTO Ram Mohan presented ISOC's proposal to manage the .ORG registry.[5][6] The proposal included the creation of a separate entity, called the Public Interest Registry, to oversee the .ORG domain. Its board of directors is appointed by ISOC. Afilias was selected as the back-end technical provider for .ORG under contract with the Public Interest Registry.[7][8] The largest domain transfer in history[9] occurred on January 1, 2003, when ICANN had VeriSign delegate 2.6 million domains to the Public Interest Registry.[10] An Internet Society Vice President, David Maher, became the chairman.[8] The following month, Ed Viltz became the organization’s first CEO.[11]

On June 23, 2010, The Public Interest Registry implemented the Domain Name System Security Extensions (DNSSEC) protocol for .ORG.[12] DNSSEC is intended to prevent cache poisoning attacks by making sure internet users arrive at the URL they intended.[13][14] The implementation began in test environments in mid-2009.[15] The protocol was [13] implemented by PIR's technical partner Afilias[16] during the tenure of former CEO, Alexa Raad, who played a role in creating the DNSSEC Industry Coalition. Raad resigned from the Public Interest Registry in late 2010.[17] The non-profit had an interim CEO, until it recruited former Afilias executive Brian Cute as its third chief executive officer on January 14, 2011.[18]

After the 2011 tsunami in Japan, the Public Interest Registry waived renewal fees for Japan-based .ORG domains to prevent domains from expiring due to intermittent internet access.[19]

Domains

.ORG

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The number of .ORG domains registered with the Public Interest Registry

.ORG is the third largest generic top-level domain of the Domain Name System used in the internet. .ORG domains have been registered by the Public Interest Registry since 2003. Craigslist.org and Wikipedia.org are among the more popular .ORG users.[20] Since 2009, the Public Interest Registry has published a bi-annual report called “The Dashboard”[21] on the number of registered .ORG domains. There were more than 8 million registered .ORGs in 2009,[20] 8.8 million in 2010,[22] and 9.6 million in 2011.[23] The Public Interest Registry registered the ten millionth .ORG domain in June, 2012.[24] In June 2015 there were 10.5 million .ORG domains registered.[25]

The Public Interest Registry promotes and publicizes the .ORG domain. While .ORG is an open domain, the Public Interest Registry wants more people to view .ORG as a domain for communities and entities that serve the public good, rather than being perceived as directed to non-profits.[26] In 2010, the Public Interest Registry launched “WhyIChose.org” as part of campaign to promote the .ORG domain extension.[27]

It conducted a survey of consumers in 2011 on how domain names are perceived by internet users. The survey found that 81 percent of Americans still rely on an organization’s website before Twitter or Facebook. It also suggested .ORG sites were seen as more trustworthy.[9] Respondents were more likely to turn to .ORG websites in a crisis, more likely to post content on .ORG sites and to trust information on a .ORG domain. It also found that younger age groups were almost twice as likely to register a .ORG as Americans age 55-64.[28]

In July 2015, Public Interest Registry marked the 30th anniversary of the first .ORG registration, and launched a website featuring a timeline of .ORG registrations from 1985 to 2015 and a gallery of .ORG websites.[29] The first .ORG domain name to be registered was mitre.org.[30]

.NGO

In June 2011, ICANN expanded the internet’s naming system to allow applications for new top-level domain names.[31] The Public Interest Registry declared publicly an interest in the .NGO domain in August 2011[32] and applied for it in May 2012.[33] It also applied for an equivalent domain, .ONG, which stands for “Organisation Non Gouvernementale” in French, and is also recognizable in Spanish, Italian and other romance languages.[34][35] Unlike the .ORG domain, .NGO will require validation of the registrant’s non-governmental status.[31] Non-governmental organizations told the Public Interest Registry they needed a closed domain[36] that validated the legitimacy of websites accepting online donations to avoid fraud.[36][37] The Public Interest Registry plans to use the funds from selling .NGO domains[38] to develop an “NGO Community Program” to reach out to NGOs in developing nations.[31] It also intends to create a directory service of NGOs to support their SEO and visibility, and develop a closed community for NGOs to learn from each other.[38] The new domains have been publicly available since May 6, 2015.

Advocacy

The Public Interest Registry often supports ICANN on policy and privacy issues on the internet. In 2003, The Public Interest Registry wrote a letter to ICANN supporting its opposition of wildcard redirection services that automatically redirect internet users to correct spelling errors and typos. The letter supported ICANN’s request for VeriSign to voluntarily suspend a DNS wildcard service called Site Finder and asked ICANN to make a policy against similar services across the internet.[39] The Public Interest Registry and other organizations opposed the move by VeriSign, because automatic redirects may affect spam filters and mail servers that rely on error messages from non-existent domains.[40]

The Public Interest Registry reduced domain tasting by charging fees to registrars that cancel 90 percent of their domains in less than five days. In 2007, ICANN used that as a model for a similar proposal to curb domain tasting through non-refundable fees.[41] The Public Interest Registry supported ICANN’s expansion of top-level domain names. The CEO, Brian Cute, commented that internet users will still gravitate towards established domain names, but new domains will target specific communities.[42] The Public Interest Registry has also urged ICANN to address privacy implications of the WHOIS database.[43][44] The organization is critical of the security of DNS filtering techniques[9] and supports the DNSSEC protocol.[27] It also shuts down .ORG-based phishing scams.[9]

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. 8.0 8.1 Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 9.2 9.3 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.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. 20.0 20.1 Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. 27.0 27.1 Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. 31.0 31.1 31.2 Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. 36.0 36.1 Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. 38.0 38.1 Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.

External links