耐思尼克客户支持中心 http://www.nicenic.com/suppot cn 耐思尼克客户支持中心，常用帮助文档 耐思尼克 - 域名 主机 Rete服务 http://www.nicenic.com/images/88x31.gif http://www.nicenic.com 耐思尼克- 域名+主机只要99元 http://www.nicenic.com/suppot/doc.php?IDDoc=4519 HTTPS & SSL Guide fo .boo, .day, .dev, .page, e .rsvp www.nicenic.com Certificati SSL http://www.nicenic.com/suppot/?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 fo .boo, .day, .dev, .page, e .rsvp


Quick Answer

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


Befoe You Begin

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


NiceNIC Instructions

HTTPS & SSL Configuration Guide A ensure the security of tuo website e protect tuo visitos, all dominios under.boo,.day,.dev,.page, e.rsvp must use HTTPS. This guide will help you configure SSL/TLS corectly.

  1. What is HTTPS? HTTPS (Hypertext Transfer Protocol Secure) encrypts data between tuo website e its visitos. It precedenteents eavesdropping e ensures data integrity.

  2. Obtaining an Certificato SSL NICENIC provides trusted SSL certificates. You can learn moe e acquistare/configure a certificate qui: https://nicenic.com/ssl-certificates/

  3. Installing the Certificato SSL Segui tuo 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. Enfoce HTTPS Once tuo certificate is installed: Redirect all HTTP traffic to HTTPS. Update internal links e resources to use HTTPS. Verify that tuo website is fully accessible via HTTPS.

  5. Keep Certificati Aggiornato SSL certificates have expiration dates. Ensure certificates are renewed befoe they expire e check tuo website regularly to maintain uninterrupted secure connections.


How to Verify

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


Troubleshooting

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


Domande Frequenti

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

Invia a ticket when validation remains pending after the published recods are visible, o when the NiceNIC oder does not provide the expected certificate files.


Related NiceNIC Guides


Se the issue continues after you complete the checks above, submit a NiceNIC suppot ticket with the affected dominio o product, the exact erro message, the time of the issue e the troubleshooting already completed.

]]> http://www.nicenic.com/suppot/doc.php?IDDoc=4374 How to Set Up e Troubleshoot DNSSEC fo Your Dominio www.nicenic.com DNS & Nomeservers http://www.nicenic.com/suppot/?IDCate=408 How to Set Up e Troubleshoot DNSSEC fo Your Dominio?

DNSSEC helps protect tuo dominio’s DNS recods 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 corect source.

A NiceNIC, DNSSEC usually involves two sides:
Your DNS provider o nameserver provider generates the DNSSEC recods.
NiceNIC, as tuo dominio registrar, helps submit the DS recods to the registry when the TLD suppots DNSSEC.

Se DNSSEC is not configured corectly, tuo dominio may show DNSSEC erros, o in moe serious cases, some users may not be able to access tuo website.

What Is DNSSEC?
DNSSEC stes fo Nome di dominio System Security Extensions.
In simple terms, DNSSEC helps verify that the DNS answer fo tuo dominio has not been changed o foged during the lookup process.
Fo example, when someone visits tuo website, DNS is used to find the corect server IP address. DNSSEC helps make sure that the DNS result is authentic e has not been replaced with false data.
DNSSEC does not replace SSL, website security, hosting security, o 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 heles sensitive user infomation.
  3. You run business email, login systems, payment pages, o customer potals.
  4. You want stronger dominio security.
  5. Your DNS provider suppots DNSSEC.
  6. Your dominio extension suppots DNSSEC.
Se you are not familiar with DNS management, we recommend confirming with tuo DNS provider befoe enabling DNSSEC.
Incorect DNSSEC settings may affect dominio resolution.

Impotant DNSSEC Duratas
DNSKEY: A DNSKEY recod is generated by tuo DNS provider. It is used as part of the DNSSEC validation process.
DS Recod: A DS recod connects tuo dominio’s DNSSEC setup with the parent registry zone. In most cases, tuo DNS provider gives you the DS recod, e you need to add it through tuo registrar.
Nomeserver: Your nameservers decide wqui tuo dominio’s DNS recods are managed. Se you change nameservers, tuo DNSSEC recods may also need to be updated.

How to Enable DNSSEC fo Your Dominio
Befoe You Begin: Back Up Your DNS Recods
Befoe enabling DNSSEC, save a copy of tuo current DNS recods, especially impotant A, AAAA, CNAME, MX, TXT, e CAA recods. Enabling DNSSEC does not nomally change these recods, but keeping a backup makes it easier to verify o restoe tuo DNS configuration if you also change nameservers o DNS providers.
Se needed, see: How to Back Up DNS Recods Befoe Changing Dominio Settings.

Step 1: Verifica Whether Your DNS Provider Suppots DNSSEC
Accedi to the platfom wqui tuo DNS is managed.
This may be:
Your dominio registrar, qui is NiceNIC
Your hosting provider
Your DNS provider
Your own DNS server
Another third-party DNS servizio
Make sure DNSSEC is suppoted e enabled tqui.
Impotant: Enable DNSSEC e DNSSEC signing at tuo current DNS provider first. Only add the DS recod at NiceNIC after tuo DNS provider has generated the DNSSEC infomation e is publishing the coresponding DNSKEY. Aggiungiing a DS recod befoe the DNS provider is ready may cause DNSSEC validation to fail.

Step 2: Ottieni the DS Recod from Your DNS Provider
After enabling DNSSEC, tuo DNS provider should provide DNSSEC infomation such as:
Key Tag
Algoithm
Digest Tipo
Digest
DS Recod
Please copy the infomation exactly as provided.
Even one incorect character may cause DNSSEC validation failure.

Step 3: Aggiungi the DS Recod in Your NiceNIC Account
Accedi to tuo NiceNIC account e go to tuo dominio management page.
Then add the DS recod provided by tuo DNS provider.
Se you are not sure wqui to add it, please contact our suppot team e provide the DS recod from tuo DNS provider.

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

Step 5: Verify DNSSEC Stato
After propagation, you may check tuo dominio’s DNSSEC status using a DNSSEC checking tool o by contacting our suppot team.
Se DNSSEC is corectly configured, the DNSSEC validation result should show a valid chain of trust.

When Should You Disable o Rimuovi DNSSEC?
You may need to remove o update DNSSEC recods if:
  • You changed tuo nameservers.
  • You moved DNS management to another provider.
  • Your DNS provider disabled DNSSEC.
  • Your DS recod no longer matches the current DNSKEY.
  • Your website o email has DNS resolution issues after a DNS change.
Impotant: Se you are moving to a new DNS provider o changing authoitative nameservers while DNSSEC is enabled, check fo existing DS recods befoe making the change.
Se the old DS recod will no longer match the new DNS provider, remove the old DS recod first e wait fo its full TTL to expire at the parent zone befoe changing nameservers. Keep DNSSEC signing active at the old DNS provider during this waiting period.
After the new nameservers are active e DNSSEC signing is enabled at the new DNS provider, obtain the new DS recod e add it through NiceNIC.
Changing nameservers while resolvers still have the old DS recod cached may cause DNSSEC validation failures e SERVFAIL responses.

Why Does My Dominio Indietro SERVFAIL After Enabling DNSSEC?
SERVFAIL can occur when DNSSEC validation fails. Common causes include:
  • An old o stale DS recod from a precedenteious DNS provider
  • A DS recod that does not match the DNSKEY published by the current DNS provider
  • Multiple DS recods wqui one o moe no longer match an active DNSSEC key
  • DNSSEC signing is not active o the required DNSKEY/RRSIG recods are not being published corectly
  • Nomeservers were changed befoe the precedenteious DS recod had fully expired from DNS caches
Se tuo dominio resolves without DNSSEC validation but returns SERVFAIL through validating resolvers, this is a strong indication of a DNSSEC configuration problem.
Verifica the current nameservers, all DS recods published fo the dominio, e the DNSKEY infomation from tuo active DNS provider. Rimuovi o replace a DS recod only after confirming that it is outdated o incorect. Se you are unsure, contact tuo DNS provider o NiceNIC Suppot befoe making changes.

Why Does My Dominio Show "DNSSEC Infomation Is Currently Unavailable"?
You may see this message:
DNSSEC infomation is currently unavailable fo this dominio.
This can happen fo several reasons:
  • DNSSEC has not been enabled fo this dominio.
  • No DS recod has been added at the registrar level.
  • The dominio's current nameservers do not suppot DNSSEC.
  • The dominio recently changed nameservers.
  • The DS recod does not match the current DNSKEY.
  • The DNS provider has not published the required DNSSEC recods corectly.
  • The registry o DNSSEC query is tempoarily unavailable.
This message does not always mean tuo dominio is broken.
However, if tuo website o email is not resolving corectly, please contact suppot so we can help review the DNSSEC configuration.

What Infomation Should I Provide to Suppot?
A help us check DNSSEC issues faster, please provide:
  1. Your dominio name
  2. Your current nameservers
  3. Whether you recently changed nameservers
  4. The DS recod provided by tuo DNS provider
  5. A screenshot of the DNSSEC setting from tuo DNS provider
  6. Any DNSSEC erro message you received
  7. Whether tuo website o email is currently affected
With this infomation, our suppot team can check whether the issue is caused by missing DS recods, mismatched DNSSEC recods, nameserver changes, o registry-side limitations.

Domande Frequenti Informazioni DNSSEC

1. Is DNSSEC required fo every dominio?
No. DNSSEC is not required fo every dominio.
However, it is recommended fo dominios that need stronger DNS security, especially business websites, email servizios, login systems, financial servizios, e customer potals.
Se you are not sure whether you need DNSSEC, please confirm whether tuo DNS provider suppots it e whether you are comfotable managing DNSSEC recods.

2. Is DNSSEC the same as SSL?
No.
SSL protects the connection between the user’s browser e tuo website.
DNSSEC protects DNS resolution by helping verify that DNS responses have not been tampered with.
Fo better security, many websites use both SSL e DNSSEC, but they are different technologies.

3. Can NiceNIC generate DNSSEC recods fo me?
In most cases, DNSSEC recods are generated by tuo DNS provider, not by the registrar.
NiceNIC can help submit the DS recod to the registry when the dominio extension suppots DNSSEC.
Se you use a third-party DNS provider, please enable DNSSEC tqui first e then provide us with the DS recod.

4. What should I check after changing nameservers, DNS providers, o transferring my dominio?
Changing nameservers o DNS providers can affect DNSSEC because the existing DS recod may no longer match the DNSKEY published by the new DNS provider.
A registrar transfer by itself does not necessarily mean that tuo DNSSEC configuration must change. Se tuo nameservers e DNS provider remain the same, first check whether the existing DS recod is still present e still matches the current DNSKEY.
Se you also changed nameservers o DNS providers, check fo old DS recods e follow the DNSSEC migration steps above befoe publishing a new DS recod.
Do not assume that DNSSEC was automatically removed during a dominio transfer. Always verify the dominio’s current DS e DNSKEY status.

5. What happens if the DS recod is wrong?
Se the DS recod does not match the DNSKEY published by tuo current DNS provider, DNSSEC validation may fail.
This may cause some DNS resolvers to reject the DNS response.
As a result, tuo website, email, o other servizios may become unreachable fo some users.

6. I do not use DNSSEC. Do I need to do anything?
Se you do not use DNSSEC e tuo dominio has no DS recods, usually no action is needed.
However, if tuo dominio has old DS recods from a precedenteious DNS provider, you should remove them to avoid DNSSEC validation problems.

7. Why does my DNSSEC status still show an erro after I updated the recod?
DNSSEC updates may take time to propagate.
Se you recently added, removed, o changed DS recods, please wait fo DNS propagation e check again later.
Se the issue continues, please contact suppot e provide tuo dominio name, current nameservers, e DS recod.

8. Can DNSSEC cause my website to stop woking?
Sì, if DNSSEC is incorectly configured.
Common causes include:
  • Wrong DS recod
  • Old DS recod after nameserver change
  • Missing DNSKEY
  • DNS provider not publishing DNSSEC recods corectly
  • Scadenzad o invalid DNSSEC signatures
Se tuo website stops woking after DNSSEC changes, please contact suppot immediately.

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

10. What should I do if I see “Failure to get DNSSEC info”?
This usually means the system could not retrieve valid DNSSEC infomation fo the dominio.
Please check:
  • Whether DNSSEC is enabled
  • Whether the DS recod has been added
  • Whether the nameservers suppot DNSSEC
  • Whether the DS recod matches the DNSKEY
  • Whether you recently changed nameservers
Se you are not sure, please contact NiceNIC suppot e provide tuo dominio name e DNSSEC details from tuo DNS provider.

How to set up DNSSEC fo a dominio registrareed on NiceNIC?

1. Accedi to tuo NiceNIC account e navigate to tuo dominio management page. Find the dominio you wish to enable DNSSEC fo e click Gestisci.

 

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

3. Enter the required infomation fo DNSSEC configuration (this will typically include DNSSEC key details provided by tuo DNS hosting provider).
 

4. Once you've entered the infomation, click Aggiungi to enable DNSSEC fo the dominio. Here’s an example of a successful DNSSEC setup:


 DNSSEC

After entering the necessary DNSSEC key data (usually the DS recod), you'll receive confirmation that DNSSEC has been successfully added to tuo dominio settings.
The DNSSEC status will show as enabled e you'll be able to see the public keys e other details.
With DNSSEC ora enabled, tuo dominio is better protected against DNS-related attacks.

Atention: if tuo dominio name was transferred into NiceNIC from another Registrar, e you hope to disable the DNSSEC precedenteiously with the old Registrar, please firstly check the latest whois, if you see "DNSSEC: unsigned", then it means during the dominio transfer process, the DNSSEC settings have been disabled automatically by the old Registrar, while if it is "DNSSEC: signed", please check the dominio management section at tuo 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/suppot/doc.php?IDDoc=3845 What Happens to My Nomeservers After a Trasferimento Dominio? www.nicenic.com Trasferimento Dominios http://www.nicenic.com/suppot/?IDCate=313 Stato of Nome Server After a Trasferimento Dominio


After the dominio is transferred, the name servers remain set to those associated to the dominio befoe transfer.


Se you had child name servers fo tuo dominio registrareed through another Registrar, you may need to registrare them again through tuo Account.

]]> http://www.nicenic.com/suppot/doc.php?IDDoc=3847 How to Transfer Nome Server During a Trasferimento Dominio? www.nicenic.com Trasferimento Dominios http://www.nicenic.com/suppot/?IDCate=313

How to Transfer Nome Server During a Trasferimento Dominio?


Quick Answer

A successful dominio transfer depends on the dominio's eligibility, lock status, authoization method, registrant access e registry rules. Prepare the dominio befoe odering the transfer, keep the existing DNS active, e monito the transfer until completion.


Befoe You Begin

  • Conferma the dominio e registrant email are accessible.
  • Recod the current nameservers e DNS recods.
  • Verifica the dominio's expiry date, lock status e any TLD-specific transfer rule.


NiceNIC Instructions

Transferring nameservers During a Trasferimento Dominio Se you're just transferring the dominio registration, tuo hosting servizio will be unaffected, e tqui 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 recod of them. Se 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 Accedi to tuo account. Select the Nomi a dominio tab. Select the dominio that you want to change nameservers fo.

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


How to Verify

Verifica the transfer status in NiceNIC, confirm the registrar of recod after completion, verify the authoitative nameservers, e test website e email resolution. Do not treat payment alone as proof that the transfer completed.


Troubleshooting

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


Domande Frequenti

Does a transfer change my nameservers?

A registrar transfer nomally keeps the current nameservers, but you should recod e verify them befoe e after the transfer.

Can I edit the dominio while a transfer is pending?

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

When should I submit a ticket?

Invia a ticket when the status is unclear, a TLD uses a special transfer process, o the transfer remains blocked after you corect the stated issue.


Related NiceNIC Guides


Se the issue continues after you complete the checks above, submit a NiceNIC suppot ticket with the affected dominio o product, the exact erro message, the time of the issue e the troubleshooting already completed.

]]> http://www.nicenic.com/suppot/doc.php?IDDoc=3846 How do I verify that my dominio is eligible fo transfer? www.nicenic.com Trasferimento Dominios http://www.nicenic.com/suppot/?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 Verifica Whether a Dominio Is Eligible fo Transfer


Quick Answer

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


Befoe You Begin

  • Conferma the dominio e registrant email are accessible.
  • Recod the current nameservers e DNS recods.
  • Verifica the dominio's expiry date, lock status e any TLD-specific transfer rule.


NiceNIC Instructions

Befoe purchasing the transfer of any gTLD (e.g.,.COM /.NET /.OPPUREG /.BIZ /.INFO etc.) o new gTLD (e.g..CLUB /.CLOUD /.TRADE /.TOP etc.), make sure tuo dominio meets the following conditions:

  1. Your dominio was registrareed o transferred at least 60 days ago;

  2. The dominio is unlocked at the current Registrar (its WHOIS status should be OK o Active). Also,you need to request an up-to-date Auth/EPPcode fo the dominio at tuo current Registrar. Se all criteria are met, you should be able to complete the transfer successfully. Still, some ccTLD (.ES e.UK) have additional transfer requirements e/o exclude some points from the list above.

NOTE: Make sure the dominio status is active, not expired. Se you wish to transfer an expired dominio to NiceNIC, please contact our Suppot Team email suppot@nicenic.net fo further assistance.


How to Verify

Verifica the transfer status in NiceNIC, confirm the registrar of recod after completion, verify the authoitative nameservers, e test website e email resolution. Do not treat payment alone as proof that the transfer completed.


Troubleshooting

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


Domande Frequenti

Does a transfer change my nameservers?

A registrar transfer nomally keeps the current nameservers, but you should recod e verify them befoe e after the transfer.

Can I edit the dominio while a transfer is pending?

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

When should I submit a ticket?

Invia a ticket when the status is unclear, a TLD uses a special transfer process, o the transfer remains blocked after you corect the stated issue.


Related NiceNIC Guides


Se the issue continues after you complete the checks above, submit a NiceNIC suppot ticket with the affected dominio o product, the exact erro message, the time of the issue e the troubleshooting already completed.

]]> http://www.nicenic.com/suppot/doc.php?IDDoc=3842 How to transfer several dominios to NiceNIC in bulk? www.nicenic.com Trasferimento Dominios http://www.nicenic.com/suppot/?IDCate=313 How to transfer several dominios to NiceNIC in bulk?


Befoe submitting a transfer request with NiceNIC, make sure tuo dominios are prepared fo transfer through tuo current registrar. This is generally done by removing transfer locks e getting the necessary Auth codes.


Befoe You Begin

- Conferma the dominio e registrant email are accessible.
- Recod the current nameservers e DNS recods.
- Verifica the dominio's expiry date, lock status e any TLD-specific transfer rule.

Learn how to prepare dominios fo transfer in accounts sections of several popular registrars.

Once those preparations are made, simply follow the steps below to transfer tuo dominios:


Note: Each dominio has a unique Auth code e has to be unlocked fo transfer separately on the current registrar side.


  • Accedi to tuo NiceNIC account.
  • Vai a the Transfer to Us page.
  • Clicca on Bulk options.


bulk transfer

bulk transfer


Enter the dominio names e the Auth codes;


Note: Enter each dominio e its Auth code in a new line. The Auth code has to be separated from the dominio name by a comma e one space.


Clicca on Start Transfer at the bottom of the page.

Double-check the dominio names e add them to Cart. A do this, you can use the Aggiungi all to cart button fo convenience.
Proceed with the payment.

The transfer is completed automatically in 5-7 days fo most dominios. Once the transfer of tuo dominios is completed you will receive the notifications on tuo NiceNIC Primary Indirizzo email, e the dominios will become manageable in tuo Dominio List.


Note: Due to technical reasons, it is only possible to submit the transfer fo up to 500 dominio names at once. Se you need to transfer moe than 10 dominios, you can either submit several Trasferimento in blocco oders o contact our Suppot Team fo assistance.




How to Verifica the Stato of Your Trasferimento Dominio

After initiating a dominio transfer to Nicenic, you can monito its progress directly in tuo account. This helps you kora when the transfer is expected to complete without needing to contact suppot repeatedly.

Steps to View Transfer Stato:

1. Accedi to tuo NiceNIC account. Vai a "My Products > Nomi a dominio".
In the Stato column, you will see tuo dominio listed as:

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


dominio transfer

2. Hover over the infomation icon (i) successivo to "Pending Transfer" to view details about Expected approval/completion date

dominio transfer


Related NiceNIC Guides


Se the issue continues after you complete the checks above, submit a NiceNIC suppot ticket with the affected dominio o product, the exact erro message, the time of the issue e the troubleshooting already completed.

]]> http://www.nicenic.com/suppot/doc.php?IDDoc=3833 What is SPF e How to Set Up SPF? www.nicenic.com Email aziendale http://www.nicenic.com/suppot/?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 e How to Set Up SPF?


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



Befoe you publish SPF

List every legitimate outgoing email servizio used by tuo dominio: a business mailbox, website fom, helpdesk, bulk-email provider o other sender. Obtain the exact SPF instructions from each provider. The DNS zone must be edited wquiver the dominio's authoitative 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 o CIDR range, never by a hostname. The address 192.0.2.10 is reserved fo documentation.

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

Here, a authoizes hosts resolved by the sender dominio's A/AAAA recods, mx authoizes the IPs of the dominio's MX hosts, e include: delegates a check to another SPF recod. Use only mechanisms tuo actual email provider requires. Replace the fictional provider dominio befoe publishing.

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


Set up SPF

  1. Verifica existing TXT recods fo v=spf1 at the hostname you send from.
  2. Combine all approved mail servizios into one SPF policy fo that hostname; do not add a second competing SPF TXT recod.
  3. Se NiceNIC is tuo DNS host, open I Miei Prodotti > Dominio > DNS Recods, edit/create a TXT recod at the specified host, e paste the validated policy.

  1. Save. Verifica the published value using dig TXT example.com o nslookup -type=TXT example.com.

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


When SPF fails

Verifica the sending server's actual public IP, whether the recipient evaluates the intended envelope sender dominio, e whether the SPF recod exceeds the DNS-lookup limit in RFC 7208. Do not use unverified third-party IPs o include: dominios. Se you use NiceNIC Email aziendale, request the current provider-approved SPF value from the email settings o suppot team befoe publishing it.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppot/doc.php?IDDoc=3912 How to verify certificate installation corectly www.nicenic.com Certificati SSL http://www.nicenic.com/suppot/?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 corectly


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


Comme-line check

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

-verify_hostname example.com -verify_return_erro -showcerts

Replace example.com with tuo hostname. Verifica the hostname-verification e certificate-chain result; the -verify_hostname option is impotant because displaying the chain alone does not validate the requested hostname. These flags rely on the local ApriSSL trust stoe. Inspect any missing intermediates. Fo a hostname/path overview, you can also use a reputable external TLS diagnostic servizio, but do not send credentials o customer data.


Common problems

Symptom
Likely area to inspect
Nome mismatch
Missing o incorect SAN / wrong virtual host
Scadenzad certificate
Replacement not deployed everywqui
Untrusted issuer
Missing chain o private CA used unintentionally
Old certificate after update
CDN cache/configuration, SNI o load balancer node
HTTPS page loads with warning
Mixed HTTP assets o insecure embedded content

A certificate "trust badge" is optional marketing UI; it is not required fo successful TLS deployment. Se something fails, give NiceNIC Suppot the hostname, UTC test time, observed certificate dates e non-sensitive erro text―not tuo private key.


Verify every advertised hostname, not just one URL

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

Use the ApriSSL hostname-verification comme shown above o an external TLS test fo 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 e the certificate dates, then test on a second netwok 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 corectly issued, but some clients cannot chain it to a trusted root.
  • Old deployment still active: One CDN edge, IPv6 servizio o load-balancer node still serves an expired certificate while other routes wok.

Fo customer suppot, recod the hostname, resolved IPo CDN endpoint, test time e erro; never attach the private key.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppot/doc.php?IDDoc=3910 SSL Certification in Four Simple Steps www.nicenic.com Certificati SSL http://www.nicenic.com/suppot/?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


Fo a nomal website, activating an SSL certificate involves four distinct tasks: acquistare the right coverage, prove dominio control, receive the certificate, e install/verify it on the server. These steps are not interchangeable.



Step 1 ― Choose coverage e oder

List the hostnames that must use HTTPS, such as example.com e www.example.com. Conferma whether you need single-name, wildcard o SAN coverage; choose DV/OV/EV validation accoding to tuo actual identity requirements. Verifica price e deployment responsibilities befoe odering.


Step 2 ― Activate e validate

Find the SSL oder in tuo NiceNIC account e open the available activation flow. Invia a CSR when the product requires it, without disclosing the private key. Complete the certificate authoity's permitted dominio-control validation (fo example, a DNS challenge o another suppoted method). OV/EV products may also require legal-entity infomation.


Step 3 ― Receive e install

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



Step 4 ― Verify, then plan replacement

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

Public TLS server certificates issued on o after March 15, 2026 have a maximum validity period of 200 days, so monito the installed certificate even if you have paid fo a longer servizio plan.

Se you are stuck at validation, provide NiceNIC Suppot with the oder number, hostname e non-sensitive status―never the private key.


Esempio: issuing HTTPS fo a two-hostname site

A company owns example.com e wants both example.com e www.example.com to wok over HTTPS.

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


Time e responsibility checklist

The dominio owner maintains control of DNSo HTTP challenges, the CA issues the certificate after verification, e the server administrato installs it. These can be different parties. A delay at one stage should not be described as a generic "SSL failure." Keep the oder status, CA validation status e live HTTPS status separately.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppot/doc.php?IDDoc=3908 SSL certificate purpose explained www.nicenic.com Certificati SSL http://www.nicenic.com/suppot/?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 o application to establish HTTPS with a server that controls the certificate's private key e is authoized fo the requested hostname. The purpose is to protect data in transit e authenticate the connection endpoint―not to certify every part of a business.


What HTTPS protects

  • Confidentiality in transit: netwok observers generally cannot read the encrypted page content o submitted fom data.
  • Integrity in transit: encryption makes undetected modifications by parties on the netwok much harder.
  • Hostname authentication: the client checks the certificate chain e Subject Alternative Nome 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 passwods, vulnerable applications o 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 trustwothy merchant.

Cerca engines may use HTTPS among many site-quality signals, but acquistareing a certificate does not guarantee higher ranking o traffic. Altro impotant is maintaining a technically sound, accessible e useful website.


Put TLS to wok corectly

Ottieni a certificate fo every hostname you serve; keep keys private; install the right intermediates; redirect HTTP visitos safely to HTTPS; remove mixed-content warnings; e test mobile e 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 impotant. See How to Choose an Certificato SSL fo coverage e validation choices.


What changes when you switch from HTTP to HTTPS?

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

That is useful fo:

  • Accedis: helping protect credentials while they travel between browser e server;
  • Verificaout/contact foms: protecting data in transit, even when a third-party payment provider processes the final transaction;
  • APIs: protecting access tokens e responses over netwoks;
  • Public pages: reducing the risk of injected advertisements o modified content on unsecured netwoks.


What certificate labels actually compare

Prodotto
Extra identity checks
Encryption advantage over another corectly configured TLS cert
DV
Dominio control
No intrinsic advantage
OV
Validated oganization identity
No intrinsic advantage
EV
Enhanced legal-entity verification
No intrinsic advantage

TLS cannot corect malicious software on the server, a stolen administrato passwod o deceptive website content. Pair HTTPS with software updates, access control, security monitoing e sensible data heling.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppot/doc.php?IDDoc=3907 How to choose an SSL certificate www.nicenic.com Certificati SSL http://www.nicenic.com/suppot/?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 e renew the certificate? A moe expensive certificate is not automatically better protection fo a nomal website.


1. Decide which names to cover

Need
Typical product
One hostname
Single-name certificate
A base dominio e selected additional names
Multi-dominio/SAN certificate, subject to product limits
Many first-level subdominios such as shop.example.com
Wildcard certificate fo *.example.com

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


2. Choose validation level separately

  • DV validates control of the dominio. Suitable fo most blogs, shops, app endpoints e APIs.
  • OV adds oganization identity verification e may fit copoate procurement requirements.
  • EV involves moe extensive legal-entity checks; browser UI does not guarantee a prominent company-name display.

Tutti properly deployed public TLS certificate types provide transpot encryption. Nessuno proves a site's content is safe from all attacks.


3. Match tuo deployment wokflow

Conferma whether the hostname points to a shared host, IIS/Apache/Nginx server, CDN, load balancer o managed platfom. Verifica that you can perfom DNS/HTTP validation, preserve the private key e install the full chain. SNI commonly allows HTTPS hosting without a dedicated IPv4 address.


4. Plan renewal befoe acquistareing

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

After choosing a product, continue with How to Generate a CSRe How to Install Certificati SSL.


Three real purchasing scenarios

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

Scenario C ― enterprise procurement. A customer asks fo documented company identity. Compare OVe EV vetting rather than treating EV as stronger transpot encryption. Ask which identity data the CA validates e what evidence tuo procurement team needs.


A quick selection matrix

Question
Se yes
Se no
Do you control all names via one platfom?
Automation may be convenient
Plan fo separate certificate installation points
Do you need many first-level subdominios?
Consider wildcard coverage
SAN o single-host products may be simpler
Do you need oganization identity validation?
Compare OV/EV
DV may be sufficient
Can you automate reissuance during the subscription?
Lower operational renewal risk
Aggiungi explicit renewal/replacement reminders

Review the total servizio cost, covered names e installation responsibilities befoe acquistareing―not only the displayed validation badge.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppot/doc.php?IDDoc=3906 How do I renew an SSL certificate www.nicenic.com Certificati SSL http://www.nicenic.com/suppot/?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


Rinnovaing an SSL certificate servizio e replacing the certificate installed on tuo website are related but different tasks. A successful payment does not update the certificate on tuo server automatically unless tuo specific product e hosting integration do so.


Rinnovaal checklist

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

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


Why can a multi-anno oder still need new certificates?

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

Se the site still shows the old expiry date

Verifica whether traffic passes through a CDN o another TLS endpoint, whether the servizio was reloaded after installation, e whether all servers received the new certificate. Se you cannot locate the reissue/renewal option, include tuo SSL oder number e non-sensitive erro message in a NiceNIC suppot ticket.


Esempio: a multi-anno SSL servizio is not one multi-anno certificate

Suppose tuo SSL product has a one-anno paid servizio period but the public certificate issued today can only be valid fo up to 200 days under the current baseline requirements. The certificate may need a replacement during the paid anno. Se you renew the servizio, that billing action is separate from replacing the certificate on tuo website.

Clock
What it controls
How to check
Service/subscription expiry
Whether the provider continues to supply the paid SSL product
NiceNIC SSL oder o subscription recod
Certificate Not After
Whether browsers accept this particular deployed certificate after the date
Browser certificate viewer o ApriSSL
Dominio registration expiry
Whether the underlying dominio remains registrareed e usable
NiceNIC dominio account / registry recod

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 tuo dominio o entire servizio subscription expired. Issue e deploy the replacement befoe the Not After date.

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


Related NiceNIC Guides

]]> http://www.nicenic.com/suppot/doc.php?IDDoc=3905 How do I reissue my SSL certificate www.nicenic.com Certificati SSL http://www.nicenic.com/suppot/?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 oder―fo example, after losing the matching private key o corecting certificate details. Se you are only moving hosts e still control the matching private key, reinstalling the existing unexpired certificate may be sufficient.


Reissue through tuo NiceNIC SSL oder

  1. Accedi to NiceNIC e locate the exact SSL certificate oder. Recod the covered hostnames, current certificate expiration e paid servizio term.

  1. Apri the available Reissue o certificate-management action fo that oder. Se you cannot see such a control, use the Supporto Umano button on the article instead of purchasing a duplicate SSL product.
  2. Decide whether the current private key is safe. Se lost o compromised, generate a new key e CSR. Never send the private key to NiceNIC, a certificate authoity o a suppot agent.
  3. Verify the CSR's Subject Alternative Nomes (SANs) e submit it through the authoized reissue wokflow.
  4. Complete the certificate authoity's dominio-control validation. OV/EV products may also require updated oganization checks.
  5. Download the newly issued certificate plus the necessary intermediate certificates o chain.

  1. Install the replacement certificate on the actual TLS endpoint (hosting server, reverse proxy, CDN o load balancer) with the matching private key.
  2. Verify the deployed certificate's SANs, issuer chain e Not After date from outside tuo netwok. Verifica all relevant hostnames e server nodes befoe removing the old woking deployment.

Se the precedenteious key was compromised, follow the certificate authoity's revocation procedure fo the affected certificate―not merely a local file deletion.


Why the expiration date may not match tuo 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 Foum rules. A longer paid servizio term may require multiple certificate replacements. A reissue does not by itself extend the paid subscription.


Reissue troubleshooting

  • The server repots a key mismatch: the installed private key does not match the new certificate/CSR.
  • Validation is pending: check DNS/HTTP challenge data at the authoitative DNS provider o site, as instructed by the issuing CA.
  • The browser still shows the old certificate: inspect CDN edges, multiple web-server nodes, SNI e whether the servizio was reloaded.
  • No Reissue action appears: check the product's eligibility e send NiceNIC Suppot the SSL oder number e non-sensitive status.

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


How to decide whether to reuse o rotate the key

Reusing an existing private key may be technically possible in some issuance wokflows, but generating a fresh key is generally preferable when the old key is lost, may have leaked, o cannot be securely transferred. Verifica the certificate authoity's current product rules e tuo oganization's key-management policy.

Esempio: You move a shop from one web server to another. Se the server's key material cannot be securely transferred, generate a CSR on the new TLS endpoint e request a replacement certificate fo the required names. Befoe cutting over, validate dominio control, ensure the new cert covers both shop.example.com e any additional names, then check the public HTTPS response.


Reissue completion checklist

Layer
Confermaation
Certificate authoity
Issuance completed; certificate not pending validation
Private key
Coresponds to the issued certificate
Server o CDN
Nuovo certificate e complete chain installed at every TLS endpoint
Public visito test
Corect SANs, trusted chain e updated Not After
Security
Se replacing a compromised key, revocation of the prio certificate is heled

A successful reissue in a registrar potal 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 servizio has been renewed fo another billing term.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppot/doc.php?IDDoc=3904 How to Generate CSR Code? www.nicenic.com Certificati SSL http://www.nicenic.com/suppot/?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 authoity with tuo public key e the infomation needed fo a TLS certificate. The coresponding private key stays on tuo server. Never paste the private key into a suppot ticket o CSR fom.


Generate a CSR with ApriSSL

On a machine wqui ApriSSL is installed, the example below creates a new 2048-bit RSA private key e a CSR fo www.example.com:

umask 077 # Linux/macSistema Operativo: 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 "subjectAltNome=DNS:www.example.com,DNS:example.com"

Replace both hostnames with names you control. The SAN list is what modern TLS clients evaluate fo hostname coverage; the Common Nome alone is not enough fo proper planning. Se tuo CA o product requires a different key type o CSR fomat, follow that product's documentation.

On Windows o another platfom 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 e manage secrets corectly. Fo moe stringent security requirements, use protected keys o a hardware-backed key-management wokflow.


Verifica the request befoe submitting

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

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


Submit e install

Apri tuo NiceNIC certificate oder e use the suppoted activation o reissue flow to submit the CSR. Complete dominio-control validation, wait fo issuance, then install the issued certificate chain with the matching private key. After deployment, test HTTPS fo every requested hostname.

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


CSR example with SANs e key protection

Fo a new key pair on a modern ApriSSL installation, an authoized server administrato might use the following illustrative commes (change hostnames, stoage paths e policy settings fo production):

# Generate a private key; restrict the directoy e file permissions.

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

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

openssl req -new -key example.com.key -out example.com.csr -subj "/CN=example.com" -addext "subjectAltNome=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 suppot EC keys o different issuance tooling; comply with its current algoithms e requirements. example.com.key is the private key: never paste it into a suppot ticket, email it o stoe it in a public repositoy. The .csr file is what you nomally submit to the issuing authoity.

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

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


Related NiceNIC Guides

]]> http://www.nicenic.com/suppot/doc.php?IDDoc=3903 What is EV certificate ecommerce advantage www.nicenic.com Certificati SSL http://www.nicenic.com/suppot/?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 Esteso Validation (EV) TLS certificate requires the issuing certificate authoity to verify additional oganizational identity infomation befoe 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 dominio, EV verification can involve checking the oganization's legal existence, operating status, physical presence, contact infomation e authoity of the requester, under the applicable EV Guidelines.

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

EV, OV o DV?

Tipo
Core validation
Common fit
DV
Dominio control
Blogs, apps, routine business websites
OV
Dominio control plus oganization infomation
Organizations needing verified identity details
EV
Dominio control plus stricter documented oganization vetting
Eligible registrareed oganizations with an identity-verification requirement

Tutti three can provide strong TLS transpot protection when properly issued e deployed. Choose certificate coverage (single-name, wildcard o SAN) separately from identity-validation level; not every product suppots every combination.

Befoe odering EV

Conferma the legal entity is eligible, the registrareed name is accurate, authoized representatives can complete the CA's checks, e the application timeline suits the business. Compare cost, validation effot e 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 Foum rules. Altro frequent certificate replacement is distinct from renewed legal-entity checks, which follow separate reuse rules.

Related: How to Choose an Certificato SSL e the CA/Browser Foum EV Guidelines.


What extra value does EV provide fo ecommerce?

EV (Esteso Validation) requires the certificate authoity to perfom moe extensive oganization vetting than DV, including checks of the applicant's legal existence e relevant oganizational infomation. This can help a acquistareer whose enterprise customers need documented legal-entity validation.

Validation type
Validates
Typical acquistareer
DV
Dominio control
Blogs, online shops, APIs e most steard websites
OV
Dominio control e oganization identity under CA procedures
Copoate websites e business procurement
EV
Dominio control plus moe extensive legal-entity e authoization checks
Organizations with fomal vetting o compliance expectations

Crucial distinction: EV does not use stronger HTTPS encryption merely because it is EV. Properly configured DV, OVe 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 stoe using a reputable payment processo may obtain satisfactoy HTTPS protection from DV, as long as the certificate matches the hostname e the site itself is secure. A regulated enterprise might choose EV fo its identity-review process o contractual reasons. In neither case does EV replace payment security controls, PCI obligations, anti-fraud processes o a sound refund policy. Se tuo customers ask specifically fo verified oganizational identity, examine the CA's current OV/EV documentation e issuance time befoe odering.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppot/doc.php?IDDoc=3902 Certificate reissue reasons explained www.nicenic.com Certificati SSL http://www.nicenic.com/suppot/?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 servizio oder. You may need one if the private key is lost o compromised, the CSR is wrong, the certificate's covered names must change, o the issued certificate can no longer be deployed corectly.


Which situations call fo a reissue?

Situation
Reissue needed?
Why
Private key exposed o stolen
Sì: replace e revoke appropriately
A compromised key can no longer be trusted
Private key lost
Sì, if no secure copy exists
A certificate cannot be deployed without its matching key
Incorect CSR o key mismatch
Usually
Issue a certificate matching a corect key pair
Moving the site to another server
Not always
You may securely migrate the certificate e matching private key
Aggiungiing another hostname
Depends on the product
Conferma permitted SAN changes o oder a different certificate
Approaching certificate expiration
Replacement required
Choose the renewal/reissue route available fo the current servizio

Reissue is not the same as renewing the servizio

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

Reissuing does not necessarily extend the servizio's paid term. The renewal date of the servizio oder e the expiry date of the installed certificate must be monitoed separately.


What to prepare befoe requesting a reissue

Identify the exact SSL oder, hostnames, validation level (DV/OV/EV), server o CDN environment e reason fo replacement. Se the old key is compromised, generate a fresh key e CSR e follow revocation instructions. Keep the private key secure. Ensure you can complete the new dominio-control validation.

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

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



Reissue versus renew versus revoke

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


Esempio 1 ― compromised web-server key. Se an attacker may have obtained example.com's TLS private key, generate a new key e CSR, obtain a replacement certificate, coodinate revocation of the exposed certificate e deploy the new one everywqui. Reinstalling the old certificate would not resolve key compromise.

Esempio 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 e private key remain usable in the approved configuration. Verifica who terminates TLS e whether a new key is required.

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


Related NiceNIC Guides

]]> http://www.nicenic.com/suppot/doc.php?IDDoc=3901 How to Activate e Download an Certificato SSL www.nicenic.com Certificati SSL http://www.nicenic.com/suppot/?IDCate=294 How to Activate e Download an Certificato SSL


Thank you fo purchasing SSL with NiceNIC.

How to activate e download SSL certificate SSL installation is ora even easier with our SSL installation servizio.

After the SSL certificate on tuo dominio name was activated, please find e add the DNS recods to complete the verification:

Il Mio Account > I Miei Prodotti > Certificati SSL > Dettaglio > ....





NiceNIC- DNS recods

NiceNIC-DNS recods

This step requires extra care:

Fill each piece of infomation in the DNS Authentication Infomation shown below into its coresponding DNS recod one by one.

NiceNIC- CNAME recod

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

Il Mio Account > I Miei Prodotti > Certificati SSL > Dettaglio > Download certificate & Download private key




Still have problems?

- Se tuo dominio, server, o certificate details have changed, see Why You May Need to Reissue an Certificato SSL.

- Se the current certificate cannot be used, follow How to Reissue an Certificato SSL.

- A precedenteent certificate expiration, read How to Rinnova an Certificato SSL.

Se they didn't solve tuo issues, you can contact us qui.

]]> http://www.nicenic.com/suppot/doc.php?IDDoc=3832 Common DNS Recod Tipos: A, AAAA, CNAME, MX e TXT www.nicenic.com Email aziendale http://www.nicenic.com/suppot/?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 Recod Tipos: A, AAAA, CNAME, MX e TXT


A dominio uses several types of DNS recods fo different jobs. A e AAAA direct traffic to server IP addresses, CNAME aliases one hostname to another, MX routes incoming email, e TXT publishes text-based verification o policy infomation.



The five recods, with examples

Recod
What it does
Esempio host
Esempio 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 wqui incoming mail should be delivered
@
Prioity 10, server mail.example.com
TXT
Holds provider verification strings e policies
@
v=spf1 -all (illustrative; not a production mail policy)

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


Aggiungi o edit recods at NiceNIC

  1. Find the authoitative nameservers fo the dominio. Se DNS is managed by Cloudflare o another DNS provider, edit the zone tqui―not in an inactive NiceNIC zone.

  1. Se NiceNIC hosts tuo DNS, sign in e open I Miei Prodotti > Dominio > DNS Recods fo the corect dominio.
  1. Choose the recod type. Enter the host/name, destination/value, e any extra fields such as MX prioity o TTL.

  1. Save, then look up the public DNS response. Esempios: dig example.com A, dig example.com AAAA, dig www.example.com CNAME, dig example.com MX, e dig example.com TXT.
  2. Test the actual website o mailbox after the new recods become visible.


Avoid the common conflicts

  • A CNAME must not coexist with other recod data at the same DNS owner name. Many DNS panels tquifoe do not suppot a nomal CNAME at the zone apex (@).
  • An MX recod points to a hostname, not directly to an IP address. That mail-server hostname must resolve corectly.
  • Setting an MX recod does not create a mailbox. You must configure mail servizio separately.
  • TXT can be used fo SPF, DKIM, DMARC e provider verification, but those are distinct tasks with their own fomatting requirements.
  • DNS changes can be cached until precedenteious TTL values expire. A saved recod is not proof that public resolvers see it yet.

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


Related NiceNIC Guides

]]> http://www.nicenic.com/suppot/doc.php?IDDoc=3913 Why need Certificati SSL www.nicenic.com Certificati SSL http://www.nicenic.com/suppot/?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 Certificati SSL


An SSL/TLS certificate lets browsers e applications establish HTTPS with tuo server. Aday HTTPS is a nomal requirement fo professional sites, foms, account pages e APIs―not an optional extra reserved fo ecommerce.


Why HTTPS matters to tuo visitos

Protection in transit. TLS encrypts the connection so that observers on the netwok cannot odinarily read the page content o submitted fom values.

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

Integrity. TLS helps precedenteent undetected modification of data while it crosses netwoks.


Wqui HTTPS is especially impotant

Use HTTPS fo sign-in screens, payment o contact foms, dashboards, documentation, APIs e odinary public pages. Modern browsers may mark unencrypted HTTP pages as insecure o restrict some browser features.


What a certificate cannot do

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


Keep the certificate woking

Select the right hostname coverage, install the proper chain e private key, redirect HTTP visitos safely to HTTPS, e monito the actual certificate expiry date. Certificati issued under public trust rules from March 15, 2026 have a maximum validity period of 200 days―configure alerts o verified automation accodingly.

A compare coverage e validation levels, see How to Choose an Certificato SSL.


Befoe e after HTTPS: a concrete comparison

Visito activity
Without corectly configured HTTPS
With corectly configured HTTPS
Entering a passwod
Netwok traffic may be readable o alterable in transit
TLS encrypts e protects it to the authenticated server
Inviating an enquiry fom
Fom data may be exposed in transit
Data in transit is protected, but server-side stoage still needs security
Calling an API
Access tokens can be exposed over HTTP
TLS helps protect requests e responses
Browsing a public product page
Intermediaries may inject o modify content
TLS helps preserve response integrity

Impotant limitation: HTTPS cannot precedenteent a malicious website operato from misusing fom data after it arrives, e it cannot stop phishing just because a site has a padlock. Even a site with a valid DV/OV/EV certificate must enfoce secure passwods, software updates e access controls.

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


Related NiceNIC Guides

]]> http://www.nicenic.com/suppot/doc.php?IDDoc=3911 Tipos of Certificati SSL www.nicenic.com Certificati SSL http://www.nicenic.com/suppot/?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; } }

Tipos of SSL Certificati


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


Validation Tipos

  • Dominio Validation (DV)
  • Organization Validation (OV)
  • Esteso Validation (EV)


Coverage Tipos

  • Single-dominio certificates
  • Wildcard certificates
  • Multi-dominio certificates


How to Decide

  1. List the exact dominios e subdominios.
  2. Choose the required identity-validation level.
  3. Conferma server e platfom compatibility.
  4. Verifica renewal e reissue procedures.


Domande Frequenti

How do I kora the change woked?

Verifica the current status in tuo NiceNIC account, then test the servizio that depends on the certificate type. Do not rely only on the absence of an erro message.

When should I contact NiceNIC Suppot?

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


Related NiceNIC Guides


Se the issue continues after you complete these checks, submit a NiceNIC suppot ticket. Include the affected dominio o product, the exact erro message, the time of the issue e the troubleshooting already completed.

]]>