Your Website, Protected · No. 27

What your website runs on, and the five minute check that tells you

If you cannot say what your site is built on, you can get a first answer in five minutes from your own browser. Written answers from the builder come later.

A yellow magnifying glass with a red handle resting on a blue blueprint sheet with white grid lines, stacked on green and red sheets, on a warm white background.

You read a headline about a website flaw, then open your own site and realize you cannot say what it is built on. The person who built it stopped answering email a while ago. Maybe the site was a gift from a nephew, a favor from a friend, or a project from an agency that has since closed.

You can get a first answer on what your website is built on in about five minutes, alone, from your own browser: look at the login you use, read the names in the page source, and count what the site has to keep running.

The five minutes is the looking. Written answers from whoever built the site come later, if you can reach them, and the note you make now tells you which questions to send. If you cannot reach them, the note still stands on its own.

Move the pointer over the tray and each layer stands up and says its name. The red ones at the back are the parts that need updating.

The short answer

  • Look first, alone: your login, the page source, your inbox and any plugin list.
  • Write down every name you find. That note is the result of the five minutes.
  • Ask the builder and the host in writing later, and keep the replies.

Why what your site runs on decides what you maintain

A website is a stack of layers, and a layer your site runs is a layer someone has to keep current. Knowing what yours runs on tells you what needs updates each month, which published flaws could reach your site, and who to call when something breaks. Without that, a headline about a flaw is just noise.

The layers are a theme or page builder, plugins, a database, code that runs when someone visits, and finally the page itself. Each layer that exists needs someone to keep it current, and each one a published flaw can reach is a door. At one end sit plain finished pages. At the other sits a site with a theme, plugins, a database and server code. The drawing puts those two ends side by side. Neither end is good or bad on its own.

A site with parts to run (example)

  1. Theme or page builder updates monthly Needs updates
  2. Plugins updates per plugin Needs updates
  3. Database builds each page Runs on request
  4. Server code starts each visit Runs on request

Two chores and two layers that run on each visit

A site served as finished pages (example)

  1. Finished page files built before the visit Nothing to run
  2. Host that sends the file sends the file Nothing to run

No database, plugins or per-visit code

An illustration of how we count moving parts.

In our view, a site's exposure is better judged by counting the moving parts it exposes than by blaming the owner. Plugins, a database and per-visit code are the three we count, and a site built as finished pages carries none of them. We covered what an attacker can reach in three doors into a hacked site.

A site with moving parts can be kept well, and a site with none can still be neglected. Either way, the count tells you what to ask about.

The five minute check, done alone

Run the check from a phone or laptop with nothing installed or changed. Look at the login you use or were given, read the names in the page source, count plugins if a dashboard lists them, and search your inbox for hosting and domain notices. Each look takes about a minute, and you write down what you find.

The five minute check

  1. Find your login

    Open the login page you use or were given. Write down its address and any name shown on the page. If you have no login at all, write that down too.

  2. Read the page source

    On a laptop, right click the page and choose the option to view the page source. Read the names it mentions and write down any you do not recognize.

  3. Count the parts

    If a dashboard lists plugins or add-ons, count them. Note whether anyone has told you a database or code runs when someone visits.

  4. Search your inbox

    Look for hosting and domain notices. Write down which name and email address they carry.

  5. Write the note

    One page: what the site seems to run on, the names from the source, the plugin count, and who gets the notices.

Here is how we read the results. A login page means someone logs in, which means accounts to protect and software to keep current. No login anywhere earns a follow up question for later: is the site served as finished pages? The page source is plain text, and you are reading names in it, such as a theme, a builder or a tracking script. Write down each one you cannot place, because a name you cannot place is still a question to send the builder.

The looking and the asking are separate on purpose. You can finish the looking today, alone. The asking depends on someone else, so it goes on a list and waits.

Here is how one run might go. In the example below, the owner finds most answers alone, and the builder never replies.

Example: one owner runs the five minute check

Looking alone

  • Found the login page Pass
  • Read the names in the page source Pass
  • Found the hosting and domain notices Pass

All passed

Asking in writing

  • Builder named what the site runs on Fail
  • Builder sent the monthly update list Fail

2 failed

An example run with made up results. A fail here means no answer yet.

Read the example this way. A pass is an answer the owner now has. A fail is a question still open, so it goes on the list for the builder or host, and the owner moves on. The first group is five minutes of looking. The second group waits for replies.

The point of the split is the order. Your own browser and inbox answer the first group, so you have something to hold before anyone replies. If a reply never comes, the note still tells a new builder where to start.

What each result can mean
  • A login page exists What you may see Software to keep current
    A login page exists What to do Ask later who updates it and how often
  • No login page What you may see Possibly finished pages
    No login page What to do Ask the builder to confirm in writing
  • Many names in the source What you may see Many parts to ask about
    Many names in the source What to do Send the list and ask what each one does
  • Nobody answers What you may see Nobody may own it
    Nobody answers What to do Search your inbox for hosting and domain notices

Tap a card to see what to do about each result.

What a published flaw can reach on your site

A published flaw usually matters to your site only if your site runs the affected part. If it has no plugins, no database and no code running on each visit, a flaw in those parts has far less of yours to reach. If it has all three, each one is a door worth checking.

A headline about a flaw names one product or one kind of part. That turns a scary story into a checkable fact. In our view the first question is does my site run that part? An owner who has written down what the site runs on can answer it in a minute. We worked through one example in a flaw that turned out not to be a WordPress bug.

Here is what that written note can look like after the check, with made up entries.

Example

Example: the owner's note after the check

Page Size Result
Login page Found, address written down Pass
Page source names Names listed, one unknown Pass
Plugin count No dashboard access yet Fail
Hosting notices Go to the builder's email Fail
An example of a note, with made up entries. A fail is a question still open.

Who to ask, and what to put in writing

Ask whoever built the site and whoever hosts it, and put three questions in writing: what the site is built on, what must be updated each month and by whom, and who holds the logins. A clear written reply is your record. If nobody answers, your own note from the check is still a record, and it tells you what to ask the next person you hire.

A written reply can be forwarded to whoever you hire next, and it shows how well the builder knows their own work. Ask for facts, and keep the reply somewhere you can find in a year.

If the builder has gone quiet, the inbox search from step four still shows who receives the hosting and domain notices, and that person is where to start. Three people may hold the answers.

Who can answer what

  • You, the owner

    Your login, the page source and your inbox

  • The builder

    What it is built on and what needs updating

  • The host

    Whose account the site sits under

If the builder names a framework, for example Astro, a JavaScript web framework for building fast, content-driven websites, write the name on your note and ask what it needs from you each month.

Ask whose name is on the hosting account and the domain, since those are the accounts people forget. If the answer is the builder's name alone, you do not control your own site.

A good reply is short. It names the platform, lists what needs updating and says who does it. A long, vague reply is an answer too, and it goes on your note. When a reply comes, set it beside your note. Where the two agree, you have a confirmed answer. Where they differ, send one short message asking which is right.

  1. Today

    Send the questions

    Ask what the site is built on, what must be updated and by whom, and who holds the logins.

  2. This week

    Read the replies

    Set each one beside your note and write down any name you do not recognize.

  3. Each month

    Check the update list

    Ask whether the monthly updates were done and by whom.

  4. Each quarter

    Run the check again

    Compare the new answers with your note.

Two more questions belong on that list. First, where the tracking tags live, since a tag is a small snippet of code and each one is another moving part. We keep permanent tracking in the site code where builds can check it, as we explained in permanent analytics belongs in the code. Second, how the site was proven before launch. We hold that a pre-launch audit is a gate the builder must pass and show you, and proving a site before launch lays out why. Lighthouse is a tool you can point at your own page to get an audit, so you can run one yourself. Both questions come back to proof. A builder who works well can show you in a sentence what was checked and when.

The check, as a routine

  1. Login page found
  2. Page source read
  3. Parts counted
  4. Questions sent New
  5. Note in hand

What good looks like after the check

After the check you hold a note with four lines: what your site seems to run on, the names from the source, a count of the moving parts, and the questions still open for the builder. With that note, a headline about a flaw becomes a quick question instead of a worry.

Keep that note. When something goes wrong, the first question a helper will ask is what the site runs on, and you will already have the answer.

Run the check again each quarter, and again whenever the site changes hands. A new builder, a redesign or a move to a new host can change a line on your note.

If the answers turn up more moving parts than you want to keep current, that is a fair thing to raise with a web designer, and our web design service is one place to ask.

Do this today

Ready to ship

Talk to Offer before you decide anything.

You'll talk with Offer, not a sales rep. A short call, no pitch deck.

Talk to Offer

This post was drafted with AI tools from our own project records, anonymized, and checked by us before it published. Read our editorial standards.

Related Articles

Want to talk through your marketing?

Tell us where things stand and we'll tell you plainly what we'd do next.