This policy will apply from 6 April 2010. Please view the current version of the AUP here.

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

Introduction

In the past we have experienced persistently large volumes of create 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.

General use of our Automaton service

There are generally no specific limits set on the level of use of Automaton commands, other than the specific limits on the use of the create and delete commands set out below.

Notwithstanding the above, it is not acceptable to use the Automaton service, or knowingly or recklessly permit others to use the Automaton service:

1. so as to interfere with the use of the Automaton by other customers or authorised users;
2. in a manner which does, or is designed to, harass or cause a denial-of-service to any other user of the Automaton service; or 
3. in a manner which causes or is likely to cause an interruption or degradation of, interference with, or disproportionate burden on the operations of the Automaton service, regardless of whether such interruption, degradation, interference or burden is the result of the registrar’s actions or those of a third party over which the registrar has no control.
   

If, in Nominet’s reasonable opinion, a registrar is using the Automaton service in such an unacceptable manner Nominet will take such steps as it deems appropriate to stop the unacceptable use including, but not limited to, suspending, restricting or terminating the registrar’s access to or use of some or all of Nominet’s registrar systems.

Use of create 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 create operations attempted on names that already exist and EPP create commands on names that already exist 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, but use of the EPP check command, modifications and queries (for domains on their tag) will be permitted.  The registrar will be notified of the block by an automatic email.  The block will be automatically lifted upon expiry of the 24-hour period.   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.

Use of the delete and investigation lock operations

The instructions for use of the delete and investigation lock operations clearly state their intended use.  Any other use of these commands is misuse and may lead to blocking and/or having the commands selectively blocked, disabled or withdrawn.

In order to protect our systems we impose a limit on the sum total of delete and investigation lock operations on new registrations.  The delete and investigation lock operations are limited to 5 or 5% of uninvoiced registrations, whichever is higher, within the following effective period:

• From the 1st of the month to the 7th of the month, the limits are calculated back to the beginning of the previous month.
• From the 8th of the month to the end of the month, the limits are calculated back to the beginning of the same month.  (This means domain names deleted or locked between the 1st and 7th are counted in two consecutive months)

If this limit is exceeded, the delete and investigation lock operations are automatically disabled for new registrations on that tag.  These operations will remain disabled until:

• the registrar has registered enough domain names to permit further operations under the 5% limit or
  
• midnight on the 7th of the following month when the limit is automatically reset.

If you need to delete or lock more domain names than the limit allows, then please contact us at hostmaster@nominet.org.uk.

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.

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.

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.