How Automatic SSL Works
Hostgrid automatically provisions and manages SSL certificates for every verified custom domain.
Once your domain has been verified, Hostgrid requests an SSL certificate, enables HTTPS, and continues renewing the certificate automatically before it expires.
There is no need to purchase, upload, or manually renew certificates.
Why SSL matters
Section titled “Why SSL matters”SSL (more accurately, TLS) encrypts traffic between your visitors and Hostgrid.
HTTPS provides several important benefits:
- Encrypts data in transit
- Protects user privacy
- Prevents browsers from displaying security warnings
- Improves trust for visitors
- Is required by many modern browser features
Without a valid SSL certificate, browsers may warn users that your website is not secure.
How automatic SSL works
Section titled “How automatic SSL works”SSL provisioning is part of the normal domain activation process.
Create Domain │ ▼Configure DNS │ ▼DNS Verification │ ▼Domain Activated │ ▼SSL Certificate Issued │ ▼HTTPS EnabledA domain only begins serving traffic after verification has completed and a valid SSL certificate has been provisioned.
Domain activation
Section titled “Domain activation”Hostgrid activates a domain only after all required checks have completed successfully.
This helps ensure that:
- You control the domain.
- DNS is correctly configured.
- HTTPS is available immediately.
- Visitors can access your application securely.
Until verification is complete, the domain will remain inactive.
Automatic certificate renewal
Section titled “Automatic certificate renewal”SSL certificates expire periodically.
Hostgrid monitors every active domain and automatically renews certificates before they expire.
No manual action is required.
As long as your domain remains correctly configured and verified, HTTPS continues working without interruption.
What happens when a visitor connects
Section titled “What happens when a visitor connects”When someone visits your custom domain, Hostgrid performs the following steps:
- Receives the HTTPS request.
- Presents the SSL certificate for the requested domain.
- Establishes a secure connection.
- Executes upstream rules.
- Executes domain rules.
- Forwards the request to your upstream.
- Returns the upstream response to the visitor.
Visitor │HTTPS Request │ ▼Hostgrid │SSL Certificate │ ▼Secure Connection │ ▼Upstream Rules │ ▼Domain Rules │ ▼Forward Request │ ▼UpstreamThis process is automatic for every active custom domain.
Wildcard domains
Section titled “Wildcard domains”If you’re using a wildcard domain, Hostgrid can provision a wildcard SSL certificate where supported.
A wildcard certificate secures every matching subdomain.
For example:
*.example.comcovers:
alice.example.comportal.example.comcustomer.example.comThis simplifies deployments where new subdomains are created frequently.
Learn more in the Understanding Domain Types guide.
Frequently asked questions
Section titled “Frequently asked questions”Do I need to upload my own certificate?
Section titled “Do I need to upload my own certificate?”No.
Hostgrid automatically provisions and manages SSL certificates for verified domains.
Do I need to renew certificates manually?
Section titled “Do I need to renew certificates manually?”No.
Certificates are renewed automatically before they expire.
Can visitors use HTTP instead of HTTPS?
Section titled “Can visitors use HTTP instead of HTTPS?”Once a domain is active, HTTPS is available automatically.
Hostgrid recommends always using HTTPS for secure communication.
Why hasn’t my certificate been issued yet?
Section titled “Why hasn’t my certificate been issued yet?”SSL provisioning begins only after your domain has been successfully verified.
If DNS records are incorrect or have not finished propagating, certificate issuance may be delayed until verification succeeds.
See the DNS Verification Guide for more information.
Does Hostgrid modify my application?
Section titled “Does Hostgrid modify my application?”No.
Hostgrid provides SSL termination and secure request forwarding but does not modify your upstream application or its content.
Platform-specific branding, headers, or application behavior remain unchanged.
Best practices
Section titled “Best practices”- Verify your DNS records as soon as possible after creating a domain.
- Keep DNS records unchanged after activation unless you intend to update your configuration.
- Always access your application using HTTPS.
- Monitor your domain’s verification status if you make DNS changes.