Test how to generate an SSL certificate using DNS or HTTP verification. Enter a domain you control, follow the verification instructions, and download the test certificate files.
Staging test: This prototype is available to logged-in administrators only. It issues test certificates that browsers do not trust; do not install them on a live website.
Enter your domain details to begin your certificate request.
Your private keys are generated in this browser. Keep this tab open until your files are downloaded. Issuance and renewal are manual.
Prove control of your domain using a DNS TXT record or an HTTP verification file.
The certificate private key is generated in your browser during the test process.
Download the staging certificate, private key, CA bundle and full chain.
Review the steps for installing and renewing certificates through your hosting provider.
1. Enter your domain. Use a hostname such as example.com, without https:// or a page path. You can select the www option to request both hostnames.
2. Enter your email and choose verification. Select DNS TXT record or HTTP file upload, and accept the subscriber agreement.
3. Verify domain control. Add the record or upload the file exactly as shown. Wait until each change is publicly visible, then select Verify.
4. Download the test files. After successful issuance, download your staging certificate, private key, CA bundle and full chain. Keep the tab open until the files are saved.
An SSL certificate enables HTTPS, helping encrypt information exchanged between visitors and a website. This can protect data in transit when people sign in or submit a form.
Modern websites use TLS, the successor to SSL, although “SSL certificate” is still the common term. HTTPS is one part of security; it does not replace updates, backups or strong passwords.
DNS verification: Add the TXT record displayed by the tool in your DNS provider’s dashboard. DNS updates may take time to become publicly visible. Some providers automatically append your domain to the record name.
HTTP file verification: Upload the file to the exact /.well-known/acme-challenge/ path shown. The certificate authority must be able to reach it over HTTP on port 80. Firewall, CDN and server rules can interfere.
If you request both your root domain and www hostname, follow the instructions shown for each name.
Certificate: Identifies the hostname or hostnames covered by the issued certificate.
Private key: Must match the certificate. Keep it confidential. In this prototype, the key is generated in your browser; closing or refreshing the page interrupts the session.
CA bundle: Contains intermediate certificates used to establish a chain of trust.
Full chain: Combines the website certificate and intermediates for servers or hosting panels that request one chain file.
For a production certificate, open SSL/TLS in cPanel and look for Manage SSL sites. Select the domain, enter the certificate and matching private key, provide the CA bundle if needed, and install it. Visit the HTTPS version of your site to check the result. Options vary by host.
Many hosts offer AutoSSL or another automatic service. Check your hosting account before installing a certificate manually. Staging certificates are not trusted by browsers and should not be installed on a live website.
Validity depends on the issuing certificate authority and profile. Let’s Encrypt has announced a default 64-day lifetime beginning February 10, 2027. Always check the actual expiration date shown on the issued certificate.
The prototype does not install or renew certificates automatically. For a manually managed production certificate, request a replacement, complete any required verification, install the new files and check the updated expiration date. Let’s Encrypt no longer sends expiry notification emails, so set your own reminders or use automatic renewal from your host.
DNS record not found: Check the name and value and allow time for DNS changes to become visible.
HTTP file not reachable: Verify the exact path and content, port 80, firewall, CDN and server settings.
Private key does not match: Use the key created for the same certificate request.
Browser warning: Staging certificates are intentionally untrusted. For production certificates, check expiry, hostname coverage and the certificate chain.
Find answers to common questions about domain validation, certificate files, installation and renewal.
Yes. Let’s Encrypt offers free domain-validated certificates after confirming that you control the domain. The current TechHippo tool uses staging and issues test certificates only.
No. This prototype is available to administrators for staging tests. Its certificates are not browser-trusted and should not be installed on a live website.
You must control the domain or have permission to manage its DNS records or website files. The certificate authority verifies control before issuing a certificate.
They are separate hostnames. The prototype can request both when you enter a non-www domain and select the www option. Follow the verification instructions for each name.
Let’s Encrypt supports wildcard certificates with DNS validation, but the current TechHippo prototype does not support wildcard requests.
No. Installation and renewal are manual in this prototype. Some hosting providers offer their own automatic SSL installation and renewal service.
A production certificate can secure a WordPress site when supported by the hosting provider. Installation generally happens in your hosting panel or web server.
Browsers may display security warnings and applications may reject the connection. Renew and install a replacement before the expiration date.
No. HTTPS protects data in transit but does not replace software updates, strong passwords, backups or malware protection.
After installing a production certificate, use the SSL Certificate Checker to inspect it. Use the DNS Records Checker to review public DNS records.