[ URL ftp://rs.internic.net/templates/domain-template.txt ] [ 6/97 ]
**************** Please DO NOT REMOVE Version Number ***************
Domain Version Number: 3.5
********** Please see attached detailed instructions ***************
NETWORK SOLUTIONS, INC.
DOMAIN NAME REGISTRATION AGREEMENT
A. Introduction. This domain name registration agreement ("Registration Agreement") is submitted to NETWORK SOLUTIONS, INC. ("NSI") for the purpose of applying for and registering a domain name on the Internet. If this Registration Agreement is accepted by NSI, and a domain name is registered in NSI's domain name database and assigned to the Registrant, Registrant ("Registrant") agrees to be bound by the terms of this Registration Agreement and the terms of NSI's Domain Name Dispute Policy ("Dispute Policy") which is incorporated herein by reference and made a part of this Registration Agreement. This Registration Agreement shall be accepted at the offices of NSI.
B. Fees and Payments. Registrant agrees to pay a registration fee of One Hundred United States Dollars (US$100) as consideration for the registration of each new domain name or Fifty United States Dollars (US$50) to renew an existing registration. The payment may be made payable either directly to "Network Solutions, Inc.", or indirectly to NSI through the Registrant's Internet Service Provider ("ISP"). Payment is due within thirty (30) days from the date of the invoice. The non-refundable fee covers a period of two (2) years for each new registration, and one (1) year for each renewal, and includes any permitted modification(s) to the domain name's record during the covered period.
C. Dispute Policy. Registrant agrees, as a condition to submitting this Registration Agreement, and if the Registration Agreement is accepted by NSI, that the Registrant shall be bound by NSI's current Dispute Policy. The current version of the Dispute Policy may be found at the InterNIC Registration Services web site: "http://rs.internic.net/dispute.html".
D. Dispute Policy Changes or Modifications. Registrant agrees that NSI, in its sole discretion, may change or modify the Dispute Policy, incorporated by reference herein, at any time. Registrant agrees that Registrant's maintaining the registration of a domain name after changes or modifications to the Dispute Policy become effective constitutes Registrant's continued acceptance of these changes or modifications. Registrant agrees that if Registrant considers any such changes or modifications to be unacceptable, Registrant may request that the domain name be deleted from the domain name database.
E. Disputes. Registrant agrees that, if the registration of its domain name is challenged by any third party, the Registrant will be subject to the provisions specified in the Dispute Policy.
F. Agents. Registrant agrees that if this Registration Agreement is completed by an agent for the Registrant, such as an ISP or Administrative Contact/Agent, the Registrant is nonetheless bound as a principal by all terms and conditions herein, including the Dispute Policy.
G. Limitation of Liability. Registrant agrees that NSI shall have no liability to the Registrant for any loss Registrant may incur in connection with NSI's processing of this Registration Agreement, in connection with NSI's processing of any authorized modification to the domain name's record during the covered period, as a result of the Registrant's ISP's failure to pay either the initial registration fee or renewal fee, or as a result of the application of the provisions of the Dispute Policy. Registrant agrees that in no event shall the maximum liability of NSI under this Agreement for any matter exceed Five Hundred United States Dollars (US$500).
H. Indemnity. Registrant agrees, in the event the Registration Agreement is accepted by NSI and a subsequent dispute arises with any third party, to indemnify and hold NSI harmless pursuant to the terms and conditions contained in the Dispute Policy.
I. Breach. Registrant agrees that failure to abide by any provision of this Registration Agreement or the Dispute Policy may be considered by NSI to be a material breach and that NSI may provide a written notice, describing the breach, to the Registrant. If, within thirty (30) days of the date of mailing such notice, the Registrant fails to provide evidence, which is reasonably satisfactory to NSI, that it has not breached its obligations, then NSI may delete Registrant's registration of the domain name. Any such breach by a Registrant shall not be deemed to be excused simply because NSI did not act earlier in response to that, or any other, breach by the Registrant.
J. No Guaranty. Registrant agrees that, by registration of a domain name, such registration does not confer immunity from objection to either the registration or use of the domain name.
K. Warranty. Registrant warrants by submitting this Registration Agreement that, to the best of Registrant's knowledge and belief, the information submitted herein is true and correct, and that any future changes to this information will be provided to NSI in a timely manner according to the domain name modification procedures in place at that time. Breach of this warranty will constitute a material breach.
L. Revocation. Registrant agrees that NSI may delete a Registrant's domain name if this Registration Agreement, or subsequent modification(s) thereto, contains false or misleading information, or conceals or omits any information NSI would likely consider material to its decision to approve this Registration Agreement.
M. Right of Refusal. NSI, in its sole discretion, reserves the right to refuse to approve the Registration Agreement for any Registrant. Registrant agrees that the submission of this Registration Agreement does not obligate NSI to accept this Registration Agreement. Registrant agrees that NSI shall not be liable for loss or damages that may result from NSI's refusal to accept this Registration Agreement.
N. Severability. Registrant agrees that the terms of this Registration Agreement are severable. If any term or provision is declared invalid, it shall not affect the remaining terms or provisions which shall continue to be binding.
O. Entirety. Registrant agrees that this Registration Agreement and the Dispute Policy is the complete and exclusive agreement between Registrant and NSI regarding the registration of Registrant's domain name. This Registration Agreement and the Dispute Policy supersede all prior agreements and understandings, whether established by custom, practice, policy, or precedent.
P. Governing Law. Registrant agrees that this Registration Agreement shall be governed in all respects by and construed in accordance with the laws of the Commonwealth of Virginia, United States of America. By submitting this Registration Agreement, Registrant consents to the exclusive jurisdiction and venue of the United States District Court for the Eastern District of Virginia, Alexandria Division. If there is no jurisdiction in the United States District Court for the Eastern District of Virginia, Alexandria Division, then jurisdiction shall be in the Circuit Court of Fairfax County, Fairfax, Virginia.
Q. This is Domain Name Registration Agreement Version Number 3.5. This Registration Agreement is only for registrations under top-level domains: COM, ORG, NET, and EDU. By completing and submitting this Registration Agreement for consideration and acceptance by NSI, the Registrant agrees that he/she has read and agrees to be bound by A through P above.
Authorization 0a. (N)ew (M)odify (D)elete.........: 0b. Auth Scheme.....................: 0c. Auth Info.......................:
2. Complete Domain Name.............:
Organization Using Domain Name 3a. Organization Name (Registrant)..: 3b. Street Address..................: 3c. City............................: 3d. State...........................: 3e. Postal Code.....................: 3f. Country Code (2 letter).........:
Administrative Contact/Agent 4a. NIC Handle (if known)...........: 4b. (I)ndividual or (R)ole?.........: 4c. Name............................: 4d. Organization Name...............: 4e. Street Address..................: 4f. City............................: 4g. State...........................: 4h. Postal Code.....................: 4i. Country Code (2 letter).........: 4j. Phone Number....................: 4k. Fax Number......................: 4l. Email Address...................:
Technical Contact 5a. NIC Handle (if known)...........: 5b. (I)ndividual or (R)ole?.........: 5c. Name............................: 5d. Organization Name...............: 5e. Street Address..................: 5f. City............................: 5g. State...........................: 5h. Postal Code.....................: 5i. Country Code (2 letter).........: 5j. Phone Number....................: 5k. Fax Number......................: 5l. Email Address...................:
Billing Contact 6a. NIC Handle (if known)...........: 6b. (I)ndividual or (R)ole?.........: 6c. Name............................: 6d. Organization Name...............: 6e. Street Address..................: 6f. City............................: 6g. State...........................: 6h. Postal Code.....................: 6i. Country Code (2 letter).........: 6j. Phone Number....................: 6k. Fax Number......................: 6l. Email Address...................:
Primary Name Server 7a. Primary Server Hostname.........: 7b. Primary Server Netaddress.......:
Secondary Name Server(s) 8a. Secondary Server Hostname.......: 8b. Secondary Server Netaddress.....:
END OF AGREEMENT
I. This Registration Agreement must be submitted to NSI for any of the following actions:
a. Registering a New Domain Name.
b. Modifying a Domain Name Record.
c. Deleting a Domain Name.
d. Transferring a Domain Name.
Specific Instructions for completing each action can be found under the appropriate heading for each section. To ensure your agreement is promptly processed, please read and follow the instructions carefully.
II. The Registration Agreement must be submitted for acceptance to NSI via Email at: "HOSTMASTER@INTERNIC.NET".
III. Upon receipt of the Registration Agreement, NSI will acknowledge receipt by Email. The Email will include a tracking number in the form "NIC-YYMMDD.#" (#=Sequential number from 1 to 5 digits). Use the tracking number in the Subject of any Email you send regarding that particular Registration Agreement.
IV. Upon initial acceptance and processing of the Registration Agreement, NSI will send an Email notice that the domain name registration is completed.
V. Do not modify the Registration Agreement or remove the Registration Agreement version number.
VI. Before completing the Registration Agreement, check to see if the domain name has already been registered by accessing the "whois" database at the world wide web location: "http://rs.internic.net/cgi-bin/whois". Use the information in the database where appropriate and as required. This will minimize the possibility of your Registration Agreement being returned.
REGISTERING A NEW DOMAIN NAME
Section 0 - Registration Type and Security
* Item 0a: Following the colon, type the character "N" or the word "New" to indicate a new domain name registration.
* The purpose of security (Items 0b and 0c) is to protect the Registrant's domain name information from unauthorized modifications. For more information about security, refer to the InterNIC homepage at "http://rs. internic.net/guardian/".
* If Item 0a is marked (N)ew, Items 0b and 0c will be ignored. (Items 0b and 0c can only be used to (M)odify and (D)elete names.)
Section 1 - Purpose of Registration
* Briefly describe the domain name Registrant and the purpose for which this domain name is being applied. The description should support the choice of the top-level domain described below in Section 2.
Section 2 - Complete Domain Name
* For second-level domain names under .COM, .ORG, .NET, or .EDU, insert the name of the domain you wish to register as in, "EXAMPLE.COM". The total length of the two-part (second level.top level) name may be up to 26 characters (including the 4 characters .com). The only characters allowed in a domain name are letters, digits and the dash (-). A domain name cannot begin or end with a dash. The top level domains registered by NSI are .COM, .ORG, .NET, and .EDU.
* Registrant is responsible for the accuracy of name submission; names will be registered as submitted; any changes will entail an additional registration fee.
Section 3 - Domain Name Registrant
* The domain name is considered to be registered to a "legal entity", even if the legal entity is an individual (e.g., Lee Smith). Do not list a "dba" or acronym as the registrant. In this section, it is important to list the legal name and address of the Registrant, not the Internet Service Provider ("ISP").
* If Items 3d or 3e are not applicable for your country, leave that Item blank. Items 3a, 3b, 3c and 3f must be completed or the Agreement will not be accepted.
* Item 3f may be either the country name or two-letter country code. A list of country codes is available at "http://www.isi.edu/div7/iana/domain-names.html".
Sections 4, 5 & 6 - Contacts
* The Administrative Contact/Agent is the person or organization authorized by the domain name Registrant to act on behalf of the legal entity listed in Item 3a. The Administrative Contact/Agent should be able to answer non-technical questions about the legal entity's plans for using the domain name and the procedures for establishing sub-domains.
* Generally, the Technical Contact is the person or organization who maintains the domain name Registrant's primary name server, resolver software, and database files. The Technical Contact person keeps the name server running and interacts with technical people in other domains to solve problems that affect the domain name. An ISP often performs this role.
* The Billing Contact will be invoiced for registrations and renewals.
* If the Technical or Billing Contact information is missing from the Registration Agreement, it will be presumed that the domain name Registrant has authorized the Administrative Contact/Agent to perform those roles.
* If the contact has never been registered or the handle is unknown, leave Item "a" (NIC Handle) blank. The registration software will check for matches with existing contact records. If a contact record is found in the database that matches the information on the Registration Agreement in a significant way (name, organization, phone, Email Address), the database information will override the information you supply in the Registration Agreement. (A contact record cannot be updated by using the Registration Agreement.)
* Each contact in NSI's database is assigned a "handle" - a unique tag to differentiate him/her from all other contacts in the database. Only one handle should exist for each Individual or Role. If the contact handle is already in the database, insert it in Item "a" and leave the rest of the section blank. If the contact handle is inserted and additional information is also provided, only the contact handle will be used. Any additional information will be ignored. Use contact handles whenever possible.
* Item b - indicate the type of contact you are registering. If the contact is a person, insert "I" for "Individual". If it is a group or an organization where several individuals may be acting in that role, insert "R" for "Role".
* Item c - place the name of the Individual or Role being registered. For Individuals, supply the full name (last, first and middle initial). Do not use titles. If suffixes are used, such as "Jr." or "III", separate the name from the suffix with a comma. For example, "Public, John Q., III" will result in a handle in the form of "JQP123". For Role contacts, provide the full name, for example, "Customer Service Support Center" would generate a handle of CSSC-ORG. The maximum length of a handle is 10 characters.
* Item e - Street Address.
* Multiple entries in Items j, k, and l must be separated by a comma.
* For each contact, if a NIC handle is not entered in a, Items b, c, d, e, f, i, j, and l must be completed. Agreements that do not have this information will be returned.
Sections 7 & 8 - Name Servers
* Items a and b must be completed in full. Incomplete information in Sections 7 and 8 will result in the Agreement being returned.
* Most ISP's can provide one or more name servers if you do not have your own. Do not list name servers without the explicit approval of their owners. The owners of the servers listed must configure the servers before your domain name will function.
* If possible, name servers should be in physically separate locations and on different networks.
* Provide the fully-qualified name of the machine that is to be the name server. For example, use "machinename.domainname.com" not just "machinename."
* If several secondary servers are desired, copy and complete Section 8 as many times as necessary. Do not renumber or change the copied section.
* A new domain name registration Agreement will not change either the hostname (i.e., the name of the name server) or the netaddress (i.e., the IP number) of a name server registered in the database. (To change a hostname or netaddress, submit a Host Template. For more information about a Host Template refer to "ftp://rs.internic.net/template/host-template.txt".)
MODIFYING A DOMAIN NAME RECORD
* Modifying an existing domain name record is done by "replacement". This means the contents of various fields in the database are replaced with new information from the Registration Agreement. Use the "whois" database at "http://rs.internic.net/cgi-bin/whois" if you are unsure about the current information for a domain name, name server or contact.
* If you want to transfer a domain name from one organization (Registrant) to another organization (Registrant), see instructions for TRANSFERRING A DOMAIN NAME.
* The spelling of a domain name cannot be changed by submitting a modification Agreement. If you want a domain name with different spelling, you must file a New Registration Agreement for the new domain name and a Delete Registration Agreement when you are ready to have the old name removed. A new registration fee will be charged; payments will not be transferred.
* If you want to change a contact record, use the Contact Template at "ftp://rs.internic.net/templates/contact-template.txt".
* If you want to change a Name Server record, use the Host Template at "ftp://rs.internic.net/templates/host-template.txt".
Section 0 - Registration Type and Security
* Item 0a - type the character "M" or the word "Modify" to indicate a modification to an existing domain name registration.
* Modifications will be made according to the security parameters established by the contacts for the domain name registrant. If the contacts have not chosen any level of security, the change will be made if the Registration Agreement is submitted by the domain name Registrant or the Administrative Contact/Agent. - Items 0b and 0c depend on the level of security chosen by the contact submitting the modification. - If Item 0b is blank, Item 0c will be ignored. - If Item 0b is M or Mail-From, Item 0c will be ignored. This is the default. - If Item 0b is C or Crypt-PW, enter your cleartext password (i.e., the plain text of the encrypted password) in Item 0c. - If Item 0b is P or PGP, Item 0c is ignored. The sender should sign the entire Modification Registration Agreement with the PGP key and send it in cleartext.
* Notification of pending or finished modifications will be made according to the security parameters chosen by the contacts. If no security parameter has been chosen, the notification of the modification and the approximate time the modification will take effect will be sent to: - the requester - if contacts are changing, both old and new contacts - if name servers are changing, the Technical Contacts for the domains in which the old and new primary name servers reside
* This dissemination of modification information is to ensure that all parties involved are aware and are given an opportunity to agree or disagree with the modification.
* For more information on the levels of security available and how to generate passwords, see "http://rs.internic.net/guardian".
* Complete Sections 0 through 2, then complete only the Sections being modified. The completed Registration Agreement should be sent to "HOSTMASTER@INTERNIC.NET".
Section 1 - Purpose of Modification
* Briefly describe the purpose of the modification in Item 1. If the request for modification is not from a currently listed contact, the request will be forwarded to the listed contacts for approval before being processed.
Section 2 - Complete Domain Name
* Insert the domain name of the domain name to be modified (e.g., "EXAMPLE.COM"). This section is required.
Sections 3 - Organization Using the Domain Name
* The domain name is considered to be registered to a "legal entity" even if the legal entity is an individual (e.g., Julie Smith). (Transfer of a domain name from one legal entity to another is not considered to be a modification. See Transferring a Domain Name.)
Sections 4, 5 & 6 - Contacts
* A contact can be changed only by supplying another Individual or Role contact. If the new contact's information is already in the database, enter the handle in Item a. To register a new contact, complete Items b through 1. If you want to change the information associated with a previously registered contact (e.g., Email address, Telephone number, etc.), you must submit a Contact Template.
Sections 7 & 8 - Primary and Secondary Name Servers
* To change the primary and secondary name servers, complete Items a and b. A complete list of name servers must be provided even if only one name server is being replaced.
DELETING A DOMAIN NAME
* A request that comes from the Registrant or the Administrative Contact/Agent will be honored, providing any security constraints are met.
* Notification of a completed deletion request will be sent to: - the requester - the contacts currently listed - the Technical Contact for the domain in which the primary name server resides
* A request that comes from an ISP currently providing name service for the domain name may result in the name being placed on hold.
* If the request comes from none of the above, and does not meet any security established for the contacts, it will be returned for further explanation of the relationship between the requester and Registrant. The Administrative Contact/Agent and the Technical Contact will be notified.
* If an ISP removes name service, the domain name may be placed on "hold". "Hold" means that the domain name will be visible via "whois" at "http://rs.internic.net/cgi-bin/whois", but cannot be used.
* The completed Registration Agreement requesting the deletion should be sent to "HOSTMASTER@INTERNIC.NET".
Section 0 - Registration Type and Security
* Item 0a - type the character "D" or the word "Delete" to designate the deletion of an existing domain name registration.
* Deletions will be made according to the security parameters established for the contacts for the domain name Registrant.
* Items 0b and 0c depend on the level of security chosen by the contact submitting the modification.
* If Item 0b is blank, Item 0c will be ignored.
* If Item 0b is M or Mail-From, Item 0c will be ignored. This is the default.
* If Item 0b is C or Crypt-PW, enter your cleartext password (i.e. the plain text of the encrypted password) in Item 0c.
* If Item 0b is P or PGP, Item 0c is ignored. The sender should sign the entire Modification Registration Agreement with the PGP key and send it in cleartext.
* Notification of pending deletions will also be made according to the security parameters chosen by the contacts. If no security parameter has been chosen, the notification of the modification will be sent to: - the requester - contacts
* This dissemination of deletion information is to ensure that all parties involved are aware and are given an opportunity to concur or disagree with the deletion.
Section 1 - Purpose of Deletion
* If the request for deletion is not from a currently listed contact, the request will be forwarded to the listed contacts for approval before being processed.
* If additional records, such as the point(s) of contact or name servers should also be deleted, use the appropriate Contact Template or Host Template referred to above.
Section 2 - Complete Domain Name
* Insert the domain name of the domain name to be deleted (e.g., "EXAMPLE.COM").
Section 3 through Section 8
* These sections should be left blank.
TRANSFERRING A DOMAIN NAME
This process ONLY applies if you want to transfer a domain name from one organization (Registrant) to another organization (Registrant). The TRANSFERRING A DOMAIN NAME process does NOT apply if you want to move your domain name to a new service provider; to change service providers, see instructions for MODIFYING A DOMAIN NAME RECORD.
Please note that full registration fees must be paid by both the original and new Registrant. The new Registrant will be billed for a new two-year period beginning on the transfer date.
* Two separate Registration Agreements are required to transfer a domain name. The current domain name holder completes a Registration Agreement for deletion of the domain name. The legal entity seeking to obtain that domain name completes a new Registration Agreement and submits both Registration Agreements in one Email to NSI. The following procedures apply:
- The current Administrative Contact/Agent must complete Items 0 through 2 of a Registration Agreement. Item 0a should be marked "D" or "Delete". This Registration Agreement should be Emailed to the legal entity seeking to obtain the domain name. The subject line must read "Transfer Domain" and specify the domain name.
- The new Registrant for the domain name should complete a separate Registration Agreement with Item 0a reflecting "N" or "New" and all other Items completed as appropriate.
- The new Registrant should append the New Registration Agreement to the Email from the current domain holder and forward the joined Registration Agreements as a single submission to: "HOSTMASTER@INTERNIC.NET".
- If the current Administrative Contact/Agent no longer has access to the Internet, a fax on organization letterhead and signed by an officer with title identified and with the authority to legally bind the organization listed as the Registrant, authorizing the transfer may be sent to NSI and the recipient.
- If the recipient of the domain name does not have Internet access, the recipient can obtain an Email account through the ISP selected to support the domain name.
* The Email header from both parties must be intact to provide evidence of appropriate authorization; the email addresses must be identical to those in the current WHOIS record for the contacts unless alternate authentication methods (Crypt Password or PGP) are used. If it is not clear that the transfer is authorized by the current holder, the Registration Agreements will not be processed and will be returned.
-----END OF INSTRUCTIONS-----