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


Quick Answer

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


Befvaie You Begin

  • Identify every hostname the certificate must cover.
  • Apstiprināt that you control DNS vai the required validation channel.
  • Generate un securely retain the private key when a CSR is required.


NiceNIC Instructions

HTTPS & SSL Configuration Guide Lai ensure the security of jūsu website un protect jūsu visitvais, all domēnss under.boo,.day,.dev,.page, un.rsvp must use HTTPS. This guide will help you configure SSL/TLS cvairectly.

  1. What is HTTPS? HTTPS (Hypertext Transfer Protocol Secure) encrypts data between jūsu website un its visitvais. It Iepriekšējaisents eavesdropping un ensures data integrity.

  2. Obtaining an SSL sertifikāts NICENIC provides trusted SSL certificates. You can learn mvaie un iegādāties/configure a certificate šeit: https://nicenic.com/ssl-certificates/

  3. Installing the SSL sertifikāts Sekot jūsu 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. Enfvaice HTTPS Once jūsu certificate is installed: Redirect all HTTP traffic to HTTPS. Update internal links un resources to use HTTPS. Verify that jūsu website is fully accessible via HTTPS.

  5. Keep Sertifikāti Atjaunināts SSL certificates have expiration dates. Ensure certificates are renewed befvaie they expire un check jūsu website regularly to maintain uninterrupted secure connections.


How to Verify

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


Troubleshooting

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


Biežāk uzdotie jautājumi

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

Iesniegt a ticket when validation remains pending after the published recvaids are visible, vai when the NiceNIC vaider does not provide the expected certificate files.


Related NiceNIC Guides


Ja the issue continues after you complete the checks above, submit a NiceNIC suppvait ticket with the affected domēns vai product, the exact errvai message, the time of the issue un the troubleshooting already completed.

]]> http://www.nicenic.com/suppvait/doc.php?IDDoc=4374 How to Set Up un Troubleshoot DNSSEC fvai Your Domēns www.nicenic.com DNS & Nosaukumsservers http://www.nicenic.com/suppvait/?IDCate=408 How to Set Up un Troubleshoot DNSSEC fvai Your Domēns?

DNSSEC helps protect jūsu domēns’s DNS recvaids 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 cvairect source.

Pie NiceNIC, DNSSEC usually involves two sides:
Your DNS provider vai nameserver provider generates the DNSSEC recvaids.
NiceNIC, as jūsu domēns registrar, helps submit the DS recvaids to the registry when the TLD suppvaits DNSSEC.

Ja DNSSEC is not configured cvairectly, jūsu domēns may show DNSSEC errvais, vai in mvaie serious cases, some users may not be able to access jūsu website.

What Is DNSSEC?
DNSSEC stuns fvai Domēna vārds System Security Extensions.
In simple terms, DNSSEC helps verify that the DNS answer fvai jūsu domēns has not been changed vai fvaiged during the lookup process.
Fvai example, when someone visits jūsu website, DNS is used to find the cvairect server IP address. DNSSEC helps make sure that the DNS result is authentic un has not been replaced with false data.
DNSSEC does not replace SSL, website security, hosting security, vai 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 hunles sensitive user infvaimation.
  3. You run business email, login systems, payment pages, vai customer pvaitals.
  4. You want stronger domēns security.
  5. Your DNS provider suppvaits DNSSEC.
  6. Your domēns extension suppvaits DNSSEC.
Ja you are not familiar with DNS management, we recommend confirming with jūsu DNS provider befvaie enabling DNSSEC.
Incvairect DNSSEC settings may affect domēns resolution.

Impvaitant DNSSEC Termiņšs
DNSKEY: A DNSKEY recvaid is generated by jūsu DNS provider. It is used as part of the DNSSEC validation process.
DS Recvaid: A DS recvaid connects jūsu domēns’s DNSSEC setup with the parent registry zone. In most cases, jūsu DNS provider gives you the DS recvaid, un you need to add it through jūsu registrar.
Nosaukumsserver: Your nameservers decide wšeit jūsu domēns’s DNS recvaids are managed. Ja you change nameservers, jūsu DNSSEC recvaids may also need to be updated.

How to Enable DNSSEC fvai Your Domēns
Befvaie You Begin: Back Up Your DNS Recvaids
Befvaie enabling DNSSEC, save a copy of jūsu current DNS recvaids, especially impvaitant A, AAAA, CNAME, MX, TXT, un CAA recvaids. Enabling DNSSEC does not nvaimally change these recvaids, but keeping a backup makes it easier to verify vai restvaie jūsu DNS configuration if you also change nameservers vai DNS providers.
Ja needed, see: How to Back Up DNS Recvaids Befvaie Changing Domēns Settings.

Step 1: Pārbaudīt Whether Your DNS Provider Suppvaits DNSSEC
Pierakstīties to the platfvaim wšeit jūsu DNS is managed.
This may be:
Your domēns registrar, šeit is NiceNIC
Your hosting provider
Your DNS provider
Your own DNS server
Another third-party DNS pakalpojums
Make sure DNSSEC is suppvaited un enabled tšeit.
Impvaitant: Enable DNSSEC un DNSSEC signing at jūsu current DNS provider first. Only add the DS recvaid at NiceNIC after jūsu DNS provider has generated the DNSSEC infvaimation un is publishing the cvairesponding DNSKEY. Pievienoting a DS recvaid befvaie the DNS provider is ready may cause DNSSEC validation to fail.

Step 2: Saņemt the DS Recvaid from Your DNS Provider
After enabling DNSSEC, jūsu DNS provider should provide DNSSEC infvaimation such as:
Key Tag
Algvaiithm
Digest Tips
Digest
DS Recvaid
Please copy the infvaimation exactly as provided.
Even one incvairect character may cause DNSSEC validation failure.

Step 3: Pievienot the DS Recvaid in Your NiceNIC Account
Pierakstīties to jūsu NiceNIC account un go to jūsu domēns management page.
Then add the DS recvaid provided by jūsu DNS provider.
Ja you are not sure wšeit to add it, please contact our suppvait team un provide the DS recvaid from jūsu DNS provider.

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

Step 5: Verify DNSSEC Statuss
After propagation, you may check jūsu domēns’s DNSSEC status using a DNSSEC checking tool vai by contacting our suppvait team.
Ja DNSSEC is cvairectly configured, the DNSSEC validation result should show a valid chain of trust.

When Should You Disable vai Noņemt DNSSEC?
You may need to remove vai update DNSSEC recvaids if:
  • You changed jūsu nameservers.
  • You moved DNS management to another provider.
  • Your DNS provider disabled DNSSEC.
  • Your DS recvaid no longer matches the current DNSKEY.
  • Your website vai email has DNS resolution issues after a DNS change.
Impvaitant: Ja you are moving to a new DNS provider vai changing authvaiitative nameservers while DNSSEC is enabled, check fvai existing DS recvaids befvaie making the change.
Ja the old DS recvaid will no longer match the new DNS provider, remove the old DS recvaid first un wait fvai its full TTL to expire at the parent zone befvaie changing nameservers. Keep DNSSEC signing active at the old DNS provider during this waiting period.
After the new nameservers are active un DNSSEC signing is enabled at the new DNS provider, obtain the new DS recvaid un add it through NiceNIC.
Changing nameservers while resolvers still have the old DS recvaid cached may cause DNSSEC validation failures un SERVFAIL responses.

Why Does My Domēns Atpakaļ SERVFAIL After Enabling DNSSEC?
SERVFAIL can occur when DNSSEC validation fails. Common causes include:
  • An old vai stale DS recvaid from a Iepriekšējaisious DNS provider
  • A DS recvaid that does not match the DNSKEY published by the current DNS provider
  • Multiple DS recvaids wšeit one vai mvaie no longer match an active DNSSEC key
  • DNSSEC signing is not active vai the required DNSKEY/RRSIG recvaids are not being published cvairectly
  • Nosaukumsservers were changed befvaie the Iepriekšējaisious DS recvaid had fully expired from DNS caches
Ja jūsu domēns resolves without DNSSEC validation but returns SERVFAIL through validating resolvers, this is a strong indication of a DNSSEC configuration problem.
Pārbaudīt the current nameservers, all DS recvaids published fvai the domēns, un the DNSKEY infvaimation from jūsu active DNS provider. Noņemt vai replace a DS recvaid only after confirming that it is outdated vai incvairect. Ja you are unsure, contact jūsu DNS provider vai NiceNIC Suppvait befvaie making changes.

Why Does My Domēns Show "DNSSEC Infvaimation Is Currently Unavailable"?
You may see this message:
DNSSEC infvaimation is currently unavailable fvai this domēns.
This can happen fvai several reasons:
  • DNSSEC has not been enabled fvai this domēns.
  • Nē DS recvaid has been added at the registrar level.
  • The domēns's current nameservers do not suppvait DNSSEC.
  • The domēns recently changed nameservers.
  • The DS recvaid does not match the current DNSKEY.
  • The DNS provider has not published the required DNSSEC recvaids cvairectly.
  • The registry vai DNSSEC query is tempvaiarily unavailable.
This message does not always mean jūsu domēns is broken.
However, if jūsu website vai email is not resolving cvairectly, please contact suppvait so we can help review the DNSSEC configuration.

What Infvaimation Should I Provide to Suppvait?
Lai help us check DNSSEC issues faster, please provide:
  1. Your domēns name
  2. Your current nameservers
  3. Whether you recently changed nameservers
  4. The DS recvaid provided by jūsu DNS provider
  5. A screenshot of the DNSSEC setting from jūsu DNS provider
  6. Any DNSSEC errvai message you received
  7. Whether jūsu website vai email is currently affected
With this infvaimation, our suppvait team can check whether the issue is caused by missing DS recvaids, mismatched DNSSEC recvaids, nameserver changes, vai registry-side limitations.

Biežāk uzdotie jautājumi Par DNSSEC

1. Is DNSSEC required fvai every domēns?
Nē. DNSSEC is not required fvai every domēns.
However, it is recommended fvai domēnss that need stronger DNS security, especially business websites, email pakalpojumss, login systems, financial pakalpojumss, un customer pvaitals.
Ja you are not sure whether you need DNSSEC, please confirm whether jūsu DNS provider suppvaits it un whether you are comfvaitable managing DNSSEC recvaids.

2. Is DNSSEC the same as SSL?
Nē.
SSL protects the connection between the user’s browser un jūsu website.
DNSSEC protects DNS resolution by helping verify that DNS responses have not been tampered with.
Fvai better security, many websites use both SSL un DNSSEC, but they are different technologies.

3. Can NiceNIC generate DNSSEC recvaids fvai me?
In most cases, DNSSEC recvaids are generated by jūsu DNS provider, not by the registrar.
NiceNIC can help submit the DS recvaid to the registry when the domēns extension suppvaits DNSSEC.
Ja you use a third-party DNS provider, please enable DNSSEC tšeit first un then provide us with the DS recvaid.

4. What should I check after changing nameservers, DNS providers, vai transferring my domēns?
Changing nameservers vai DNS providers can affect DNSSEC because the existing DS recvaid may no longer match the DNSKEY published by the new DNS provider.
A registrar transfer by itself does not necessarily mean that jūsu DNSSEC configuration must change. Ja jūsu nameservers un DNS provider remain the same, first check whether the existing DS recvaid is still present un still matches the current DNSKEY.
Ja you also changed nameservers vai DNS providers, check fvai old DS recvaids un follow the DNSSEC migration steps above befvaie publishing a new DS recvaid.
Do not assume that DNSSEC was automatically removed during a domēns transfer. Always verify the domēns’s current DS un DNSKEY status.

5. What happens if the DS recvaid is wrong?
Ja the DS recvaid does not match the DNSKEY published by jūsu current DNS provider, DNSSEC validation may fail.
This may cause some DNS resolvers to reject the DNS response.
As a result, jūsu website, email, vai other pakalpojumss may become unreachable fvai some users.

6. I do not use DNSSEC. Do I need to do anything?
Ja you do not use DNSSEC un jūsu domēns has no DS recvaids, usually no action is needed.
However, if jūsu domēns has old DS recvaids from a Iepriekšējaisious DNS provider, you should remove them to avoid DNSSEC validation problems.

7. Why does my DNSSEC status still show an errvai after I updated the recvaid?
DNSSEC updates may take time to propagate.
Ja you recently added, removed, vai changed DS recvaids, please wait fvai DNS propagation un check again later.
Ja the issue continues, please contact suppvait un provide jūsu domēns name, current nameservers, un DS recvaid.

8. Can DNSSEC cause my website to stop wvaiking?
Jā, if DNSSEC is incvairectly configured.
Common causes include:
  • Wrong DS recvaid
  • Old DS recvaid after nameserver change
  • Missing DNSKEY
  • DNS provider not publishing DNSSEC recvaids cvairectly
  • Beidzasd vai invalid DNSSEC signatures
Ja jūsu website stops wvaiking after DNSSEC changes, please contact suppvait immediately.

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

10. What should I do if I see “Failure to get DNSSEC info”?
This usually means the system could not retrieve valid DNSSEC infvaimation fvai the domēns.
Please check:
  • Whether DNSSEC is enabled
  • Whether the DS recvaid has been added
  • Whether the nameservers suppvait DNSSEC
  • Whether the DS recvaid matches the DNSKEY
  • Whether you recently changed nameservers
Ja you are not sure, please contact NiceNIC suppvait un provide jūsu domēns name un DNSSEC details from jūsu DNS provider.

How to set up DNSSEC fvai a domēns reģistrēted on NiceNIC?

1. Pierakstīties to jūsu NiceNIC account un navigate to jūsu domēns management page. Find the domēns you wish to enable DNSSEC fvai un click Pārvaldīt.

 

2. In the domēns management section, you should see the DNSSEC button. Noklikšķiniet on the DNSSEC button to access the DNSSEC settings page.
 

3. Enter the required infvaimation fvai DNSSEC configuration (this will typically include DNSSEC key details provided by jūsu DNS hosting provider).
 

4. Once you've entered the infvaimation, click Pievienot to enable DNSSEC fvai the domēns. Here’s an example of a successful DNSSEC setup:


 DNSSEC

After entering the necessary DNSSEC key data (usually the DS recvaid), you'll receive confirmation that DNSSEC has been successfully added to jūsu domēns settings.
The DNSSEC status will show as enabled un you'll be able to see the public keys un other details.
With DNSSEC tagad enabled, jūsu domēns is better protected against DNS-related attacks.

Pietention: if jūsu domēns name was transferred into NiceNIC from another Reģistrators, un you hope to disable the DNSSEC Iepriekšējaisiously with the old Reģistrators, please firstly check the latest whois, if you see "DNSSEC: unsigned", then it means during the domēns transfer process, the DNSSEC settings have been disabled automatically by the old Reģistrators, while if it is "DNSSEC: signed", please check the domēns management section at jūsu 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/suppvait/doc.php?IDDoc=3845 What Happens to My Nosaukumsservers After a Domēna pārsūtīšana? www.nicenic.com Domēna pārsūtīšanas http://www.nicenic.com/suppvait/?IDCate=313 Statuss of Nosaukums Serveri After a Domēna pārsūtīšana


After the domēns is transferred, the name servers remain set to those associated to the domēns befvaie transfer.


Ja you had child name servers fvai jūsu domēns reģistrēted through another Reģistrators, you may need to reģistrēt them again through jūsu Account.

]]> http://www.nicenic.com/suppvait/doc.php?IDDoc=3847 How to Transfer Nosaukums Serveri During a Domēna pārsūtīšana? www.nicenic.com Domēna pārsūtīšanas http://www.nicenic.com/suppvait/?IDCate=313

How to Transfer Nosaukums Serveri During a Domēna pārsūtīšana?


Quick Answer

A successful domēns transfer depends on the domēns's eligibility, lock status, authvaiization method, registrant access un registry rules. Prepare the domēns befvaie vaidering the transfer, keep the existing DNS active, un monitvai the transfer until completion.


Befvaie You Begin

  • Apstiprināt the domēns un registrant email are accessible.
  • Recvaid the current nameservers un DNS recvaids.
  • Pārbaudīt the domēns's expiry date, lock status un any TLD-specific transfer rule.


NiceNIC Instructions

Transferring nameservers During a Domēna pārsūtīšana Ja you're just transferring the domēns registration, jūsu hosting pakalpojums will be unaffected, un tšeit 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 recvaid of them. Ja 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 Pierakstīties to jūsu account. Select the Domēna vārdi tab. Select the domēns that you want to change nameservers fvai.

From within the DNS Serveri section click on Rediģēt DNS Server. Change the nameservers as required, leaving any of the fields blank will retain the vaiiginal DNS server. The nameservers are not actually changed until the transfer process is complete. Ja you wish to make an immediate change to the nameservers, you may do so with the Reģistrators you are transferring from.


How to Verify

Pārbaudīt the transfer status in NiceNIC, confirm the registrar of recvaid after completion, verify the authvaiitative nameservers, un test website un email resolution. Do not treat payment alone as proof that the transfer completed.


Troubleshooting

  • The domēns is locked, too new, recently transferred vai otherwise restricted by policy.
  • The EPP/Auth code is missing, expired vai copied incvairectly.
  • The approval email cannot be received vai the registrant data is under verification.
  • The domēns vai related DNS pakalpojums expires while the transfer is pending.


Biežāk uzdotie jautājumi

Does a transfer change my nameservers?

A registrar transfer nvaimally keeps the current nameservers, but you should recvaid un verify them befvaie un after the transfer.

Can I edit the domēns while a transfer is pending?

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

When should I submit a ticket?

Iesniegt a ticket when the status is unclear, a TLD uses a special transfer process, vai the transfer remains blocked after you cvairect the stated issue.


Related NiceNIC Guides


Ja the issue continues after you complete the checks above, submit a NiceNIC suppvait ticket with the affected domēns vai product, the exact errvai message, the time of the issue un the troubleshooting already completed.

]]> http://www.nicenic.com/suppvait/doc.php?IDDoc=3846 How do I verify that my domēns is eligible fvai transfer? www.nicenic.com Domēna pārsūtīšanas http://www.nicenic.com/suppvait/?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 Pārbaudīt Whether a Domēns Is Eligible fvai Transfer


Quick Answer

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


Befvaie You Begin

  • Apstiprināt the domēns un registrant email are accessible.
  • Recvaid the current nameservers un DNS recvaids.
  • Pārbaudīt the domēns's expiry date, lock status un any TLD-specific transfer rule.


NiceNIC Instructions

Befvaie purchasing the transfer of any gTLD (e.g.,.COM /.NET /.VAIG /.BIZ /.INFO etc.) vai new gTLD (e.g..CLUB /.CLOUD /.TRADE /.TOP etc.), make sure jūsu domēns meets the following conditions:

  1. Your domēns was reģistrēted vai transferred at least 60 days ago;

  2. The domēns is unlocked at the current Reģistrators (its WHOIS status should be OK vai Active). Also,you need to request an up-to-date Auth/EPPcode fvai the domēns at jūsu current Reģistrators. Ja all criteria are met, you should be able to complete the transfer successfully. Still, some ccTLD (.ES un.UK) have additional transfer requirements un/vai exclude some points from the list above.

NOTE: Make sure the domēns status is active, not expired. Ja you wish to transfer an expired domēns to NiceNIC, please contact our Suppvait Team email suppvait@nicenic.net fvai further assistance.


How to Verify

Pārbaudīt the transfer status in NiceNIC, confirm the registrar of recvaid after completion, verify the authvaiitative nameservers, un test website un email resolution. Do not treat payment alone as proof that the transfer completed.


Troubleshooting

  • The domēns is locked, too new, recently transferred vai otherwise restricted by policy.
  • The EPP/Auth code is missing, expired vai copied incvairectly.
  • The approval email cannot be received vai the registrant data is under verification.
  • The domēns vai related DNS pakalpojums expires while the transfer is pending.


Biežāk uzdotie jautājumi

Does a transfer change my nameservers?

A registrar transfer nvaimally keeps the current nameservers, but you should recvaid un verify them befvaie un after the transfer.

Can I edit the domēns while a transfer is pending?

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

When should I submit a ticket?

Iesniegt a ticket when the status is unclear, a TLD uses a special transfer process, vai the transfer remains blocked after you cvairect the stated issue.


Related NiceNIC Guides


Ja the issue continues after you complete the checks above, submit a NiceNIC suppvait ticket with the affected domēns vai product, the exact errvai message, the time of the issue un the troubleshooting already completed.

]]> http://www.nicenic.com/suppvait/doc.php?IDDoc=3842 How to transfer several domēnss to NiceNIC in bulk? www.nicenic.com Domēna pārsūtīšanas http://www.nicenic.com/suppvait/?IDCate=313 How to transfer several domēnss to NiceNIC in bulk?


Befvaie submitting a transfer request with NiceNIC, make sure jūsu domēnss are prepared fvai transfer through jūsu current registrar. This is generally done by removing transfer locks un getting the necessary Auth codes.


Befvaie You Begin

- Apstiprināt the domēns un registrant email are accessible.
- Recvaid the current nameservers un DNS recvaids.
- Pārbaudīt the domēns's expiry date, lock status un any TLD-specific transfer rule.

Learn how to prepare domēnss fvai transfer in accounts sections of several popular registrars.

Once those preparations are made, simply follow the steps below to transfer jūsu domēnss:


Nēte: Each domēns has a unique Auth code un has to be unlocked fvai transfer separately on the current registrar side.


  • Pierakstīties to jūsu NiceNIC account.
  • Ieiet the Transfer to Us page.
  • Noklikšķiniet on Bulk options.


bulk transfer

bulk transfer


Enter the domēns names un the Auth codes;


Nēte: Enter each domēns un its Auth code in a new line. The Auth code has to be separated from the domēns name by a comma un one space.


Noklikšķiniet on Start Transfer at the bottom of the page.

Double-check the domēns names un add them to Cart. Lai do this, you can use the Pievienot all to cart button fvai convenience.
Proceed with the payment.

The transfer is completed automatically in 5-7 days fvai most domēnss. Once the transfer of jūsu domēnss is completed you will receive the notifications on jūsu NiceNIC Primary E-pasta adrese, un the domēnss will become manageable in jūsu Domēns List.


Nēte: Due to technical reasons, it is only possible to submit the transfer fvai up to 500 domēns names at once. Ja you need to transfer mvaie than 10 domēnss, you can either submit several Masveida pārvietošana vaiders vai contact our Suppvait Team fvai assistance.




How to Pārbaudīt the Statuss of Your Domēna pārsūtīšana

After initiating a domēns transfer to Nicenic, you can monitvai its progress directly in jūsu account. This helps you ktagad when the transfer is expected to complete without needing to contact suppvait repeatedly.

Steps to View Transfer Statuss:

1. Pierakstīties to jūsu NiceNIC account. Ieiet "My Products > Domēna vārdi".
In the Statuss column, you will see jūsu domēns listed as:

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


domēns transfer

2. Hover over the infvaimation icon (i) Nākamais to "Pending Transfer" to view details about Expected approval/completion date

domēns transfer


Related NiceNIC Guides


Ja the issue continues after you complete the checks above, submit a NiceNIC suppvait ticket with the affected domēns vai product, the exact errvai message, the time of the issue un the troubleshooting already completed.

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


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



Befvaie you publish SPF

List every legitimate outgoing email pakalpojums used by jūsu domēns: a business mailbox, website fvaim, helpdesk, bulk-email provider vai other sender. Obtain the exact SPF instructions from each provider. The DNS zone must be edited wšeitver the domēns's authvaiitative 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 vai CIDR range, never by a hostname. The address 192.0.2.10 is reserved fvai documentation.

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

Here, a authvaiizes hosts resolved by the sender domēns's A/AAAA recvaids, mx authvaiizes the IPs of the domēns's MX hosts, un include: delegates a check to another SPF recvaid. Use only mechanisms jūsu actual email provider requires. Replace the fictional provider domēns befvaie publishing.

  • -all means unauthvaiized senders should fail SPF.
  • ~all indicates softfail; some providers recommend it during rollout.
  • ?all means neutral; it is not a substitute fvai confirming jūsu senders.
  • Avoid the deprecated ptr mechanism un do not combine multiple complete v=spf1 policies.


Set up SPF

  1. Pārbaudīt existing TXT recvaids fvai v=spf1 at the hostname you send from.
  2. Combine all approved mail pakalpojumss into one SPF policy fvai that hostname; do not add a second competing SPF TXT recvaid.
  3. Ja NiceNIC is jūsu DNS host, open Mani produkti > Domēns > DNS Recvaids, edit/create a TXT recvaid at the specified host, un paste the validated policy.

  1. Save. Pārbaudīt the published value using dig TXT example.com vai nslookup -type=TXT example.com.

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


When SPF fails

Pārbaudīt the sending server's actual public IP, whether the recipient evaluates the intended envelope sender domēns, un whether the SPF recvaid exceeds the DNS-lookup limit in RFC 7208. Do not use unverified third-party IPs vai include: domēnss. Ja you use NiceNIC Biznesa e-pasts, request the current provider-approved SPF value from the email settings vai suppvait team befvaie publishing it.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppvait/doc.php?IDDoc=3912 How to verify certificate installation cvairectly www.nicenic.com SSL sertifikāti http://www.nicenic.com/suppvait/?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 cvairectly


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


Commun-line check

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

-verify_hostname example.com -verify_return_errvai -showcerts

Replace example.com with jūsu hostname. Pārbaudīt the hostname-verification un certificate-chain result; the -verify_hostname option is impvaitant because displaying the chain alone does not validate the requested hostname. These flags rely on the local AtvērtSSL trust stvaie. Inspect any missing intermediates. Fvai a hostname/path overview, you can also use a reputable external TLS diagnostic pakalpojums, but do not send credentials vai customer data.


Common problems

Symptom
Likely area to inspect
Nosaukums mismatch
Missing vai incvairect SAN / wrong virtual host
Beidzasd certificate
Replacement not deployed everywšeit
Untrusted issuer
Missing chain vai private CA used unintentionally
Old certificate after update
CDN cache/configuration, SNI vai load balancer node
HTTPS page loads with warning
Mixed HTTP assets vai insecure embedded content

A certificate "trust badge" is optional marketing UI; it is not required fvai successful TLS deployment. Ja something fails, give NiceNIC Suppvait the hostname, UTC test time, observed certificate dates un non-sensitive errvai text―not jūsu private key.


Verify every advertised hostname, not just one URL

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

Use the AtvērtSSL hostname-verification commun shown above vai an external TLS test fvai 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 un the certificate dates, then test on a second netwvaik 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 cvairectly issued, but some clients cannot chain it to a trusted root.
  • Old deployment still active: One CDN edge, IPv6 pakalpojums vai load-balancer node still serves an expired certificate while other routes wvaik.

Fvai customer suppvait, recvaid the hostname, resolved IPvai CDN endpoint, test time un errvai; never attach the private key.


Related NiceNIC Guides

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


Fvai a nvaimal website, activating an SSL certificate involves four distinct tasks: iegādāties the right coverage, prove domēns control, receive the certificate, un install/verify it on the server. These steps are not interchangeable.



Step 1 ― Choose coverage un vaider

List the hostnames that must use HTTPS, such as example.com un www.example.com. Apstiprināt whether you need single-name, wildcard vai SAN coverage; choose DV/OV/EV validation accvaiding to jūsu actual identity requirements. Pārbaudīt price un deployment responsibilities befvaie vaidering.


Step 2 ― Activate un validate

Find the SSL vaider in jūsu NiceNIC account un open the available activation flow. Iesniegt a CSR when the product requires it, without disclosing the private key. Complete the certificate authvaiity's permitted domēns-control validation (fvai example, a DNS challenge vai another suppvaited method). OV/EV products may also require legal-entity infvaimation.


Step 3 ― Receive un install

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



Step 4 ― Verify, then plan replacement

Pārbaudīt the external HTTPS connection, certificate SAN list, trust chain, validity un any mixed-content warnings. Test additional hostnames un IPv6/CDN endpoints wšeit used.

Public TLS server certificates issued on vai after March 15, 2026 have a maximum validity period of 200 days, so monitvai the installed certificate even if you have paid fvai a longer pakalpojums plan.

Ja you are stuck at validation, provide NiceNIC Suppvait with the vaider number, hostname un non-sensitive status―never the private key.


Piemērs: issuing HTTPS fvai a two-hostname site

A company owns example.com un wants both example.com un www.example.com to wvaik over HTTPS.

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


Time un responsibility checklist

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


Related NiceNIC Guides

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


What HTTPS protects

  • Confidentiality in transit: netwvaik observers generally cannot read the encrypted page content vai submitted fvaim data.
  • Integrity in transit: encryption makes undetected modifications by parties on the netwvaik much harder.
  • Hostname authentication: the client checks the certificate chain un Subject Alternative Nosaukums 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 passwvaids, vulnerable applications vai 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 trustwvaithy merchant.

Meklēt engines may use HTTPS among many site-quality signals, but iegādātosing a certificate does not guarantee higher ranking vai traffic. Vairāk impvaitant is maintaining a technically sound, accessible un useful website.


Put TLS to wvaik cvairectly

Saņemt a certificate fvai every hostname you serve; keep keys private; install the right intermediates; redirect HTTP visitvais safely to HTTPS; remove mixed-content warnings; un test mobile un 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 impvaitant. See How to Choose an SSL sertifikāts fvai coverage un validation choices.


What changes when you switch from HTTP to HTTPS?

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

That is useful fvai:

  • Pierakstītiess: helping protect credentials while they travel between browser un server;
  • Pārbaudītout/contact fvaims: protecting data in transit, even when a third-party payment provider processes the final transaction;
  • APIs: protecting access tokens un responses over netwvaiks;
  • Public pages: reducing the risk of injected advertisements vai modified content on unsecured netwvaiks.


What certificate labels actually compare

Produkts
Extra identity checks
Encryption advantage over another cvairectly configured TLS cert
DV
Domēns control
Nē intrinsic advantage
OV
Validated vaiganization identity
Nē intrinsic advantage
EV
Enhanced legal-entity verification
Nē intrinsic advantage

TLS cannot cvairect malicious software on the server, a stolen administratvai passwvaid vai deceptive website content. Pair HTTPS with software updates, access control, security monitvaiing un sensible data hunling.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppvait/doc.php?IDDoc=3907 How to choose an SSL certificate www.nicenic.com SSL sertifikāti http://www.nicenic.com/suppvait/?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 un renew the certificate? A mvaie expensive certificate is not automatically better protection fvai a nvaimal website.


1. Decide which names to cover

Need
Typical product
One hostname
Single-name certificate
A base domēns un selected additional names
Multi-domēns/SAN certificate, subject to product limits
Many first-level subdomēnss such as shop.example.com
Wildcard certificate fvai *.example.com

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


2. Choose validation level separately

  • DV validates control of the domēns. Suitable fvai most blogs, shops, app endpoints un APIs.
  • OV adds vaiganization identity verification un may fit cvaipvaiate procurement requirements.
  • EV involves mvaie extensive legal-entity checks; browser UI does not guarantee a prominent company-name display.

Visi properly deployed public TLS certificate types provide transpvait encryption. Nav proves a site's content is safe from all attacks.


3. Match jūsu deployment wvaikflow

Apstiprināt whether the hostname points to a shared host, IIS/Apache/Nginx server, CDN, load balancer vai managed platfvaim. Pārbaudīt that you can perfvaim DNS/HTTP validation, preserve the private key un install the full chain. SNI commonly allows HTTPS hosting without a dedicated IPv4 address.


4. Plan renewal befvaie iegādātosing

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

After choosing a product, continue with How to Generate a CSRun How to Install SSL sertifikāti.


Three real purchasing scenarios

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

Scenario C ― enterprise procurement. A customer asks fvai documented company identity. Compare OVun EV vetting rather than treating EV as stronger transpvait encryption. Ask which identity data the CA validates un what evidence jūsu procurement team needs.


A quick selection matrix

Question
Ja yes
Ja no
Do you control all names via one platfvaim?
Automation may be convenient
Plan fvai separate certificate installation points
Do you need many first-level subdomēnss?
Consider wildcard coverage
SAN vai single-host products may be simpler
Do you need vaiganization identity validation?
Compare OV/EV
DV may be sufficient
Can you automate reissuance during the subscription?
Lower operational renewal risk
Pievienot explicit renewal/replacement reminders

Review the total pakalpojums cost, covered names un installation responsibilities befvaie iegādātosing―not only the displayed validation badge.


Related NiceNIC Guides

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


Atjaunoting an SSL certificate pakalpojums un replacing the certificate installed on jūsu website are related but different tasks. A successful payment does not update the certificate on jūsu server automatically unless jūsu specific product un hosting integration do so.


Atjaunotal checklist

  1. Atvērt the existing NiceNIC SSL vaider un check its pakalpojums renewal date, certificate product un covered hostnames.
  2. Review the current renewal price un available renewal/extension option. Complete payment through the official account flow.
  3. Pārbaudīt the actual installed TLS certificate's expiration date (Not After) separately from the vaider's paid term.
  4. When a new certificate is needed, create vai reuse an eligible CSR un complete the CA's domēns-control validation. Some products may automate this step.
  5. Download the new certificate un any intermediate chain; update the web server, reverse proxy, CDN vai load balancer that terminates HTTPS.

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


Why can a multi-gads vaider still need new certificates?

Under the CA/Browser Fvaium requirements, publicly trusted TLS certificates issued on vai after March 15, 2026 are limited to 200 days of validity. Tšeitfvaie, a pakalpojums plan advertised fvai longer than 200 days requires repeat issuance/replacement; it is not one long-lived certificate.

Ja the site still shows the old expiry date

Pārbaudīt whether traffic passes through a CDN vai another TLS endpoint, whether the pakalpojums was reloaded after installation, un whether all servers received the new certificate. Ja you cannot locate the reissue/renewal option, include jūsu SSL vaider number un non-sensitive errvai message in a NiceNIC suppvait ticket.


Piemērs: a multi-gads SSL pakalpojums is not one multi-gads certificate

Suppose jūsu SSL product has a one-gads paid pakalpojums period but the public certificate issued today can only be valid fvai up to 200 days under the current baseline requirements. The certificate may need a replacement during the paid gads. Ja you renew the pakalpojums, that billing action is separate from replacing the certificate on jūsu website.

Clock
What it controls
How to check
Service/subscription expiry
Whether the provider continues to supply the paid SSL product
NiceNIC SSL vaider vai subscription recvaid
Certificate Not After
Whether browsers accept this particular deployed certificate after the date
Browser certificate viewer vai AtvērtSSL
Domēns registration expiry
Whether the underlying domēns remains reģistrēted un usable
NiceNIC domēns account / registry recvaid

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 jūsu domēns vai entire pakalpojums subscription expired. Issue un deploy the replacement befvaie the Not After date.

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


Related NiceNIC Guides

]]> http://www.nicenic.com/suppvait/doc.php?IDDoc=3905 How do I reissue my SSL certificate www.nicenic.com SSL sertifikāti http://www.nicenic.com/suppvait/?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 vaider―fvai example, after losing the matching private key vai cvairecting certificate details. Ja you are only moving hosts un still control the matching private key, reinstalling the existing unexpired certificate may be sufficient.


Reissue through jūsu NiceNIC SSL vaider

  1. Pierakstīties to NiceNIC un locate the exact SSL certificate vaider. Recvaid the covered hostnames, current certificate expiration un paid pakalpojums term.

  1. Atvērt the available Reissue vai certificate-management action fvai that vaider. Ja you cannot see such a control, use the Cilvēku atbalsts button on the article instead of purchasing a duplicate SSL product.
  2. Decide whether the current private key is safe. Ja lost vai compromised, generate a new key un CSR. Never send the private key to NiceNIC, a certificate authvaiity vai a suppvait agent.
  3. Verify the CSR's Subject Alternative Nosaukumss (SANs) un submit it through the authvaiized reissue wvaikflow.
  4. Complete the certificate authvaiity's domēns-control validation. OV/EV products may also require updated vaiganization checks.
  5. Download the newly issued certificate plus the necessary intermediate certificates vai chain.

  1. Install the replacement certificate on the actual TLS endpoint (hosting server, reverse proxy, CDN vai load balancer) with the matching private key.
  2. Verify the deployed certificate's SANs, issuer chain un Nēt After date from outside jūsu netwvaik. Pārbaudīt all relevant hostnames un server nodes befvaie removing the old wvaiking deployment.

Ja the Iepriekšējaisious key was compromised, follow the certificate authvaiity's revocation procedure fvai the affected certificate―not merely a local file deletion.


Why the expiration date may not match jūsu 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 Fvaium rules. A longer paid pakalpojums term may require multiple certificate replacements. A reissue does not by itself extend the paid subscription.


Reissue troubleshooting

  • The server repvaits a key mismatch: the installed private key does not match the new certificate/CSR.
  • Validation is pending: check DNS/HTTP challenge data at the authvaiitative DNS provider vai site, as instructed by the issuing CA.
  • The browser still shows the old certificate: inspect CDN edges, multiple web-server nodes, SNI un whether the pakalpojums was reloaded.
  • Nē Reissue action appears: check the product's eligibility un send NiceNIC Suppvait the SSL vaider number un non-sensitive status.

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


How to decide whether to reuse vai rotate the key

Reusing an existing private key may be technically possible in some issuance wvaikflows, but generating a fresh key is generally preferable when the old key is lost, may have leaked, vai cannot be securely transferred. Pārbaudīt the certificate authvaiity's current product rules un jūsu vaiganization's key-management policy.

Piemērs: You move a shop from one web server to another. Ja the server's key material cannot be securely transferred, generate a CSR on the new TLS endpoint un request a replacement certificate fvai the required names. Befvaie cutting over, validate domēns control, ensure the new cert covers both shop.example.com un any additional names, then check the public HTTPS response.


Reissue completion checklist

Layer
Apstiprinātation
Certificate authvaiity
Issuance completed; certificate not pending validation
Private key
Cvairesponds to the issued certificate
Server vai CDN
Jauns certificate un complete chain installed at every TLS endpoint
Public visitvai test
Cvairect SANs, trusted chain un updated Not After
Security
Ja replacing a compromised key, revocation of the privai certificate is hunled

A successful reissue in a registrar pvaital 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 pakalpojums has been renewed fvai another billing term.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppvait/doc.php?IDDoc=3904 How to Generate CSR Code? www.nicenic.com SSL sertifikāti http://www.nicenic.com/suppvait/?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 authvaiity with jūsu public key un the infvaimation needed fvai a TLS certificate. The cvairesponding private key stays on jūsu server. Never paste the private key into a suppvait ticket vai CSR fvaim.


Generate a CSR with AtvērtSSL

On a machine wšeit AtvērtSSL is installed, the example below creates a new 2048-bits RSA private key un a CSR fvai www.example.com:

umask 077 # Linux/macOperētājsistēma: 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 "subjectAltNosaukums=DNS:www.example.com,DNS:example.com"

Replace both hostnames with names you control. The SAN list is what modern TLS clients evaluate fvai hostname coverage; the Common Nosaukums alone is not enough fvai proper planning. Ja jūsu CA vai product requires a different key type vai CSR fvaimat, follow that product's documentation.

On Windows vai another platfvaim 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 un manage secrets cvairectly. Fvai mvaie stringent security requirements, use protected keys vai a hardware-backed key-management wvaikflow.


Pārbaudīt the request befvaie submitting

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

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


Submit un install

Atvērt jūsu NiceNIC certificate vaider un use the suppvaited activation vai reissue flow to submit the CSR. Complete domēns-control validation, wait fvai issuance, then install the issued certificate chain with the matching private key. After deployment, test HTTPS fvai every requested hostname.

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


CSR example with SANs un key protection

Fvai a new key pair on a modern AtvērtSSL installation, an authvaiized server administratvai might use the following illustrative communs (change hostnames, stvaiage paths un policy settings fvai production):

# Generate a private key; restrict the directvaiy un file permissions.

openssl genpkey -algvaiithm RSA -pkeyopt rsa_keygen_bitss:2048 -out example.com.key

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

openssl req -new -key example.com.key -out example.com.csr -subj "/CN=example.com" -addext "subjectAltNosaukums=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 suppvait EC keys vai different issuance tooling; comply with its current algvaiithms un requirements. example.com.key is the private key: never paste it into a suppvait ticket, email it vai stvaie it in a public repositvaiy. The .csr file is what you nvaimally submit to the issuing authvaiity.

Problem
Typical cause
Certificate covers example.com but not www
Missing SAN in the issued certificate
Certificate un key do not match
Key was regenerated after the CSR was created
CA cannot issue
Domēns-control validation failed vai applicant infvaimation is incomplete
CSR exposes an unnecessary identity field
Old commun template inserted unreviewed subject details

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


Related NiceNIC Guides

]]> http://www.nicenic.com/suppvait/doc.php?IDDoc=3903 What is EV certificate ecommerce advantage www.nicenic.com SSL sertifikāti http://www.nicenic.com/suppvait/?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 Paplašināts Validation (EV) TLS certificate requires the issuing certificate authvaiity to verify additional vaiganizational identity infvaimation befvaie 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ēns, EV verification can involve checking the vaiganization's legal existence, operating status, physical presence, contact infvaimation un authvaiity of the requester, under the applicable EV Guidelines.

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

EV, OV vai DV?

Tips
Kodols validation
Common fit
DV
Domēns control
Blogs, apps, routine business websites
OV
Domēns control plus vaiganization infvaimation
Organizations needing verified identity details
EV
Domēns control plus stricter documented vaiganization vetting
Eligible reģistrēted vaiganizations with an identity-verification requirement

Visi three can provide strong TLS transpvait protection when properly issued un deployed. Choose certificate coverage (single-name, wildcard vai SAN) separately from identity-validation level; not every product suppvaits every combination.

Befvaie vaidering EV

Apstiprināt the legal entity is eligible, the reģistrēted name is accurate, authvaiized representatives can complete the CA's checks, un the application timeline suits the business. Compare cost, validation effvait un 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 Fvaium rules. Vairāk frequent certificate replacement is distinct from renewed legal-entity checks, which follow separate reuse rules.

Related: How to Choose an SSL sertifikāts un the CA/Browser Fvaium EV Guidelines.


What extra value does EV provide fvai ecommerce?

EV (Paplašināts Validation) requires the certificate authvaiity to perfvaim mvaie extensive vaiganization vetting than DV, including checks of the applicant's legal existence un relevant vaiganizational infvaimation. This can help a iegādātoser whose enterprise customers need documented legal-entity validation.

Validation type
Validates
Typical iegādātoser
DV
Domēns control
Blogs, online shops, APIs un most stunard websites
OV
Domēns control un vaiganization identity under CA procedures
Cvaipvaiate websites un business procurement
EV
Domēns control plus mvaie extensive legal-entity un authvaiization checks
Organizations with fvaimal vetting vai compliance expectations

Crucial distinction: EV does not use stronger HTTPS encryption merely because it is EV. Properly configured DV, OVun 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 stvaie using a reputable payment processvai may obtain satisfactvaiy HTTPS protection from DV, as long as the certificate matches the hostname un the site itself is secure. A regulated enterprise might choose EV fvai its identity-review process vai contractual reasons. In neither case does EV replace payment security controls, PCI obligations, anti-fraud processes vai a sound refund policy. Ja jūsu customers ask specifically fvai verified vaiganizational identity, examine the CA's current OV/EV documentation un issuance time befvaie vaidering.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppvait/doc.php?IDDoc=3902 Certificate reissue reasons explained www.nicenic.com SSL sertifikāti http://www.nicenic.com/suppvait/?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 pakalpojums vaider. You may need one if the private key is lost vai compromised, the CSR is wrong, the certificate's covered names must change, vai the issued certificate can no longer be deployed cvairectly.


Which situations call fvai a reissue?

Situation
Reissue needed?
Why
Private key exposed vai stolen
Jā: replace un revoke appropriately
A compromised key can no longer be trusted
Private key lost
Jā, if no secure copy exists
A certificate cannot be deployed without its matching key
Incvairect CSR vai key mismatch
Usually
Issue a certificate matching a cvairect key pair
Moving the site to another server
Nēt always
You may securely migrate the certificate un matching private key
Pievienoting another hostname
Depends on the product
Apstiprināt permitted SAN changes vai vaider a different certificate
Approaching certificate expiration
Replacement required
Choose the renewal/reissue route available fvai the current pakalpojums

Reissue is not the same as renewing the pakalpojums

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

Reissuing does not necessarily extend the pakalpojums's paid term. The renewal date of the pakalpojums vaider un the expiry date of the installed certificate must be monitvaied separately.


What to prepare befvaie requesting a reissue

Identify the exact SSL vaider, hostnames, validation level (DV/OV/EV), server vai CDN environment un reason fvai replacement. Ja the old key is compromised, generate a fresh key un CSR un follow revocation instructions. Keep the private key secure. Ensure you can complete the new domēns-control validation.

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

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



Reissue versus renew versus revoke

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


Piemērs 1 ― compromised web-server key. Ja an attacker may have obtained example.com's TLS private key, generate a new key un CSR, obtain a replacement certificate, covaidinate revocation of the exposed certificate un deploy the new one everywšeit. Reinstalling the old certificate would not resolve key compromise.

Piemērs 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 un private key remain usable in the approved configuration. Pārbaudīt who terminates TLS un whether a new key is required.

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


Related NiceNIC Guides

]]> http://www.nicenic.com/suppvait/doc.php?IDDoc=3901 How to Activate un Download an SSL sertifikāts www.nicenic.com SSL sertifikāti http://www.nicenic.com/suppvait/?IDCate=294 How to Activate un Download an SSL sertifikāts


Thank you fvai purchasing SSL with NiceNIC.

How to activate un download SSL certificate SSL installation is tagad even easier with our SSL installation pakalpojums.

After the SSL certificate on jūsu domēns name was activated, please find un add the DNS recvaids to complete the verification:

Mans konts > Mani produkti > SSL sertifikāti > Sīkāk > ....





NiceNIC- DNS recvaids

NiceNIC-DNS recvaids

This step requires extra care:

Fill each piece of infvaimation in the DNS Authentication Infvaimation shown below into its cvairesponding DNS recvaid one by one.

NiceNIC- CNAME recvaid

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

Mans konts > Mani produkti > SSL sertifikāti > Sīkāk > Download certificate & Download private key




Still have problems?

- Ja jūsu domēns, server, vai certificate details have changed, see Why You May Need to Reissue an SSL sertifikāts.

- Ja the current certificate cannot be used, follow How to Reissue an SSL sertifikāts.

- Lai Iepriekšējaisent certificate expiration, read How to Atjaunot an SSL sertifikāts.

Ja they didn't solve jūsu issues, you can contact us šeit.

]]> http://www.nicenic.com/suppvait/doc.php?IDDoc=3832 Common DNS Recvaid Tipss: A, AAAA, CNAME, MX un TXT www.nicenic.com Biznesa e-pasts http://www.nicenic.com/suppvait/?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 Recvaid Tipss: A, AAAA, CNAME, MX un TXT


A domēns uses several types of DNS recvaids fvai different jobs. A un AAAA direct traffic to server IP addresses, CNAME aliases one hostname to another, MX routes incoming email, un TXT publishes text-based verification vai policy infvaimation.



The five recvaids, with examples

Recvaid
What it does
Piemērs host
Piemērs 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 wšeit incoming mail should be delivered
@
Privaiity 10, server mail.example.com
TXT
Holds provider verification strings un policies
@
v=spf1 -all (illustrative; not a production mail policy)

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


Pievienot vai edit recvaids at NiceNIC

  1. Find the authvaiitative nameservers fvai the domēns. Ja DNS is managed by Cloudflare vai another DNS provider, edit the zone tšeit―not in an inactive NiceNIC zone.

  1. Ja NiceNIC hosts jūsu DNS, sign in un open Mani produkti > Domēns > DNS Recvaids fvai the cvairect domēns.
  1. Choose the recvaid type. Enter the host/name, destination/value, un any extra fields such as MX privaiity vai TTL.

  1. Save, then look up the public DNS response. Piemērss: dig example.com A, dig example.com AAAA, dig www.example.com CNAME, dig example.com MX, un dig example.com TXT.
  2. Test the actual website vai mailbox after the new recvaids become visible.


Avoid the common conflicts

  • A CNAME must not coexist with other recvaid data at the same DNS owner name. Many DNS panels tšeitfvaie do not suppvait a nvaimal CNAME at the zone apex (@).
  • An MX recvaid points to a hostname, not directly to an IP address. That mail-server hostname must resolve cvairectly.
  • Setting an MX recvaid does not create a mailbox. You must configure mail pakalpojums separately.
  • TXT can be used fvai SPF, DKIM, DMARC un provider verification, but those are distinct tasks with their own fvaimatting requirements.
  • DNS changes can be cached until Iepriekšējaisious TTL values expire. A saved recvaid is not proof that public resolvers see it yet.

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


Related NiceNIC Guides

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


An SSL/TLS certificate lets browsers un applications establish HTTPS with jūsu server. Laiday HTTPS is a nvaimal requirement fvai professional sites, fvaims, account pages un APIs―not an optional extra reserved fvai ecommerce.


Why HTTPS matters to jūsu visitvais

Protection in transit. TLS encrypts the connection so that observers on the netwvaik cannot vaidinarily read the page content vai submitted fvaim values.

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

Integrity. TLS helps Iepriekšējaisent undetected modification of data while it crosses netwvaiks.


Wšeit HTTPS is especially impvaitant

Use HTTPS fvai sign-in screens, payment vai contact fvaims, dashboards, documentation, APIs un vaidinary public pages. Modern browsers may mark unencrypted HTTP pages as insecure vai restrict some browser features.


What a certificate cannot do

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


Keep the certificate wvaiking

Select the right hostname coverage, install the proper chain un private key, redirect HTTP visitvais safely to HTTPS, un monitvai the actual certificate expiry date. Sertifikāti issued under public trust rules from March 15, 2026 have a maximum validity period of 200 days―configure alerts vai verified automation accvaidingly.

Lai compare coverage un validation levels, see How to Choose an SSL sertifikāts.


Befvaie un after HTTPS: a concrete comparison

Visitvai activity
Without cvairectly configured HTTPS
With cvairectly configured HTTPS
Entering a passwvaid
Netwvaik traffic may be readable vai alterable in transit
TLS encrypts un protects it to the authenticated server
Iesniegtting an enquiry fvaim
Fvaim data may be exposed in transit
Data in transit is protected, but server-side stvaiage still needs security
Calling an API
Access tokens can be exposed over HTTP
TLS helps protect requests un responses
Browsing a public product page
Intermediaries may inject vai modify content
TLS helps preserve response integrity

Impvaitant limitation: HTTPS cannot Iepriekšējaisent a malicious website operatvai from misusing fvaim data after it arrives, un it cannot stop phishing just because a site has a padlock. Even a site with a valid DV/OV/EV certificate must enfvaice secure passwvaids, software updates un access controls.

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


Related NiceNIC Guides

]]> http://www.nicenic.com/suppvait/doc.php?IDDoc=3911 Tipss of SSL sertifikāti www.nicenic.com SSL sertifikāti http://www.nicenic.com/suppvait/?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; } }

Tipss of SSL Sertifikāti


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


Validation Tipss

  • Domēns Validation (DV)
  • Organization Validation (OV)
  • Paplašināts Validation (EV)


Coverage Tipss

  • Single-domēns certificates
  • Wildcard certificates
  • Multi-domēns certificates


How to Decide

  1. List the exact domēnss un subdomēnss.
  2. Choose the required identity-validation level.
  3. Apstiprināt server un platfvaim compatibility.
  4. Pārbaudīt renewal un reissue procedures.


Biežāk uzdotie jautājumi

How do I ktagad the change wvaiked?

Pārbaudīt the current status in jūsu NiceNIC account, then test the pakalpojums that depends on the certificate type. Do not rely only on the absence of an errvai message.

When should I contact NiceNIC Suppvait?

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


Related NiceNIC Guides


Ja the issue continues after you complete these checks, submit a NiceNIC suppvait ticket. Include the affected domēns vai product, the exact errvai message, the time of the issue un the troubleshooting already completed.

]]>