Wildcard certificates
One Let's Encrypt certificate covers your apex domain and every next-level subdomain — no per-host issuance.
ACME DNS-01 · Wildcard ready
HTTPS that runs
on autopilot.
Issue, deploy, and renew Let's Encrypt wildcard certificates from one console. SetHttps handles DNS validation, multi-node delivery, and renewals — so your sites stay encrypted without the maintenance.
Let's Encrypt certificates No manual renewals Linux · Nginx · Apache
- api.acme.dev DNS-01 verified
- *.acme.dev Certificate issued
- edge-sg-01 Deployment synced
- next renewal Auto · 59 days
$ curl -sI https://acme.dev | head -3
HTTP/2 200
server: nginx
strict-transport-security: max-age=31536000
certificate: Let's Encrypt · valid 90d
Built on open standards
- Let's Encrypt
- ACME v2
- RFC 8555
- DNS-01
- TLS 1.3
- SFTP / SSH
- Nginx
- OpenResty
- Apache
- Docker
Live platform data
A live view of the platform.
Live counts from the platform database, combined with historical totals and updated continuously.
—
Domains served
Connected to the platform
—
Certificates issued
Let's Encrypt · wildcard or single-host
—
Sites deployed
Certificates delivered to a node
—
Days live
Since the first domain was connected
Live data plus historical totals · last updated —
Why SetHttps
Certificate operations, minus the operations.
Wildcard coverage, DNS validation, fleet-wide delivery, and renewals that quietly take care of themselves.
WildcardOne certificate for your apex and every next-level subdomain.
DNS-01No inbound HTTP challenge. No port 80 exposure.
Multi-nodeDeliver the same certificate to every server you run.
Auto-renewDaily checks renew and redeploy before expiry.
Platform
Everything between “add domain” and “HTTPS”.
A focused toolset for teams that would rather ship product than babysit certificate expiries.
Hands-off renewals
Certificates renew before expiry and are redeployed automatically. No cron jobs, no calendar reminders.
Multi-node deployment
Push certificates to every server in your fleet, each with its own upload path and reload command.
DNS-01 validation
Guided DNS records with automatic checks. Validate ownership without exposing an HTTP challenge server.
Credential isolation
Server passwords are encrypted at rest and used only for SFTP uploads. The platform runs no arbitrary commands.
Operational visibility
Domain, certificate, and deployment states in one console, with task history when something needs attention.
Workflow
From DNS record to deployed certificate.
Four steps to set up. Then the pipeline keeps itself current.
-
01
Add your domain
Enter the apex domain. You can scope the certificate to a single host or a wildcard.
-
02
Publish one DNS record
The console generates the record. Add it at your DNS provider and let the platform verify it.
_acme-challenge → CNAME -
03
Issue the certificate
ACME completes the DNS-01 challenge. The certificate is stored and ready to deliver.
-
04
Deploy and forget
Pick your nodes. Renewals, uploads, and reload commands repeat automatically before expiry.
nginx -s reload
pipeline.yml
read-only
# 1 · DNS validation (managed by SetHttps)
_acme-challenge.acme.dev. 300 IN CNAME <token>.acme.sethttps.com.
# 2 · Issue a wildcard certificate
acme issue --domain acme.dev --wildcard
# 3 · Deploy to every node
acme deploy --node edge-sg-01 \
--path /usr/local/nginx/ssl \
--reload "nginx -s reload"
# 4 · Renewal runs automatically
acme renew --auto --before 30dConsole
Every certificate, one clear status.
See validation, issuance, and deployment at a glance — and know exactly which step needs you.
Domains
3 domains · 1 deployment node
| Domain | Validation | Certificate | Deployment |
|---|---|---|---|
| sethttps.com | Verified | Issued | Deployed |
| api.sethttps.com | Verified | Issued | Pending |
| app.sethttps.com | Pending | Queued | — |
Last checked 2 minutes ago
Auto-renew: enabled
Security
Security is the product.
TLS only helps if the pipeline around it is trustworthy. SetHttps keeps credentials, transfers, and actions deliberately narrow.
- Encrypted at rest. Server passwords are stored encrypted and never returned by the API.
- File transfer only. Certificates are uploaded over SFTP; the platform does not execute arbitrary remote commands.
- Per-node control. Each target has its own path and explicit reload command.
- Task history. Issuance and deployment runs are logged for review.
- Auditable deploy account. The account we create on your servers comes from a ~120 line public script — read it before you run it. Source on GitHub
Security model
ACME protocolRFC 8555
ValidationDNS-01
DeliverySFTP / SSH
Certificate authorityLet's Encrypt
SecretsEncrypted at rest
TransportTLS 1.2+
Deploy accountOpen source · MIT
Who it's for
Built for people who run their own servers.
Ship side projects without expiry anxiety
Add a domain, publish one record, and let the wildcard certificate renew itself.
Keep every subdomain encrypted
One wildcard certificate covers customer subdomains, with the same policy across every node.
Standardise HTTPS across clients
Repeatable deployment targets and a clear status view for every site you operate.
FAQ
Questions, answered.
Do you support wildcard certificates?
Yes. SetHttps issues Let's Encrypt wildcard certificates through DNS-01 validation. One certificate covers your apex domain and its next-level subdomains.
Do I need to expose port 80?
No. DNS-01 validation only requires a DNS record, so you do not need to expose HTTP ports or run a challenge server.
Where are my server credentials stored?
Server passwords are encrypted at rest with a server-side key and are never returned by the API. They are used only for SFTP certificate uploads.
What happens at renewal time?
The platform checks certificates daily, renews them before expiry, and redeploys them to every configured node automatically.
Which servers can I deploy to?
Linux servers reachable over SSH/SFTP. Nginx, OpenResty, and Apache are the common targets; any service with a reload command can be configured.
Put HTTPS on autopilot.
Open the console, add your first domain, and leave certificate renewals behind.