Openprovider Fair Use Policy

Version 2020-06-10

At Openprovider, we believe in building systems that all our customers will enjoy working with. That means that we do not impose many restrictions on our customers, but also expect from our customers that their behaviour is reasonable. What do we expect from you?

The Openprovider system in general

  • Security: get acquainted with and take advantage of all the security measures that Openprovider offers. For example, create an account for every employee instead of sharing an account, choose strong passwords, enable two factor authentication and configure IP whitelists. Refer to our blog post for more information.
  • Excessive use: you can use the control panel freely, but don’t script calls to the control panel. If you want to perform repetitive queries, use our bulk tools in the control panel or our API.

Openprovider API

When using the API, we expect the following from you:

  • Security: use a hash value instead of plain password for interaction with our API, and whitelist your IP addresses.
  • Excessive querying: if a command fails, don’t repeat it unaltered as it will fail again. Instead, investigate the error and fix it before trying again. A special case of this behavior is dropcatching domains; this is covered below under “Domain management”. We have API limits in place that are reviewed and adapted as necessary. Exceeding those limits may lead to blocking your API access.
  • Bulk operations: while the API is intended for bulk operations, we prefer if you let us know when you expect to do 10.000 or more orders or updates on products in a day. Not only to protect our own systems, but also to advise you if any of our suppliers have limits in place.

Domain management

Specifically related to domain management, we expect the following from you:

  • Contact data: always provide correct, complete and up-to-date information about the domain contacts. We strongly discourage substituting your customer’s data with your own data; in many cases this is not allowed by registry policies and could result in the domain being revoked.
  • Availability checks: before registering a domain name, perform an availability check.
  • Transfers: before transferring a domain name (incoming or outgoing), ensure that the end user is aware. That prevents unforeseen complicacies such as rejected transfers.
  • Drop catching: do not use the Openprovider systems to drop catch domains. For a single domain, it’s okay to do an availability check every few seconds to determine when it has been released for registration but if you want to catch multiple domains or expect competition for registration, the Openprovider system is not your best option. Instead, refer to one of the many professional drop catching providers: the chances of getting your domain will be much higher as they are specialised in this business.
  • Registry policies: know the rules of each extension’s registry. You can find those rules in our contract section.
  • Abuse and complaints: in case of a complaint about one of your domains, solve it quickly and respond to the complainant.

DNS management

  • Free DNS service: the DNS service offered by Openprovider is free of charge until further notice, and is offered on “best effort” premises. The Openprovider DNS service is intended for use with domains registered in Openprovider only.
  • DNS for domains outside of Openprovider: DNS zones can be created even if the domain is not managed by Openprovider, for example to prepare for a registration or incoming transfer. We reserve the right to delete or disable the DNS zone 28 days after creation if there is no active domain in your Openprovider account. We will inform you upfront about such decision.
  • High load: for the sake of stability and performance of the Openprovider DNS service we reserve the right to disable a DNS zone or quarantine it by moving it to a separate nameserver cluster if we see that there are too many requests being sent to a certain DNS zone and performance of the Openprovider DNS service is being impacted (for example in case of a DDoS attack).

License management

Specifically related to license management, we expect the following from you:

  • Legal use: follow the End User License Agreement (EULA) and Terms of Use of the vendor.
  • One license – one server: a Plesk license may be installed on one server only (1 public IP address registered on the license). Openprovider will charge for every extra IP address detected, and eventually terminate the license.
  • Awareness: inform your customers or all other parties involved of legal and fair use policies published by the distributor and software vendor.
  • Bundling: you are entitled to use of the Plesk Product licenses only in your own technical infrastructure (servers / data centers) and you are allowed to resell Plesk to your own customers only if the licenses are bundled with your own technical infrastructure. In all other cases, reselling is not permitted


Specifically related to spam filtering, we expect the following from you:

  • Mailboxes: the maximum number of mailboxes on a single domain name is 1.000. Mailboxes above that limit will be charged.
  • Legal use: follow the End User License Agreement (EULA) and Terms of Use of the vendor.

Breach of the Fair Use Policy

As anyone can make a mistake, we won’t immediately terminate your reseller account if you do not apply to this Fair Use Policy. However, if we face continuous breaches from your side, we may decide to (temporarily) suspend your account, charge handling fees or even start the termination process according to articles 9 and 11 of our General Terms and Conditions.