Red Center Studio
Back to Free tools Free tool / Business continuity

Single point of failure check for your business.

On 12 and 13 November 2026 a Microsoft 365 outage cut businesses around the world off from Outlook and other Microsoft services. Enter your domain to see what else one outage could take down.

Takes about 5 seconds. Reads public DNS records only. Scanned domains are not stored; results are cached for one hour, then discarded. See the Privacy Policy.

TL;DR

Most small businesses rent their email, staff sign-in, DNS and website from a handful of companies. When one company runs two or more of those layers, a single outage at that company stops all of them at once. This free check reads your public DNS records, names the company behind each layer, flags any concentration, and gives you a risk score out of 100 with the fixes to make first. No sign-up, nothing installed, and scans are not stored.

Want a person to check what a scan from outside cannot see, such as who holds each login, renewals and backups? The Resilience Check is $299 USD, once.

On Microsoft 365 or Google Workspace? See what stops in an outage and what to set up: Microsoft 365 dependency check / Google Workspace dependency check.

How it works

Public DNS in, plain English out.

  1. Email. MX records show who receives your mail. SPF, DKIM and autodiscover records confirm the mailbox provider and list the services that send email as you.
  2. Staff sign-in. Microsoft and Google mailboxes come with their sign-in systems. Device registration and verification records add more signals.
  3. DNS. Name server records show which company answers for your domain. If DNS fails, your website and email fail with it.
  4. Website. The www record and the network that owns your website's IP address (looked up through Team Cymru's public service) show where the site is served from.
  5. SaaS footprint. Verification records left by tools such as Atlassian, DocuSign or Zoom show other services your team relies on.

Then it checks whether any one company runs two or more of the critical layers (email, staff sign-in, DNS and website). That is the headline finding, because it is how one outage becomes a full stop.

The risk score, in full

Higher means more risk. Every point added or removed is listed with your results.

  • +10 Starting point: every business depends on outside providers
  • +40 One vendor controls 3 or more critical layers
  • +25 One vendor controls 2 critical layers
  • +10 A second vendor also controls 2 or more critical layers
  • +20 No DMARC record
  • +10 DMARC policy is p=none (monitoring only)
  • +10 No SPF record
  • +10 All name servers are with one DNS provider
  • -10 Email, DNS and website each use a different vendor

The score is capped between 0 and 100. 0 to 29 is low, 30 to 59 is moderate and 60 or more is high.

This is an indicator, not an audit. It reads public DNS only, so it cannot see contracts, backups, private networks, or single sign-on setups that leave no DNS trace. A proxy such as Cloudflare can also hide the server behind a website.

Frequently asked questions

What is a single point of failure for a business?

It is one supplier or system that, if it stops working, takes several parts of your business down with it. A common example is one company running your email, staff sign-in and DNS, so a single outage stops email, logins and your website at once.

Would the November 2026 Microsoft 365 outage have affected my business?

If the scan shows Microsoft for your email or staff sign-in, then yes: on 12 and 13 November 2026 many businesses on Microsoft 365 could not reach Outlook and other Microsoft 365 services. If Microsoft also runs your DNS or website, those layers depend on the same company too.

How is the risk score calculated?

It starts at 10. It adds 25 points when one vendor runs two critical layers (40 for three or more), 10 if a second vendor also does, 20 for no DMARC record (10 if DMARC only monitors), 10 for no SPF record and 10 when all name servers are with one DNS provider. It takes off 10 when email, DNS and website each use a different vendor. The result is capped between 0 and 100.

Does the scanner access my systems or store my domain?

No. It only reads public DNS records, the same ones any email server or browser reads, through Cloudflare's public DNS over HTTPS service. It never logs in anywhere or visits your website. Results are cached for one hour so repeat scans are fast, then discarded. Domains are not stored. If you ask for an emailed copy, your email address, the domain and your score are kept so the report can be sent and followed up once.

How do I reduce single points of failure?

Keep DNS with a different company from your email and website, have a backup way to reach staff and customers, publish SPF and DMARC, keep emergency admin accounts that do not depend on single sign-on, and write a one-page plan for who does what during an outage.