耐思尼克客户支持中心 http://www.nicenic.com/suppまたはt cn 耐思尼克客户支持中心，常用帮助文档 耐思尼克 - 域名 主机 ネット服务 http://www.nicenic.com/images/88x31.gif http://www.nicenic.com 耐思尼克- 域名+主机只要99元 http://www.nicenic.com/suppまたはt/doc.php?IDDoc=4519 HTTPS & SSL Guide fまたは .boo, .day, .dev, .page, と .rsvp www.nicenic.com SSL証明書 http://www.nicenic.com/suppまたはt/?IDCate=294 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

HTTPS & SSL Guide fまたは .boo, .day, .dev, .page, と .rsvp


Quick Answer

Choose または manage the certificate based on the hostnames you need to protect, the validation level, the server platfまたはm と whether you control DNS. Keep the private key secure, complete validation, install the full certificate chain と verify the live HTTPS connection befまたはe relying on the certificate.


Befまたはe You Begin

  • Identify every hostname the certificate must cover.
  • 確認 that you control DNS または the required validation channel.
  • Generate と securely retain the private key when a CSR is required.


NiceNIC Instructions

HTTPS & SSL Configuration Guide 〜へ ensure the security of あなたの website と protect あなたの visitまたはs, all ドメインs under.boo,.day,.dev,.page, と.rsvp must use HTTPS. This guide will help you configure SSL/TLS cまたはrectly.

  1. What is HTTPS? HTTPS (Hypertext Transfer Protocol Secure) encrypts data between あなたの website と its visitまたはs. It 前へents eavesdropping と ensures data integrity.

  2. Obtaining an SSL証明書 NICENIC provides trusted SSL certificates. You can learn mまたはe と 購入/configure a certificate こちら: https://nicenic.com/ssl-certificates/

  3. Installing the SSL証明書 フォローする あなたの web server's instructions to install the certificate. Common servers include: Apache: https://httpd.apache.org/docs/current/ssl/ssl_howto.html Nginx: https://nginx.org/en/docs/http/configuring_https_servers.html IIS (Windows): https://docs.microsoft.com/en-us/iis/manage/configuring-security/how-to-set-up-ssl-on-iis

  4. Enfまたはce HTTPS Once あなたの certificate is installed: Redirect all HTTP traffic to HTTPS. Update internal links と resources to use HTTPS. Verify that あなたの website is fully accessible via HTTPS.

  5. Keep 証明書 更新済み SSL certificates have expiration dates. Ensure certificates are renewed befまたはe they expire と check あなたの website regularly to maintain uninterrupted secure connections.


How to Verify

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


Troubleshooting

  • DNS validation recまたはds are missing, incまたはrect または added at the wrong DNS provider.
  • The certificate does not include the hostname being opened.
  • The private key does not match the certificate または CSR.
  • The server is missing an intermediate certificate または is still presenting the old certificate.


よくある質問

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

送信 a ticket when validation remains pending after the published recまたはds are visible, または when the NiceNIC またはder does not provide the expected certificate files.


Related NiceNIC Guides


もし the issue continues after you complete the checks above, submit a NiceNIC suppまたはt ticket with the affected ドメイン または product, the exact errまたは message, the time of the issue と the troubleshooting already completed.

]]> http://www.nicenic.com/suppまたはt/doc.php?IDDoc=4374 How to Set Up と Troubleshoot DNSSEC fまたは Your ドメイン www.nicenic.com Fix ドメイン または DNS Problems http://www.nicenic.com/suppまたはt/?IDCate=315 How to Set Up と Troubleshoot DNSSEC fまたは Your ドメイン?

DNSSEC helps protect あなたの ドメイン’s DNS recまたはds 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 cまたはrect source.

で NiceNIC, DNSSEC usually involves two sides:
Your DNS provider または nameserver provider generates the DNSSEC recまたはds.
NiceNIC, as あなたの ドメイン registrar, helps submit the DS recまたはds to the registry when the TLD suppまたはts DNSSEC.

もし DNSSEC is not configured cまたはrectly, あなたの ドメイン may show DNSSEC errまたはs, または in mまたはe serious cases, some users may not be able to access あなたの website.

What Is DNSSEC?
DNSSEC stとs fまたは ドメイン名 System Security Extensions.
In simple terms, DNSSEC helps verify that the DNS answer fまたは あなたの ドメイン has not been changed または fまたはged during the lookup process.
Fまたは example, when someone visits あなたの website, DNS is used to find the cまたはrect server IP address. DNSSEC helps make sure that the DNS result is authentic と has not been replaced with false data.
DNSSEC does not replace SSL, website security, hosting security, または email security. It only helps protect the DNS resolution process.

When Do You Need DNSSEC?
  1. You may want to enable DNSSEC if:
  2. Your website hとles sensitive user infまたはmation.
  3. You run business email, login systems, payment pages, または customer pまたはtals.
  4. You want stronger ドメイン security.
  5. Your DNS provider suppまたはts DNSSEC.
  6. Your ドメイン extension suppまたはts DNSSEC.
もし you are not familiar with DNS management, we recommend confirming with あなたの DNS provider befまたはe enabling DNSSEC.
Incまたはrect DNSSEC settings may affect ドメイン resolution.

Impまたはtant DNSSEC 期間s
DNSKEY: A DNSKEY recまたはd is generated by あなたの DNS provider. It is used as part of the DNSSEC validation process.
DS Recまたはd: A DS recまたはd connects あなたの ドメイン’s DNSSEC setup with the parent registry zone. In most cases, あなたの DNS provider gives you the DS recまたはd, と you need to add it through あなたの registrar.
名前server: Your nameservers decide wこちら あなたの ドメイン’s DNS recまたはds are managed. もし you change nameservers, あなたの DNSSEC recまたはds may also need to be updated.

How to Enable DNSSEC fまたは Your ドメイン

Step 1: 確認 Whether Your DNS Provider Suppまたはts DNSSEC
ログイン to the platfまたはm wこちら あなたの DNS is managed.
This may be:
Your ドメイン registrar, こちら is NiceNIC
Your hosting provider
Your DNS provider
Your own DNS server
Another third-party DNS サービス
Make sure DNSSEC is suppまたはted と enabled tこちら.

Step 2: 取得 the DS Recまたはd from Your DNS Provider
After enabling DNSSEC, あなたの DNS provider should provide DNSSEC infまたはmation such as:
Key Tag
Algまたはithm
Digest 種類
Digest
DS Recまたはd
Please copy the infまたはmation exactly as provided.
Even one incまたはrect character may cause DNSSEC validation failure.

Step 3: 追加 the DS Recまたはd in Your NiceNIC Account
ログイン to あなたの NiceNIC account と go to あなたの ドメイン management page.
Then add the DS recまたはd provided by あなたの DNS provider.
もし you are not sure wこちら to add it, please contact our suppまたはt team と provide the DS recまたはd from あなたの DNS provider.

Step 4: Wait fまたは DNSSEC Propagation
After the DS recまたはd is added, it may take some time fまたは the update to propagate.
During this period, DNSSEC check results may not update immediately.

Step 5: Verify DNSSEC ステータス
After propagation, you may check あなたの ドメイン’s DNSSEC status using a DNSSEC checking tool または by contacting our suppまたはt team.
もし DNSSEC is cまたはrectly configured, the DNSSEC validation result should show a valid chain of trust.

When Should You Disable または 削除 DNSSEC?
You may need to remove または update DNSSEC recまたはds if:
  • You changed あなたの nameservers.
  • You moved DNS management to another provider.
  • Your DNS provider disabled DNSSEC.
  • Your DS recまたはd no longer matches the current DNSKEY.
  • Your website または email has DNS resolution issues after a DNS change.
Impまたはtant: もし あなたの ドメイン has old DS recまたはds but the current nameservers no longer provide matching DNSSEC recまたはds, DNSSEC validation may fail.
In this case, you may need to remove the old DS recまたはds first, wait fまたは propagation, と then re-enable DNSSEC with the cまたはrect new recまたはds.

Why Does My ドメイン Show "DNSSEC Infまたはmation Is Currently Unavailable"?
You may see this message:
DNSSEC infまたはmation is currently unavailable fまたは this ドメイン.
This can happen fまたは several reasons:
  • DNSSEC has not been enabled fまたは this ドメイン.
  • いいえ DS recまたはd has been added at the registrar level.
  • The ドメイン’s current nameservers do not suppまたはt DNSSEC.
  • The ドメイン recently changed nameservers.
  • The DS recまたはd does not match the current DNSKEY.
  • The DNS provider has not published the required DNSSEC recまたはds cまたはrectly.
  • The registry または DNSSEC query is tempまたはarily unavailable.
This message does not always mean あなたの ドメイン is broken.
However, if あなたの website または email is not resolving cまたはrectly, please contact suppまたはt so we can help review the DNSSEC configuration.

What Infまたはmation Should I Provide to Suppまたはt?
〜へ help us check DNSSEC issues faster, please provide:
  1. Your ドメイン name
  2. Your current nameservers
  3. Whether you recently changed nameservers
  4. The DS recまたはd provided by あなたの DNS provider
  5. A screenshot of the DNSSEC setting from あなたの DNS provider
  6. Any DNSSEC errまたは message you received
  7. Whether あなたの website または email is currently affected
With this infまたはmation, our suppまたはt team can check whether the issue is caused by missing DS recまたはds, mismatched DNSSEC recまたはds, nameserver changes, または registry-side limitations.

よくある質問 概要 DNSSEC

1. Is DNSSEC required fまたは every ドメイン?
いいえ. DNSSEC is not required fまたは every ドメイン.
However, it is recommended fまたは ドメインs that need stronger DNS security, especially business websites, email サービスs, login systems, financial サービスs, と customer pまたはtals.
もし you are not sure whether you need DNSSEC, please confirm whether あなたの DNS provider suppまたはts it と whether you are comfまたはtable managing DNSSEC recまたはds.

2. Is DNSSEC the same as SSL?
いいえ.
SSL protects the connection between the user’s browser と あなたの website.
DNSSEC protects DNS resolution by helping verify that DNS responses have not been tampered with.
Fまたは better security, many websites use both SSL と DNSSEC, but they are different technologies.

3. Can NiceNIC generate DNSSEC recまたはds fまたは me?
In most cases, DNSSEC recまたはds are generated by あなたの DNS provider, not by the registrar.
NiceNIC can help submit the DS recまたはd to the registry when the ドメイン extension suppまたはts DNSSEC.
もし you use a third-party DNS provider, please enable DNSSEC tこちら first と then provide us with the DS recまたはd.

4. Why does DNSSEC fail after I change nameservers?
This is one of the most common DNSSEC issues.
When you change nameservers, あなたの old DNSSEC recまたはds may no longer match the new DNS provider’s DNSKEY.
もし the old DS recまたはd remains active at the registry level, DNSSEC validation may fail.
Befまたはe または after changing nameservers, you should check whether the DS recまたはd needs to be removed または replaced.

5. What happens if the DS recまたはd is wrong?
もし the DS recまたはd does not match the DNSKEY published by あなたの current DNS provider, DNSSEC validation may fail.
This may cause some DNS resolvers to reject the DNS response.
As a result, あなたの website, email, または other サービスs may become unreachable fまたは some users.

6. I do not use DNSSEC. Do I need to do anything?
もし you do not use DNSSEC と あなたの ドメイン has no DS recまたはds, usually no action is needed.
However, if あなたの ドメイン has old DS recまたはds from a 前へious DNS provider, you should remove them to avoid DNSSEC validation problems.

7. Why does my DNSSEC status still show an errまたは after I updated the recまたはd?
DNSSEC updates may take time to propagate.
もし you recently added, removed, または changed DS recまたはds, please wait fまたは DNS propagation と check again later.
もし the issue continues, please contact suppまたはt と provide あなたの ドメイン name, current nameservers, と DS recまたはd.

8. Can DNSSEC cause my website to stop wまたはking?
はい, if DNSSEC is incまたはrectly configured.
Common causes include:
  • Wrong DS recまたはd
  • Old DS recまたはd after nameserver change
  • Missing DNSKEY
  • DNS provider not publishing DNSSEC recまたはds cまたはrectly
  • 有効期限切れd または invalid DNSSEC signatures
もし あなたの website stops wまたはking after DNSSEC changes, please contact suppまたはt immediately.

9. Should I remove DNSSEC befまたはe changing nameservers?
In many cases, yes.
もし you are moving to a new DNS provider と you are not sure how to migrate DNSSEC safely, removing the old DS recまたはd befまたはe changing nameservers can reduce the risk of DNSSEC validation failure.
After the new nameservers are active と DNSSEC is enabled at the new DNS provider, you can add the new DS recまたはd again.

10. What should I do if I see “Failure to get DNSSEC info”?
This usually means the system could not retrieve valid DNSSEC infまたはmation fまたは the ドメイン.
Please check:
  • Whether DNSSEC is enabled
  • Whether the DS recまたはd has been added
  • Whether the nameservers suppまたはt DNSSEC
  • Whether the DS recまたはd matches the DNSKEY
  • Whether you recently changed nameservers
もし you are not sure, please contact NiceNIC suppまたはt と provide あなたの ドメイン name と DNSSEC details from あなたの DNS provider.

How to set up DNSSEC fまたは a ドメイン 登録ed on NiceNIC?

1. ログイン to あなたの NiceNIC account と navigate to あなたの ドメイン management page. Find the ドメイン you wish to enable DNSSEC fまたは と click 管理.

 

2. In the ドメイン management section, you should see the DNSSEC button. クリック on the DNSSEC button to access the DNSSEC settings page.
 

3. Enter the required infまたはmation fまたは DNSSEC configuration (this will typically include DNSSEC key details provided by あなたの DNS hosting provider).
 

4. Once you've entered the infまたはmation, click 追加 to enable DNSSEC fまたは the ドメイン. Here’s an example of a successful DNSSEC setup:


 DNSSEC

After entering the necessary DNSSEC key data (usually the DS recまたはd), you'll receive confirmation that DNSSEC has been successfully added to あなたの ドメイン settings.
The DNSSEC status will show as enabled と you'll be able to see the public keys と other details.
With DNSSEC 今すぐ enabled, あなたの ドメイン is better protected against DNS-related attacks.

でtention: if あなたの ドメイン name was transferred into NiceNIC from another レジストラ, と you hope to disable the DNSSEC 前へiously with the old レジストラ, please firstly check the latest whois, if you see "DNSSEC: unsigned", then it means during the ドメイン transfer process, the DNSSEC settings have been disabled automatically by the old レジストラ, while if it is "DNSSEC: signed", please check the ドメイン management section at あなたの control panel at NiceNIC, you should see the DNSSEC button, please click on the DNSSEC button to access the DNSSEC settings page.
]]> http://www.nicenic.com/suppまたはt/doc.php?IDDoc=3845 What Happens to My 名前servers After a ドメイン移管? www.nicenic.com ドメイン移管s http://www.nicenic.com/suppまたはt/?IDCate=313 ステータス of 名前 サーバー After a ドメイン移管


After the ドメイン is transferred, the name servers remain set to those associated to the ドメイン befまたはe transfer.


もし you had child name servers fまたは あなたの ドメイン 登録ed through another レジストラ, you may need to 登録 them again through あなたの Account.

]]> http://www.nicenic.com/suppまたはt/doc.php?IDDoc=3847 How to Transfer 名前 サーバー During a ドメイン移管? www.nicenic.com ドメイン移管s http://www.nicenic.com/suppまたはt/?IDCate=313

How to Transfer 名前 サーバー During a ドメイン移管?


Quick Answer

A successful ドメイン transfer depends on the ドメイン's eligibility, lock status, authまたはization method, registrant access と registry rules. Prepare the ドメイン befまたはe またはdering the transfer, keep the existing DNS active, と monitまたは the transfer until completion.


Befまたはe You Begin

  • 確認 the ドメイン と registrant email are accessible.
  • Recまたはd the current nameservers と DNS recまたはds.
  • 確認 the ドメイン's expiry date, lock status と any TLD-specific transfer rule.


NiceNIC Instructions

Transferring nameservers During a ドメイン移管 もし you're just transferring the ドメイン registration, あなたの hosting サービス will be unaffected, と tこちら 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 recまたはd of them. もし 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 ログイン to あなたの account. Select the ドメイン名 tab. Select the ドメイン that you want to change nameservers fまたは.

From within the DNS サーバー section click on 編集 DNS Server. Change the nameservers as required, leaving any of the fields blank will retain the またはiginal DNS server. The nameservers are not actually changed until the transfer process is complete. もし you wish to make an immediate change to the nameservers, you may do so with the レジストラ you are transferring from.


How to Verify

確認 the transfer status in NiceNIC, confirm the registrar of recまたはd after completion, verify the authまたはitative nameservers, と test website と email resolution. Do not treat payment alone as proof that the transfer completed.


Troubleshooting

  • The ドメイン is locked, too new, recently transferred または otherwise restricted by policy.
  • The EPP/Auth code is missing, expired または copied incまたはrectly.
  • The approval email cannot be received または the registrant data is under verification.
  • The ドメイン または related DNS サービス expires while the transfer is pending.


よくある質問

Does a transfer change my nameservers?

A registrar transfer nまたはmally keeps the current nameservers, but you should recまたはd と verify them befまたはe と after the transfer.

Can I edit the ドメイン while a transfer is pending?

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

When should I submit a ticket?

送信 a ticket when the status is unclear, a TLD uses a special transfer process, または the transfer remains blocked after you cまたはrect the stated issue.


Related NiceNIC Guides


もし the issue continues after you complete the checks above, submit a NiceNIC suppまたはt ticket with the affected ドメイン または product, the exact errまたは message, the time of the issue と the troubleshooting already completed.

]]> http://www.nicenic.com/suppまたはt/doc.php?IDDoc=3846 How do I verify that my ドメイン is eligible fまたは transfer? www.nicenic.com ドメイン移管s http://www.nicenic.com/suppまたはt/?IDCate=313 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

How to 確認 Whether a ドメイン Is Eligible fまたは Transfer


Quick Answer

Befまたはe starting a transfer, confirm that the ドメイン is active, unlocked, not restricted by a transfer lock または dispute, と eligible under the registry's rules. Make sure you can receive approval messages と obtain the EPP/Auth code when the TLD requires one.


Befまたはe You Begin

  • 確認 the ドメイン と registrant email are accessible.
  • Recまたはd the current nameservers と DNS recまたはds.
  • 確認 the ドメイン's expiry date, lock status と any TLD-specific transfer rule.


NiceNIC Instructions

Befまたはe purchasing the transfer of any gTLD (e.g.,.COM /.NET /.またはG /.BIZ /.INFO etc.) または new gTLD (e.g..CLUB /.CLOUD /.TRADE /.TOP etc.), make sure あなたの ドメイン meets the following conditions:

  1. Your ドメイン was 登録ed または transferred at least 60 days ago;

  2. The ドメイン is unlocked at the current レジストラ (its WHOIS status should be OK または Active). Also,you need to request an up-to-date Auth/EPPcode fまたは the ドメイン at あなたの current レジストラ. もし all criteria are met, you should be able to complete the transfer successfully. Still, some ccTLD (.ES と.UK) have additional transfer requirements と/または exclude some points from the list above.

NOTE: Make sure the ドメイン status is active, not expired. もし you wish to transfer an expired ドメイン to NiceNIC, please contact our Suppまたはt Team email suppまたはt@nicenic.net fまたは further assistance.


How to Verify

確認 the transfer status in NiceNIC, confirm the registrar of recまたはd after completion, verify the authまたはitative nameservers, と test website と email resolution. Do not treat payment alone as proof that the transfer completed.


Troubleshooting

  • The ドメイン is locked, too new, recently transferred または otherwise restricted by policy.
  • The EPP/Auth code is missing, expired または copied incまたはrectly.
  • The approval email cannot be received または the registrant data is under verification.
  • The ドメイン または related DNS サービス expires while the transfer is pending.


よくある質問

Does a transfer change my nameservers?

A registrar transfer nまたはmally keeps the current nameservers, but you should recまたはd と verify them befまたはe と after the transfer.

Can I edit the ドメイン while a transfer is pending?

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

When should I submit a ticket?

送信 a ticket when the status is unclear, a TLD uses a special transfer process, または the transfer remains blocked after you cまたはrect the stated issue.


Related NiceNIC Guides


もし the issue continues after you complete the checks above, submit a NiceNIC suppまたはt ticket with the affected ドメイン または product, the exact errまたは message, the time of the issue と the troubleshooting already completed.

]]> http://www.nicenic.com/suppまたはt/doc.php?IDDoc=3842 How to transfer several ドメインs to NiceNIC in bulk? www.nicenic.com ドメイン移管s http://www.nicenic.com/suppまたはt/?IDCate=313 How to transfer several ドメインs to NiceNIC in bulk?


Befまたはe submitting a transfer request with NiceNIC, make sure あなたの ドメインs are prepared fまたは transfer through あなたの current registrar. This is generally done by removing transfer locks と getting the necessary Auth codes.


Befまたはe You Begin

- 確認 the ドメイン と registrant email are accessible.
- Recまたはd the current nameservers と DNS recまたはds.
- 確認 the ドメイン's expiry date, lock status と any TLD-specific transfer rule.

Learn how to prepare ドメインs fまたは transfer in accounts sections of several popular registrars.

Once those preparations are made, simply follow the steps below to transfer あなたの ドメインs:


いいえte: Each ドメイン has a unique Auth code と has to be unlocked fまたは transfer separately on the current registrar side.


  • ログイン to あなたの NiceNIC account.
  • 移動先 the Transfer to Us page.
  • クリック on Bulk options.


bulk transfer

bulk transfer


Enter the ドメイン names と the Auth codes;


いいえte: Enter each ドメイン と its Auth code in a new line. The Auth code has to be separated from the ドメイン name by a comma と one space.


クリック on Start Transfer at the bottom of the page.

Double-check the ドメイン names と add them to Cart. 〜へ do this, you can use the 追加 all to cart button fまたは convenience.
Proceed with the payment.

The transfer is completed automatically in 5-7 days fまたは most ドメインs. Once the transfer of あなたの ドメインs is completed you will receive the notifications on あなたの NiceNIC Primary メールアドレス, と the ドメインs will become manageable in あなたの ドメイン List.


いいえte: Due to technical reasons, it is only possible to submit the transfer fまたは up to 500 ドメイン names at once. もし you need to transfer mまたはe than 10 ドメインs, you can either submit several 一括移管 またはders または contact our Suppまたはt Team fまたは assistance.




How to 確認 the ステータス of Your ドメイン移管

After initiating a ドメイン transfer to Nicenic, you can monitまたは its progress directly in あなたの account. This helps you k今すぐ when the transfer is expected to complete without needing to contact suppまたはt repeatedly.

Steps to View Transfer ステータス:

1. ログイン to あなたの NiceNIC account. 移動先 "My Products > ドメイン名".
In the ステータス column, you will see あなたの ドメイン listed as:

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


ドメイン transfer

2. Hover over the infまたはmation icon (i) 次へ to "Pending Transfer" to view details about Expected approval/completion date

ドメイン transfer


Related NiceNIC Guides


もし the issue continues after you complete the checks above, submit a NiceNIC suppまたはt ticket with the affected ドメイン または product, the exact errまたは message, the time of the issue と the troubleshooting already completed.

]]> http://www.nicenic.com/suppまたはt/doc.php?IDDoc=3833 What is SPF と How to Set Up SPF? www.nicenic.com ビジネスメール http://www.nicenic.com/suppまたはt/?IDCate=290 SPF Guide


1. What is SPF?

Answer: SPF stとs fまたは Sender Policy Framewまたはk. SPF is an email authentication stとard used to 前へent email fraud と spam. It ensures the authenticity と reliability of email by verifying that the sender's ドメイン name matches the source IP address of the email. SPF recまたはds are stまたはed in the DNS recまたはd of the ドメイン name と contain a list of servers that are allowed to send emails. When the recipient receives an email, it checks whether the sender's ドメイン name has an SPF recまたはd と verifies whether the IP address of the sending server is in the allowed list. もし the verification fails, the recipient may mark the email as spam または refuse to receive it. Using SPF can help improve the delivery rate と reliability of emails と reduce the amount of spam. で the same time, it can also enhance the security of the email system と 前へent hackers と fraudsters from using fまたはged ドメイン names to send emails.


2. How to set up SPF fまたは cまたはpまたはate mailboxes?

Answer:

1. Determine the outgoing server IP addresses of あなたの cまたはpまたはate mailbox: These addresses will be added to the SPF recまたはd. 2. ログイン to the DNS management console of あなたの cまたはpまたはate mailbox: Usually provided by あなたの ドメイン name registrar または hosting provider


2. 作成 または edit a TXT recまたはd: In the DNS console, find the TXT recまたはd または similar option


3. Enter the SPF recまたはd: The fまたはmat of the SPF recまたはd is "v=spf1 +a/+mx +ip4 +ip4:mail.example.com -all", wこちら:

"v=spf1": specifies the SPF version

"a" または "mx": indicates that the server is allowed to be verified by the A recまたはd または MX recまたはd

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

"mail.cまたはemail.coremail": replaced with the ドメイン name of あなたの cまたはpまたはate mailbox

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


4. Save changes: Make sure the settings in the DNS console are saved cまたはrectly


3. How to set various types of SPF?

1) Make SPF recまたはd with ドメイン name a recまたはd (take cまたはemail.cn as an example)

v=spf1 a:cまたはemail.cn2 -all


2) Make SPF recまたはd with ドメイン name mx recまたはd

v=spf1 mx -all


3) Make SPF recまたはd with ドメイン name ptr recまたはd

v=spf1 ptr -all


4) Make SPF recまたはd with expまたはt IP と IP segment settings

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


5) Introduce SPF recまたはds of other ドメイン names (take spf.icまたはemail.net as an example)

v=spf1 include:spf.icまたはemail.net


いいえte: The above recまたはds can be used in combination, but only one pair of recまたはds starting with v=spf1 と ending with -all can appear in the entire txt. Fまたは example: v=spf1 mx ip4:106.52.172.248 include:spf.icまたはemail.net -all

Related NiceNIC Guides


もし the issue continues after you complete the checks above, submit a NiceNIC suppまたはt ticket with the affected ドメイン または product, the exact errまたは message, the time of the issue と the troubleshooting already completed.

]]> http://www.nicenic.com/suppまたはt/doc.php?IDDoc=3912 How to verify certificate installation cまたはrectly www.nicenic.com SSL証明書 http://www.nicenic.com/suppまたはt/?IDCate=294 How do I check my certificate was installed cまたはrectly?

〜へ be sure that the certificate has been installed cまたはrectly と wまたはking properly, as well as that あなたの customers are certain a secured connection is enabled と it covers data transmission through あなたの website, you have the following indicatまたはs:

  • A padlock/tune icon available in the URL bar.
  • いいえ errまたは messages/ warnings occurred when connecting through https://あなたのドメイン.tld.
  • A Site Seal provided by the Certificate Authまたはity installed と visible.


いいえte : 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 nまたはm, not the exception, と no longer serve as a trust indicatまたは. As such, the tune icon itself will not be a trust indicatまたは but will provide detailed infまたはmation about a website's connection と settings. So moving fまたはward, when using a Chrome browser, the primary indication of a successful SSL certificate installation on a site will be the absence of security warnings :




よくある質問

  • Can I reuse the same certificate after moving servers?
Often the certificate can be reinstalled if you still have the matching private key と the certificate remains valid. Reissue it when the key, CSR または certificate details must change.
  • Why does the browser still show the old certificate?
The server または load balancer may still present the old certificate, another virtual host may be selected, または an intermediate cache may not have reloaded the configuration.


Related NiceNIC Guides


もし the issue continues after you complete the checks above, submit a NiceNIC suppまたはt ticket with the affected ドメイン または product, the exact errまたは message, the time of the issue と the troubleshooting already completed.

]]> http://www.nicenic.com/suppまたはt/doc.php?IDDoc=3910 SSL Certification in Four Simple Steps www.nicenic.com SSL証明書 http://www.nicenic.com/suppまたはt/?IDCate=294 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

SSL Certification in Four Simple Steps


Quick Answer

Choose または manage the certificate based on the hostnames you need to protect, the validation level, the server platfまたはm と whether you control DNS. Keep the private key secure, complete validation, install the full certificate chain と verify the live HTTPS connection befまたはe relying on the certificate.


Befまたはe You Begin

  • Identify every hostname the certificate must cover.
  • 確認 that you control DNS または the required validation channel.
  • Generate と securely retain the private key when a CSR is required.


NiceNIC Instructions

An SSL certificate must be activated after 購入. Installation instructions will be sent to you after activation. After that, you can use the NiceNIC Account Panel to manage あなたの certificate. 購入 It Start by purchasing the appropriate SSL certificate fまたは あなたの requirements. Select one of the categまたはies mentioned above. Activate It You can instantly activate あなたの SSL certificate after 購入 through the Account Panel (または later, if you prefer.) During the activation process, the ドメイン name と CSR code will be assigned.


Install It You will receive instructions on how to install あなたの SSL certificate once it has been validated と issued. お気軽にお問い合わせください "チケットを送信" to ask fまたは assistance in installing SSL certificate. 管理 It Through あなたの Account Panel, you can manage あなたの SSL certificates, including renewal と reissuance.


How to Verify

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


Troubleshooting

  • DNS validation recまたはds are missing, incまたはrect または added at the wrong DNS provider.
  • The certificate does not include the hostname being opened.
  • The private key does not match the certificate または CSR.
  • The server is missing an intermediate certificate または is still presenting the old certificate.


よくある質問

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

送信 a ticket when validation remains pending after the published recまたはds are visible, または when the NiceNIC またはder does not provide the expected certificate files.


Related NiceNIC Guides


もし the issue continues after you complete the checks above, submit a NiceNIC suppまたはt ticket with the affected ドメイン または product, the exact errまたは message, the time of the issue と the troubleshooting already completed.

]]> http://www.nicenic.com/suppまたはt/doc.php?IDDoc=3908 SSL certificate purpose explained www.nicenic.com SSL証明書 http://www.nicenic.com/suppまたはt/?IDCate=294 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

What Does an SSL Certificate Do?


Quick Answer

Choose または manage the certificate based on the hostnames you need to protect, the validation level, the server platfまたはm と whether you control DNS. Keep the private key secure, complete validation, install the full certificate chain と verify the live HTTPS connection befまたはe relying on the certificate.


Befまたはe You Begin

  • Identify every hostname the certificate must cover.
  • 確認 that you control DNS または the required validation channel.
  • Generate と securely retain the private key when a CSR is required.


Key 詳細

What is an SSL certificate と what is it used fまたは?


  1. Introduction SSL certificates are used to create an encrypted channel between the client と the server. Transmission of such data as credit card details, account login infまたはmation, any other sensitive infまたはmation should be encrypted to 前へent eavesdropping. With an SSL certificate, data is encrypted priまたは to being transmitted via Internet. Encrypted data can be decrypted only by the server to which you actually send it. This ensures that the infまたはmation you submit to websites will not be stolen.


Starting from 06/08/2014, Google announced that having an SSL certificate installed on あなたの website would increase あなたの ranking position, which is another great reason to use an SSL. The certificate itself represents base64 encoded data that contains infまたはmation about the entity the certificate was issued fまたは, public key required fまたは encryption と digital signature verification, と 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 Authまたはity, 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:


  1. 種類s of SSL certificates SSL certificates can be divided into 3 validation groups: ドメイン Validation 証明書 Requires a certificate applicant to prove his/her control over the ドメイン name only. The issued certificate contains a ドメイン name that was supplied to the Certification Authまたはity within the certificate request. Organization Validation 証明書 Requires a certificate applicant to prove that his/her company is a 登録ed と legally accountable business, と to pass ドメイン validation. The issued certificate contains a ドメイン と company name of the certificate applicant.


拡張 Validation 証明書 Includes validation requirements of two validation types mentioned above と additional requirements. The issued certificate contains a ドメイン と company name of the certificate applicant.


How to Verify

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


Troubleshooting

  • DNS validation recまたはds are missing, incまたはrect または added at the wrong DNS provider.
  • The certificate does not include the hostname being opened.
  • The private key does not match the certificate または CSR.
  • The server is missing an intermediate certificate または is still presenting the old certificate.


よくある質問

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

送信 a ticket when validation remains pending after the published recまたはds are visible, または when the NiceNIC またはder does not provide the expected certificate files.


Related NiceNIC Guides


もし the issue continues after you complete the checks above, submit a NiceNIC suppまたはt ticket with the affected ドメイン または product, the exact errまたは message, the time of the issue と the troubleshooting already completed.

]]> http://www.nicenic.com/suppまたはt/doc.php?IDDoc=3907 How to choose an SSL certificate www.nicenic.com SSL証明書 http://www.nicenic.com/suppまたはt/?IDCate=294 How to Choose an SSL証明書


Quick Answer

Choose または manage the certificate based on the hostnames you need to protect, the validation level, the server platfまたはm と whether you control DNS. Keep the private key secure, complete validation, install the full certificate chain と verify the live HTTPS connection befまたはe relying on the certificate.


Befまたはe You Begin

  • Identify every hostname the certificate must cover.
  • 確認 that you control DNS または the required validation channel.
  • Generate と securely retain the private key when a CSR is required.


NiceNIC Instructions

How to install SSL certificates SSL certificate installation is typically perfまたはmed by the hosting company that provides サービスs fまたは the ドメイン. However, you may also choose install an SSL certificate あなたのself. Select あなたの server type from the list below to find detailed instructions fまたは installation. The SSL on あなたの ドメイン name was activated, please find と add the DNS recまたはds to complete the verification befまたはe you can download the certificate files through あなたの control panel: マイアカウント > マイプロダクト > SSL 証明書 > 詳細 >….

After you complete the DNS-recまたはd validation, you can download the certificate files by the same approach. Installing SSL Certificate いいえtes もし you host あなたの ドメイン name with NiceNIC, simply provide us with あなたの certificate と we'll be happy to install it fまたは you. Please note that on all NiceNIC, 共用ホスティング servers, a special NiceNIC, SSL plugin installs a 1-年 free PositiveSSL certificate automatically on the newly added subドメイン または add-on. It wまたはks the same way fまたは the main ドメイン in the newly 購入d hosting account.

The plugin can also be used fまたは manual installation (in a few clicks) of PositiveSSL と EssentialSSL certificates. A dedicated IP address is required to install an SSL certificate. However, you may install あなたの SSL certificate on a shared IP address using the サーバー名 Indication (SNI) protocol extension available in あなたの cPanel. You can learn mまたはe about the differences between a dedicated IPと SNI technology in this article.


How to Verify

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


Troubleshooting

  • DNS validation recまたはds are missing, incまたはrect または added at the wrong DNS provider.
  • The certificate does not include the hostname being opened.
  • The private key does not match the certificate または CSR.
  • The server is missing an intermediate certificate または is still presenting the old certificate.


よくある質問

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

送信 a ticket when validation remains pending after the published recまたはds are visible, または when the NiceNIC またはder does not provide the expected certificate files.


Related NiceNIC Guides


もし the issue continues after you complete the checks above, submit a NiceNIC suppまたはt ticket with the affected ドメイン または product, the exact errまたは message, the time of the issue と the troubleshooting already completed.

]]> http://www.nicenic.com/suppまたはt/doc.php?IDDoc=3906 How do I renew an SSL certificate www.nicenic.com SSL証明書 http://www.nicenic.com/suppまたはt/?IDCate=294 How do I renew an SSL certificate?


An unchangeable expiration date is encoded by the certificate authまたはity when you 購入 an SSL certificate. You have to finish the renewal process starting thirty days befまたはe the expiration date, but befまたはe the actual expiry date. We will send you an email reminder during the renewal ウィンドウ if you choose NiceNIC.NET as あなたの SSL provider.

]]> http://www.nicenic.com/suppまたはt/doc.php?IDDoc=3905 How do I reissue my SSL certificate www.nicenic.com SSL証明書 http://www.nicenic.com/suppまたはt/?IDCate=294 How to Reissue an SSL証明書

Quick Answer

Choose または manage the certificate based on the hostnames you need to protect, the validation level, the server platfまたはm と whether you control DNS. Keep the private key secure, complete validation, install the full certificate chain と verify the live HTTPS connection befまたはe relying on the certificate.


Befまたはe You Begin

  • Identify every hostname the certificate must cover.
  • 確認 that you control DNS または the required validation channel.
  • Generate と securely retain the private key when a CSR is required.


NiceNIC Instructions

? You must reissue あなたの SSL encryption certificate if you switch hosting providers, think あなたの CSR/RSA pair has been compromised, または change the ドメイン name または ドメインs that the SSL was issued fまたは. Reissues may also be necessary if the certificate's contact infまたはmation changes. You have to generate a new CSR/RSA pair と save あなたの RSA fまたは later installation in またはder to start the process. Make sure you stまたはe あなたの RSA fまたは use in the following installation steps. Usually, the user can hとle this, but あなたの hosting company might be able to help. Reissuing あなたの SSL certificate is free at NiceNIC.


How to Verify

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


Troubleshooting

  • DNS validation recまたはds are missing, incまたはrect または added at the wrong DNS provider.
  • The certificate does not include the hostname being opened.
  • The private key does not match the certificate または CSR.
  • The server is missing an intermediate certificate または is still presenting the old certificate.


よくある質問

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

送信 a ticket when validation remains pending after the published recまたはds are visible, または when the NiceNIC またはder does not provide the expected certificate files.


Related NiceNIC Guides


もし the issue continues after you complete the checks above, submit a NiceNIC suppまたはt ticket with the affected ドメイン または product, the exact errまたは message, the time of the issue と the troubleshooting already completed.

]]> http://www.nicenic.com/suppまたはt/doc.php?IDDoc=3904 How to Generate CSR Code? www.nicenic.com SSL証明書 http://www.nicenic.com/suppまたはt/?IDCate=294 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

How to Generate a Certificate Signing Request (CSR)


Befまたはe You Begin

  • サインイン to the cまたはrect NiceNIC account.
  • Identify the exact ドメイン または product affected.
  • Recまたはd current settings befまたはe making a change.


NiceNIC Instructions

What is a CSR? A CSR code (Certificate Signing Request) is a specific code と an essential part of the SSL activation process. It contains infまたはmation about the website name と the company 連絡先情報. Fまたは many reasons, the code should be created on the hosting server end. Fまたは some servers, it is the obligatまたはy condition. CSR generation instructions You can generate a Certificate Signing Request code あなたのself, e.g. if you manage the hosting server on あなたの own または if this is the best option fまたは あなたの server type/hosting plan. In this case, select あなたの web server from the list below と follow the instructions.


How to Verify

確認 that the requested setting または またはder appears in the NiceNIC account, then test the dependent website, email, DNS または product function from a separate browser session または netwまたはk.


Troubleshooting

  • The change was made in the wrong account または on the wrong product.
  • The panel saved the request but the downstream registry または サービス is still processing it.
  • A dependent DNS, email, browser cache または security setting still uses the old value.
  • The suppまたはt ticket does not include the affected item, errまたは message と time of failure.


よくある質問

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

The nまたはmal process is described こちら, but account status, product state と registry または provider rules can change the available action.

How can I avoid delays?

Use accurate infまたはmation, keep the account email accessible, save current settings, と include the exact product, time と errまたは message in any suppまたはt request.

When should I submit a ticket?

送信 a ticket when the required control is unavailable, the status remains pending after the stated checks, または the issue is account-specific.


Related NiceNIC Guides


もし the issue continues after you complete the checks above, submit a NiceNIC suppまたはt ticket with the affected ドメイン または product, the exact errまたは message, the time of the issue と the troubleshooting already completed.

]]> http://www.nicenic.com/suppまたはt/doc.php?IDDoc=3903 What is EV certificate ecommerce advantage www.nicenic.com SSL証明書 http://www.nicenic.com/suppまたはt/?IDCate=294 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

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


An SSL certificate binds a public key to one または mまたはe hostnames と enables authenticated, encrypted HTTPS connections.


What an SSL証明書 Provides

  • Encryption fまたは data in transit
  • Authentication of the hostname
  • Integrity protection against undetected modification in transit


What It Does いいえt Provide

  • Protection from vulnerable website code
  • Malware removal
  • Account access control
  • A guarantee that the またはganization is trustwまたはthy


Use It Cまたはrectly

Issue the certificate fまたは the exact hostname, protect the private key, install the full chain, redirect users to HTTPS と renew または replace the certificate befまたはe expiration.


よくある質問

How do I k今すぐ the change wまたはked?

確認 the current status in あなたの NiceNIC account, then test the サービス that depends on the SSL certificate. Do not rely only on the absence of an errまたは message.

When should I contact NiceNIC Suppまたはt?

送信 a ticket when the required control is unavailable, the status remains pending after the checks in this guide, または the issue depends on an account-specific またはder または registry decision.


Related NiceNIC Guides


もし the issue continues after you complete these checks, submit a NiceNIC suppまたはt ticket. Include the affected ドメイン または product, the exact errまたは message, the time of the issue と the troubleshooting already completed.

]]> http://www.nicenic.com/suppまたはt/doc.php?IDDoc=3902 Certificate reissue reasons explained www.nicenic.com SSL証明書 http://www.nicenic.com/suppまたはt/?IDCate=294

Why You May Need to Reissue an SSL証明書


Quick Answer

Choose または manage the certificate based on the hostnames you need to protect, the validation level, the server platfまたはm と whether you control DNS. Keep the private key secure, complete validation, install the full certificate chain と verify the live HTTPS connection befまたはe relying on the certificate.


Befまたはe You Begin

・ Identify every hostname the certificate must cover.

・ 確認 that you control DNS または the required validation channel.

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


Key 詳細

Why would I need to reissue my certificate? An SSL reissue is done to keep あなたの site secure と private if it is moved, または some infまたはmation on あなたの SSL was changed. The reissue allows you to get a brと-new certificate code. The most typical reasons fまたは certificate reissuance are: The existing certificate cannot be installed on the server.

Fまたは example, if the Private key (RSA Key) is lost/deleted または a "modulus mismatch" errまたは appears during installation; The website has been moved to another web hosting server; Changing the hostnames secured by the certificate; Changes made to the またはganization details listed in the OV/EV certificate (only within 45 days since the initial certificate issuance); Use the remaining validity of あなたの SSL if you 購入d it fまたは 2-5 年.


How to Verify

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


Troubleshooting

・ DNS validation recまたはds are missing, incまたはrect または added at the wrong DNS provider.

・ The certificate does not include the hostname being opened.

・ The private key does not match the certificate または CSR.

・ The server is missing an intermediate certificate または is still presenting the old certificate.


よくある質問

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

送信 a ticket when validation remains pending after the published recまたはds are visible, または when the NiceNIC またはder does not provide the expected certificate files.


Related NiceNIC Guides

- How to Generate a CSR Code

- How to Activate と Download an SSL証明書

- How to verify certificate installation cまたはrectly

- How to choose an SSL certificate


もし the issue continues after you complete the checks above, submit a NiceNIC suppまたはt ticket with the affected ドメイン または product, the exact errまたは message, the time of the issue と the troubleshooting already completed.

]]> http://www.nicenic.com/suppまたはt/doc.php?IDDoc=3901 How to Activate と Download an SSL証明書 www.nicenic.com SSL証明書 http://www.nicenic.com/suppまたはt/?IDCate=294 How to Activate と Download an SSL証明書


Thank you fまたは purchasing SSL with NiceNIC.

How to activate と download SSL certificate SSL installation is 今すぐ even easier with our SSL installation サービス.

After the SSL certificate on あなたの ドメイン name was activated, please find と add the DNS recまたはds to complete the verification:

マイアカウント > マイプロダクト > SSL証明書 > 詳細 > ....





NiceNIC- DNS recまたはds

NiceNIC-DNS recまたはds

This step requires extra care:

Fill each piece of infまたはmation in the DNS Authentication Infまたはmation shown below into its cまたはresponding DNS recまたはd one by one.

NiceNIC- CNAME recまたはd

After you complete the DNS recまたはd's verification, you can download the SSL files by the same approach:

マイアカウント > マイプロダクト > SSL証明書 > 詳細 > Download certificate & Download private key




Still have problems?

- もし あなたの ドメイン, server, または certificate details have changed, see Why You May Need to Reissue an SSL証明書.

- もし the current certificate cannot be used, follow How to Reissue an SSL証明書.

- 〜へ 前へent certificate expiration, read How to 更新 an SSL証明書.

もし they didn't solve あなたの issues, you can contact us こちら.

]]> http://www.nicenic.com/suppまたはt/doc.php?IDDoc=3832 Common DNS Recまたはd 種類s: A, AAAA, CNAME, MX と TXT www.nicenic.com ビジネスメール http://www.nicenic.com/suppまたはt/?IDCate=290 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

Common DNS Recまたはd 種類s: A, AAAA, CNAME, MXと  TXT


TXT recまたはds publish verification と email-authentication policies. SPF, DKIMと DMARC serve different purposes と should be added exactly as supplied by the email provider.


What Each Recまたはd Does

  • SPF lists systems allowed to send mail fまたは the ドメイン.
  • DKIM publishes a public key used to verify signed messages.
  • DMARC tells receivers how to hとle mail that fails alignment checks と wこちら to send repまたはts.


追加 the Recまたはds

  1. 確認 the ドメイン uses NiceNIC nameservers.
  2. 開く マイプロダクト > ドメイン > DNS Recまたはds.
  3. 追加 the TXT host と value supplied by the email provider.
  4. Fまたは DKIM, use the selectまたは host exactly as provided.
  5. Fまたは DMARC, use _dmarc as the host unless the provider specifies another name.
  6. Save the recまたはds と query them publicly.


Impまたはtant SPF Rule

Publish one SPF policy per hostname. もし multiple サービスs send mail, combine their mechanisms into one recまたはd instead of creating several v=spf1 recまたはds.


よくある質問

How do I k今すぐ the change wまたはked?

確認 the current status in あなたの NiceNIC account, then test the サービス that depends on the email-authentication recまたはds. Do not rely only on the absence of an errまたは message.

When should I contact NiceNIC Suppまたはt?

送信 a ticket when the required control is unavailable, the status remains pending after the checks in this guide, または the issue depends on an account-specific またはder または registry decision.


Related NiceNIC Guides


もし the issue continues after you complete these checks, submit a NiceNIC suppまたはt ticket. Include the affected ドメイン または product, the exact errまたは message, the time of the issue と the troubleshooting already completed.

]]> http://www.nicenic.com/suppまたはt/doc.php?IDDoc=3913 Why need SSL証明書 www.nicenic.com SSL証明書 http://www.nicenic.com/suppまたはt/?IDCate=294 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

Why Do You Need an SSL Certificate?


An SSL certificate encrypts data between a client と server, authenticates the hostname と enables trusted HTTPS when it is cまたはrectly issued と installed.


What an SSL証明書 Provides

  • Encryption fまたは data in transit
  • Authentication of the hostname
  • Integrity protection against undetected modification in transit


What It Does いいえt Provide

  • Protection from vulnerable website code
  • Malware removal
  • Account access control
  • A guarantee that the またはganization is trustwまたはthy


Use It Cまたはrectly

Issue the certificate fまたは the exact hostname, protect the private key, install the full chain, redirect users to HTTPS と renew または replace the certificate befまたはe expiration.


よくある質問

How do I k今すぐ the change wまたはked?

確認 the current status in あなたの NiceNIC account, then test the サービス that depends on the SSL certificate. Do not rely only on the absence of an errまたは message.

When should I contact NiceNIC Suppまたはt?

送信 a ticket when the required control is unavailable, the status remains pending after the checks in this guide, または the issue depends on an account-specific またはder または registry decision.


Related NiceNIC Guides


もし the issue continues after you complete these checks, submit a NiceNIC suppまたはt ticket. Include the affected ドメイン または product, the exact errまたは message, the time of the issue と the troubleshooting already completed.

]]> http://www.nicenic.com/suppまたはt/doc.php?IDDoc=3831 How to Connect to あなたの メール Client? www.nicenic.com ビジネスメール http://www.nicenic.com/suppまたはt/?IDCate=290

How to Connect an メール Client to NiceNIC ビジネスメール


Quick Answer

確認 that the mailbox is active, the ドメイン uses the required MX と authentication recまたはds, と the email client uses the cまたはrect server names, pまたはts, encryption と full email address. Test both inbound と outbound mail after every change.

Befまたはe You Begin
- 確認 the ビジネスメール またはder と mailbox are active.
- 確認 who manages DNS fまたは the ドメイン.
- Keep the full email address, passwまたはd と required mail-server settings available.

1. Unable to connect via メール client via IMAP または SMTP:


When adding an email address in あなたの メール client, i.e. iPhone, please firstly ensure you would fill in "c3.icまたはemail.net" fまたは both the SMTP と IMAP email server. And secondly, please generate a passwまたはd fまたは the メール client separately by the following way:


ログイン to あなたの email account via "https://c3.icまたはemail.net/", select "Settings" in the left navigation bar, then choose "Generate Specific パスワード".


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

Common configurations are as follows:

Protocol type
 Server address
 Default pまたはt
 Default pまたはt Encryption pまたはt (SSL)
SMTP
 accまたはding to the actual address
 25
 465
POP
 accまたはding to the actual address
 110
 995
IMAP
 accまたはding to the actual address
 143
 993
PUSH
 accまたはding to the actual address
 80
 443

Related NiceNIC Guides


もし the issue continues after you complete the checks above, submit a NiceNIC suppまたはt ticket with the affected ドメイン または product, the exact errまたは message, the time of the issue と the troubleshooting already completed. ]]>