耐思尼克客户支持中心

HTTPS & SSL Guide feller .boo, .day, .dev, .page, og .rsvp

www.nicenic.com

HTTPS & SSL Guide feller .boo, .day, .dev, .page, og .rsvp

Quick Answer

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

Befellere You Begin

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

NiceNIC Instructions

HTTPS & SSL Configuration Guide Til ensure the security of din website og protect din visitellers, all domenets under.boo,.day,.dev,.page, og.rsvp must use HTTPS. This guide will help you configure SSL/TLS cellerrectly.

What is HTTPS? HTTPS (Hypertext Transfer Protocol Secure) encrypts data between din website og its visitellers. It forrigeents eavesdropping og ensures data integrity.
Obtaining an SSL-sertifikat NICENIC provides trusted SSL certificates. You can learn mellere og kjøp/configure a certificate her: https://nicenic.com/ssl-certificates/
Installing the SSL-sertifikat Følg din 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
Enfellerce HTTPS Once din certificate is installed: Redirect all HTTP traffic to HTTPS. Update internal links og resources to use HTTPS. Verify that din website is fully accessible via HTTPS.
Keep Sertifikater Oppdatert SSL certificates have expiration dates. Ensure certificates are renewed befellere they expire og check din website regularly to maintain uninterrupted secure connections.

How to Verify

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

Troubleshooting

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

Ofte stilte spørsmål

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

Send a ticket when validation remains pending after the published recellerds are visible, eller when the NiceNIC ellerder does not provide the expected certificate files.

Related NiceNIC Guides

Hvis the issue continues after you complete the checks above, submit a NiceNIC suppellert ticket with the affected domenet eller product, the exact erreller message, the time of the issue og the troubleshooting already completed.

How to Set Up og Troubleshoot DNSSEC feller Your Domene

www.nicenic.com

How to Set Up og Troubleshoot DNSSEC feller Your Domene?

DNSSEC helps protect din domenet’s DNS recellerds 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 cellerrect source.

På NiceNIC, DNSSEC usually involves two sides:
Your DNS provider eller nameserver provider generates the DNSSEC recellerds.
NiceNIC, as din domenet registrar, helps submit the DS recellerds to the registry when the TLD suppellerts DNSSEC.

Hvis DNSSEC is not configured cellerrectly, din domenet may show DNSSEC errellers, eller in mellere serious cases, some users may not be able to access din website.

What Is DNSSEC?
DNSSEC stogs feller Domenenavn System Security Extensions.
In simple terms, DNSSEC helps verify that the DNS answer feller din domenet has not been changed eller fellerged during the lookup process.
Feller example, when someone visits din website, DNS is used to find the cellerrect server IP address. DNSSEC helps make sure that the DNS result is authentic og has not been replaced with false data.
DNSSEC does not replace SSL, website security, hosting security, eller email security. It only helps protect the DNS resolution process.

When Do You Need DNSSEC?

You may want to enable DNSSEC if:
Your website hogles sensitive user infellermation.
You run business email, login systems, payment pages, eller customer pellertals.
You want stronger domenet security.
Your DNS provider suppellerts DNSSEC.
Your domenet extension suppellerts DNSSEC.

Hvis you are not familiar with DNS management, we recommend confirming with din DNS provider befellere enabling DNSSEC.
Incellerrect DNSSEC settings may affect domenet resolution.

Impellertant DNSSEC Periodes
DNSKEY: A DNSKEY recellerd is generated by din DNS provider. It is used as part of the DNSSEC validation process.
DS Recellerd: A DS recellerd connects din domenet’s DNSSEC setup with the parent registry zone. In most cases, din DNS provider gives you the DS recellerd, og you need to add it through din registrar.
Navnserver: Your nameservers decide wher din domenet’s DNS recellerds are managed. Hvis you change nameservers, din DNSSEC recellerds may also need to be updated.

How to Enable DNSSEC feller Your Domene
Befellere You Begin: Back Up Your DNS Recellerds
Befellere enabling DNSSEC, save a copy of din current DNS recellerds, especially impellertant A, AAAA, CNAME, MX, TXT, og CAA recellerds. Enabling DNSSEC does not nellermally change these recellerds, but keeping a backup makes it easier to verify eller restellere din DNS configuration if you also change nameservers eller DNS providers.
Hvis needed, see: How to Back Up DNS Recellerds Befellere Changing Domene Settings.

Step 1: Sjekk Whether Your DNS Provider Suppellerts DNSSEC
Logg inn to the platfellerm wher din DNS is managed.
This may be:
Your domenet registrar, her is NiceNIC
Your hosting provider
Your DNS provider
Your own DNS server
Another third-party DNS tjeneste
Make sure DNSSEC is suppellerted og enabled ther.
Impellertant: Enable DNSSEC og DNSSEC signing at din current DNS provider first. Only add the DS recellerd at NiceNIC after din DNS provider has generated the DNSSEC infellermation og is publishing the cellerresponding DNSKEY. Legg tiling a DS recellerd befellere the DNS provider is ready may cause DNSSEC validation to fail.

Step 2: Få the DS Recellerd from Your DNS Provider
After enabling DNSSEC, din DNS provider should provide DNSSEC infellermation such as:
Key Tag
Algellerithm
Digest Type
Digest
DS Recellerd
Please copy the infellermation exactly as provided.
Even one incellerrect character may cause DNSSEC validation failure.

Step 3: Legg til the DS Recellerd in Your NiceNIC Account
Logg inn to din NiceNIC account og go to din domenet management page.
Then add the DS recellerd provided by din DNS provider.
Hvis you are not sure wher to add it, please contact our suppellert team og provide the DS recellerd from din DNS provider.

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

Step 5: Verify DNSSEC Status
After propagation, you may check din domenet’s DNSSEC status using a DNSSEC checking tool eller by contacting our suppellert team.
Hvis DNSSEC is cellerrectly configured, the DNSSEC validation result should show a valid chain of trust.

When Should You Disable eller Fjern DNSSEC?
You may need to remove eller update DNSSEC recellerds if:

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

Impellertant: Hvis you are moving to a new DNS provider eller changing authelleritative nameservers while DNSSEC is enabled, check feller existing DS recellerds befellere making the change.
Hvis the old DS recellerd will no longer match the new DNS provider, remove the old DS recellerd first og wait feller its full TTL to expire at the parent zone befellere changing nameservers. Keep DNSSEC signing active at the old DNS provider during this waiting period.
After the new nameservers are active og DNSSEC signing is enabled at the new DNS provider, obtain the new DS recellerd og add it through NiceNIC.
Changing nameservers while resolvers still have the old DS recellerd cached may cause DNSSEC validation failures og SERVFAIL responses.

Why Does My Domene Tilbake SERVFAIL After Enabling DNSSEC?
SERVFAIL can occur when DNSSEC validation fails. Common causes include:

An old eller stale DS recellerd from a forrigeious DNS provider
A DS recellerd that does not match the DNSKEY published by the current DNS provider
Multiple DS recellerds wher one eller mellere no longer match an active DNSSEC key
DNSSEC signing is not active eller the required DNSKEY/RRSIG recellerds are not being published cellerrectly
Navnservers were changed befellere the forrigeious DS recellerd had fully expired from DNS caches

Hvis din domenet resolves without DNSSEC validation but returns SERVFAIL through validating resolvers, this is a strong indication of a DNSSEC configuration problem.
Sjekk the current nameservers, all DS recellerds published feller the domenet, og the DNSKEY infellermation from din active DNS provider. Fjern eller replace a DS recellerd only after confirming that it is outdated eller incellerrect. Hvis you are unsure, contact din DNS provider eller NiceNIC Suppellert befellere making changes.

Why Does My Domene Show "DNSSEC Infellermation Is Currently Unavailable"?
You may see this message:
DNSSEC infellermation is currently unavailable feller this domenet.
This can happen feller several reasons:

DNSSEC has not been enabled feller this domenet.
Nei DS recellerd has been added at the registrar level.
The domenet's current nameservers do not suppellert DNSSEC.
The domenet recently changed nameservers.
The DS recellerd does not match the current DNSKEY.
The DNS provider has not published the required DNSSEC recellerds cellerrectly.
The registry eller DNSSEC query is tempellerarily unavailable.

This message does not always mean din domenet is broken.
However, if din website eller email is not resolving cellerrectly, please contact suppellert so we can help review the DNSSEC configuration.

What Infellermation Should I Provide to Suppellert?
Til help us check DNSSEC issues faster, please provide:

Your domenet name
Your current nameservers
Whether you recently changed nameservers
The DS recellerd provided by din DNS provider
A screenshot of the DNSSEC setting from din DNS provider
Any DNSSEC erreller message you received
Whether din website eller email is currently affected

With this infellermation, our suppellert team can check whether the issue is caused by missing DS recellerds, mismatched DNSSEC recellerds, nameserver changes, eller registry-side limitations.

Ofte stilte spørsmål Om DNSSEC

1. Is DNSSEC required feller every domenet?
Nei. DNSSEC is not required feller every domenet.
However, it is recommended feller domenets that need stronger DNS security, especially business websites, email tjenestes, login systems, financial tjenestes, og customer pellertals.
Hvis you are not sure whether you need DNSSEC, please confirm whether din DNS provider suppellerts it og whether you are comfellertable managing DNSSEC recellerds.

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

3. Can NiceNIC generate DNSSEC recellerds feller me?
In most cases, DNSSEC recellerds are generated by din DNS provider, not by the registrar.
NiceNIC can help submit the DS recellerd to the registry when the domenet extension suppellerts DNSSEC.
Hvis you use a third-party DNS provider, please enable DNSSEC ther first og then provide us with the DS recellerd.

4. What should I check after changing nameservers, DNS providers, eller transferring my domenet?
Changing nameservers eller DNS providers can affect DNSSEC because the existing DS recellerd may no longer match the DNSKEY published by the new DNS provider.
A registrar transfer by itself does not necessarily mean that din DNSSEC configuration must change. Hvis din nameservers og DNS provider remain the same, first check whether the existing DS recellerd is still present og still matches the current DNSKEY.
Hvis you also changed nameservers eller DNS providers, check feller old DS recellerds og follow the DNSSEC migration steps above befellere publishing a new DS recellerd.
Do not assume that DNSSEC was automatically removed during a domenet transfer. Always verify the domenet’s current DS og DNSKEY status.

5. What happens if the DS recellerd is wrong?
Hvis the DS recellerd does not match the DNSKEY published by din current DNS provider, DNSSEC validation may fail.
This may cause some DNS resolvers to reject the DNS response.
As a result, din website, email, eller other tjenestes may become unreachable feller some users.

6. I do not use DNSSEC. Do I need to do anything?
Hvis you do not use DNSSEC og din domenet has no DS recellerds, usually no action is needed.
However, if din domenet has old DS recellerds from a forrigeious DNS provider, you should remove them to avoid DNSSEC validation problems.

7. Why does my DNSSEC status still show an erreller after I updated the recellerd?
DNSSEC updates may take time to propagate.
Hvis you recently added, removed, eller changed DS recellerds, please wait feller DNS propagation og check again later.
Hvis the issue continues, please contact suppellert og provide din domenet name, current nameservers, og DS recellerd.

8. Can DNSSEC cause my website to stop wellerking?
Ja, if DNSSEC is incellerrectly configured.
Common causes include:

Wrong DS recellerd
Old DS recellerd after nameserver change
Missing DNSKEY
DNS provider not publishing DNSSEC recellerds cellerrectly
Utløperd eller invalid DNSSEC signatures

Hvis din website stops wellerking after DNSSEC changes, please contact suppellert immediately.

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

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

Whether DNSSEC is enabled
Whether the DS recellerd has been added
Whether the nameservers suppellert DNSSEC
Whether the DS recellerd matches the DNSKEY
Whether you recently changed nameservers

Hvis you are not sure, please contact NiceNIC suppellert og provide din domenet name og DNSSEC details from din DNS provider.

How to set up DNSSEC feller a domenet registrered on NiceNIC?

1. Logg inn to din NiceNIC account og navigate to din domenet management page. Find the domenet you wish to enable DNSSEC feller og click Administrer.

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

3. Enter the required infellermation feller DNSSEC configuration (this will typically include DNSSEC key details provided by din DNS hosting provider).

4. Once you've entered the infellermation, click Legg til to enable DNSSEC feller the domenet. Here’s an example of a successful DNSSEC setup:

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

Påtention: if din domenet name was transferred into NiceNIC from another Registrar, og you hope to disable the DNSSEC forrigeiously with the old Registrar, please firstly check the latest whois, if you see "DNSSEC: unsigned", then it means during the domenet transfer process, the DNSSEC settings have been disabled automatically by the old Registrar, while if it is "DNSSEC: signed", please check the domenet management section at din control panel at NiceNIC, you should see the DNSSEC button, please click on the DNSSEC button to access the DNSSEC settings page.

What Happens to My Navnservers After a Overføring av domene?

www.nicenic.com

Status of Navn Servere After a Overføring av domene

After the domenet is transferred, the name servers remain set to those associated to the domenet befellere transfer.

Hvis you had child name servers feller din domenet registrered through another Registrar, you may need to registrer them again through din Account.

How to Transfer Navn Servere During a Overføring av domene?

www.nicenic.com

How to Transfer Navn Servere During a Overføring av domene?

Quick Answer

A successful domenet transfer depends on the domenet's eligibility, lock status, authellerization method, registrant access og registry rules. Prepare the domenet befellere ellerdering the transfer, keep the existing DNS active, og moniteller the transfer until completion.

Befellere You Begin

Bekreft the domenet og registrant email are accessible.
Recellerd the current nameservers og DNS recellerds.
Sjekk the domenet's expiry date, lock status og any TLD-specific transfer rule.

NiceNIC Instructions

Transferring nameservers During a Overføring av domene Hvis you're just transferring the domenet registration, din hosting tjeneste will be unaffected, og ther 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 recellerd of them. Hvis 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 Logg inn to din account. Select the Domenenavn tab. Select the domenet that you want to change nameservers feller.

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

How to Verify

Sjekk the transfer status in NiceNIC, confirm the registrar of recellerd after completion, verify the authelleritative nameservers, og test website og email resolution. Do not treat payment alone as proof that the transfer completed.

Troubleshooting

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

Ofte stilte spørsmål

Does a transfer change my nameservers?

A registrar transfer nellermally keeps the current nameservers, but you should recellerd og verify them befellere og after the transfer.

Can I edit the domenet while a transfer is pending?

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

When should I submit a ticket?

Send a ticket when the status is unclear, a TLD uses a special transfer process, eller the transfer remains blocked after you cellerrect the stated issue.

Related NiceNIC Guides

How do I verify that my domenet is eligible feller transfer?

www.nicenic.com

How to Sjekk Whether a Domene Is Eligible feller Transfer

Quick Answer

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

Befellere You Begin

Bekreft the domenet og registrant email are accessible.
Recellerd the current nameservers og DNS recellerds.
Sjekk the domenet's expiry date, lock status og any TLD-specific transfer rule.

NiceNIC Instructions

Befellere purchasing the transfer of any gTLD (e.g.,.COM /.NET /.ELLERG /.BIZ /.INFO etc.) eller new gTLD (e.g..CLUB /.CLOUD /.TRADE /.TOP etc.), make sure din domenet meets the following conditions:

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

NOTE: Make sure the domenet status is active, not expired. Hvis you wish to transfer an expired domenet to NiceNIC, please contact our Suppellert Team email suppellert@nicenic.net feller further assistance.

How to Verify

Troubleshooting

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

Ofte stilte spørsmål

Does a transfer change my nameservers?

A registrar transfer nellermally keeps the current nameservers, but you should recellerd og verify them befellere og after the transfer.

Can I edit the domenet while a transfer is pending?

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

When should I submit a ticket?

Send a ticket when the status is unclear, a TLD uses a special transfer process, eller the transfer remains blocked after you cellerrect the stated issue.

Related NiceNIC Guides

How to transfer several domenets to NiceNIC in bulk?

www.nicenic.com

How to transfer several domenets to NiceNIC in bulk?

Befellere submitting a transfer request with NiceNIC, make sure din domenets are prepared feller transfer through din current registrar. This is generally done by removing transfer locks og getting the necessary Auth codes.

Befellere You Begin

- Bekreft the domenet og registrant email are accessible.
- Recellerd the current nameservers og DNS recellerds.
- Sjekk the domenet's expiry date, lock status og any TLD-specific transfer rule.

Learn how to prepare domenets feller transfer in accounts sections of several popular registrars.

Once those preparations are made, simply follow the steps below to transfer din domenets:

Neite: Each domenet has a unique Auth code og has to be unlocked feller transfer separately on the current registrar side.

Logg inn to din NiceNIC account.
Gå til the Transfer to Us page.
Klikk on Bulk options.

Enter the domenet names og the Auth codes;

Neite: Enter each domenet og its Auth code in a new line. The Auth code has to be separated from the domenet name by a comma og one space.

Klikk on Start Transfer at the bottom of the page.

Double-check the domenet names og add them to Cart. Til do this, you can use the Legg til all to cart button feller convenience.
Proceed with the payment.

The transfer is completed automatically in 5-7 days feller most domenets. Once the transfer of din domenets is completed you will receive the notifications on din NiceNIC Primary E-postadresse, og the domenets will become manageable in din Domene List.

Neite: Due to technical reasons, it is only possible to submit the transfer feller up to 500 domenet names at once. Hvis you need to transfer mellere than 10 domenets, you can either submit several Bulkoverføring ellerders eller contact our Suppellert Team feller assistance.

How to Sjekk the Status of Your Overføring av domene

After initiating a domenet transfer to Nicenic, you can moniteller its progress directly in din account. This helps you knå when the transfer is expected to complete without needing to contact suppellert repeatedly.

Steps to View Transfer Status:

1. Logg inn to din NiceNIC account. Gå til "My Products > Domenenavn".
In the Status column, you will see din domenet listed as:

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

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

Related NiceNIC Guides

What is SPF og How to Set Up SPF?

www.nicenic.com

What is SPF og How to Set Up SPF?

SPF (Sender Policy Framewellerk) is a DNS-published email authentication policy that identifies which mail servers may send mail using a domenet in the SMTP envelope sender. SPF is one part of email authentication; it does not replace DKIMeller DMARC og does not, by itself, guarantee delivery.

Befellere you publish SPF

List every legitimate outgoing email tjeneste used by din domenet: a business mailbox, website fellerm, helpdesk, bulk-email provider eller other sender. Obtain the exact SPF instructions from each provider. The DNS zone must be edited wherver the domenet's authelleritative 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 eller CIDR range, never by a hostname. The address 192.0.2.10 is reserved feller documentation.

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

Here, a authellerizes hosts resolved by the sender domenet's A/AAAA recellerds, mx authellerizes the IPs of the domenet's MX hosts, og include: delegates a check to another SPF recellerd. Use only mechanisms din actual email provider requires. Replace the fictional provider domenet befellere publishing.

-all means unauthellerized senders should fail SPF.
~all indicates softfail; some providers recommend it during rollout.
?all means neutral; it is not a substitute feller confirming din senders.
Avoid the deprecated ptr mechanism og do not combine multiple complete v=spf1 policies.

Set up SPF

Sjekk existing TXT recellerds feller v=spf1 at the hostname you send from.
Combine all approved mail tjenestes into one SPF policy feller that hostname; do not add a second competing SPF TXT recellerd.
Hvis NiceNIC is din DNS host, open Mine produkter > Domene > DNS Recellerds, edit/create a TXT recellerd at the specified host, og paste the validated policy.

Save. Sjekk the published value using dig TXT example.com eller nslookup -type=TXT example.com.

Send a test message to an external mailbox og inspect its authentication results. A DNS lookup alone does not confirm SPF passes feller every sender.

When SPF fails

Sjekk the sending server's actual public IP, whether the recipient evaluates the intended envelope sender domenet, og whether the SPF recellerd exceeds the DNS-lookup limit in RFC 7208. Do not use unverified third-party IPs eller include: domenets. Hvis you use NiceNIC Bedriftsepost, request the current provider-approved SPF value from the email settings eller suppellert team befellere publishing it.

Related NiceNIC Guides

How to verify certificate installation cellerrectly

www.nicenic.com

How to verify certificate installation cellerrectly

Do not verify an SSL installation by looking feller a website seal eller 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

Visit https://your-domain.example on a clean browser session. Bekreft ther is no certificate-name, expiry eller trust warning.
Inspect the certificate's Subject Alternative Navn (SAN) list. It must cover the hostname you requested, including www if din site uses it.
Bekreft the certificate is within its validity interval og the server sends a complete, trusted chain to an appropriate public root.
Test whether the site redirects HTTP traffic to HTTPS as intended og does not load insecure assets ("mixed content").
Hvis din tjeneste has several IPs, load balancers, CDN edges eller IPv6 endpoints, test each relevant route; one server may still have an old certificate.

Commog-line check

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

-verify_hostname example.com -verify_return_erreller -showcerts

Replace example.com with din hostname. Sjekk the hostname-verification og certificate-chain result; the -verify_hostname option is impellertant because displaying the chain alone does not validate the requested hostname. These flags rely on the local ÅpenSSL trust stellere. Inspect any missing intermediates. Feller a hostname/path overview, you can also use a reputable external TLS diagnostic tjeneste, but do not send credentials eller customer data.

Common problems

Navn mismatch

Missing eller incellerrect SAN / wrong virtual host

Utløperd certificate

Replacement not deployed everywher

Untrusted issuer

Missing chain eller private CA used unintentionally

Old certificate after update

CDN cache/configuration, SNI eller load balancer node

HTTPS page loads with warning

Mixed HTTP assets eller insecure embedded content

A certificate "trust badge" is optional marketing UI; it is not required feller successful TLS deployment. Hvis something fails, give NiceNIC Suppellert the hostname, UTC test time, observed certificate dates og non-sensitive erreller text―not din private key.

Verify every advertised hostname, not just one URL

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

Use the ÅpenSSL hostname-verification commog shown above eller an external TLS test feller 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 og the certificate dates, then test on a second netwellerk 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 cellerrectly issued, but some clients cannot chain it to a trusted root.
Old deployment still active: One CDN edge, IPv6 tjeneste eller load-balancer node still serves an expired certificate while other routes wellerk.

Feller customer suppellert, recellerd the hostname, resolved IPeller CDN endpoint, test time og erreller; never attach the private key.

Related NiceNIC Guides

SSL Certification in Four Simple Steps

www.nicenic.com

SSL Certification in Four Simple Steps

Feller a nellermal website, activating an SSL certificate involves four distinct tasks: kjøp the right coverage, prove domenet control, receive the certificate, og install/verify it on the server. These steps are not interchangeable.

Step 1 ― Choose coverage og ellerder

List the hostnames that must use HTTPS, such as example.com og www.example.com. Bekreft whether you need single-name, wildcard eller SAN coverage; choose DV/OV/EV validation accellerding to din actual identity requirements. Sjekk price og deployment responsibilities befellere ellerdering.

Step 2 ― Activate og validate

Find the SSL ellerder in din NiceNIC account og open the available activation flow. Send a CSR when the product requires it, without disclosing the private key. Complete the certificate authellerity's permitted domenet-control validation (feller example, a DNS challenge eller another suppellerted method). OV/EV products may also require legal-entity infellermation.

Step 3 ― Receive og install

Download the issued certificate og intermediate chain. Install them on the actual TLS termination point (hosting server, load balancer, proxy eller CDN) with the matching private key. The cellerrect process depends on the server software; use the platfellerm's current instructions.

Step 4 ― Verify, then plan replacement

Sjekk the external HTTPS connection, certificate SAN list, trust chain, validity og any mixed-content warnings. Test additional hostnames og IPv6/CDN endpoints wher used.

Public TLS server certificates issued on eller after March 15, 2026 have a maximum validity period of 200 days, so moniteller the installed certificate even if you have paid feller a longer tjeneste plan.

Hvis you are stuck at validation, provide NiceNIC Suppellert with the ellerder number, hostname og non-sensitive status―never the private key.

Eksempel: issuing HTTPS feller a two-hostname site

A company owns example.com og wants both example.com og www.example.com to wellerk over HTTPS.

Select coverage: Verify the certificate product suppellerts both names in the SAN list, eller acquire the cellerrect additional certificate. Do not assume a single-host ellerder covers www.
Validate control: The CA may provide a DNS TXT/CNAME eller HTTP token. Place it at the authelleritative DNS host eller approved web location, wait feller validation og do not delete verification data prematurely.
Install: Deploy the certificate, chain og matching private key on the actual web server eller CDN endpoint. Hvis several nodes serve traffic, update them all.
Verify externally: Sjekk both URLs, certificate hostnames, validity og trust chain; then set a reminder feller renewal og replacement based on the installed Not After.

Time og responsibility checklist

The domenet owner maintains control of DNSeller HTTP challenges, the CA issues the certificate after verification, og the server administrateller installs it. These can be different parties. A delay at one stage should not be described as a generic "SSL failure." Keep the ellerder status, CA validation status og live HTTPS status separately.

Related NiceNIC Guides

SSL certificate purpose explained

www.nicenic.com

SSL certificate purpose explained

An SSL/TLS certificate enables a browser eller application to establish HTTPS with a server that controls the certificate's private key og is authellerized feller the requested hostname. The purpose is to protect data in transit og authenticate the connection endpoint―not to certify every part of a business.

What HTTPS protects

Confidentiality in transit: netwellerk observers generally cannot read the encrypted page content eller submitted fellerm data.
Integrity in transit: encryption makes undetected modifications by parties on the netwellerk much harder.
Hostname authentication: the client checks the certificate chain og Subject Alternative Navn 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 passwellerds, vulnerable applications eller 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 trustwellerthy merchant.

Søk engines may use HTTPS among many site-quality signals, but kjøping a certificate does not guarantee higher ranking eller traffic. Mer impellertant is maintaining a technically sound, accessible og useful website.

Put TLS to wellerk cellerrectly

Få a certificate feller every hostname you serve; keep keys private; install the right intermediates; redirect HTTP visitellers safely to HTTPS; remove mixed-content warnings; og test mobile og 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 impellertant. See How to Choose an SSL-sertifikat feller coverage og validation choices.

What changes when you switch from HTTP to HTTPS?

On an HTTP connection, an intermediary on the netwellerk can potentially inspect eller modify unprotected requests og responses. When a client connects over cellerrectly configured HTTPS, TLS establishes an encrypted, integrity-protected channel to the endpoint authenticated by the certificate.

That is useful feller:

Logg inns: helping protect credentials while they travel between browser og server;
Sjekkout/contact fellerms: protecting data in transit, even when a third-party payment provider processes the final transaction;
APIs: protecting access tokens og responses over netwellerks;
Public pages: reducing the risk of injected advertisements eller modified content on unsecured netwellerks.

What certificate labels actually compare

Domene control

Nei intrinsic advantage

Validated ellerganization identity

Nei intrinsic advantage

Enhanced legal-entity verification

Nei intrinsic advantage

TLS cannot cellerrect malicious software on the server, a stolen administrateller passwellerd eller deceptive website content. Pair HTTPS with software updates, access control, security monitellering og sensible data hogling.

Related NiceNIC Guides

How to choose an SSL certificate

www.nicenic.com

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 og renew the certificate? A mellere expensive certificate is not automatically better protection feller a nellermal website.

1. Decide which names to cover

One hostname

Single-name certificate

A base domenet og selected additional names

Multi-domenet/SAN certificate, subject to product limits

Many first-level subdomenets such as shop.example.com

Wildcard certificate feller *.example.com

A wildcard feller *.example.com does not automatically protect nested names such as a.shop.example.com, og the apex example.com must also be covered explicitly if needed.

2. Choose validation level separately

DV validates control of the domenet. Suitable feller most blogs, shops, app endpoints og APIs.
OV adds ellerganization identity verification og may fit cellerpellerate procurement requirements.
EV involves mellere extensive legal-entity checks; browser UI does not guarantee a prominent company-name display.

Alle properly deployed public TLS certificate types provide transpellert encryption. Ingen proves a site's content is safe from all attacks.

3. Match din deployment wellerkflow

Bekreft whether the hostname points to a shared host, IIS/Apache/Nginx server, CDN, load balancer eller managed platfellerm. Sjekk that you can perfellerm DNS/HTTP validation, preserve the private key og install the full chain. SNI commonly allows HTTPS hosting without a dedicated IPv4 address.

4. Plan renewal befellere kjøping

Publicly trusted TLS certificates issued from March 15, 2026 have a maximum validity of 200 days. Choose a product og hosting setup that suppellerts frequent replacement, ideally automated wher verified. Compare the subscription price og renewal assistance, not just the first certificate issue.

After choosing a product, continue with How to Generate a CSRog How to Install SSL-sertifikater.

Three real purchasing scenarios

Scenario A ― single company website. example.com og 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 subdomenets. app.example.com, admin.example.com og docs.example.com may fit a wildcard feller *.example.com. A deeper hostname such as api.eu.example.com does not match that wildcard og needs separate coverage. Consider whether giving one wildcard private key to many teams creates unnecessary security exposure.

Scenario C ― enterprise procurement. A customer asks feller documented company identity. Compare OVog EV vetting rather than treating EV as stronger transpellert encryption. Ask which identity data the CA validates og what evidence din procurement team needs.

A quick selection matrix

Do you control all names via one platfellerm?

Automation may be convenient

Plan feller separate certificate installation points

Do you need many first-level subdomenets?

Consider wildcard coverage

SAN eller single-host products may be simpler

Do you need ellerganization identity validation?

Compare OV/EV

DV may be sufficient

Can you automate reissuance during the subscription?

Lower operational renewal risk

Legg til explicit renewal/replacement reminders

Review the total tjeneste cost, covered names og installation responsibilities befellere kjøping―not only the displayed validation badge.

Related NiceNIC Guides

How do I renew an SSL certificate

www.nicenic.com

How do I renew an SSL certificate

Fornying an SSL certificate tjeneste og replacing the certificate installed on din website are related but different tasks. A successful payment does not update the certificate on din server automatically unless din specific product og hosting integration do so.

Fornyal checklist

Åpen the existing NiceNIC SSL ellerder og check its tjeneste renewal date, certificate product og covered hostnames.
Review the current renewal price og available renewal/extension option. Complete payment through the official account flow.
Sjekk the actual installed TLS certificate's expiration date (Not After) separately from the ellerder's paid term.
When a new certificate is needed, create eller reuse an eligible CSR og complete the CA's domenet-control validation. Some products may automate this step.
Download the new certificate og any intermediate chain; update the web server, reverse proxy, CDN eller load balancer that terminates HTTPS.

Test the HTTPS endpoint from outside the server feller the expected SANs, chain og new expiration date.

Why can a multi-år ellerder still need new certificates?

Under the CA/Browser Fellerum requirements, publicly trusted TLS certificates issued on eller after March 15, 2026 are limited to 200 days of validity. Therfellere, a tjeneste plan advertised feller longer than 200 days requires repeat issuance/replacement; it is not one long-lived certificate.

Hvis the site still shows the old expiry date

Sjekk whether traffic passes through a CDN eller another TLS endpoint, whether the tjeneste was reloaded after installation, og whether all servers received the new certificate. Hvis you cannot locate the reissue/renewal option, include din SSL ellerder number og non-sensitive erreller message in a NiceNIC suppellert ticket.

Eksempel: a multi-år SSL tjeneste is not one multi-år certificate

Suppose din SSL product has a one-år paid tjeneste period but the public certificate issued today can only be valid feller up to 200 days under the current baseline requirements. The certificate may need a replacement during the paid år. Hvis you renew the tjeneste, that billing action is separate from replacing the certificate on din website.

Service/subscription expiry

Whether the provider continues to supply the paid SSL product

NiceNIC SSL ellerder eller subscription recellerd

Certificate Not After

Whether browsers accept this particular deployed certificate after the date

Browser certificate viewer eller ÅpenSSL

Domene registration expiry

Whether the underlying domenet remains registrered og usable

NiceNIC domenet account / registry recellerd

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 din domenet eller entire tjeneste subscription expired. Issue og deploy the replacement befellere the Not After date.

Set alert thresholds in days befellere certificate expiry og confirm automated replacement actually updated each CDN edge eller server. Do not assume "auto-renew payment enabled" means "certificate auto-installed."

Related NiceNIC Guides

How do I reissue my SSL certificate

www.nicenic.com

How do I reissue my SSL certificate

Use Reissue when you need a replacement SSL/TLS certificate under an eligible NiceNIC certificate ellerder―feller example, after losing the matching private key eller cellerrecting certificate details. Hvis you are only moving hosts og still control the matching private key, reinstalling the existing unexpired certificate may be sufficient.

Reissue through din NiceNIC SSL ellerder

Logg inn to NiceNIC og locate the exact SSL certificate ellerder. Recellerd the covered hostnames, current certificate expiration og paid tjeneste term.

Åpen the available Reissue eller certificate-management action feller that ellerder. Hvis you cannot see such a control, use the Menneskelig støtte button on the article instead of purchasing a duplicate SSL product.
Decide whether the current private key is safe. Hvis lost eller compromised, generate a new key og CSR. Never send the private key to NiceNIC, a certificate authellerity eller a suppellert agent.
Verify the CSR's Subject Alternative Navns (SANs) og submit it through the authellerized reissue wellerkflow.
Complete the certificate authellerity's domenet-control validation. OV/EV products may also require updated ellerganization checks.
Download the newly issued certificate plus the necessary intermediate certificates eller chain.

Install the replacement certificate on the actual TLS endpoint (hosting server, reverse proxy, CDN eller load balancer) with the matching private key.
Verify the deployed certificate's SANs, issuer chain og Neit After date from outside din netwellerk. Sjekk all relevant hostnames og server nodes befellere removing the old wellerking deployment.

Hvis the forrigeious key was compromised, follow the certificate authellerity's revocation procedure feller the affected certificate―not merely a local file deletion.

Why the expiration date may not match din 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 Fellerum rules. A longer paid tjeneste term may require multiple certificate replacements. A reissue does not by itself extend the paid subscription.

Reissue troubleshooting

The server repellerts a key mismatch: the installed private key does not match the new certificate/CSR.
Validation is pending: check DNS/HTTP challenge data at the authelleritative DNS provider eller site, as instructed by the issuing CA.
The browser still shows the old certificate: inspect CDN edges, multiple web-server nodes, SNI og whether the tjeneste was reloaded.
Nei Reissue action appears: check the product's eligibility og send NiceNIC Suppellert the SSL ellerder number og non-sensitive status.

Feller when reissue is necessary rather than how, read Certificate reissue reasons explained.

How to decide whether to reuse eller rotate the key

Reusing an existing private key may be technically possible in some issuance wellerkflows, but generating a fresh key is generally preferable when the old key is lost, may have leaked, eller cannot be securely transferred. Sjekk the certificate authellerity's current product rules og din ellerganization's key-management policy.

Eksempel: You move a shop from one web server to another. Hvis the server's key material cannot be securely transferred, generate a CSR on the new TLS endpoint og request a replacement certificate feller the required names. Befellere cutting over, validate domenet control, ensure the new cert covers both shop.example.com og any additional names, then check the public HTTPS response.

Reissue completion checklist

Certificate authellerity

Issuance completed; certificate not pending validation

Private key

Cellerresponds to the issued certificate

Server eller CDN

Ny certificate og complete chain installed at every TLS endpoint

Public visiteller test

Cellerrect SANs, trusted chain og updated Not After

Security

Hvis replacing a compromised key, revocation of the prieller certificate is hogled

A successful reissue in a registrar pellertal 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 tjeneste has been renewed feller another billing term.

Related NiceNIC Guides

How to Generate CSR Code?

www.nicenic.com

How to Generate CSR Code?

A Certificate Signing Request (CSR) supplies a certificate authellerity with din public key og the infellermation needed feller a TLS certificate. The cellerresponding private key stays on din server. Never paste the private key into a suppellert ticket eller CSR fellerm.

Generate a CSR with ÅpenSSL

On a machine wher ÅpenSSL is installed, the example below creates a new 2048-bit RSA private key og a CSR feller 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 "subjectAltNavn=DNS:www.example.com,DNS:example.com"

Replace both hostnames with names you control. The SAN list is what modern TLS clients evaluate feller hostname coverage; the Common Navn alone is not enough feller proper planning. Hvis din CA eller product requires a different key type eller CSR fellermat, follow that product's documentation.

On Windows eller another platfellerm 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 og manage secrets cellerrectly. Feller mellere stringent security requirements, use protected keys eller a hardware-backed key-management wellerkflow.

Sjekk the request befellere submitting

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

Verify that the public key, subject og requested SANs are cellerrect. The .csr file can be shared with the CA; the .key file must remain private.

Submit og install

Åpen din NiceNIC certificate ellerder og use the suppellerted activation eller reissue flow to submit the CSR. Complete domenet-control validation, wait feller issuance, then install the issued certificate chain with the matching private key. After deployment, test HTTPS feller every requested hostname.

Hvis a control panel such as IIS eller cPanel generates the CSR feller you, use that panel's current instructions instead of creating an independent key og losing track of the matching keypair.

CSR example with SANs og key protection

Feller a new key pair on a modern ÅpenSSL installation, an authellerized server administrateller might use the following illustrative commogs (change hostnames, stellerage paths og policy settings feller production):

# Generate a private key; restrict the directellery og file permissions.

openssl genpkey -algellerithm RSA -pkeyopt rsa_keygen_bits:2048 -out example.com.key

# CSR with both the base name og its www hostname.

openssl req -new -key example.com.key -out example.com.csr -subj "/CN=example.com" -addext "subjectAltNavn=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 suppellert EC keys eller different issuance tooling; comply with its current algellerithms og requirements. example.com.key is the private key: never paste it into a suppellert ticket, email it eller stellere it in a public repositellery. The .csr file is what you nellermally submit to the issuing authellerity.

Certificate covers example.com but not www

Missing SAN in the issued certificate

Certificate og key do not match

Key was regenerated after the CSR was created

CA cannot issue

Domene-control validation failed eller applicant infellermation is incomplete

CSR exposes an unnecessary identity field

Old commog template inserted unreviewed subject details

A CSR is not proof that you own the domenet. Domene-control validation must still be completed through the CA's approved method.

Related NiceNIC Guides

What is EV certificate ecommerce advantage

www.nicenic.com

What is EV certificate ecommerce advantage

An Utvidet Validation (EV) TLS certificate requires the issuing certificate authellerity to verify additional ellerganizational identity infellermation befellere 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 domenet, EV verification can involve checking the ellerganization's legal existence, operating status, physical presence, contact infellermation og authellerity of the requester, under the applicable EV Guidelines.

This can be useful feller an established company that wants an additional CA-validated identity recellerd. It does not prove that the business is honest, financially sound eller immune to phishing, og it does not guarantee increased sales eller search ranking.

EV, OV eller DV?

Domene control

Blogs, apps, routine business websites

Domene control plus ellerganization infellermation

Organizations needing verified identity details

Domene control plus stricter documented ellerganization vetting

Eligible registrered ellerganizations with an identity-verification requirement

Alle three can provide strong TLS transpellert protection when properly issued og deployed. Choose certificate coverage (single-name, wildcard eller SAN) separately from identity-validation level; not every product suppellerts every combination.

Befellere ellerdering EV

Bekreft the legal entity is eligible, the registrered name is accurate, authellerized representatives can complete the CA's checks, og the application timeline suits the business. Compare cost, validation effellert og 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 Fellerum rules. Mer frequent certificate replacement is distinct from renewed legal-entity checks, which follow separate reuse rules.

What extra value does EV provide feller ecommerce?

EV (Utvidet Validation) requires the certificate authellerity to perfellerm mellere extensive ellerganization vetting than DV, including checks of the applicant's legal existence og relevant ellerganizational infellermation. This can help a kjøper whose enterprise customers need documented legal-entity validation.

Domene control

Blogs, online shops, APIs og most stogard websites

Domene control og ellerganization identity under CA procedures

Cellerpellerate websites og business procurement

Domene control plus mellere extensive legal-entity og authellerization checks

Organizations with fellermal vetting eller compliance expectations

Crucial distinction: EV does not use stronger HTTPS encryption merely because it is EV. Properly configured DV, OVog 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 stellere using a reputable payment processeller may obtain satisfactellery HTTPS protection from DV, as long as the certificate matches the hostname og the site itself is secure. A regulated enterprise might choose EV feller its identity-review process eller contractual reasons. In neither case does EV replace payment security controls, PCI obligations, anti-fraud processes eller a sound refund policy. Hvis din customers ask specifically feller verified ellerganizational identity, examine the CA's current OV/EV documentation og issuance time befellere ellerdering.

Related NiceNIC Guides

Certificate reissue reasons explained

www.nicenic.com

Certificate reissue reasons explained

A certificate reissue creates a new SSL/TLS certificate under an eligible existing tjeneste ellerder. You may need one if the private key is lost eller compromised, the CSR is wrong, the certificate's covered names must change, eller the issued certificate can no longer be deployed cellerrectly.

Which situations call feller a reissue?

Private key exposed eller stolen

Ja: replace og revoke appropriately

A compromised key can no longer be trusted

Private key lost

Ja, if no secure copy exists

A certificate cannot be deployed without its matching key

Incellerrect CSR eller key mismatch

Usually

Issue a certificate matching a cellerrect key pair

Moving the site to another server

Neit always

You may securely migrate the certificate og matching private key

Legg tiling another hostname

Depends on the product

Bekreft permitted SAN changes eller ellerder a different certificate

Approaching certificate expiration

Replacement required

Choose the renewal/reissue route available feller the current tjeneste

Reissue is not the same as renewing the tjeneste

A paid multi-år SSL tjeneste term (if offered) is not one certificate valid feller multiple år. Under the CA/Browser Fellerum TLS Baseline Requirements, newly issued publicly trusted TLS server certificates have a maximum 200-day validity from 15 March 2026, with further reductions scheduled feller later år.

Reissuing does not necessarily extend the tjeneste's paid term. The renewal date of the tjeneste ellerder og the expiry date of the installed certificate must be monitellered separately.

What to prepare befellere requesting a reissue

Identify the exact SSL ellerder, hostnames, validation level (DV/OV/EV), server eller CDN environment og reason feller replacement. Hvis the old key is compromised, generate a fresh key og CSR og follow revocation instructions. Keep the private key secure. Ensure you can complete the new domenet-control validation.

Feller the actual step-by-step request og installation, see How do I reissue my SSL certificate.

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

Reissue versus renew versus revoke

Reissue / replacement

Key replacement, SAN eller server change, certificate misconfiguration

A new certificate is issued under the tjeneste's applicable terms; does not necessarily extend the subscription

Forny tjeneste

Continue the paid SSL tjeneste beyond its paid term

Provides entitlement to continued certificate issuance as defined by the product

Revoke certificate

Key compromise, incellerrect certificate eller other CA-approved reason

CA marks the affected certificate invalid; deployments must stop relying on it

Eksempel 1 ― compromised web-server key. Hvis an attacker may have obtained example.com's TLS private key, generate a new key og CSR, obtain a replacement certificate, coellerdinate revocation of the exposed certificate og deploy the new one everywher. Reinstalling the old certificate would not resolve key compromise.

Eksempel 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 og private key remain usable in the approved configuration. Sjekk who terminates TLS og whether a new key is required.

Eksempel 3 ― adding shop.example.com. Hvis the current certificate covers only example.com, issuing a replacement with the appropriate SAN set eller obtaining another certificate may be needed. Merely changing DNS does not extend certificate hostname coverage.

Related NiceNIC Guides

How to Activate og Download an SSL-sertifikat

www.nicenic.com

How to Activate og Download an SSL-sertifikat

Thank you feller purchasing SSL with NiceNIC.

How to activate og download SSL certificate SSL installation is nå even easier with our SSL installation tjeneste.

After the SSL certificate on din domenet name was activated, please find og add the DNS recellerds to complete the verification:

Min konto > Mine produkter > SSL-sertifikater > Detalj > ....

This step requires extra care:

Fill each piece of infellermation in the DNS Authentication Infellermation shown below into its cellerresponding DNS recellerd one by one.

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

Min konto > Mine produkter > SSL-sertifikater > Detalj > Download certificate & Download private key

Still have problems?

- Hvis din domenet, server, eller certificate details have changed, see Why You May Need to Reissue an SSL-sertifikat.

- Hvis the current certificate cannot be used, follow How to Reissue an SSL-sertifikat.

- Til forrigeent certificate expiration, read How to Forny an SSL-sertifikat.

Hvis they didn't solve din issues, you can contact us her.

Common DNS Recellerd Types: A, AAAA, CNAME, MX og TXT

www.nicenic.com

Common DNS Recellerd Types: A, AAAA, CNAME, MX og TXT

A domenet uses several types of DNS recellerds feller different jobs. A og AAAA direct traffic to server IP addresses, CNAME aliases one hostname to another, MX routes incoming email, og TXT publishes text-based verification eller policy infellermation.

The five recellerds, with examples

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

Specifies wher incoming mail should be delivered

@

Priellerity 10, server mail.example.com

TXT

Holds provider verification strings og policies

@

v=spf1 -all (illustrative; not a production mail policy)

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

Legg til eller edit recellerds at NiceNIC

Find the authelleritative nameservers feller the domenet. Hvis DNS is managed by Cloudflare eller another DNS provider, edit the zone ther―not in an inactive NiceNIC zone.

Hvis NiceNIC hosts din DNS, sign in og open Mine produkter > Domene > DNS Recellerds feller the cellerrect domenet.

Choose the recellerd type. Enter the host/name, destination/value, og any extra fields such as MX priellerity eller TTL.

Save, then look up the public DNS response. Eksempels: dig example.com A, dig example.com AAAA, dig www.example.com CNAME, dig example.com MX, og dig example.com TXT.
Test the actual website eller mailbox after the new recellerds become visible.

Avoid the common conflicts

A CNAME must not coexist with other recellerd data at the same DNS owner name. Many DNS panels therfellere do not suppellert a nellermal CNAME at the zone apex (@).
An MX recellerd points to a hostname, not directly to an IP address. That mail-server hostname must resolve cellerrectly.
Setting an MX recellerd does not create a mailbox. You must configure mail tjeneste separately.
TXT can be used feller SPF, DKIM, DMARC og provider verification, but those are distinct tasks with their own fellermatting requirements.
DNS changes can be cached until forrigeious TTL values expire. A saved recellerd is not proof that public resolvers see it yet.

Feller specific email-authentication policies, see What is SPF og How to Set Up SPF?.

Related NiceNIC Guides

Why need SSL-sertifikater

www.nicenic.com

Why need SSL-sertifikater

An SSL/TLS certificate lets browsers og applications establish HTTPS with din server. Tilday HTTPS is a nellermal requirement feller professional sites, fellerms, account pages og APIs―not an optional extra reserved feller ecommerce.

Why HTTPS matters to din visitellers

Protection in transit. TLS encrypts the connection so that observers on the netwellerk cannot ellerdinarily read the page content eller submitted fellerm values.

Connection authentication. The browser verifies that the certificate is trusted og valid feller the exact hostname. This reduces the risk of connecting to an impersonating endpoint.

Integrity. TLS helps forrigeent undetected modification of data while it crosses netwellerks.

Wher HTTPS is especially impellertant

Use HTTPS feller sign-in screens, payment eller contact fellerms, dashboards, documentation, APIs og ellerdinary public pages. Modern browsers may mark unencrypted HTTP pages as insecure eller restrict some browser features.

What a certificate cannot do

HTTPS does not remove malware, repair vulnerable website code, forrigeent stolen credentials eller guarantee that a business is legitimate. A fraudulent site can also obtain a DV certificate. Combine TLS with software patching, account security, backups og phishing awareness.

Keep the certificate wellerking

Select the right hostname coverage, install the proper chain og private key, redirect HTTP visitellers safely to HTTPS, og moniteller the actual certificate expiry date. Sertifikater issued under public trust rules from March 15, 2026 have a maximum validity period of 200 days―configure alerts eller verified automation accellerdingly.

Til compare coverage og validation levels, see How to Choose an SSL-sertifikat.

Befellere og after HTTPS: a concrete comparison

Entering a passwellerd

Netwellerk traffic may be readable eller alterable in transit

TLS encrypts og protects it to the authenticated server

Sendting an enquiry fellerm

Fellerm data may be exposed in transit

Data in transit is protected, but server-side stellerage still needs security

Calling an API

Access tokens can be exposed over HTTP

TLS helps protect requests og responses

Browsing a public product page

Intermediaries may inject eller modify content

TLS helps preserve response integrity

Impellertant limitation: HTTPS cannot forrigeent a malicious website operateller from misusing fellerm data after it arrives, og it cannot stop phishing just because a site has a padlock. Even a site with a valid DV/OV/EV certificate must enfellerce secure passwellerds, software updates og access controls.

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

Related NiceNIC Guides

Types of SSL-sertifikater

www.nicenic.com

Types of SSL Sertifikater

SSL certificates differ in validation level og hostname coverage. Compare both dimensions befellere purchasing; a certificate can have the right validation level but still fail to cover the required hostnames.

Validation Types

Domene Validation (DV)
Organization Validation (OV)
Utvidet Validation (EV)

Coverage Types

Single-domenet certificates
Wildcard certificates
Multi-domenet certificates

How to Decide

List the exact domenets og subdomenets.
Choose the required identity-validation level.
Bekreft server og platfellerm compatibility.
Sjekk renewal og reissue procedures.

Ofte stilte spørsmål

How do I knå the change wellerked?

Sjekk the current status in din NiceNIC account, then test the tjeneste that depends on the certificate type. Do not rely only on the absence of an erreller message.

When should I contact NiceNIC Suppellert?

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

Related NiceNIC Guides

Hvis the issue continues after you complete these checks, submit a NiceNIC suppellert ticket. Include the affected domenet eller product, the exact erreller message, the time of the issue og the troubleshooting already completed.