Introduction

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

In the past we have experienced persistently large volumes of REQUEST or QUERY operations for domains that are already registered and on another tag.  This behaviour causes the following problems:

• delays for other automaton users
• significant mail congestion in the automaton mail queues as the automaton replies are sent at a higher rate than can be accepted by the registrar’s mail gateway.
• large volumes of effectively unnecessary log file entries per day
• the cost of building an infrastructure larger than required
• unnecessary work for the automaton leading potentially to a greater exposure of the automaton to faults
  

In addition, we have seen the first signs of the practice of ‘domain tasting’.  This is where a domain name is registered, tested for commercial viability using a pay-per-click site (or similar) and then cancelled before invoicing if sufficient pay-per-click revenue is not generated. This practice is not an acceptable use of our systems.  It creates load on our systems that is not paid for, putting an unfair burden on other registrants and users.

Use of REQUEST operation on already registered names

The acceptable limits are set per registrar, per rolling 24 hours and apply to operations attempted on names that already exist.  The limit is:

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

If exceeded, the tags will be blocked from making any new registrations for 24 hours and from using the EPP check operation, but modifications and queries (for domains on their tag) will be permitted.  The registrar will be notified of the block by an automatic email but if the requests do not cease as a result, the registrar's PGP key for that tag will be disabled, preventing any further use of the automaton and they will be asked to contact the support team. The block will be automatically lifted upon expiry of the 24-hour period.

Use of DELETE operation

The intended use of the DELETE operation 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 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 operation 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 operation.  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 operation, then please contact us to discuss this further.

Other operations

There are no specific limits sets for MODIFY, RELEASE or RENEW operations.

Using the MODIFY, RELEASE or RENEW operations 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.

SMTP Connections

The intended purpose of the Automaton is to receive emails from multiple registrars. Some registrars have been deliberately holding open SMTP connections for very long periods to aid the early registration of cancelled domains. This causes considerable problems for the Automaton because it requires it hold open many more email connections than necessary and interferes with normal message processing.
 
We put a limit of one hour for any SMTP connection to stay open and where possible this is enforced by the Automaton, which will disconnect any connection that is held open for longer. Any attempt to hold open a connection for longer than one hour is may be treated as abuse and so result in the registrar's tag being immediately blocked.

Failure to provide a valid email address for automaton replies

Registrars who fail to provide a valid email address for automaton replies will be blocked automatically and asked via an email to the administration contact shown in the tag database to contact the support team.

Failure to accept delivery attempts of automaton replies

Registrars who fail to accept delivery attempts of automaton replies will be blocked automatically and asked via an email to the administration contact shown in the tag database to contact the support team.

Further escalation

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