Quick start
CertOne offers free SSL/TLS certificates issued by Let's Encrypt and professional certificates issued by Sectigo (formerly Comodo).
Let's Encrypt uses the ACME protocol to verify control of your domains and issue certificates. Domain validation can be performed manually by adding TXT records, but repeating this process for every renewal prevents full automation. Alternatively, DNS API credentials allow validation records to be managed automatically. CertOne is designed to automate renewal and deployment and supports three validation methods:
- DNS authorization: provide API credentials for your DNS provider.
- CNAME validation: add the specified CNAME records to your DNS zone; no DNS API credentials are required.
- HTTP validation: configure your server as instructed; no DNS API credentials are required.
1. Create a DNS authorization (skip this step for CNAME validation)
Supported DNS API integrations include Alibaba Cloud, AWS, GoDaddy, DNSPod.cn (Tencent Cloud), Cloudflare, Huawei Cloud, and Baidu AI Cloud. If your DNS provider is not supported, consider moving your DNS hosting to a supported provider. We continue to add integrations.
Create API credentials with your DNS provider by following the relevant guide:
- DNS authorization - Alibaba Cloud
- DNS authorization - AWS
- DNS authorization - GoDaddy
- DNS authorization - DNSPod.cn (Tencent Cloud)
- DNS authorization - Huawei Cloud
- DNS authorization - Baidu AI Cloud
- DNS authorization - Cloudflare
- DNS authorization - DNS.LA
- DNS authorization - West.cn
Then add the authorization in CertOne:
- Select DNS authorizations in the sidebar.
- Click Add authorization.
- Select your DNS provider and enter the API credentials you created.
- Click Add authorization to save.
You will use this authorization when creating a certificate. Domains managed by the same DNS provider can share an authorization, provided its permissions cover them. You can name, search, delete, and edit authorizations in the dashboard.
2. Create an HTTPS certificate
To use CNAME validation:
- Select Certificates in the sidebar.
- Click Create certificate.
- Select CNAME validation.
- Choose a single-domain, multi-domain, or wildcard certificate.
- Enter the domain names to include in the certificate.
- Add the CNAME records shown below the domain fields to your DNS zone.
- Click Validate DNS records to verify control of the domains. Validation usually takes 1–2 minutes.
- After validation succeeds, click Create certificate. Issuance usually takes 3–10 minutes.
To use DNS authorization:
- Select Certificates in the sidebar.
- Click Create certificate.
- Select DNS authorization.
- Choose a single-domain, multi-domain, or wildcard certificate.
- Enter the domain names to include in the certificate.
- Select the DNS provider and corresponding authorization.
- Click Verify authorization to verify control of the domains. Validation usually takes 1–2 minutes.
- After validation succeeds, click Create certificate. If validation fails, check the DNS API credentials and try again. Issuance usually takes 3–10 minutes.
Open the certificate details to view its version history and deployment history. The first version is created when issuance completes. Open a version to inspect cert.key (PEM private key), cert.cer (PEM certificate), and fullchain.cer (PEM certificate with intermediate certificates). You can also name, search, delete, and configure certificates in the dashboard.
3. Create a deployment node
Add a deployment node to deploy certificates to cloud load balancers, certificate stores, or CDNs on Alibaba Cloud, Tencent Cloud, Qiniu, DogeCloud, and BT Panel; NGINX, HTTPD, or OpenResty containers; or targets such as webhooks, SSH, APIs, and Synology NAS.
For cloud integrations, create the required API credentials first. See the relevant guide:
- Alibaba Cloud - SSL
- Alibaba Cloud - ALB
- Alibaba Cloud - SLB
- Alibaba Cloud - CDN
- Alibaba Cloud - DCDN
- Alibaba Cloud - OSS
- Tencent Cloud - SSL
- Tencent Cloud - CLB
- Tencent Cloud - CDN
- Qiniu - SSL
- Qiniu - CDN
- BT Panel - Website SSL
- BT Panel - Panel SSL
- Baidu AI Cloud - CDN
- Baidu Yunjiasu - CDN
- SSH
- Webhook
- OpenAPI
- DogeCloud - CDN
- Upyun - SSL
- Synology NAS
After creating the credentials, add the deployment node in CertOne:
- Select Deployment nodes in the sidebar.
- Click Add node.
- Select your provider, such as Alibaba Cloud, Tencent Cloud, Qiniu, or BT Panel.
- Select the destination: load balancer (Alibaba Cloud SLB/ALB or Tencent Cloud CLB), CDN, or SSL certificate store.
- Enter the API credentials you created with the provider.
- Click Next and select the certificates to associate with the node.
- Click Create deployment node.
SSL certificate store nodes can receive multiple certificates without overwriting one another. A load balancer or CDN node targets a specific binding and should have only one certificate associated with it; associating multiple certificates can cause them to overwrite each other.
Docker nodes do not require cloud API credentials:
- Select Deployment nodes in the sidebar.
- Click Add node.
- Select Docker.
- Select the container type: NGINX, HTTPD, or OpenResty.
- Click Generate to create a token.
- Click Next and select the certificates to associate with the node.
- Click Create deployment node.
NGINX, HTTPD, OpenResty, and custom containers are supported. Contact us by email if you need another container integration. Multiple containers started from the same image can share one deployment node, and a container can use multiple certificates. Containers fetch the latest associated certificates at startup, so create the certificates and configure the deployment node before starting them.
See these guides for container setup:
4. Configure certificate automation
Click Configure on the certificate management page to enable expiration reminders, automatic renewal, and automatic deployment, and to select deployment nodes.
5. Monitor site certificates
Site monitoring checks the expiration date of the SSL/TLS certificate served by a domain, even if it was issued outside CertOne. Expiration reminder emails are sent 20 days before expiration so that you can renew the certificate in time.