SSL certificates
Certificates issued and installed for domains hosted with us, so browsers connect over an encrypted channel and stop warning your visitors away.
Home/SSL & Security
SSL, HTTPS and the security basics that actually get used
Certificates, encrypted connections, DNS hygiene and account security — the practical layer that keeps a website trusted by browsers and usable by customers.
A note on security claims No hosting provider can make a website completely secure, and we will not tell you otherwise. Security is a set of ongoing practices shared between the host, the website’s developer and the people who hold the passwords. What follows is what we do, and what we ask of you.
HTTPS configuration
HTTPS enabled for the site, with redirects and mixed-content issues addressed during setup so the padlock actually appears on every page.
Website security practices
Sensible server-side configuration and guidance on keeping the application layer — CMS, themes, plugins — updated, which is where most compromises begin.
Account security
Separate credentials, prompt removal of old access and a clear reporting route. Most incidents start with a password, not a server.
DNS and domain security
Correct name server and record configuration, careful handling of registrar changes, and domain privacy where the extension allows it.
Incident response
A defined route for reporting a suspected compromise, and an honest assessment of what happened and what remediation involves.
SSL certificates
What HTTPS does, and what it does not do
What it does: encrypts the connection between a visitor’s browser and your server, so data in transit — form entries, logins, payment details — cannot be read or altered along the way. It also removes the “Not secure” warning browsers show on unencrypted sites.
What it does not do: it does not clean up a hacked website, patch outdated software, protect a weak password, or vouch for the honesty of whoever runs the site. HTTPS is a prerequisite, not a security programme.
- Certificate issued and installed for your domain
- Site served over HTTPS, with HTTP redirected where appropriate
- Renewal handled so the certificate does not lapse
- Mixed-content issues flagged during setup
Account security we ask you to maintain
- Use a unique password for the client portal and for hosting control panel access
- Do not share one login across a team — ask us for separate access instead
- Keep the email address on your account current and secure
- Remove access for people who leave, promptly
- Keep website software, themes and plugins updated
- Report anything unexpected to [email protected] straight away
We will never ask you for your password by email. Any message that does is not from us.
If something goes wrong
Reporting a suspected compromise
Speed matters more than detail. Contact us first, then gather the specifics.
First
Tell us immediately
Email [email protected] or raise a ticket in the client portal with the affected domain in the subject line.
Then
Change the credentials you control
Client portal, control panel, website admin and mailbox passwords — from a device you trust.
Then
Record what you saw
Times, error messages, unexpected emails, changed content. This shortens the investigation considerably.
Finally
Agree the remediation scope
Cleanup work is assessed per incident. We will explain what we find, what we can do, and what sits with your developer.
Get the security basics right from the start
SSL, HTTPS, DNS records and sensible account practices are part of setting up a service with us — not an upsell after something breaks.