When you hire somebody to build or fix your website, you give them a way in. That is not a mistake - they cannot do the work otherwise. The mistake is that nobody ever takes it back. The project ends, the invoice is paid, everybody moves on, and the way in stays exactly where it was.
We are not suggesting your old developer is going to attack you. Almost nobody does. The risk is duller than that and much more common: their laptop is stolen, or their own email is broken into, or they keep the key in a folder that gets backed up somewhere careless. Your site is then exposed through a door you forgot you had cut.
What SSH actually is, in one paragraph
Your website lives on a computer in a data centre. SSH - Secure Shell - is the standard way for a human to log in to that computer from somewhere else and type commands directly at it. It is not the same as logging in to WordPress, and it is not the same as your hosting control panel. It is a level below both of them. Somebody with SSH access does not need your WordPress password, because they can read, change or delete the files WordPress is made of, the database behind it, and the records of what happened.
That is why it is the first thing worth auditing and the last thing most people think of. A strong admin password protects the front door of the house. SSH is the floor.

Why the list grows and never shrinks
Access is granted in a hurry and removed never. Every one of these is an ordinary Tuesday afternoon, and every one of them leaves something behind:
- The agency that built the site. Given full access on day one, because that is what building a site needs. Still has it three years and two redesigns later.
- The freelancer who fixed one thing. Added a key to sort out a broken form in 2024, was paid, and was never removed because removing people is nobody’s job.
- The developer who left that agency. Their key is on your server under the agency’s account. When they resigned, your site was not on anybody’s offboarding list.
- A migration that was never cleaned up. Moving hosts often means temporary access for the new host’s team, and temporary has a way of becoming permanent.
- Your own old laptop. The key you generated on the machine you sold or threw away is still trusted by the server, because the server has no way of knowing the laptop is gone.
None of that is negligence by anybody in particular. It is simply that adding access solves a problem today and removing it solves a problem that has not happened yet.
The five kinds of access worth checking
People say "who has access to my website" as if it were one thing. It is five, and they are kept in five different places. Check them in this order, because they go from most powerful to least:
The hosting account itself
The login that can delete everything, move the domain, or cancel the plan. Check who is listed as an owner and who has been invited as a sub-user. This one should be you, and almost nobody else.
SSH keys and SSH passwords
The list of keys trusted by the server, plus whether password login over SSH is switched on at all. This is the one nobody looks at.
FTP and SFTP accounts
Older sites often have several, created one per person or per job, with names like "designer" or "temp". Each is a working login until somebody deletes it.
Database users
Your site needs one. Some setups accumulate more - one from an old plugin, one from a migration tool, one from a developer’s test.
The CMS itself
WordPress administrators, Shopify staff accounts, and anything with the word "admin" on it. The easiest to check and the one most people stop at.
How to see your own list
Where this lives depends on your hosting panel. The two most common in our own client base are cPanel and Hostinger’s hPanel:
- cPanel. Security → SSH Access → Manage SSH Keys. The page lists every public key the server knows about and shows whether each is authorised.
- Hostinger hPanel. Advanced → SSH Access on shared and web hosting plans. The same page carries the on/off toggle and the list of keys. On a VPS it is under the server’s own Settings → SSH keys instead, and on agency plans under Advanced → Remote Access. Whether SSH is available at all depends on your plan tier, and the published guidance on which tiers include it does not agree with itself - so if the menu is missing, that is the likely reason rather than anything being broken.
- Anything else. Search your panel for "SSH". If there is genuinely no such page, your site may be on a plan without SSH at all, which is one fewer thing to worry about - go and check the FTP accounts instead.
Underneath whichever panel you use, the trusted keys are kept in a single file on the server called ~/.ssh/authorized_keys. You do not need to open it. It is worth knowing the name, for the reason in the next section.
The trap: deauthorise before you delete
This is the part that catches people, and it is the reason a tidy-up can look done while the access is still live.
In cPanel, a key has two separate states: it exists in your account, and it is authorised to log in. Those are stored in two different places. Deleting a key from the list does not reliably remove it from authorized_keys, which is the file the server actually consults when somebody knocks. It is entirely possible to delete a key, see it vanish from the page, and leave the holder able to log in exactly as before.
So the order matters. Deauthorise first, then delete. And afterwards, ask your host to confirm the key is gone from authorized_keys - one short support message, and the only way to be sure.

Keys beat passwords, and why
If SSH on your server accepts a password, then anybody on the internet can sit there and guess. They do, constantly and automatically, on every server with a public address - not because they have singled you out but because trying millions of addresses costs them almost nothing.
A key works differently. You hold a private half that never leaves your machine; the server holds the public half. There is nothing to guess, because the secret is never sent. Turning password login off and using keys only is the single change that removes the entire category of guessing attacks against SSH - and it is a setting, not a project.
- Put a passphrase on the private key. Without one, the key is a single file - whoever ends up holding it is you, as far as the server is concerned.
- One key per person, never a shared one. A shared key cannot be revoked for one person, and when something odd appears in the logs it cannot tell you who did it.
- Ed25519 for anything new. It is the current default key type, short and well supported. If an existing key is an old 1024-bit RSA, replacing it is worth the ten minutes.
- Restrict where logins can come from, if your host allows it. Limiting SSH to known addresses or a VPN turns a global problem into a local one.
One practical warning for whoever does the work: changing SSH settings while connected over SSH is how people lock themselves out of their own server. Keep a second session open until the new setting is proven. Your host can let you back in, but it is a bad afternoon.
What good looks like
You do not need a security programme. For an ordinary business website, this is the whole of it:
A list you have actually seen
You know who can log in, at every one of the five levels, because you looked once and wrote it down.
Nobody on it who has left
Access ends when the work ends. Removing it is a line on the project checklist, not a favour.
Keys, not passwords
Password login over SSH is off. Every key has a named owner and a passphrase.
A date in the calendar
Once a year, beside the domain renewal. Five minutes, and it is the only reason any of the above stays true.
The conversation to have with whoever built your site
If an agency or freelancer built your website, you are allowed to ask them this, and a good one will answer the same day. Four questions:
- Who at your end currently has access to my hosting and my server, by name?
- What happens to that access when one of them leaves your company?
- Is SSH password login switched off on my server, and does every key have an owner?
- When our work together ends, what is your process for removing it all?
Nobody should be offended by those. We are asked them and we answer them. If the reply is vague, or you are told it does not matter, that is itself the answer - and it is worth knowing before something goes wrong rather than after.
If you want to know what else is open on your site before you have that conversation, the free website audit checks the things visible from outside - HTTPS, security headers, the server software you are announcing to the world - in about twelve seconds. It cannot see your key list; nothing from outside can. But it will tell you whether the rest of the house is locked.