Five things to check about your website and the people who can change it.

Who this is for. A shelter or rescue that has a website, a volunteer who “does the tech”, or a company that builds or hosts software for you, and nobody on staff who can judge whether that is being done safely.

What you will have at the end. A list of every person and company that can change your website or systems, two-step sign-in on the accounts that matter most, a copy of your website that you control, and five questions to ask any software vendor with a sense of what a good answer sounds like.

Walkthrough 1: List who can change your website

  1. Write down where your website lives. Ask whoever set it up: is it WordPress, Squarespace, Wix, a site a volunteer built, or something your shelter-software vendor provides? Write down the company and the login address.

  2. Open the people list. Each platform has one. In WordPress it is Users in the left menu of your dashboard. In Squarespace it is Settings > Permissions. In Wix it is Settings > Roles & Permissions. If a volunteer keeps the site in GitHub, it is the repository’s Settings > Collaborators and teams.

  3. Write every name down, with what they can do. Owners and administrators can do anything, including lock you out. Editors can change pages. If a name belongs to someone who left, a past volunteer, or a company you no longer pay, remove it today.

  4. Make sure your organization owns the account. The owner login should be an address at your organization (for example director@yourshelter.org), not a volunteer’s personal email. If it is not, ask the platform’s support to transfer ownership.

How you know it worked. The list has only current people on it, and the owner is an address your organization controls.

Walkthrough 2: Turn on two-step sign-in for the accounts that control the website

The owner account for your website, your domain name (the company you pay yearly for yourshelter.org), and any code hosting are the three logins an attacker most wants. Two-step sign-in means a stolen password is not enough.

  1. Start with the domain registrar. Sign in to the company that sells you your domain name (GoDaddy, Namecheap, Cloudflare and others). Open the account security settings and turn on two-step verification, using an authenticator app on a phone rather than text messages if offered.

  2. Then the website platform. In WordPress this needs a plugin or your host’s setting; ask your host. In Squarespace it is Account > Account & Security > Two-factor authentication. In Wix it is Account Settings > Privacy & Security > 2-Step Verification.

  3. Then code hosting, if any. On GitHub, open your password and authentication settings and click Enable two-factor authentication. GitHub’s own instructions cover the choices.

  4. Save the recovery codes. Every one of these services gives you a short list of backup codes when you turn it on. Print them and keep them with the other important papers, not on the computer.

How you know it worked. Signing out and back in asks for a code from the phone. The printed recovery codes are in the binder.

Walkthrough 3: Keep a copy of your website that you control

If the volunteer disappears or the company folds, you should be able to hand your site to someone else.

  1. Export the content. In WordPress: Tools > Export > All content > Download Export File. In Squarespace: Settings > Advanced > Import / Export > Export. In Wix, there is no full export; copy the text of each page into documents and download your images from the Media Manager. In GitHub: open the repository, click the green Code button, then Download ZIP.

  2. Export the domain details. From the registrar, note the nameservers and any DNS records (your registrar’s support can send them as a file). These are what point your name at your site and your email.

  3. Put the copies somewhere safe. A folder in your organization’s shared drive named website-backup with the date in the file names. Repeat twice a year and after any big change.

How you know it worked. A folder with this month’s date holds the export files, and someone other than the person who made them knows where it is.

Walkthrough 4: Five questions for anyone who builds software for you

Send these to any vendor, contractor or volunteer who writes or hosts software that touches your data. You do not need to understand the answers in detail; you need to notice whether they have one.

  1. Who can push changes to our live site or system, and what has to happen first? A good answer names people and says a second person reviews every change before it goes live.
  2. Do you check your code and the parts you borrow for known security problems before each release? A good answer says yes, automatically, every time, and names a tool or two.
  3. Where is our data, who else can see it, and how do we get it back if we leave? A good answer names the hosting company and the country, says only named staff can see it, and offers an export in a common format.
  4. How do you handle a security problem someone reports to you? A good answer has an email address for it and a promise about how fast they respond.
  5. When did an outside party last test your security, and can we see a summary? A good answer gives a date within the last year or two and sends a one-page summary.

How you know it worked. You have written answers to all five in the vendor’s own words, in the binder from the insurer and board guide. A vendor who cannot answer in a paragraph is telling you something.

Walkthrough 5: If a volunteer keeps your code on GitHub

Two free settings catch most problems without anyone watching.

  1. Turn on alerts for borrowed code with known problems. In the repository, click Settings, then Advanced Security (older accounts show Code security and analysis) in the left menu, and turn on Dependabot alerts and Dependabot security updates.

  2. Turn on secret scanning. On the same page, turn on Secret scanning and Push protection, so a password or key pasted into the code by accident is caught before it is saved.

  3. Add the ready-made checks. The security checks this site runs on itself are free to copy from security-pipelines. Your volunteer can add one short file to the repository and get secret scanning, code scanning and a broken-link check on every change.

How you know it worked. The repository’s Security tab shows the features as enabled, and a change that includes a pasted password is refused.

What I could not show you a picture of

Walkthroughs 1, 2 and 3 happen inside your own accounts on WordPress, Squarespace, Wix, your registrar and GitHub, so the menu paths above come from each vendor’s help pages rather than from screenshots, and this guide has no pictures yet. If a path has moved, tell me and I will fix it. If you want help reading a vendor’s answers, write to me. It is free.