OOmnistu

Blog / Security

Security

Website admin account security: protecting the logins that run your site

Attackers do not need to hack your site if they can log in as you. The three habits that protect hosting, CMS and registrar accounts: long unique passwords, MFA, and tight permissions.

OOmnistu
Reviewed 2026-11-20 · 3 min read

An attacker does not need to break your website's code if they can simply log in as you. The accounts that run your site - hosting, CMS admin, domain registrar, and the email address that resets them all - are the master keys, and they deserve at least as much care as the site itself. This guide covers the three habits that matter most, grounded in CISA's Secure Our World guidance.

Passwords that hold

CISA's advice for strong passwords comes down to three properties, and a strong password has all three. First, long: at least 16 characters, where longer is stronger. Second, random: either a generated string of mixed letters, numbers and symbols, or a passphrase of four to seven unrelated words. Third, unique: a different password for every account, so one leaked password opens exactly one door. Nobody memorizes dozens of these, which is why CISA recommends a password manager - it generates and stores the strong ones so you only need to remember one. Simple passwords and personal details like birthdays, CISA notes, are the equivalent of locking the door but leaving the key in the lock.

Add the second lock

Multifactor authentication means a stolen password alone is no longer enough: CISA's guidance is to turn it on wherever it is offered, because an unauthorized user who has your password still cannot meet the second step. Prioritize the accounts in order of blast radius - the email address that receives password resets first, then hosting, the CMS, and the registrar. Our two-factor authentication and MFA comparison guides go deeper on the options; the short version is that an authenticator app or security key beats SMS where you have the choice.

People and permissions

Admin hygiene is also about who holds keys, not just how strong they are. Give each person their own account rather than sharing one master login - shared logins make it impossible to tell who changed what and painful to revoke one person's access. Grant the least access that lets someone do their job: WordPress, for example, defines roles from Administrator down through Editor, Author and Contributor to Subscriber, each with different capabilities, so the person writing posts rarely needs the account that installs plugins. Remove accounts promptly when a contractor or employee moves on.

Mind the recovery paths

Every account you own eventually offers a "forgot password" link, and those links point somewhere - usually your email inbox. That makes the email account the true master key: secure it first, with a unique password and MFA. Keep recovery phone numbers and backup addresses current so a legitimate lockout is an inconvenience rather than a catastrophe, and store any backup codes somewhere you will actually find them.

FAQ

Is a password manager safe to trust with everything?

CISA recommends using one: the alternative to a manager is reused or written-down passwords, which are worse. Protect the manager itself with a long, unique master password and MFA, and the trade favors you clearly.

How many admin accounts should my site have?

One per person who genuinely needs administrative access, and no more. Everyone else gets a role with only the capabilities their work requires - separate accounts also mean you can revoke one person without disrupting the rest.

I already reuse passwords everywhere. Where do I start?

Change the highest-stakes accounts first: your email, hosting, CMS admin and registrar, each to a long, unique password. A password manager then makes fixing the long tail tractable instead of overwhelming.

Does MFA make strong passwords unnecessary?

No - CISA presents them as separate, complementary habits. A weak password still gets tried first, and MFA can occasionally fail or be bypassed; a strong, unique password plus MFA means both layers have to give way.