← All articles

A connected reading series

Digital Trust for Businesses

A practical 48-part guide to websites, email, security reports and invoice services. Understand how the mechanisms work, what evidence means and where protection ends.

48 of 48 parts published8 thematic sectionsStart reading · Part 1 →

Parts 1–6

Trust and security evidence

  1. Who are you trusting with your invoices?

    Understand the separate jobs behind sending an invoice: delivery, storage, access and support.

  2. Your website is a shop window — not the whole business

    What a provider's public website can tell you about security, and what it cannot reveal about invoice handling.

  3. One company, different systems: website, portal, API and Peppol

    Follow the different systems involved in a digital service, from its public website to invoice exchange.

  4. Passive observation, active checks and penetration tests

    Understand what different security checks actually do before interpreting their results.

  5. A finding is not always a vulnerability

    Learn why a scanner finding needs context before it can be called an exploitable weakness.

  6. What a green security score cannot tell you

    Read a security score without mistaking a summary of selected checks for a guarantee.

Parts 7–12

Domains and DNS

  1. Your domain name is more than your website

    Understand how a business domain connects its website, email and other services.

  2. DNS and name servers: how your browser finds a website

    Follow how a browser finds a website, and learn the separate roles of DNS and name servers.

  3. A, AAAA and CNAME: three ways to find a destination

    Understand how three common DNS records direct computers to the services behind a name.

  4. MX and TXT: where email goes and what a sender can prove

    Learn how DNS helps deliver email and publish information used to check its sender.

  5. DNSSEC and CAA protect two different steps

    Understand why DNSSEC and CAA protect different steps and cannot replace one another.

  6. When a service closes but its web name stays behind

    See how a web name left behind after a service closes can create a security problem.

Parts 13–18

HTTPS, certificates and discovery

  1. What HTTPS protects when you open a website

    Follow what HTTPS protects between your browser and a website, and where that protection ends.

  2. A website certificate is not a recommendation

    Understand what a website certificate verifies without mistaking it for an endorsement of the business.

  3. Why a certificate needs care after installation

    Learn why certificates need renewal and monitoring after the initial website setup.

  4. How a website name can become public before launch

    Understand how certificate records can reveal a website name before its public launch.

  5. A scanner found your website. Was it hacked?

    Distinguish automated visits to a website from evidence that someone has broken into it.

  6. The page opens with HTTPS. What could still be wrong?

    Understand why an encrypted connection does not settle every question about website security.

Parts 19–24

Email and invoice fraud

  1. What happens after you press Send?

    Follow an email from the Send button through the systems responsible for delivering it.

  2. SPF: who is allowed to send this email?

    Understand how SPF checks whether a server may send mail for a particular domain.

  3. DKIM: what an email signature actually tells you

    Learn what a DKIM signature can tell you about an email, and what it does not verify.

  4. DMARC: does the checked domain match the name on the email?

    Understand how DMARC connects email authentication to the domain visible in the sender address.

  5. Who protects an email while it travels?

    Follow the protection of an email during transport and distinguish it from end-to-end confidentiality.

  6. The invoice is familiar. Is the new bank account genuine?

    Understand why a familiar invoice does not authenticate a new bank account, and how to check a change.

Parts 25–28

Browser protections

  1. The invisible instructions that arrive with a web page

    Meet the invisible instructions a website sends to the browser alongside its visible content.

  2. CSP: how a page tells the browser which code may run

    Follow how CSP tells a browser which code it may run, with advanced details kept separate.

  3. Three browser protections that do three different jobs

    Understand three browser protections by following the different problems they address.

  4. How a website remembers you — and what CORS has to do with it

    Learn how a website remembers a visit and why browser cross-origin rules are a separate control.

Parts 29–36

Website operations and protection

  1. A WordPress website still needs looking after

    Understand why a delivered WordPress website still needs updates, ownership and recovery arrangements.

  2. An old version number does not tell you whether the software is fixed

    Learn why a visible software version is a starting point for investigation, not proof of its patch status.

  3. When a backup becomes a public download

    See how a backup can become a public download and why recovery copies need their own protection.

  4. Why some website code is public—and some keys must not be

    Understand why browsers receive some website code while private credentials must remain protected.

  5. What a chat button brings onto your website

    Follow what happens when a website adds chat or another outside script, and what trust it introduces.

  6. A browser warning is a reason to stop, not a complete diagnosis

    Treat browser warnings as a reason to stop and investigate without jumping to an unsupported diagnosis.

  7. What “we use Cloudflare” tells you about a website

    Understand what using Cloudflare can mean for a website and why configuration and scope matter.

  8. Protecting the original server without stopping legitimate work

    Learn why protecting a website's front door also requires attention to its underlying server.

Parts 37–42

APIs, access and invoice delivery

  1. What your accounting program does through an API

    Follow how an accounting program exchanges information through an API without requiring a programming background.

  2. A public API address is not an open invoice cabinet

    Understand the difference between knowing an API address and being allowed to retrieve invoice data.

  3. Knowing who you are does not decide what you may do

    Separate identifying a user from deciding which information and actions that user may access.

  4. Why your login must not open another company’s invoices

    Follow why a service must check access to each invoice and keep different businesses' records apart.

  5. You sent the invoice. Did it go through?

    Understand what invoice delivery messages do and do not establish at each step of the journey.

  6. What Peppol protects on an invoice’s journey

    Understand the protection of an invoice during Peppol exchange and the separate responsibilities at its endpoints.

Parts 43–48

Reports, recovery and provider choice

  1. How to read a website scan report without getting lost

    Read a website scan by checking what was examined, what was observed and what the findings mean.

  2. The website report changed. Did the website change?

    Distinguish a changed website from changed tests, coverage or reporting when comparing scan results.

  3. Your email address appeared in a breach. What does that mean?

    Understand what an exposed email address establishes, what remains unknown and which actions can help.

  4. Ask your supplier to show what happens when an invoice goes wrong

    Ask a supplier to demonstrate what happens when an invoice fails, rather than showing only successful delivery.

  5. The service is back. Can we safely send invoices again?

    Distinguish a service returning online from evidence that invoice processing can safely resume.

  6. Choosing an invoicing provider you can actually work with

    Bring delivery, usable copies, support, access and exit arrangements together when choosing an invoice service.

Return to the full article archive