Learn what an SSL certificate does, how HTTPS protects visitors, and why browsers expect a valid certificate on your website.

Domain Validation, Organization Validation, and Extended Validation differ in how the issuer checks your business and what visitors may see in the browser.

Understand what you generate, what MixSSL issues, and which files you must keep private when installing HTTPS.

See when a single domain, wildcard, or extra names (SANs) are the right choice for your website and subdomains.

How long certificates last, when to renew before expiry, and when a reissue is needed instead of a simple renewal.

Register on MixSSL and confirm your email address before you buy a certificate or complete payment.

Use the MixSSL catalog to compare brands, validation type, wildcard and SAN options, and see the price for your chosen term.

How paid orders work on MixSSL, what happens after payment, and how refunds apply to paid certificates.

After payment, use your MixSSL account to verify your CSR, prove domain control, and submit the order for issuance.

Where to download CSR, certificate, and CA files from your account, and how the 30-day refund policy works for paid orders.

A plain-language guide to your certificate file, intermediate chain, private key, and ZIP download from your account.

Step-by-step guidance for small businesses using Nginx: where to place the certificate, key, and chain files.

How to configure Apache httpd with your certificate, private key, and CA chain from MixSSL.

Import your certificate and private key on Windows Server or IIS hosting for HTTPS on your business site.

Upload your MixSSL certificate through cPanel, Plesk, or similar panels when you do not manage the web server directly.

Quick checks any business owner can do: padlock icon, certificate expiry, and domain name on the live site.

Paste your live certificate into the free SSL Decoder on MixSSL to read expiry, domains, and issuer in plain language.

Why missing intermediate certificates cause trust warnings, and how to confirm the full chain is installed.

Make sure the certificate covers www, bare domain, and any extra names you bought—wildcard rules explained simply.

For owners who work with a hosting partner or IT helper: simple OpenSSL commands to test HTTPS on the server.

Fix common CSR problems: wrong domain format, too many names, IP addresses on products that do not support them, or weak key size.

DNS, HTTP, file, and email validation tips when your order stays in processing on MixSSL.

Why wildcard orders often require DNS validation, especially on Let's Encrypt products sold through MixSSL.

Troubleshoot trust errors, expiry, installing the wrong file, or serving an old certificate after you renewed.

How to reissue, add SANs when allowed, pay an unpaid order, and reach support without phone lines.