domorder

As an ICANN-accredited Registrar, you may receive a UDRP Complaint from either the Complainant or the UDRP Service Provider, directly. Ideally, you should have received a hard/soft copy of the official UDRP
complaint, before processing a complaint. However, some UDRP Service Providers expect the Sponsoring Registrar to initiate the process even without sending the official complaint.

Processing the UDRP Service Provider's Request

1. Lock the domain name through OrderBox and if Privacy Protection has been enabled for the domain name, disable the same. Provide a meaningful reason while performing these actions, such that both you and your Customer can identify the purpose of Locking the domain name/disabling Privacy Protection [when viewing from their OrderBox interface].

   Note

   • Locking a Domain Name

   • Disabling Privacy Protection for a Domain Name

2. Respond to the questions of the UDRP Service Provider as per the format mentioned below. The following is the set of questions asked by WIPO; other UDRP Service Providers ask only a subset of these
   questions:

   <Your Registrar Company Name> acknowledges the UDRP Case <Case No.> administrative proceedings against the domain name <domain name>. Kindly find our compliance to your requirements as below - Question (1) - indicate whether, at the time of your reply to us, you are in receipt of a copy of the Complaint sent by the Complainant, as required by WIPO Supplemental Rules for Uniform Domain Name Dispute Resolution Policy, Paragraph 4(b). Answer (1) - <Your Registrar Company Name> is in receipt of the copy of the Complaint forwarded by the Complainant [<Complainant Company Name - Complainant Email Address>] in soft/hard copy. OR No, <Your Registrar Company Name> is NOT in Receipt of the Complaint. Question (2) - confirm that the specified domain name(s) is/are registered with you. Answer (2) - The domain name <Domain Name>'s registration is sponsored by the Registrar <Your Registrar Company Name>. Question (3) - confirm that the Respondent is the current registrant of the domain name(s). Answer (3) - The Current Registrant as per the Whois database is the same as the Respondent - <Domain Name's Registrant Contact Details> OR The Current Registrant as per the Whois database is the different from the Respondent - <Domain Name's Registrant Contact Details> Question (4) - provide the full contact details (i.e., postal address(es), telephone number(s), facsimile number(s), e-mail address(es)) that are available in your WHOIS database for the domain name registrant, technical contact, administrative contact and billing contact, for the above domain name(s). Answer (4) - The complete Contact Details of the domain name <Domain Name> as per <your Whois Server URL> are - <Domain Name's all Contact Details as seen in the Whois Output> Question (5) confirm that the Uniform Domain Name Dispute Resolution Policy applies to the domain name(s). Answer (5) - <Your Registrar Company Name> confirms that UDRP extends to all <this domain name's TLD> domain name registrations, registered through <Your Registrar Company Name>. Under the policy, most types of trademark-based domain-name disputes must be resolved by agreement, court action, or arbitration before a Registrar will cancel, suspend, or transfer a domain name. Question (6) - indicate the date of expiry of the domain name(s). Answer (6) - The Expiry Date of the domain name as per our database is <Expiry date within OrderBox>. Question (7) - confirm that the domain name(s) will remain on registrar lock during the pending administrative proceeding (reference is also made to paragraph 3.7.5.7. of the ICANN Expired Domain Deletion Policy, at https://www.icann.org/registrars/eddp.htm). Answer (7) - A Registrar Lock has been applied to <domain name> and will continue to be maintained, until the Expiry of the domain name (Expiry Date), post which the Complainant may choose to Renew this domain name through Registrar <Your Registrar Company Name>, prior to the Automatic Deletion (Deletion Date) of the domain name. If of course, Registrar <Your Registrar Company Name> receives the UDRP decision prior the domain name's automatic (system) deletion on <Deletion Date>, we would comply with their decision. Question (8) - indicate the specific language of the registration agreement as used by the registrant for each domain name. Answer (8) - The <Language Name> language was used to inform the Registrant of both the Domain Registration Agreement as well as the Customer Master Agreement during the domain name Registration and Customer Signup process. Question (9) - indicate whether the domain name registrant has submitted in its Registration Agreement to the jurisdiction at the location of the principal office of the Registrar for court adjudication of disputes concerning or arising from the use of the domain name(s) (Rules, Paragraph 1). Answer (9) - Yes, the Registrant/Customer has confirmed this via <Your Registrar Company Name>'s Customer Master Agreement Policy 23 - JURISDICTION & ATTORNEY'S FEES, during the domain name registration and Customer Signup process. Please feel free to update Registrar <Your Registrar Company Name> during the administrative proceedings, by sending us an e-mail at <Your Compliance Team's Email Address> or any other means found justifiable by you.

3. When the UDRP Service Provider completes its proceeding, it will inform all the parties concerned of its decision. This e-mail or attached document will either:

   1. ask the Registrar to transfer the rights of the domain name to the Complainant, or

   2. inform the Registrar that Complainant could not demonstrate infringement of Trademark and the case is nullified/dissolved, or

   3. ask the Registrar to cancel the rights of the domain name.

4. Immediately upon receipt of the UDRP Service Provider's decision, you need to reply all to the mail sent from the UDRP Service Provider that the decision will be implemented on the 11th Business Day from the day when the decision was rendered, unless you receive a Court Order from the Respondent restraining you from doing so.

5. If the Respondent so desires, he can contest the UDRP Service Provider's decision in any Court. This can only happen within 10 Business Days of the UDRP Service Provider's decision.
   On the 11th Business Day from the day when the decision was rendered, if you did not receive any Court Order, you would need to affect the UDRP Service Provider's decision.

   Process the UDRP Service Provider's decision as follows:

   • Scenario 1: The UDRP Service Provider asks the Registrar to transfer the rights of the domain name to the Complainant:

     1. Add a Customer through your Registrar Control Panel with the details of the Complainant. See details

     2. Unlock the domain name. See details

     3. Move the domain name to this New Customer Control Panel. See details

   • Scenario 2: UDRP Service Provider informs the Registrar that Complainant could not demonstrate infringement of Trademark and the case is nullified/dissolved:

     In this case, you can simply Unlock the domain name. See details

   • Scenario 3: UDRP Service Provider asks the Registrar to cancel the rights of the domain name:

     In this case, you need to Delete the domain name. See details

6. Upon performing any of the above actions, reply all to the mail sent from the UDRP Service Provider with the action taken by your team.

   Pursuant to the decision rendered by <UDRP Service Provider's Name> on Case ID - <Case No.>, Registrar <Your Registrar Company Name> confirms that, we have: not received any ruling from any Court of Law within 10 Business days from the Date of the UDRP Decision, [therefore] have created a Customer Control Panel for the Complainant - <Name, Company Name, Email Address>, sent login details to this Customer to <Complainant Email Address>, removed Registrar Lock from this domain name, moved this domain name to the Complainant, and confirmed this Move via e-mail to the Complainant.

The Uniform Domain-Name Dispute Resolution Policy (UDRP) has been adopted by ICANN-accredited Registrars in all gTLDs (.aero, .biz, .com, .coop, .info, .museum, .name, .net, .org,
.pro). The UDRP is a policy between a Registrar and its customer and is included in registration agreements for all ICANN-accredited registrars.

Through UDRP, dispute proceedings arising from alleged abusive registrations of domain names (for example, cybersquatting) may be initiated by a holder of trademark rights.

Terminology

• Complainant: the party initiating a complaint concerning a domain-name registration.

• ICANN: refers to the Internet Corporation for Assigned Names and Numbers.

• Mutual Jurisdiction: a court jurisdiction at the location of either

  • the principal office of the Registrar (provided the domain-name holder has submitted in its Registration Agreement to that jurisdiction for court adjudication of disputes concerning or arising from the use of the domain name), or

  • the domain-name holder's address as shown for the registration of the domain name in Registrar's Whois database at the time the complaint is submitted to the Provider.

• Panel: an administrative panel appointed by a Provider to decide a complaint concerning a domain-name registration.

• Panelist: an individual appointed by a Provider to be a member of a Panel.

• Party: a Complainant or a Respondent.

• Policy: the Uniform Domain Name Dispute Resolution Policy that is incorporated by reference and made a part of the Registration Agreement.

• Provider: a dispute-resolution service provider approved by ICANN. A list of such Providers appears at www.icann.org/udrp/approved-providers.htm.

• Registrar: the entity with which the Respondent has registered a domain name that is the subject of a complaint.

• Registration Agreement: the agreement between a Registrar and a domain-name holder.

• Respondent: the holder of a domain-name registration against which a complaint is initiated.

• Reverse Domain Name Hijacking: using the Policy in bad faith to attempt to deprive a registered domain-name holder of a domain name.

• Supplemental Rules: the rules adopted by the Provider administering a proceeding to supplement these Rules. Supplemental Rules shall not be inconsistent with the Policy or these Rules and shall cover such topics as fees, word and page limits and guidelines, the means for communicating with the Provider and the Panel, and the form of cover sheets.

After you have followed the process of Restoring a domain name through OrderBox, you need to manually submit a Restore Report to the Registry, to complete the Restoration process. Unfortunately, the Registry does not provide any method to automate this part. See details

It is important that you submit the Restore Report at the Registry within 5 days of receiving it. During this period, the domain name status in the Whois lookup would show Pending Restore. If the Restore Report is not submitted while the domain name is in this status, you would forfeit the fees you paid the Registry for Restoration, and the status of the domain name would revert to Pending Delete Restorable for 30 days.

To complete the Restoration for .CO/.TEL domain names, follow the below mentioned process.

Restoring a .CO/.TEL domain name at the Registry

1. Login into the Registrar Admin Tool from https://forregistrars.neulevel.biz/regadm/index.jsp.

2. Under the Domain Operations section, click the Restore Domain button.

3. On the next page, select Environment as CO-PRODUCTION (for restoring a .CO domain name) or TEL-PRODUCTION (for restoring a .TEL domain name), enter the domain name to be Restored and click the Search button.

4. The following two details are displayed -

   Sponsoring Registrar ID (Name): [Registrar Id (Registrar Name)]

   Current Expiration Date: [Day Month Date Time GMT Year]

5. Provide the following details and click the Restore button -

   • Restore Reason Code: Select

     • 1 - Registrant Error [if Action History shows only Deletion], or

     • 2 - Registrar Error [if Action History shows System Deletion]

   • Restore Comment: Mention

     • Registrant did not Renew domain name in Renewal Grace Period [if Action History shows System Deletion], or

     • Registrant Deleted domain name explicitly [if Action History shows only Deletion]

   • Select Yes for True Data and Valid Use.

6. Confirm by clicking the Restore button or if you wish to make any changes, click the Back button.

7. OrderBox would automatically check if the domain name is set Active at the Registry, and set this domain name as Active in the Control Panel and submit the Name Servers displayed in the Control Panel at the Registry.

   If this domain name was Restored after its Expiry, then the Registry typically takes 24 hours after submission of the Restore Report to update the domain name's Expiry Date to include the 1 year Renewal.

Restoring a .BIZ/.CC/.COM/.EU/.IN/.INFO/.NET/.ORG/.TV/.US domain name is a pretty straight-forward affair. You need to merely click on the Restore Domain Now button in the Order Details view of the Pending Delete Restorable .BIZ/.CC/.COM/.EU/.IN/.INFO/.NET/.ORG/.TV/.US domain name, in the Control Panel.

An Invoice is generated for your Customer that needs to be paid. When this Invoice is paid for, the cost for Restoring this domain name is Locked from your Current Debit Account Balance and a Restore command is sent to the corresponding Registry. Upon receipt of a Success message from the Registry, the Locked funds are utilized towards settling the Invoice for Restoring this domain name. See details

Within 24 hours of the completion of the above said process, the domain name is marked as Active at both the Registry as well as your Control Panel.

If a Domain Name is not renewed within 40 days of expiration, it goes into Redemption, or Pending Delete Restorable status and is deleted from the system. However, your Customers can still redeem
the domain name, by clicking on the Restore button and paying the Invoice that is generated. See details

Once the Invoice for Restoration is paid, the system executes the order and sends the Restore command to the Registry. Once this is done, a restore report is generated for the domain name, which is sent to you from
sales@logicboxes.com. You would now have to login to the Registrar Admin Tool, and submit this restore report.

Note that, until you complete the the restoration process and submit the report, the Order would remain Locked in Processing.

The following links explain the process for restoration of domain names with different Registries.

In order to curb the practice of domain tasting, where a domain name registrant uses the five day grace period (the Add Grace Period or AGP) following the registration of a domain name to test its marketability, ICANN included in its Operating Plan and Budget for the fiscal year 2008-2009 a section intended to deal with the problem of domain tasting across all gTLDs.

Accordingly, effective 1st July 2008, domain names deleted during AGP would attract the applicable ICANN transaction fee, if domain deletions for a registrar exceed 10% of its net gTLD registrations in a month (total registrations less domain names deleted during AGP), or fifty domain names, whichever is greater. See details

Let's understand the impact of the above ICANN policy through a few scenarios:

• Example I:

  Total domain Registrations under Registrar A (under all gTLDs the Registrar is accredited for) during a particular month: 2000
  
  Domain Deletions under this Registrar (under all gTLDs the Registrar is accredited for) during this month: 200
  
  Net Registrations under this Registrar (under all gTLDs the Registrar is accredited for) during this month: 1800
  
  Deletion limit allowed for this Registrar: 180 (higher value among '10% of 1800' and '50')
  
  Deletions exceeding the above limit: 200 - 180 = 20

  These 20 deletions would attract the applicable per domain ICANN transaction fee.

• Example II:

  Total domain Registrations under Registrar B (under all gTLDs the Registrar is accredited for) during a particular month: 500
  
  Domain Deletions under this Registrar (under all gTLDs the Registrar is accredited for) during this month: 40
  
  Net Registrations under this Registrar (under all gTLDs the Registrar is accredited for) during this month: 460
  
  Deletion limit allowed for this Registrar: 50 (higher value among '10% of 460' and '50')
  
  Deletions exceeding the above limit: Nil

  There would be no extra fees charged to this Registrar.

Another measure introduced by ICANN aims at restraining the gTLD Registries from issuing refunds for domain names registered and deleted during AGP, exceeding the threshold mentioned above. The Add Grace Period (AGP) Limits Policy announced by ICANN on 17 December, 2008 states that during any given month, a gTLD Registry Operator shall not offer any refund to an ICANN-accredited Registrar for any domain names deleted during the AGP that exceed (i) 10% of that Registrar's net new registrations (calculated as the total number of net adds of one-year through ten-year registrations as defined in the monthly reporting requirement of Operator Agreements) in that month, or (ii) fifty (50) domain names, whichever is greater, unless an exemption has been granted by an Operator. See details

Some Registries have deployed the policy while others have planned the deployment in the future:

The following examples should be able to clarify this Policy:

• Example I:

  Total domain Registrations for a particular gTLD, say .COM, under Registrar A during a particular month: 500
  
  .COM domain Deletions under this Registrar during this month: 60
  
  Net .COM Registrations under this Registrar during this month: 440
  
  Deletion limit allowed for this Registrar: 50 (higher value among '10% of 440' and '50')
  
  Deletions exceeding the above limit: 60 - 50 = 10

  No credit would be receivable to this Registrar from the Registry for these 10 deletions.

• Example I:

  Total domain Registrations for a particular gTLD, say .COM, under Registrar B during a particular month: 500
  
  .COM domain Deletions under this Registrar during this month: 40
  
  Net .COM Registrations under this Registrar during this month: 460
  
  Deletion limit allowed for this Registrar: 50 (higher value among '10% of 460' and '50')
  
  Deletions exceeding the above limit: Nil

  This Registrar would receive full credit for all .COM deletions during this month.

In order to ensure that the number of deletions do not exceed these limitations, you are required to closely monitor:

• total deletions under all gTLDs accredited for (as per the ICANN policy), and

• deletion of domain names under all gTLDs and specific ccTLDs (for which the Policy has been implemented), that your Registrar company is accredited for (as per the individual Registry policy).

The Registrar Admin Control Panel now allows you to generate a report to assist you in this regard.

Generating the Domain Deletion Report

1. Login into your Registrar Control Panel. See details

2. In the Mneu, point to Tools -> Reports and then click Domain Deletion Report.

3. Select the TLD from Select Product and then click the Generate report >> button.

This report lists the Total Registrations, Total Deletions, Net Registrations (Total Registrations less Total Deletions during the month) and the Deletion Percentage for the selected TLD during the current month.

Add Grace Period (AGP) Deletion Policy deployed by

In order to assist Registrars in controlling the AGP deletions under their Registrar Account, has restricted AGP deletions across the system. Deletions beyond 8% of net gTLD registrations in a month (total registrations less domain names deleted during AGP) will not be allowed.

From your Registrar Admin Control Panel, you can trace the entire hierarchy of Resellers / Sub-resellers through whom a particular domain name was registered.

Viewing the entire Reseller chain for a domain name

1. Login into your Registrar Control Panel. See details

2. Search for the domain name in question, by pointing to Products -> Domain Registration in the Menu and then clicking Search.

3. In the search results, click on the domain name. This will take you to the Order Details view.

4. Click the Reseller Chain link. This will display the Order Ownership Tree which bears the entire chain of Resellers and Sub-resellers associated with the Order, culminating with the Customer account that holds the domain name, in the following fashion:

   (You)

     
   

   Your Reseller (Reseller)

     
       

   His Sub-Reseller (Reseller)

     
   

   End Customer (Customer)

    

The Bulk Stuffing Tool in your Registrar Control Panel, allows you to add domain names to the OrderBox database, such that they are manageable by your Customers from their individual Control Panels.

Bulk Stuffing Domain Names

1. Login into your Registrar Control Panel. See details

2. In the Menu, point to Tools and click Bulk Domain Stuffing.

3. For stuffing .com/.net domain names, a different procedure needs to be followed. So, while stuffing multiple domain names, .com/.net domain names have to be stuffed separately. Select the appropriate radio button in the domain stuffing type.

   • Stuffing .com/.net domain names

     1. Upload a .txt file with all details of domain names to be stuffed, in the following format:

        "Domain Name", "Email Address", "Company Name", "Registrant First Name", "Registrant Last Name", "Address", "City",
        "State", "Country", "Postal Code", "Telephone Number", "Fax Number", "Name Server 1", "Name Server 2", "Name Server 3",
        "Name Server 4", "Name Server 5","Name Server 6"

        (Details of each domain name should be entered on a separate line. Non-compulsory details such as additional Name Server values can be simply passed blank, as """").

     2. Select the Registration Type depending upon the circumstance:

        • Domain migrated from Registrar's database - if you are in the process of moving your domain names from your old system to ours

        • Domain registered through SnapNames - if you have partnered with SnapNames and some domain names did not get automatically stuffed under your account

        • Domain registered through Pool - if you have partnered with Pool and some domain names did not get automatically stuffed under your account

     3. Now select the stuffing type by selecting the appropriate radio button.

        • If you wish to stuff the domain names under an existing Customer account, mention the Customer Username as the Email address in the file. New Contacts will be created under the specified Customer account, using the Registrant information specified in the file, and associated with the corresponding domain names.

        • If you wish to stuff the domain names under a new Customer account, provide the Reseller ID under which you wish to create the Customer account. For your direct Customers, provide your own Reseller ID.

          This will create a new Customer account for groups of domain names belonging to the same Registrant, using the Registrant information specified in the file. The Customer account will be created under the specified Reseller ID. Domain names will then be stuffed under the Customer account. New Contacts will be created under the Customer account, using the Registrant information specified in the file, and associated with the corresponding domain names.

     4. Click the Submit button.

   • Stuffing domain names other than .com/.net

     1. Upload a .txt file with a list of all domain names to be stuffed. Each domain name should be entered on a new line.

     2. Select the Registration Type depending upon the circumstance:

        • Domain migrated from Registrar's database - if you are in the process of moving your domain names from your old system to ours

        • Domain registered through SnapNames - if you have partnered with SnapNames and some domain names did not get automatically stuffed under your account

        • Domain registered through Pool - if you have partnered with Pool and some domain names did not get automatically stuffed under your account

     3. Now select the stuffing type by selecting the appropriate radio button.

        • If you wish to stuff the domain names under an existing Customer account, provide the Customer ID for this account.

        • If you wish to stuff the domain names under a new Customer account, provide the Reseller ID under which you wish to create the Customer account. For your direct Customers, provide your own Reseller ID.

          In this case, the Customer account created will have the same profile details as the Registrant Contact for the domain names.

     4. Click the Submit button.

4. OrderBox will now display a report of:

   • all correctly and incorrectly formatted domain names in the uploaded file, so that you may correct these, and

   • the Customer account, under whom you wish to stuff these domain names (if you are stuffing under an existing Customer).

5. Click the Proceed button to submit the domain names to the Bulk Stuffing queue.

   You will receive an e-mail from us, confirming that these domain names have been added successfully to the queue. After these domain names have been stuffed, you will receive another mail with details of all successful stuffing along with any failures.

The OrderBox offers a feature-rich experience to all its users, in order to manage their domain names and all related services in an efficient manner.

Apart from all the common offerings, your Registrar Control Panel also provides certain additional features, to effectively administer domain names registered through your Registrar. These features are not accessible through any Reseller/Customer Control Panel.

Find here a guide to these features.