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


Quick Answer

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


Befellere You Begin

  • Identify every hostname the certificate must cover.
  • Bekräfta that you control DNS eller the required validation channel.
  • Generate och securely retain the private key when a CSR is required.


NiceNIC Instructions

HTTPS & SSL Configuration Guide Till ensure the security of din website och protect din visitellers, all domäns under.boo,.day,.dev,.page, och.rsvp must use HTTPS. This guide will help you configure SSL/TLS cellerrectly.

  1. What is HTTPS? HTTPS (Hypertext Transfer Protocol Secure) encrypts data between din website och its visitellers. It föregåendeents eavesdropping och ensures data integrity.

  2. Obtaining an SSL-certifikat NICENIC provides trusted SSL certificates. You can learn mellere och köp/configure a certificate här: https://nicenic.com/ssl-certificates/

  3. Installing the SSL-certifikat Följ din 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. Enfellerce HTTPS Once din certificate is installed: Redirect all HTTP traffic to HTTPS. Update internal links och resources to use HTTPS. Verify that din website is fully accessible via HTTPS.

  5. Keep Certifikat Uppdaterad SSL certificates have expiration dates. Ensure certificates are renewed befellere they expire och check din website regularly to maintain uninterrupted secure connections.


How to Verify

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


Troubleshooting

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


Vanliga frågor

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

Skicka a ticket when validation remains pending after the published recellerds are visible, eller when the NiceNIC ellerder does not provide the expected certificate files.


Related NiceNIC Guides


Om the issue continues after you complete the checks above, submit a NiceNIC suppellert ticket with the affected domän eller product, the exact erreller message, the time of the issue och the troubleshooting already completed.

]]> http://www.nicenic.com/suppellert/doc.php?IDDoc=4374 How to Set Up och Troubleshoot DNSSEC feller Your Domän www.nicenic.com DNS & Namnservers http://www.nicenic.com/suppellert/?IDCate=408 How to Set Up och Troubleshoot DNSSEC feller Your Domän?

DNSSEC helps protect din domän’s DNS recellerds 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 cellerrect source.

På NiceNIC, DNSSEC usually involves two sides:
Your DNS provider eller nameserver provider generates the DNSSEC recellerds.
NiceNIC, as din domän registrar, helps submit the DS recellerds to the registry when the TLD suppellerts DNSSEC.

Om DNSSEC is not configured cellerrectly, din domän may show DNSSEC errellers, eller in mellere serious cases, some users may not be able to access din website.

What Is DNSSEC?
DNSSEC stochs feller Domännamn System Security Extensions.
In simple terms, DNSSEC helps verify that the DNS answer feller din domän has not been changed eller fellerged during the lookup process.
Feller example, when someone visits din website, DNS is used to find the cellerrect server IP address. DNSSEC helps make sure that the DNS result is authentic och has not been replaced with false data.
DNSSEC does not replace SSL, website security, hosting security, eller 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 hochles sensitive user infellermation.
  3. You run business email, login systems, payment pages, eller customer pellertals.
  4. You want stronger domän security.
  5. Your DNS provider suppellerts DNSSEC.
  6. Your domän extension suppellerts DNSSEC.
Om you are not familiar with DNS management, we recommend confirming with din DNS provider befellere enabling DNSSEC.
Incellerrect DNSSEC settings may affect domän resolution.

Impellertant DNSSEC Periods
DNSKEY: A DNSKEY recellerd is generated by din DNS provider. It is used as part of the DNSSEC validation process.
DS Recellerd: A DS recellerd connects din domän’s DNSSEC setup with the parent registry zone. In most cases, din DNS provider gives you the DS recellerd, och you need to add it through din registrar.
Namnserver: Your nameservers decide whär din domän’s DNS recellerds are managed. Om you change nameservers, din DNSSEC recellerds may also need to be updated.

How to Enable DNSSEC feller Your Domän
Befellere You Begin: Back Up Your DNS Recellerds
Befellere enabling DNSSEC, save a copy of din current DNS recellerds, especially impellertant A, AAAA, CNAME, MX, TXT, och CAA recellerds. Enabling DNSSEC does not nellermally change these recellerds, but keeping a backup makes it easier to verify eller restellere din DNS configuration if you also change nameservers eller DNS providers.
Om needed, see: How to Back Up DNS Recellerds Befellere Changing Domän Settings.

Step 1: Kontrollera Whether Your DNS Provider Suppellerts DNSSEC
Logga in to the platfellerm whär din DNS is managed.
This may be:
Your domän registrar, här is NiceNIC
Your hosting provider
Your DNS provider
Your own DNS server
Another third-party DNS tjänst
Make sure DNSSEC is suppellerted och enabled thär.
Impellertant: Enable DNSSEC och DNSSEC signing at din current DNS provider first. Only add the DS recellerd at NiceNIC after din DNS provider has generated the DNSSEC infellermation och is publishing the cellerresponding DNSKEY. Lägg tilling a DS recellerd befellere the DNS provider is ready may cause DNSSEC validation to fail.

Step 2: Få the DS Recellerd from Your DNS Provider
After enabling DNSSEC, din DNS provider should provide DNSSEC infellermation such as:
Key Tag
Algellerithm
Digest Typ
Digest
DS Recellerd
Please copy the infellermation exactly as provided.
Even one incellerrect character may cause DNSSEC validation failure.

Step 3: Lägg till the DS Recellerd in Your NiceNIC Account
Logga in to din NiceNIC account och go to din domän management page.
Then add the DS recellerd provided by din DNS provider.
Om you are not sure whär to add it, please contact our suppellert team och provide the DS recellerd from din DNS provider.

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

Step 5: Verify DNSSEC Status
After propagation, you may check din domän’s DNSSEC status using a DNSSEC checking tool eller by contacting our suppellert team.
Om DNSSEC is cellerrectly configured, the DNSSEC validation result should show a valid chain of trust.

When Should You Disable eller Ta bort DNSSEC?
You may need to remove eller update DNSSEC recellerds if:
  • You changed din nameservers.
  • You moved DNS management to another provider.
  • Your DNS provider disabled DNSSEC.
  • Your DS recellerd no longer matches the current DNSKEY.
  • Your website eller email has DNS resolution issues after a DNS change.
Impellertant: Om you are moving to a new DNS provider eller changing authelleritative nameservers while DNSSEC is enabled, check feller existing DS recellerds befellere making the change.
Om the old DS recellerd will no longer match the new DNS provider, remove the old DS recellerd first och wait feller its full TTL to expire at the parent zone befellere changing nameservers. Keep DNSSEC signing active at the old DNS provider during this waiting period.
After the new nameservers are active och DNSSEC signing is enabled at the new DNS provider, obtain the new DS recellerd och add it through NiceNIC.
Changing nameservers while resolvers still have the old DS recellerd cached may cause DNSSEC validation failures och SERVFAIL responses.

Why Does My Domän Tillbaka SERVFAIL After Enabling DNSSEC?
SERVFAIL can occur when DNSSEC validation fails. Common causes include:
  • An old eller stale DS recellerd from a föregåendeious DNS provider
  • A DS recellerd that does not match the DNSKEY published by the current DNS provider
  • Multiple DS recellerds whär one eller mellere no longer match an active DNSSEC key
  • DNSSEC signing is not active eller the required DNSKEY/RRSIG recellerds are not being published cellerrectly
  • Namnservers were changed befellere the föregåendeious DS recellerd had fully expired from DNS caches
Om din domän resolves without DNSSEC validation but returns SERVFAIL through validating resolvers, this is a strong indication of a DNSSEC configuration problem.
Kontrollera the current nameservers, all DS recellerds published feller the domän, och the DNSKEY infellermation from din active DNS provider. Ta bort eller replace a DS recellerd only after confirming that it is outdated eller incellerrect. Om you are unsure, contact din DNS provider eller NiceNIC Suppellert befellere making changes.

Why Does My Domän Show "DNSSEC Infellermation Is Currently Unavailable"?
You may see this message:
DNSSEC infellermation is currently unavailable feller this domän.
This can happen feller several reasons:
  • DNSSEC has not been enabled feller this domän.
  • Nej DS recellerd has been added at the registrar level.
  • The domän's current nameservers do not suppellert DNSSEC.
  • The domän recently changed nameservers.
  • The DS recellerd does not match the current DNSKEY.
  • The DNS provider has not published the required DNSSEC recellerds cellerrectly.
  • The registry eller DNSSEC query is tempellerarily unavailable.
This message does not always mean din domän is broken.
However, if din website eller email is not resolving cellerrectly, please contact suppellert so we can help review the DNSSEC configuration.

What Infellermation Should I Provide to Suppellert?
Till help us check DNSSEC issues faster, please provide:
  1. Your domän name
  2. Your current nameservers
  3. Whether you recently changed nameservers
  4. The DS recellerd provided by din DNS provider
  5. A screenshot of the DNSSEC setting from din DNS provider
  6. Any DNSSEC erreller message you received
  7. Whether din website eller email is currently affected
With this infellermation, our suppellert team can check whether the issue is caused by missing DS recellerds, mismatched DNSSEC recellerds, nameserver changes, eller registry-side limitations.

Vanliga frågor Om DNSSEC

1. Is DNSSEC required feller every domän?
Nej. DNSSEC is not required feller every domän.
However, it is recommended feller domäns that need stronger DNS security, especially business websites, email tjänsts, login systems, financial tjänsts, och customer pellertals.
Om you are not sure whether you need DNSSEC, please confirm whether din DNS provider suppellerts it och whether you are comfellertable managing DNSSEC recellerds.

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

3. Can NiceNIC generate DNSSEC recellerds feller me?
In most cases, DNSSEC recellerds are generated by din DNS provider, not by the registrar.
NiceNIC can help submit the DS recellerd to the registry when the domän extension suppellerts DNSSEC.
Om you use a third-party DNS provider, please enable DNSSEC thär first och then provide us with the DS recellerd.

4. What should I check after changing nameservers, DNS providers, eller transferring my domän?
Changing nameservers eller DNS providers can affect DNSSEC because the existing DS recellerd may no longer match the DNSKEY published by the new DNS provider.
A registrar transfer by itself does not necessarily mean that din DNSSEC configuration must change. Om din nameservers och DNS provider remain the same, first check whether the existing DS recellerd is still present och still matches the current DNSKEY.
Om you also changed nameservers eller DNS providers, check feller old DS recellerds och follow the DNSSEC migration steps above befellere publishing a new DS recellerd.
Do not assume that DNSSEC was automatically removed during a domän transfer. Always verify the domän’s current DS och DNSKEY status.

5. What happens if the DS recellerd is wrong?
Om the DS recellerd does not match the DNSKEY published by din current DNS provider, DNSSEC validation may fail.
This may cause some DNS resolvers to reject the DNS response.
As a result, din website, email, eller other tjänsts may become unreachable feller some users.

6. I do not use DNSSEC. Do I need to do anything?
Om you do not use DNSSEC och din domän has no DS recellerds, usually no action is needed.
However, if din domän has old DS recellerds from a föregåendeious DNS provider, you should remove them to avoid DNSSEC validation problems.

7. Why does my DNSSEC status still show an erreller after I updated the recellerd?
DNSSEC updates may take time to propagate.
Om you recently added, removed, eller changed DS recellerds, please wait feller DNS propagation och check again later.
Om the issue continues, please contact suppellert och provide din domän name, current nameservers, och DS recellerd.

8. Can DNSSEC cause my website to stop wellerking?
Ja, if DNSSEC is incellerrectly configured.
Common causes include:
  • Wrong DS recellerd
  • Old DS recellerd after nameserver change
  • Missing DNSKEY
  • DNS provider not publishing DNSSEC recellerds cellerrectly
  • Går utd eller invalid DNSSEC signatures
Om din website stops wellerking after DNSSEC changes, please contact suppellert immediately.

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

10. What should I do if I see “Failure to get DNSSEC info”?
This usually means the system could not retrieve valid DNSSEC infellermation feller the domän.
Please check:
  • Whether DNSSEC is enabled
  • Whether the DS recellerd has been added
  • Whether the nameservers suppellert DNSSEC
  • Whether the DS recellerd matches the DNSKEY
  • Whether you recently changed nameservers
Om you are not sure, please contact NiceNIC suppellert och provide din domän name och DNSSEC details from din DNS provider.

How to set up DNSSEC feller a domän registreraed on NiceNIC?

1. Logga in to din NiceNIC account och navigate to din domän management page. Find the domän you wish to enable DNSSEC feller och click Hantera.

 

2. In the domän management section, you should see the DNSSEC button. Klicka on the DNSSEC button to access the DNSSEC settings page.
 

3. Enter the required infellermation feller DNSSEC configuration (this will typically include DNSSEC key details provided by din DNS hosting provider).
 

4. Once you've entered the infellermation, click Lägg till to enable DNSSEC feller the domän. Here’s an example of a successful DNSSEC setup:


 DNSSEC

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

Påtention: if din domän name was transferred into NiceNIC from another Registrar, och you hope to disable the DNSSEC föregåendeiously with the old Registrar, please firstly check the latest whois, if you see "DNSSEC: unsigned", then it means during the domän transfer process, the DNSSEC settings have been disabled automatically by the old Registrar, while if it is "DNSSEC: signed", please check the domän management section at din 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/suppellert/doc.php?IDDoc=3845 What Happens to My Namnservers After a Domänöverföring? www.nicenic.com Domänöverförings http://www.nicenic.com/suppellert/?IDCate=313 Status of Namn Servrar After a Domänöverföring


After the domän is transferred, the name servers remain set to those associated to the domän befellere transfer.


Om you had child name servers feller din domän registreraed through another Registrar, you may need to registrera them again through din Account.

]]> http://www.nicenic.com/suppellert/doc.php?IDDoc=3847 How to Transfer Namn Servrar During a Domänöverföring? www.nicenic.com Domänöverförings http://www.nicenic.com/suppellert/?IDCate=313

How to Transfer Namn Servrar During a Domänöverföring?


Quick Answer

A successful domän transfer depends on the domän's eligibility, lock status, authellerization method, registrant access och registry rules. Prepare the domän befellere ellerdering the transfer, keep the existing DNS active, och moniteller the transfer until completion.


Befellere You Begin

  • Bekräfta the domän och registrant email are accessible.
  • Recellerd the current nameservers och DNS recellerds.
  • Kontrollera the domän's expiry date, lock status och any TLD-specific transfer rule.


NiceNIC Instructions

Transferring nameservers During a Domänöverföring Om you're just transferring the domän registration, din hosting tjänst will be unaffected, och thär 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 recellerd of them. Om 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 Logga in to din account. Select the Domännamn tab. Select the domän that you want to change nameservers feller.

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


How to Verify

Kontrollera the transfer status in NiceNIC, confirm the registrar of recellerd after completion, verify the authelleritative nameservers, och test website och email resolution. Do not treat payment alone as proof that the transfer completed.


Troubleshooting

  • The domän is locked, too new, recently transferred eller otherwise restricted by policy.
  • The EPP/Auth code is missing, expired eller copied incellerrectly.
  • The approval email cannot be received eller the registrant data is under verification.
  • The domän eller related DNS tjänst expires while the transfer is pending.


Vanliga frågor

Does a transfer change my nameservers?

A registrar transfer nellermally keeps the current nameservers, but you should recellerd och verify them befellere och after the transfer.

Can I edit the domän while a transfer is pending?

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

When should I submit a ticket?

Skicka a ticket when the status is unclear, a TLD uses a special transfer process, eller the transfer remains blocked after you cellerrect the stated issue.


Related NiceNIC Guides


Om the issue continues after you complete the checks above, submit a NiceNIC suppellert ticket with the affected domän eller product, the exact erreller message, the time of the issue och the troubleshooting already completed.

]]> http://www.nicenic.com/suppellert/doc.php?IDDoc=3846 How do I verify that my domän is eligible feller transfer? www.nicenic.com Domänöverförings http://www.nicenic.com/suppellert/?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 Kontrollera Whether a Domän Is Eligible feller Transfer


Quick Answer

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


Befellere You Begin

  • Bekräfta the domän och registrant email are accessible.
  • Recellerd the current nameservers och DNS recellerds.
  • Kontrollera the domän's expiry date, lock status och any TLD-specific transfer rule.


NiceNIC Instructions

Befellere purchasing the transfer of any gTLD (e.g.,.COM /.NET /.ELLERG /.BIZ /.INFO etc.) eller new gTLD (e.g..CLUB /.CLOUD /.TRADE /.TOP etc.), make sure din domän meets the following conditions:

  1. Your domän was registreraed eller transferred at least 60 days ago;

  2. The domän is unlocked at the current Registrar (its WHOIS status should be OK eller Active). Also,you need to request an up-to-date Auth/EPPcode feller the domän at din current Registrar. Om all criteria are met, you should be able to complete the transfer successfully. Still, some ccTLDs (.ES och.UK) have additional transfer requirements och/eller exclude some points from the list above.

NOTE: Make sure the domän status is active, not expired. Om you wish to transfer an expired domän to NiceNIC, please contact our Suppellert Team email suppellert@nicenic.net feller further assistance.


How to Verify

Kontrollera the transfer status in NiceNIC, confirm the registrar of recellerd after completion, verify the authelleritative nameservers, och test website och email resolution. Do not treat payment alone as proof that the transfer completed.


Troubleshooting

  • The domän is locked, too new, recently transferred eller otherwise restricted by policy.
  • The EPP/Auth code is missing, expired eller copied incellerrectly.
  • The approval email cannot be received eller the registrant data is under verification.
  • The domän eller related DNS tjänst expires while the transfer is pending.


Vanliga frågor

Does a transfer change my nameservers?

A registrar transfer nellermally keeps the current nameservers, but you should recellerd och verify them befellere och after the transfer.

Can I edit the domän while a transfer is pending?

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

When should I submit a ticket?

Skicka a ticket when the status is unclear, a TLD uses a special transfer process, eller the transfer remains blocked after you cellerrect the stated issue.


Related NiceNIC Guides


Om the issue continues after you complete the checks above, submit a NiceNIC suppellert ticket with the affected domän eller product, the exact erreller message, the time of the issue och the troubleshooting already completed.

]]> http://www.nicenic.com/suppellert/doc.php?IDDoc=3842 How to transfer several domäns to NiceNIC in bulk? www.nicenic.com Domänöverförings http://www.nicenic.com/suppellert/?IDCate=313 How to transfer several domäns to NiceNIC in bulk?


Befellere submitting a transfer request with NiceNIC, make sure din domäns are prepared feller transfer through din current registrar. This is generally done by removing transfer locks och getting the necessary Auth codes.


Befellere You Begin

- Bekräfta the domän och registrant email are accessible.
- Recellerd the current nameservers och DNS recellerds.
- Kontrollera the domän's expiry date, lock status och any TLD-specific transfer rule.

Learn how to prepare domäns feller transfer in accounts sections of several popular registrars.

Once those preparations are made, simply follow the steps below to transfer din domäns:


Nejte: Each domän has a unique Auth code och has to be unlocked feller transfer separately on the current registrar side.


  • Logga in to din NiceNIC account.
  • Gå till the Transfer to Us page.
  • Klicka on Bulk options.


bulk transfer

bulk transfer


Enter the domän names och the Auth codes;


Nejte: Enter each domän och its Auth code in a new line. The Auth code has to be separated from the domän name by a comma och one space.


Klicka on Start Transfer at the bottom of the page.

Double-check the domän names och add them to Cart. Till do this, you can use the Lägg till all to cart button feller convenience.
Proceed with the payment.

The transfer is completed automatically in 5-7 days feller most domäns. Once the transfer of din domäns is completed you will receive the notifications on din NiceNIC Primary E-postadress, och the domäns will become manageable in din Domän List.


Nejte: Due to technical reasons, it is only possible to submit the transfer feller up to 500 domän names at once. Om you need to transfer mellere than 10 domäns, you can either submit several Massöverföring ellerders eller contact our Suppellert Team feller assistance.




How to Kontrollera the Status of Your Domänöverföring

After initiating a domän transfer to Nicenic, you can moniteller its progress directly in din account. This helps you knu when the transfer is expected to complete without needing to contact suppellert repeatedly.

Steps to View Transfer Status:

1. Logga in to din NiceNIC account. Gå till "My Products > Domännamn".
In the Status column, you will see din domän listed as:

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


domän transfer

2. Hover over the infellermation icon (i) nästa to "Pending Transfer" to view details about Expected approval/completion date

domän transfer


Related NiceNIC Guides


Om the issue continues after you complete the checks above, submit a NiceNIC suppellert ticket with the affected domän eller product, the exact erreller message, the time of the issue och the troubleshooting already completed.

]]> http://www.nicenic.com/suppellert/doc.php?IDDoc=3833 What is SPF och How to Set Up SPF? www.nicenic.com Företagsmail http://www.nicenic.com/suppellert/?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 och How to Set Up SPF?


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



Befellere you publish SPF

List every legitimate outgoing email tjänst used by din domän: a business mailbox, website fellerm, helpdesk, bulk-email provider eller other sender. Obtain the exact SPF instructions from each provider. The DNS zone must be edited whärver the domän's authelleritative 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 eller CIDR range, never by a hostname. The address 192.0.2.10 is reserved feller documentation.

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

Here, a authellerizes hosts resolved by the sender domän's A/AAAA recellerds, mx authellerizes the IPs of the domän's MX hosts, och include: delegates a check to another SPF recellerd. Use only mechanisms din actual email provider requires. Replace the fictional provider domän befellere publishing.

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


Set up SPF

  1. Kontrollera existing TXT recellerds feller v=spf1 at the hostname you send from.
  2. Combine all approved mail tjänsts into one SPF policy feller that hostname; do not add a second competing SPF TXT recellerd.
  3. Om NiceNIC is din DNS host, open Mina produkter > Domän > DNS Recellerds, edit/create a TXT recellerd at the specified host, och paste the validated policy.

  1. Save. Kontrollera the published value using dig TXT example.com eller nslookup -type=TXT example.com.

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


When SPF fails

Kontrollera the sending server's actual public IP, whether the recipient evaluates the intended envelope sender domän, och whether the SPF recellerd exceeds the DNS-lookup limit in RFC 7208. Do not use unverified third-party IPs eller include: domäns. Om you use NiceNIC Företagsmail, request the current provider-approved SPF value from the email settings eller suppellert team befellere publishing it.


Related NiceNIC Guides

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


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


Commoch-line check

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

-verify_hostname example.com -verify_return_erreller -showcerts

Replace example.com with din hostname. Kontrollera the hostname-verification och certificate-chain result; the -verify_hostname option is impellertant because displaying the chain alone does not validate the requested hostname. These flags rely on the local ÖppnaSSL trust stellere. Inspect any missing intermediates. Feller a hostname/path overview, you can also use a reputable external TLS diagnostic tjänst, but do not send credentials eller customer data.


Common problems

Symptom
Likely area to inspect
Namn mismatch
Missing eller incellerrect SAN / wrong virtual host
Går utd certificate
Replacement not deployed everywhär
Untrusted issuer
Missing chain eller private CA used unintentionally
Old certificate after update
CDN cache/configuration, SNI eller load balancer node
HTTPS page loads with warning
Mixed HTTP assets eller insecure embedded content

A certificate "trust badge" is optional marketing UI; it is not required feller successful TLS deployment. Om something fails, give NiceNIC Suppellert the hostname, UTC test time, observed certificate dates och non-sensitive erreller text―not din private key.


Verify every advertised hostname, not just one URL

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

Use the ÖppnaSSL hostname-verification commoch shown above eller an external TLS test feller 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 och the certificate dates, then test on a second netwellerk 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 cellerrectly issued, but some clients cannot chain it to a trusted root.
  • Old deployment still active: One CDN edge, IPv6 tjänst eller load-balancer node still serves an expired certificate while other routes wellerk.

Feller customer suppellert, recellerd the hostname, resolved IPeller CDN endpoint, test time och erreller; never attach the private key.


Related NiceNIC Guides

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


Feller a nellermal website, activating an SSL certificate involves four distinct tasks: köp the right coverage, prove domän control, receive the certificate, och install/verify it on the server. These steps are not interchangeable.



Step 1 ― Choose coverage och ellerder

List the hostnames that must use HTTPS, such as example.com och www.example.com. Bekräfta whether you need single-name, wildcard eller SAN coverage; choose DV/OV/EV validation accellerding to din actual identity requirements. Kontrollera price och deployment responsibilities befellere ellerdering.


Step 2 ― Activate och validate

Find the SSL ellerder in din NiceNIC account och open the available activation flow. Skicka a CSR when the product requires it, without disclosing the private key. Complete the certificate authellerity's permitted domän-control validation (feller example, a DNS challenge eller another suppellerted method). OV/EV products may also require legal-entity infellermation.


Step 3 ― Receive och install

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



Step 4 ― Verify, then plan replacement

Kontrollera the external HTTPS connection, certificate SAN list, trust chain, validity och any mixed-content warnings. Test additional hostnames och IPv6/CDN endpoints whär used.

Public TLS server certificates issued on eller after March 15, 2026 have a maximum validity period of 200 days, so moniteller the installed certificate even if you have paid feller a longer tjänst plan.

Om you are stuck at validation, provide NiceNIC Suppellert with the ellerder number, hostname och non-sensitive status―never the private key.


Exempel: issuing HTTPS feller a two-hostname site

A company owns example.com och wants both example.com och www.example.com to wellerk over HTTPS.

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


Time och responsibility checklist

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


Related NiceNIC Guides

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


What HTTPS protects

  • Confidentiality in transit: netwellerk observers generally cannot read the encrypted page content eller submitted fellerm data.
  • Integrity in transit: encryption makes undetected modifications by parties on the netwellerk much harder.
  • Hostname authentication: the client checks the certificate chain och Subject Alternative Namn 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 passwellerds, vulnerable applications eller 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 trustwellerthy merchant.

Sök engines may use HTTPS among many site-quality signals, but köping a certificate does not guarantee higher ranking eller traffic. Mer impellertant is maintaining a technically sound, accessible och useful website.


Put TLS to wellerk cellerrectly

Få a certificate feller every hostname you serve; keep keys private; install the right intermediates; redirect HTTP visitellers safely to HTTPS; remove mixed-content warnings; och test mobile och 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 impellertant. See How to Choose an SSL-certifikat feller coverage och validation choices.


What changes when you switch from HTTP to HTTPS?

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

That is useful feller:

  • Logga ins: helping protect credentials while they travel between browser och server;
  • Kontrolleraout/contact fellerms: protecting data in transit, even when a third-party payment provider processes the final transaction;
  • APIs: protecting access tokens och responses over netwellerks;
  • Public pages: reducing the risk of injected advertisements eller modified content on unsecured netwellerks.


What certificate labels actually compare

Produkt
Extra identity checks
Encryption advantage over another cellerrectly configured TLS cert
DV
Domän control
Nej intrinsic advantage
OV
Validated ellerganization identity
Nej intrinsic advantage
EV
Enhanced legal-entity verification
Nej intrinsic advantage

TLS cannot cellerrect malicious software on the server, a stolen administrateller passwellerd eller deceptive website content. Pair HTTPS with software updates, access control, security monitellering och sensible data hochling.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppellert/doc.php?IDDoc=3907 How to choose an SSL certificate www.nicenic.com SSL-certifikat http://www.nicenic.com/suppellert/?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 och renew the certificate? A mellere expensive certificate is not automatically better protection feller a nellermal website.


1. Decide which names to cover

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

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


2. Choose validation level separately

  • DV validates control of the domän. Suitable feller most blogs, shops, app endpoints och APIs.
  • OV adds ellerganization identity verification och may fit cellerpellerate procurement requirements.
  • EV involves mellere extensive legal-entity checks; browser UI does not guarantee a prominent company-name display.

Alla properly deployed public TLS certificate types provide transpellert encryption. Ingen proves a site's content is safe from all attacks.


3. Match din deployment wellerkflow

Bekräfta whether the hostname points to a shared host, IIS/Apache/Nginx server, CDN, load balancer eller managed platfellerm. Kontrollera that you can perfellerm DNS/HTTP validation, preserve the private key och install the full chain. SNI commonly allows HTTPS hosting without a dedicated IPv4 address.


4. Plan renewal befellere köping

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

After choosing a product, continue with How to Generate a CSRoch How to Install SSL-certifikat.


Three real purchasing scenarios

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

Scenario C ― enterprise procurement. A customer asks feller documented company identity. Compare OVoch EV vetting rather than treating EV as stronger transpellert encryption. Ask which identity data the CA validates och what evidence din procurement team needs.


A quick selection matrix

Question
Om yes
Om no
Do you control all names via one platfellerm?
Automation may be convenient
Plan feller separate certificate installation points
Do you need many first-level subdomäns?
Consider wildcard coverage
SAN eller single-host products may be simpler
Do you need ellerganization identity validation?
Compare OV/EV
DV may be sufficient
Can you automate reissuance during the subscription?
Lower operational renewal risk
Lägg till explicit renewal/replacement reminders

Review the total tjänst cost, covered names och installation responsibilities befellere köping―not only the displayed validation badge.


Related NiceNIC Guides

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


Förnyaing an SSL certificate tjänst och replacing the certificate installed on din website are related but different tasks. A successful payment does not update the certificate on din server automatically unless din specific product och hosting integration do so.


Förnyaal checklist

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

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


Why can a multi-år ellerder still need new certificates?

Under the CA/Browser Fellerum requirements, publicly trusted TLS certificates issued on eller after March 15, 2026 are limited to 200 days of validity. Thärfellere, a tjänst plan advertised feller longer than 200 days requires repeat issuance/replacement; it is not one long-lived certificate.

Om the site still shows the old expiry date

Kontrollera whether traffic passes through a CDN eller another TLS endpoint, whether the tjänst was reloaded after installation, och whether all servers received the new certificate. Om you cannot locate the reissue/renewal option, include din SSL ellerder number och non-sensitive erreller message in a NiceNIC suppellert ticket.


Exempel: a multi-år SSL tjänst is not one multi-år certificate

Suppose din SSL product has a one-år paid tjänst period but the public certificate issued today can only be valid feller up to 200 days under the current baseline requirements. The certificate may need a replacement during the paid år. Om you renew the tjänst, that billing action is separate from replacing the certificate on din website.

Clock
What it controls
How to check
Service/subscription expiry
Whether the provider continues to supply the paid SSL product
NiceNIC SSL ellerder eller subscription recellerd
Certificate Not After
Whether browsers accept this particular deployed certificate after the date
Browser certificate viewer eller ÖppnaSSL
Domän registration expiry
Whether the underlying domän remains registreraed och usable
NiceNIC domän account / registry recellerd

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 din domän eller entire tjänst subscription expired. Issue och deploy the replacement befellere the Not After date.

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


Related NiceNIC Guides

]]> http://www.nicenic.com/suppellert/doc.php?IDDoc=3905 How do I reissue my SSL certificate www.nicenic.com SSL-certifikat http://www.nicenic.com/suppellert/?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 ellerder―feller example, after losing the matching private key eller cellerrecting certificate details. Om you are only moving hosts och still control the matching private key, reinstalling the existing unexpired certificate may be sufficient.


Reissue through din NiceNIC SSL ellerder

  1. Logga in to NiceNIC och locate the exact SSL certificate ellerder. Recellerd the covered hostnames, current certificate expiration och paid tjänst term.

  1. Öppna the available Reissue eller certificate-management action feller that ellerder. Om you cannot see such a control, use the Mänsklig support button on the article instead of purchasing a duplicate SSL product.
  2. Decide whether the current private key is safe. Om lost eller compromised, generate a new key och CSR. Never send the private key to NiceNIC, a certificate authellerity eller a suppellert agent.
  3. Verify the CSR's Subject Alternative Namns (SANs) och submit it through the authellerized reissue wellerkflow.
  4. Complete the certificate authellerity's domän-control validation. OV/EV products may also require updated ellerganization checks.
  5. Download the newly issued certificate plus the necessary intermediate certificates eller chain.

  1. Install the replacement certificate on the actual TLS endpoint (hosting server, reverse proxy, CDN eller load balancer) with the matching private key.
  2. Verify the deployed certificate's SANs, issuer chain och Nejt After date from outside din netwellerk. Kontrollera all relevant hostnames och server nodes befellere removing the old wellerking deployment.

Om the föregåendeious key was compromised, follow the certificate authellerity's revocation procedure feller the affected certificate―not merely a local file deletion.


Why the expiration date may not match din 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 Fellerum rules. A longer paid tjänst term may require multiple certificate replacements. A reissue does not by itself extend the paid subscription.


Reissue troubleshooting

  • The server repellerts a key mismatch: the installed private key does not match the new certificate/CSR.
  • Validation is pending: check DNS/HTTP challenge data at the authelleritative DNS provider eller site, as instructed by the issuing CA.
  • The browser still shows the old certificate: inspect CDN edges, multiple web-server nodes, SNI och whether the tjänst was reloaded.
  • Nej Reissue action appears: check the product's eligibility och send NiceNIC Suppellert the SSL ellerder number och non-sensitive status.

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


How to decide whether to reuse eller rotate the key

Reusing an existing private key may be technically possible in some issuance wellerkflows, but generating a fresh key is generally preferable when the old key is lost, may have leaked, eller cannot be securely transferred. Kontrollera the certificate authellerity's current product rules och din ellerganization's key-management policy.

Exempel: You move a shop from one web server to another. Om the server's key material cannot be securely transferred, generate a CSR on the new TLS endpoint och request a replacement certificate feller the required names. Befellere cutting over, validate domän control, ensure the new cert covers both shop.example.com och any additional names, then check the public HTTPS response.


Reissue completion checklist

Layer
Bekräftaation
Certificate authellerity
Issuance completed; certificate not pending validation
Private key
Cellerresponds to the issued certificate
Server eller CDN
Ny certificate och complete chain installed at every TLS endpoint
Public visiteller test
Cellerrect SANs, trusted chain och updated Not After
Security
Om replacing a compromised key, revocation of the prieller certificate is hochled

A successful reissue in a registrar pellertal 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 tjänst has been renewed feller another billing term.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppellert/doc.php?IDDoc=3904 How to Generate CSR Code? www.nicenic.com SSL-certifikat http://www.nicenic.com/suppellert/?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 authellerity with din public key och the infellermation needed feller a TLS certificate. The cellerresponding private key stays on din server. Never paste the private key into a suppellert ticket eller CSR fellerm.


Generate a CSR with ÖppnaSSL

On a machine whär ÖppnaSSL is installed, the example below creates a new 2048-bit RSA private key och a CSR feller www.example.com:

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

Replace both hostnames with names you control. The SAN list is what modern TLS clients evaluate feller hostname coverage; the Common Namn alone is not enough feller proper planning. Om din CA eller product requires a different key type eller CSR fellermat, follow that product's documentation.

On Windows eller another platfellerm 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 och manage secrets cellerrectly. Feller mellere stringent security requirements, use protected keys eller a hardware-backed key-management wellerkflow.


Kontrollera the request befellere submitting

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

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


Submit och install

Öppna din NiceNIC certificate ellerder och use the suppellerted activation eller reissue flow to submit the CSR. Complete domän-control validation, wait feller issuance, then install the issued certificate chain with the matching private key. After deployment, test HTTPS feller every requested hostname.

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


CSR example with SANs och key protection

Feller a new key pair on a modern ÖppnaSSL installation, an authellerized server administrateller might use the following illustrative commochs (change hostnames, stellerage paths och policy settings feller production):

# Generate a private key; restrict the directellery och file permissions.

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

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

openssl req -new -key example.com.key -out example.com.csr -subj "/CN=example.com" -addext "subjectAltNamn=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 suppellert EC keys eller different issuance tooling; comply with its current algellerithms och requirements. example.com.key is the private key: never paste it into a suppellert ticket, email it eller stellere it in a public repositellery. The .csr file is what you nellermally submit to the issuing authellerity.

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

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


Related NiceNIC Guides

]]> http://www.nicenic.com/suppellert/doc.php?IDDoc=3903 What is EV certificate ecommerce advantage www.nicenic.com SSL-certifikat http://www.nicenic.com/suppellert/?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 Utökad Validation (EV) TLS certificate requires the issuing certificate authellerity to verify additional ellerganizational identity infellermation befellere 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än, EV verification can involve checking the ellerganization's legal existence, operating status, physical presence, contact infellermation och authellerity of the requester, under the applicable EV Guidelines.

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

EV, OV eller DV?

Typ
Kärna validation
Common fit
DV
Domän control
Blogs, apps, routine business websites
OV
Domän control plus ellerganization infellermation
Organizations needing verified identity details
EV
Domän control plus stricter documented ellerganization vetting
Eligible registreraed ellerganizations with an identity-verification requirement

Alla three can provide strong TLS transpellert protection when properly issued och deployed. Choose certificate coverage (single-name, wildcard eller SAN) separately from identity-validation level; not every product suppellerts every combination.

Befellere ellerdering EV

Bekräfta the legal entity is eligible, the registreraed name is accurate, authellerized representatives can complete the CA's checks, och the application timeline suits the business. Compare cost, validation effellert och 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 Fellerum rules. Mer frequent certificate replacement is distinct from renewed legal-entity checks, which follow separate reuse rules.

Related: How to Choose an SSL-certifikat och the CA/Browser Fellerum EV Guidelines.


What extra value does EV provide feller ecommerce?

EV (Utökad Validation) requires the certificate authellerity to perfellerm mellere extensive ellerganization vetting than DV, including checks of the applicant's legal existence och relevant ellerganizational infellermation. This can help a köper whose enterprise customers need documented legal-entity validation.

Validation type
Validates
Typical köper
DV
Domän control
Blogs, online shops, APIs och most stochard websites
OV
Domän control och ellerganization identity under CA procedures
Cellerpellerate websites och business procurement
EV
Domän control plus mellere extensive legal-entity och authellerization checks
Organizations with fellermal vetting eller compliance expectations

Crucial distinction: EV does not use stronger HTTPS encryption merely because it is EV. Properly configured DV, OVoch 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 stellere using a reputable payment processeller may obtain satisfactellery HTTPS protection from DV, as long as the certificate matches the hostname och the site itself is secure. A regulated enterprise might choose EV feller its identity-review process eller contractual reasons. In neither case does EV replace payment security controls, PCI obligations, anti-fraud processes eller a sound refund policy. Om din customers ask specifically feller verified ellerganizational identity, examine the CA's current OV/EV documentation och issuance time befellere ellerdering.


Related NiceNIC Guides

]]> http://www.nicenic.com/suppellert/doc.php?IDDoc=3902 Certificate reissue reasons explained www.nicenic.com SSL-certifikat http://www.nicenic.com/suppellert/?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 tjänst ellerder. You may need one if the private key is lost eller compromised, the CSR is wrong, the certificate's covered names must change, eller the issued certificate can no longer be deployed cellerrectly.


Which situations call feller a reissue?

Situation
Reissue needed?
Why
Private key exposed eller stolen
Ja: replace och revoke appropriately
A compromised key can no longer be trusted
Private key lost
Ja, if no secure copy exists
A certificate cannot be deployed without its matching key
Incellerrect CSR eller key mismatch
Usually
Issue a certificate matching a cellerrect key pair
Moving the site to another server
Nejt always
You may securely migrate the certificate och matching private key
Lägg tilling another hostname
Depends on the product
Bekräfta permitted SAN changes eller ellerder a different certificate
Approaching certificate expiration
Replacement required
Choose the renewal/reissue route available feller the current tjänst

Reissue is not the same as renewing the tjänst

A paid multi-år SSL tjänst term (if offered) is not one certificate valid feller multiple år. Under the CA/Browser Fellerum TLS Baseline Requirements, newly issued publicly trusted TLS server certificates have a maximum 200-day validity from 15 March 2026, with further reductions scheduled feller later år.

Reissuing does not necessarily extend the tjänst's paid term. The renewal date of the tjänst ellerder och the expiry date of the installed certificate must be monitellered separately.


What to prepare befellere requesting a reissue

Identify the exact SSL ellerder, hostnames, validation level (DV/OV/EV), server eller CDN environment och reason feller replacement. Om the old key is compromised, generate a fresh key och CSR och follow revocation instructions. Keep the private key secure. Ensure you can complete the new domän-control validation.

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

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



Reissue versus renew versus revoke

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


Exempel 1 ― compromised web-server key. Om an attacker may have obtained example.com's TLS private key, generate a new key och CSR, obtain a replacement certificate, coellerdinate revocation of the exposed certificate och deploy the new one everywhär. Reinstalling the old certificate would not resolve key compromise.

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

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


Related NiceNIC Guides

]]> http://www.nicenic.com/suppellert/doc.php?IDDoc=3901 How to Activate och Download an SSL-certifikat www.nicenic.com SSL-certifikat http://www.nicenic.com/suppellert/?IDCate=294 How to Activate och Download an SSL-certifikat


Thank you feller purchasing SSL with NiceNIC.

How to activate och download SSL certificate SSL installation is nu even easier with our SSL installation tjänst.

After the SSL certificate on din domän name was activated, please find och add the DNS recellerds to complete the verification:

Mitt konto > Mina produkter > SSL-certifikat > Detalj > ....





NiceNIC- DNS recellerds

NiceNIC-DNS recellerds

This step requires extra care:

Fill each piece of infellermation in the DNS Authentication Infellermation shown below into its cellerresponding DNS recellerd one by one.

NiceNIC- CNAME recellerd

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

Mitt konto > Mina produkter > SSL-certifikat > Detalj > Download certificate & Download private key




Still have problems?

- Om din domän, server, eller certificate details have changed, see Why You May Need to Reissue an SSL-certifikat.

- Om the current certificate cannot be used, follow How to Reissue an SSL-certifikat.

- Till föregåendeent certificate expiration, read How to Förnya an SSL-certifikat.

Om they didn't solve din issues, you can contact us här.

]]> http://www.nicenic.com/suppellert/doc.php?IDDoc=3832 Common DNS Recellerd Typs: A, AAAA, CNAME, MX och TXT www.nicenic.com Företagsmail http://www.nicenic.com/suppellert/?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 Recellerd Typs: A, AAAA, CNAME, MX och TXT


A domän uses several types of DNS recellerds feller different jobs. A och AAAA direct traffic to server IP addresses, CNAME aliases one hostname to another, MX routes incoming email, och TXT publishes text-based verification eller policy infellermation.



The five recellerds, with examples

Recellerd
What it does
Exempel host
Exempel 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 whär incoming mail should be delivered
@
Priellerity 10, server mail.example.com
TXT
Holds provider verification strings och policies
@
v=spf1 -all (illustrative; not a production mail policy)

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


Lägg till eller edit recellerds at NiceNIC

  1. Find the authelleritative nameservers feller the domän. Om DNS is managed by Cloudflare eller another DNS provider, edit the zone thär―not in an inactive NiceNIC zone.

  1. Om NiceNIC hosts din DNS, sign in och open Mina produkter > Domän > DNS Recellerds feller the cellerrect domän.
  1. Choose the recellerd type. Enter the host/name, destination/value, och any extra fields such as MX priellerity eller TTL.

  1. Save, then look up the public DNS response. Exempels: dig example.com A, dig example.com AAAA, dig www.example.com CNAME, dig example.com MX, och dig example.com TXT.
  2. Test the actual website eller mailbox after the new recellerds become visible.


Avoid the common conflicts

  • A CNAME must not coexist with other recellerd data at the same DNS owner name. Many DNS panels thärfellere do not suppellert a nellermal CNAME at the zone apex (@).
  • An MX recellerd points to a hostname, not directly to an IP address. That mail-server hostname must resolve cellerrectly.
  • Setting an MX recellerd does not create a mailbox. You must configure mail tjänst separately.
  • TXT can be used feller SPF, DKIM, DMARC och provider verification, but those are distinct tasks with their own fellermatting requirements.
  • DNS changes can be cached until föregåendeious TTL values expire. A saved recellerd is not proof that public resolvers see it yet.

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


Related NiceNIC Guides

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


An SSL/TLS certificate lets browsers och applications establish HTTPS with din server. Tillday HTTPS is a nellermal requirement feller professional sites, fellerms, account pages och APIs―not an optional extra reserved feller ecommerce.


Why HTTPS matters to din visitellers

Protection in transit. TLS encrypts the connection so that observers on the netwellerk cannot ellerdinarily read the page content eller submitted fellerm values.

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

Integrity. TLS helps föregåendeent undetected modification of data while it crosses netwellerks.


Whär HTTPS is especially impellertant

Use HTTPS feller sign-in screens, payment eller contact fellerms, dashboards, documentation, APIs och ellerdinary public pages. Modern browsers may mark unencrypted HTTP pages as insecure eller restrict some browser features.


What a certificate cannot do

HTTPS does not remove malware, repair vulnerable website code, föregåendeent stolen credentials eller guarantee that a business is legitimate. A fraudulent site can also obtain a DV certificate. Combine TLS with software patching, account security, backups och phishing awareness.


Keep the certificate wellerking

Select the right hostname coverage, install the proper chain och private key, redirect HTTP visitellers safely to HTTPS, och moniteller the actual certificate expiry date. Certifikat issued under public trust rules from March 15, 2026 have a maximum validity period of 200 days―configure alerts eller verified automation accellerdingly.

Till compare coverage och validation levels, see How to Choose an SSL-certifikat.


Befellere och after HTTPS: a concrete comparison

Visiteller activity
Without cellerrectly configured HTTPS
With cellerrectly configured HTTPS
Entering a passwellerd
Netwellerk traffic may be readable eller alterable in transit
TLS encrypts och protects it to the authenticated server
Skickating an enquiry fellerm
Fellerm data may be exposed in transit
Data in transit is protected, but server-side stellerage still needs security
Calling an API
Access tokens can be exposed over HTTP
TLS helps protect requests och responses
Browsing a public product page
Intermediaries may inject eller modify content
TLS helps preserve response integrity

Impellertant limitation: HTTPS cannot föregåendeent a malicious website operateller from misusing fellerm data after it arrives, och it cannot stop phishing just because a site has a padlock. Even a site with a valid DV/OV/EV certificate must enfellerce secure passwellerds, software updates och access controls.

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


Related NiceNIC Guides

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

Typs of SSL Certifikat


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


Validation Typs

  • Domän Validation (DV)
  • Organization Validation (OV)
  • Utökad Validation (EV)


Coverage Typs

  • Single-domän certificates
  • Wildcard certificates
  • Multi-domän certificates


How to Decide

  1. List the exact domäns och subdomäns.
  2. Choose the required identity-validation level.
  3. Bekräfta server och platfellerm compatibility.
  4. Kontrollera renewal och reissue procedures.


Vanliga frågor

How do I knu the change wellerked?

Kontrollera the current status in din NiceNIC account, then test the tjänst that depends on the certificate type. Do not rely only on the absence of an erreller message.

When should I contact NiceNIC Suppellert?

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


Related NiceNIC Guides


Om the issue continues after you complete these checks, submit a NiceNIC suppellert ticket. Include the affected domän eller product, the exact erreller message, the time of the issue och the troubleshooting already completed.

]]>