Latest revision as of 20:19, 21 September 2022

ERRP - Expired Registration Recovery Policy

The Expired Registration Recovery Policy is intended to help align registrant expectations with registrar practices by establishing certain minimum communications requirements and making renewal and redemption of registrations uniformly available in prescribed circumstances. Essentially, formalizing the process of renewal and redemption for all gTLDs.

[edit] ERRP Overview

[edit] Rationale for the ERRP Policy

• To help prevent unintended non-renewal of domain name registrations, registrars will be required to notify registered name holders of the expiration of their registrations at least two times: approximately one month prior to the expiration date and, again, approximately one week prior to the expiration date.
• All gTLD registries must offer a Redemption Grace Period of 30 days immediately following the deletion of a registration. (Sponsored gTLDs are exempt, and not required to offer a Redemption Grace Period.) During the Redemption Grace Period, the registrant must be permitted by its registrar to restore the deleted registration.
• To promote consumer choice and awareness, registrars must make their renewal and redemption fees reasonably available to registered name holders and prospective registered name holders at the time of registration of a domain name.
• As in the past, registrars may delete registrations at any time after they expire, subject to applicable consensus policies and provisions of the Registrar Accreditation Agreement. However, the ERRP requires that resolution of the domain name be interrupted for a period of time after expiration, but before deletion, of the name to help make the registrant aware of the expiration of its name. Additionally, any parking page hosted by the registrar at the expired domain name must include or point to renewal instructions.

[edit] ERRP For Resellers

• All required ERRP notifications must be sent out from the Registrar of Record, therefore, notifications will use the generic email address of [email protected].
• Resellers can brand these notifications for their own customers through the Control Panel (see Notification Branding below)
• Resellers ARE REQUIRED to clearly display Renewal and Restoration information on their websites, including information about ERRP renewal notices and how ERRP notices will be delivered (see Resellers Terms of Use below)
• Resellers ARE REQUIRED to clearly display Registrant renewal pricing, restore pricing (Redemption Grace Period (RGP)) fees and how to access renewal/restore information - meaning that resellers must post renewal and restore fees on their pricing page as well as link to these prices in their own terms of use.

[edit] ICANN Policy

• Official ERRP Policy Page
  

HISTORY
At the request of ICANN's At-Large Advisory Committee, on 5 December 2008, ICANN published an ISSUES REPORT on the topic of Post-Expiration Domain Name Recovery. The Generic Names Supporting Organization Council ("GNSO") initiated a Policy Development Process in May 2009, which resulted in the submission of several policy and process recommendations to the ICANN Board of Directors. The ICANN Board adopted the policy recommendations on 28 October 2011, and directed ICANN staff to implement this policy.

A period for public comment on the Expired Registration Recovery Policy opened on 11 October 2012 and closed on 18 November 2012. The period for reply opened on 19 November 2012 and closed on 7 December 2012. ICANN has reviewed the comments submitted, and where appropriate, incorporated suggested modifications into the Expired Registration Recovery Policy.

[edit] Email Templates & Reseller Branding

Resellers are able to brand the ERRP notifications through HEXONET's Control Panel. The instructions are below:

• Login to the Control Panel and navigate to Reseller Controls > Product Settings > Domain Settings > Default ERRP Email Settings
• Configure the following fields and these values will be automatically inserted into the ERRP notifications for the Reseller's customers.

* Company Name - provide the company name to be used in the email
* Renewal Website URL - Instructions on how your customers can renew their domains
* Telephone Number - A customer service number
* Support Email Address - A direct email for support and used as 'Reply-To' address
* Legal URL - a link to your Terms of Use or another legal page  
* Signature - a footer of up to four lines

• IMPORTANT - there is no "FROM" email-address option however your Company Name will be set as sender name and your Support Email Address will be stated in the email and will be used as 'Reply-To' address
• For resellers who choose not to configure any of the branding fields, your clients will see a generic email without extra information or links.

Sample Email Template

HEADER From: X-ERRP-RSP <[email protected]>

Reply-To: X-ERRP-EMAIL

To: REGISTRANTEMAILADDRESS

Subject: IMPORTANT - Domain Expiry Notification

BODY Upcoming Expiring Domains in Approximately a Month

Dear REGISTANTNAME:

As the Registrant of the domains listed below, this email is to notify you that the following domains are about to expire in approximately one month. If you wish to keep any or all of these domains, it is important that you renew your domains through your Domain Service Provider before their respective expiration dates. Please note that restoring an expired domain is more expensive, therefore please consider renewing the domains you wish to keep today.

<BEGIN OPTIONAL CONTACT DETAILS. ONLY INCLUDED IF AT LEASE ONE OF X-ERRP-URL, X-ERRP-EMAIL, OR X-ERRP-PHONE IS PROVIDED>

You can reach your Domain Service Provider here:

URL: X-ERRP-URL

EMAIL: X-ERRP-EMAIL

PHONE: X-ERRP-PHONE

<END OPTIONAL CONTACT DETAILS>

Terms and Conditions of your Domain Service Provider are available at: X-ERRP-TAC-URL

<Domain List>

Domain Name | Expiration Date

...

<BEGIN OPTIONAL FOOTER. ONLY INCLUDED IF AT LEAST X-ERRP-SIGNATURE0, X-ERRP-SIGNATURE1, X-ERRP-SIGNATURE2, OR X-ERRP-SIGNATURE3 IS PROVIDED>

X-ERRP-SIGNATURE0

X-ERRP-SIGNATURE1

X-ERRP-SIGNATURE2

X-ERRP-SIGNATURE3

<END OPTIONAL FOOTER>

[edit] Reseller Terms of Use

For Resellers to be in compliance with the ERRP, the follow or similar wording must be in the Reseller's own terms of use with their customers.

1. Renewal Notices. Approximately one month prior to the expiration date of a domain name, the registrant will be emailed an expiration notice to the registrant's email address. Subsequently, approximately one week prior to the expiration date of a domain name, a second notice will be emailed to the registrant's email address. And if a domain is not renewed, within five (5) days of a domain name's expiration date, the registrant will be emailed a third notice stating the domain name has expired.
2. Renewal and Restore Fees. The fees associated with renewing gTLDs are located on the Reseller's website at URL: <<http://myresellersite.com/fees>>

[edit] FAQs

1. When does the Expired Registration Recovery Policy (ERRP) policy become effective?

   ICANN requires ERRP policy to be effective starting on August 31, 2013

2. How many ERRP email notices will be sent out to my customers?

   Each and every EXPIRING domain must receive up to three (3) notices - approximately one month and one week before the expiration date of a domain and five (5) days after. Bulk domain notifications will be sent in the same single email if domains are expiring at approximately the same date range

3. Can I specify the sender email address on a per domain and per account basis?

   No. All notices will be sent from a generic and and non-descriptive email address but you can specify the sender name and a Reply-To email address on a per domain and per account basis

4. Can the ERRP email be branded?

   Yes. Login into the Control Panel and navigate to MANAGE ACCOUNT > MY SETTINGS > DOMAIN SETTINGS > ERRP EMAIL SETTINGS where you can set a default branding for all ERRP notices going to your customers. In addition it is also possible to set the branding on a per domain basis

5. Where should renewal fees be displayed on my website?

   On any one or all of the following pages - homepage, pricing page, or terms of use page. Some resellers will also display prices in the customer login area of their website

6. Which fees do I have to display if I sell domains as a package with hosting?

   According to the ERRP policy, the domain renewal and domain restore price must clearly be displayed. If you only offer bundles, then the bundle price must include the renewal and/or restore price

7. Will ERRP emails be sent out if the domain is in AUTORENEW status?

   Yes. ICANN requires ERRP notices to be sent until the renewal is finalized. If a domain is set to AUTORENEW only the two pre-expirey (2) ERRP emails will be sent (approximately one month and one week before the expiration date)

8. Will HEXONET park Reseller's expired domains?

   No. Though we are looking at offering Parking Services to our Resellers in the coming months

9. Will HEXONET sell Reseller's expired domain if they are in redemption or are on HOLD status?

   No. Though we are looking at offering Auction Services to our Resellers in the coming months

10. Which TLDs does the ERRP policy apply?

    Only gTLDs are affected by the ERRP policy, all ccTLDs are excluded

11. When will a domain stop resolving?

    Only for gTLDs that are set to AUTODELETE/AUTOEXPIRE, the DNS resolution will be interrupted 36 days after expiration. This is eight days before deletion

12. Can I still transfer a domain if it is not resolving any more?

    Yes. It is still possible to transfer a domain

13. Is ERRP wording required in my general terms and conditions or TLD regulations?

    Not officially, but we recommend that you do update your terms of use with the wording we provided in our notice and this wiki

14. Can I activate my domain with a simple RENEW if it stopped resolving?

    Yes. Until a domain is deleted you can simply renew it

15. How I could prevent or stop the ERRP notice from being sent out for a domain?

    If you explicitly RENEW your domain at least 30 days before the expiration date no ERRP notice will be sent out.

If you explicitly RENEW your domain at least 7 days before deletion only the first ERRP notice (approximately one month before the expiration date) will be sent out.
16. If a domain is configured to AUTORENEW or if you explicitly RENEW your domain at least one day after expiration only the two ERRP pre-expirey notices (approximately one month and one week before the expiration date) are sent out