Encrypt the connection between visitors and your website with HTTPS. Choose a certificate for your domain structure alongside its validation, installation and renewal process.
Domain nameA list of all addresses to protect.
VerificationDomain and, when needed, organization checks.
InstallationKey, certificate and intermediate certificate chain.
RenewalMonitoring validity and automated tasks.
Assess the encryption protocol, identity validation level and covered domains separately. Current product, term and pricing options are determined at the quote stage.
Control of the domain is verified. Suitable for consideration for company information sites, content publications and many projects needing an HTTPS connection.
Organization details are verified in addition to domain control. Suitable for companies and purchasing processes that require organization identity validation.
Options for covering a domain’s subdomains or several different domains. Validation level and domain coverage are chosen separately.
| Requirement | Option to consider | What to check |
|---|---|---|
| Single website | Single-domain DV or OV | Root domain and www coverage. |
| panel.ornek.com and destek.ornek.com | Wildcard certificate | Subdomain level and inclusion of the root domain. |
| Domains for different brands | SAN / multi-domain certificate | Name count, additions and reissuance conditions. |
| Organization identity validation | OV; EV depending on requirements | Organization documents and certificate authority validation requirements. |
Free and paid certificates can provide TLS connections when installed correctly. When comparing fees, assess the validation type, covered names and who will monitor each part after installation separately.
| Item | Clarify in the quote | Check at handover |
|---|---|---|
| Validation and domains | DV / OV / EV; single-domain, wildcard or SAN coverage. | All addresses in use appear in the certificate’s name list. |
| Installation and reissuance | Servers for installation, support scope and reissuance conditions. | Correct certificate chain; website, panel and any API addresses working individually. |
| Renewal and automation | Subscription term, certificate validity, automatic renewal and notification contact. | The new certificate is active on the server visitors connect to, not merely issued. |
| CDN / load balancer | Certificate requirements for visitor-to-CDN and CDN-to-origin-server connections. | Correct names, valid dates and appropriate validation settings at each connection endpoint. |
DNS permissions, an incorrect validation record or an inaccessible HTTP validation file can block the process. If the domain has a CAA record, check that the selected certificate authority is permitted. Follow the validation method in use instead of arbitrarily removing security or DNS settings.
Obtain your payment provider’s and organization’s certificate requirements in writing. Choosing OV / EV relates to the need for organization validation; a higher price alone does not mean stronger traffic encryption. Obtaining an SSL certificate does not establish that PCI DSS or KVKK obligations are fulfilled.
The certificate chain, redirects and addresses used by the application should be checked together. The renewal schedule and validation method should also be part of the service plan.
Our web security approachReplace the sample addresses on the right with your own domains. Listing each name separately allows root domains, subdomains and different brands to be checked during quoting. Do not share private keys or panel passwords.
Let’s Encrypt’s validation documentation illustrates HTTP and DNS methods. The certificate authority, validation method and renewal access are determined for your installation.
Get an SSL quote with your address listIf you see a certificate warning, follow the TLS error checks before purchasing.
A certificate’s technical components
A CSR is a certificate request; the private key is kept secret on the server. Do not attach your private key to email or support messages. Choose the key algorithm and size appropriate for your installation environment.
Domain control is demonstrated through methods such as a DNS TXT record or HTTP validation file. Wildcard certificates may require DNS validation; involve your DNS administrator in the process.
The server certificate and intermediate certificates must be installed in the correct order. An incomplete chain can cause connection errors on some devices; check browsers and application clients together.
When a page opens over HTTPS, no images, fonts or scripts should still be requested over HTTP. Update application addresses and redirect HTTP requests to the correct HTTPS address.
If automatic renewal is used, monitor DNS access, the validation path and task execution. Check that the new certificate has actually been installed on the relevant server or load balancer.
HSTS requires browsers to use HTTPS. Settings that include subdomains or preloading should not be enabled until HTTPS compatibility has been verified for every subdomain.
ornek.com and www.ornek.com are separate server names. If you use both, check that both appear in your certificate’s name list. If you will use one certificate on another server, plan key management too.
A wildcard such as *.ornek.com generally covers one subdomain level. Build a separate SAN list for different brands or deeper subdomains; the certificate for an address being redirected must also be valid.
Share your domain coverage needsSSL is commonly used as the name for the certificate service. TLS is the protocol used for modern secure connections. The TLS versions supported by the server and its secure configuration matter as much as the certificate.
Free DV certificates that verify domain control may suit many projects. Check the hosting environment’s support for automatic validation and renewal. Paid options are considered for different needs such as organization validation, coverage or support.
SSL / TLS encrypts communications and helps verify the domain being connected to. It does not remove malware or alone fix weak passwords, outdated plugins or application vulnerabilities. Application security and backups should be planned separately.
For example, *.ornek.com generally covers subdomains at one level, such as panel.ornek.com; it does not automatically cover deeper levels such as a.panel.ornek.com. Check separately that the root domain and other required names appear in the certificate.
Validity periods and issuance conditions depend on the certificate authority and current browser rules. The service subscription term may differ from the validity of an individual certificate. Pricing, renewal and reissuance scope are specified in your quote.
Browser address-bar indicators change over time. Do not assume an organization-validated certificate will provide a particular address-bar color or visible organization name. Choose a certificate based on validation and technical requirements.
FROM SELECTION TO SETUP
Share the addresses to protect, your panel and organization validation needs. Let’s clarify installation and renewal scope.
