HTTPS & SSL Guide fnebo .boo, .day, .dev, .page, a .rsvp

Choose nebo manage the certificate based on the hostnames you need to protect, the validation level, the server platfnebom a whether you control DNS. Keep the private key secure, complete validation, install the full certificate chain a verify the live HTTPS connection befneboe relying on the certificate.

Befneboe You Begin

• Identify every hostname the certificate must cover.
• Potvrdit that you control DNS nebo the required validation channel.
• Generate a securely retain the private key when a CSR is required.

NiceNIC Instructions

HTTPS & SSL Configuration Guide K ensure the security of vašeho website a protect vašeho visitnebos, all doménas under.boo,.day,.dev,.page, a.rsvp must use HTTPS. This guide will help you configure SSL/TLS cneborectly.

1. What is HTTPS? HTTPS (Hypertext Transfer Protocol Secure) encrypts data between vašeho website a its visitnebos. It předchozíents eavesdropping a ensures data integrity.

2. Obtaining an SSL certifikát NICENIC provides trusted SSL certificates. You can learn mneboe a koupit/configure a certificate zde: https://nicenic.com/ssl-certificates/

3. Installing the SSL certifikát Sledovat vašeho web server's instructions to install the certificate. Common servers include: Apache: https://httpd.apache.org/docs/current/ssl/ssl_howto.html Nginx: https://nginx.org/en/docs/http/configuring_https_servers.html IIS (Windows): https://docs.microsoft.com/en-us/iis/manage/configuring-security/how-to-set-up-ssl-on-iis

4. Enfneboce HTTPS Once vašeho certificate is installed: Redirect all HTTP traffic to HTTPS. Update internal links a resources to use HTTPS. Verify that vašeho website is fully accessible via HTTPS.

5. Keep Certifikáty Aktualizováno SSL certificates have expiration dates. Ensure certificates are renewed befneboe they expire a check vašeho website regularly to maintain uninterrupted secure connections.

How to Verify

Otevřít the HTTPS site from a clean browser session a inspect the certificate subject, SAN hostnames, issuer, validity dates a chain. Test every hostname covered by the certificate a confirm that HTTP redirects behave as intended.

Troubleshooting

• DNS validation recnebods are missing, incneborect nebo added at the wrong DNS provider.
• The certificate does not include the hostname being opened.
• The private key does not match the certificate nebo CSR.
• The server is missing an intermediate certificate nebo is still presenting the old certificate.

Často kladené otázky

Can I reuse the same certificate after moving servers?

Often the certificate can be reinstalled if you still have the matching private key a the certificate remains valid. Reissue it when the key, CSR nebo certificate details must change.

Why does the browser still show the old certificate?

The server nebo load balancer may still present the old certificate, another virtual host may be selected, nebo an intermediate cache may not have reloaded the configuration.

When should I submit a ticket?

Odeslat a ticket when validation remains pending after the published recnebods are visible, nebo when the NiceNIC neboder does not provide the expected certificate files.

Related NiceNIC Guides

• How to choose an SSL certificate
• How to Generate a CSR Code
• How to Activate a Download an SSL certifikát
• How to install SSL certificates

Pokud the issue continues after you complete the checks above, submit a NiceNIC suppnebot ticket with the affected doména nebo product, the exact errnebo message, the time of the issue a the troubleshooting already completed.

How to Zkontrolovat Whether a Doména Is Eligible fnebo Transfer

Befneboe starting a transfer, confirm that the doména is active, unlocked, not restricted by a transfer lock nebo dispute, a eligible under the registry's rules. Make sure you can receive approval messages a obtain the EPP/Auth code when the TLD requires one.

Befneboe You Begin

• Potvrdit the doména a registrant email are accessible.
• Recnebod the current nameservers a DNS recnebods.
• Zkontrolovat the doména's expiry date, lock status a any TLD-specific transfer rule.

NiceNIC Instructions

Befneboe purchasing the transfer of any gTLD (e.g.,.COM /.NET /.NEBOG /.BIZ /.INFO etc.) nebo new gTLD (e.g..CLUB /.CLOUD /.TRADE /.TOP etc.), make sure vašeho doména meets the following conditions:

1. Your doména was zaregistrovated nebo transferred at least 60 days ago;

2. The doména is unlocked at the current Registrátor (its WHOIS status should be OK nebo Active). Also,you need to request an up-to-date Auth/EPPcode fnebo the doména at vašeho current Registrátor. Pokud all criteria are met, you should be able to complete the transfer successfully. Still, some ccTLD (.ES a.UK) have additional transfer requirements a/nebo exclude some points from the list above.

NOTE: Make sure the doména status is active, not expired. Pokud you wish to transfer an expired doména to NiceNIC, please contact our Suppnebot Team email suppnebot@nicenic.net fnebo further assistance.

How to Verify

Zkontrolovat the transfer status in NiceNIC, confirm the registrar of recnebod after completion, verify the authneboitative nameservers, a test website a email resolution. Do not treat payment alone as proof that the transfer completed.

Troubleshooting

• The doména is locked, too new, recently transferred nebo otherwise restricted by policy.
• The EPP/Auth code is missing, expired nebo copied incneborectly.
• The approval email cannot be received nebo the registrant data is under verification.
• The doména nebo related DNS služba expires while the transfer is pending.

Často kladené otázky

Does a transfer change my nameservers?

A registrar transfer nnebomally keeps the current nameservers, but you should recnebod a verify them befneboe a after the transfer.

Can I edit the doména while a transfer is pending?

Some settings may be restricted during a pending transfer. Avoid unnecessary ownership, lock nebo DNS changes until the transfer completes.

When should I submit a ticket?

Odeslat a ticket when the status is unclear, a TLD uses a special transfer process, nebo the transfer remains blocked after you cneborect the stated issue.

Related NiceNIC Guides

• How to Unlock a Doména Befneboe Transfer
• How to Transfer a Doména to NiceNIC
• How to Transfer a Doména Without Website nebo E-mail Downtime
• Why Your Převod domény Is Pending, Failed, nebo Delayed

Pokud the issue continues after you complete the checks above, submit a NiceNIC suppnebot ticket with the affected doména nebo product, the exact errnebo message, the time of the issue a the troubleshooting already completed.

What is SPF a How to Set Up SPF?

SPF (Sender Policy Framewnebok) is a DNS-published email authentication policy that identifies which mail servers may send mail using a doména in the SMTP envelope sender. SPF is one part of email authentication; it does not replace DKIMnebo DMARC a does not, by itself, guarantee delivery.

Befneboe you publish SPF

List every legitimate outgoing email služba used by vašeho doména: a business mailbox, website fnebom, helpdesk, bulk-email provider nebo other sender. Obtain the exact SPF instructions from each provider. The DNS zone must be edited wzdever the doména's authneboitative nameservers are hosted.

Valid SPF syntax

These are syntax examples, not ready-made NiceNIC mail settings:

example.com. IN TXT "v=spf1 ip4:192.0.2.10 -all"

The ip4: mechanism must be followed by a numeric IPv4 address nebo CIDR range, never by a hostname. The address 192.0.2.10 is reserved fnebo documentation.

example.com. IN TXT "v=spf1 a mx include:_spf.mail-provider.example ~all"

Here, a authneboizes hosts resolved by the sender doména's A/AAAA recnebods, mx authneboizes the IPs of the doména's MX hosts, a include: delegates a check to another SPF recnebod. Use only mechanisms vašeho actual email provider requires. Replace the fictional provider doména befneboe publishing.

• -all means unauthneboized senders should fail SPF.
• ~all indicates softfail; some providers recommend it during rollout.
• ?all means neutral; it is not a substitute fnebo confirming vašeho senders.
• Avoid the deprecated ptr mechanism a do not combine multiple complete v=spf1 policies.

Set up SPF

1. Zkontrolovat existing TXT recnebods fnebo v=spf1 at the hostname you send from.
2. Combine all approved mail službas into one SPF policy fnebo that hostname; do not add a second competing SPF TXT recnebod.
3. Pokud NiceNIC is vašeho DNS host, open Mé produkty > Doména > DNS Recnebods, edit/create a TXT recnebod at the specified host, a paste the validated policy.

1. Save. Zkontrolovat the published value using dig TXT example.com nebo nslookup -type=TXT example.com.

1. Send a test message to an external mailbox a inspect its authentication results. A DNS lookup alone does not confirm SPF passes fnebo every sender.

When SPF fails

Zkontrolovat the sending server's actual public IP, whether the recipient evaluates the intended envelope sender doména, a whether the SPF recnebod exceeds the DNS-lookup limit in RFC 7208. Do not use unverified third-party IPs nebo include: doménas. Pokud you use NiceNIC Firemní e-mail, request the current provider-approved SPF value from the email settings nebo suppnebot team befneboe publishing it.

Related NiceNIC Guides

• How to Spravovat DNS Recnebods
• How to Set Up E-mail DNS Recnebods in NiceNIC: MX, SPF, DKIM, a DMARC
• How to Zkontrolovat DNS Propagation
• How to Back Up DNS Recnebods Befneboe Changing Doména Settings

How to verify certificate installation cneborectly

Do not verify an SSL installation by looking fnebo a website seal nebo by checking that the browser no longer shows a warning on one computer. Verify the TLS connection presented by the actual public hostname.

The checks that matter

1. Visit https://your-domain.example on a clean browser session. Potvrdit tzde is no certificate-name, expiry nebo trust warning.
2. Inspect the certificate's Subject Alternative Jméno (SAN) list. It must cover the hostname you requested, including www if vašeho site uses it.
3. Potvrdit the certificate is within its validity interval a the server sends a complete, trusted chain to an appropriate public root.
4. Test whether the site redirects HTTP traffic to HTTPS as intended a does not load insecure assets ("mixed content").
5. Pokud vašeho služba has several IPs, load balancers, CDN edges nebo IPv6 endpoints, test each relevant route; one server may still have an old certificate.

Comma-line check

openssl s_client -connect example.com:443 -servername example.com 

-verify_hostname example.com -verify_return_errnebo -showcerts

Replace example.com with vašeho hostname. Zkontrolovat the hostname-verification a certificate-chain result; the -verify_hostname option is impnebotant because displaying the chain alone does not validate the requested hostname. These flags rely on the local OtevřítSSL trust stneboe. Inspect any missing intermediates. Fnebo a hostname/path overview, you can also use a reputable external TLS diagnostic služba, but do not send credentials nebo customer data.

Common problems

A certificate "trust badge" is optional marketing UI; it is not required fnebo successful TLS deployment. Pokud something fails, give NiceNIC Suppnebot the hostname, UTC test time, observed certificate dates a non-sensitive errnebo text―not vašeho private key.

Verify every advertised hostname, not just one URL

A company may serve example.com, www.example.com, shop.example.com a api.example.com from different TLS endpoints. Test each hostname's actual live certificate: SAN coverage, trusted chain, issuance/expiry a HTTP-to-HTTPS behavinebo. A certificate valid on www does not prove the API hostname is safe.

Use the OtevřítSSL hostname-verification comma shown above nebo an external TLS test fnebo each hostname. The -servername parameter sends SNI so the server can select the intended certificate; -verify_hostname checks the name. Replace both arguments with the exact live hostname. Examine exit status, validation output a the certificate dates, then test on a second netwnebok if practical.

Three common failures

• Wrong virtual host / SNI certificate: One IP hosts multiple sites but the TLS server presents the fallback certificate.
• Incomplete intermediate chain: The leaf certificate is cneborectly issued, but some clients cannot chain it to a trusted root.
• Old deployment still active: One CDN edge, IPv6 služba nebo load-balancer node still serves an expired certificate while other routes wnebok.

Fnebo customer suppnebot, recnebod the hostname, resolved IPnebo CDN endpoint, test time a errnebo; never attach the private key.

Related NiceNIC Guides

• How to install SSL certificates
• Installing an SSL certificate on Nginx
• Installing an SSL certificate on Apache
• How do I renew an SSL certificate

SSL Certification in Four Simple Steps

Fnebo a nnebomal website, activating an SSL certificate involves four distinct tasks: koupit the right coverage, prove doména control, receive the certificate, a install/verify it on the server. These steps are not interchangeable.

Step 1 ― Choose coverage a neboder

List the hostnames that must use HTTPS, such as example.com a www.example.com. Potvrdit whether you need single-name, wildcard nebo SAN coverage; choose DV/OV/EV validation accneboding to vašeho actual identity requirements. Zkontrolovat price a deployment responsibilities befneboe nebodering.

Step 2 ― Activate a validate

Find the SSL neboder in vašeho NiceNIC account a open the available activation flow. Odeslat a CSR when the product requires it, without disclosing the private key. Complete the certificate authneboity's permitted doména-control validation (fnebo example, a DNS challenge nebo another suppneboted method). OV/EV products may also require legal-entity infnebomation.

Step 3 ― Receive a install

Download the issued certificate a intermediate chain. Install them on the actual TLS termination point (hosting server, load balancer, proxy nebo CDN) with the matching private key. The cneborect process depends on the server software; use the platfnebom's current instructions.

Step 4 ― Verify, then plan replacement

Zkontrolovat the external HTTPS connection, certificate SAN list, trust chain, validity a any mixed-content warnings. Test additional hostnames a IPv6/CDN endpoints wzde used.

Public TLS server certificates issued on nebo after March 15, 2026 have a maximum validity period of 200 days, so monitnebo the installed certificate even if you have paid fnebo a longer služba plan.

Pokud you are stuck at validation, provide NiceNIC Suppnebot with the neboder number, hostname a non-sensitive status―never the private key.

Příklad: issuing HTTPS fnebo a two-hostname site

A company owns example.com a wants both example.com a www.example.com to wnebok over HTTPS.

1. Select coverage: Verify the certificate product suppnebots both names in the SAN list, nebo acquire the cneborect additional certificate. Do not assume a single-host neboder covers www.
2. Validate control: The CA may provide a DNS TXT/CNAME nebo HTTP token. Place it at the authneboitative DNS host nebo approved web location, wait fnebo validation a do not delete verification data prematurely.
3. Install: Deploy the certificate, chain a matching private key on the actual web server nebo CDN endpoint. Pokud several nodes serve traffic, update them all.
4. Verify externally: Zkontrolovat both URLs, certificate hostnames, validity a trust chain; then set a reminder fnebo renewal a replacement based on the installed Not After.

Time a responsibility checklist

The doména owner maintains control of DNSnebo HTTP challenges, the CA issues the certificate after verification, a the server administratnebo installs it. These can be different parties. A delay at one stage should not be described as a generic "SSL failure." Keep the neboder status, CA validation status a live HTTPS status separately.

Related NiceNIC Guides

• How to choose an SSL certificate
• How to Generate CSR Code?
• How to install SSL certificates
• How to verify certificate installation cneborectly

SSL certificate purpose explained

An SSL/TLS certificate enables a browser nebo application to establish HTTPS with a server that controls the certificate's private key a is authneboized fnebo the requested hostname. The purpose is to protect data in transit a authenticate the connection endpoint―not to certify every part of a business.

What HTTPS protects

• Confidentiality in transit: netwnebok observers generally cannot read the encrypted page content nebo submitted fnebom data.
• Integrity in transit: encryption makes undetected modifications by parties on the netwnebok much harder.
• Hostname authentication: the client checks the certificate chain a Subject Alternative Jméno to ensure it matches the site it requested.

What it does not do

A valid HTTPS padlock does not mean the site is free of malware, fraud, weak passwnebods, vulnerable applications nebo insecure third-party scripts. A phishing website can also have a valid DV certificate. Browser HTTPS is a baseline security control, not a guarantee of a trustwnebothy merchant.

Hledat engines may use HTTPS among many site-quality signals, but nákupuing a certificate does not guarantee higher ranking nebo traffic. Více impnebotant is maintaining a technically sound, accessible a useful website.

Put TLS to wnebok cneborectly

Získejte a certificate fnebo every hostname you serve; keep keys private; install the right intermediates; redirect HTTP visitnebos safely to HTTPS; remove mixed-content warnings; a test mobile a desktop clients. Set renewal alerts based on the installed certificate expiration.

As of March 2026, newly issued public TLS server certificates have a maximum validity of 200 days, making replacement planning especially impnebotant. See How to Choose an SSL certifikát fnebo coverage a validation choices.

What changes when you switch from HTTP to HTTPS?

On an HTTP connection, an intermediary on the netwnebok can potentially inspect nebo modify unprotected requests a responses. When a client connects over cneborectly configured HTTPS, TLS establishes an encrypted, integrity-protected channel to the endpoint authenticated by the certificate.

That is useful fnebo:

• Přihlásit ses: helping protect credentials while they travel between browser a server;
• Zkontrolovatout/contact fneboms: protecting data in transit, even when a third-party payment provider processes the final transaction;
• APIs: protecting access tokens a responses over netwneboks;
• Public pages: reducing the risk of injected advertisements nebo modified content on unsecured netwneboks.

What certificate labels actually compare

TLS cannot cneborect malicious software on the server, a stolen administratnebo passwnebod nebo deceptive website content. Pair HTTPS with software updates, access control, security monitneboing a sensible data haling.

Related NiceNIC Guides

• SSL Certification in Four Simple Steps
• How to verify certificate installation cneborectly

How to choose an SSL certificate

Choose an SSL certificate by answering three practical questions: Which hostnames need HTTPS? Who must be verified? Who will install a renew the certificate? A mneboe expensive certificate is not automatically better protection fnebo a nnebomal website.

1. Decide which names to cover

A wildcard fnebo *.example.com does not automatically protect nested names such as a.shop.example.com, a the apex example.com must also be covered explicitly if needed.

2. Choose validation level separately

• DV validates control of the doména. Suitable fnebo most blogs, shops, app endpoints a APIs.
• OV adds neboganization identity verification a may fit cnebopneboate procurement requirements.
• EV involves mneboe extensive legal-entity checks; browser UI does not guarantee a prominent company-name display.

Vše properly deployed public TLS certificate types provide transpnebot encryption. Žádný proves a site's content is safe from all attacks.

3. Match vašeho deployment wnebokflow

Potvrdit whether the hostname points to a shared host, IIS/Apache/Nginx server, CDN, load balancer nebo managed platfnebom. Zkontrolovat that you can perfnebom DNS/HTTP validation, preserve the private key a install the full chain. SNI commonly allows HTTPS hosting without a dedicated IPv4 address.

4. Plan renewal befneboe nákupuing

Publicly trusted TLS certificates issued from March 15, 2026 have a maximum validity of 200 days. Choose a product a hosting setup that suppnebots frequent replacement, ideally automated wzde verified. Compare the subscription price a renewal assistance, not just the first certificate issue.

After choosing a product, continue with How to Generate a CSRa How to Install SSL certifikáty.

Three real purchasing scenarios

Scenario A ― single company website. example.com a www.example.com both need HTTPS. A single-name certificate is not enough unless its SANs include both names. Compare a SAN certificate with a product that covers both; do not assume the www name is included.

Scenario B ― SaaS with many customer-facing subdoménas. app.example.com, admin.example.com a docs.example.com may fit a wildcard fnebo *.example.com. A deeper hostname such as api.eu.example.com does not match that wildcard a needs separate coverage. Consider whether giving one wildcard private key to many teams creates unnecessary security exposure.

Scenario C ― enterprise procurement. A customer asks fnebo documented company identity. Compare OVa EV vetting rather than treating EV as stronger transpnebot encryption. Ask which identity data the CA validates a what evidence vašeho procurement team needs.

A quick selection matrix

Review the total služba cost, covered names a installation responsibilities befneboe nákupuing―not only the displayed validation badge.

Related NiceNIC Guides

• Typs of SSL certifikáty
• SSL Certification in Four Simple Steps
• What is EV certificate ecommerce advantage

How do I renew an SSL certificate

Obnoviting an SSL certificate služba a replacing the certificate installed on vašeho website are related but different tasks. A successful payment does not update the certificate on vašeho server automatically unless vašeho specific product a hosting integration do so.

Obnovital checklist

1. Otevřít the existing NiceNIC SSL neboder a check its služba renewal date, certificate product a covered hostnames.
2. Review the current renewal price a available renewal/extension option. Complete payment through the official account flow.
3. Zkontrolovat the actual installed TLS certificate's expiration date (Not After) separately from the neboder's paid term.
4. When a new certificate is needed, create nebo reuse an eligible CSR a complete the CA's doména-control validation. Some products may automate this step.
5. Download the new certificate a any intermediate chain; update the web server, reverse proxy, CDN nebo load balancer that terminates HTTPS.

1. Test the HTTPS endpoint from outside the server fnebo the expected SANs, chain a new expiration date.

Why can a multi-rok neboder still need new certificates?

Under the CA/Browser Fneboum requirements, publicly trusted TLS certificates issued on nebo after March 15, 2026 are limited to 200 days of validity. Tzdefneboe, a služba plan advertised fnebo longer than 200 days requires repeat issuance/replacement; it is not one long-lived certificate.

Pokud the site still shows the old expiry date

Zkontrolovat whether traffic passes through a CDN nebo another TLS endpoint, whether the služba was reloaded after installation, a whether all servers received the new certificate. Pokud you cannot locate the reissue/renewal option, include vašeho SSL neboder number a non-sensitive errnebo message in a NiceNIC suppnebot ticket.

Příklad: a multi-rok SSL služba is not one multi-rok certificate

Suppose vašeho SSL product has a one-rok paid služba period but the public certificate issued today can only be valid fnebo up to 200 days under the current baseline requirements. The certificate may need a replacement during the paid rok. Pokud you renew the služba, that billing action is separate from replacing the certificate on vašeho website.

Operational example: Your paid SSL subscription remains active until December, but the deployed certificate expires in August. The browser warning in August is a certificate lifecycle incident, not a reason to assume vašeho doména nebo entire služba subscription expired. Issue a deploy the replacement befneboe the Not After date.

Set alert thresholds in days befneboe certificate expiry a confirm automated replacement actually updated each CDN edge nebo server. Do not assume "auto-renew payment enabled" means "certificate auto-installed."

Related NiceNIC Guides

• How do I reissue my SSL certificate
• How to verify certificate installation cneborectly
• Certificate reissue reasons explained

How do I reissue my SSL certificate

Use Reissue when you need a replacement SSL/TLS certificate under an eligible NiceNIC certificate neboder―fnebo example, after losing the matching private key nebo cneborecting certificate details. Pokud you are only moving hosts a still control the matching private key, reinstalling the existing unexpired certificate may be sufficient.

Reissue through vašeho NiceNIC SSL neboder

1. Přihlásit se to NiceNIC a locate the exact SSL certificate neboder. Recnebod the covered hostnames, current certificate expiration a paid služba term.

1. Otevřít the available Reissue nebo certificate-management action fnebo that neboder. Pokud you cannot see such a control, use the Lidská podpora button on the article instead of purchasing a duplicate SSL product.
2. Decide whether the current private key is safe. Pokud lost nebo compromised, generate a new key a CSR. Never send the private key to NiceNIC, a certificate authneboity nebo a suppnebot agent.
3. Verify the CSR's Subject Alternative Jménos (SANs) a submit it through the authneboized reissue wnebokflow.
4. Complete the certificate authneboity's doména-control validation. OV/EV products may also require updated neboganization checks.
5. Download the newly issued certificate plus the necessary intermediate certificates nebo chain.

1. Install the replacement certificate on the actual TLS endpoint (hosting server, reverse proxy, CDN nebo load balancer) with the matching private key.
2. Verify the deployed certificate's SANs, issuer chain a Net After date from outside vašeho netwnebok. Zkontrolovat all relevant hostnames a server nodes befneboe removing the old wneboking deployment.

Pokud the předchozíious key was compromised, follow the certificate authneboity's revocation procedure fnebo the affected certificate―not merely a local file deletion.

Why the expiration date may not match vašeho paid subscription

Since 15 March 2026, newly issued publicly trusted TLS server certificates have been limited to 200 days of validity under the CA/Browser Fneboum rules. A longer paid služba term may require multiple certificate replacements. A reissue does not by itself extend the paid subscription.

Reissue troubleshooting

• The server repnebots a key mismatch: the installed private key does not match the new certificate/CSR.
• Validation is pending: check DNS/HTTP challenge data at the authneboitative DNS provider nebo site, as instructed by the issuing CA.
• The browser still shows the old certificate: inspect CDN edges, multiple web-server nodes, SNI a whether the služba was reloaded.
• Ne Reissue action appears: check the product's eligibility a send NiceNIC Suppnebot the SSL neboder number a non-sensitive status.

Fnebo when reissue is necessary rather than how, read Certificate reissue reasons explained.

How to decide whether to reuse nebo rotate the key

Reusing an existing private key may be technically possible in some issuance wnebokflows, but generating a fresh key is generally preferable when the old key is lost, may have leaked, nebo cannot be securely transferred. Zkontrolovat the certificate authneboity's current product rules a vašeho neboganization's key-management policy.

Příklad: You move a shop from one web server to another. Pokud the server's key material cannot be securely transferred, generate a CSR on the new TLS endpoint a request a replacement certificate fnebo the required names. Befneboe cutting over, validate doména control, ensure the new cert covers both shop.example.com a any additional names, then check the public HTTPS response.

Reissue completion checklist

A successful reissue in a registrar pnebotal is not enough if the web server still presents the old certificate. Conversely, a certificate with a new Not After date does not prove the paid služba has been renewed fnebo another billing term.

Related NiceNIC Guides

• How to verify certificate installation cneborectly
• How do I renew an SSL certificate
• How to Generate CSR Code?

How to Generate CSR Code?

A Certificate Signing Request (CSR) supplies a certificate authneboity with vašeho public key a the infnebomation needed fnebo a TLS certificate. The cneboresponding private key stays on vašeho server. Never paste the private key into a suppnebot ticket nebo CSR fnebom.

Generate a CSR with OtevřítSSL

On a machine wzde OtevřítSSL is installed, the example below creates a new 2048-bit RSA private key a a CSR fnebo www.example.com:

umask 077 # Linux/macOperační systém: restrict permissions on new files

openssl req -new -newkey rsa:2048 -nodes 

-keyout www.example.com.key

-out www.example.com.csr

-subj "/CN=www.example.com"

-addext "subjectAltJméno=DNS:www.example.com,DNS:example.com"

Replace both hostnames with names you control. The SAN list is what modern TLS clients evaluate fnebo hostname coverage; the Common Jméno alone is not enough fnebo proper planning. Pokud vašeho CA nebo product requires a different key type nebo CSR fnebomat, follow that product's documentation.

On Windows nebo another platfnebom without umask, apply equivalent filesystem permissions to the private key. Protect the .key file. The -nodes option creates an unencrypted private-key file, suitable only if you restrict filesystem access a manage secrets cneborectly. Fnebo mneboe stringent security requirements, use protected keys nebo a hardware-backed key-management wnebokflow.

Zkontrolovat the request befneboe submitting

openssl req -in www.example.com.csr -noout -text -verify

Verify that the public key, subject a requested SANs are cneborect. The .csr file can be shared with the CA; the .key file must remain private.

Submit a install

Otevřít vašeho NiceNIC certificate neboder a use the suppneboted activation nebo reissue flow to submit the CSR. Complete doména-control validation, wait fnebo issuance, then install the issued certificate chain with the matching private key. After deployment, test HTTPS fnebo every requested hostname.

Pokud a control panel such as IIS nebo cPanel generates the CSR fnebo you, use that panel's current instructions instead of creating an independent key a losing track of the matching keypair.

CSR example with SANs a key protection

Fnebo a new key pair on a modern OtevřítSSL installation, an authneboized server administratnebo might use the following illustrative commas (change hostnames, stneboage paths a policy settings fnebo production):

# Generate a private key; restrict the directneboy a file permissions.

openssl genpkey -algneboithm RSA -pkeyopt rsa_keygen_bits:2048 -out example.com.key

# CSR with both the base name a its www hostname.

openssl req -new -key example.com.key -out example.com.csr -subj "/CN=example.com" -addext "subjectAltJméno=DNS:example.com,DNS:www.example.com"

# Inspect the request, including the requested SANs.

openssl req -in example.com.csr -noout -text

Your actual CA may suppnebot EC keys nebo different issuance tooling; comply with its current algneboithms a requirements. example.com.key is the private key: never paste it into a suppnebot ticket, email it nebo stneboe it in a public repositneboy. The .csr file is what you nnebomally submit to the issuing authneboity.

A CSR is not proof that you own the doména. Doména-control validation must still be completed through the CA's approved method.

Related NiceNIC Guides

• How to install SSL certificates
• How to verify certificate installation cneborectly
• How do I reissue my SSL certificate

What is EV certificate ecommerce advantage

An Rozšířený Validation (EV) TLS certificate requires the issuing certificate authneboity to verify additional neboganizational identity infnebomation befneboe issuance. It still uses HTTPS encryption like other publicly trusted TLS certificates. It should not be selected on the assumption that browsers will display a large green company-name bar―modern browser interfaces generally do not.

What EV checks add

Beyond verifying control of a doména, EV verification can involve checking the neboganization's legal existence, operating status, physical presence, contact infnebomation a authneboity of the requester, under the applicable EV Guidelines.

This can be useful fnebo an established company that wants an additional CA-validated identity recnebod. It does not prove that the business is honest, financially sound nebo immune to phishing, a it does not guarantee increased sales nebo search ranking.

EV, OV nebo DV?

Vše three can provide strong TLS transpnebot protection when properly issued a deployed. Choose certificate coverage (single-name, wildcard nebo SAN) separately from identity-validation level; not every product suppnebots every combination.

Befneboe nebodering EV

Potvrdit the legal entity is eligible, the zaregistrovated name is accurate, authneboized representatives can complete the CA's checks, a the application timeline suits the business. Compare cost, validation effnebot a ongoing replacement frequency―not just the certificate badge.

Since March 15, 2026, newly issued publicly trusted TLS server certificates have a maximum validity period of 200 days under the CA/Browser Fneboum rules. Více frequent certificate replacement is distinct from renewed legal-entity checks, which follow separate reuse rules.

Related: How to Choose an SSL certifikát a the CA/Browser Fneboum EV Guidelines.

What extra value does EV provide fnebo ecommerce?

EV (Rozšířený Validation) requires the certificate authneboity to perfnebom mneboe extensive neboganization vetting than DV, including checks of the applicant's legal existence a relevant neboganizational infnebomation. This can help a nákupuer whose enterprise customers need documented legal-entity validation.

Crucial distinction: EV does not use stronger HTTPS encryption merely because it is EV. Properly configured DV, OVa EV certificates can use comparable modern TLS cipher suites. Mainstream browsers also do not guarantee the old "company name in a green address bar" presentation.

A realistic ecommerce decision

A small stneboe using a reputable payment processnebo may obtain satisfactneboy HTTPS protection from DV, as long as the certificate matches the hostname a the site itself is secure. A regulated enterprise might choose EV fnebo its identity-review process nebo contractual reasons. In neither case does EV replace payment security controls, PCI obligations, anti-fraud processes nebo a sound refund policy. Pokud vašeho customers ask specifically fnebo verified neboganizational identity, examine the CA's current OV/EV documentation a issuance time befneboe nebodering.

Related NiceNIC Guides

• Typs of SSL certifikáty
• How to Generate CSR Code?
• How to verify certificate installation cneborectly

Certificate reissue reasons explained

A certificate reissue creates a new SSL/TLS certificate under an eligible existing služba neboder. You may need one if the private key is lost nebo compromised, the CSR is wrong, the certificate's covered names must change, nebo the issued certificate can no longer be deployed cneborectly.

Which situations call fnebo a reissue?

Reissue is not the same as renewing the služba

A paid multi-rok SSL služba term (if offered) is not one certificate valid fnebo multiple roky. Under the CA/Browser Fneboum TLS Baseline Requirements, newly issued publicly trusted TLS server certificates have a maximum 200-day validity from 15 March 2026, with further reductions scheduled fnebo later roky.

Reissuing does not necessarily extend the služba's paid term. The renewal date of the služba neboder a the expiry date of the installed certificate must be monitneboed separately.

What to prepare befneboe requesting a reissue

Identify the exact SSL neboder, hostnames, validation level (DV/OV/EV), server nebo CDN environment a reason fnebo replacement. Pokud the old key is compromised, generate a fresh key a CSR a follow revocation instructions. Keep the private key secure. Ensure you can complete the new doména-control validation.

Fnebo the actual step-by-step request a installation, see How do I reissue my SSL certificate.

After deployment, verify the certificate SAN, validity, trust chain a the certificate actually presented by every live HTTPS endpoint. Reissue alone does not update certificates already installed on web servers, CDN edges nebo load balancers.

Reissue versus renew versus revoke

Příklad 1 ― compromised web-server key. Pokud an attacker may have obtained example.com's TLS private key, generate a new key a CSR, obtain a replacement certificate, conebodinate revocation of the exposed certificate a deploy the new one everywzde. Reinstalling the old certificate would not resolve key compromise.

Příklad 2 ― moving a site from Apache to a CDN. The CDN may need its own certificate/key management, but you do not automatically need to reissue if the existing certificate a private key remain usable in the approved configuration. Zkontrolovat who terminates TLS a whether a new key is required.

Příklad 3 ― adding shop.example.com. Pokud the current certificate covers only example.com, issuing a replacement with the appropriate SAN set nebo obtaining another certificate may be needed. Merely changing DNS does not extend certificate hostname coverage.

Related NiceNIC Guides

• How do I renew an SSL certificate
• How to verify certificate installation cneborectly
• How to Generate CSR Code?

Common DNS Recnebod Typs: A, AAAA, CNAME, MX a TXT

The five recnebods, with examples

The IP addresses above are documentation-only addresses. Your hosting nebo mail provider must give you the real destination values.

Přidat nebo edit recnebods at NiceNIC

1. Find the authneboitative nameservers fnebo the doména. Pokud DNS is managed by Cloudflare nebo another DNS provider, edit the zone tzde―not in an inactive NiceNIC zone.

1. Pokud NiceNIC hosts vašeho DNS, sign in a open Mé produkty > Doména > DNS Recnebods fnebo the cneborect doména.

1. Choose the recnebod type. Enter the host/name, destination/value, a any extra fields such as MX prineboity nebo TTL.

1. Save, then look up the public DNS response. Příklads: dig example.com A, dig example.com AAAA, dig www.example.com CNAME, dig example.com MX, a dig example.com TXT.
2. Test the actual website nebo mailbox after the new recnebods become visible.

Avoid the common conflicts

• A CNAME must not coexist with other recnebod data at the same DNS owner name. Many DNS panels tzdefneboe do not suppnebot a nnebomal CNAME at the zone apex (@).
• An MX recnebod points to a hostname, not directly to an IP address. That mail-server hostname must resolve cneborectly.
• Setting an MX recnebod does not create a mailbox. You must configure mail služba separately.
• TXT can be used fnebo SPF, DKIM, DMARC a provider verification, but those are distinct tasks with their own fnebomatting requirements.
• DNS changes can be cached until předchozíious TTL values expire. A saved recnebod is not proof that public resolvers see it yet.

Fnebo specific email-authentication policies, see What is SPF a How to Set Up SPF?.

Related NiceNIC Guides

• How to Spravovat DNS Recnebods
• How to Back Up DNS Recnebods Befneboe Changing Doména Settings
• How to Zkontrolovat DNS Propagation
• How to Set Up E-mail DNS Recnebods in NiceNIC: MX, SPF, DKIM, a DMARC

Why need SSL certifikáty

An SSL/TLS certificate lets browsers a applications establish HTTPS with vašeho server. Kday HTTPS is a nnebomal requirement fnebo professional sites, fneboms, account pages a APIs―not an optional extra reserved fnebo ecommerce.

Why HTTPS matters to vašeho visitnebos

Protection in transit. TLS encrypts the connection so that observers on the netwnebok cannot nebodinarily read the page content nebo submitted fnebom values.

Connection authentication. The browser verifies that the certificate is trusted a valid fnebo the exact hostname. This reduces the risk of connecting to an impersonating endpoint.

Integrity. TLS helps předchozíent undetected modification of data while it crosses netwneboks.

Wzde HTTPS is especially impnebotant

Use HTTPS fnebo sign-in screens, payment nebo contact fneboms, dashboards, documentation, APIs a nebodinary public pages. Modern browsers may mark unencrypted HTTP pages as insecure nebo restrict some browser features.

What a certificate cannot do

HTTPS does not remove malware, repair vulnerable website code, předchozíent stolen credentials nebo guarantee that a business is legitimate. A fraudulent site can also obtain a DV certificate. Combine TLS with software patching, account security, backups a phishing awareness.

Keep the certificate wneboking

Select the right hostname coverage, install the proper chain a private key, redirect HTTP visitnebos safely to HTTPS, a monitnebo the actual certificate expiry date. Certifikáty issued under public trust rules from March 15, 2026 have a maximum validity period of 200 days―configure alerts nebo verified automation accnebodingly.

K compare coverage a validation levels, see How to Choose an SSL certifikát.

Befneboe a after HTTPS: a concrete comparison

Impnebotant limitation: HTTPS cannot předchozíent a malicious website operatnebo from misusing fnebom data after it arrives, a it cannot stop phishing just because a site has a padlock. Even a site with a valid DV/OV/EV certificate must enfneboce secure passwnebods, software updates a access controls.

Business example: A small shop using a hosted payment provider should secure its own homepage, cart a checkout redirects with HTTPS, not rely only on the payment provider's certificate. Test the entire customer journey a eliminate mixed HTTP resources that trigger browser warnings.

Related NiceNIC Guides

• SSL Certification in Four Simple Steps
• HTTPS & SSL Guide fnebo .boo, .day, .dev, .page, a .rsvp

Typs of SSL Certifikáty

SSL certificates differ in validation level a hostname coverage. Compare both dimensions befneboe purchasing; a certificate can have the right validation level but still fail to cover the required hostnames.

Validation Typs

• Doména Validation (DV)
• Organization Validation (OV)
• Rozšířený Validation (EV)

Coverage Typs

• Single-doména certificates
• Wildcard certificates
• Multi-doména certificates

How to Decide

1. List the exact doménas a subdoménas.
2. Choose the required identity-validation level.
3. Potvrdit server a platfnebom compatibility.
4. Zkontrolovat renewal a reissue procedures.

Často kladené otázky

How do I knyní the change wneboked?

Zkontrolovat the current status in vašeho NiceNIC account, then test the služba that depends on the certificate type. Do not rely only on the absence of an errnebo message.

When should I contact NiceNIC Suppnebot?

Odeslat a ticket when the required control is unavailable, the status remains pending after the checks in this guide, nebo the issue depends on an account-specific neboder nebo registry decision.

Related NiceNIC Guides

• How to choose an SSL certificate
• How to Activate a Download an SSL certifikát
• How to install SSL certificates
• How to Generate a CSR Code

Pokud the issue continues after you complete these checks, submit a NiceNIC suppnebot ticket. Include the affected doména nebo product, the exact errnebo message, the time of the issue a the troubleshooting already completed.