Security & DNS
TLS certificate estates issued, installed, automated and monitored across websites, mail, control panels and internal services so nothing expires unnoticed.
Certificates are inventoried, issued to a plan, installed with the full chain and renewed automatically u2014 expiry should never be an incident.
Every endpoint terminating TLS is listed with its issuer and expiry date.
Validation level chosen per service; public sites and payment paths are treated differently from internal tools.
Renewal runs unattended, with reload hooks so services actually pick up the new certificate.
Configuration is tested externally after every change, not assumed from the panel.
The encryption is identical. Paid certificates buy organisation validation, longer terms, warranties and support u2014 useful for public-facing commerce, unnecessary for most internal services.
Almost always a missing intermediate certificate. The full chain has to be installed, which is why every change is verified with an external checker.
It simplifies many subdomains on one platform, but one private key then covers everything. Where hosts are administered by different people, separate certificates are safer.
Yes. Both panels support ACME issuance, and renewal plus service reload is configured so certificates never lapse.
Send the environment details and get an engineered proposal with assumptions, risks and a rollback path.