HTTPS & SSL Guide for .boo, .day, .dev, .page, and .rsvp - FAQ

Quick Answer

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

Before You Begin

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

NiceNIC Instructions

HTTPS & SSL Configuration Guide To ensure the security of your website and protect your visitors, all domains under.boo,.day,.dev,.page, and.rsvp must use HTTPS. This guide will help you configure SSL/TLS correctly.

What is HTTPS? HTTPS (Hypertext Transfer Protocol Secure) encrypts data between your website and its visitors. It prevents eavesdropping and ensures data integrity.
Obtaining an SSL Certificate NICENIC provides trusted SSL certificates. You can learn more and purchase/configure a certificate here: https://nicenic.com/ssl-certificates/
Installing the SSL Certificate Follow your 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
Enforce HTTPS Once your certificate is installed: Redirect all HTTP traffic to HTTPS. Update internal links and resources to use HTTPS. Verify that your website is fully accessible via HTTPS.
Keep Certificates Updated SSL certificates have expiration dates. Ensure certificates are renewed before they expire and check your website regularly to maintain uninterrupted secure connections.

How to Verify

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

Troubleshooting

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

Frequently Asked Questions

Can I reuse the same certificate after moving servers?

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

Why does the browser still show the old certificate?

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

When should I submit a ticket?

Submit a ticket when validation remains pending after the published records are visible, or when the NiceNIC order does not provide the expected certificate files.

Related NiceNIC Guides

If the issue continues after you complete the checks above, submit a NiceNIC support ticket with the affected domain or product, the exact error message, the time of the issue and the troubleshooting already completed.