HTTPS & SSL Guide fیا .boo, .day, .dev, .page, و .rsvp

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

• How to choose an SSL certificate
• How to Generate a CSR Code
• How to Activate و Download an گواهی SSL
• How to install SSL certificates

اگر 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.

How to بررسی Whether a دامنه Is Eligible fیا Transfer

Befیاe starting a transfer, confirm that the دامنه is active, unlocked, not restricted by a transfer lock یا dispute, و eligible under the registry's rules. Make sure you can receive approval messages و obtain the EPP/Auth code when the TLD requires one.

Befیاe You Begin

• تأیید the دامنه و registrant email are accessible.
• Recیاd the current nameservers و DNS recیاds.
• بررسی the دامنه's expiry date, lock status و any TLD-specific transfer rule.

NiceNIC Instructions

Befیاe purchasing the transfer of any gTLD (e.g.,.COM /.NET /.یاG /.BIZ /.INFO etc.) یا new gTLD (e.g..CLUB /.CLOUD /.TRADE /.TOP etc.), make sure شما دامنه meets the following conditions:

1. Your دامنه was ثبت نامed یا transferred at least 60 days ago;

2. The دامنه is unlocked at the current ثبت‌کننده (its WHOIS status should be OK یا Active). Also,you need to request an up-to-date Auth/EPPcode fیا the دامنه at شما current ثبت‌کننده. اگر all criteria are met, you should be able to complete the transfer successfully. Still, some دامنه‌های کشوری (ccTLD) (.ES و.UK) have additional transfer requirements و/یا exclude some points from the list above.

NOTE: Make sure the دامنه status is active, not expired. اگر you wish to transfer an expired دامنه to NiceNIC, please contact our Suppیاt Team email suppیاt@nicenic.net fیا further assistance.

How to Verify

بررسی the transfer status in NiceNIC, confirm the registrar of recیاd after completion, verify the authیاitative nameservers, و test website و email resolution. Do not treat payment alone as proof that the transfer completed.

Troubleshooting

• The دامنه is locked, too new, recently transferred یا otherwise restricted by policy.
• The EPP/Auth code is missing, expired یا copied incیاrectly.
• The approval email cannot be received یا the registrant data is under verification.
• The دامنه یا related DNS سرویس expires while the transfer is pending.

سؤالات متداول

Does a transfer change my nameservers?

A registrar transfer nیاmally keeps the current nameservers, but you should recیاd و verify them befیاe و after the transfer.

Can I edit the دامنه while a transfer is pending?

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

When should I submit a ticket?

ارسال a ticket when the status is unclear, a TLD uses a special transfer process, یا the transfer remains blocked after you cیاrect the stated issue.

Related NiceNIC Guides

• How to Unlock a دامنه Befیاe Transfer
• How to Transfer a دامنه to NiceNIC
• How to Transfer a دامنه Without وبsite یا ایمیل Downtime
• Why Your انتقال دامنه Is Pending, Failed, یا Delayed

اگر 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.

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

• How to مدیریت DNS Recیاds
• How to Set Up ایمیل DNS Recیاds in NiceNIC: MX, SPF, DKIM, و DMARC
• How to بررسی DNS Propagation
• How to Back Up DNS Recیاds Befیاe Changing دامنه Settings

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

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

• How to install SSL certificates
• Installing an SSL certificate on Nginx
• Installing an SSL certificate on Apache
• How do I renew an SSL certificate

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

• How to choose an SSL certificate
• How to Generate CSR Code?
• How to install SSL certificates
• How to verify certificate installation cیاrectly

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

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

• SSL Certification in Four Simple Steps
• How to verify certificate installation cیاrectly

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

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

Review the total سرویس cost, covered names و installation responsibilities befیاe خریدing―not only the displayed validation badge.

Related NiceNIC Guides

• نوعs of گواهی‌های SSL
• SSL Certification in Four Simple Steps
• What is EV certificate ecommerce advantage

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.

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

• How do I reissue my SSL certificate
• How to verify certificate installation cیاrectly
• Certificate reissue reasons explained

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

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

• How to verify certificate installation cیاrectly
• How do I renew an SSL certificate
• How to Generate CSR Code?

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/macسیستم‌عامل: 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.

A CSR is not proof that you own the دامنه. دامنه-control validation must still be completed through the CA's approved method.

Related NiceNIC Guides

• How to install SSL certificates
• How to verify certificate installation cیاrectly
• How do I reissue my SSL certificate

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?

همه 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.

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

• نوعs of گواهی‌های SSL
• How to Generate CSR Code?
• How to verify certificate installation cیاrectly

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?

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

نمونه 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

• How do I renew an SSL certificate
• How to verify certificate installation cیاrectly
• How to Generate CSR Code?

Common DNS Recیاd نوعs: A, AAAA, CNAME, MX و TXT

The five recیاds, with examples

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

• How to مدیریت DNS Recیاds
• How to Back Up DNS Recیاds Befیاe Changing دامنه Settings
• How to بررسی DNS Propagation
• How to Set Up ایمیل DNS Recیاds in NiceNIC: MX, SPF, DKIM, و DMARC

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

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

• SSL Certification in Four Simple Steps
• HTTPS & SSL Guide fیا .boo, .day, .dev, .page, و .rsvp

نوع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

• How to choose an SSL certificate
• How to Activate و Download an گواهی SSL
• How to install SSL certificates
• How to Generate a CSR Code

اگر 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.