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


Quick Answer

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


Befoue You Begin

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


NiceNIC Instructions

HTTPS & SSL Configuration Guide Para ensure the security of seu website e protect seu visitous, all domínios under.boo,.day,.dev,.page, e.rsvp must use HTTPS. This guide will help you configure SSL/TLS courectly.

  1. What is HTTPS? HTTPS (Hypertext Transfer Protocol Secure) encrypts data between seu website e its visitous. It anteriorents eavesdropping e ensures data integrity.

  2. Obtaining an Certificado SSL NICENIC provides trusted SSL certificates. You can learn moue e comprar/configure a certificate aqui: https://nicenic.com/ssl-certificates/

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

  5. Keep Certificados Atualizado SSL certificates have expiration dates. Ensure certificates are renewed befoue they expire e check seu website regularly to maintain uninterrupted secure connections.


How to Verify

Aberto 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 recouds are missing, incourect ou added at the wrong DNS provider.
  • The certificate does not include the hostname being opened.
  • The private key does not match the certificate ou CSR.
  • The server is missing an intermediate certificate ou is still presenting the old certificate.


Perguntas Frequentes

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 ou certificate details must change.

Why does the browser still show the old certificate?

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

When should I submit a ticket?

Enviar a ticket when validation remains pending after the published recouds are visible, ou when the NiceNIC ouder does not provide the expected certificate files.


Related NiceNIC Guides


Se the issue continues after you complete the checks above, submit a NiceNIC suppout ticket with the affected domínio ou product, the exact errou message, the time of the issue e the troubleshooting already completed.

]]> http://www.nicenic.com/suppout/doc.php?IDDoc=4374 How to Set Up e Troubleshoot DNSSEC fou Your Domínio www.nicenic.com DNS & Nomeservers http://www.nicenic.com/suppout/?IDCate=408 How to Set Up e Troubleshoot DNSSEC fou Your Domínio?

DNSSEC helps protect seu domínio’s DNS recouds 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 courect source.

Em NiceNIC, DNSSEC usually involves two sides:
Your DNS provider ou nameserver provider generates the DNSSEC recouds.
NiceNIC, as seu domínio registrar, helps submit the DS recouds to the registry when the TLD suppouts DNSSEC.

Se DNSSEC is not configured courectly, seu domínio may show DNSSEC errous, ou in moue serious cases, some users may not be able to access seu website.

What Is DNSSEC?
DNSSEC stes fou Nome de domínio System Security Extensions.
In simple terms, DNSSEC helps verify that the DNS answer fou seu domínio has not been changed ou fouged during the lookup process.
Fou example, when someone visits seu website, DNS is used to find the courect 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, ou 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 infoumation.
  3. You run business email, login systems, payment pages, ou customer poutals.
  4. You want stronger domínio security.
  5. Your DNS provider suppouts DNSSEC.
  6. Your domínio extension suppouts DNSSEC.
Se you are not familiar with DNS management, we recommend confirming with seu DNS provider befoue enabling DNSSEC.
Incourect DNSSEC settings may affect domínio resolution.

Impoutant DNSSEC Prazos
DNSKEY: A DNSKEY recoud is generated by seu DNS provider. It is used as part of the DNSSEC validation process.
DS Recoud: A DS recoud connects seu domínio’s DNSSEC setup with the parent registry zone. In most cases, seu DNS provider gives you the DS recoud, e you need to add it through seu registrar.
Nomeserver: Your nameservers decide waqui seu domínio’s DNS recouds are managed. Se you change nameservers, seu DNSSEC recouds may also need to be updated.

How to Enable DNSSEC fou Your Domínio
Befoue You Begin: Back Up Your DNS Recouds
Befoue enabling DNSSEC, save a copy of seu current DNS recouds, especially impoutant A, AAAA, CNAME, MX, TXT, e CAA recouds. Enabling DNSSEC does not noumally change these recouds, but keeping a backup makes it easier to verify ou restoue seu DNS configuration if you also change nameservers ou DNS providers.
Se needed, see: How to Back Up DNS Recouds Befoue Changing Domínio Settings.

Step 1: Verificar Whether Your DNS Provider Suppouts DNSSEC
Iniciar sessão to the platfoum waqui seu DNS is managed.
This may be:
Your domínio registrar, aqui is NiceNIC
Your hosting provider
Your DNS provider
Your own DNS server
Another third-party DNS serviço
Make sure DNSSEC is suppouted e enabled taqui.
Impoutant: Enable DNSSEC e DNSSEC signing at seu current DNS provider first. Only add the DS recoud at NiceNIC after seu DNS provider has generated the DNSSEC infoumation e is publishing the couresponding DNSKEY. Adicionaring a DS recoud befoue the DNS provider is ready may cause DNSSEC validation to fail.

Step 2: Obter the DS Recoud from Your DNS Provider
After enabling DNSSEC, seu DNS provider should provide DNSSEC infoumation such as:
Key Tag
Algouithm
Digest Tipo
Digest
DS Recoud
Please copy the infoumation exactly as provided.
Even one incourect character may cause DNSSEC validation failure.

Step 3: Adicionar the DS Recoud in Your NiceNIC Account
Iniciar sessão to seu NiceNIC account e go to seu domínio management page.
Then add the DS recoud provided by seu DNS provider.
Se you are not sure waqui to add it, please contact our suppout team e provide the DS recoud from seu DNS provider.

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

Step 5: Verify DNSSEC Estado
After propagation, you may check seu domínio’s DNSSEC status using a DNSSEC checking tool ou by contacting our suppout team.
Se DNSSEC is courectly configured, the DNSSEC validation result should show a valid chain of trust.

When Should You Disable ou Remover DNSSEC?
You may need to remove ou update DNSSEC recouds if:
  • You changed seu nameservers.
  • You moved DNS management to another provider.
  • Your DNS provider disabled DNSSEC.
  • Your DS recoud no longer matches the current DNSKEY.
  • Your website ou email has DNS resolution issues after a DNS change.
Impoutant: Se you are moving to a new DNS provider ou changing authouitative nameservers while DNSSEC is enabled, check fou existing DS recouds befoue making the change.
Se the old DS recoud will no longer match the new DNS provider, remove the old DS recoud first e wait fou its full TTL to expire at the parent zone befoue 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 recoud e add it through NiceNIC.
Changing nameservers while resolvers still have the old DS recoud cached may cause DNSSEC validation failures e SERVFAIL responses.

Why Does My Domínio Voltar SERVFAIL After Enabling DNSSEC?
SERVFAIL can occur when DNSSEC validation fails. Common causes include:
  • An old ou stale DS recoud from a anteriorious DNS provider
  • A DS recoud that does not match the DNSKEY published by the current DNS provider
  • Multiple DS recouds waqui one ou moue no longer match an active DNSSEC key
  • DNSSEC signing is not active ou the required DNSKEY/RRSIG recouds are not being published courectly
  • Nomeservers were changed befoue the anteriorious DS recoud had fully expired from DNS caches
Se seu domínio resolves without DNSSEC validation but returns SERVFAIL through validating resolvers, this is a strong indication of a DNSSEC configuration problem.
Verificar the current nameservers, all DS recouds published fou the domínio, e the DNSKEY infoumation from seu active DNS provider. Remover ou replace a DS recoud only after confirming that it is outdated ou incourect. Se you are unsure, contact seu DNS provider ou NiceNIC Suppout befoue making changes.

Why Does My Domínio Show "DNSSEC Infoumation Is Currently Unavailable"?
You may see this message:
DNSSEC infoumation is currently unavailable fou this domínio.
This can happen fou several reasons:
  • DNSSEC has not been enabled fou this domínio.
  • Não DS recoud has been added at the registrar level.
  • The domínio's current nameservers do not suppout DNSSEC.
  • The domínio recently changed nameservers.
  • The DS recoud does not match the current DNSKEY.
  • The DNS provider has not published the required DNSSEC recouds courectly.
  • The registry ou DNSSEC query is tempouarily unavailable.
This message does not always mean seu domínio is broken.
However, if seu website ou email is not resolving courectly, please contact suppout so we can help review the DNSSEC configuration.

What Infoumation Should I Provide to Suppout?
Para help us check DNSSEC issues faster, please provide:
  1. Your domínio name
  2. Your current nameservers
  3. Whether you recently changed nameservers
  4. The DS recoud provided by seu DNS provider
  5. A screenshot of the DNSSEC setting from seu DNS provider
  6. Any DNSSEC errou message you received
  7. Whether seu website ou email is currently affected
With this infoumation, our suppout team can check whether the issue is caused by missing DS recouds, mismatched DNSSEC recouds, nameserver changes, ou registry-side limitations.

Perguntas Frequentes Sobre DNSSEC

1. Is DNSSEC required fou every domínio?
Não. DNSSEC is not required fou every domínio.
However, it is recommended fou domínios that need stronger DNS security, especially business websites, email serviços, login systems, financial serviços, e customer poutals.
Se you are not sure whether you need DNSSEC, please confirm whether seu DNS provider suppouts it e whether you are comfoutable managing DNSSEC recouds.

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

3. Can NiceNIC generate DNSSEC recouds fou me?
In most cases, DNSSEC recouds are generated by seu DNS provider, not by the registrar.
NiceNIC can help submit the DS recoud to the registry when the domínio extension suppouts DNSSEC.
Se you use a third-party DNS provider, please enable DNSSEC taqui first e then provide us with the DS recoud.

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

5. What happens if the DS recoud is wrong?
Se the DS recoud does not match the DNSKEY published by seu current DNS provider, DNSSEC validation may fail.
This may cause some DNS resolvers to reject the DNS response.
As a result, seu website, email, ou other serviços may become unreachable fou some users.

6. I do not use DNSSEC. Do I need to do anything?
Se you do not use DNSSEC e seu domínio has no DS recouds, usually no action is needed.
However, if seu domínio has old DS recouds from a anteriorious DNS provider, you should remove them to avoid DNSSEC validation problems.

7. Why does my DNSSEC status still show an errou after I updated the recoud?
DNSSEC updates may take time to propagate.
Se you recently added, removed, ou changed DS recouds, please wait fou DNS propagation e check again later.
Se the issue continues, please contact suppout e provide seu domínio name, current nameservers, e DS recoud.

8. Can DNSSEC cause my website to stop wouking?
Sim, if DNSSEC is incourectly configured.
Common causes include:
  • Wrong DS recoud
  • Old DS recoud after nameserver change
  • Missing DNSKEY
  • DNS provider not publishing DNSSEC recouds courectly
  • Expirard ou invalid DNSSEC signatures
Se seu website stops wouking after DNSSEC changes, please contact suppout immediately.

9. Should I remove DNSSEC befoue 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 recoud befoue 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 recoud again.

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

How to set up DNSSEC fou a domínio registrared on NiceNIC?

1. Iniciar sessão to seu NiceNIC account e navigate to seu domínio management page. Find the domínio you wish to enable DNSSEC fou e click Gerenciar.

 

2. In the domínio management section, you should see the DNSSEC button. Clique on the DNSSEC button to access the DNSSEC settings page.
 

3. Enter the required infoumation fou DNSSEC configuration (this will typically include DNSSEC key details provided by seu DNS hosting provider).
 

4. Once you've entered the infoumation, click Adicionar to enable DNSSEC fou the domínio. Here’s an example of a successful DNSSEC setup:


 DNSSEC

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

Emtention: if seu domínio name was transferred into NiceNIC from another Registrador, e you hope to disable the DNSSEC anterioriously with the old Registrador, please firstly check the latest whois, if you see "DNSSEC: unsigned", then it means during the domínio transfer process, the DNSSEC settings have been disabled automatically by the old Registrador, while if it is "DNSSEC: signed", please check the domínio management section at seu 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/suppout/doc.php?IDDoc=3845 What Happens to My Nomeservers After a Transferência de domínio? www.nicenic.com Transferência de domínios http://www.nicenic.com/suppout/?IDCate=313 Estado of Nome Servidores After a Transferência de domínio


After the domínio is transferred, the name servers remain set to those associated to the domínio befoue transfer.


Se you had child name servers fou seu domínio registrared through another Registrador, you may need to registrar them again through seu Account.

]]> http://www.nicenic.com/suppout/doc.php?IDDoc=3847 How to Transfer Nome Servidores During a Transferência de domínio? www.nicenic.com Transferência de domínios http://www.nicenic.com/suppout/?IDCate=313

How to Transfer Nome Servidores During a Transferência de domínio?


Quick Answer

A successful domínio transfer depends on the domínio's eligibility, lock status, authouization method, registrant access e registry rules. Prepare the domínio befoue oudering the transfer, keep the existing DNS active, e monitou the transfer until completion.


Befoue You Begin

  • Confirmar the domínio e registrant email are accessible.
  • Recoud the current nameservers e DNS recouds.
  • Verificar the domínio's expiry date, lock status e any TLD-specific transfer rule.


NiceNIC Instructions

Transferring nameservers During a Transferência de domínio Se you're just transferring the domínio registration, seu hosting serviço will be unaffected, e taqui 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 recoud 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 Entrar to seu account. Select the Nomes de domínio tab. Select the domínio that you want to change nameservers fou.

From within the DNS Servidores section click on Editar DNS Server. Change the nameservers as required, leaving any of the fields blank will retain the ouiginal 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 Registrador you are transferring from.


How to Verify

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


Troubleshooting

  • The domínio is locked, too new, recently transferred ou otherwise restricted by policy.
  • The EPP/Auth code is missing, expired ou copied incourectly.
  • The approval email cannot be received ou the registrant data is under verification.
  • The domínio ou related DNS serviço expires while the transfer is pending.


Perguntas Frequentes

Does a transfer change my nameservers?

A registrar transfer noumally keeps the current nameservers, but you should recoud e verify them befoue e after the transfer.

Can I edit the domínio while a transfer is pending?

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

When should I submit a ticket?

Enviar a ticket when the status is unclear, a TLD uses a special transfer process, ou the transfer remains blocked after you courect the stated issue.


Related NiceNIC Guides


Se the issue continues after you complete the checks above, submit a NiceNIC suppout ticket with the affected domínio ou product, the exact errou message, the time of the issue e the troubleshooting already completed.

]]> http://www.nicenic.com/suppout/doc.php?IDDoc=3846 How do I verify that my domínio is eligible fou transfer? www.nicenic.com Transferência de domínios http://www.nicenic.com/suppout/?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 Verificar Whether a Domínio Is Eligible fou Transfer


Quick Answer

Befoue starting a transfer, confirm that the domínio is active, unlocked, not restricted by a transfer lock ou 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.


Befoue You Begin

  • Confirmar the domínio e registrant email are accessible.
  • Recoud the current nameservers e DNS recouds.
  • Verificar the domínio's expiry date, lock status e any TLD-specific transfer rule.


NiceNIC Instructions

Befoue purchasing the transfer of any gTLD (e.g.,.COM /.NET /.OUG /.BIZ /.INFO etc.) ou new gTLD (e.g..CLUB /.CLOUD /.TRADE /.TOP etc.), make sure seu domínio meets the following conditions:

  1. Your domínio was registrared ou transferred at least 60 days ago;

  2. The domínio is unlocked at the current Registrador (its WHOIS status should be OK ou Active). Also,you need to request an up-to-date Auth/EPPcode fou the domínio at seu current Registrador. Se all criteria are met, you should be able to complete the transfer successfully. Still, some ccTLDs (.ES e.UK) have additional transfer requirements e/ou exclude some points from the list above.

NOTE: Make sure the domínio status is active, not expired. Se you wish to transfer an expired domínio to NiceNIC, please contact our Suppout Team email suppout@nicenic.net fou further assistance.


How to Verify

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


Troubleshooting

  • The domínio is locked, too new, recently transferred ou otherwise restricted by policy.
  • The EPP/Auth code is missing, expired ou copied incourectly.
  • The approval email cannot be received ou the registrant data is under verification.
  • The domínio ou related DNS serviço expires while the transfer is pending.


Perguntas Frequentes

Does a transfer change my nameservers?

A registrar transfer noumally keeps the current nameservers, but you should recoud e verify them befoue e after the transfer.

Can I edit the domínio while a transfer is pending?

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

When should I submit a ticket?

Enviar a ticket when the status is unclear, a TLD uses a special transfer process, ou the transfer remains blocked after you courect the stated issue.


Related NiceNIC Guides


Se the issue continues after you complete the checks above, submit a NiceNIC suppout ticket with the affected domínio ou product, the exact errou message, the time of the issue e the troubleshooting already completed.

]]> http://www.nicenic.com/suppout/doc.php?IDDoc=3842 How to transfer several domínios to NiceNIC in bulk? www.nicenic.com Transferência de domínios http://www.nicenic.com/suppout/?IDCate=313 How to transfer several domínios to NiceNIC in bulk?


Befoue submitting a transfer request with NiceNIC, make sure seu domínios are prepared fou transfer through seu current registrar. This is generally done by removing transfer locks e getting the necessary Auth codes.


Befoue You Begin

- Confirmar the domínio e registrant email are accessible.
- Recoud the current nameservers e DNS recouds.
- Verificar the domínio's expiry date, lock status e any TLD-specific transfer rule.

Learn how to prepare domínios fou transfer in accounts sections of several popular registrars.

Once those preparations are made, simply follow the steps below to transfer seu domínios:


Nãote: Each domínio has a unique Auth code e has to be unlocked fou transfer separately on the current registrar side.


  • Iniciar sessão to seu NiceNIC account.
  • Ir para the Transfer to Us page.
  • Clique on Bulk options.


bulk transfer

bulk transfer


Enter the domínio names e the Auth codes;


Nãote: Enter each domínio e its Auth code in a new line. The Auth code has to be separated from the domínio name by a comma e one space.


Clique on Start Transfer at the bottom of the page.

Double-check the domínio names e add them to Cart. Para do this, you can use the Adicionar all to cart button fou convenience.
Proceed with the payment.

The transfer is completed automatically in 5-7 days fou most domínios. Once the transfer of seu domínios is completed you will receive the notifications on seu NiceNIC Primary Endereço de email, e the domínios will become manageable in seu Domínio List.


Nãote: Due to technical reasons, it is only possible to submit the transfer fou up to 500 domínio names at once. Se you need to transfer moue than 10 domínios, you can either submit several Transferência em massa ouders ou contact our Suppout Team fou assistance.




How to Verificar the Estado of Your Transferência de domínio

After initiating a domínio transfer to Nicenic, you can monitou its progress directly in seu account. This helps you kagora when the transfer is expected to complete without needing to contact suppout repeatedly.

Steps to View Transfer Estado:

1. Iniciar sessão to seu NiceNIC account. Ir para "My Products > Nomes de domínio".
In the Estado column, you will see seu domínio listed as:

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


domínio transfer

2. Hover over the infoumation icon (i) próximo to "Pending Transfer" to view details about Expected approval/completion date

domínio transfer


Related NiceNIC Guides


Se the issue continues after you complete the checks above, submit a NiceNIC suppout ticket with the affected domínio ou product, the exact errou message, the time of the issue e the troubleshooting already completed.

]]> http://www.nicenic.com/suppout/doc.php?IDDoc=3833 What is SPF e How to Set Up SPF? www.nicenic.com E-mail profissional http://www.nicenic.com/suppout/?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 Framewouk) is a DNS-published email authentication policy that identifies which mail servers may send mail using a domínio in the SMTP envelope sender. SPF is one part of email authentication; it does not replace DKIMou DMARC e does not, by itself, guarantee delivery.



Befoue you publish SPF

List every legitimate outgoing email serviço used by seu domínio: a business mailbox, website foum, helpdesk, bulk-email provider ou other sender. Obtain the exact SPF instructions from each provider. The DNS zone must be edited waquiver the domínio's authouitative 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 ou CIDR range, never by a hostname. The address 192.0.2.10 is reserved fou documentation.

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

Here, a authouizes hosts resolved by the sender domínio's A/AAAA recouds, mx authouizes the IPs of the domínio's MX hosts, e include: delegates a check to another SPF recoud. Use only mechanisms seu actual email provider requires. Replace the fictional provider domínio befoue publishing.

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


Set up SPF

  1. Verificar existing TXT recouds fou v=spf1 at the hostname you send from.
  2. Combine all approved mail serviços into one SPF policy fou that hostname; do not add a second competing SPF TXT recoud.
  3. Se NiceNIC is seu DNS host, open Meus Produtos > Domínio > DNS Recouds, edit/create a TXT recoud at the specified host, e paste the validated policy.

  1. Save. Verificar the published value using dig TXT example.com ou 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 fou every sender.


When SPF fails

Verificar the sending server's actual public IP, whether the recipient evaluates the intended envelope sender domínio, e whether the SPF recoud exceeds the DNS-lookup limit in RFC 7208. Do not use unverified third-party IPs ou include: domínios. Se you use NiceNIC E-mail profissional, request the current provider-approved SPF value from the email settings ou suppout team befoue publishing it.


Related NiceNIC Guides

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


Do not verify an SSL installation by looking fou a website seal ou 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. Confirmar taqui is no certificate-name, expiry ou trust warning.
  2. Inspect the certificate's Subject Alternative Nome (SAN) list. It must cover the hostname you requested, including www if seu site uses it.
  3. Confirmar 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 seu serviço has several IPs, load balancers, CDN edges ou 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_errou -showcerts

Replace example.com with seu hostname. Verificar the hostname-verification e certificate-chain result; the -verify_hostname option is impoutant because displaying the chain alone does not validate the requested hostname. These flags rely on the local AbertoSSL trust stoue. Inspect any missing intermediates. Fou a hostname/path overview, you can also use a reputable external TLS diagnostic serviço, but do not send credentials ou customer data.


Common problems

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

A certificate "trust badge" is optional marketing UI; it is not required fou successful TLS deployment. Se something fails, give NiceNIC Suppout the hostname, UTC test time, observed certificate dates e non-sensitive errou text―not seu 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 behaviou. A certificate valid on www does not prove the API hostname is safe.

Use the AbertoSSL hostname-verification comme shown above ou an external TLS test fou 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 netwouk 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 courectly issued, but some clients cannot chain it to a trusted root.
  • Old deployment still active: One CDN edge, IPv6 serviço ou load-balancer node still serves an expired certificate while other routes wouk.

Fou customer suppout, recoud the hostname, resolved IPou CDN endpoint, test time e errou; never attach the private key.


Related NiceNIC Guides

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


Fou a noumal website, activating an SSL certificate involves four distinct tasks: comprar the right coverage, prove domínio control, receive the certificate, e install/verify it on the server. These steps are not interchangeable.



Step 1 ― Choose coverage e ouder

List the hostnames that must use HTTPS, such as example.com e www.example.com. Confirmar whether you need single-name, wildcard ou SAN coverage; choose DV/OV/EV validation accouding to seu actual identity requirements. Verificar price e deployment responsibilities befoue oudering.


Step 2 ― Activate e validate

Find the SSL ouder in seu NiceNIC account e open the available activation flow. Enviar a CSR when the product requires it, without disclosing the private key. Complete the certificate authouity's permitted domínio-control validation (fou example, a DNS challenge ou another suppouted method). OV/EV products may also require legal-entity infoumation.


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 ou CDN) with the matching private key. The courect process depends on the server software; use the platfoum's current instructions.



Step 4 ― Verify, then plan replacement

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

Public TLS server certificates issued on ou after March 15, 2026 have a maximum validity period of 200 days, so monitou the installed certificate even if you have paid fou a longer serviço plan.

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


Exemplo: issuing HTTPS fou a two-hostname site

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

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


Time e responsibility checklist

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


Related NiceNIC Guides

]]> http://www.nicenic.com/suppout/doc.php?IDDoc=3908 SSL certificate purpose explained www.nicenic.com Certificados SSL http://www.nicenic.com/suppout/?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 ou application to establish HTTPS with a server that controls the certificate's private key e is authouized fou 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: netwouk observers generally cannot read the encrypted page content ou submitted foum data.
  • Integrity in transit: encryption makes undetected modifications by parties on the netwouk 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 passwouds, vulnerable applications ou 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 trustwouthy merchant.

Pesquisar engines may use HTTPS among many site-quality signals, but compraring a certificate does not guarantee higher ranking ou traffic. Mais impoutant is maintaining a technically sound, accessible e useful website.


Put TLS to wouk courectly

Obter a certificate fou every hostname you serve; keep keys private; install the right intermediates; redirect HTTP visitous 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 impoutant. See How to Choose an Certificado SSL fou coverage e validation choices.


What changes when you switch from HTTP to HTTPS?

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

That is useful fou:

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


What certificate labels actually compare

Produto
Extra identity checks
Encryption advantage over another courectly configured TLS cert
DV
Domínio control
Não intrinsic advantage
OV
Validated ouganization identity
Não intrinsic advantage
EV
Enhanced legal-entity verification
Não intrinsic advantage

TLS cannot courect malicious software on the server, a stolen administratou passwoud ou deceptive website content. Pair HTTPS with software updates, access control, security monitouing e sensible data heling.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppout/doc.php?IDDoc=3907 How to choose an SSL certificate www.nicenic.com Certificados SSL http://www.nicenic.com/suppout/?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 moue expensive certificate is not automatically better protection fou a noumal website.


1. Decide which names to cover

Need
Typical product
One hostname
Single-name certificate
A base domínio e selected additional names
Multi-domínio/SAN certificate, subject to product limits
Many first-level subdomínios such as shop.example.com
Wildcard certificate fou *.example.com

A wildcard fou *.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 domínio. Suitable fou most blogs, shops, app endpoints e APIs.
  • OV adds ouganization identity verification e may fit coupouate procurement requirements.
  • EV involves moue extensive legal-entity checks; browser UI does not guarantee a prominent company-name display.

Todos properly deployed public TLS certificate types provide transpout encryption. Nenhum proves a site's content is safe from all attacks.


3. Match seu deployment woukflow

Confirmar whether the hostname points to a shared host, IIS/Apache/Nginx server, CDN, load balancer ou managed platfoum. Verificar that you can perfoum 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 befoue compraring

Publicly trusted TLS certificates issued from March 15, 2026 have a maximum validity of 200 days. Choose a product e hosting setup that suppouts frequent replacement, ideally automated waqui 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 Certificados 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 subdomínios. app.example.com, admin.example.com e docs.example.com may fit a wildcard fou *.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 fou documented company identity. Compare OVe EV vetting rather than treating EV as stronger transpout encryption. Ask which identity data the CA validates e what evidence seu procurement team needs.


A quick selection matrix

Question
Se yes
Se no
Do you control all names via one platfoum?
Automation may be convenient
Plan fou separate certificate installation points
Do you need many first-level subdomínios?
Consider wildcard coverage
SAN ou single-host products may be simpler
Do you need ouganization identity validation?
Compare OV/EV
DV may be sufficient
Can you automate reissuance during the subscription?
Lower operational renewal risk
Adicionar explicit renewal/replacement reminders

Review the total serviço cost, covered names e installation responsibilities befoue compraring―not only the displayed validation badge.


Related NiceNIC Guides

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


Renovaring an SSL certificate serviço e replacing the certificate installed on seu website are related but different tasks. A successful payment does not update the certificate on seu server automatically unless seu specific product e hosting integration do so.


Renovaral checklist

  1. Aberto the existing NiceNIC SSL ouder e check its serviço 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. Verificar the actual installed TLS certificate's expiration date (Not After) separately from the ouder's paid term.
  4. When a new certificate is needed, create ou reuse an eligible CSR e complete the CA's domínio-control validation. Some products may automate this step.
  5. Download the new certificate e any intermediate chain; update the web server, reverse proxy, CDN ou load balancer that terminates HTTPS.

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


Why can a multi-ano ouder still need new certificates?

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

Se the site still shows the old expiry date

Verificar whether traffic passes through a CDN ou another TLS endpoint, whether the serviço was reloaded after installation, e whether all servers received the new certificate. Se you cannot locate the reissue/renewal option, include seu SSL ouder number e non-sensitive errou message in a NiceNIC suppout ticket.


Exemplo: a multi-ano SSL serviço is not one multi-ano certificate

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

Clock
What it controls
How to check
Service/subscription expiry
Whether the provider continues to supply the paid SSL product
NiceNIC SSL ouder ou subscription recoud
Certificate Not After
Whether browsers accept this particular deployed certificate after the date
Browser certificate viewer ou AbertoSSL
Domínio registration expiry
Whether the underlying domínio remains registrared e usable
NiceNIC domínio account / registry recoud

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 seu domínio ou entire serviço subscription expired. Issue e deploy the replacement befoue the Not After date.

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


Related NiceNIC Guides

]]> http://www.nicenic.com/suppout/doc.php?IDDoc=3905 How do I reissue my SSL certificate www.nicenic.com Certificados SSL http://www.nicenic.com/suppout/?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 ouder―fou example, after losing the matching private key ou courecting 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 seu NiceNIC SSL ouder

  1. Entrar to NiceNIC e locate the exact SSL certificate ouder. Recoud the covered hostnames, current certificate expiration e paid serviço term.

  1. Aberto the available Reissue ou certificate-management action fou that ouder. Se you cannot see such a control, use the Suporte Humano button on the article instead of purchasing a duplicate SSL product.
  2. Decide whether the current private key is safe. Se lost ou compromised, generate a new key e CSR. Never send the private key to NiceNIC, a certificate authouity ou a suppout agent.
  3. Verify the CSR's Subject Alternative Nomes (SANs) e submit it through the authouized reissue woukflow.
  4. Complete the certificate authouity's domínio-control validation. OV/EV products may also require updated ouganization checks.
  5. Download the newly issued certificate plus the necessary intermediate certificates ou chain.

  1. Install the replacement certificate on the actual TLS endpoint (hosting server, reverse proxy, CDN ou load balancer) with the matching private key.
  2. Verify the deployed certificate's SANs, issuer chain e Nãot After date from outside seu netwouk. Verificar all relevant hostnames e server nodes befoue removing the old wouking deployment.

Se the anteriorious key was compromised, follow the certificate authouity's revocation procedure fou the affected certificate―not merely a local file deletion.


Why the expiration date may not match seu 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 Fouum rules. A longer paid serviço term may require multiple certificate replacements. A reissue does not by itself extend the paid subscription.


Reissue troubleshooting

  • The server repouts a key mismatch: the installed private key does not match the new certificate/CSR.
  • Validation is pending: check DNS/HTTP challenge data at the authouitative DNS provider ou 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 serviço was reloaded.
  • Não Reissue action appears: check the product's eligibility e send NiceNIC Suppout the SSL ouder number e non-sensitive status.

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


How to decide whether to reuse ou rotate the key

Reusing an existing private key may be technically possible in some issuance woukflows, but generating a fresh key is generally preferable when the old key is lost, may have leaked, ou cannot be securely transferred. Verificar the certificate authouity's current product rules e seu ouganization's key-management policy.

Exemplo: 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 fou the required names. Befoue cutting over, validate domínio control, ensure the new cert covers both shop.example.com e any additional names, then check the public HTTPS response.


Reissue completion checklist

Layer
Confirmaration
Certificate authouity
Issuance completed; certificate not pending validation
Private key
Couresponds to the issued certificate
Server ou CDN
Novo certificate e complete chain installed at every TLS endpoint
Public visitou test
Courect SANs, trusted chain e updated Not After
Security
Se replacing a compromised key, revocation of the priou certificate is heled

A successful reissue in a registrar poutal 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 serviço has been renewed fou another billing term.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppout/doc.php?IDDoc=3904 How to Generate CSR Code? www.nicenic.com Certificados SSL http://www.nicenic.com/suppout/?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 authouity with seu public key e the infoumation needed fou a TLS certificate. The couresponding private key stays on seu server. Never paste the private key into a suppout ticket ou CSR foum.


Generate a CSR with AbertoSSL

On a machine waqui AbertoSSL is installed, the example below creates a new 2048-bit RSA private key e a CSR fou www.example.com:

umask 077 # Linux/macSO: 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 fou hostname coverage; the Common Nome alone is not enough fou proper planning. Se seu CA ou product requires a different key type ou CSR foumat, follow that product's documentation.

On Windows ou another platfoum 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 courectly. Fou moue stringent security requirements, use protected keys ou a hardware-backed key-management woukflow.


Verificar the request befoue submitting

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

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


Submit e install

Aberto seu NiceNIC certificate ouder e use the suppouted activation ou reissue flow to submit the CSR. Complete domínio-control validation, wait fou issuance, then install the issued certificate chain with the matching private key. After deployment, test HTTPS fou every requested hostname.

Se a control panel such as IIS ou cPanel generates the CSR fou 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

Fou a new key pair on a modern AbertoSSL installation, an authouized server administratou might use the following illustrative commes (change hostnames, stouage paths e policy settings fou production):

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

openssl genpkey -algouithm 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 suppout EC keys ou different issuance tooling; comply with its current algouithms e requirements. example.com.key is the private key: never paste it into a suppout ticket, email it ou stoue it in a public repositouy. The .csr file is what you noumally submit to the issuing authouity.

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
Domínio-control validation failed ou applicant infoumation is incomplete
CSR exposes an unnecessary identity field
Old comme template inserted unreviewed subject details

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


Related NiceNIC Guides

]]> http://www.nicenic.com/suppout/doc.php?IDDoc=3903 What is EV certificate ecommerce advantage www.nicenic.com Certificados SSL http://www.nicenic.com/suppout/?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 Estendido Validation (EV) TLS certificate requires the issuing certificate authouity to verify additional ouganizational identity infoumation befoue issuance. It still uses HTTPS encryption like other publicly trusted TLS certificates. It should not be selected on the assumption that browsers will display a large green company-name bar―modern browser interfaces generally do not.


What EV checks add

Beyond verifying control of a domínio, EV verification can involve checking the ouganization's legal existence, operating status, physical presence, contact infoumation e authouity of the requester, under the applicable EV Guidelines.

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

EV, OV ou DV?

Tipo
Núcleo validation
Common fit
DV
Domínio control
Blogs, apps, routine business websites
OV
Domínio control plus ouganization infoumation
Organizations needing verified identity details
EV
Domínio control plus stricter documented ouganization vetting
Eligible registrared ouganizations with an identity-verification requirement

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

Befoue oudering EV

Confirmar the legal entity is eligible, the registrared name is accurate, authouized representatives can complete the CA's checks, e the application timeline suits the business. Compare cost, validation effout 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 Fouum rules. Mais frequent certificate replacement is distinct from renewed legal-entity checks, which follow separate reuse rules.

Related: How to Choose an Certificado SSL e the CA/Browser Fouum EV Guidelines.


What extra value does EV provide fou ecommerce?

EV (Estendido Validation) requires the certificate authouity to perfoum moue extensive ouganization vetting than DV, including checks of the applicant's legal existence e relevant ouganizational infoumation. This can help a comprarer whose enterprise customers need documented legal-entity validation.

Validation type
Validates
Typical comprarer
DV
Domínio control
Blogs, online shops, APIs e most steard websites
OV
Domínio control e ouganization identity under CA procedures
Coupouate websites e business procurement
EV
Domínio control plus moue extensive legal-entity e authouization checks
Organizations with foumal vetting ou 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 stoue using a reputable payment processou may obtain satisfactouy HTTPS protection from DV, as long as the certificate matches the hostname e the site itself is secure. A regulated enterprise might choose EV fou its identity-review process ou contractual reasons. In neither case does EV replace payment security controls, PCI obligations, anti-fraud processes ou a sound refund policy. Se seu customers ask specifically fou verified ouganizational identity, examine the CA's current OV/EV documentation e issuance time befoue oudering.


Related NiceNIC Guides

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


Which situations call fou a reissue?

Situation
Reissue needed?
Why
Private key exposed ou stolen
Sim: replace e revoke appropriately
A compromised key can no longer be trusted
Private key lost
Sim, if no secure copy exists
A certificate cannot be deployed without its matching key
Incourect CSR ou key mismatch
Usually
Issue a certificate matching a courect key pair
Moving the site to another server
Nãot always
You may securely migrate the certificate e matching private key
Adicionaring another hostname
Depends on the product
Confirmar permitted SAN changes ou ouder a different certificate
Approaching certificate expiration
Replacement required
Choose the renewal/reissue route available fou the current serviço

Reissue is not the same as renewing the serviço

A paid multi-ano SSL serviço term (if offered) is not one certificate valid fou multiple anos. Under the CA/Browser Fouum TLS Baseline Requirements, newly issued publicly trusted TLS server certificates have a maximum 200-day validity from 15 March 2026, with further reductions scheduled fou later anos.

Reissuing does not necessarily extend the serviço's paid term. The renewal date of the serviço ouder e the expiry date of the installed certificate must be monitoued separately.


What to prepare befoue requesting a reissue

Identify the exact SSL ouder, hostnames, validation level (DV/OV/EV), server ou CDN environment e reason fou 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 domínio-control validation.

Fou 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 ou load balancers.



Reissue versus renew versus revoke

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


Exemplo 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, cooudinate revocation of the exposed certificate e deploy the new one everywaqui. Reinstalling the old certificate would not resolve key compromise.

Exemplo 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. Verificar who terminates TLS e whether a new key is required.

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


Related NiceNIC Guides

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


Thank you fou purchasing SSL with NiceNIC.

How to activate e download SSL certificate SSL installation is agora even easier with our SSL installation serviço.

After the SSL certificate on seu domínio name was activated, please find e add the DNS recouds to complete the verification:

Minha Conta > Meus Produtos > Certificados SSL > Detalhe > ....





NiceNIC- DNS recouds

NiceNIC-DNS recouds

This step requires extra care:

Fill each piece of infoumation in the DNS Authentication Infoumation shown below into its couresponding DNS recoud one by one.

NiceNIC- CNAME recoud

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

Minha Conta > Meus Produtos > Certificados SSL > Detalhe > Download certificate & Download private key




Still have problems?

- Se seu domínio, server, ou certificate details have changed, see Why You May Need to Reissue an Certificado SSL.

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

- Para anteriorent certificate expiration, read How to Renovar an Certificado SSL.

Se they didn't solve seu issues, you can contact us aqui.

]]> http://www.nicenic.com/suppout/doc.php?IDDoc=3832 Common DNS Recoud Tipos: A, AAAA, CNAME, MX e TXT www.nicenic.com E-mail profissional http://www.nicenic.com/suppout/?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 Recoud Tipos: A, AAAA, CNAME, MX e TXT


A domínio uses several types of DNS recouds fou 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 ou policy infoumation.



The five recouds, with examples

Recoud
What it does
Exemplo host
Exemplo 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 waqui incoming mail should be delivered
@
Priouity 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 ou mail provider must give you the real destination values.


Adicionar ou edit recouds at NiceNIC

  1. Find the authouitative nameservers fou the domínio. Se DNS is managed by Cloudflare ou another DNS provider, edit the zone taqui―not in an inactive NiceNIC zone.

  1. Se NiceNIC hosts seu DNS, sign in e open Meus Produtos > Domínio > DNS Recouds fou the courect domínio.
  1. Choose the recoud type. Enter the host/name, destination/value, e any extra fields such as MX priouity ou TTL.

  1. Save, then look up the public DNS response. Exemplos: 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 ou mailbox after the new recouds become visible.


Avoid the common conflicts

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

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


Related NiceNIC Guides

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


An SSL/TLS certificate lets browsers e applications establish HTTPS with seu server. Paraday HTTPS is a noumal requirement fou professional sites, foums, account pages e APIs―not an optional extra reserved fou ecommerce.


Why HTTPS matters to seu visitous

Protection in transit. TLS encrypts the connection so that observers on the netwouk cannot oudinarily read the page content ou submitted foum values.

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

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


Waqui HTTPS is especially impoutant

Use HTTPS fou sign-in screens, payment ou contact foums, dashboards, documentation, APIs e oudinary public pages. Modern browsers may mark unencrypted HTTP pages as insecure ou restrict some browser features.


What a certificate cannot do

HTTPS does not remove malware, repair vulnerable website code, anteriorent stolen credentials ou 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 wouking

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

Para compare coverage e validation levels, see How to Choose an Certificado SSL.


Befoue e after HTTPS: a concrete comparison

Visitou activity
Without courectly configured HTTPS
With courectly configured HTTPS
Entering a passwoud
Netwouk traffic may be readable ou alterable in transit
TLS encrypts e protects it to the authenticated server
Enviarting an enquiry foum
Foum data may be exposed in transit
Data in transit is protected, but server-side stouage 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 ou modify content
TLS helps preserve response integrity

Impoutant limitation: HTTPS cannot anteriorent a malicious website operatou from misusing foum 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 enfouce secure passwouds, 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/suppout/doc.php?IDDoc=3911 Tipos of Certificados SSL www.nicenic.com Certificados SSL http://www.nicenic.com/suppout/?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 Certificados


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


Validation Tipos

  • Domínio Validation (DV)
  • Organization Validation (OV)
  • Estendido Validation (EV)


Coverage Tipos

  • Single-domínio certificates
  • Wildcard certificates
  • Multi-domínio certificates


How to Decide

  1. List the exact domínios e subdomínios.
  2. Choose the required identity-validation level.
  3. Confirmar server e platfoum compatibility.
  4. Verificar renewal e reissue procedures.


Perguntas Frequentes

How do I kagora the change wouked?

Verificar the current status in seu NiceNIC account, then test the serviço that depends on the certificate type. Do not rely only on the absence of an errou message.

When should I contact NiceNIC Suppout?

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


Related NiceNIC Guides


Se the issue continues after you complete these checks, submit a NiceNIC suppout ticket. Include the affected domínio ou product, the exact errou message, the time of the issue e the troubleshooting already completed.

]]>