domorder

Domain Products

Transfer-In without Auth-code

Before proceeding with the Transfer, you are advised to first check the following:

  • confirm if your domain name can be
    transferred
    . See details

  • check if you require to obtain a Domain (Transfer) Secret or Authorization Code (known as Unique Domain Authentication ID (UDAI) for .NZ domain
    names) for your domain name prior to placing a Transfer
    request. See details

Note
  • Once a .TEL domain name is Transferred to your account under , our system automatically assigns a new .TEL
    Hosting Control Panel and sends the login details to the Registrant Contact. This results in deletion of the .TEL Hosting Control Panel with the Losing (Old)
    Registrar
    .

    Hence, before initiating the Transfer of a .TEL domain name to , you need to create a
    backup (Anchor: backup-restore) of the data under the .TEL Hosting Control Panel
    with the old Registrar and download it to your local computer. Once the domain name has been transferred (to
    ), you may restore the data from within the .TEL Hosting Control Panel provided by
    .

  • Upon Transferring-In your .XXX domain name, the system will submit the Registrant's full name and email address as recorded in the Contact database to the .XXX Registry,
    so that the Registry may contact the Registrant to self-certify as a Member of the
    adult-community. See details

Once you have confirmed the above, you may place a Transfer request for your domain name with .

Instructions for Customers

  1. Login to your Customer Control
    Panel
    . See details

  2. In the Menu, point to Domains -> Domain Registration and then click Transfer.

  3. Now, enter the domain name you wish to Transfer and the Domain (Transfer) Secret Key/Authorization Code.

    Note

    .ES domain names do not require a Domain (Transfer) Secret Key/Authorization Code.

  4. Select the various Contacts (Registrant, Admin, Technical & Billing Contact) for this domain name.
    You may select from the available list of Contacts or Add a New Contact.

    Note

    In case of a .NZ domain name, you need to select only the Registrant Contact, since a .NZ domain name has only a Registrant Contact associated with it.

  5. You may choose to enable Privacy Protection for your domain name by selecting the Privacy Protection check box.

    Additional Information

    Privacy Protection

  6. Next, select the check box to agree to the associated Product Agreement(s).

    Note

    This is a mandatory action.

  7. Proceed with the Payment of the Invoice.

    Additional Information

    Paying for an Invoice

  8. After you have placed the Transfer Order, the Administrative Contact for the domain name will receive an e-mail from
    for the Transfer Authorization process, which needs to be approved within 5 days.

  9. Note
    • If the Administrative Contact does not approve the Transfer within 5 days, it is assumed that the Admin Contact does not wish for the Transfer to complete and
      the Order is deleted in our system.

    • Transfer of a .NZ domain name does not involve seeking approval by the Registrant Contact through email/FAX. Once a Transfer request is initiated, the .NZ Registry
      authenticates the Transfer through the provided Unique Domain Authentication ID (UDAI) and completes the Transfer instantly.

      The Transfer of a .NZ domain name will result in generation of a new Unique Domain Authentication ID (UDAI). This process is implemented from a security perspective.

    • To Transfer your .DE domain name to , you need to only provide your Domain (Transfer) Secret Key/Authorization Code.
      Once we get confirmation from the Registry that the Domain (Transfer) Secret Key/Authorization Code is accurate, the domain name is instantly transferred without the need of receiving
      additional confirmation from the Registrant / Administrative Contact, via email or FAX.

    • Upon placing a Transfer request for your .ES domain name to , the .ES Registry will email the Admin Contact listed in
      the Whois of the domain name. The Admin Contact must click the approval link within 10 days to confirm the Transfer. If the approval link is not clicked
      or the decline link is clicked, the domain name will continue being registered with the current Registrar.

    • Upon placing a Transfer request for a .AU domain name, would be emailing the Registrant Contact
      for his approval.

  10. After clicking the approval link in the Transfer Authorization email, the Administrative Contact needs to provide the Domain (Transfer) Secret Key/Authorization Code. Alternatively, you can provide the Domain (Transfer) Secret Key/Authorization Code from within your Control Panel:

    1. Login to your Control Panel, search for the domain name being transferred and proceed to the Order Information view. See details

    2. Click the link within Click here to submit your Authorization Code..

    3. Provide the Domain (Transfer) Secret Key/Authorization Code and click the Submit button.

  11. Once the mail has been approved by the Administrative Contact and the Domain (Transfer) Secret Key/Authorization Code submitted, the Current Registrar will be notified regarding the transfer.

    The Current Registrar will send an e-mail to the Registrant and/or the Administrative Contact of the concerned domain name to confirm that they wish to Transfer their domain name.
    If the Transfer is not denied by either the Registrant or the Administrative Contact or the Current Registrar, the domain name will be Transferred to you under
    in the next 5 days.

Note

Instructions for Resellers

  1. Login to your Reseller Control Panel. See details

  2. In the Menu, point to Products -> Domain Registration and then click Transfer.

  3. Now, enter the domain name you wish to Transfer and the Domain (Transfer) Secret.

    Note

    .ES domain names do not require a Domain (Transfer) Secret Key/Authorization Code.

  4. Enter the Username (Email Address) of the Customer, on whose behalf you wish to Transfer this domain name. If the Customer is new, you
    can Add the Customer, by filling the form given there.

  5. Select the various Contacts (Registrant, Admin, Technical & Billing Contact) for this domain name.
    You may select from the available list of Contacts or Add a New Contact.

    Note

    In case of a .NZ domain name, you need to select only the Registrant Contact, since a .NZ domain name has only a Registrant Contact associated with it.

  6. You may choose to enable Privacy Protection for your domain name by selecting the Privacy Protection check box.

    Additional Information

    Privacy Protection

  7. Next, select the check box to agree to the associated Product Agreement(s).

    Note

    This is a mandatory action.

  8. Proceed with the Payment of the Invoice.

    Additional Information

    Paying for an Invoice

  9. After you have placed the Transfer Order, the Administrative Contact for the domain name will receive an e-mail from
    for the Transfer Authorization process, which needs to be approved within 5 days.

    Note
    • If the Administrative Contact does not approve the Transfer within 5 days, it is assumed that the Administrative Contact does not wish for the Transfer to complete and
      the Order is deleted in our system.

    • Transfer of a .NZ domain name does not involve seeking approval by the Registrant Contact through email/FAX. Once a Transfer request is initiated, the .NZ Registry
      authenticates the Transfer through the provided Unique Domain Authentication ID (UDAI) and completes the Transfer instantly.

      The Transfer of a .NZ domain name will result in generation of a new Unique Domain Authentication ID (UDAI). This process is implemented from a security perspective.

    • To Transfer your .DE domain name to , you need to only provide your Domain Transfer Secret / Authorization Key.
      Once we get confirmation from the Registry that the Domain Transfer Secret / Authorization Key is accurate, the domain name is instantly transferred without the need of receiving additional
      confirmation from the Registrant / Administrative Contact, via email or FAX.

    • Upon placing a Transfer request for your .ES domain name to , the .ES Registry will email the Admin Contact listed in
      the Whois of the domain name. The Admin Contact must click the approval link within 10 days to confirm the Transfer. If the approval link is not clicked
      or the decline link is clicked, the domain name will continue being registered with the current Registrar.

    • Upon placing a Transfer request for a .AU domain name, would be emailing the Registrant Contact
      for his approval.

  10. After clicking the approval link in the Transfer Authorization email, the Administrative Contact needs to provide the Domain (Transfer) Secret Key/Authorization Code. Alternatively, the Domain (Transfer) Secret Key/Authorization Code can be submitted by the Customer from within his Customer Control Panel:

    1. Login to the Customer Control Panel, search for the domain name being transferred and proceed to the Order Information view. See details

    2. Click the link within Click here to submit your Authorization Code..

    3. Provide the Domain (Transfer) Secret Key/Authorization Code and click the Submit button.

  11. Once the mail has been approved by the Administrative Contact and the Domain (Transfer) Secret Key/Authorization Code submitted, the Current Registrar will be notified regarding the transfer.

    The Current Registrar will send an e-mail to the Registrant and/or the Administrative Contact of the concerned domain name to confirm that they wish to Transfer their domain name.
    If the Transfer is not denied by either the Registrant or the Administrative Contact or the Current Registrar, the domain name will be Transferred to you under
    in the next 5 days.

Note

Check Availability - IDN

Description

Checks the availability of the specified Internationalized Domain Name(s) (IDN).

Parameters

Name Data Type Required / Optional Description
auth-userid Integer Required Authentication Parameter
api-key String Required Authentication Parameter
domain-name Array of Strings Required

Internationalized Domain Name(s) that you need to check the availability for

Refer to the supported character sets mentioned below:

Note

The domain name used in the API call can be in Unicode (the native language) or in Punycode format.

Example: The domain name can be provided as ѯҋ111 (Unicode) or xn--111-dkd4l (Punycode).

domain-name=ѯҋ111
domain-name=xn--111-dkd4l

tld String Required TLD for which the domain name availability needs to be checked See details
idnLanguageCode String Required

While performing check availability for an Internationalized Domain Name, you need to provide the corresponding language code:

  • .ASIA IDN: The language code depends upon the language whose characters are used in the domain name. Supported languages and the corresponding language codes are:

    • Chinese - zh

    • Japanese - ja

    • Korean - ko

    idnLanguageCode=ko

  • .BIZ IDN: The language code depends upon the language whose characters are used in the domain name. Supported languages and the corresponding language codes are:

    • Chinese - zh

    • Danish - da

    • Finnish - fi

    • German - de

    • Hungarian - hu

    • Icelandic - is

    • Japanese - jp

    • Korean - ko

    • Lithuanian - lt

    • Latvian - lv

    • Norwegian - no

    • Polish - pl

    • Portuguese - pt

    • Spanish - es

    • Swedish - sv

    idnLanguageCode=ko

  • .CA IDN: The language code needs to be mentioned as fr.

    idnLanguageCode=fr

  • .CC / .TV IDN: The language code depends upon the language whose characters are used in the domain name. You can refer to the list of languages supported and the corresponding language code.

    idnLanguageCode=aze

  • .CO IDN: The language code depends upon the language whose characters are used in the domain name. Supported languages and the corresponding language codes are:

    • Chinese - zh

    • Danish - da

    • Finnish - fi

    • Icelandic - is

    • Japanese - jp

    • Korean - ko

    • Norwegian - no

    • Spanish - es

    • Swedish - sv

    idnLanguageCode=da

  • .COM / .NET IDN: The language code depends upon the language whose characters are used in the domain name. You can refer to the list of languages supported and the corresponding language code.

    idnLanguageCode=aze

  • .DE IDN: The language code needs to be mentioned as de.

    idnLanguageCode=de

  • .ES IDN: The language code needs to be mentioned as es.

    idnLanguageCode=es

  • .EU IDN: The language code needs to be mentioned as latin.

    idnLanguageCode=latin

  • .IN.NET IDN: The language code depends upon the language whose characters are used in the domain name. Supported languages and the corresponding language codes are:

    • Arabic - ara

    • Chinese - chi

    • Cyrillic - cyr

    • Greek - gre

    • Hebrew - heb

    • Japanese - jpn

    • Korean - kor

    • Lao - lao

    • Latin - lat

    • Thai - tha

    idnLanguageCode=jpn

  • .INFO IDN: The language code depends upon the language whose characters are used in the domain name. Supported languages and the corresponding language codes are:

    • Danish - da

    • German - de

    • Hungarian - hu

    • Icelandic - is

    • Korean - ko

    • Lithuanian - lt

    • Latvian - lv

    • Polish - pl

    • Spanish - es

    • Swedish - sv

    idnLanguageCode=ko

  • .NAME IDN: The language code depends upon the language whose characters are used in the domain name. You can refer to the list of languages supported and the corresponding language code.

    idnLanguageCode=aze

  • .ORG IDN: The language code depends upon the language whose characters are used in the domain name. Supported languages and the corresponding language codes are:

    • Chinese - zh-cn (for IDN.org domain name and .机构 domain name - the Chinese IDN for .org)

    • Cyrillic - ru (for .орг domain name - the Russian IDN for .org)

    • Danish - da

    • German - de

    • Hindi - hin-deva (for .संगठन domain name - the Hindi IDN for .org)

    • Hungarian - hu

    • Icelandic - is

    • Korean - ko

    • Latvian - lv

    • Lithuanian - lt

    • Polish - pl

    • Spanish - es

    • Swedish - sv

    idnLanguageCode=ko

  • .PW IDN: The language code depends upon the language whose characters are used in the domain name. Supported languages and the corresponding language codes are:

    • Arabic - ara

    • Chinese - chi

    • Cyrillic - cyr

    • Greek - gre

    • Hebrew - heb

    • Japanese - jpn

    • Korean - kor

    • Lao - lao

    • Latin - lat

    • Thai - tha

    idnLanguageCode=tha

  • .TEL IDN: The language code depends upon the language whose characters are used in the domain name. Supported languages and the corresponding language codes are:

    • Chinese - zh

    • Danish - da

    • Finnish - fi

    • French - fr

    • German - de

    • Hungarian - hu

    • Icelandic - is

    • Japanese - jp

    • Korean - ko

    • Latvian - lv

    • Lithuanian - lt

    • Norwegian - no

    • Polish - pl

    • Portuguese - pt

    • Russian - ru

    • Spanish - es

    • Swedish - sv

    idnLanguageCode=ko

  • CentralNic IDN: The language code depends upon the language whose characters are used in the domain name. Supported languages and the corresponding language codes are:

    • .EU.COM:

      • Arabic - ara

      • Cyrillic - cyr

      • Greek - gre

      • Hebrew - heb

      • Latin - lat

    • .GB.COM, .QC.COM, .DE.COM, .GB.NET, .NO.COM, .HU.COM, .UY.COM, .ZA.COM, .BR.COM, .SE.COM, .SE.NET, .UK.COM and .UK.NET:

      • Latin - lat

    • .AE.ORG and .SA.COM:

      • Arabic - ara

    • .KR.COM:

      • Korean - kor

    • .US.COM:

      • Arabic - ara

      • Chinese - chi

      • Cyrillic - cyr

      • Greek - gre

      • Hebrew - heb

      • Japanese - jpn

      • Latin - lat

    • .GR.COM:

      • Greek - gre

    • .JPN.COM:

      • Japanese - jpn

    • .CN.COM:

      • Chinese - chi

    • .RU.COM:

      • Cyrillic - cyr

    idnLanguageCode=lat

  • .在线 (Chinese IDN for .online): The language code needs to be mentioned as zh.

    attr-name1=idnLanguageCode&attr-value1=zh

  • .中文网 (Chinese IDN for .network): The language code needs to be mentioned as zh.

    attr-name1=idnLanguageCode&attr-value1=zh

  • .भारत (Hindi IDN for .BHARAT): The language code needs to be mentioned as hin-deva.

    attr-name1=idnLanguageCode&attr-value1=hin-deva

HTTP Method

GET

Example Test URL Request


https://domaincheck.httpapi.com/api/domains/idn-available.json?auth-userid=0&api-key=key&domain-name=ѯҋ111&domain-name=ѯҋ112&tld=com&idnLanguageCode=aze

Response

Returns a hash map containing domain name availability status for the requested TLDs:

  • available - domain name available for registration

  • regthroughus - domain name currently registered through the Registrar whose connection is being used to check the availability of the domain name

  • regthroughothers - domain name currently registered through a Registrar other than the one whose connection is being used to check the availability of the domain name. If you wish to manage such a domain name through your Reseller / Registrar Account, you may pass a Domain Transfer API call. See details

  • unknown - returned, if for some reason, the Registry connections are not available. You should ideally re-check the domain name availability after some time.

    Note

    In case of .CA TLD, domain name availability can be checked for a maximum of 15 strings in one API call. Including more than 15 strings in an API call will return the status as unknown for all the strings.

Responding to a UDRP Service Provider's Request for Registrar Verification

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.

Note
  • Verify that you are the Sponsoring Registrar of this domain name.

  • Always store the official UDRP Complaint, safely and make it readily accessible to your Compliance Team.

  • Upon receipt of a complaint from any UDRP Service Provider, you are expected to respond to it within 48 hours.

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].

  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.

Uniform Domain-Name Dispute Resolution Policy

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.

Additional Information

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.

Restoring .CO/.TEL Domain Names

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 .BIZ/.CC/.COM/.EU/.IN/.INFO/.NET/.ORG/.TV/.US Domain Names

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.

Restoration of Domain Names

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.