DOCSLIB.ORG

Ftld Registrar - Frequently Asked Questions (FAQ)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Ftld Registrar - Frequently Asked Questions (FAQ) fTLD Registrar - Frequently Asked Questions (FAQ) How do I become an fTLD registrar? See the information at BECOME AN fTLD REGISTRAR for details on the process. fTLD Registry System Who operates the fTLD Registry System? Verisign is the Registry Service Provider and Symantec is the Verification Agent. Is there a web interface available for registrars to process registrations for fTLD? No, fTLD registration is not supported by a web interface to EPP. Registration is initially first-come, first-served, but what is used to determine which registration arrived first? The registration that arrives at the EPP editor first and is put into pending create will lock the domain name until verification is either approved or rejected. Can eligible registrants register any domain name(s) they want? Any domain name(s) that corresponds to the registrant’s trademarks, trade names or service marks can be registered during General Availability. For guidance on selecting domains, please see the fTLD Name Selection Policies and their Implementation Guidelines here. Are there any differences between the “corresponds to” rule for domain names in .BANK and .INSURANCE? Yes, in .INSURANCE domain names must correspond to a trademark, trade name or service mark of the Applicant in bona fide use for the offering of goods or services, or provision of information, in the jurisdiction where the registrant is licensed, approved or certified to conduct business. Please consult section 3.1 of the .INSURANCE Name Selection Policy for specific information. When does the five-day (5) Add Grace Period start since domain names are put into a pending create status when initially registered? The five-day (5) Add Grace Period starts when the domain name has been put in pending create status by Verisign. Can a registrar delete a domain name after the five-day (5) Add Grace Period? Yes, a domain name can be deleted after the Add Grace Period. However, the registrar would not receive any refund from Verisign. Are there specific instances where an exemption will not be given to registrars for the AGP (Add Grace Period) Limits Policy? Exemptions will not be made under the AGP Limits Policy if the registrant submits multiple domain names for registration and verification and then deletes all but one domain name during the Add Grace Period. Registrars should discourage the potential use of this process by registrants. Is Registry Lock available for domain names? No, Verisign’s Registry Lock service is currently unavailable for domain names. When Verisign is ready to support it, all approved registrars will be notified of its availability. How is the registrar notified when a registration has been approved or rejected? When fTLD confirms (either approval or rejection) the verification order, Symantec will generate an email to the registrar and registrant unless the registrar has turned off the notification feature. When fTLD confirms the Verisign registration, an EPP polling message to update the status of the transaction will be generated. How is the registrant notified when their registration has been approved or rejected? Once fTLD confirms the verification performed by Symantec on the Verisign system, the registrar should generate their standard message to the registrant confirming that the registration has been approved or rejected based on the EPP message from Verisign. When a domain name is approved or rejected on Symantec, an email on that action is also sent to the registrar and registrant unless the registrar has turned that feature off as described in the Symantec Verification Guide for .BANK and Symantec Verification Guide for .INSURANCE (“Symantec Verification Guides”). Can a domain name in the pending create status be registered by someone else? No, a domain name in the pending create status is not available for registration and will return a “domain is not available” message for any EPP inquiries on the domain name. If a registrar submits 15 domain names for verification in one order and five of the domain names are not approved, will all 15 domain names be rejected? No, each domain name is verified separately and the ten that pass all validations including the relevant fTLD Name Selection Policy will be approved and the other five will be rejected. If all of the domain names are rejected or the registrant verification fails then the entire order will be rejected with an order status of Cancelled. If any of the domains are approved, then the order status will be set to Completed. The status of each domain will be reflected in the Domain Information area as either Rejected or Approved. Does fTLD accept all single and two-character names for registration? fTLD has made single-character and most two-character names available in .BANK and .INSURANCE (except certain two-letter domains still reserved by ICANN). These previously reserved names are available on first-come, first-served basis subject to fTLD’s Registrant Eligibility and Name Selection Policies. As these names are deemed premium, they are subject to a higher initial and renewal registration fee. For more information about the specific two-character names that are available please see the information here. Are there any premium names in .BANK and .INSURANCE? Yes, the premium names in .BANK and ,INSURANCE are currently all single-character and certain two- letter names as detailed here. 2 Are there any special requirements by Verisign or Symantec for registrars to be able to offer fTLD Premium Names? Yes, registrars need to select the appropriate option in Exhibit A of Verisign’s Platform Access Order Form for each fTLD domain supported to be able to sell fTLD premium names. If a registrar did not initially select this option for the desired fTLD domain, they should contact Verisign at cao@verisign- grs.com to update their Form(s). There are no specific requirements from Symantec to be able to offer premium names. Will fTLD be using a specific auction provider to handle premium name sales and other auction opportunities? There is currently no auction process established for fTLD. Registrars will be notified if a process is created. Can fTLD registrants sell/transfer their domain names? Yes, domain names can be sold/transferred. However, the new registrant must meet fTLD’s Registrant Eligibility and Name Selection Policies for the domain name and must also successfully be verified by Symantec. If fTLD does not approve the transfer, registrars will need to work with fTLD to restore the domain name ownership to the original verified registrant. Where can I find the lists of fTLD’s Reserved Names in .BANK and .INSURANCE? The lists are available here. What information is available to registrars and registrants to assist in the activation of fTLD Domains? The following resources have been developed in consultation with members of the financial services community and are intended to: Support the planning and implementation of an fTLD Domain Provide a framework for communicating an fTLD Domain plan to registrant employees, customers and other stakeholders Educate registrant executives, technology teams and/or third-party providers about the value of the robust security technologies and practices of an fTLD Domain. fTLD has incorporated the lessons learned and implementation solutions from early adopters into three guides that are designed to help registrants transition to a new fTLD domain. In addition, a planning checklist is provided to highlight the tasks that need review by a registrant implementation team. Implementation Planning Checklist Planning and Communications Guide Executive Guide to Security Requirements Technical Guide to Security Requirements These guides and the checklist can be downloaded here. fTLD Verification Is there a way to submit Symantec Orders without using the Symantec API? Yes, a web interface (“Web Form”) is available for registrars to submit Symantec orders if they have or anticipate having less than 50 total .BANK or .INSURANCE domain names under management. Registrars can also use the Web Form for Bi-annual Re-verification Orders even if they have more than 50 .BANK or .INSURANCE registrations under management. 3 If you want to see if you are eligible to use the Symantec Web Form to submit your Symantec orders, please contact fTLD at [email protected] for more details. Please note that all information needed for the API version is still needed for the Web Form version. What information is provided to Symantec for use in the fTLD verification process? Complete information for all fields in the Symantec order is provided in the Symantec Verification Order API Developer's Guide (“Symantec API documentation”), which is provided to fTLD approved registrars. For both .BANK and .INSURANCE, a Re-verification Type is required for Symantec orders submitted for existing domains. The specific requirement can be found in the Special Instructions field of the Symantec API documentation. What additional information is required for .BANK verification and how is it provided to Symantec? This additional information specific to .BANK is provided in the Special Instructions field that is detailed in the Symantec API documentation: Government Regulatory Authority Name – This information is required unless it is not applicable to the registrant type (e.g., trade associations, service providers). Regulatory ID Number – This information is required unless it is not applicable to the registrant type (e.g., trade associations, service providers). Human Resources Contact name and telephone number – Contact information to verify the employment information of the registrant contact. Registrant’s Management Contact name and telephone number – Contact information to verify that the registrant contact is authorized to register the domains requested. What additional information is required for .INSURANCE verification and how is it provided to Symantec? In addition to the Human Resources and Registrant’s Management Contact information, the following information is required for .INSURANCE orders and is detailed in the Special Instructions field of the Symantec API documentation.
Load more

Recommended publications
  • Privacy Policy V1.1
    CENTRALNIC LTD REGISTRY PRIVACY POLICY Version 1.1 September 2018 CentralNic Ltd 35-39 Moorgate London EC2R 6AR Table of Contents TABLE OF CONTENTS ......................................................................................................................... 2 AMENDMENT ISSUE SHEET ................................................................................................................. 3 INTRODUCTION ................................................................................................................................ 4 DATA PROTECTION RIGHTS ................................................................................................................. 5 RELATIONSHIP WITH REGISTRARS ......................................................................................................... 6 WHAT INFORMATION CENTRALNIC COLLECTS .......................................................................................... 6 INFORMATION CENTRALNIC DOES NOT COLLECT ....................................................................................... 8 HOW INFORMATION IS STORED ............................................................................................................ 8 HOW WE USE INFORMATION ............................................................................................................... 8 HOW INFORMATION IS PROTECTED ..................................................................................................... 13 HOW INFORMATION IS DELETED ........................................................................................................
    [Show full text]
  • From WHOIS to WHOWAS: a Large-Scale Measurement Study of Domain Registration Privacy Under the GDPR
    From WHOIS to WHOWAS: A Large-Scale Measurement Study of Domain Registration Privacy under the GDPR Chaoyi Lu∗†, Baojun Liu∗†¶B, Yiming Zhang∗†, Zhou Li§, Fenglu Zhang∗, Haixin Duan∗¶B, Ying Liu∗, Joann Qiongna Chen§, Jinjin LiangY, Zaifeng ZhangY, Shuang Hao∗∗ and Min Yang†† ∗Tsinghua University, †Beijing National Research Center for Information Science and Technology, flcy17, zhangyim17, zfl[email protected], flbj, [email protected], [email protected] §University of California, Irvine, fzhou.li, [email protected], ¶Qi An Xin Group, Y360 Netlab, fliangjinjin, [email protected], ∗∗University of Texas at Dallas, [email protected], ††Fudan University, m [email protected] Abstract—When a domain is registered, information about the [39], online advertising [55], [96], [103], [102] and usability registrants and other related personnel is recorded by WHOIS of privacy notices [104], [78], [79], [90], [50], [49], [27], [72]. databases owned by registrars or registries (called WHOIS providers jointly), which are open to public inquiries. However, Due to its broad scope, not only does the GDPR protect due to the enforcement of the European Union’s General Data normal users browsing websites, users setting up websites and Protection Regulation (GDPR), certain WHOIS data (i.e., the the associated infrastructure are also protected. One example records about EEA, or the European Economic Area, registrants) is domain registration. After a user registers a domain name, needs to be redacted before being released to the public. Anec- e.g., example.com, its sponsoring registrar and upper-stream dotally, it was reported that actions have been taken by some registry will store his/her personal information like name and WHOIS providers.
    [Show full text]
  • Master Services Agreement
    MASTER SERVICES AGREEMENT WHEREAS, Tucows.com Co., a Nova Scotia Corporation with its principal place of business in Toronto, Ontario, Canada (hereafter “Tucows”), provides certain services defined below as the “Tucows Services;” and WHEREAS, Customer, the person or entity defined below, wishes to use, resell and/or provision the Tucows Services for itself and the benefit its own Users, NOW, THEREFORE, in consideration of the mutual promises described in this Agreement, the parties agree to legally bind themselves as follows: 1. DEFINITIONS 1.1. “Aftermarket Premium Domain Names” refers to domains that are presently registered by a third party and that are available for purchase through a third-party service. 1.2. “Agreement” means this document and all its schedules and other documents incorporated by reference. 1.3. “API” is an acronym that stands for “Application Program Interface.” As used in this Agreement, “API” means the set of technical specifications and routines that allow Customer’s computer systems to access and carry out certain operations on Tucows’ computer systems. 1.4. “Commission” refers to the amount earned by a Customer on the sale of OpenSRS services via Storefront. 1.5. “Communications” means all written communications with Users, including registration applications, confirmations, modifications, terminations, invoices, credits, or other correspondence related to the use or provisioning of the Tucows Services. 1.6. “Confidential Information” means all information disclosed by a party, including technical information, software, financial data, and business and marketing plans. Confidential Information shall not include information which i. is publicly available at the time of its disclosure or becomes publicly available though no fault of the receiving party; ii.
    [Show full text]
  • SAC101 SSAC Advisory Regarding Access to Domain Name Registration Data
    SAC101 SSAC Advisory Regarding Access to Domain Name Registration Data An Advisory from the ICANN Security and Stability Advisory Committee (SSAC) 14 June 2018 SSAC Advisory Regarding Access to Domain Name Registration Data Preface This is an advisory to the ICANN Board, the ICANN Organization staff, the ICANN community, and, more broadly, the Internet community from the ICANN Security and Stability Advisory Committee (SSAC) about access to domain name registration data and Registration Data Directory Services (RDDS). The SSAC focuses on matters relating to the security and integrity of the Internet’s naming and address allocation systems. This includes operational matters (e.g., pertaining to the correct and reliable operation of the root zone publication system), administrative matters (e.g., pertaining to address allocation and Internet number assignment), and registration matters (e.g., pertaining to registry and registrar services). SSAC engages in ongoing threat assessment and risk analysis of the Internet naming and address allocation services to assess where the principal threats to stability and security lie, and advises the ICANN community accordingly. The SSAC has no authority to regulate, enforce, or adjudicate. Those functions belong to other parties, and the advice offered here should be evaluated on its merits. SAC101 1 SSAC Advisory Regarding Access to Domain Name Registration Data Table of Contents Preface 1 Table of Contents 2 Executive Summary 3 2 Background 6 3 Uses of Domain Registration Data for Security and Stability
    [Show full text]
  • Us Delegated Manager Agreement 1. Introduction
    .US DELEGATED MANAGER AGREEMENT 1. INTRODUCTION. In this .us Delegated Manager Agreement ("Agreement"), "we", "us" and "our" refer to Neustar, Inc. ("usTLD Administrator"), a Delaware corporation located at 46000 Center Oak Plaza, Sterling, Virginia 20166, and "you" and "your" refer to any person that serves as a delegated manager (“Delegated Manager”) responsible for the maintenance, support and administration over .us locality domain names (“Locality Names”) registered by localities, schools, state agencies, federal agencies, distributed national institutes, and general independent entities (collectively referred to as "Registrants"). This Agreement explains our obligations to you, and your obligations to us in relation to our .US domain registration services. If your .US domain name registration services for a particular Locality Name previously were provided under arrangement with any of our predecessors, including, but not limited to VeriSign, Inc., Network Solutions, Inc., or the Information Sciences Institute, University of Southern California (collectively referred to as “Predecessors"), your continued service as a Delegated Manager in the .US domain and the use of our .US domain name registration services constitutes your assent to the terms of this Agreement. If you submitted an application for our .US domain name registration services, the Effective Date of this Agreement shall be the date of our acceptance of your application. If you previously received .US domain name registration services from any Predecessor, the Effective Date of this Agreement is October 12, 2005. 2. TERM. The term of this Agreement is from the Effective Date to the date on which the usTLD Administrator has no further obligation to render .US Top Level Domain ("TLD") administration services under any agreement with the United States Government, or until earlier terminated pursuant to Section 26 hereof (the "Initial Term").
    [Show full text]
  • Beginner's Guide to Domain Names
    Beginner’s Guide to D O M A I N N A M E S THIS IS ONE OF A SERIES OF GUIDES ABOUT ISSUES OF IMPORTANCE TO INTERNET USERS. EDUCATING NEW USERS ABOUT INTERNET ISSUES IS PART OF ICANN’S MISSION TO ENSURE A STABLE, SECURE, GLOBALLY INTEROPERABLE INTERNET. ICANN PREPARED THIS GUIDE AT THE REQUEST OF THE AT-LARGE ADVISORY COMMITTEE, THE VOICE OF THE INDIVIDUAL INTERNET USER AT ICANN. WE SINCERELY HOPE YOU FIND IT HELPFUL. TA b l E O f C ontents Introduction.................................................................................................................................................................................................................................2 Domain Names...........................................................................................................................................................................................................................3 1 What.is.a.domain.name.and.how.does.it.work?...........................................................................................................................................3 2 ...How.do.I.register.a.domain.name?.......................................................................................................................................................................3 . 3 ...How.do.I.select.a.domain.name.to.register?..................................................................................................................................................4 4 What.is.a.registrar.and.how.do.I.select.one?...................................................................................................................................................5
    [Show full text]
  • NEUSTAR Launch Policies
    .NEUSTAR Launch Policies Introduction This Plan has been developed to describe the Launch Program for the .NEUSTAR Top Level Domain ("TLD") by Neustar, Inc. ("Registry Operator"). As recognized by ICANN, the TLD qualifies as a .BRAND TLD and as such incorporates Specification 13 in the TLD’s Registry Agreement, which exempts Registry Operator from the requirement to conduct a Sunrise Period prior to opening up General Registration, or any other Limited Registration Period. As such, upon launch, the TLD will proceed immediately to General Availability. This document forms the complete initial plan, policy and process adopted by the Registry Operator for the launch of the TLD. Background Rights Protection Mechanisms and the Trademark Clearinghouse ICANN has established the Trademark Clearinghouse (“TMCH”) and associated processes and procedures so that the Registry Operator can comply with its obligation to implement Rights Protection Mechanisms. Registry Operator's implementation of the mandatory Claims Period has been integrated and tested with the TMCH Sunrise and Claims Operator appointed by ICANN (“TMCH Service Provider”). Information about the Trademark Clearinghouse and the TMCH Service Provider can be found at the following link http://trademark- clearinghouse.com/. Registry Operator's role is to verify that the information provided to it by a registrar matches the information that is contained in the TMCH. Registry Operator does not make any decisions about the validity or use of a mark or its inclusion in the Trademark Clearinghouse. If the event that Registry Operator changes the nature of the .NEUSTAR TLD such that the TLD no longer meets the criteria set forth in Specification 13, Registry Operator will implement a Sunrise Period and amend these launch policies to include the policies and procedures required under such Rights Protection Mechanism.
    [Show full text]
  • ("Agreement"), Is Between Tucows Domains Inc
    MASTER DOMAIN REGISTRATION AGREEMENT THIS REGISTRATION AGREEMENT ("Agreement"), is between Tucows Domains Inc. ("Tucows") and you, on behalf of yourself or the entity you represent ("Registrant"), as offered through the Reseller participating in Tucows' distribution channel for domain name registrations. Any reference to "Registry" or "Registry Operator" shall refer to the registry administrator of the applicable top-level domain ("TLD"). This Agreement explains Tucows' obligations to Registrant, and Registrant's obligations to Tucows, for the domain registration services. By agreeing to the terms and conditions set forth in this Agreement, Registrant agrees to be bound by the rules and regulations set forth in this Agreement, and by a registry for that particular TLD. DOMAIN NAME REGISTRATION. Domain name registrations are for a limited term, which ends on the expiration date communicated to the Registrant. A domain name submitted through Tucows will be deemed active when the relevant registry accepts the Registrant's application and activates Registrant's domain name registration or renewal. Tucows cannot guarantee that Registrant will obtain a desired domain name, even if an inquiry indicates that a domain name is available at the time of application. Tucows is not responsible for any inaccuracies or errors in the domain name registration or renewal process. FEES. Registrant agrees to pay Reseller the applicable service fees prior to the registration or renewal of a domain. All fees payable here under are non-refundable even if Registrant's domain name registration is suspended, cancelled or transferred prior to the end of your current registration term. TERM. This Agreement will remain in effect during the term of the domain name registration as selected, recorded and paid for at the time of registration or renewal.
    [Show full text]
  • Autodns User Manual
    USER MANUAL AutoDNS Manual Version 9.0 September 2016 © 1998-2016 InterNetX GmbH Text, content, design and the arrangement of this manual are subject to the protection of copyright laws. You may only use or copy its content for private use, Copyright personal or non-commercial purposes and while respecting the provisions of copyright laws. Table of Contents 1 Introduction ..................................................................................................... 9 1.1 Welcome .............................................................................................................................. 9 1.2 The New Interface Version 3.0 ........................................................................................... 9 2 Documentation and Help ............................................................................. 11 2.1 Using this Documentation ............................................................................................... 11 Conventions ........................................................................................................................ 11 Form Section Options ......................................................................................................... 11 2.2 Getting Help ....................................................................................................................... 12 Sending an Email to our Support ....................................................................................... 13 2.3 Glossary ............................................................................................................................
    [Show full text]
  • RDAP) Contact Manual T +31 (0)26 352 5500 [email protected]
    Registration Data Access Protocol (RDAP) Contact Manual T +31 (0)26 352 5500 [email protected] www.sidn.nl Offices Meander 501 6825 MD Arnhem The Netherlands Mailing address PO Box 5022 6802 EA Arnhem The Netherlands Date Classification Page 20 August 2019 Public 1/10 Author Status SIDN Final Date Classification Page Fout! Verwijzingsbron niet gevonden. Public 2/10 Table of Contents 1 Introduction 3 2 How to use RDAP 4 2.1 HTTP Error Codes 4 2.2 RDAP Clients 4 2.3 Additional Services 5 2.4 References 5 2.5 Future of Port 43 Whois 5 2.6 Feedback and questions 5 3 Roles 6 4 Statuses 6 5 Data output 7 5.1 Domain name 7 5.2 Registrar 9 5.3 Name server 9 5.4 DNSSEC 9 5.5 Auteursrechtvoorbehoud/Copyright notice 10 Date Classification Page Fout! Verwijzingsbron niet gevonden. Public 3/10 1 Introduction This document describes SIDN's support for the RDAP protocol. RDAP was designed by the weirds working group of the Internet Engineering Task Force (IETF), in response to ICANN’s request for the IETF to develop a replacement for Whois. RDAP returns data similar to that provided by the Whois service, but in a JSON-structured format. With RDAP, you can look up the following object classes: 1. Domains 2. Name servers 3. Entities RDAP is intended to address deficiencies in the Whois protocol [RFC3912] that have been identified over time, including: Lack of standardised command structures Lack of standardised output and error structures Lack of support for internationalisation and localisation Lack of support for user identification, authentication and access control RDAP builds upon HTTP and the "REST" (REpresentational State Transfer) architectural style.
    [Show full text]
  • Territorialization of the Internet Domain Name System
    Scholarly Commons @ UNLV Boyd Law Scholarly Works Faculty Scholarship 2018 Territorialization of the Internet Domain Name System Marketa Trimble University of Nevada, Las Vegas -- William S. Boyd School of Law Follow this and additional works at: https://scholars.law.unlv.edu/facpub Part of the Intellectual Property Law Commons, International Law Commons, and the Internet Law Commons Recommended Citation Trimble, Marketa, "Territorialization of the Internet Domain Name System" (2018). Scholarly Works. 1020. https://scholars.law.unlv.edu/facpub/1020 This Article is brought to you by the Scholarly Commons @ UNLV Boyd Law, an institutional repository administered by the Wiener-Rogers Law Library at the William S. Boyd School of Law. For more information, please contact [email protected]. Territorialization of the Internet Domain Name System Marketa Trimble* Abstract Territorializationof the internet-the linking of the internet to physical geography is a growing trend. Internet users have become accustomed to the conveniences of localized advertising, have enjoyed location-based services, and have witnessed an increasing use of geolocation and geo- blocking tools by service and content providers who for various reasons- either allow or block access to internet content based on users' physical locations. This article analyzes whether, and if so how, the trend toward territorializationhas affected the internetDomain Name System (DNS). As a hallmark of cyberspace governance that aimed to be detached from the territorially-partitionedgovernance of the physical world, the DNS might have been expected to resist territorialization-a design that seems antithetical to the original design of and intent for the internet as a globally distributed network that lacks a single point of control.
    [Show full text]
  • WHOIS Search Provides Domain Registration Information from Network Solutions 314/11/Friday 11H39
    WHOIS Search provides domain registration information from Network Solutions 314/11/Friday 11h39 Login Your cart is empty WHOIS Search Results Keep prying eyes out of your e-mail. Get MessageGuard™ today! WHOIS Record For Need More Info? Contact us today! mercyhands.net CALL 1-800-361-5712 Services from Network Solutions: CONTACT a sales Certified Offer Service - Let us help you get this domain name! consultant SSL Certificates - Get peace of mind with a secure certificate. Site Confirm Seals - Display a security seal and gain visitor trust. Whois Server Version 2.0 Domain names in the .com and .net domains can now be registered with many different competing registrars. Go to http://www.internic.net for detailed information. Domain Name: MERCYHANDS.NET Registrar: SPOT DOMAIN LLC DBA DOMAINSITE.COM Whois Server: whois.domainsite.com Referral URL: http://www.domainsite.com Name Server: NS942.SECURENET-SERVER.NET Name Server: NS941.SECURENET-SERVER.NET Status: REGISTRAR-LOCK EPP Status: clientDeleteProhibited EPP Status: clientRenewProhibited EPP Status: clientTransferProhibited EPP Status: clientUpdateProhibited Updated Date: 18-Oct-2006 Creation Date: 31-May-2005 Expiration Date: 31-May-2007 >>> Last update of whois database: Fri, 10 Nov 2006 05:34:29 EST <<< NOTICE: The expiration date displayed in this record is the date the registrar's sponsorship of the domain name registration in the registry is currently set to expire. This date does not necessarily reflect the expiration date of the domain name registrant's agreement with the sponsoring registrar. Users may consult the sponsoring registrar's Whois database to view the registrar's reported date of expiration for this registration.
    [Show full text]