SSL/TLS certificates encrypt traffic between users and Sundun's edge servers, ensuring secure communication. This guide covers certificate management options and configuration.
Sundun offers multiple certificate management options:
| Option | Description | Best For |
|---|---|---|
| Sundun Universal SSL | Free, auto-provisioned certificates | Most websites |
| Custom Certificate | Upload your own certificate | Specific compliance requirements |
| Dedicated Certificate | Single-tenant certificate | Enterprise, financial services |
Universal SSL certificates are automatically provisioned for all domains on Sundun. These certificates:
Universal SSL is enabled by default. To verify:
Universal SSL certificates cover:
example.com ✓ Covered www.example.com ✓ Covered *.example.com ✓ Covered (wildcard) sub.sub.example.com ✗ Not covered (multi-level)
Note: For multi-level subdomains (e.g.,
api.v2.example.com), use a custom certificate or add each subdomain separately.
Upload your own SSL certificate for full control over certificate authority, validity period, and subject details.
| Format | Extensions | Description |
|---|---|---|
| PEM | .pem, .crt, .cer | Base64 encoded, most common |
| PKCS#7 | .p7b, .p7c | Certificate chain format |
┌─────────────────────────────────────────────────┐ │ Certificate (PEM format) │ │ ┌───────────────────────────────────────────┐ │ │ │ -----BEGIN CERTIFICATE----- │ │ │ │ MIIFjTCCA3WgAwIBAgIRANOxciY0... │ │ │ │ -----END CERTIFICATE----- │ │ │ └───────────────────────────────────────────┘ │ │ │ │ Private Key (PEM format) │ │ ┌───────────────────────────────────────────┐ │ │ │ -----BEGIN RSA PRIVATE KEY----- │ │ │ │ MIIEowIBAAKCAQEA0Z3VS0... │ │ │ │ -----END RSA PRIVATE KEY----- │ │ │ └───────────────────────────────────────────┘ │ │ │ │ Certificate Chain (optional) │ │ ┌───────────────────────────────────────────┐ │ │ │ Intermediate and root certificates │ │ │ └───────────────────────────────────────────┘ │ └─────────────────────────────────────────────────┘
For custom certificates, include the full certificate chain:
Your Certificate (leaf) ↓ Intermediate Certificate(s) ↓ Root Certificate (optional, usually not needed)
Correct chain order:
-----BEGIN CERTIFICATE----- [Your domain certificate] -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- [Intermediate certificate] -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- [Root certificate - optional] -----END CERTIFICATE-----
Configure the minimum TLS version accepted:
| Version | Recommendation | Browser Support |
|---|---|---|
| TLS 1.0 | Not recommended | Legacy only |
| TLS 1.1 | Not recommended | Deprecated |
| TLS 1.2 | Recommended minimum | 98%+ browsers |
| TLS 1.3 | Best security | 95%+ browsers |
To configure:
Sundun supports modern cipher suites by default:
TLS 1.3 Ciphers:
TLS 1.2 Ciphers:
Configure how Sundun connects to your origin server:
| Mode | Edge ↔ User | Edge ↔ Origin | Use Case |
|---|---|---|---|
| Off | HTTP | HTTP | Not recommended |
| Flexible | HTTPS | HTTP | Origin without SSL |
| Full | HTTPS | HTTPS | Origin with self-signed cert |
| Full (Strict) | HTTPS | HTTPS (validated) | Production recommended |
Recommendation: Always use "Full (Strict)" mode in production to ensure end-to-end encryption with certificate validation.
Force all traffic to use HTTPS:
Redirect all HTTP requests to HTTPS:
http://example.com → https://example.com (301 redirect)
Enable in SSL/TLS → Edge Certificates → Always Use HTTPS
Enable HSTS to instruct browsers to always use HTTPS:
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Configure HSTS settings:
Sundun monitors certificate expiration and sends alerts:
Check certificate status in your dashboard:
| Status | Description |
|---|---|
| Active | Certificate is valid and serving traffic |
| Pending | Certificate is being provisioned |
| Expiring Soon | Certificate expires within 30 days |
| Expired | Certificate has expired |
| Error | Provisioning failed |
If browsers show mixed content warnings:
//example.com/resource)# Verify certificate chain openssl s_client -connect example.com:443 -servername example.com # Check for chain issues openssl verify -CAfile chain.pem certificate.pem
Manage certificates via API:
# List certificates curl -X GET https://api.Sundun.com/v1/domains/example.com/certificates \ -H "Authorization: Bearer YOUR_API_KEY" # Upload custom certificate curl -X POST https://api.Sundun.com/v1/domains/example.com/certificates \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "certificate": "-----BEGIN CERTIFICATE-----...", "private_key": "-----BEGIN RSA PRIVATE KEY-----...", "chain": "-----BEGIN CERTIFICATE-----..." }'
Need help with SSL/TLS? Contact support@Sundun.com