.post
Introduced | 2012 |
---|---|
TLD type | Sponsored top-level domain |
Status | Active |
Registry | Afilias |
Sponsor | Universal Postal Union |
Intended use | UPU members, Post offices and related organizations of the Postal Sector |
Actual use | In use by UPU members |
Registration restrictions | Registrants must be approved as being members of the postal community before registering domains |
Structure | Full authentication of verification of eligible registrants with structured naming rules for second and third-level registrations. |
Documents | ICANN New sTLD RFP Application; .Post Sponsored TLD Agreement |
Dispute policies | UDRP |
Website | www.info.post |
DNSSEC | yes |
.post is a sponsored top-level domain (sTLD) available exclusively for the postal sector. .post is the first gTLD to be 100% secured by DNSSEC. .post aims to integrate the physical, financial and electronic dimensions of postal services to enable and facilitate e-post, e-finance, e-commerce and e-government services. The domain was approved by ICANN on April 8, 2005 as a sponsored TLD in the second group of new TLD applications evaluated in 2004.
Having delegated authority for .post, the Universal Postal Union (UPU) develops, implements and monitors governance rules for it. It is also responsible for attributing domain names for postal-sector stakeholders who meet the eligibility criteria.
The UPU, based in Bern, Switzerland, became the first United Nations organization to be granted the right to operate a sponsored top-level domain (sTLD) by ICANN in 2004, in the first group of new TLD applications evaluated in 2004.[1] The UPU was the only organization to pass all criteria by ICANN as a truly representative organization to sponsor a top-level domain.
In 2009, ICANN and the UPU signed an historic agreement giving the UPU managing authority over .post as a top-level domain. The agreement came about after long negotiations, public review through ICANN's public comment process, reviews within the UPU governing Councils and consideration by ICANN's Board of Directors.[2]
The sTLD was added to the IANA TLD registry August 8, 2012 when .post entered the root of the internet.[3]
Purpose
.post is a secure and trusted electronic infrastructure on the Internet to serve the needs of the global postal community in cyberspace. .post will immediately identify legitimate postal services and avoid confusion for individuals, business and stakeholders.
.post aims to integrate the physical, financial, and electronic dimensions of postal services to enable and facilitate e-post, e-finance, e-commerce and e-government services.
With .post, users will benefit from:
Security .post uses the latest Internet security. It is the first gTLD to be 100% secured by Domain Name System Security Extensions (DNSSEC), a set of codes for securing the Domain Name System (DNS), the global database system that translates a computer's fully qualified domain name into an Internet Protocol (IP) address. It is the most secure sTLD on the net right now. You can trust a .post domain is not taking you to a fake postal website.
Authentication As .post is for an exclusive community that is fully authenticated, there are strict controls on who can own a .post domain. You can be assured a .post website is managed by an organization recognized by the UPU.
Interconnectivity Using these rigorous controls, domain owners can interconnect their domains and services in a safe and trusted environment.
Interoperability Using UPU standards, the interoperability of e-services can open up new international digital services. .post is an international platform for Posts to develop new revenue and new markets using e-identification, e-commerce, e-government and e-postal services.
Authentication
To register a .post domain, you need to submit a Community ID request here.[4] Registrants must be approved as being members of the .post Sponsored Community before registering domains. .post Domain Management Policy[5]
Prior to registering a .post domain, the UPU verifies the registrant's eligibility to register a domain name and issues a .post Community ID.
Each applicant is required to provide legal proof of ownership of the string, as well as falling into 1 of 11 Registrant Groups set out by the .post Domain Management Policy, paragraph 3.3.[6]
References
- ↑ http://www.icann.org/en/about/agreements/registries/post. Missing or empty
|title=
(help) - ↑ http://www.icann.org/en/announcements/announcement-2-11dec09-en.htm. Missing or empty
|title=
(help) - ↑ http://www.iana.org/domains/root/db/post.html
- ↑ https://apply.info.post/dpms.web/Login.aspx?ReturnUrl=%2fdpms.web%2f/
- ↑ http://www.upu.int/fileadmin/documentsFiles/activities/dotPost/policyManagementDotPostEn.pdf/
- ↑ http://www.upu.int/fileadmin/documentsFiles/activities/dotPost/policyManagementDotPostEn.pdf/
External links
|