Certificates are automatic

Every domain you point at a site here gets a certificate automatically, usually within a few minutes of DNS resolving, and it renews itself for as long as the domain points here. There is nothing to buy, upload or configure.

Why yours might be pending

A certificate can only be issued for a name that already resolves to us. So the order is always: point the DNS, wait for it to resolve, certificate arrives. A domain still showing Pending an hour after it went Active is worth a ticket.

A browser warning on a site that has a certificate

Three causes, in the order they actually happen:

1. You are visiting a name the certificate does not cover — www.example.com when only

example.com was attached. Attach both; the site screen does it in one click.

2. Mixed content. The page is served over HTTPS but pulls an image or a script over HTTP,

so the browser says the page is not fully secure. The site's own settings are where that is fixed, and on WordPress it is usually one hard-coded URL in the database.

3. The clock on the visiting device is wrong. Rare, and unmistakable once you check it.

Bringing your own certificate

Supported where you genuinely need it — an EV certificate your compliance team insists on, or a wildcard issued elsewhere. Sites → your site → Domains → Certificate. For everything else the automatic one is the same encryption and one fewer thing to let expire.