This Acceptable Use Policy describes actions that Realtime Register prohibits when any party uses the Realtime Register Services. The Realtime Register Services may not be used in any illegal, abusive or other manner that interferes with the business or activities of any other party. The following list gives examples of prohibited actions. This list is provided by way of example and should not be considered exhaustive.

• Attempting to bypass or break any security mechanism on any of the Realtime Register Services or using the Realtime Register Services in any other manner that poses a security or service risk to Realtime Register or any of its users.
• Testing or reverse-engineering the Realtime Register Services in order to find limitations, vulnerabilities or evade filtering capabilities.
• Launching or facilitating, whether intentionally or unintentionally, a denial of service attack on any of the Realtime Register Services or any other conduct that adversely impacts the availability, reliability or stability of the Realtime Register Services.

Unacceptable use

As unacceptable use is considered:

• Excessive and, or unnecessary querying.
• Generating a substantial number of avoidable error messages.
• Generating avoidable system load with unnecessary or useless commands.
• Other actions that harms the interests of Realtime Register, its partners or customers.

Guidelines

By following the guidelines below you are assured of a responsive and uninterrupted use of the Realtime Register domain name registration and management platform.

• Do not send repeated requests with a questionable chance of being successful. The Realtime Register systems do not support drop catching.
• Use the isProxy to check the availability of the domain name, instead of checking it through the WHOIS or the check domain call.
• Keep a parallel administration locally and query this first for information needs about unchanged objects. This will avoid excessive and, or unnecessary querying.
• Large scale operations, like bulk actions on domains or other objects, should be submitted sequential. Keep a minimum of one second between the requests. Custom arrangements can be discussed for special projects.
• The number of requests and, or connections should be proportionate to the number of domains registered in the account.
• Follow and respond to instructions of the Realtime Register technical support staff.

Best practices

• Check the availability of an object before attempting to create it.