3-2-1 Backup Strategy: How to Never Lose Your Data
Learn what the 3-2-1 backup strategy is, how to apply it to your website, and how to confirm your backups actually work with a restore test.
View →What is an SSL certificate, and what types are there? A step-by-step HTTPS switch, common post-migration issues, HSTS and renewal tips for your site.

An SSL certificate is a digital document that encrypts the connection between your website and the visitor's browser, and verifies that the site really belongs to you. Once a certificate is installed, your address opens with https:// instead of http://, and the browser shows a secure connection indicator in the address bar. Today, using HTTPS is not an option but the minimum expected standard, whatever type of site it is. This guide explains what a certificate does, its types, and the steps to switch to HTTPS.
A certificate performs three basic functions. The first is encryption: forms, login information and payment data sent by the visitor cannot be read over the network. The second is authentication: the visitor can trust that the server they connect to is controlled by the owner of the domain name. The third is integrity: the page cannot be altered in transit, and ads or malicious code cannot be inserted.
An unencrypted HTTP site is open to traffic monitoring in environments such as shared wireless networks. Modern browsers display warnings when forms are filled on unencrypted pages, which lowers visitor trust and conversions. Search engines also prefer HTTPS, but it is not right to consider it the decisive factor for ranking.
SSL (Secure Sockets Layer) is the name of an old protocol and is no longer considered secure. The protocol used today is called TLS (Transport Layer Security). The term "SSL certificate" continues to be used out of habit; what is actually meant when buying or installing one is a TLS certificate. Make sure old protocol versions are disabled on your server and current TLS versions are enabled.
Certificates are classified by their validation level and by the number of domain names they cover. There is no basic difference in encryption strength between them; the difference is how detailed the validation is.
| Type | What it validates | Who it suits |
|---|---|---|
| DV (Domain Validated) | Only that you control the domain name | Blogs, corporate showcase sites, most small and medium-sized sites |
| OV (Organization Validated) | In addition to the domain name, the existence and details of the organization | Companies that want to emphasize corporate trust |
| EV (Extended Validation) | Stricter organization validation | Corporate or financial structures that require high-level validation |
| Scope | Description |
|---|---|
| Single domain | Valid only for the specified domain name |
| Wildcard | Covers all subdomains of one domain name (for example, subdomains) in a single certificate |
| Multi-domain (SAN) | Groups several different domain names in one certificate |
Many servers and hosting providers offer free, automatically renewed DV certificates. Unless you have a specific requirement such as a corporate or contractual need, DV is sufficient for small and medium-sized sites. If you want to recall the domain name concept, see our article what is a domain name.
When a visitor's browser connects to the site, the server sends its certificate. The browser checks that the certificate was signed by a trusted certificate authority, that the domain name matches, and that it has not expired. If the checks succeed, the parties agree on encryption keys specific to that session, and all data from then on flows encrypted. If the checks fail, the browser shows the visitor a warning page. So a certificate is not just a file but part of a verification chain; intermediate certificates must also be installed correctly on the server, otherwise a warning may appear on some devices.
There are two common ways to obtain a certificate: an automatic certificate feature offered by your hosting panel, or purchasing one from a certificate authority and installing it on the server manually. To prove that you own the domain, you usually add a DNS record or publish a verification file sent to you. In a manual installation, the certificate file, private key and intermediate certificate bundle must be uploaded in the correct order. Never share the private key with anyone or send it by email.
The installation path depends on your hosting environment. On shared hosting you can often finish with a few clicks from the panel, while if you manage your own server you set up renewal automation yourself.
yourdomain.com and www.yourdomain.com versions.http:// addresses in template, image, script and style files with https://.The search side of the switch is part of the general technical SEO audit; for details, see our technical SEO checklist.
If the page opens over HTTPS but an image or script inside it is still called over HTTP, the browser shows a warning or blocks that resource. The browser developer console lists these resources. The fix is to change those addresses to HTTPS.
If the server, application and reverse proxy layers (such as a CDN) each perform their own redirects, the page can fall into an endless redirect. Make sure only one layer performs the redirect and that the others recognize it correctly.
When a certificate expires, visitors see a full-page security warning and most users leave the site. Even if automatic renewal is set up, check periodically that it is running, and set up monitoring that alerts you as the expiry date approaches.
If the certificate was obtained only for one domain name, you will see errors on the other version (for example, without www, or on a subdomain). Choose the scope correctly from the start.
HSTS is a response header that tells the browser to connect to the site only over HTTPS. Before enabling it, make sure all of the site and its subdomains work without issues over HTTPS; a misconfigured HSTS can make the site difficult to access until it is corrected. Proceed by keeping the duration value short at first and testing. Disabling old and weak encryption algorithms on the server and using current TLS versions are also important. These are items we routinely check in our server and maintenance services.
Certificates are not valid indefinitely; they must be renewed at set intervals, and these intervals may shorten over time according to industry rules. The safest approach is to use automatic renewal and monitor the result. Define an address that receives an email notification if renewal fails, and make sure that address is a mailbox that is actually read. If you use a corporate certificate, also document who or which team is responsible for it as the certificate owner, so that renewal is not forgotten when staff change.
When deciding, ask these questions: Does the site have user accounts, or forms that collect personal data or payments? How many domains and subdomains need to be protected? Is there a commercial or contractual requirement to have your organization validated? For a small corporate showcase site or blog, the automatic DV certificate offered by your hosting provider is usually sufficient. If you have many subdomains, a wildcard certificate makes sense; if you want to manage different domain names from one place, multi-domain certificate management makes it easier. The price difference usually comes from the validation process and the additional services provided rather than from encryption, so do not assume that a more expensive certificate offers stronger encryption.
The SSL (TLS) certificate is the first step toward visitor trust and basic web security; correct redirects and renewal matter as much as the installation itself. If you want us to handle your HTTPS switch smoothly, or to take over the security and maintenance of your site, you can get in touch with Erdem Software.
It is less a legal requirement than a technical and commercial necessity. Every site that collects forms, logins or payments should use one; browsers show warnings on unencrypted sites and visitor trust drops.
In practice they serve the same purpose. SSL is the name of an old protocol and is not considered secure; the protocol used today is TLS. When people say certificate, they usually mean a TLS certificate.
For most small and medium-sized sites, a free DV certificate is sufficient; the encryption level is the same. If you have specific requirements such as organization validation, consider OV or EV.
Not if it is done correctly. Redirecting all HTTP addresses to HTTPS with 301, and updating canonical tags and the sitemap, keeps the switch healthy.
Visitors see a full-page security warning in the browser and most leave the site. That is why you should set up automatic renewal and monitor the expiry date.
Tell us briefly about your project, and we’ll get back to you with a roadmap and a quote.
Learn what the 3-2-1 backup strategy is, how to apply it to your website, and how to confirm your backups actually work with a restore test.
View →
Learn the essential defensive measures that protect your site, including updates, two-step verification, HTTPS, security headers, backups and monitoring, with a checklist.
View →
Learn what SPF, DKIM and DMARC records do for business email, how to set them up correctly and how to test them so your messages stop landing in spam.
View →We would like to use Google Analytics cookies to understand how the site is used. If you decline, no statistics cookies are set. Details