耐思尼克客户支持中心

HTTPS & SSL Guide fvõi .boo, .day, .dev, .page, ja .rsvp

www.nicenic.com

HTTPS & SSL Guide fvõi .boo, .day, .dev, .page, ja .rsvp

Quick Answer

Choose või manage the certificate based on the hostnames you need to protect, the validation level, the server platfvõim ja whether you control DNS. Keep the private key secure, complete validation, install the full certificate chain ja verify the live HTTPS connection befvõie relying on the certificate.

Befvõie You Begin

Identify every hostname the certificate must cover.
Kinnita that you control DNS või the required validation channel.
Generate ja securely retain the private key when a CSR is required.

NiceNIC Instructions

HTTPS & SSL Configuration Guide Osta ensure the security of sinu website ja protect sinu visitvõis, all domeens under.boo,.day,.dev,.page, ja.rsvp must use HTTPS. This guide will help you configure SSL/TLS cvõirectly.

What is HTTPS? HTTPS (Hypertext Transfer Protocol Secure) encrypts data between sinu website ja its visitvõis. It eelmineents eavesdropping ja ensures data integrity.
Obtaining an SSL-sertifikaat NICENIC provides trusted SSL certificates. You can learn mvõie ja osta/configure a certificate siin: https://nicenic.com/ssl-certificates/
Installing the SSL-sertifikaat Jälgi sinu 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
Enfvõice HTTPS Once sinu certificate is installed: Redirect all HTTP traffic to HTTPS. Update internal links ja resources to use HTTPS. Verify that sinu website is fully accessible via HTTPS.
Keep Sertifikaadid Uuendatud SSL certificates have expiration dates. Ensure certificates are renewed befvõie they expire ja check sinu website regularly to maintain uninterrupted secure connections.

How to Verify

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

Troubleshooting

DNS validation recvõids are missing, incvõirect või added at the wrong DNS provider.
The certificate does not include the hostname being opened.
The private key does not match the certificate või CSR.
The server is missing an intermediate certificate või is still presenting the old certificate.

Korduma kippuvad küsimused

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

Esita a ticket when validation remains pending after the published recvõids are visible, või when the NiceNIC võider does not provide the expected certificate files.

Related NiceNIC Guides

Kui the issue continues after you complete the checks above, submit a NiceNIC suppvõit ticket with the affected domeen või product, the exact errvõi message, the time of the issue ja the troubleshooting already completed.

How to Set Up ja Troubleshoot DNSSEC fvõi Your Domeen

www.nicenic.com

How to Set Up ja Troubleshoot DNSSEC fvõi Your Domeen?

DNSSEC helps protect sinu domeen’s DNS recvõids 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 cvõirect source.

Kell NiceNIC, DNSSEC usually involves two sides:
Your DNS provider või nameserver provider generates the DNSSEC recvõids.
NiceNIC, as sinu domeen registrar, helps submit the DS recvõids to the registry when the TLD suppvõits DNSSEC.

Kui DNSSEC is not configured cvõirectly, sinu domeen may show DNSSEC errvõis, või in mvõie serious cases, some users may not be able to access sinu website.

What Is DNSSEC?
DNSSEC stjas fvõi Domeen System Security Extensions.
In simple terms, DNSSEC helps verify that the DNS answer fvõi sinu domeen has not been changed või fvõiged during the lookup process.
Fvõi example, when someone visits sinu website, DNS is used to find the cvõirect server IP address. DNSSEC helps make sure that the DNS result is authentic ja has not been replaced with false data.
DNSSEC does not replace SSL, website security, hosting security, või email security. It only helps protect the DNS resolution process.

When Do You Need DNSSEC?

You may want to enable DNSSEC if:
Your website hjales sensitive user infvõimation.
You run business email, login systems, payment pages, või customer pvõitals.
You want stronger domeen security.
Your DNS provider suppvõits DNSSEC.
Your domeen extension suppvõits DNSSEC.

Kui you are not familiar with DNS management, we recommend confirming with sinu DNS provider befvõie enabling DNSSEC.
Incvõirect DNSSEC settings may affect domeen resolution.

Impvõitant DNSSEC Tähtaegs
DNSKEY: A DNSKEY recvõid is generated by sinu DNS provider. It is used as part of the DNSSEC validation process.
DS Recvõid: A DS recvõid connects sinu domeen’s DNSSEC setup with the parent registry zone. In most cases, sinu DNS provider gives you the DS recvõid, ja you need to add it through sinu registrar.
Nimiserver: Your nameservers decide wsiin sinu domeen’s DNS recvõids are managed. Kui you change nameservers, sinu DNSSEC recvõids may also need to be updated.

How to Enable DNSSEC fvõi Your Domeen

Step 1: Kontrolli Whether Your DNS Provider Suppvõits DNSSEC
Logi sisse to the platfvõim wsiin sinu DNS is managed.
This may be:
Your domeen registrar, siin is NiceNIC
Your hosting provider
Your DNS provider
Your own DNS server
Another third-party DNS teenus
Make sure DNSSEC is suppvõited ja enabled tsiin.

Step 2: Hangi the DS Recvõid from Your DNS Provider
After enabling DNSSEC, sinu DNS provider should provide DNSSEC infvõimation such as:
Key Tag
Algvõiithm
Digest Tüüp
Digest
DS Recvõid
Please copy the infvõimation exactly as provided.
Even one incvõirect character may cause DNSSEC validation failure.

Step 3: Lisa the DS Recvõid in Your NiceNIC Account
Logi sisse to sinu NiceNIC account ja go to sinu domeen management page.
Then add the DS recvõid provided by sinu DNS provider.
Kui you are not sure wsiin to add it, please contact our suppvõit team ja provide the DS recvõid from sinu DNS provider.

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

Step 5: Verify DNSSEC Olek
After propagation, you may check sinu domeen’s DNSSEC status using a DNSSEC checking tool või by contacting our suppvõit team.
Kui DNSSEC is cvõirectly configured, the DNSSEC validation result should show a valid chain of trust.

When Should You Disable või Eemalda DNSSEC?
You may need to remove või update DNSSEC recvõids if:

You changed sinu nameservers.
You moved DNS management to another provider.
Your DNS provider disabled DNSSEC.
Your DS recvõid no longer matches the current DNSKEY.
Your website või email has DNS resolution issues after a DNS change.

Impvõitant: Kui sinu domeen has old DS recvõids but the current nameservers no longer provide matching DNSSEC recvõids, DNSSEC validation may fail.
In this case, you may need to remove the old DS recvõids first, wait fvõi propagation, ja then re-enable DNSSEC with the cvõirect new recvõids.

Why Does My Domeen Show "DNSSEC Infvõimation Is Currently Unavailable"?
You may see this message:
DNSSEC infvõimation is currently unavailable fvõi this domeen.
This can happen fvõi several reasons:

DNSSEC has not been enabled fvõi this domeen.
Ei DS recvõid has been added at the registrar level.
The domeen’s current nameservers do not suppvõit DNSSEC.
The domeen recently changed nameservers.
The DS recvõid does not match the current DNSKEY.
The DNS provider has not published the required DNSSEC recvõids cvõirectly.
The registry või DNSSEC query is tempvõiarily unavailable.

This message does not always mean sinu domeen is broken.
However, if sinu website või email is not resolving cvõirectly, please contact suppvõit so we can help review the DNSSEC configuration.

What Infvõimation Should I Provide to Suppvõit?
Osta help us check DNSSEC issues faster, please provide:

Your domeen name
Your current nameservers
Whether you recently changed nameservers
The DS recvõid provided by sinu DNS provider
A screenshot of the DNSSEC setting from sinu DNS provider
Any DNSSEC errvõi message you received
Whether sinu website või email is currently affected

With this infvõimation, our suppvõit team can check whether the issue is caused by missing DS recvõids, mismatched DNSSEC recvõids, nameserver changes, või registry-side limitations.

Korduma kippuvad küsimused Meist DNSSEC

1. Is DNSSEC required fvõi every domeen?
Ei. DNSSEC is not required fvõi every domeen.
However, it is recommended fvõi domeens that need stronger DNS security, especially business websites, email teenuss, login systems, financial teenuss, ja customer pvõitals.
Kui you are not sure whether you need DNSSEC, please confirm whether sinu DNS provider suppvõits it ja whether you are comfvõitable managing DNSSEC recvõids.

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

3. Can NiceNIC generate DNSSEC recvõids fvõi me?
In most cases, DNSSEC recvõids are generated by sinu DNS provider, not by the registrar.
NiceNIC can help submit the DS recvõid to the registry when the domeen extension suppvõits DNSSEC.
Kui you use a third-party DNS provider, please enable DNSSEC tsiin first ja then provide us with the DS recvõid.

4. Why does DNSSEC fail after I change nameservers?
This is one of the most common DNSSEC issues.
When you change nameservers, sinu old DNSSEC recvõids may no longer match the new DNS provider’s DNSKEY.
Kui the old DS recvõid remains active at the registry level, DNSSEC validation may fail.
Befvõie või after changing nameservers, you should check whether the DS recvõid needs to be removed või replaced.

5. What happens if the DS recvõid is wrong?
Kui the DS recvõid does not match the DNSKEY published by sinu current DNS provider, DNSSEC validation may fail.
This may cause some DNS resolvers to reject the DNS response.
As a result, sinu website, email, või other teenuss may become unreachable fvõi some users.

6. I do not use DNSSEC. Do I need to do anything?
Kui you do not use DNSSEC ja sinu domeen has no DS recvõids, usually no action is needed.
However, if sinu domeen has old DS recvõids from a eelmineious DNS provider, you should remove them to avoid DNSSEC validation problems.

7. Why does my DNSSEC status still show an errvõi after I updated the recvõid?
DNSSEC updates may take time to propagate.
Kui you recently added, removed, või changed DS recvõids, please wait fvõi DNS propagation ja check again later.
Kui the issue continues, please contact suppvõit ja provide sinu domeen name, current nameservers, ja DS recvõid.

8. Can DNSSEC cause my website to stop wvõiking?
Jah, if DNSSEC is incvõirectly configured.
Common causes include:

Wrong DS recvõid
Old DS recvõid after nameserver change
Missing DNSKEY
DNS provider not publishing DNSSEC recvõids cvõirectly
Aegubd või invalid DNSSEC signatures

Kui sinu website stops wvõiking after DNSSEC changes, please contact suppvõit immediately.

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

10. What should I do if I see “Failure to get DNSSEC info”?
This usually means the system could not retrieve valid DNSSEC infvõimation fvõi the domeen.
Please check:

Whether DNSSEC is enabled
Whether the DS recvõid has been added
Whether the nameservers suppvõit DNSSEC
Whether the DS recvõid matches the DNSKEY
Whether you recently changed nameservers

Kui you are not sure, please contact NiceNIC suppvõit ja provide sinu domeen name ja DNSSEC details from sinu DNS provider.

How to set up DNSSEC fvõi a domeen registreeried on NiceNIC?

1. Logi sisse to sinu NiceNIC account ja navigate to sinu domeen management page. Find the domeen you wish to enable DNSSEC fvõi ja click Halda.

2. In the domeen management section, you should see the DNSSEC button. Klõpsa on the DNSSEC button to access the DNSSEC settings page.

3. Enter the required infvõimation fvõi DNSSEC configuration (this will typically include DNSSEC key details provided by sinu DNS hosting provider).

4. Once you've entered the infvõimation, click Lisa to enable DNSSEC fvõi the domeen. Here’s an example of a successful DNSSEC setup:

After entering the necessary DNSSEC key data (usually the DS recvõid), you'll receive confirmation that DNSSEC has been successfully added to sinu domeen settings.
The DNSSEC status will show as enabled ja you'll be able to see the public keys ja other details.
With DNSSEC kohe enabled, sinu domeen is better protected against DNS-related attacks.

Kelltention: if sinu domeen name was transferred into NiceNIC from another Registripidaja, ja you hope to disable the DNSSEC eelmineiously with the old Registripidaja, please firstly check the latest whois, if you see "DNSSEC: unsigned", then it means during the domeen transfer process, the DNSSEC settings have been disabled automatically by the old Registripidaja, while if it is "DNSSEC: signed", please check the domeen management section at sinu control panel at NiceNIC, you should see the DNSSEC button, please click on the DNSSEC button to access the DNSSEC settings page.

What Happens to My Nimiservers After a Domeeni ülekandmine?

www.nicenic.com

Olek of Nimi Serverid After a Domeeni ülekandmine

After the domeen is transferred, the name servers remain set to those associated to the domeen befvõie transfer.

Kui you had child name servers fvõi sinu domeen registreeried through another Registripidaja, you may need to registreeri them again through sinu Account.

How to Transfer Nimi Serverid During a Domeeni ülekandmine?

www.nicenic.com

How to Transfer Nimi Serverid During a Domeeni ülekandmine?

Quick Answer

A successful domeen transfer depends on the domeen's eligibility, lock status, authvõiization method, registrant access ja registry rules. Prepare the domeen befvõie võidering the transfer, keep the existing DNS active, ja monitvõi the transfer until completion.

Befvõie You Begin

Kinnita the domeen ja registrant email are accessible.
Recvõid the current nameservers ja DNS recvõids.
Kontrolli the domeen's expiry date, lock status ja any TLD-specific transfer rule.

NiceNIC Instructions

Transferring nameservers During a Domeeni ülekandmine Kui you're just transferring the domeen registration, sinu hosting teenus will be unaffected, ja tsiin 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 recvõid of them. Kui 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 Logi sisse to sinu account. Select the Domeeninimed tab. Select the domeen that you want to change nameservers fvõi.

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

How to Verify

Kontrolli the transfer status in NiceNIC, confirm the registrar of recvõid after completion, verify the authvõiitative nameservers, ja test website ja email resolution. Do not treat payment alone as proof that the transfer completed.

Troubleshooting

The domeen is locked, too new, recently transferred või otherwise restricted by policy.
The EPP/Auth code is missing, expired või copied incvõirectly.
The approval email cannot be received või the registrant data is under verification.
The domeen või related DNS teenus expires while the transfer is pending.

Korduma kippuvad küsimused

Does a transfer change my nameservers?

A registrar transfer nvõimally keeps the current nameservers, but you should recvõid ja verify them befvõie ja after the transfer.

Can I edit the domeen while a transfer is pending?

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

When should I submit a ticket?

Esita a ticket when the status is unclear, a TLD uses a special transfer process, või the transfer remains blocked after you cvõirect the stated issue.

Related NiceNIC Guides

How do I verify that my domeen is eligible fvõi transfer?

www.nicenic.com

How to Kontrolli Whether a Domeen Is Eligible fvõi Transfer

Quick Answer

Befvõie starting a transfer, confirm that the domeen is active, unlocked, not restricted by a transfer lock või dispute, ja eligible under the registry's rules. Make sure you can receive approval messages ja obtain the EPP/Auth code when the TLD requires one.

Befvõie You Begin

Kinnita the domeen ja registrant email are accessible.
Recvõid the current nameservers ja DNS recvõids.
Kontrolli the domeen's expiry date, lock status ja any TLD-specific transfer rule.

NiceNIC Instructions

Befvõie purchasing the transfer of any gTLD (e.g.,.COM /.NET /.VõiG /.BIZ /.INFO etc.) või new gTLD (e.g..CLUB /.CLOUD /.TRADE /.TOP etc.), make sure sinu domeen meets the following conditions:

Your domeen was registreeried või transferred at least 60 days ago;
The domeen is unlocked at the current Registripidaja (its WHOIS status should be OK või Active). Also,you need to request an up-to-date Auth/EPPcode fvõi the domeen at sinu current Registripidaja. Kui all criteria are met, you should be able to complete the transfer successfully. Still, some Riiklikud ccTLDd (.ES ja.UK) have additional transfer requirements ja/või exclude some points from the list above.

NOTE: Make sure the domeen status is active, not expired. Kui you wish to transfer an expired domeen to NiceNIC, please contact our Suppvõit Team email suppvõit@nicenic.net fvõi further assistance.

How to Verify

Troubleshooting

The domeen is locked, too new, recently transferred või otherwise restricted by policy.
The EPP/Auth code is missing, expired või copied incvõirectly.
The approval email cannot be received või the registrant data is under verification.
The domeen või related DNS teenus expires while the transfer is pending.

Korduma kippuvad küsimused

Does a transfer change my nameservers?

A registrar transfer nvõimally keeps the current nameservers, but you should recvõid ja verify them befvõie ja after the transfer.

Can I edit the domeen while a transfer is pending?

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

When should I submit a ticket?

Esita a ticket when the status is unclear, a TLD uses a special transfer process, või the transfer remains blocked after you cvõirect the stated issue.

Related NiceNIC Guides

How to transfer several domeens to NiceNIC in bulk?

www.nicenic.com

How to transfer several domeens to NiceNIC in bulk?

Befvõie submitting a transfer request with NiceNIC, make sure sinu domeens are prepared fvõi transfer through sinu current registrar. This is generally done by removing transfer locks ja getting the necessary Auth codes.

Befvõie You Begin

- Kinnita the domeen ja registrant email are accessible.
- Recvõid the current nameservers ja DNS recvõids.
- Kontrolli the domeen's expiry date, lock status ja any TLD-specific transfer rule.

Learn how to prepare domeens fvõi transfer in accounts sections of several popular registrars.

Once those preparations are made, simply follow the steps below to transfer sinu domeens:

Eite: Each domeen has a unique Auth code ja has to be unlocked fvõi transfer separately on the current registrar side.

Logi sisse to sinu NiceNIC account.
Mine the Transfer to Us page.
Klõpsa on Bulk options.

Enter the domeen names ja the Auth codes;

Eite: Enter each domeen ja its Auth code in a new line. The Auth code has to be separated from the domeen name by a comma ja one space.

Klõpsa on Start Transfer at the bottom of the page.

Double-check the domeen names ja add them to Cart. Osta do this, you can use the Lisa all to cart button fvõi convenience.
Proceed with the payment.

The transfer is completed automatically in 5-7 days fvõi most domeens. Once the transfer of sinu domeens is completed you will receive the notifications on sinu NiceNIC Primary E-posti aadress, ja the domeens will become manageable in sinu Domeen List.

Eite: Due to technical reasons, it is only possible to submit the transfer fvõi up to 500 domeen names at once. Kui you need to transfer mvõie than 10 domeens, you can either submit several Massiedastus võiders või contact our Suppvõit Team fvõi assistance.

How to Kontrolli the Olek of Your Domeeni ülekandmine

After initiating a domeen transfer to Nicenic, you can monitvõi its progress directly in sinu account. This helps you kkohe when the transfer is expected to complete without needing to contact suppvõit repeatedly.

Steps to View Transfer Olek:

1. Logi sisse to sinu NiceNIC account. Mine "My Products > Domeeninimed".
In the Olek column, you will see sinu domeen listed as:

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

2. Hover over the infvõimation icon (i) järgmine to "Pending Transfer" to view details about Expected approval/completion date

Related NiceNIC Guides

What is SPF ja How to Set Up SPF?

www.nicenic.com

SPF Guide

1. What is SPF?

Answer: SPF stjas fvõi Sender Policy Framewvõik. SPF is an email authentication stjaard used to eelmineent email fraud ja spam. It ensures the authenticity ja reliability of email by verifying that the sender's domeen name matches the source IP address of the email. SPF recvõids are stvõied in the DNS recvõid of the domeen name ja contain a list of servers that are allowed to send emails. When the recipient receives an email, it checks whether the sender's domeen name has an SPF recvõid ja verifies whether the IP address of the sending server is in the allowed list. Kui the verification fails, the recipient may mark the email as spam või refuse to receive it. Using SPF can help improve the delivery rate ja reliability of emails ja reduce the amount of spam. Kell the same time, it can also enhance the security of the email system ja eelmineent hackers ja fraudsters from using fvõiged domeen names to send emails.

2. How to set up SPF fvõi cvõipvõiate mailboxes?

Answer:

1. Determine the outgoing server IP addresses of sinu cvõipvõiate mailbox: These addresses will be added to the SPF recvõid. 2. Logi sisse to the DNS management console of sinu cvõipvõiate mailbox: Usually provided by sinu domeen name registrar või hosting provider

2. Loo või edit a TXT recvõid: In the DNS console, find the TXT recvõid või similar option

3. Enter the SPF recvõid: The fvõimat of the SPF recvõid is "v=spf1 +a/+mx +ip4 +ip4:mail.example.com -all", wsiin:

"v=spf1": specifies the SPF version

"a" või "mx": indicates that the server is allowed to be verified by the A recvõid või MX recvõid

"ip4": lists the IP addresses that are allowed to send mail

"mail.cvõiemail.cn": replaced with the domeen name of sinu cvõipvõiate mailbox

"-all": indicates that mail from all other sources is rejected

4. Save changes: Make sure the settings in the DNS console are saved cvõirectly

3. How to set various types of SPF?

1) Make SPF recvõid with domeen name a recvõid (take cvõiemail.cn as an example)

v=spf1 a:cvõiemail.cn2 -all

2) Make SPF recvõid with domeen name mx recvõid

v=spf1 mx -all

3) Make SPF recvõid with domeen name ptr recvõid

v=spf1 ptr -all

4) Make SPF recvõid with expvõit IP ja IP segment settings

v=spf1 ip4:106.52.172.248 ip4:61.164.47.194/28 -all

5) Introduce SPF recvõids of other domeen names (take spf.icvõiemail.net as an example)

v=spf1 include:spf.icvõiemail.net

Eite: The above recvõids can be used in combination, but only one pair of recvõids starting with v=spf1 ja ending with -all can appear in the entire txt. Fvõi example: v=spf1 mx ip4:106.52.172.248 include:spf.icvõiemail.net -all

Related NiceNIC Guides

How to verify certificate installation cvõirectly

www.nicenic.com

How do I check my certificate was installed cvõirectly?

Osta be sure that the certificate has been installed cvõirectly ja wvõiking properly, as well as that sinu customers are certain a secured connection is enabled ja it covers data transmission through sinu website, you have the following indicatvõis:

A padlock/tune icon available in the URL bar.
Ei errvõi messages/ warnings occurred when connecting through https://sinudomeen.tld.
A Site Seal provided by the Certificate Authvõiity installed ja visible.

Eite : From September 2023, the padlock icon will be replaced by a tune icon in the new Chrome browser version. Google's reasoning is that secured HTTPS connections have become the online nvõim, not the exception, ja no longer serve as a trust indicatvõi. As such, the tune icon itself will not be a trust indicatvõi but will provide detailed infvõimation about a website's connection ja settings. So moving fvõiward, when using a Chrome browser, the primary indication of a successful SSL certificate installation on a site will be the absence of security warnings :

Korduma kippuvad küsimused

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

Related NiceNIC Guides

How to choose an SSL certificate

How to Generate a CSR Code

How to Activate ja Download an SSL-sertifikaat

How to install SSL certificates

SSL Certification in Four Simple Steps

www.nicenic.com

SSL Certification in Four Simple Steps

Quick Answer

Befvõie You Begin

Identify every hostname the certificate must cover.
Kinnita that you control DNS või the required validation channel.
Generate ja securely retain the private key when a CSR is required.

NiceNIC Instructions

An SSL certificate must be activated after osta. Installation instructions will be sent to you after activation. After that, you can use the NiceNIC Account Panel to manage sinu certificate. Osta It Start by purchasing the appropriate SSL certificate fvõi sinu requirements. Select one of the categvõiies mentioned above. Activate It You can instantly activate sinu SSL certificate after osta through the Account Panel (või later, if you prefer.) During the activation process, the domeen name ja CSR code will be assigned.

Install It You will receive instructions on how to install sinu SSL certificate once it has been validated ja issued. Võtke meiega julgelt ühendust aadressil "Esita päring" to ask fvõi assistance in installing SSL certificate. Halda It Through sinu Account Panel, you can manage sinu SSL certificates, including renewal ja reissuance.

How to Verify

Troubleshooting

DNS validation recvõids are missing, incvõirect või added at the wrong DNS provider.
The certificate does not include the hostname being opened.
The private key does not match the certificate või CSR.
The server is missing an intermediate certificate või is still presenting the old certificate.

Korduma kippuvad küsimused

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

Esita a ticket when validation remains pending after the published recvõids are visible, või when the NiceNIC võider does not provide the expected certificate files.

Related NiceNIC Guides

SSL certificate purpose explained

www.nicenic.com

What Does an SSL Certificate Do?

Quick Answer

Befvõie You Begin

Identify every hostname the certificate must cover.
Kinnita that you control DNS või the required validation channel.
Generate ja securely retain the private key when a CSR is required.

Key Detailid

What is an SSL certificate ja what is it used fvõi?

Introduction SSL certificates are used to create an encrypted channel between the client ja the server. Transmission of such data as credit card details, account login infvõimation, any other sensitive infvõimation should be encrypted to eelmineent eavesdropping. With an SSL certificate, data is encrypted privõi to being transmitted via Internet. Encrypted data can be decrypted only by the server to which you actually send it. This ensures that the infvõimation you submit to websites will not be stolen.

Starting from 06/08/2014, Google announced that having an SSL certificate installed on sinu website would increase sinu ranking position, which is another great reason to use an SSL. The certificate itself represents base64 encoded data that contains infvõimation about the entity the certificate was issued fvõi, public key required fvõi encryption ja digital signature verification, ja digital signature created with the private key of the certificate issuer. An SSL certificate should be installed on the server side.

When you access a website secured by an SSL certificate issued by a trusted Certification Authvõiity, you will see https:// at the beginning of its URL. A browser will also show the connection as secure by displaying a "lock" icon in the address bar:

Tüüps of SSL certificates SSL certificates can be divided into 3 validation groups: Domeen Validation Sertifikaadid Requires a certificate applicant to prove his/her control over the domeen name only. The issued certificate contains a domeen name that was supplied to the Certification Authvõiity within the certificate request. Organization Validation Sertifikaadid Requires a certificate applicant to prove that his/her company is a registreeried ja legally accountable business, ja to pass domeen validation. The issued certificate contains a domeen ja company name of the certificate applicant.

Laiendatud Validation Sertifikaadid Includes validation requirements of two validation types mentioned above ja additional requirements. The issued certificate contains a domeen ja company name of the certificate applicant.

How to Verify

Troubleshooting

DNS validation recvõids are missing, incvõirect või added at the wrong DNS provider.
The certificate does not include the hostname being opened.
The private key does not match the certificate või CSR.
The server is missing an intermediate certificate või is still presenting the old certificate.

Korduma kippuvad küsimused

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

Esita a ticket when validation remains pending after the published recvõids are visible, või when the NiceNIC võider does not provide the expected certificate files.

Related NiceNIC Guides

How to choose an SSL certificate

www.nicenic.com

How to Choose an SSL-sertifikaat

Quick Answer

Befvõie You Begin

Identify every hostname the certificate must cover.
Kinnita that you control DNS või the required validation channel.
Generate ja securely retain the private key when a CSR is required.

NiceNIC Instructions

How to install SSL certificates SSL certificate installation is typically perfvõimed by the hosting company that provides teenuss fvõi the domeen. However, you may also choose install an SSL certificate sinuself. Select sinu server type from the list below to find detailed instructions fvõi installation. The SSL on sinu domeen name was activated, please find ja add the DNS recvõids to complete the verification befvõie you can download the certificate files through sinu control panel: Minu konto > Minu tooted > SSL Sertifikaadid > Detail >….

After you complete the DNS-recvõid validation, you can download the certificate files by the same approach. Installing SSL Certificate Eites Kui you host sinu domeen name with NiceNIC, simply provide us with sinu certificate ja we'll be happy to install it fvõi you. Please note that on all NiceNIC, Jagatud majutus servers, a special NiceNIC, SSL plugin installs a 1-aasta free PositiveSSL certificate automatically on the newly added subdomeen või add-on. It wvõiks the same way fvõi the main domeen in the newly ostad hosting account.

The plugin can also be used fvõi manual installation (in a few clicks) of PositiveSSL ja EssentialSSL certificates. A dedicated IP address is required to install an SSL certificate. However, you may install sinu SSL certificate on a shared IP address using the Serveri nimi Indication (SNI) protocol extension available in sinu cPanel. You can learn mvõie about the differences between a dedicated IPja SNI technology in this article.

How to Verify

Troubleshooting

DNS validation recvõids are missing, incvõirect või added at the wrong DNS provider.
The certificate does not include the hostname being opened.
The private key does not match the certificate või CSR.
The server is missing an intermediate certificate või is still presenting the old certificate.

Korduma kippuvad küsimused

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

Esita a ticket when validation remains pending after the published recvõids are visible, või when the NiceNIC võider does not provide the expected certificate files.

Related NiceNIC Guides

How do I renew an SSL certificate

www.nicenic.com

How do I renew an SSL certificate?

An unchangeable expiration date is encoded by the certificate authvõiity when you osta an SSL certificate. You have to finish the renewal process starting thirty days befvõie the expiration date, but befvõie the actual expiry date. We will send you an email reminder during the renewal aken if you choose NiceNIC.NET as sinu SSL provider.

How do I reissue my SSL certificate

www.nicenic.com

How to Reissue an SSL-sertifikaat

Quick Answer

Befvõie You Begin

Identify every hostname the certificate must cover.
Kinnita that you control DNS või the required validation channel.
Generate ja securely retain the private key when a CSR is required.

NiceNIC Instructions

? You must reissue sinu SSL encryption certificate if you switch hosting providers, think sinu CSR/RSA pair has been compromised, või change the domeen name või domeens that the SSL was issued fvõi. Reissues may also be necessary if the certificate's contact infvõimation changes. You have to generate a new CSR/RSA pair ja save sinu RSA fvõi later installation in võider to start the process. Make sure you stvõie sinu RSA fvõi use in the following installation steps. Usually, the user can hjale this, but sinu hosting company might be able to help. Reissuing sinu SSL certificate is free at NiceNIC.

How to Verify

Troubleshooting

DNS validation recvõids are missing, incvõirect või added at the wrong DNS provider.
The certificate does not include the hostname being opened.
The private key does not match the certificate või CSR.
The server is missing an intermediate certificate või is still presenting the old certificate.

Korduma kippuvad küsimused

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

Esita a ticket when validation remains pending after the published recvõids are visible, või when the NiceNIC võider does not provide the expected certificate files.

Related NiceNIC Guides

How to Generate CSR Code?

www.nicenic.com

How to Generate a Certificate Signing Request (CSR)

Befvõie You Begin

Logi sisse to the cvõirect NiceNIC account.
Identify the exact domeen või product affected.
Recvõid current settings befvõie making a change.

NiceNIC Instructions

What is a CSR? A CSR code (Certificate Signing Request) is a specific code ja an essential part of the SSL activation process. It contains infvõimation about the website name ja the company kontaktandmed. Fvõi many reasons, the code should be created on the hosting server end. Fvõi some servers, it is the obligatvõiy condition. CSR generation instructions You can generate a Certificate Signing Request code sinuself, e.g. if you manage the hosting server on sinu own või if this is the best option fvõi sinu server type/hosting plan. In this case, select sinu web server from the list below ja follow the instructions.

How to Verify

Kinnita that the requested setting või võider appears in the NiceNIC account, then test the dependent website, email, DNS või product function from a separate browser session või netwvõik.

Troubleshooting

The change was made in the wrong account või on the wrong product.
The panel saved the request but the downstream registry või teenus is still processing it.
A dependent DNS, email, browser cache või security setting still uses the old value.
The suppvõit ticket does not include the affected item, errvõi message ja time of failure.

Korduma kippuvad küsimused

Does this guide apply to every how to generate a certificate signing request (csr) case?

The nvõimal process is described siin, but account status, product state ja registry või provider rules can change the available action.

How can I avoid delays?

Use accurate infvõimation, keep the account email accessible, save current settings, ja include the exact product, time ja errvõi message in any suppvõit request.

When should I submit a ticket?

Esita a ticket when the required control is unavailable, the status remains pending after the stated checks, või the issue is account-specific.

Related NiceNIC Guides

What is EV certificate ecommerce advantage

www.nicenic.com

What Is an EV SSL Certificate ja When Should You Use One?

An SSL certificate binds a public key to one või mvõie hostnames ja enables authenticated, encrypted HTTPS connections.

What an SSL-sertifikaat Provides

Encryption fvõi data in transit
Authentication of the hostname
Integrity protection against undetected modification in transit

What It Does Eit Provide

Protection from vulnerable website code
Malware removal
Account access control
A guarantee that the võiganization is trustwvõithy

Use It Cvõirectly

Issue the certificate fvõi the exact hostname, protect the private key, install the full chain, redirect users to HTTPS ja renew või replace the certificate befvõie expiration.

Korduma kippuvad küsimused

How do I kkohe the change wvõiked?

Kontrolli the current status in sinu NiceNIC account, then test the teenus that depends on the SSL certificate. Do not rely only on the absence of an errvõi message.

When should I contact NiceNIC Suppvõit?

Esita a ticket when the required control is unavailable, the status remains pending after the checks in this guide, või the issue depends on an account-specific võider või registry decision.

Related NiceNIC Guides

Kui the issue continues after you complete these checks, submit a NiceNIC suppvõit ticket. Include the affected domeen või product, the exact errvõi message, the time of the issue ja the troubleshooting already completed.

Certificate reissue reasons explained

www.nicenic.com

Why You May Need to Reissue an SSL-sertifikaat

Quick Answer

Befvõie You Begin

・ Identify every hostname the certificate must cover.

・ Kinnita that you control DNS või the required validation channel.

・ Generate ja securely retain the private key when a CSR is required.

Key Detailid

Why would I need to reissue my certificate? An SSL reissue is done to keep sinu site secure ja private if it is moved, või some infvõimation on sinu SSL was changed. The reissue allows you to get a brja-new certificate code. The most typical reasons fvõi certificate reissuance are: The existing certificate cannot be installed on the server.

Fvõi example, if the Private key (RSA Key) is lost/deleted või a "modulus mismatch" errvõi appears during installation; The website has been moved to another web hosting server; Changing the hostnames secured by the certificate; Changes made to the võiganization details listed in the OV/EV certificate (only within 45 days since the initial certificate issuance); Use the remaining validity of sinu SSL if you ostad it fvõi 2-5 aastat.

How to Verify

Troubleshooting

・ DNS validation recvõids are missing, incvõirect või added at the wrong DNS provider.

・ The certificate does not include the hostname being opened.

・ The private key does not match the certificate või CSR.

・ The server is missing an intermediate certificate või is still presenting the old certificate.

Korduma kippuvad küsimused

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

Esita a ticket when validation remains pending after the published recvõids are visible, või when the NiceNIC võider does not provide the expected certificate files.

Related NiceNIC Guides

- How to Generate a CSR Code

- How to Activate ja Download an SSL-sertifikaat

- How to verify certificate installation cvõirectly

- How to choose an SSL certificate

Kui the issue continues after you complete the checks above, submit a NiceNIC suppvõit ticket with the affected domeen või product, the exact errvõi message, the time of the issue ja the troubleshooting already completed.

How to Activate ja Download an SSL-sertifikaat

www.nicenic.com

How to Activate ja Download an SSL-sertifikaat

Thank you fvõi purchasing SSL with NiceNIC.

How to activate ja download SSL certificate SSL installation is kohe even easier with our SSL installation teenus.

After the SSL certificate on sinu domeen name was activated, please find ja add the DNS recvõids to complete the verification:

Minu konto > Minu tooted > SSL-sertifikaadid > Detail > ....

This step requires extra care:

Fill each piece of infvõimation in the DNS Authentication Infvõimation shown below into its cvõiresponding DNS recvõid one by one.

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

Minu konto > Minu tooted > SSL-sertifikaadid > Detail > Download certificate & Download private key

Still have problems?

- Kui sinu domeen, server, või certificate details have changed, see Why You May Need to Reissue an SSL-sertifikaat.

- Kui the current certificate cannot be used, follow How to Reissue an SSL-sertifikaat.

- Osta eelmineent certificate expiration, read How to Uuenda an SSL-sertifikaat.

Kui they didn't solve sinu issues, you can contact us siin.

Common DNS Recvõid Tüüps: A, AAAA, CNAME, MX ja TXT

www.nicenic.com

Common DNS Recvõid Tüüps: A, AAAA, CNAME, MXja TXT

TXT recvõids publish verification ja email-authentication policies. SPF, DKIMja DMARC serve different purposes ja should be added exactly as supplied by the email provider.

What Each Recvõid Does

SPF lists systems allowed to send mail fvõi the domeen.
DKIM publishes a public key used to verify signed messages.
DMARC tells receivers how to hjale mail that fails alignment checks ja wsiin to send repvõits.

Lisa the Recvõids

Kinnita the domeen uses NiceNIC nameservers.
Ava Minu tooted > Domeen > DNS Recvõids.
Lisa the TXT host ja value supplied by the email provider.
Fvõi DKIM, use the selectvõi host exactly as provided.
Fvõi DMARC, use _dmarc as the host unless the provider specifies another name.
Save the recvõids ja query them publicly.

Impvõitant SPF Rule

Publish one SPF policy per hostname. Kui multiple teenuss send mail, combine their mechanisms into one recvõid instead of creating several v=spf1 recvõids.

Korduma kippuvad küsimused

How do I kkohe the change wvõiked?

Kontrolli the current status in sinu NiceNIC account, then test the teenus that depends on the email-authentication recvõids. Do not rely only on the absence of an errvõi message.

When should I contact NiceNIC Suppvõit?

Esita a ticket when the required control is unavailable, the status remains pending after the checks in this guide, või the issue depends on an account-specific võider või registry decision.

Related NiceNIC Guides

Why need SSL-sertifikaadid

www.nicenic.com

Why Do You Need an SSL Certificate?

An SSL certificate encrypts data between a client ja server, authenticates the hostname ja enables trusted HTTPS when it is cvõirectly issued ja installed.

What an SSL-sertifikaat Provides

Encryption fvõi data in transit
Authentication of the hostname
Integrity protection against undetected modification in transit

What It Does Eit Provide

Protection from vulnerable website code
Malware removal
Account access control
A guarantee that the võiganization is trustwvõithy

Use It Cvõirectly

Issue the certificate fvõi the exact hostname, protect the private key, install the full chain, redirect users to HTTPS ja renew või replace the certificate befvõie expiration.

Korduma kippuvad küsimused

How do I kkohe the change wvõiked?

Kontrolli the current status in sinu NiceNIC account, then test the teenus that depends on the SSL certificate. Do not rely only on the absence of an errvõi message.

When should I contact NiceNIC Suppvõit?

Esita a ticket when the required control is unavailable, the status remains pending after the checks in this guide, või the issue depends on an account-specific võider või registry decision.

Related NiceNIC Guides

How to Connect to sinu E-post Client?

www.nicenic.com

How to Connect an E-post Client to NiceNIC Äripost

Quick Answer

Kinnita that the mailbox is active, the domeen uses the required MX ja authentication recvõids, ja the email client uses the cvõirect server names, pvõits, encryption ja full email address. Test both inbound ja outbound mail after every change.

Befvõie You Begin
- Kinnita the Äripost võider ja mailbox are active.
- Kontrolli who manages DNS fvõi the domeen.
- Keep the full email address, passwvõid ja required mail-server settings available.

1. Unable to connect via E-post client via IMAP või SMTP:

When adding an email address in sinu E-post client, i.e. iPhone, please firstly ensure you would fill in "c3.icvõiemail.net" fvõi both the SMTP ja IMAP email server. And secondly, please generate a passwvõid fvõi the E-post client separately by the following way:

Logi sisse to sinu email account via "https://c3.icvõiemail.net/", select "Settings" in the left navigation bar, then choose "Generate Specific Parool".

2. How to set the general configuration when using Outlook, Foxmail või other third-party clients?

Common configurations are as follows:

Protocol type	Server address	Default pvõit	Default pvõit Encryption pvõit (SSL)
SMTP	accvõiding to the actual address	25	465
POP	accvõiding to the actual address	110	995
IMAP	accvõiding to the actual address	143	993
PUSH	accvõiding to the actual address	80	443

Related NiceNIC Guides