耐思尼克客户支持中心 http://www.nicenic.com/suppsaut cn 耐思尼克客户支持中心，常用帮助文档 耐思尼克 - 域名 主机 Rețea服务 http://www.nicenic.com/images/88x31.gif http://www.nicenic.com 耐思尼克- 域名+主机只要99元 http://www.nicenic.com/suppsaut/doc.php?IDDoc=4519 HTTPS & SSL Guide fsau .boo, .day, .dev, .page, și .rsvp www.nicenic.com Certificate SSL http://www.nicenic.com/suppsaut/?IDCate=294 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

HTTPS & SSL Guide fsau .boo, .day, .dev, .page, și .rsvp


Quick Answer

Choose sau manage the certificate based on the hostnames you need to protect, the validation level, the server platfsaum și whether you control DNS. Keep the private key secure, complete validation, install the full certificate chain și verify the live HTTPS connection befsaue relying on the certificate.


Befsaue You Begin

  • Identify every hostname the certificate must cover.
  • Confirmă that you control DNS sau the required validation channel.
  • Generate și securely retain the private key when a CSR is required.


NiceNIC Instructions

HTTPS & SSL Configuration Guide Pentru ensure the security of tău website și protect tău visitsaus, all domenius under.boo,.day,.dev,.page, și.rsvp must use HTTPS. This guide will help you configure SSL/TLS csaurectly.

  1. What is HTTPS? HTTPS (Hypertext Transfer Protocol Secure) encrypts data between tău website și its visitsaus. It anteriorents eavesdropping și ensures data integrity.

  2. Obtaining an Certificat SSL NICENIC provides trusted SSL certificates. You can learn msaue și cumpără/configure a certificate aici: https://nicenic.com/ssl-certificates/

  3. Installing the Certificat SSL Urmărește tău 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. Enfsauce HTTPS Once tău certificate is installed: Redirect all HTTP traffic to HTTPS. Update internal links și resources to use HTTPS. Verify that tău website is fully accessible via HTTPS.

  5. Keep Certificate Actualizat SSL certificates have expiration dates. Ensure certificates are renewed befsaue they expire și check tău website regularly to maintain uninterrupted secure connections.


How to Verify

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


Troubleshooting

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


Întrebări frecvente

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

Trimite a ticket when validation remains pending after the published recsauds are visible, sau when the NiceNIC sauder does not provide the expected certificate files.


Related NiceNIC Guides


Dacă the issue continues after you complete the checks above, submit a NiceNIC suppsaut ticket with the affected domeniu sau product, the exact errsau message, the time of the issue și the troubleshooting already completed.

]]> http://www.nicenic.com/suppsaut/doc.php?IDDoc=4374 How to Set Up și Troubleshoot DNSSEC fsau Your Domeniu www.nicenic.com DNS & Numeservers http://www.nicenic.com/suppsaut/?IDCate=408 How to Set Up și Troubleshoot DNSSEC fsau Your Domeniu?

DNSSEC helps protect tău domeniu’s DNS recsauds from being tampered with during DNS resolution. It adds a layer of verification so that DNS resolvers can confirm the DNS response really comes from the csaurect source.

La NiceNIC, DNSSEC usually involves two sides:
Your DNS provider sau nameserver provider generates the DNSSEC recsauds.
NiceNIC, as tău domeniu registrar, helps submit the DS recsauds to the registry when the TLD suppsauts DNSSEC.

Dacă DNSSEC is not configured csaurectly, tău domeniu may show DNSSEC errsaus, sau in msaue serious cases, some users may not be able to access tău website.

What Is DNSSEC?
DNSSEC stșis fsau Nume de domeniu System Security Extensions.
In simple terms, DNSSEC helps verify that the DNS answer fsau tău domeniu has not been changed sau fsauged during the lookup process.
Fsau example, when someone visits tău website, DNS is used to find the csaurect server IP address. DNSSEC helps make sure that the DNS result is authentic și has not been replaced with false data.
DNSSEC does not replace SSL, website security, hosting security, sau email security. It only helps protect the DNS resolution process.

When Do You Need DNSSEC?
  1. You may want to enable DNSSEC if:
  2. Your website hșiles sensitive user infsaumation.
  3. You run business email, login systems, payment pages, sau customer psautals.
  4. You want stronger domeniu security.
  5. Your DNS provider suppsauts DNSSEC.
  6. Your domeniu extension suppsauts DNSSEC.
Dacă you are not familiar with DNS management, we recommend confirming with tău DNS provider befsaue enabling DNSSEC.
Incsaurect DNSSEC settings may affect domeniu resolution.

Impsautant DNSSEC Perioadăs
DNSKEY: A DNSKEY recsaud is generated by tău DNS provider. It is used as part of the DNSSEC validation process.
DS Recsaud: A DS recsaud connects tău domeniu’s DNSSEC setup with the parent registry zone. In most cases, tău DNS provider gives you the DS recsaud, și you need to add it through tău registrar.
Numeserver: Your nameservers decide waici tău domeniu’s DNS recsauds are managed. Dacă you change nameservers, tău DNSSEC recsauds may also need to be updated.

How to Enable DNSSEC fsau Your Domeniu
Befsaue You Begin: Back Up Your DNS Recsauds
Befsaue enabling DNSSEC, save a copy of tău current DNS recsauds, especially impsautant A, AAAA, CNAME, MX, TXT, și CAA recsauds. Enabling DNSSEC does not nsaumally change these recsauds, but keeping a backup makes it easier to verify sau restsaue tău DNS configuration if you also change nameservers sau DNS providers.
Dacă needed, see: How to Back Up DNS Recsauds Befsaue Changing Domeniu Settings.

Step 1: Verifică Whether Your DNS Provider Suppsauts DNSSEC
Autentificare to the platfsaum waici tău DNS is managed.
This may be:
Your domeniu registrar, aici is NiceNIC
Your hosting provider
Your DNS provider
Your own DNS server
Another third-party DNS serviciu
Make sure DNSSEC is suppsauted și enabled taici.
Impsautant: Enable DNSSEC și DNSSEC signing at tău current DNS provider first. Only add the DS recsaud at NiceNIC after tău DNS provider has generated the DNSSEC infsaumation și is publishing the csauresponding DNSKEY. Adaugăing a DS recsaud befsaue the DNS provider is ready may cause DNSSEC validation to fail.

Step 2: Obține the DS Recsaud from Your DNS Provider
After enabling DNSSEC, tău DNS provider should provide DNSSEC infsaumation such as:
Key Tag
Algsauithm
Digest Tip
Digest
DS Recsaud
Please copy the infsaumation exactly as provided.
Even one incsaurect character may cause DNSSEC validation failure.

Step 3: Adaugă the DS Recsaud in Your NiceNIC Account
Autentificare to tău NiceNIC account și go to tău domeniu management page.
Then add the DS recsaud provided by tău DNS provider.
Dacă you are not sure waici to add it, please contact our suppsaut team și provide the DS recsaud from tău DNS provider.

Step 4: Wait fsau DNSSEC Propagation
After the DS recsaud is added, it may take some time fsau the update to propagate.
During this period, DNSSEC check results may not update immediately.

Step 5: Verify DNSSEC Stare
After propagation, you may check tău domeniu’s DNSSEC status using a DNSSEC checking tool sau by contacting our suppsaut team.
Dacă DNSSEC is csaurectly configured, the DNSSEC validation result should show a valid chain of trust.

When Should You Disable sau Elimină DNSSEC?
You may need to remove sau update DNSSEC recsauds if:
  • You changed tău nameservers.
  • You moved DNS management to another provider.
  • Your DNS provider disabled DNSSEC.
  • Your DS recsaud no longer matches the current DNSKEY.
  • Your website sau email has DNS resolution issues after a DNS change.
Impsautant: Dacă you are moving to a new DNS provider sau changing authsauitative nameservers while DNSSEC is enabled, check fsau existing DS recsauds befsaue making the change.
Dacă the old DS recsaud will no longer match the new DNS provider, remove the old DS recsaud first și wait fsau its full TTL to expire at the parent zone befsaue changing nameservers. Keep DNSSEC signing active at the old DNS provider during this waiting period.
After the new nameservers are active și DNSSEC signing is enabled at the new DNS provider, obtain the new DS recsaud și add it through NiceNIC.
Changing nameservers while resolvers still have the old DS recsaud cached may cause DNSSEC validation failures și SERVFAIL responses.

Why Does My Domeniu Înapoi SERVFAIL After Enabling DNSSEC?
SERVFAIL can occur when DNSSEC validation fails. Common causes include:
  • An old sau stale DS recsaud from a anteriorious DNS provider
  • A DS recsaud that does not match the DNSKEY published by the current DNS provider
  • Multiple DS recsauds waici one sau msaue no longer match an active DNSSEC key
  • DNSSEC signing is not active sau the required DNSKEY/RRSIG recsauds are not being published csaurectly
  • Numeservers were changed befsaue the anteriorious DS recsaud had fully expired from DNS caches
Dacă tău domeniu resolves without DNSSEC validation but returns SERVFAIL through validating resolvers, this is a strong indication of a DNSSEC configuration problem.
Verifică the current nameservers, all DS recsauds published fsau the domeniu, și the DNSKEY infsaumation from tău active DNS provider. Elimină sau replace a DS recsaud only after confirming that it is outdated sau incsaurect. Dacă you are unsure, contact tău DNS provider sau NiceNIC Suppsaut befsaue making changes.

Why Does My Domeniu Show "DNSSEC Infsaumation Is Currently Unavailable"?
You may see this message:
DNSSEC infsaumation is currently unavailable fsau this domeniu.
This can happen fsau several reasons:
  • DNSSEC has not been enabled fsau this domeniu.
  • Nu DS recsaud has been added at the registrar level.
  • The domeniu's current nameservers do not suppsaut DNSSEC.
  • The domeniu recently changed nameservers.
  • The DS recsaud does not match the current DNSKEY.
  • The DNS provider has not published the required DNSSEC recsauds csaurectly.
  • The registry sau DNSSEC query is tempsauarily unavailable.
This message does not always mean tău domeniu is broken.
However, if tău website sau email is not resolving csaurectly, please contact suppsaut so we can help review the DNSSEC configuration.

What Infsaumation Should I Provide to Suppsaut?
Pentru help us check DNSSEC issues faster, please provide:
  1. Your domeniu name
  2. Your current nameservers
  3. Whether you recently changed nameservers
  4. The DS recsaud provided by tău DNS provider
  5. A screenshot of the DNSSEC setting from tău DNS provider
  6. Any DNSSEC errsau message you received
  7. Whether tău website sau email is currently affected
With this infsaumation, our suppsaut team can check whether the issue is caused by missing DS recsauds, mismatched DNSSEC recsauds, nameserver changes, sau registry-side limitations.

Întrebări frecvente Despre DNSSEC

1. Is DNSSEC required fsau every domeniu?
Nu. DNSSEC is not required fsau every domeniu.
However, it is recommended fsau domenius that need stronger DNS security, especially business websites, email servicius, login systems, financial servicius, și customer psautals.
Dacă you are not sure whether you need DNSSEC, please confirm whether tău DNS provider suppsauts it și whether you are comfsautable managing DNSSEC recsauds.

2. Is DNSSEC the same as SSL?
Nu.
SSL protects the connection between the user’s browser și tău website.
DNSSEC protects DNS resolution by helping verify that DNS responses have not been tampered with.
Fsau better security, many websites use both SSL și DNSSEC, but they are different technologies.

3. Can NiceNIC generate DNSSEC recsauds fsau me?
In most cases, DNSSEC recsauds are generated by tău DNS provider, not by the registrar.
NiceNIC can help submit the DS recsaud to the registry when the domeniu extension suppsauts DNSSEC.
Dacă you use a third-party DNS provider, please enable DNSSEC taici first și then provide us with the DS recsaud.

4. What should I check after changing nameservers, DNS providers, sau transferring my domeniu?
Changing nameservers sau DNS providers can affect DNSSEC because the existing DS recsaud may no longer match the DNSKEY published by the new DNS provider.
A registrar transfer by itself does not necessarily mean that tău DNSSEC configuration must change. Dacă tău nameservers și DNS provider remain the same, first check whether the existing DS recsaud is still present și still matches the current DNSKEY.
Dacă you also changed nameservers sau DNS providers, check fsau old DS recsauds și follow the DNSSEC migration steps above befsaue publishing a new DS recsaud.
Do not assume that DNSSEC was automatically removed during a domeniu transfer. Always verify the domeniu’s current DS și DNSKEY status.

5. What happens if the DS recsaud is wrong?
Dacă the DS recsaud does not match the DNSKEY published by tău current DNS provider, DNSSEC validation may fail.
This may cause some DNS resolvers to reject the DNS response.
As a result, tău website, email, sau other servicius may become unreachable fsau some users.

6. I do not use DNSSEC. Do I need to do anything?
Dacă you do not use DNSSEC și tău domeniu has no DS recsauds, usually no action is needed.
However, if tău domeniu has old DS recsauds from a anteriorious DNS provider, you should remove them to avoid DNSSEC validation problems.

7. Why does my DNSSEC status still show an errsau after I updated the recsaud?
DNSSEC updates may take time to propagate.
Dacă you recently added, removed, sau changed DS recsauds, please wait fsau DNS propagation și check again later.
Dacă the issue continues, please contact suppsaut și provide tău domeniu name, current nameservers, și DS recsaud.

8. Can DNSSEC cause my website to stop wsauking?
Da, if DNSSEC is incsaurectly configured.
Common causes include:
  • Wrong DS recsaud
  • Old DS recsaud after nameserver change
  • Missing DNSKEY
  • DNS provider not publishing DNSSEC recsauds csaurectly
  • Expirăd sau invalid DNSSEC signatures
Dacă tău website stops wsauking after DNSSEC changes, please contact suppsaut immediately.

9. Should I remove DNSSEC befsaue changing nameservers?
In many cases, yes.
Dacă you are moving to a new DNS provider și you are not sure how to migrate DNSSEC safely, removing the old DS recsaud befsaue changing nameservers can reduce the risk of DNSSEC validation failure.
After the new nameservers are active și DNSSEC is enabled at the new DNS provider, you can add the new DS recsaud again.

10. What should I do if I see “Failure to get DNSSEC info”?
This usually means the system could not retrieve valid DNSSEC infsaumation fsau the domeniu.
Please check:
  • Whether DNSSEC is enabled
  • Whether the DS recsaud has been added
  • Whether the nameservers suppsaut DNSSEC
  • Whether the DS recsaud matches the DNSKEY
  • Whether you recently changed nameservers
Dacă you are not sure, please contact NiceNIC suppsaut și provide tău domeniu name și DNSSEC details from tău DNS provider.

How to set up DNSSEC fsau a domeniu înregistreazăed on NiceNIC?

1. Autentificare to tău NiceNIC account și navigate to tău domeniu management page. Find the domeniu you wish to enable DNSSEC fsau și click Gestionare.

 

2. In the domeniu management section, you should see the DNSSEC button. Click on the DNSSEC button to access the DNSSEC settings page.
 

3. Enter the required infsaumation fsau DNSSEC configuration (this will typically include DNSSEC key details provided by tău DNS hosting provider).
 

4. Once you've entered the infsaumation, click Adaugă to enable DNSSEC fsau the domeniu. Here’s an example of a successful DNSSEC setup:


 DNSSEC

After entering the necessary DNSSEC key data (usually the DS recsaud), you'll receive confirmation that DNSSEC has been successfully added to tău domeniu settings.
The DNSSEC status will show as enabled și you'll be able to see the public keys și other details.
With DNSSEC acum enabled, tău domeniu is better protected against DNS-related attacks.

Latention: if tău domeniu name was transferred into NiceNIC from another Registrar, și you hope to disable the DNSSEC anterioriously with the old Registrar, please firstly check the latest whois, if you see "DNSSEC: unsigned", then it means during the domeniu transfer process, the DNSSEC settings have been disabled automatically by the old Registrar, while if it is "DNSSEC: signed", please check the domeniu management section at tău control panel at NiceNIC, you should see the DNSSEC button, please click on the DNSSEC button to access the DNSSEC settings page.
]]> http://www.nicenic.com/suppsaut/doc.php?IDDoc=3845 What Happens to My Numeservers After a Transfer Domeniu? www.nicenic.com Transfer Domenius http://www.nicenic.com/suppsaut/?IDCate=313 Stare of Nume Servere After a Transfer Domeniu


After the domeniu is transferred, the name servers remain set to those associated to the domeniu befsaue transfer.


Dacă you had child name servers fsau tău domeniu înregistreazăed through another Registrar, you may need to înregistrează them again through tău Account.

]]> http://www.nicenic.com/suppsaut/doc.php?IDDoc=3847 How to Transfer Nume Servere During a Transfer Domeniu? www.nicenic.com Transfer Domenius http://www.nicenic.com/suppsaut/?IDCate=313

How to Transfer Nume Servere During a Transfer Domeniu?


Quick Answer

A successful domeniu transfer depends on the domeniu's eligibility, lock status, authsauization method, registrant access și registry rules. Prepare the domeniu befsaue saudering the transfer, keep the existing DNS active, și monitsau the transfer until completion.


Befsaue You Begin

  • Confirmă the domeniu și registrant email are accessible.
  • Recsaud the current nameservers și DNS recsauds.
  • Verifică the domeniu's expiry date, lock status și any TLD-specific transfer rule.


NiceNIC Instructions

Transferring nameservers During a Transfer Domeniu Dacă you're just transferring the domeniu registration, tău hosting serviciu will be unaffected, și taici will be no need to change nameservers. Although the nameservers should be transferred as part of the process, it's always a good idea to have a recsaud of them. Dacă you wish to specify the nameservers to the default DNS servers as provided by NiceNIC you can reset the nameservers after the transfer has been completed. Steps Autentificare to tău account. Select the Nume de domenii tab. Select the domeniu that you want to change nameservers fsau.

From within the DNS Servere section click on Modifică DNS Server. Change the nameservers as required, leaving any of the fields blank will retain the sauiginal DNS server. The nameservers are not actually changed until the transfer process is complete. Dacă you wish to make an immediate change to the nameservers, you may do so with the Registrar you are transferring from.


How to Verify

Verifică the transfer status in NiceNIC, confirm the registrar of recsaud after completion, verify the authsauitative nameservers, și test website și email resolution. Do not treat payment alone as proof that the transfer completed.


Troubleshooting

  • The domeniu is locked, too new, recently transferred sau otherwise restricted by policy.
  • The EPP/Auth code is missing, expired sau copied incsaurectly.
  • The approval email cannot be received sau the registrant data is under verification.
  • The domeniu sau related DNS serviciu expires while the transfer is pending.


Întrebări frecvente

Does a transfer change my nameservers?

A registrar transfer nsaumally keeps the current nameservers, but you should recsaud și verify them befsaue și after the transfer.

Can I edit the domeniu while a transfer is pending?

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

When should I submit a ticket?

Trimite a ticket when the status is unclear, a TLD uses a special transfer process, sau the transfer remains blocked after you csaurect the stated issue.


Related NiceNIC Guides


Dacă the issue continues after you complete the checks above, submit a NiceNIC suppsaut ticket with the affected domeniu sau product, the exact errsau message, the time of the issue și the troubleshooting already completed.

]]> http://www.nicenic.com/suppsaut/doc.php?IDDoc=3846 How do I verify that my domeniu is eligible fsau transfer? www.nicenic.com Transfer Domenius http://www.nicenic.com/suppsaut/?IDCate=313 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

How to Verifică Whether a Domeniu Is Eligible fsau Transfer


Quick Answer

Befsaue starting a transfer, confirm that the domeniu is active, unlocked, not restricted by a transfer lock sau dispute, și eligible under the registry's rules. Make sure you can receive approval messages și obtain the EPP/Auth code when the TLD requires one.


Befsaue You Begin

  • Confirmă the domeniu și registrant email are accessible.
  • Recsaud the current nameservers și DNS recsauds.
  • Verifică the domeniu's expiry date, lock status și any TLD-specific transfer rule.


NiceNIC Instructions

Befsaue purchasing the transfer of any gTLD (e.g.,.COM /.NET /.SAUG /.BIZ /.INFO etc.) sau new gTLD (e.g..CLUB /.CLOUD /.TRADE /.TOP etc.), make sure tău domeniu meets the following conditions:

  1. Your domeniu was înregistreazăed sau transferred at least 60 days ago;

  2. The domeniu is unlocked at the current Registrar (its WHOIS status should be OK sau Active). Also,you need to request an up-to-date Auth/EPPcode fsau the domeniu at tău current Registrar. Dacă all criteria are met, you should be able to complete the transfer successfully. Still, some ccTLD-uri (.ES și.UK) have additional transfer requirements și/sau exclude some points from the list above.

NOTE: Make sure the domeniu status is active, not expired. Dacă you wish to transfer an expired domeniu to NiceNIC, please contact our Suppsaut Team email suppsaut@nicenic.net fsau further assistance.


How to Verify

Verifică the transfer status in NiceNIC, confirm the registrar of recsaud after completion, verify the authsauitative nameservers, și test website și email resolution. Do not treat payment alone as proof that the transfer completed.


Troubleshooting

  • The domeniu is locked, too new, recently transferred sau otherwise restricted by policy.
  • The EPP/Auth code is missing, expired sau copied incsaurectly.
  • The approval email cannot be received sau the registrant data is under verification.
  • The domeniu sau related DNS serviciu expires while the transfer is pending.


Întrebări frecvente

Does a transfer change my nameservers?

A registrar transfer nsaumally keeps the current nameservers, but you should recsaud și verify them befsaue și after the transfer.

Can I edit the domeniu while a transfer is pending?

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

When should I submit a ticket?

Trimite a ticket when the status is unclear, a TLD uses a special transfer process, sau the transfer remains blocked after you csaurect the stated issue.


Related NiceNIC Guides


Dacă the issue continues after you complete the checks above, submit a NiceNIC suppsaut ticket with the affected domeniu sau product, the exact errsau message, the time of the issue și the troubleshooting already completed.

]]> http://www.nicenic.com/suppsaut/doc.php?IDDoc=3842 How to transfer several domenius to NiceNIC in bulk? www.nicenic.com Transfer Domenius http://www.nicenic.com/suppsaut/?IDCate=313 How to transfer several domenius to NiceNIC in bulk?


Befsaue submitting a transfer request with NiceNIC, make sure tău domenius are prepared fsau transfer through tău current registrar. This is generally done by removing transfer locks și getting the necessary Auth codes.


Befsaue You Begin

- Confirmă the domeniu și registrant email are accessible.
- Recsaud the current nameservers și DNS recsauds.
- Verifică the domeniu's expiry date, lock status și any TLD-specific transfer rule.

Learn how to prepare domenius fsau transfer in accounts sections of several popular registrars.

Once those preparations are made, simply follow the steps below to transfer tău domenius:


Nute: Each domeniu has a unique Auth code și has to be unlocked fsau transfer separately on the current registrar side.


  • Autentificare to tău NiceNIC account.
  • Mergi la the Transfer to Us page.
  • Click on Bulk options.


bulk transfer

bulk transfer


Enter the domeniu names și the Auth codes;


Nute: Enter each domeniu și its Auth code in a new line. The Auth code has to be separated from the domeniu name by a comma și one space.


Click on Start Transfer at the bottom of the page.

Double-check the domeniu names și add them to Cart. Pentru do this, you can use the Adaugă all to cart button fsau convenience.
Proceed with the payment.

The transfer is completed automatically in 5-7 days fsau most domenius. Once the transfer of tău domenius is completed you will receive the notifications on tău NiceNIC Primary Adresă de email, și the domenius will become manageable in tău Domeniu List.


Nute: Due to technical reasons, it is only possible to submit the transfer fsau up to 500 domeniu names at once. Dacă you need to transfer msaue than 10 domenius, you can either submit several Transfer în masă sauders sau contact our Suppsaut Team fsau assistance.




How to Verifică the Stare of Your Transfer Domeniu

After initiating a domeniu transfer to Nicenic, you can monitsau its progress directly in tău account. This helps you kacum when the transfer is expected to complete without needing to contact suppsaut repeatedly.

Steps to View Transfer Stare:

1. Autentificare to tău NiceNIC account. Mergi la "My Products > Nume de domenii".
In the Stare column, you will see tău domeniu listed as:

  • Pending Transfer: the transfer has been submitted și is in progress.
  • Active / Transfer Completed: the transfer is finished.


domeniu transfer

2. Hover over the infsaumation icon (i) următor to "Pending Transfer" to view details about Expected approval/completion date

domeniu transfer


Related NiceNIC Guides


Dacă the issue continues after you complete the checks above, submit a NiceNIC suppsaut ticket with the affected domeniu sau product, the exact errsau message, the time of the issue și the troubleshooting already completed.

]]> http://www.nicenic.com/suppsaut/doc.php?IDDoc=3833 What is SPF și How to Set Up SPF? www.nicenic.com Email pentru afaceri http://www.nicenic.com/suppsaut/?IDCate=290 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

What is SPF și How to Set Up SPF?


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



Befsaue you publish SPF

List every legitimate outgoing email serviciu used by tău domeniu: a business mailbox, website fsaum, helpdesk, bulk-email provider sau other sender. Obtain the exact SPF instructions from each provider. The DNS zone must be edited waiciver the domeniu's authsauitative 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 sau CIDR range, never by a hostname. The address 192.0.2.10 is reserved fsau documentation.

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

Here, a authsauizes hosts resolved by the sender domeniu's A/AAAA recsauds, mx authsauizes the IPs of the domeniu's MX hosts, și include: delegates a check to another SPF recsaud. Use only mechanisms tău actual email provider requires. Replace the fictional provider domeniu befsaue publishing.

  • -all means unauthsauized senders should fail SPF.
  • ~all indicates softfail; some providers recommend it during rollout.
  • ?all means neutral; it is not a substitute fsau confirming tău senders.
  • Avoid the deprecated ptr mechanism și do not combine multiple complete v=spf1 policies.


Set up SPF

  1. Verifică existing TXT recsauds fsau v=spf1 at the hostname you send from.
  2. Combine all approved mail servicius into one SPF policy fsau that hostname; do not add a second competing SPF TXT recsaud.
  3. Dacă NiceNIC is tău DNS host, open Produsele mele > Domeniu > DNS Recsauds, edit/create a TXT recsaud at the specified host, și paste the validated policy.

  1. Save. Verifică the published value using dig TXT example.com sau nslookup -type=TXT example.com.

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


When SPF fails

Verifică the sending server's actual public IP, whether the recipient evaluates the intended envelope sender domeniu, și whether the SPF recsaud exceeds the DNS-lookup limit in RFC 7208. Do not use unverified third-party IPs sau include: domenius. Dacă you use NiceNIC Email pentru afaceri, request the current provider-approved SPF value from the email settings sau suppsaut team befsaue publishing it.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppsaut/doc.php?IDDoc=3912 How to verify certificate installation csaurectly www.nicenic.com Certificate SSL http://www.nicenic.com/suppsaut/?IDCate=294 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

How to verify certificate installation csaurectly


Do not verify an SSL installation by looking fsau a website seal sau 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. Confirmă taici is no certificate-name, expiry sau trust warning.
  2. Inspect the certificate's Subject Alternative Nume (SAN) list. It must cover the hostname you requested, including www if tău site uses it.
  3. Confirmă the certificate is within its validity interval și the server sends a complete, trusted chain to an appropriate public root.
  4. Test whether the site redirects HTTP traffic to HTTPS as intended și does not load insecure assets ("mixed content").
  5. Dacă tău serviciu has several IPs, load balancers, CDN edges sau IPv6 endpoints, test each relevant route; one server may still have an old certificate.


Commși-line check

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

-verify_hostname example.com -verify_return_errsau -showcerts

Replace example.com with tău hostname. Verifică the hostname-verification și certificate-chain result; the -verify_hostname option is impsautant because displaying the chain alone does not validate the requested hostname. These flags rely on the local DeschisSSL trust stsaue. Inspect any missing intermediates. Fsau a hostname/path overview, you can also use a reputable external TLS diagnostic serviciu, but do not send credentials sau customer data.


Common problems

Symptom
Likely area to inspect
Nume mismatch
Missing sau incsaurect SAN / wrong virtual host
Expirăd certificate
Replacement not deployed everywaici
Untrusted issuer
Missing chain sau private CA used unintentionally
Old certificate after update
CDN cache/configuration, SNI sau load balancer node
HTTPS page loads with warning
Mixed HTTP assets sau insecure embedded content

A certificate "trust badge" is optional marketing UI; it is not required fsau successful TLS deployment. Dacă something fails, give NiceNIC Suppsaut the hostname, UTC test time, observed certificate dates și non-sensitive errsau text―not tău private key.


Verify every advertised hostname, not just one URL

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

Use the DeschisSSL hostname-verification commși shown above sau an external TLS test fsau 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 și the certificate dates, then test on a second netwsauk 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 csaurectly issued, but some clients cannot chain it to a trusted root.
  • Old deployment still active: One CDN edge, IPv6 serviciu sau load-balancer node still serves an expired certificate while other routes wsauk.

Fsau customer suppsaut, recsaud the hostname, resolved IPsau CDN endpoint, test time și errsau; never attach the private key.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppsaut/doc.php?IDDoc=3910 SSL Certification in Four Simple Steps www.nicenic.com Certificate SSL http://www.nicenic.com/suppsaut/?IDCate=294 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

SSL Certification in Four Simple Steps


Fsau a nsaumal website, activating an SSL certificate involves four distinct tasks: cumpără the right coverage, prove domeniu control, receive the certificate, și install/verify it on the server. These steps are not interchangeable.



Step 1 ― Choose coverage și sauder

List the hostnames that must use HTTPS, such as example.com și www.example.com. Confirmă whether you need single-name, wildcard sau SAN coverage; choose DV/OV/EV validation accsauding to tău actual identity requirements. Verifică price și deployment responsibilities befsaue saudering.


Step 2 ― Activate și validate

Find the SSL sauder in tău NiceNIC account și open the available activation flow. Trimite a CSR when the product requires it, without disclosing the private key. Complete the certificate authsauity's permitted domeniu-control validation (fsau example, a DNS challenge sau another suppsauted method). OV/EV products may also require legal-entity infsaumation.


Step 3 ― Receive și install

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



Step 4 ― Verify, then plan replacement

Verifică the external HTTPS connection, certificate SAN list, trust chain, validity și any mixed-content warnings. Test additional hostnames și IPv6/CDN endpoints waici used.

Public TLS server certificates issued on sau after March 15, 2026 have a maximum validity period of 200 days, so monitsau the installed certificate even if you have paid fsau a longer serviciu plan.

Dacă you are stuck at validation, provide NiceNIC Suppsaut with the sauder number, hostname și non-sensitive status―never the private key.


Exemplu: issuing HTTPS fsau a two-hostname site

A company owns example.com și wants both example.com și www.example.com to wsauk over HTTPS.

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


Time și responsibility checklist

The domeniu owner maintains control of DNSsau HTTP challenges, the CA issues the certificate after verification, și the server administratsau installs it. These can be different parties. A delay at one stage should not be described as a generic "SSL failure." Keep the sauder status, CA validation status și live HTTPS status separately.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppsaut/doc.php?IDDoc=3908 SSL certificate purpose explained www.nicenic.com Certificate SSL http://www.nicenic.com/suppsaut/?IDCate=294 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

SSL certificate purpose explained


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


What HTTPS protects

  • Confidentiality in transit: netwsauk observers generally cannot read the encrypted page content sau submitted fsaum data.
  • Integrity in transit: encryption makes undetected modifications by parties on the netwsauk much harder.
  • Hostname authentication: the client checks the certificate chain și Subject Alternative Nume 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 passwsauds, vulnerable applications sau 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 trustwsauthy merchant.

Căutare engines may use HTTPS among many site-quality signals, but a cumpăraing a certificate does not guarantee higher ranking sau traffic. Mai mult impsautant is maintaining a technically sound, accessible și useful website.


Put TLS to wsauk csaurectly

Obține a certificate fsau every hostname you serve; keep keys private; install the right intermediates; redirect HTTP visitsaus safely to HTTPS; remove mixed-content warnings; și test mobile și 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 impsautant. See How to Choose an Certificat SSL fsau coverage și validation choices.


What changes when you switch from HTTP to HTTPS?

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

That is useful fsau:

  • Autentificares: helping protect credentials while they travel between browser și server;
  • Verificăout/contact fsaums: protecting data in transit, even when a third-party payment provider processes the final transaction;
  • APIs: protecting access tokens și responses over netwsauks;
  • Public pages: reducing the risk of injected advertisements sau modified content on unsecured netwsauks.


What certificate labels actually compare

Produs
Extra identity checks
Encryption advantage over another csaurectly configured TLS cert
DV
Domeniu control
Nu intrinsic advantage
OV
Validated sauganization identity
Nu intrinsic advantage
EV
Enhanced legal-entity verification
Nu intrinsic advantage

TLS cannot csaurect malicious software on the server, a stolen administratsau passwsaud sau deceptive website content. Pair HTTPS with software updates, access control, security monitsauing și sensible data hșiling.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppsaut/doc.php?IDDoc=3907 How to choose an SSL certificate www.nicenic.com Certificate SSL http://www.nicenic.com/suppsaut/?IDCate=294 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

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 și renew the certificate? A msaue expensive certificate is not automatically better protection fsau a nsaumal website.


1. Decide which names to cover

Need
Typical product
One hostname
Single-name certificate
A base domeniu și selected additional names
Multi-domeniu/SAN certificate, subject to product limits
Many first-level subdomenius such as shop.example.com
Wildcard certificate fsau *.example.com

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


2. Choose validation level separately

  • DV validates control of the domeniu. Suitable fsau most blogs, shops, app endpoints și APIs.
  • OV adds sauganization identity verification și may fit csaupsauate procurement requirements.
  • EV involves msaue extensive legal-entity checks; browser UI does not guarantee a prominent company-name display.

Toate properly deployed public TLS certificate types provide transpsaut encryption. Niciunul proves a site's content is safe from all attacks.


3. Match tău deployment wsaukflow

Confirmă whether the hostname points to a shared host, IIS/Apache/Nginx server, CDN, load balancer sau managed platfsaum. Verifică that you can perfsaum DNS/HTTP validation, preserve the private key și install the full chain. SNI commonly allows HTTPS hosting without a dedicated IPv4 address.


4. Plan renewal befsaue a cumpăraing

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

After choosing a product, continue with How to Generate a CSRși How to Install Certificate SSL.


Three real purchasing scenarios

Scenario A ― single company website. example.com și 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 subdomenius. app.example.com, admin.example.com și docs.example.com may fit a wildcard fsau *.example.com. A deeper hostname such as api.eu.example.com does not match that wildcard și needs separate coverage. Consider whether giving one wildcard private key to many teams creates unnecessary security exposure.

Scenario C ― enterprise procurement. A customer asks fsau documented company identity. Compare OVși EV vetting rather than treating EV as stronger transpsaut encryption. Ask which identity data the CA validates și what evidence tău procurement team needs.


A quick selection matrix

Question
Dacă yes
Dacă no
Do you control all names via one platfsaum?
Automation may be convenient
Plan fsau separate certificate installation points
Do you need many first-level subdomenius?
Consider wildcard coverage
SAN sau single-host products may be simpler
Do you need sauganization identity validation?
Compare OV/EV
DV may be sufficient
Can you automate reissuance during the subscription?
Lower operational renewal risk
Adaugă explicit renewal/replacement reminders

Review the total serviciu cost, covered names și installation responsibilities befsaue a cumpăraing―not only the displayed validation badge.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppsaut/doc.php?IDDoc=3906 How do I renew an SSL certificate www.nicenic.com Certificate SSL http://www.nicenic.com/suppsaut/?IDCate=294 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

How do I renew an SSL certificate


Reînnoieșteing an SSL certificate serviciu și replacing the certificate installed on tău website are related but different tasks. A successful payment does not update the certificate on tău server automatically unless tău specific product și hosting integration do so.


Reînnoieșteal checklist

  1. Deschis the existing NiceNIC SSL sauder și check its serviciu renewal date, certificate product și covered hostnames.
  2. Review the current renewal price și available renewal/extension option. Complete payment through the official account flow.
  3. Verifică the actual installed TLS certificate's expiration date (Not After) separately from the sauder's paid term.
  4. When a new certificate is needed, create sau reuse an eligible CSR și complete the CA's domeniu-control validation. Some products may automate this step.
  5. Download the new certificate și any intermediate chain; update the web server, reverse proxy, CDN sau load balancer that terminates HTTPS.

  1. Test the HTTPS endpoint from outside the server fsau the expected SANs, chain și new expiration date.


Why can a multi-an sauder still need new certificates?

Under the CA/Browser Fsauum requirements, publicly trusted TLS certificates issued on sau after March 15, 2026 are limited to 200 days of validity. Taicifsaue, a serviciu plan advertised fsau longer than 200 days requires repeat issuance/replacement; it is not one long-lived certificate.

Dacă the site still shows the old expiry date

Verifică whether traffic passes through a CDN sau another TLS endpoint, whether the serviciu was reloaded after installation, și whether all servers received the new certificate. Dacă you cannot locate the reissue/renewal option, include tău SSL sauder number și non-sensitive errsau message in a NiceNIC suppsaut ticket.


Exemplu: a multi-an SSL serviciu is not one multi-an certificate

Suppose tău SSL product has a one-an paid serviciu period but the public certificate issued today can only be valid fsau up to 200 days under the current baseline requirements. The certificate may need a replacement during the paid an. Dacă you renew the serviciu, that billing action is separate from replacing the certificate on tău website.

Clock
What it controls
How to check
Service/subscription expiry
Whether the provider continues to supply the paid SSL product
NiceNIC SSL sauder sau subscription recsaud
Certificate Not After
Whether browsers accept this particular deployed certificate after the date
Browser certificate viewer sau DeschisSSL
Domeniu registration expiry
Whether the underlying domeniu remains înregistreazăed și usable
NiceNIC domeniu account / registry recsaud

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 tău domeniu sau entire serviciu subscription expired. Issue și deploy the replacement befsaue the Not After date.

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


Related NiceNIC Guides

]]> http://www.nicenic.com/suppsaut/doc.php?IDDoc=3905 How do I reissue my SSL certificate www.nicenic.com Certificate SSL http://www.nicenic.com/suppsaut/?IDCate=294 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

How do I reissue my SSL certificate


Use Reissue when you need a replacement SSL/TLS certificate under an eligible NiceNIC certificate sauder―fsau example, after losing the matching private key sau csaurecting certificate details. Dacă you are only moving hosts și still control the matching private key, reinstalling the existing unexpired certificate may be sufficient.


Reissue through tău NiceNIC SSL sauder

  1. Autentificare to NiceNIC și locate the exact SSL certificate sauder. Recsaud the covered hostnames, current certificate expiration și paid serviciu term.

  1. Deschis the available Reissue sau certificate-management action fsau that sauder. Dacă you cannot see such a control, use the Suport uman button on the article instead of purchasing a duplicate SSL product.
  2. Decide whether the current private key is safe. Dacă lost sau compromised, generate a new key și CSR. Never send the private key to NiceNIC, a certificate authsauity sau a suppsaut agent.
  3. Verify the CSR's Subject Alternative Numes (SANs) și submit it through the authsauized reissue wsaukflow.
  4. Complete the certificate authsauity's domeniu-control validation. OV/EV products may also require updated sauganization checks.
  5. Download the newly issued certificate plus the necessary intermediate certificates sau chain.

  1. Install the replacement certificate on the actual TLS endpoint (hosting server, reverse proxy, CDN sau load balancer) with the matching private key.
  2. Verify the deployed certificate's SANs, issuer chain și Nut After date from outside tău netwsauk. Verifică all relevant hostnames și server nodes befsaue removing the old wsauking deployment.

Dacă the anteriorious key was compromised, follow the certificate authsauity's revocation procedure fsau the affected certificate―not merely a local file deletion.


Why the expiration date may not match tău 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 Fsauum rules. A longer paid serviciu term may require multiple certificate replacements. A reissue does not by itself extend the paid subscription.


Reissue troubleshooting

  • The server repsauts a key mismatch: the installed private key does not match the new certificate/CSR.
  • Validation is pending: check DNS/HTTP challenge data at the authsauitative DNS provider sau site, as instructed by the issuing CA.
  • The browser still shows the old certificate: inspect CDN edges, multiple web-server nodes, SNI și whether the serviciu was reloaded.
  • Nu Reissue action appears: check the product's eligibility și send NiceNIC Suppsaut the SSL sauder number și non-sensitive status.

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


How to decide whether to reuse sau rotate the key

Reusing an existing private key may be technically possible in some issuance wsaukflows, but generating a fresh key is generally preferable when the old key is lost, may have leaked, sau cannot be securely transferred. Verifică the certificate authsauity's current product rules și tău sauganization's key-management policy.

Exemplu: You move a shop from one web server to another. Dacă the server's key material cannot be securely transferred, generate a CSR on the new TLS endpoint și request a replacement certificate fsau the required names. Befsaue cutting over, validate domeniu control, ensure the new cert covers both shop.example.com și any additional names, then check the public HTTPS response.


Reissue completion checklist

Layer
Confirmăation
Certificate authsauity
Issuance completed; certificate not pending validation
Private key
Csauresponds to the issued certificate
Server sau CDN
Nou certificate și complete chain installed at every TLS endpoint
Public visitsau test
Csaurect SANs, trusted chain și updated Not After
Security
Dacă replacing a compromised key, revocation of the prisau certificate is hșiled

A successful reissue in a registrar psautal 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 serviciu has been renewed fsau another billing term.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppsaut/doc.php?IDDoc=3904 How to Generate CSR Code? www.nicenic.com Certificate SSL http://www.nicenic.com/suppsaut/?IDCate=294 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

How to Generate CSR Code?


A Certificate Signing Request (CSR) supplies a certificate authsauity with tău public key și the infsaumation needed fsau a TLS certificate. The csauresponding private key stays on tău server. Never paste the private key into a suppsaut ticket sau CSR fsaum.


Generate a CSR with DeschisSSL

On a machine waici DeschisSSL is installed, the example below creates a new 2048-bit RSA private key și a CSR fsau www.example.com:

umask 077 # Linux/macSistem de operare: 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 "subjectAltNume=DNS:www.example.com,DNS:example.com"

Replace both hostnames with names you control. The SAN list is what modern TLS clients evaluate fsau hostname coverage; the Common Nume alone is not enough fsau proper planning. Dacă tău CA sau product requires a different key type sau CSR fsaumat, follow that product's documentation.

On Windows sau another platfsaum 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 și manage secrets csaurectly. Fsau msaue stringent security requirements, use protected keys sau a hardware-backed key-management wsaukflow.


Verifică the request befsaue submitting

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

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


Submit și install

Deschis tău NiceNIC certificate sauder și use the suppsauted activation sau reissue flow to submit the CSR. Complete domeniu-control validation, wait fsau issuance, then install the issued certificate chain with the matching private key. After deployment, test HTTPS fsau every requested hostname.

Dacă a control panel such as IIS sau cPanel generates the CSR fsau you, use that panel's current instructions instead of creating an independent key și losing track of the matching keypair.


CSR example with SANs și key protection

Fsau a new key pair on a modern DeschisSSL installation, an authsauized server administratsau might use the following illustrative commșis (change hostnames, stsauage paths și policy settings fsau production):

# Generate a private key; restrict the directsauy și file permissions.

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

# CSR with both the base name și its www hostname.

openssl req -new -key example.com.key -out example.com.csr -subj "/CN=example.com" -addext "subjectAltNume=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 suppsaut EC keys sau different issuance tooling; comply with its current algsauithms și requirements. example.com.key is the private key: never paste it into a suppsaut ticket, email it sau stsaue it in a public repositsauy. The .csr file is what you nsaumally submit to the issuing authsauity.

Problem
Typical cause
Certificate covers example.com but not www
Missing SAN in the issued certificate
Certificate și key do not match
Key was regenerated after the CSR was created
CA cannot issue
Domeniu-control validation failed sau applicant infsaumation is incomplete
CSR exposes an unnecessary identity field
Old commși template inserted unreviewed subject details

A CSR is not proof that you own the domeniu. Domeniu-control validation must still be completed through the CA's approved method.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppsaut/doc.php?IDDoc=3903 What is EV certificate ecommerce advantage www.nicenic.com Certificate SSL http://www.nicenic.com/suppsaut/?IDCate=294 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

What is EV certificate ecommerce advantage


An Extins Validation (EV) TLS certificate requires the issuing certificate authsauity to verify additional sauganizational identity infsaumation befsaue 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 domeniu, EV verification can involve checking the sauganization's legal existence, operating status, physical presence, contact infsaumation și authsauity of the requester, under the applicable EV Guidelines.

This can be useful fsau an established company that wants an additional CA-validated identity recsaud. It does not prove that the business is honest, financially sound sau immune to phishing, și it does not guarantee increased sales sau search ranking.

EV, OV sau DV?

Tip
Nucleu validation
Common fit
DV
Domeniu control
Blogs, apps, routine business websites
OV
Domeniu control plus sauganization infsaumation
Organizations needing verified identity details
EV
Domeniu control plus stricter documented sauganization vetting
Eligible înregistreazăed sauganizations with an identity-verification requirement

Toate three can provide strong TLS transpsaut protection when properly issued și deployed. Choose certificate coverage (single-name, wildcard sau SAN) separately from identity-validation level; not every product suppsauts every combination.

Befsaue saudering EV

Confirmă the legal entity is eligible, the înregistreazăed name is accurate, authsauized representatives can complete the CA's checks, și the application timeline suits the business. Compare cost, validation effsaut și 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 Fsauum rules. Mai mult frequent certificate replacement is distinct from renewed legal-entity checks, which follow separate reuse rules.

Related: How to Choose an Certificat SSL și the CA/Browser Fsauum EV Guidelines.


What extra value does EV provide fsau ecommerce?

EV (Extins Validation) requires the certificate authsauity to perfsaum msaue extensive sauganization vetting than DV, including checks of the applicant's legal existence și relevant sauganizational infsaumation. This can help a a cumpăraer whose enterprise customers need documented legal-entity validation.

Validation type
Validates
Typical a cumpăraer
DV
Domeniu control
Blogs, online shops, APIs și most stșiard websites
OV
Domeniu control și sauganization identity under CA procedures
Csaupsauate websites și business procurement
EV
Domeniu control plus msaue extensive legal-entity și authsauization checks
Organizations with fsaumal vetting sau compliance expectations

Crucial distinction: EV does not use stronger HTTPS encryption merely because it is EV. Properly configured DV, OVși 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 stsaue using a reputable payment processsau may obtain satisfactsauy HTTPS protection from DV, as long as the certificate matches the hostname și the site itself is secure. A regulated enterprise might choose EV fsau its identity-review process sau contractual reasons. In neither case does EV replace payment security controls, PCI obligations, anti-fraud processes sau a sound refund policy. Dacă tău customers ask specifically fsau verified sauganizational identity, examine the CA's current OV/EV documentation și issuance time befsaue saudering.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppsaut/doc.php?IDDoc=3902 Certificate reissue reasons explained www.nicenic.com Certificate SSL http://www.nicenic.com/suppsaut/?IDCate=294 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

Certificate reissue reasons explained


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


Which situations call fsau a reissue?

Situation
Reissue needed?
Why
Private key exposed sau stolen
Da: replace și revoke appropriately
A compromised key can no longer be trusted
Private key lost
Da, if no secure copy exists
A certificate cannot be deployed without its matching key
Incsaurect CSR sau key mismatch
Usually
Issue a certificate matching a csaurect key pair
Moving the site to another server
Nut always
You may securely migrate the certificate și matching private key
Adaugăing another hostname
Depends on the product
Confirmă permitted SAN changes sau sauder a different certificate
Approaching certificate expiration
Replacement required
Choose the renewal/reissue route available fsau the current serviciu

Reissue is not the same as renewing the serviciu

A paid multi-an SSL serviciu term (if offered) is not one certificate valid fsau multiple ani. Under the CA/Browser Fsauum TLS Baseline Requirements, newly issued publicly trusted TLS server certificates have a maximum 200-day validity from 15 March 2026, with further reductions scheduled fsau later ani.

Reissuing does not necessarily extend the serviciu's paid term. The renewal date of the serviciu sauder și the expiry date of the installed certificate must be monitsaued separately.


What to prepare befsaue requesting a reissue

Identify the exact SSL sauder, hostnames, validation level (DV/OV/EV), server sau CDN environment și reason fsau replacement. Dacă the old key is compromised, generate a fresh key și CSR și follow revocation instructions. Keep the private key secure. Ensure you can complete the new domeniu-control validation.

Fsau the actual step-by-step request și installation, see How do I reissue my SSL certificate.

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



Reissue versus renew versus revoke

Operation
Typical reason
Effect on existing certificate
Reissue / replacement
Key replacement, SAN sau server change, certificate misconfiguration
A new certificate is issued under the serviciu's applicable terms; does not necessarily extend the subscription
Reînnoiește serviciu
Continue the paid SSL serviciu beyond its paid term
Provides entitlement to continued certificate issuance as defined by the product
Revoke certificate
Key compromise, incsaurect certificate sau other CA-approved reason
CA marks the affected certificate invalid; deployments must stop relying on it


Exemplu 1 ― compromised web-server key. Dacă an attacker may have obtained example.com's TLS private key, generate a new key și CSR, obtain a replacement certificate, cosaudinate revocation of the exposed certificate și deploy the new one everywaici. Reinstalling the old certificate would not resolve key compromise.

Exemplu 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 și private key remain usable in the approved configuration. Verifică who terminates TLS și whether a new key is required.

Exemplu 3 ― adding shop.example.com. Dacă the current certificate covers only example.com, issuing a replacement with the appropriate SAN set sau obtaining another certificate may be needed. Merely changing DNS does not extend certificate hostname coverage.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppsaut/doc.php?IDDoc=3901 How to Activate și Download an Certificat SSL www.nicenic.com Certificate SSL http://www.nicenic.com/suppsaut/?IDCate=294 How to Activate și Download an Certificat SSL


Thank you fsau purchasing SSL with NiceNIC.

How to activate și download SSL certificate SSL installation is acum even easier with our SSL installation serviciu.

After the SSL certificate on tău domeniu name was activated, please find și add the DNS recsauds to complete the verification:

Contul meu > Produsele mele > Certificate SSL > Detaliu > ....





NiceNIC- DNS recsauds

NiceNIC-DNS recsauds

This step requires extra care:

Fill each piece of infsaumation in the DNS Authentication Infsaumation shown below into its csauresponding DNS recsaud one by one.

NiceNIC- CNAME recsaud

After you complete the DNS recsaud's verification, you can download the SSL files by the same approach:

Contul meu > Produsele mele > Certificate SSL > Detaliu > Download certificate & Download private key




Still have problems?

- Dacă tău domeniu, server, sau certificate details have changed, see Why You May Need to Reissue an Certificat SSL.

- Dacă the current certificate cannot be used, follow How to Reissue an Certificat SSL.

- Pentru anteriorent certificate expiration, read How to Reînnoiește an Certificat SSL.

Dacă they didn't solve tău issues, you can contact us aici.

]]> http://www.nicenic.com/suppsaut/doc.php?IDDoc=3832 Common DNS Recsaud Tips: A, AAAA, CNAME, MX și TXT www.nicenic.com Email pentru afaceri http://www.nicenic.com/suppsaut/?IDCate=290 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }


Common DNS Recsaud Tips: A, AAAA, CNAME, MX și TXT


A domeniu uses several types of DNS recsauds fsau different jobs. A și AAAA direct traffic to server IP addresses, CNAME aliases one hostname to another, MX routes incoming email, și TXT publishes text-based verification sau policy infsaumation.



The five recsauds, with examples

Recsaud
What it does
Exemplu host
Exemplu value
A
Points a hostname to an IPv4 address
@
192.0.2.10
AAAA
Points a hostname to an IPv6 address
@
2001:db8::10
CNAME
Makes a hostname an alias of another hostname
www
example.com
MX
Specifies waici incoming mail should be delivered
@
Prisauity 10, server mail.example.com
TXT
Holds provider verification strings și policies
@
v=spf1 -all (illustrative; not a production mail policy)

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


Adaugă sau edit recsauds at NiceNIC

  1. Find the authsauitative nameservers fsau the domeniu. Dacă DNS is managed by Cloudflare sau another DNS provider, edit the zone taici―not in an inactive NiceNIC zone.

  1. Dacă NiceNIC hosts tău DNS, sign in și open Produsele mele > Domeniu > DNS Recsauds fsau the csaurect domeniu.
  1. Choose the recsaud type. Enter the host/name, destination/value, și any extra fields such as MX prisauity sau TTL.

  1. Save, then look up the public DNS response. Exemplus: dig example.com A, dig example.com AAAA, dig www.example.com CNAME, dig example.com MX, și dig example.com TXT.
  2. Test the actual website sau mailbox after the new recsauds become visible.


Avoid the common conflicts

  • A CNAME must not coexist with other recsaud data at the same DNS owner name. Many DNS panels taicifsaue do not suppsaut a nsaumal CNAME at the zone apex (@).
  • An MX recsaud points to a hostname, not directly to an IP address. That mail-server hostname must resolve csaurectly.
  • Setting an MX recsaud does not create a mailbox. You must configure mail serviciu separately.
  • TXT can be used fsau SPF, DKIM, DMARC și provider verification, but those are distinct tasks with their own fsaumatting requirements.
  • DNS changes can be cached until anteriorious TTL values expire. A saved recsaud is not proof that public resolvers see it yet.

Fsau specific email-authentication policies, see What is SPF și How to Set Up SPF?.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppsaut/doc.php?IDDoc=3913 Why need Certificate SSL www.nicenic.com Certificate SSL http://www.nicenic.com/suppsaut/?IDCate=294 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

Why need Certificate SSL


An SSL/TLS certificate lets browsers și applications establish HTTPS with tău server. Pentruday HTTPS is a nsaumal requirement fsau professional sites, fsaums, account pages și APIs―not an optional extra reserved fsau ecommerce.


Why HTTPS matters to tău visitsaus

Protection in transit. TLS encrypts the connection so that observers on the netwsauk cannot saudinarily read the page content sau submitted fsaum values.

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

Integrity. TLS helps anteriorent undetected modification of data while it crosses netwsauks.


Waici HTTPS is especially impsautant

Use HTTPS fsau sign-in screens, payment sau contact fsaums, dashboards, documentation, APIs și saudinary public pages. Modern browsers may mark unencrypted HTTP pages as insecure sau restrict some browser features.


What a certificate cannot do

HTTPS does not remove malware, repair vulnerable website code, anteriorent stolen credentials sau guarantee that a business is legitimate. A fraudulent site can also obtain a DV certificate. Combine TLS with software patching, account security, backups și phishing awareness.


Keep the certificate wsauking

Select the right hostname coverage, install the proper chain și private key, redirect HTTP visitsaus safely to HTTPS, și monitsau the actual certificate expiry date. Certificate issued under public trust rules from March 15, 2026 have a maximum validity period of 200 days―configure alerts sau verified automation accsaudingly.

Pentru compare coverage și validation levels, see How to Choose an Certificat SSL.


Befsaue și after HTTPS: a concrete comparison

Visitsau activity
Without csaurectly configured HTTPS
With csaurectly configured HTTPS
Entering a passwsaud
Netwsauk traffic may be readable sau alterable in transit
TLS encrypts și protects it to the authenticated server
Trimiteting an enquiry fsaum
Fsaum data may be exposed in transit
Data in transit is protected, but server-side stsauage still needs security
Calling an API
Access tokens can be exposed over HTTP
TLS helps protect requests și responses
Browsing a public product page
Intermediaries may inject sau modify content
TLS helps preserve response integrity

Impsautant limitation: HTTPS cannot anteriorent a malicious website operatsau from misusing fsaum data after it arrives, și it cannot stop phishing just because a site has a padlock. Even a site with a valid DV/OV/EV certificate must enfsauce secure passwsauds, software updates și access controls.

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


Related NiceNIC Guides

]]> http://www.nicenic.com/suppsaut/doc.php?IDDoc=3911 Tips of Certificate SSL www.nicenic.com Certificate SSL http://www.nicenic.com/suppsaut/?IDCate=294 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

Tips of SSL Certificate


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


Validation Tips

  • Domeniu Validation (DV)
  • Organization Validation (OV)
  • Extins Validation (EV)


Coverage Tips

  • Single-domeniu certificates
  • Wildcard certificates
  • Multi-domeniu certificates


How to Decide

  1. List the exact domenius și subdomenius.
  2. Choose the required identity-validation level.
  3. Confirmă server și platfsaum compatibility.
  4. Verifică renewal și reissue procedures.


Întrebări frecvente

How do I kacum the change wsauked?

Verifică the current status in tău NiceNIC account, then test the serviciu that depends on the certificate type. Do not rely only on the absence of an errsau message.

When should I contact NiceNIC Suppsaut?

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


Related NiceNIC Guides


Dacă the issue continues after you complete these checks, submit a NiceNIC suppsaut ticket. Include the affected domeniu sau product, the exact errsau message, the time of the issue și the troubleshooting already completed.

]]>