Skip to content

Ordering TLS certificates

A TLS certificate proves to the browser that a connection really belongs to your domain. regfish issues certificates as a DigiCert partner; the brands underneath are RapidSSL, Thawte and GeoTrust.

Certificates, direct address: dash.regfish.com/my/cert

While no certificate is running, the page only shows the entry point for ordering and the link to the organizations. Once one has been issued, the active certificates appear here with their term and status.

Certificates → order your certificate, direct address: dash.regfish.com/my/cert/add

The order page with the validation type selectorThe order page with the validation type selector

At the top you pick the validation type, and that choice drives everything else.

The only thing checked is that you control the domain. This runs automatically through domain control validation (DCV) and takes minutes. The certificate carries no company name.

The products differ mainly in which names they can cover:

ProductWildcardsAlias names (SAN)Wildcard aliases
RapidSSL Standardnonono
Thawte SSL123yesyesno
GeoTrust DVyesyesyes

All three share one thing: order for the domain apex (example.com) and www.example.com is included at no extra cost.

Here the certificate authority also verifies the organization behind the domain. That takes hours rather than minutes, and in return the company name appears in the certificate. Products include GeoTrust True BusinessID and Thawte SSL WebServer, both with wildcards, alias names and wildcard aliases.

Prices and terms are shown on the product cards themselves. They change, which is why this page deliberately quotes no figures.

Certificates → Organizations, direct address: dash.regfish.com/my/cert/organizations

An organization is the verified company record that OV and EV orders require. It is created during the ordering process; this overview then lists every organization with its status:

  • orderable means it is complete and can be used for an OV or EV order right away.
  • incomplete means required details are still missing.

The org ID shown here is exactly the organization_id that the API and certbro expect. If you automate an OV order, fetch it here once and put it into your script. The two workflows for that are OV order + org id and OV with certbro.

The order creates a job that first passes domain control validation and is then issued. With DNS-based validation regfish writes the required record itself, provided the domain runs on regfish nameservers.

If you would rather not do this by hand: the whole path can be automated, either through the TLS endpoints or with certbro, which handles ordering, validation and renewal.

Newly issued certificates for your names can be watched independently of all this, even when they are not held at regfish. That is what certificate watch does.