GreenGeeks includes a free Let's Encrypt SSL certificate with its hosting plans, so you do not have to buy a separate certificate just to serve your site over HTTPS. The certificate is deployed through an automated tool in the GreenGeeks control panel, and the system is set up to renew it automatically. For most small business sites, blogs and portfolios, that free certificate is enough. The rest of this guide covers what the certificate includes, how to get it active and verified, what to do when it does not appear, and when a paid certificate is the better fit.
What the Free SSL Certificate Includes
GreenGeeks automatically issues Let's Encrypt certificates for all domains on its hosting, using DNS-based Domain Control Validation to confirm that the requester controls the domain. Domain Control Validation is the same basic check any free certificate uses: it confirms you control the domain and nothing more.
The certificate is valid for 90 days. GreenGeeks recommends renewing every 60 days to avoid potential outages on Let's Encrypt's network, and it provides automated renewal, though it states it cannot be responsible for failed issuance. Independent Let's Encrypt community guidance points the same way: certificates should ordinarily be renewed after about 60 days rather than after they expire.
On encryption, GreenGeeks lists 256-bit encryption for both its free Let's Encrypt certificate and its paid AlphaSSL Wildcard option. At the same validation tier, an independent SSL comparison notes there is no encryption-strength difference between free and paid certificates; the TLS handshake, cipher negotiation and browser padlock are identical to a paid DV certificate.
How to Activate the Certificate on a GreenGeeks Domain
Because GreenGeeks issues the certificate automatically, activation is less about pressing an "install" button and more about making sure your domain is correctly set up so issuance can succeed. The exact menu names and button order in the current control panel are not documented in the sources reviewed here, so treat the sequence below as the practical order of checks rather than a click-by-click script.
- Point the domain at your GreenGeeks hosting. The certificate must cover the domain your site actually serves. If the domain is not yet mapped to your hosting account, issuance has nothing to validate.
- Confirm DNS control. GreenGeeks uses DNS-based Domain Control Validation, so the domain's DNS records must be in place and reachable when issuance runs.
- Let the automated deployment run. GreenGeeks describes automated SSL deployment as a control-panel feature that deploys and renews free Let's Encrypt certificates. On a correctly configured account, you should not need to request the certificate manually.
- Check for AutoSSL exclusions. GreenGeeks notes that if you want SSL on an AutoSSL-excluded domain, the certificate must be installed manually. That is an exception to the automatic path, not the norm.
- Repeat for each domain. Issuance is described as applying to all domains, but each domain still needs its own correct DNS and mapping setup.
How to Verify HTTPS Is Working
Once issuance has run, confirm three things: that the certificate was issued, that it is installed on the domain, and that the site actually serves HTTPS.
- Check the certificate in the browser. Load your domain with
https://and confirm the padlock appears without a warning. Because the encryption and padlock match a paid DV certificate, a clean padlock is the expected result when installation succeeded. - Check the issuing authority and expiry. Open the certificate details in your browser and confirm the issuer is Let's Encrypt and the validity window is about 90 days from issuance.
- Check that HTTP redirects to HTTPS. If the plain
http://version still loads without redirecting, visitors can reach an unencrypted copy of the site even though the certificate is installed. The sources reviewed here do not document GreenGeeks' specific redirect settings, so this is a general check rather than a vendor-specific step. - Check every hostname you use. Test both
example.comandwww.example.comif both are live, since a certificate that covers one may not cover the other.
Troubleshooting a Missing or Expired Certificate
If HTTPS does not come up, work through the likely causes in order rather than assuming the certificate itself is broken.
The domain is not mapped to hosting. This is the most common reason automatic issuance has nothing to validate. Confirm the domain is added to your GreenGeeks account and resolves to the correct server.
DNS validation is failing. Because GreenGeeks relies on DNS-based Domain Control Validation, missing or incorrect DNS records will block issuance. Check that the domain's DNS is active and that you have not changed nameservers or records in a way that interrupts validation.
The domain is excluded from AutoSSL. GreenGeeks states that AutoSSL-excluded domains need the certificate installed manually. If you deliberately excluded a domain, that exclusion explains the missing certificate.
Renewal did not run in time. Certificates last 90 days, and GreenGeeks recommends renewal around the 60-day mark to avoid outages. GreenGeeks provides automated renewal but states it cannot be responsible for failed issuance, so a lapse is possible if renewal fails and nobody notices. Independent guidance agrees that renewal should happen well before expiry rather than at the deadline.
A deeply nested subdomain is not covered by a wildcard. Certificate authorities cannot issue certificates with a double wildcard such as *.*.domain.tld. If you need HTTPS on a hostname like www.newsletters.example.com, plan for a certificate that explicitly covers that hostname rather than assuming a wildcard will reach it.
Free vs Paid SSL: When the Upgrade Is Worth It
The free Let's Encrypt certificate and a paid certificate such as GreenGeeks' AlphaSSL Wildcard differ on a few points that matter for some sites and not others.
| Criterion | Free Let's Encrypt | Paid AlphaSSL Wildcard |
|---|---|---|
| Cost | Free, included with hosting | Paid; price not stated in the sources reviewed |
| Validation | Domain Validation only | Premium certificate; OV/EV not confirmed for this product |
| Encryption | 256-bit | 256-bit |
| Validity and renewal | 90-day validity, auto-renewed, 60-day renewal recommended | Paid certificates generally last about a year |
| Warranty | None | Paid CAs typically carry a warranty |
| Support | No direct Let's Encrypt support | Paid CAs typically offer priority support |
| Trust seal | Not included | Paid options may include one |
| Domain coverage | Issued automatically for domains via DNS DCV | Wildcard coverage for the domain |
The practical differences come down to validation level, warranty and support, not encryption. GreenGeeks itself says free certificates provide only Domain Validation, which confirms domain ownership and nothing more, and that Organization Validation and Extended Validation are not available for free because they require greater verification.
That matters when a third party requires more than DV. Some payment processors, banking partners or compliance frameworks specifically require OV or EV validation as a contractual condition. If a contract or onboarding checklist names OV or EV, a free certificate will not satisfy it regardless of how well it encrypts traffic.
Warranty and support are the other real differences. Free certificates carry no warranty, and Let's Encrypt does not include technical support you can access directly. Paid certificates from commercial CAs typically carry a warranty and offer phone or priority support for urgent reissuance or revocation, while Let's Encrypt is community and documentation supported only. Free certificates also do not include a site or trust seal to display.
One difference that is often overstated: search ranking. Google's ranking algorithm treats HTTPS as a binary signal, present or absent, and does not differentiate between DV, OV and EV for search ranking purposes. Upgrading for SEO alone is not a supported reason.
Who Should Choose Which
Stick with the free Let's Encrypt certificate if you run a blog, portfolio, brochure site or small business site that needs HTTPS and a padlock, does not display a trust seal as part of its brand, and has no contract requiring OV or EV validation. The automated deployment and renewal keep the administrative overhead low, provided you watch for renewal failures. Free certificates do not include a trust seal to display, so a site that markets one should look at paid options.
Consider the paid AlphaSSL Wildcard if you need wildcard coverage for multiple subdomains, want a vendor-backed support relationship for urgent reissuance, or need a CA warranty for procurement reasons. Paid certificates from commercial CAs typically carry a warranty and priority support, while Let's Encrypt is community and documentation supported only. The sources reviewed here do not confirm OV or EV validation for this specific product, so if a partner requires OV or EV, verify that the exact certificate meets the requirement before buying.
Do not upgrade for encryption reasons. At the same validation tier, free and paid certificates provide the same encryption and the same browser padlock.
The Short Version
GreenGeeks does include a free SSL certificate with its hosting, and it is a genuine Let's Encrypt certificate rather than a limited trial. Get the domain correctly mapped and its DNS in place, let the automated deployment run, then verify the padlock and the redirect to HTTPS. Keep an eye on renewal, since the certificate is short-lived and GreenGeeks does not take responsibility for failed issuance. Upgrade to a paid certificate only when a specific requirement, such as OV/EV validation, wildcard coverage, a warranty or priority support, actually applies to your site.


