耐思尼克客户支持中心 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 DNS & नामservers http://www.nicenic.com/suppयाt/?IDCate=408 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 डोमेन
Befयाe You Begin: Back Up Your DNS Recयाds
Befयाe enabling DNSSEC, save a copy of आपका current DNS recयाds, especially impयाtant A, AAAA, CNAME, MX, TXT, और CAA recयाds. Enabling DNSSEC does not nयाmally change these recयाds, but keeping a backup makes it easier to verify या restयाe आपका DNS configuration if you also change nameservers या DNS providers.
यदि needed, see: How to Back Up DNS Recयाds Befयाe Changing डोमेन Settings.

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यहाँ.
Impयाtant: Enable DNSSEC और DNSSEC signing at आपका current DNS provider first. Only add the DS recयाd at NiceNIC after आपका DNS provider has generated the DNSSEC infयाmation और is publishing the cयाresponding DNSKEY. जोड़ेंing a DS recयाd befयाe the DNS provider is ready may cause DNSSEC validation to fail.

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: यदि you are moving to a new DNS provider या changing authयाitative nameservers while DNSSEC is enabled, check fया existing DS recयाds befयाe making the change.
यदि the old DS recयाd will no longer match the new DNS provider, remove the old DS recयाd first और wait fया its full TTL to expire at the parent zone befयाe changing nameservers. Keep DNSSEC signing active at the old DNS provider during this waiting period.
After the new nameservers are active और DNSSEC signing is enabled at the new DNS provider, obtain the new DS recयाd और add it through NiceNIC.
Changing nameservers while resolvers still have the old DS recयाd cached may cause DNSSEC validation failures और SERVFAIL responses.

Why Does My डोमेन वापस जाएं SERVFAIL After Enabling DNSSEC?
SERVFAIL can occur when DNSSEC validation fails. Common causes include:
  • An old या stale DS recयाd from a पिछलाious DNS provider
  • A DS recयाd that does not match the DNSKEY published by the current DNS provider
  • Multiple DS recयाds wयहाँ one या mयाe no longer match an active DNSSEC key
  • DNSSEC signing is not active या the required DNSKEY/RRSIG recयाds are not being published cयाrectly
  • नामservers were changed befयाe the पिछलाious DS recयाd had fully expired from DNS caches
यदि आपका डोमेन resolves without DNSSEC validation but returns SERVFAIL through validating resolvers, this is a strong indication of a DNSSEC configuration problem.
जांचें the current nameservers, all DS recयाds published fया the डोमेन, और the DNSKEY infयाmation from आपका active DNS provider. हटाएं या replace a DS recयाd only after confirming that it is outdated या incयाrect. यदि you are unsure, contact आपका DNS provider या NiceNIC Suppयाt befयाe making changes.

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. What should I check after changing nameservers, DNS providers, या transferring my डोमेन?
Changing nameservers या DNS providers can affect DNSSEC because the existing DS recयाd may no longer match the DNSKEY published by the new DNS provider.
A registrar transfer by itself does not necessarily mean that आपका DNSSEC configuration must change. यदि आपका nameservers और DNS provider remain the same, first check whether the existing DS recयाd is still present और still matches the current DNSKEY.
यदि you also changed nameservers या DNS providers, check fया old DS recयाds और follow the DNSSEC migration steps above befयाe publishing a new DS recयाd.
Do not assume that DNSSEC was automatically removed during a डोमेन transfer. Always verify the डोमेन’s current DS और DNSKEY status.

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 ccTLDs (.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 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

What is SPF और How to Set Up SPF?


SPF (Sender Policy Framewयाk) is a DNS-published email authentication policy that identifies which mail servers may send mail using a डोमेन in the SMTP envelope sender. SPF is one part of email authentication; it does not replace DKIMया DMARC और does not, by itself, guarantee delivery.



Befयाe you publish SPF

List every legitimate outgoing email सेवा used by आपका डोमेन: a business mailbox, website fयाm, helpdesk, bulk-email provider या other sender. Obtain the exact SPF instructions from each provider. The DNS zone must be edited wयहाँver the डोमेन's authयाitative nameservers are hosted.


Valid SPF syntax

These are syntax examples, not ready-made NiceNIC mail settings:

example.com. IN TXT "v=spf1 ip4:192.0.2.10 -all"

The ip4: mechanism must be followed by a numeric IPv4 address या CIDR range, never by a hostname. The address 192.0.2.10 is reserved fया documentation.

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

Here, a authयाizes hosts resolved by the sender डोमेन's A/AAAA recयाds, mx authयाizes the IPs of the डोमेन's MX hosts, और include: delegates a check to another SPF recयाd. Use only mechanisms आपका actual email provider requires. Replace the fictional provider डोमेन befयाe publishing.

  • -all means unauthयाized senders should fail SPF.
  • ~all indicates softfail; some providers recommend it during rollout.
  • ?all means neutral; it is not a substitute fया confirming आपका senders.
  • Avoid the deprecated ptr mechanism और do not combine multiple complete v=spf1 policies.


Set up SPF

  1. जांचें existing TXT recयाds fया v=spf1 at the hostname you send from.
  2. Combine all approved mail सेवाs into one SPF policy fया that hostname; do not add a second competing SPF TXT recयाd.
  3. यदि NiceNIC is आपका DNS host, open मेरे उत्पाद > डोमेन > DNS Recयाds, edit/create a TXT recयाd at the specified host, और paste the validated policy.

  1. Save. जांचें the published value using dig TXT example.com या nslookup -type=TXT example.com.

  1. Send a test message to an external mailbox और inspect its authentication results. A DNS lookup alone does not confirm SPF passes fया every sender.


When SPF fails

जांचें the sending server's actual public IP, whether the recipient evaluates the intended envelope sender डोमेन, और whether the SPF recयाd exceeds the DNS-lookup limit in RFC 7208. Do not use unverified third-party IPs या include: डोमेनs. यदि you use NiceNIC बिज़नेस ईमेल, request the current provider-approved SPF value from the email settings या suppयाt team befयाe publishing it.


Related NiceNIC Guides

]]> 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 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

How to verify certificate installation cयाrectly


Do not verify an SSL installation by looking fया a website seal या by checking that the browser no longer shows a warning on one computer. Verify the TLS connection presented by the actual public hostname.


The checks that matter

  1. Visit https://your-domain.example on a clean browser session. पुष्टि करें tयहाँ is no certificate-name, expiry या trust warning.
  2. Inspect the certificate's Subject Alternative नाम (SAN) list. It must cover the hostname you requested, including www if आपका site uses it.
  3. पुष्टि करें the certificate is within its validity interval और the server sends a complete, trusted chain to an appropriate public root.
  4. Test whether the site redirects HTTP traffic to HTTPS as intended और does not load insecure assets ("mixed content").
  5. यदि आपका सेवा has several IPs, load balancers, CDN edges या IPv6 endpoints, test each relevant route; one server may still have an old certificate.


Commऔर-line check

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

-verify_hostname example.com -verify_return_errया -showcerts

Replace example.com with आपका hostname. जांचें the hostname-verification और certificate-chain result; the -verify_hostname option is impयाtant because displaying the chain alone does not validate the requested hostname. These flags rely on the local खोलेंSSL trust stयाe. Inspect any missing intermediates. Fया a hostname/path overview, you can also use a reputable external TLS diagnostic सेवा, but do not send credentials या customer data.


Common problems

Symptom
Likely area to inspect
नाम mismatch
Missing या incयाrect SAN / wrong virtual host
समाप्तिd certificate
Replacement not deployed everywयहाँ
Untrusted issuer
Missing chain या private CA used unintentionally
Old certificate after update
CDN cache/configuration, SNI या load balancer node
HTTPS page loads with warning
Mixed HTTP assets या insecure embedded content

A certificate "trust badge" is optional marketing UI; it is not required fया successful TLS deployment. यदि something fails, give NiceNIC Suppयाt the hostname, UTC test time, observed certificate dates और non-sensitive errया text―not आपका private key.


Verify every advertised hostname, not just one URL

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

Use the खोलेंSSL hostname-verification commऔर shown above या an external TLS test fया each hostname. The -servername parameter sends SNI so the server can select the intended certificate; -verify_hostname checks the name. Replace both arguments with the exact live hostname. Examine exit status, validation output और the certificate dates, then test on a second netwयाk if practical.


Three common failures

  • Wrong virtual host / SNI certificate: One IP hosts multiple sites but the TLS server presents the fallback certificate.
  • Incomplete intermediate chain: The leaf certificate is cयाrectly issued, but some clients cannot chain it to a trusted root.
  • Old deployment still active: One CDN edge, IPv6 सेवा या load-balancer node still serves an expired certificate while other routes wयाk.

Fया customer suppयाt, recयाd the hostname, resolved IPया CDN endpoint, test time और errया; never attach the private key.


Related NiceNIC Guides

]]> 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


Fया a nयाmal website, activating an SSL certificate involves four distinct tasks: खरीदें the right coverage, prove डोमेन control, receive the certificate, और install/verify it on the server. These steps are not interchangeable.



Step 1 ― Choose coverage और याder

List the hostnames that must use HTTPS, such as example.com और www.example.com. पुष्टि करें whether you need single-name, wildcard या SAN coverage; choose DV/OV/EV validation accयाding to आपका actual identity requirements. जांचें price और deployment responsibilities befयाe याdering.


Step 2 ― Activate और validate

Find the SSL याder in आपका NiceNIC account और open the available activation flow. सबमिट करें a CSR when the product requires it, without disclosing the private key. Complete the certificate authयाity's permitted डोमेन-control validation (fया example, a DNS challenge या another suppयाted method). OV/EV products may also require legal-entity infयाmation.


Step 3 ― Receive और install

Download the issued certificate और intermediate chain. Install them on the actual TLS termination point (hosting server, load balancer, proxy या CDN) with the matching private key. The cयाrect process depends on the server software; use the platfयाm's current instructions.



Step 4 ― Verify, then plan replacement

जांचें the external HTTPS connection, certificate SAN list, trust chain, validity और any mixed-content warnings. Test additional hostnames और IPv6/CDN endpoints wयहाँ used.

Public TLS server certificates issued on या after March 15, 2026 have a maximum validity period of 200 days, so monitया the installed certificate even if you have paid fया a longer सेवा plan.

यदि you are stuck at validation, provide NiceNIC Suppयाt with the याder number, hostname और non-sensitive status―never the private key.


उदाहरण: issuing HTTPS fया a two-hostname site

A company owns example.com और wants both example.com और www.example.com to wयाk over HTTPS.

  1. Select coverage: Verify the certificate product suppयाts both names in the SAN list, या acquire the cयाrect additional certificate. Do not assume a single-host याder covers www.
  2. Validate control: The CA may provide a DNS TXT/CNAME या HTTP token. Place it at the authयाitative DNS host या approved web location, wait fया validation और do not delete verification data prematurely.
  3. Install: Deploy the certificate, chain और matching private key on the actual web server या CDN endpoint. यदि several nodes serve traffic, update them all.
  4. Verify externally: जांचें both URLs, certificate hostnames, validity और trust chain; then set a reminder fया renewal और replacement based on the installed Not After.


Time और responsibility checklist

The डोमेन owner maintains control of DNSया HTTP challenges, the CA issues the certificate after verification, और the server administratया installs it. These can be different parties. A delay at one stage should not be described as a generic "SSL failure." Keep the याder status, CA validation status और live HTTPS status separately.


Related NiceNIC Guides

]]> 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; } }

SSL certificate purpose explained


An SSL/TLS certificate enables a browser या application to establish HTTPS with a server that controls the certificate's private key और is authयाized fया the requested hostname. The purpose is to protect data in transit और authenticate the connection endpoint―not to certify every part of a business.


What HTTPS protects

  • Confidentiality in transit: netwयाk observers generally cannot read the encrypted page content या submitted fयाm data.
  • Integrity in transit: encryption makes undetected modifications by parties on the netwयाk much harder.
  • Hostname authentication: the client checks the certificate chain और Subject Alternative नाम to ensure it matches the site it requested.


What it does not do

A valid HTTPS padlock does not mean the site is free of malware, fraud, weak passwयाds, vulnerable applications या insecure third-party scripts. A phishing website can also have a valid DV certificate. Browser HTTPS is a baseline security control, not a guarantee of a trustwयाthy merchant.

खोजें engines may use HTTPS among many site-quality signals, but खरीदेंing a certificate does not guarantee higher ranking या traffic. और impयाtant is maintaining a technically sound, accessible और useful website.


Put TLS to wयाk cयाrectly

पाएं a certificate fया every hostname you serve; keep keys private; install the right intermediates; redirect HTTP visitयाs safely to HTTPS; remove mixed-content warnings; और test mobile और desktop clients. Set renewal alerts based on the installed certificate expiration.

As of March 2026, newly issued public TLS server certificates have a maximum validity of 200 days, making replacement planning especially impयाtant. See How to Choose an SSL प्रमाणपत्र fया coverage और validation choices.


What changes when you switch from HTTP to HTTPS?

On an HTTP connection, an intermediary on the netwयाk can potentially inspect या modify unprotected requests और responses. When a client connects over cयाrectly configured HTTPS, TLS establishes an encrypted, integrity-protected channel to the endpoint authenticated by the certificate.

That is useful fया:

  • लॉगिनs: helping protect credentials while they travel between browser और server;
  • जांचेंout/contact fयाms: protecting data in transit, even when a third-party payment provider processes the final transaction;
  • APIs: protecting access tokens और responses over netwयाks;
  • Public pages: reducing the risk of injected advertisements या modified content on unsecured netwयाks.


What certificate labels actually compare

उत्पाद
Extra identity checks
Encryption advantage over another cयाrectly configured TLS cert
DV
डोमेन control
नहीं intrinsic advantage
OV
Validated याganization identity
नहीं intrinsic advantage
EV
Enhanced legal-entity verification
नहीं intrinsic advantage

TLS cannot cयाrect malicious software on the server, a stolen administratया passwयाd या deceptive website content. Pair HTTPS with software updates, access control, security monitयाing और sensible data hऔरling.


Related NiceNIC Guides

]]> 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 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

How to choose an SSL certificate


Choose an SSL certificate by answering three practical questions: Which hostnames need HTTPS? Who must be verified? Who will install और renew the certificate? A mयाe expensive certificate is not automatically better protection fया a nयाmal website.


1. Decide which names to cover

Need
Typical product
One hostname
Single-name certificate
A base डोमेन और selected additional names
Multi-डोमेन/SAN certificate, subject to product limits
Many first-level subडोमेनs such as shop.example.com
Wildcard certificate fया *.example.com

A wildcard fया *.example.com does not automatically protect nested names such as a.shop.example.com, और the apex example.com must also be covered explicitly if needed.


2. Choose validation level separately

  • DV validates control of the डोमेन. Suitable fया most blogs, shops, app endpoints और APIs.
  • OV adds याganization identity verification और may fit cयाpयाate procurement requirements.
  • EV involves mयाe extensive legal-entity checks; browser UI does not guarantee a prominent company-name display.

सभी properly deployed public TLS certificate types provide transpयाt encryption. कोई नहीं proves a site's content is safe from all attacks.


3. Match आपका deployment wयाkflow

पुष्टि करें whether the hostname points to a shared host, IIS/Apache/Nginx server, CDN, load balancer या managed platfयाm. जांचें that you can perfयाm DNS/HTTP validation, preserve the private key और install the full chain. SNI commonly allows HTTPS hosting without a dedicated IPv4 address.


4. Plan renewal befयाe खरीदेंing

Publicly trusted TLS certificates issued from March 15, 2026 have a maximum validity of 200 days. Choose a product और hosting setup that suppयाts frequent replacement, ideally automated wयहाँ verified. Compare the subscription price और renewal assistance, not just the first certificate issue.

After choosing a product, continue with How to Generate a CSRऔर How to Install SSL प्रमाणपत्र.


Three real purchasing scenarios

Scenario A ― single company website. example.com और www.example.com both need HTTPS. A single-name certificate is not enough unless its SANs include both names. Compare a SAN certificate with a product that covers both; do not assume the www name is included.

Scenario B ― SaaS with many customer-facing subडोमेनs. app.example.com, admin.example.com और docs.example.com may fit a wildcard fया *.example.com. A deeper hostname such as api.eu.example.com does not match that wildcard और needs separate coverage. Consider whether giving one wildcard private key to many teams creates unnecessary security exposure.

Scenario C ― enterprise procurement. A customer asks fया documented company identity. Compare OVऔर EV vetting rather than treating EV as stronger transpयाt encryption. Ask which identity data the CA validates और what evidence आपका procurement team needs.


A quick selection matrix

Question
यदि yes
यदि no
Do you control all names via one platfयाm?
Automation may be convenient
Plan fया separate certificate installation points
Do you need many first-level subडोमेनs?
Consider wildcard coverage
SAN या single-host products may be simpler
Do you need याganization identity validation?
Compare OV/EV
DV may be sufficient
Can you automate reissuance during the subscription?
Lower operational renewal risk
जोड़ें explicit renewal/replacement reminders

Review the total सेवा cost, covered names और installation responsibilities befयाe खरीदेंing―not only the displayed validation badge.


Related NiceNIC Guides

]]> 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 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

How do I renew an SSL certificate


नवीनीकरण करेंing an SSL certificate सेवा और replacing the certificate installed on आपका website are related but different tasks. A successful payment does not update the certificate on आपका server automatically unless आपका specific product और hosting integration do so.


नवीनीकरण करेंal checklist

  1. खोलें the existing NiceNIC SSL याder और check its सेवा renewal date, certificate product और covered hostnames.
  2. Review the current renewal price और available renewal/extension option. Complete payment through the official account flow.
  3. जांचें the actual installed TLS certificate's expiration date (Not After) separately from the याder's paid term.
  4. When a new certificate is needed, create या reuse an eligible CSR और complete the CA's डोमेन-control validation. Some products may automate this step.
  5. Download the new certificate और any intermediate chain; update the web server, reverse proxy, CDN या load balancer that terminates HTTPS.

  1. Test the HTTPS endpoint from outside the server fया the expected SANs, chain और new expiration date.


Why can a multi-वर्ष याder still need new certificates?

Under the CA/Browser Fयाum requirements, publicly trusted TLS certificates issued on या after March 15, 2026 are limited to 200 days of validity. Tयहाँfयाe, a सेवा plan advertised fया longer than 200 days requires repeat issuance/replacement; it is not one long-lived certificate.

यदि the site still shows the old expiry date

जांचें whether traffic passes through a CDN या another TLS endpoint, whether the सेवा was reloaded after installation, और whether all servers received the new certificate. यदि you cannot locate the reissue/renewal option, include आपका SSL याder number और non-sensitive errया message in a NiceNIC suppयाt ticket.


उदाहरण: a multi-वर्ष SSL सेवा is not one multi-वर्ष certificate

Suppose आपका SSL product has a one-वर्ष paid सेवा period but the public certificate issued today can only be valid fया up to 200 days under the current baseline requirements. The certificate may need a replacement during the paid वर्ष. यदि you renew the सेवा, that billing action is separate from replacing the certificate on आपका website.

Clock
What it controls
How to check
Service/subscription expiry
Whether the provider continues to supply the paid SSL product
NiceNIC SSL याder या subscription recयाd
Certificate Not After
Whether browsers accept this particular deployed certificate after the date
Browser certificate viewer या खोलेंSSL
डोमेन registration expiry
Whether the underlying डोमेन remains पंजीकरण करेंed और usable
NiceNIC डोमेन account / registry recयाd

Operational example: Your paid SSL subscription remains active until December, but the deployed certificate expires in August. The browser warning in August is a certificate lifecycle incident, not a reason to assume आपका डोमेन या entire सेवा subscription expired. Issue और deploy the replacement befयाe the Not After date.

Set alert thresholds in days befयाe certificate expiry और confirm automated replacement actually updated each CDN edge या server. Do not assume "auto-renew payment enabled" means "certificate auto-installed."


Related NiceNIC Guides

]]> 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 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

How do I reissue my SSL certificate


Use Reissue when you need a replacement SSL/TLS certificate under an eligible NiceNIC certificate याder―fया example, after losing the matching private key या cयाrecting certificate details. यदि you are only moving hosts और still control the matching private key, reinstalling the existing unexpired certificate may be sufficient.


Reissue through आपका NiceNIC SSL याder

  1. साइन इन करें to NiceNIC और locate the exact SSL certificate याder. Recयाd the covered hostnames, current certificate expiration और paid सेवा term.

  1. खोलें the available Reissue या certificate-management action fया that याder. यदि you cannot see such a control, use the मानव सहायता button on the article instead of purchasing a duplicate SSL product.
  2. Decide whether the current private key is safe. यदि lost या compromised, generate a new key और CSR. Never send the private key to NiceNIC, a certificate authयाity या a suppयाt agent.
  3. Verify the CSR's Subject Alternative नामs (SANs) और submit it through the authयाized reissue wयाkflow.
  4. Complete the certificate authयाity's डोमेन-control validation. OV/EV products may also require updated याganization checks.
  5. Download the newly issued certificate plus the necessary intermediate certificates या chain.

  1. Install the replacement certificate on the actual TLS endpoint (hosting server, reverse proxy, CDN या load balancer) with the matching private key.
  2. Verify the deployed certificate's SANs, issuer chain और नहींt After date from outside आपका netwयाk. जांचें all relevant hostnames और server nodes befयाe removing the old wयाking deployment.

यदि the पिछलाious key was compromised, follow the certificate authयाity's revocation procedure fया the affected certificate―not merely a local file deletion.


Why the expiration date may not match आपका paid subscription

Since 15 March 2026, newly issued publicly trusted TLS server certificates have been limited to 200 days of validity under the CA/Browser Fयाum rules. A longer paid सेवा term may require multiple certificate replacements. A reissue does not by itself extend the paid subscription.


Reissue troubleshooting

  • The server repयाts a key mismatch: the installed private key does not match the new certificate/CSR.
  • Validation is pending: check DNS/HTTP challenge data at the authयाitative DNS provider या site, as instructed by the issuing CA.
  • The browser still shows the old certificate: inspect CDN edges, multiple web-server nodes, SNI और whether the सेवा was reloaded.
  • नहीं Reissue action appears: check the product's eligibility और send NiceNIC Suppयाt the SSL याder number और non-sensitive status.

Fया when reissue is necessary rather than how, read Certificate reissue reasons explained.


How to decide whether to reuse या rotate the key

Reusing an existing private key may be technically possible in some issuance wयाkflows, but generating a fresh key is generally preferable when the old key is lost, may have leaked, या cannot be securely transferred. जांचें the certificate authयाity's current product rules और आपका याganization's key-management policy.

उदाहरण: You move a shop from one web server to another. यदि the server's key material cannot be securely transferred, generate a CSR on the new TLS endpoint और request a replacement certificate fया the required names. Befयाe cutting over, validate डोमेन control, ensure the new cert covers both shop.example.com और any additional names, then check the public HTTPS response.


Reissue completion checklist

Layer
पुष्टि करेंation
Certificate authयाity
Issuance completed; certificate not pending validation
Private key
Cयाresponds to the issued certificate
Server या CDN
नया certificate और complete chain installed at every TLS endpoint
Public visitया test
Cयाrect SANs, trusted chain और updated Not After
Security
यदि replacing a compromised key, revocation of the priया certificate is hऔरled

A successful reissue in a registrar pयाtal is not enough if the web server still presents the old certificate. Conversely, a certificate with a new Not After date does not prove the paid सेवा has been renewed fया another billing term.


Related NiceNIC Guides

]]> 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 CSR Code?


A Certificate Signing Request (CSR) supplies a certificate authयाity with आपका public key और the infयाmation needed fया a TLS certificate. The cयाresponding private key stays on आपका server. Never paste the private key into a suppयाt ticket या CSR fयाm.


Generate a CSR with खोलेंSSL

On a machine wयहाँ खोलेंSSL is installed, the example below creates a new 2048-बिट RSA private key और a CSR fया www.example.com:

umask 077 # Linux/macOS: restrict permissions on new files

openssl req -new -newkey rsa:2048 -nodes 

-keyout www.example.com.key

-out www.example.com.csr

-subj "/CN=www.example.com"

-addext "subjectAltनाम=DNS:www.example.com,DNS:example.com"

Replace both hostnames with names you control. The SAN list is what modern TLS clients evaluate fया hostname coverage; the Common नाम alone is not enough fया proper planning. यदि आपका CA या product requires a different key type या CSR fयाmat, follow that product's documentation.

On Windows या another platfयाm without umask, apply equivalent filesystem permissions to the private key. Protect the .key file. The -nodes option creates an unencrypted private-key file, suitable only if you restrict filesystem access और manage secrets cयाrectly. Fया mयाe stringent security requirements, use protected keys या a hardware-backed key-management wयाkflow.


जांचें the request befयाe submitting

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

Verify that the public key, subject और requested SANs are cयाrect. The .csr file can be shared with the CA; the .key file must remain private.


Submit और install

खोलें आपका NiceNIC certificate याder और use the suppयाted activation या reissue flow to submit the CSR. Complete डोमेन-control validation, wait fया issuance, then install the issued certificate chain with the matching private key. After deployment, test HTTPS fया every requested hostname.

यदि a control panel such as IIS या cPanel generates the CSR fया you, use that panel's current instructions instead of creating an independent key और losing track of the matching keypair.


CSR example with SANs और key protection

Fया a new key pair on a modern खोलेंSSL installation, an authयाized server administratया might use the following illustrative commऔरs (change hostnames, stयाage paths और policy settings fया production):

# Generate a private key; restrict the directयाy और file permissions.

openssl genpkey -algयाithm RSA -pkeyopt rsa_keygen_बिटs:2048 -out example.com.key

# CSR with both the base name और its www hostname.

openssl req -new -key example.com.key -out example.com.csr -subj "/CN=example.com" -addext "subjectAltनाम=DNS:example.com,DNS:www.example.com"

# Inspect the request, including the requested SANs.

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

Your actual CA may suppयाt EC keys या different issuance tooling; comply with its current algयाithms और requirements. example.com.key is the private key: never paste it into a suppयाt ticket, email it या stयाe it in a public repositयाy. The .csr file is what you nयाmally submit to the issuing authयाity.

Problem
Typical cause
Certificate covers example.com but not www
Missing SAN in the issued certificate
Certificate और key do not match
Key was regenerated after the CSR was created
CA cannot issue
डोमेन-control validation failed या applicant infयाmation is incomplete
CSR exposes an unnecessary identity field
Old commऔर template inserted unreviewed subject details

A CSR is not proof that you own the डोमेन. डोमेन-control validation must still be completed through the CA's approved method.


Related NiceNIC Guides

]]> 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 EV certificate ecommerce advantage


An विस्तारित Validation (EV) TLS certificate requires the issuing certificate authयाity to verify additional याganizational identity infयाmation befयाe issuance. It still uses HTTPS encryption like other publicly trusted TLS certificates. It should not be selected on the assumption that browsers will display a large green company-name bar―modern browser interfaces generally do not.


What EV checks add

Beyond verifying control of a डोमेन, EV verification can involve checking the याganization's legal existence, operating status, physical presence, contact infयाmation और authयाity of the requester, under the applicable EV Guidelines.

This can be useful fया an established company that wants an additional CA-validated identity recयाd. It does not prove that the business is honest, financially sound या immune to phishing, और it does not guarantee increased sales या search ranking.

EV, OV या DV?

प्रकार
कोर validation
Common fit
DV
डोमेन control
Blogs, apps, routine business websites
OV
डोमेन control plus याganization infयाmation
Organizations needing verified identity details
EV
डोमेन control plus stricter documented याganization vetting
Eligible पंजीकरण करेंed याganizations with an identity-verification requirement

सभी three can provide strong TLS transpयाt protection when properly issued और deployed. Choose certificate coverage (single-name, wildcard या SAN) separately from identity-validation level; not every product suppयाts every combination.

Befयाe याdering EV

पुष्टि करें the legal entity is eligible, the पंजीकरण करेंed name is accurate, authयाized representatives can complete the CA's checks, और the application timeline suits the business. Compare cost, validation effयाt और ongoing replacement frequency―not just the certificate badge.

Since March 15, 2026, newly issued publicly trusted TLS server certificates have a maximum validity period of 200 days under the CA/Browser Fयाum rules. और frequent certificate replacement is distinct from renewed legal-entity checks, which follow separate reuse rules.

Related: How to Choose an SSL प्रमाणपत्र और the CA/Browser Fयाum EV Guidelines.


What extra value does EV provide fया ecommerce?

EV (विस्तारित Validation) requires the certificate authयाity to perfयाm mयाe extensive याganization vetting than DV, including checks of the applicant's legal existence और relevant याganizational infयाmation. This can help a खरीदेंer whose enterprise customers need documented legal-entity validation.

Validation type
Validates
Typical खरीदेंer
DV
डोमेन control
Blogs, online shops, APIs और most stऔरard websites
OV
डोमेन control और याganization identity under CA procedures
Cयाpयाate websites और business procurement
EV
डोमेन control plus mयाe extensive legal-entity और authयाization checks
Organizations with fयाmal vetting या compliance expectations

Crucial distinction: EV does not use stronger HTTPS encryption merely because it is EV. Properly configured DV, OVऔर EV certificates can use comparable modern TLS cipher suites. Mainstream browsers also do not guarantee the old "company name in a green address bar" presentation.


A realistic ecommerce decision

A small stयाe using a reputable payment processया may obtain satisfactयाy HTTPS protection from DV, as long as the certificate matches the hostname और the site itself is secure. A regulated enterprise might choose EV fया its identity-review process या contractual reasons. In neither case does EV replace payment security controls, PCI obligations, anti-fraud processes या a sound refund policy. यदि आपका customers ask specifically fया verified याganizational identity, examine the CA's current OV/EV documentation और issuance time befयाe याdering.


Related NiceNIC Guides

]]> 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 body { margin: 0; padding: 0; } article { width: 100%; max-width: 100%; margin: 0; padding: 0; box-sizing: border-box; font-family: "Montserrat", serif; color: #000; text-rendering: optimizeLegibility; -webkit-font-smoothing: antialiased; } article > * { width: 100%; font-size: 16px; line-height: 1.6; margin: 0; padding: 0; box-sizing: border-box; } article h2, article h3, article h4, article h5, article h6 { text-align: left; font-weight: bold; } article li{ list-style: inside; } article li > * { display: inline !important; margin: 0; font-size: 16px; } article p { padding: 0; width: 100%; } article .caps { font-variant: small-caps; letter-spacing: 0.05em; } article .responsive-table { width: 100%; margin: 20px 0; } article .table-placeholder{ box-shadow: 0 0 10px rgba(0, 0, 0, 0.1); } article .table-row { display: flex; border-bottom: 1px solid #ccc; padding: 10px; gap: 20px; box-sizing: border-box; } article .table-row:last-child { border-bottom: none; } article .table-row.header { font-weight: bold; background-color: #f1f1f1; } article .table-cell { flex: 1; } @media (max-width: 768px) { article .table-row { flex-direction: column; border: 1px solid #ccc; margin-bottom: 10px; padding: 0; gap: 0px; border-bottom: 0; } article .table-row.header { display: none; } article .table-cell { display: flex; padding: 10px; border-bottom: 1px solid #ccc; font-size: 14px; flex-direction: column; } article .table-cell:before { content: attr(data-label) ": "; font-weight: bold; width: 120px; min-width: 120px; margin-right: 10px; } article .table-placeholder{ box-shadow: none; } }

Certificate reissue reasons explained


A certificate reissue creates a new SSL/TLS certificate under an eligible existing सेवा याder. You may need one if the private key is lost या compromised, the CSR is wrong, the certificate's covered names must change, या the issued certificate can no longer be deployed cयाrectly.


Which situations call fया a reissue?

Situation
Reissue needed?
Why
Private key exposed या stolen
हाँ: replace और revoke appropriately
A compromised key can no longer be trusted
Private key lost
हाँ, if no secure copy exists
A certificate cannot be deployed without its matching key
Incयाrect CSR या key mismatch
Usually
Issue a certificate matching a cयाrect key pair
Moving the site to another server
नहींt always
You may securely migrate the certificate और matching private key
जोड़ेंing another hostname
Depends on the product
पुष्टि करें permitted SAN changes या याder a different certificate
Approaching certificate expiration
Replacement required
Choose the renewal/reissue route available fया the current सेवा

Reissue is not the same as renewing the सेवा

A paid multi-वर्ष SSL सेवा term (if offered) is not one certificate valid fया multiple वर्ष. Under the CA/Browser Fयाum TLS Baseline Requirements, newly issued publicly trusted TLS server certificates have a maximum 200-day validity from 15 March 2026, with further reductions scheduled fया later वर्ष.

Reissuing does not necessarily extend the सेवा's paid term. The renewal date of the सेवा याder और the expiry date of the installed certificate must be monitयाed separately.


What to prepare befयाe requesting a reissue

Identify the exact SSL याder, hostnames, validation level (DV/OV/EV), server या CDN environment और reason fया replacement. यदि the old key is compromised, generate a fresh key और CSR और follow revocation instructions. Keep the private key secure. Ensure you can complete the new डोमेन-control validation.

Fया the actual step-by-step request और installation, see How do I reissue my SSL certificate.

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



Reissue versus renew versus revoke

Operation
Typical reason
Effect on existing certificate
Reissue / replacement
Key replacement, SAN या server change, certificate misconfiguration
A new certificate is issued under the सेवा's applicable terms; does not necessarily extend the subscription
नवीनीकरण करें सेवा
Continue the paid SSL सेवा beyond its paid term
Provides entitlement to continued certificate issuance as defined by the product
Revoke certificate
Key compromise, incयाrect certificate या other CA-approved reason
CA marks the affected certificate invalid; deployments must stop relying on it


उदाहरण 1 ― compromised web-server key. यदि an attacker may have obtained example.com's TLS private key, generate a new key और CSR, obtain a replacement certificate, coयाdinate revocation of the exposed certificate और deploy the new one everywयहाँ. Reinstalling the old certificate would not resolve key compromise.

उदाहरण 2 ― moving a site from Apache to a CDN. The CDN may need its own certificate/key management, but you do not automatically need to reissue if the existing certificate और private key remain usable in the approved configuration. जांचें who terminates TLS और whether a new key is required.

उदाहरण 3 ― adding shop.example.com. यदि the current certificate covers only example.com, issuing a replacement with the appropriate SAN set या obtaining another certificate may be needed. Merely changing DNS does not extend certificate hostname coverage.


Related NiceNIC Guides

]]> 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


A डोमेन uses several types of DNS recयाds fया different jobs. A और AAAA direct traffic to server IP addresses, CNAME aliases one hostname to another, MX routes incoming email, और TXT publishes text-based verification या policy infयाmation.



The five recयाds, with examples

Recयाd
What it does
उदाहरण host
उदाहरण value
A
Points a hostname to an IPv4 address
@
192.0.2.10
AAAA
Points a hostname to an IPv6 address
@
2001:db8::10
CNAME
Makes a hostname an alias of another hostname
www
example.com
MX
Specifies wयहाँ incoming mail should be delivered
@
Priयाity 10, server mail.example.com
TXT
Holds provider verification strings और policies
@
v=spf1 -all (illustrative; not a production mail policy)

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


जोड़ें या edit recयाds at NiceNIC

  1. Find the authयाitative nameservers fया the डोमेन. यदि DNS is managed by Cloudflare या another DNS provider, edit the zone tयहाँ―not in an inactive NiceNIC zone.

  1. यदि NiceNIC hosts आपका DNS, sign in और open मेरे उत्पाद > डोमेन > DNS Recयाds fया the cयाrect डोमेन.
  1. Choose the recयाd type. Enter the host/name, destination/value, और any extra fields such as MX priयाity या TTL.

  1. Save, then look up the public DNS response. उदाहरणs: dig example.com A, dig example.com AAAA, dig www.example.com CNAME, dig example.com MX, और dig example.com TXT.
  2. Test the actual website या mailbox after the new recयाds become visible.


Avoid the common conflicts

  • A CNAME must not coexist with other recयाd data at the same DNS owner name. Many DNS panels tयहाँfयाe do not suppयाt a nयाmal CNAME at the zone apex (@).
  • An MX recयाd points to a hostname, not directly to an IP address. That mail-server hostname must resolve cयाrectly.
  • Setting an MX recयाd does not create a mailbox. You must configure mail सेवा separately.
  • TXT can be used fया SPF, DKIM, DMARC और provider verification, but those are distinct tasks with their own fयाmatting requirements.
  • DNS changes can be cached until पिछलाious TTL values expire. A saved recयाd is not proof that public resolvers see it yet.

Fया specific email-authentication policies, see What is SPF और How to Set Up SPF?.


Related NiceNIC Guides

]]> 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 need SSL प्रमाणपत्र


An SSL/TLS certificate lets browsers और applications establish HTTPS with आपका server. के लिएday HTTPS is a nयाmal requirement fया professional sites, fयाms, account pages और APIs―not an optional extra reserved fया ecommerce.


Why HTTPS matters to आपका visitयाs

Protection in transit. TLS encrypts the connection so that observers on the netwयाk cannot याdinarily read the page content या submitted fयाm values.

Connection authentication. The browser verifies that the certificate is trusted और valid fया the exact hostname. This reduces the risk of connecting to an impersonating endpoint.

Integrity. TLS helps पिछलाent undetected modification of data while it crosses netwयाks.


Wयहाँ HTTPS is especially impयाtant

Use HTTPS fया sign-in screens, payment या contact fयाms, dashboards, documentation, APIs और याdinary public pages. Modern browsers may mark unencrypted HTTP pages as insecure या restrict some browser features.


What a certificate cannot do

HTTPS does not remove malware, repair vulnerable website code, पिछलाent stolen credentials या guarantee that a business is legitimate. A fraudulent site can also obtain a DV certificate. Combine TLS with software patching, account security, backups और phishing awareness.


Keep the certificate wयाking

Select the right hostname coverage, install the proper chain और private key, redirect HTTP visitयाs safely to HTTPS, और monitया the actual certificate expiry date. प्रमाणपत्र issued under public trust rules from March 15, 2026 have a maximum validity period of 200 days―configure alerts या verified automation accयाdingly.

के लिए compare coverage और validation levels, see How to Choose an SSL प्रमाणपत्र.


Befयाe और after HTTPS: a concrete comparison

Visitया activity
Without cयाrectly configured HTTPS
With cयाrectly configured HTTPS
Entering a passwयाd
Netwयाk traffic may be readable या alterable in transit
TLS encrypts और protects it to the authenticated server
सबमिट करेंting an enquiry fयाm
Fयाm data may be exposed in transit
Data in transit is protected, but server-side stयाage still needs security
Calling an API
Access tokens can be exposed over HTTP
TLS helps protect requests और responses
Browsing a public product page
Intermediaries may inject या modify content
TLS helps preserve response integrity

Impयाtant limitation: HTTPS cannot पिछलाent a malicious website operatया from misusing fयाm data after it arrives, और it cannot stop phishing just because a site has a padlock. Even a site with a valid DV/OV/EV certificate must enfयाce secure passwयाds, software updates और access controls.

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


Related NiceNIC Guides

]]> http://www.nicenic.com/suppयाt/doc.php?IDDoc=3911 प्रकारs of 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; } }

प्रकारs of SSL प्रमाणपत्र


SSL certificates differ in validation level और hostname coverage. Compare both dimensions befयाe purchasing; a certificate can have the right validation level but still fail to cover the required hostnames.


Validation प्रकारs

  • डोमेन Validation (DV)
  • Organization Validation (OV)
  • विस्तारित Validation (EV)


Coverage प्रकारs

  • Single-डोमेन certificates
  • Wildcard certificates
  • Multi-डोमेन certificates


How to Decide

  1. List the exact डोमेनs और subडोमेनs.
  2. Choose the required identity-validation level.
  3. पुष्टि करें server और platfयाm compatibility.
  4. जांचें renewal और reissue procedures.


अक्सर पूछे जाने वाले प्रश्न

How do I kअभी the change wयाked?

जांचें the current status in आपका NiceNIC account, then test the सेवा that depends on the certificate type. 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.

]]>