耐思尼克客户支持中心 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. ]]>