耐思尼克客户支持中心

HTTPS & SSL Guide for .boo, .day, .dev, .page, and .rsvp

www.nicenic.com

HTTPS & SSL Guide for .boo, .day, .dev, .page, and .rsvp

Quick Answer

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

Before You Begin

Identify every hostname the certificate must cover.
Confirm that you control DNS or the required validation channel.
Generate and securely retain the private key when a CSR is required.

NiceNIC Instructions

HTTPS & SSL Configuration Guide To ensure the security of your website and protect your visitors, all domains under.boo,.day,.dev,.page, and.rsvp must use HTTPS. This guide will help you configure SSL/TLS correctly.

What is HTTPS? HTTPS (Hypertext Transfer Protocol Secure) encrypts data between your website and its visitors. It prevents eavesdropping and ensures data integrity.
Obtaining an SSL Certificate NICENIC provides trusted SSL certificates. You can learn more and purchase/configure a certificate here: https://nicenic.com/ssl-certificates/
Installing the SSL Certificate Follow your 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
Enforce HTTPS Once your certificate is installed: Redirect all HTTP traffic to HTTPS. Update internal links and resources to use HTTPS. Verify that your website is fully accessible via HTTPS.
Keep Certificates Updated SSL certificates have expiration dates. Ensure certificates are renewed before they expire and check your website regularly to maintain uninterrupted secure connections.

How to Verify

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

Troubleshooting

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

Frequently Asked Questions

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

Submit a ticket when validation remains pending after the published records are visible, or when the NiceNIC order does not provide the expected certificate files.

Related NiceNIC Guides

If the issue continues after you complete the checks above, submit a NiceNIC support ticket with the affected domain or product, the exact error message, the time of the issue and the troubleshooting already completed.

How to Set Up and Troubleshoot DNSSEC for Your Domain

www.nicenic.com

How to Set Up and Troubleshoot DNSSEC for Your Domain?

DNSSEC helps protect your domain’s DNS records 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 correct source.

At NiceNIC, DNSSEC usually involves two sides:
Your DNS provider or nameserver provider generates the DNSSEC records.
NiceNIC, as your domain registrar, helps submit the DS records to the registry when the TLD supports DNSSEC.

If DNSSEC is not configured correctly, your domain may show DNSSEC errors, or in more serious cases, some users may not be able to access your website.

What Is DNSSEC?
DNSSEC stands for Domain Name System Security Extensions.
In simple terms, DNSSEC helps verify that the DNS answer for your domain has not been changed or forged during the lookup process.
For example, when someone visits your website, DNS is used to find the correct server IP address. DNSSEC helps make sure that the DNS result is authentic and has not been replaced with false data.
DNSSEC does not replace SSL, website security, hosting security, or email security. It only helps protect the DNS resolution process.

When Do You Need DNSSEC?

You may want to enable DNSSEC if:
Your website handles sensitive user information.
You run business email, login systems, payment pages, or customer portals.
You want stronger domain security.
Your DNS provider supports DNSSEC.
Your domain extension supports DNSSEC.

If you are not familiar with DNS management, we recommend confirming with your DNS provider before enabling DNSSEC.
Incorrect DNSSEC settings may affect domain resolution.

Important DNSSEC Terms
DNSKEY: A DNSKEY record is generated by your DNS provider. It is used as part of the DNSSEC validation process.
DS Record: A DS record connects your domain’s DNSSEC setup with the parent registry zone. In most cases, your DNS provider gives you the DS record, and you need to add it through your registrar.
Nameserver: Your nameservers decide where your domain’s DNS records are managed. If you change nameservers, your DNSSEC records may also need to be updated.

How to Enable DNSSEC for Your Domain

Step 1: Check Whether Your DNS Provider Supports DNSSEC
Log in to the platform where your DNS is managed.
This may be:
Your domain registrar, here is NiceNIC
Your hosting provider
Your DNS provider
Your own DNS server
Another third-party DNS service
Make sure DNSSEC is supported and enabled there.

Step 2: Get the DS Record from Your DNS Provider
After enabling DNSSEC, your DNS provider should provide DNSSEC information such as:
Key Tag
Algorithm
Digest Type
Digest
DS Record
Please copy the information exactly as provided.
Even one incorrect character may cause DNSSEC validation failure.

Step 3: Add the DS Record in Your NiceNIC Account
Log in to your NiceNIC account and go to your domain management page.
Then add the DS record provided by your DNS provider.
If you are not sure where to add it, please contact our support team and provide the DS record from your DNS provider.

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

Step 5: Verify DNSSEC Status
After propagation, you may check your domain’s DNSSEC status using a DNSSEC checking tool or by contacting our support team.
If DNSSEC is correctly configured, the DNSSEC validation result should show a valid chain of trust.

When Should You Disable or Remove DNSSEC?
You may need to remove or update DNSSEC records if:

You changed your nameservers.
You moved DNS management to another provider.
Your DNS provider disabled DNSSEC.
Your DS record no longer matches the current DNSKEY.
Your website or email has DNS resolution issues after a DNS change.

Important: If your domain has old DS records but the current nameservers no longer provide matching DNSSEC records, DNSSEC validation may fail.
In this case, you may need to remove the old DS records first, wait for propagation, and then re-enable DNSSEC with the correct new records.

Why Does My Domain Show "DNSSEC Information Is Currently Unavailable"?
You may see this message:
DNSSEC information is currently unavailable for this domain.
This can happen for several reasons:

DNSSEC has not been enabled for this domain.
No DS record has been added at the registrar level.
The domain’s current nameservers do not support DNSSEC.
The domain recently changed nameservers.
The DS record does not match the current DNSKEY.
The DNS provider has not published the required DNSSEC records correctly.
The registry or DNSSEC query is temporarily unavailable.

This message does not always mean your domain is broken.
However, if your website or email is not resolving correctly, please contact support so we can help review the DNSSEC configuration.

What Information Should I Provide to Support?
To help us check DNSSEC issues faster, please provide:

Your domain name
Your current nameservers
Whether you recently changed nameservers
The DS record provided by your DNS provider
A screenshot of the DNSSEC setting from your DNS provider
Any DNSSEC error message you received
Whether your website or email is currently affected

With this information, our support team can check whether the issue is caused by missing DS records, mismatched DNSSEC records, nameserver changes, or registry-side limitations.

Frequently Asked Questions About DNSSEC

1. Is DNSSEC required for every domain?
No. DNSSEC is not required for every domain.
However, it is recommended for domains that need stronger DNS security, especially business websites, email services, login systems, financial services, and customer portals.
If you are not sure whether you need DNSSEC, please confirm whether your DNS provider supports it and whether you are comfortable managing DNSSEC records.

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

3. Can NiceNIC generate DNSSEC records for me?
In most cases, DNSSEC records are generated by your DNS provider, not by the registrar.
NiceNIC can help submit the DS record to the registry when the domain extension supports DNSSEC.
If you use a third-party DNS provider, please enable DNSSEC there first and then provide us with the DS record.

4. Why does DNSSEC fail after I change nameservers?
This is one of the most common DNSSEC issues.
When you change nameservers, your old DNSSEC records may no longer match the new DNS provider’s DNSKEY.
If the old DS record remains active at the registry level, DNSSEC validation may fail.
Before or after changing nameservers, you should check whether the DS record needs to be removed or replaced.

5. What happens if the DS record is wrong?
If the DS record does not match the DNSKEY published by your current DNS provider, DNSSEC validation may fail.
This may cause some DNS resolvers to reject the DNS response.
As a result, your website, email, or other services may become unreachable for some users.

6. I do not use DNSSEC. Do I need to do anything?
If you do not use DNSSEC and your domain has no DS records, usually no action is needed.
However, if your domain has old DS records from a previous DNS provider, you should remove them to avoid DNSSEC validation problems.

7. Why does my DNSSEC status still show an error after I updated the record?
DNSSEC updates may take time to propagate.
If you recently added, removed, or changed DS records, please wait for DNS propagation and check again later.
If the issue continues, please contact support and provide your domain name, current nameservers, and DS record.

8. Can DNSSEC cause my website to stop working?
Yes, if DNSSEC is incorrectly configured.
Common causes include:

Wrong DS record
Old DS record after nameserver change
Missing DNSKEY
DNS provider not publishing DNSSEC records correctly
Expired or invalid DNSSEC signatures

If your website stops working after DNSSEC changes, please contact support immediately.

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

10. What should I do if I see “Failure to get DNSSEC info”?
This usually means the system could not retrieve valid DNSSEC information for the domain.
Please check:

Whether DNSSEC is enabled
Whether the DS record has been added
Whether the nameservers support DNSSEC
Whether the DS record matches the DNSKEY
Whether you recently changed nameservers

If you are not sure, please contact NiceNIC support and provide your domain name and DNSSEC details from your DNS provider.

How to set up DNSSEC for a domain registered on NiceNIC?

1. Log in to your NiceNIC account and navigate to your domain management page. Find the domain you wish to enable DNSSEC for and click Manage.

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

3. Enter the required information for DNSSEC configuration (this will typically include DNSSEC key details provided by your DNS hosting provider).

4. Once you've entered the information, click Add to enable DNSSEC for the domain. Here’s an example of a successful DNSSEC setup:

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

Attention: if your domain name was transferred into NiceNIC from another Registrar, and you hope to disable the DNSSEC previously with the old Registrar, please firstly check the latest whois, if you see "DNSSEC: unsigned", then it means during the domain transfer process, the DNSSEC settings have been disabled automatically by the old Registrar, while if it is "DNSSEC: signed", please check the domain management section at your 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 Nameservers After a Domain Transfer?

www.nicenic.com

Status of Name Servers After a Domain Transfer

After the domain is transferred, the name servers remain set to those associated to the domain before transfer.

If you had child name servers for your domain registered through another Registrar, you may need to register them again through your Account.

How to Transfer Name Servers During a Domain Transfer?

www.nicenic.com

How to Transfer Name Servers During a Domain Transfer?

Quick Answer

A successful domain transfer depends on the domain's eligibility, lock status, authorization method, registrant access and registry rules. Prepare the domain before ordering the transfer, keep the existing DNS active, and monitor the transfer until completion.

Before You Begin

Confirm the domain and registrant email are accessible.
Record the current nameservers and DNS records.
Check the domain's expiry date, lock status and any TLD-specific transfer rule.

NiceNIC Instructions

Transferring nameservers During a Domain Transfer If you're just transferring the domain registration, your hosting service will be unaffected, and there 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 record of them. If 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 Login to your account. Select the Domain Names tab. Select the domain that you want to change nameservers for.

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

How to Verify

Check the transfer status in NiceNIC, confirm the registrar of record after completion, verify the authoritative nameservers, and test website and email resolution. Do not treat payment alone as proof that the transfer completed.

Troubleshooting

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

Frequently Asked Questions

Does a transfer change my nameservers?

A registrar transfer normally keeps the current nameservers, but you should record and verify them before and after the transfer.

Can I edit the domain while a transfer is pending?

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

When should I submit a ticket?

Submit a ticket when the status is unclear, a TLD uses a special transfer process, or the transfer remains blocked after you correct the stated issue.

Related NiceNIC Guides

How do I verify that my domain is eligible for transfer?

www.nicenic.com

How to Check Whether a Domain Is Eligible for Transfer

Quick Answer

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

Before You Begin

Confirm the domain and registrant email are accessible.
Record the current nameservers and DNS records.
Check the domain's expiry date, lock status and any TLD-specific transfer rule.

NiceNIC Instructions

Before purchasing the transfer of any gTLD (e.g.,.COM /.NET /.ORG /.BIZ /.INFO etc.) or new gTLD (e.g..CLUB /.CLOUD /.TRADE /.TOP etc.), make sure your domain meets the following conditions:

Your domain was registered or transferred at least 60 days ago;
The domain is unlocked at the current Registrar (its WHOIS status should be OK or Active). Also,you need to request an up-to-date Auth/EPPcode for the domain at your current Registrar. If all criteria are met, you should be able to complete the transfer successfully. Still, some ccTLDs (.ES and.UK) have additional transfer requirements and/or exclude some points from the list above.

NOTE: Make sure the domain status is active, not expired. If you wish to transfer an expired domain to NiceNIC, please contact our Support Team email support@nicenic.net for further assistance.

How to Verify

Troubleshooting

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

Frequently Asked Questions

Does a transfer change my nameservers?

A registrar transfer normally keeps the current nameservers, but you should record and verify them before and after the transfer.

Can I edit the domain while a transfer is pending?

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

When should I submit a ticket?

Submit a ticket when the status is unclear, a TLD uses a special transfer process, or the transfer remains blocked after you correct the stated issue.

Related NiceNIC Guides

How to transfer several domains to NiceNIC in bulk?

www.nicenic.com

How to transfer several domains to NiceNIC in bulk?

Before submitting a transfer request with NiceNIC, make sure your domains are prepared for transfer through your current registrar. This is generally done by removing transfer locks and getting the necessary Auth codes.

Before You Begin

- Confirm the domain and registrant email are accessible.
- Record the current nameservers and DNS records.
- Check the domain's expiry date, lock status and any TLD-specific transfer rule.

Learn how to prepare domains for transfer in accounts sections of several popular registrars.

Once those preparations are made, simply follow the steps below to transfer your domains:

Note: Each domain has a unique Auth code and has to be unlocked for transfer separately on the current registrar side.

Log in to your NiceNIC account.
Go to the Transfer to Us page.
Click on Bulk options.

Enter the domain names and the Auth codes;

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

Click on Start Transfer at the bottom of the page.

Double-check the domain names and add them to Cart. To do this, you can use the Add all to cart button for convenience.
Proceed with the payment.

The transfer is completed automatically in 5-7 days for most domains. Once the transfer of your domains is completed you will receive the notifications on your NiceNIC Primary Email address, and the domains will become manageable in your Domain List.

Note: Due to technical reasons, it is only possible to submit the transfer for up to 500 domain names at once. If you need to transfer more than 10 domains, you can either submit several Bulk Transfer orders or contact our Support Team for assistance.

How to Check the Status of Your Domain Transfer

After initiating a domain transfer to Nicenic, you can monitor its progress directly in your account. This helps you know when the transfer is expected to complete without needing to contact support repeatedly.

Steps to View Transfer Status:

1. Log in to your NiceNIC account. Go to "My Products > Domain Names".
In the Status column, you will see your domain listed as:

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

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

Related NiceNIC Guides

What is SPF and How to Set Up SPF?

www.nicenic.com

SPF Guide

1. What is SPF?

Answer: SPF stands for Sender Policy Framework. SPF is an email authentication standard used to prevent email fraud and spam. It ensures the authenticity and reliability of email by verifying that the sender's domain name matches the source IP address of the email. SPF records are stored in the DNS record of the domain name and contain a list of servers that are allowed to send emails. When the recipient receives an email, it checks whether the sender's domain name has an SPF record and verifies whether the IP address of the sending server is in the allowed list. If the verification fails, the recipient may mark the email as spam or refuse to receive it. Using SPF can help improve the delivery rate and reliability of emails and reduce the amount of spam. At the same time, it can also enhance the security of the email system and prevent hackers and fraudsters from using forged domain names to send emails.

2. How to set up SPF for corporate mailboxes?

Answer:

1. Determine the outgoing server IP addresses of your corporate mailbox: These addresses will be added to the SPF record. 2. Log in to the DNS management console of your corporate mailbox: Usually provided by your domain name registrar or hosting provider

2. Create or edit a TXT record: In the DNS console, find the TXT record or similar option

3. Enter the SPF record: The format of the SPF record is "v=spf1 +a/+mx +ip4 +ip4:mail.example.com -all", where:

"v=spf1": specifies the SPF version

"a" or "mx": indicates that the server is allowed to be verified by the A record or MX record

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

"mail.coremail.cn": replaced with the domain name of your corporate mailbox

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

4. Save changes: Make sure the settings in the DNS console are saved correctly

3. How to set various types of SPF?

1) Make SPF record with domain name a record (take coremail.cn as an example)

v=spf1 a:coremail.cn2 -all

2) Make SPF record with domain name mx record

v=spf1 mx -all

3) Make SPF record with domain name ptr record

v=spf1 ptr -all

4) Make SPF record with export IP and IP segment settings

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

5) Introduce SPF records of other domain names (take spf.icoremail.net as an example)

v=spf1 include:spf.icoremail.net

Note: The above records can be used in combination, but only one pair of records starting with v=spf1 and ending with -all can appear in the entire txt. For example: v=spf1 mx ip4:106.52.172.248 include:spf.icoremail.net -all

Related NiceNIC Guides

How to verify certificate installation correctly

www.nicenic.com

How do I check my certificate was installed correctly?

To be sure that the certificate has been installed correctly and working properly, as well as that your customers are certain a secured connection is enabled and it covers data transmission through your website, you have the following indicators:

A padlock/tune icon available in the URL bar.
No error messages/ warnings occurred when connecting through https://yourdomain.tld.
A Site Seal provided by the Certificate Authority installed and visible.

Note : 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 norm, not the exception, and no longer serve as a trust indicator. As such, the tune icon itself will not be a trust indicator but will provide detailed information about a website's connection and settings. So moving forward, when using a Chrome browser, the primary indication of a successful SSL certificate installation on a site will be the absence of security warnings :

Frequently Asked Questions

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

The server or load balancer may still present the old certificate, another virtual host may be selected, or 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 and Download an SSL Certificate

How to install SSL certificates

SSL Certification in Four Simple Steps

www.nicenic.com

SSL Certification in Four Simple Steps

Quick Answer

Before You Begin

Identify every hostname the certificate must cover.
Confirm that you control DNS or the required validation channel.
Generate and securely retain the private key when a CSR is required.

NiceNIC Instructions

An SSL certificate must be activated after purchase. Installation instructions will be sent to you after activation. After that, you can use the NiceNIC Account Panel to manage your certificate. Buy It Start by purchasing the appropriate SSL certificate for your requirements. Select one of the categories mentioned above. Activate It You can instantly activate your SSL certificate after purchase through the Account Panel (or later, if you prefer.) During the activation process, the domain name and CSR code will be assigned.

Install It You will receive instructions on how to install your SSL certificate once it has been validated and issued. Please feel free to contact us by "Submit a Ticket" to ask for assistance in installing SSL certificate. Manage It Through your Account Panel, you can manage your SSL certificates, including renewal and reissuance.

How to Verify

Troubleshooting

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

Frequently Asked Questions

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

Submit a ticket when validation remains pending after the published records are visible, or when the NiceNIC order 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

Before You Begin

Identify every hostname the certificate must cover.
Confirm that you control DNS or the required validation channel.
Generate and securely retain the private key when a CSR is required.

Key Details

What is an SSL certificate and what is it used for?

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

Starting from 06/08/2014, Google announced that having an SSL certificate installed on your website would increase your ranking position, which is another great reason to use an SSL. The certificate itself represents base64 encoded data that contains information about the entity the certificate was issued for, public key required for encryption and digital signature verification, and 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 Authority, 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:

Types of SSL certificates SSL certificates can be divided into 3 validation groups: Domain Validation Certificates Requires a certificate applicant to prove his/her control over the domain name only. The issued certificate contains a domain name that was supplied to the Certification Authority within the certificate request. Organization Validation Certificates Requires a certificate applicant to prove that his/her company is a registered and legally accountable business, and to pass domain validation. The issued certificate contains a domain and company name of the certificate applicant.

Extended Validation Certificates Includes validation requirements of two validation types mentioned above and additional requirements. The issued certificate contains a domain and company name of the certificate applicant.

How to Verify

Troubleshooting

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

Frequently Asked Questions

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

Submit a ticket when validation remains pending after the published records are visible, or when the NiceNIC order does not provide the expected certificate files.

Related NiceNIC Guides

How to choose an SSL certificate

www.nicenic.com

How to Choose an SSL Certificate

Quick Answer

Before You Begin

Identify every hostname the certificate must cover.
Confirm that you control DNS or the required validation channel.
Generate and securely retain the private key when a CSR is required.

NiceNIC Instructions

How to install SSL certificates SSL certificate installation is typically performed by the hosting company that provides services for the domain. However, you may also choose install an SSL certificate yourself. Select your server type from the list below to find detailed instructions for installation. The SSL on your domain name was activated, please find and add the DNS records to complete the verification before you can download the certificate files through your control panel: My Account > My Products > SSL Certificates > Detail >….

After you complete the DNS-record validation, you can download the certificate files by the same approach. Installing SSL Certificate Notes If you host your domain name with NiceNIC, simply provide us with your certificate and we'll be happy to install it for you. Please note that on all NiceNIC, Shared Hosting servers, a special NiceNIC, SSL plugin installs a 1-year free PositiveSSL certificate automatically on the newly added subdomain or add-on. It works the same way for the main domain in the newly purchased hosting account.

The plugin can also be used for manual installation (in a few clicks) of PositiveSSL and EssentialSSL certificates. A dedicated IP address is required to install an SSL certificate. However, you may install your SSL certificate on a shared IP address using the Server Name Indication (SNI) protocol extension available in your cPanel. You can learn more about the differences between a dedicated IP and SNI technology in this article.

How to Verify

Troubleshooting

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

Frequently Asked Questions

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

Submit a ticket when validation remains pending after the published records are visible, or when the NiceNIC order 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 authority when you purchase an SSL certificate. You have to finish the renewal process starting thirty days before the expiration date, but before the actual expiry date. We will send you an email reminder during the renewal window if you choose NiceNIC.NET as your SSL provider.

How do I reissue my SSL certificate

www.nicenic.com

How to Reissue an SSL Certificate

Quick Answer

Before You Begin

Identify every hostname the certificate must cover.
Confirm that you control DNS or the required validation channel.
Generate and securely retain the private key when a CSR is required.

NiceNIC Instructions

? You must reissue your SSL encryption certificate if you switch hosting providers, think your CSR/RSA pair has been compromised, or change the domain name or domains that the SSL was issued for. Reissues may also be necessary if the certificate's contact information changes. You have to generate a new CSR/RSA pair and save your RSA for later installation in order to start the process. Make sure you store your RSA for use in the following installation steps. Usually, the user can handle this, but your hosting company might be able to help. Reissuing your SSL certificate is free at NiceNIC.

How to Verify

Troubleshooting

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

Frequently Asked Questions

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

Submit a ticket when validation remains pending after the published records are visible, or when the NiceNIC order 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)

Before You Begin

Sign in to the correct NiceNIC account.
Identify the exact domain or product affected.
Record current settings before making a change.

NiceNIC Instructions

What is a CSR? A CSR code (Certificate Signing Request) is a specific code and an essential part of the SSL activation process. It contains information about the website name and the company contact details. For many reasons, the code should be created on the hosting server end. For some servers, it is the obligatory condition. CSR generation instructions You can generate a Certificate Signing Request code yourself, e.g. if you manage the hosting server on your own or if this is the best option for your server type/hosting plan. In this case, select your web server from the list below and follow the instructions.

How to Verify

Confirm that the requested setting or order appears in the NiceNIC account, then test the dependent website, email, DNS or product function from a separate browser session or network.

Troubleshooting

The change was made in the wrong account or on the wrong product.
The panel saved the request but the downstream registry or service is still processing it.
A dependent DNS, email, browser cache or security setting still uses the old value.
The support ticket does not include the affected item, error message and time of failure.

Frequently Asked Questions

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

The normal process is described here, but account status, product state and registry or provider rules can change the available action.

How can I avoid delays?

Use accurate information, keep the account email accessible, save current settings, and include the exact product, time and error message in any support request.

When should I submit a ticket?

Submit a ticket when the required control is unavailable, the status remains pending after the stated checks, or the issue is account-specific.

Related NiceNIC Guides

What is EV certificate ecommerce advantage

www.nicenic.com

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

An SSL certificate binds a public key to one or more hostnames and enables authenticated, encrypted HTTPS connections.

What an SSL Certificate Provides

Encryption for data in transit
Authentication of the hostname
Integrity protection against undetected modification in transit

What It Does Not Provide

Protection from vulnerable website code
Malware removal
Account access control
A guarantee that the organization is trustworthy

Use It Correctly

Issue the certificate for the exact hostname, protect the private key, install the full chain, redirect users to HTTPS and renew or replace the certificate before expiration.

Frequently Asked Questions

How do I know the change worked?

Check the current status in your NiceNIC account, then test the service that depends on the SSL certificate. Do not rely only on the absence of an error message.

When should I contact NiceNIC Support?

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

Related NiceNIC Guides

If the issue continues after you complete these checks, submit a NiceNIC support ticket. Include the affected domain or product, the exact error message, the time of the issue and the troubleshooting already completed.

Certificate reissue reasons explained

www.nicenic.com

Why You May Need to Reissue an SSL Certificate

Quick Answer

Before You Begin

・ Identify every hostname the certificate must cover.

・ Confirm that you control DNS or the required validation channel.

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

Key Details

Why would I need to reissue my certificate? An SSL reissue is done to keep your site secure and private if it is moved, or some information on your SSL was changed. The reissue allows you to get a brand-new certificate code. The most typical reasons for certificate reissuance are: The existing certificate cannot be installed on the server.

For example, if the Private key (RSA Key) is lost/deleted or a "modulus mismatch" error appears during installation; The website has been moved to another web hosting server; Changing the hostnames secured by the certificate; Changes made to the organization details listed in the OV/EV certificate (only within 45 days since the initial certificate issuance); Use the remaining validity of your SSL if you purchased it for 2-5 years.

How to Verify

Troubleshooting

・ DNS validation records are missing, incorrect or added at the wrong DNS provider.

・ The certificate does not include the hostname being opened.

・ The private key does not match the certificate or CSR.

・ The server is missing an intermediate certificate or is still presenting the old certificate.

Frequently Asked Questions

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

Submit a ticket when validation remains pending after the published records are visible, or when the NiceNIC order does not provide the expected certificate files.

Related NiceNIC Guides

- How to Generate a CSR Code

- How to Activate and Download an SSL Certificate

- How to verify certificate installation correctly

- How to choose an SSL certificate

If the issue continues after you complete the checks above, submit a NiceNIC support ticket with the affected domain or product, the exact error message, the time of the issue and the troubleshooting already completed.

How to Activate and Download an SSL Certificate

www.nicenic.com

How to Activate and Download an SSL Certificate

Thank you for purchasing SSL with NiceNIC.

How to activate and download SSL certificate SSL installation is now even easier with our SSL installation service.

After the SSL certificate on your domain name was activated, please find and add the DNS records to complete the verification:

My Account > My Products > SSL Certificates > Detail > ....

This step requires extra care:

Fill each piece of information in the DNS Authentication Information shown below into its corresponding DNS record one by one.

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

My Account > My Products > SSL Certificates > Detail > Download certificate & Download private key

Still have problems?

- If your domain, server, or certificate details have changed, see Why You May Need to Reissue an SSL Certificate.

- If the current certificate cannot be used, follow How to Reissue an SSL Certificate.

- To prevent certificate expiration, read How to Renew an SSL Certificate.

If they didn't solve your issues, you can contact us here.

Common DNS Record Types: A, AAAA, CNAME, MX and TXT

www.nicenic.com

Common DNS Record Types: A, AAAA, CNAME, MX and TXT

TXT records publish verification and email-authentication policies. SPF, DKIM and DMARC serve different purposes and should be added exactly as supplied by the email provider.

What Each Record Does

SPF lists systems allowed to send mail for the domain.
DKIM publishes a public key used to verify signed messages.
DMARC tells receivers how to handle mail that fails alignment checks and where to send reports.

Add the Records

Confirm the domain uses NiceNIC nameservers.
Open My Products > Domain > DNS Records.
Add the TXT host and value supplied by the email provider.
For DKIM, use the selector host exactly as provided.
For DMARC, use _dmarc as the host unless the provider specifies another name.
Save the records and query them publicly.

Important SPF Rule

Publish one SPF policy per hostname. If multiple services send mail, combine their mechanisms into one record instead of creating several v=spf1 records.

Frequently Asked Questions

How do I know the change worked?

Check the current status in your NiceNIC account, then test the service that depends on the email-authentication records. Do not rely only on the absence of an error message.

When should I contact NiceNIC Support?

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

Related NiceNIC Guides

Why need SSL Certificates

www.nicenic.com

Why Do You Need an SSL Certificate?

An SSL certificate encrypts data between a client and server, authenticates the hostname and enables trusted HTTPS when it is correctly issued and installed.

What an SSL Certificate Provides

Encryption for data in transit
Authentication of the hostname
Integrity protection against undetected modification in transit

What It Does Not Provide

Protection from vulnerable website code
Malware removal
Account access control
A guarantee that the organization is trustworthy

Use It Correctly

Issue the certificate for the exact hostname, protect the private key, install the full chain, redirect users to HTTPS and renew or replace the certificate before expiration.

Frequently Asked Questions

How do I know the change worked?

Check the current status in your NiceNIC account, then test the service that depends on the SSL certificate. Do not rely only on the absence of an error message.

When should I contact NiceNIC Support?

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

Related NiceNIC Guides

How to Connect to your Email Client?

www.nicenic.com

How to Connect an Email Client to NiceNIC Business Email

Quick Answer

Confirm that the mailbox is active, the domain uses the required MX and authentication records, and the email client uses the correct server names, ports, encryption and full email address. Test both inbound and outbound mail after every change.

Before You Begin
- Confirm the Business Email order and mailbox are active.
- Check who manages DNS for the domain.
- Keep the full email address, password and required mail-server settings available.

1. Unable to connect via Email client via IMAP or SMTP:

When adding an email address in your Email client, i.e. iPhone, please firstly ensure you would fill in "c3.icoremail.net" for both the SMTP and IMAP email server. And secondly, please generate a password for the Email client separately by the following way:

Log in to your email account via "https://c3.icoremail.net/", select "Settings" in the left navigation bar, then choose "Generate Specific Password".

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

Common configurations are as follows:

Protocol type	Server address	Default port	Default port Encryption port (SSL)
SMTP	according to the actual address	25	465
POP	according to the actual address	110	995
IMAP	according to the actual address	143	993
PUSH	according to the actual address	80	443

Related NiceNIC Guides