Enter domain & plan
Choose 90 days or 1 year coverage with renewals.
Let's Encrypt · DNS & HTTP · Wallet billing
SSLBind
Bind HTTPS to your domain in minutes.
Skip the boring cert dance. Pick a domain, prove it’s yours, download the kit, ship HTTPS.
- 🔒 Browser-trusted
- ⭐ Wildcard ready
- 📡 DNS + HTTP
- 📦 cPanel install kit
$ sslbind issue --domain yourdomain.com --vibes max
acme order created ✓
verify dns / http challenge ✓
seal certificate bound ✓
export crt · key · ca-bundle ready to rock
Widely trusted
Certificates chain to Let’s Encrypt roots trusted by Chrome, Firefox, Safari, and Edge.
DNS or HTTP proof
Prove ownership with a TXT record or a challenge file — wildcards require DNS.
Install-ready kit
Download CRT, private key, full CA bundle with ISRG roots, or one ZIP for cPanel.
Four fun steps. Zero drama.
No CSRs. No vendor lock-in. Verify ownership and download PEM files.
Pay from wallet
IQD via Wayl or USD wallet balance.
Verify ownership
Add a DNS TXT record or upload one challenge file.
Download & install
Copy or ZIP your CRT, key, and CA bundle into cPanel, Nginx, or Apache.
Works with your stack
Standard PEM files install on shared hosting, VPS, and cloud panels.
🟦 cPanel🔴 Nginx🟠 Apache🟣 Plesk
🪟 IIS🟢 Node.js🐳 Docker🖤 Namecheap
Pick your power-up
Transparent USD and IQD pricing for developers and companies.
🌱
90 Days
$2.99 USD
4,000 IQD · per certificate
- One issuance window (~90 days LE cert)
- DNS or HTTP verification
- CRT · Key · CA Bundle · ZIP
🔥
1 Year
$7.99 USD
9,000 IQD · per certificate
- Renewals included for 365 days
- DNS or HTTP verification
- Expiry reminders in dashboard
Let's Encrypt issues ~90-day certificates. The 1-year plan includes renewals for 365 days.
Curious? We got answers.
Straight answers for verification, install, and renewals.
Are certificates trusted by browsers?
Yes. SSLBind issues via Let’s Encrypt, a publicly trusted CA included in major browser and OS root stores. Visitors see the padlock and https:// like any other trusted certificate.
How long is a certificate valid?
Each Let’s Encrypt leaf certificate lasts about 90 days. Our 90-day plan covers one issuance window. The 1-year plan includes renewal entitlement for 365 days so you can reissue within that period.
DNS vs HTTP — which should I use?
HTTP places a file under /.well-known/acme-challenge/ when the site is live on port 80. DNS adds _acme-challenge TXT records and works without a running site. Wildcards (*.example.com) require DNS.
Do you support wildcard certificates?
Yes. Enter *.example.com and use DNS TXT validation. The cert covers first-level subdomains; include the apex domain separately if you also need example.com.
What files do I need to install?
You need the Certificate (CRT), Private Key, and CA Bundle (intermediates + ISRG roots for cPanel). Or download the ZIP / fullchain.pem for Nginx.
Can I delete verification TXT records or challenge files afterward?
Yes. After the certificate is issued you can remove ACME challenge files and _acme-challenge TXT records.
What if I lost my private key?
Re-download from your SSLBind order if the files are still available. Otherwise reissue a new certificate — the old key cannot be recovered.
Why does the site still say Not Secure?
Usually mixed HTTP content (images/scripts) or missing HTTPS redirect. Confirm CRT, key, and CA Bundle match, then force HTTPS in .htaccess or the server config.
Do certificates work for IP addresses?
No. Certificates are for registered domain names only — not bare IP addresses.
Is commercial use allowed?
Yes. You may use certificates issued through SSLBind for commercial sites you are authorized to secure, subject to our Terms and Let’s Encrypt policies.