This is the acceptable use policy for our EPP service. As with our acceptable use policies generally, our linking principles apply.

Introduction

As detailed in our Automaton AUP, we have experienced a number of problems in the past that have required us to prevent or limit certain functionality of our registrar systems.  Our EPP service has the same controls in place.

Many of the limits given here are now combined with certain limits on the Automaton and exceeding those on one or other of the systems will trigger a block on both systems.

Use of create and check commands on already registered names

The acceptable limits are set per registrar, per rolling 24 hours and apply to the create command attempted on names that already exist. In addition these are aggregated with the Automaton REQUEST operations and with EPP check commands on domain names registered to other tags. The limit is:

• The combined number of EPP create commands on names that already exist, EPP check commands on names registered to other tags and Automaton REQUEST operations attempted on names that already exist must not exceed 1,000 in any 24 hour period.

If exceeded, all tags for that registrar will be blocked from making any new registrations for 24 hours and from using the domain check operation, but modifications and queries (for domains on their tag) will be permitted.  The registrar will be notified of the block in the EPP create and check responses.

If the requests do not cease as a result then we may block all access for that registrar. The block will be automatically lifted upon expiry of the 24-hour period.

Use of delete command

The intended use of the delete command is clearly stated in the instructions for use.  Any other use of this command is misuse and may lead to blocking and/or having the delete command selectively blocked or withdrawn.

In order to protect our systems we impose a limit on EPP delete commands combined with Automaton delete operations.  This limit is 5 or 5% of domains that have been registered but not yet invoiced, whichever is the higher.   The effective period is calculated as follows:

• From the beginning of the month to the end of the month, the period is calculated back to the beginning of the same month.
• From the beginning of the month to the 7th of the month, the period is also calculated back to the beginning of the previous month.

This does mean that any uninvoiced domain deleted between the 1st and 7th is counted in two consecutive months.

If the limit is exceeded, the use of the delete command is automatically suspended for that tag. This suspension will last until after the next invoicing run at midnight on the 7th of the following month, or until the registrar has registered sufficient domains to permit further deletions.

However this does not mean that there is an acceptable limit on the use of the delete command irrespective of the reason for the deletion.  If we believe that any domains are being cancelled in violation of the intended use then we will take action.  If you need to delete more domains than are allowed by this limit, which fall within the intended use of the delete command, then please contact us to discuss this further.

Other commands

There are no specific limits sets for other commands

Using the update, transfer or renew commands on domains on another tag may well be treated as abuse and so result in the registrar's tag being immediately blocked

Linked tags

This policy is covered by our standard anti-avoidance clause, which may mean that we link tags together when calculating the above limits.

Simultaneous connections

Each tag is limited to four simultaneous connections to the EPP service.  The IP addresses used by each tag must be set in advance through our online service.  If more than four connections are opened then the oldest connection will be forcibly closed.

Further escalation

Tags that necessitate persistent blocking will be contacted and dealt with under the Registrar Agreement and Good Practice Terms.