Who Has the Keys? Protecting the Accounts Behind Your Website
Protect the accounts behind your website with stronger MFA, individual access, a password manager, and recovery routes you can still reach.

Most small-business websites depend on a handful of accounts: the domain registrar, the DNS provider, hosting, business email, and the site's admin login. People with administrator permissions may be able to change your site, redirect email, or alter renewal settings. Protecting them takes some setup and a short review a few times a year: turn on the strongest multi-factor authentication each account offers, make sure recovery messages reach an address you control, use a password manager, and give each person their own login.
Step 1: Map the accounts
Make a list. For each account, write down the company, the login email, who has access, and what it controls. Common entries:
- Domain registrar: where the domain is registered and renewed.
- DNS provider: often the same company as the registrar, sometimes not. DNS decides where your website and email point.
- Hosting: where the site files or platform live.
- Business email: your inbox, and where many password reset links are sent.
- Website admin or content editor: where pages and posts are changed.
- Connected tools: forms, booking, analytics, payment, and newsletter services.
The Wild Logic website ownership checklist is a checklist you can use without creating an account. It advises keeping the record free of passwords and recovery codes, and pointing to entries in a password manager instead.
Step 2: Turn on the strongest MFA each account offers
Multi-factor authentication (MFA) uses two distinct factors, such as a password and a security key or authenticator app. NIST's digital identity guidelines describe how requiring two factors increases assurance compared with single-factor authentication.
Not all MFA is equal. Prefer phishing-resistant methods where offered, such as FIDO/WebAuthn security keys or passkeys. NIST's digital identity guidelines explain that methods requiring you to type in a code are not phishing-resistant.
Start with business email. If someone takes over your inbox, they may be able to reset many of your other passwords. Then the registrar and DNS, then hosting and the site admin.
Step 3: Keep recovery paths off the domain
A common trap: the registrar account's recovery email is an address at the same domain it controls. If the domain lapses or DNS breaks, that email stops working at the moment you need the reminder.
ICANN's Expired Registration Recovery Policy includes a suggested best practice: registrars should advise customers to provide a secondary email "that is not associated with the domain name itself" so expiration reminders still arrive. Apply the same idea to recovery phone numbers and backup codes: keep them current, and store backup codes in your password manager or another safe place you control.
Step 4: Use long, unique passwords and a password manager
Use a long, unique password for each account. Follow the service's requirements and keep credentials in a password manager.
NIST's digital identity guidelines, SP 800-63B-4, are written for organizations that run login systems, not for business owners. Their direction is still useful: favor length over complicated character rules, allow password managers and pasting, and change a password when there is evidence it was compromised, rather than on a fixed schedule.
A password manager makes this realistic. It generates and remembers a different password for every account, so one leaked password does not open everything.
Share access by inviting each person to their own account, or through a secure sharing method you both agree on. Keep passwords and backup codes out of ordinary email, texts, and forms.
Step 5: Give people their own logins
Shared logins hide who changed what, so where a service allows it, give each employee or contractor their own account with only the access they need. The FTC's cybersecurity guidance recommends limiting vendor access to the information and time needed. When a contractor finishes, remove their account, but never the only working owner account.
A quarterly access review
Our recommendation: put an access review on the calendar every three months, and repeat it when staff or providers change.
- Open your account map and confirm every entry is still accurate.
- Sign in to each account yourself to confirm you still can.
- Remove anyone who no longer needs access.
- Confirm MFA is on, and upgrade to a stronger method where one is now offered.
- Check renewal dates and that renewal notices reach a working address.
- Update the map.
A hypothetical example
This example is made up. A two-person cleaning company shares one email login with a former office manager. The registrar's recovery address is that shared inbox. After a review, each owner gets an individual account with MFA through an authenticator app, the former manager's access is removed, and the registrar's recovery email is moved to an address on a different domain. Nothing about the website changed, but the company now knows who can change it.
If you think an account was compromised
Change the password from a device you trust, sign out other sessions if the service offers it, turn on or reset MFA, and check recovery settings and forwarding rules for changes. If scammers are emailing as your business, the FTC suggests reporting it at ReportFraud.ftc.gov and IC3.gov and telling your customers. For a serious incident, get qualified help.
Use the website ownership checklist to keep the account map together. Store secrets separately.
Evidence
Sources
- NIST Special Publication 800-63Bpages.nist.gov · Retrieved
- Expired Registration Recovery Policywww.icann.org · Retrieved
- Cybersecurity for Small BusinessFederal Trade Commission · Retrieved
A useful next step
Keep a useful record
Use the ownership checklist to organize the accounts and people involved in your site.
Open the ownership checklist