Domains and networking
SSL / TLS
All Lofenta domains get HTTPS automatically. Here is what happens behind the scenes.
Automatic provisioning
Every project gets a free TLS certificate covering its .lofenta.app subdomain. When you add a custom domain and verification succeeds, that domain gets managed automatic HTTPS via Cloudflare (Cloudflare for SaaS). Cloudflare issues and renews the certificate for you.
Provisioning typically completes within minutes of DNS propagation. No configuration, no uploading PEM files, no manual renewal.
Certificate details
Custom-domain certificates are issued and managed by Cloudflare, so the certificate authority, key algorithm, and validity window are controlled by Cloudflare and may change. The connection guarantees Lofenta enforces are:
HTTPS enforcement
HTTPS is enforced automatically. HTTP traffic is upgraded to HTTPS at the edge before reaching your container, and an HSTS header is set so browsers use HTTPS on subsequent visits. You do not need to implement redirects in your application code.
Wildcard certificates (on request)
Wildcard certificates (*.yourdomain.com) are not provisioned automatically by the platform. Email [email protected] if your project needs one and we configure it per zone manually.
Bring your own certificate
Custom certificate upload (e.g. EV certificates, CA-signed certs for compliance) is available on the Enterprise plan. Reach out at [email protected] for details.
SSL status
The Domains page shows the SSL status for each custom domain:
Certificate issuance is in progress. Usually resolves within 60 seconds of DNS verification.
Certificate is issued and valid. HTTPS is fully functional.
Certificate issuance failed. This usually means DNS has not propagated yet. Try again in a few minutes.
Next
API reference
Manage projects and deployments programmatically