Status pages

When a site goes down, the questions start: is it just me, is it being worked on, when will it be back? A TLDTrack status page answers them for you. It is a web page showing whether a site is healthy, built from the monitoring you already run, and visitors can subscribe to be emailed when something changes. You spend an incident fixing the problem instead of fielding "is it down?" messages.

What a status page can show

A status page is built for one of your sites. Eleven checks can appear on it, and each one is a separate toggle:

• Availability. The 90-day uptime strip and the uptime percentage.
• SSL certificate. How long the certificate has left, and who issued it.
• Domain registration. When the domain registration expires.
• Malware. The clean or infected result from the malware check.
• Blacklists. Whether the site appears on any spam or threat list.
• Content. Whether monitored page content is stable or has changed.
• Compliance. The latest compliance check result.
• SEO health. The latest SEO audit result.
• Accessibility. The latest accessibility audit result.
• PageSpeed. The Google PageSpeed mobile performance score.
• User journeys. How many journey tests are passing, and when they last ran.

On top of the checks, each page carries a title and an optional custom message (useful for a standing note or a maintenance heads-up), and it can show your company details, name, phone, email and website, plus an account manager's name, email and phone, so a worried visitor knows exactly who to contact.

Choosing which checks appear, page by page

Visibility works at two levels, and both have to allow a check before it appears.

1. Your organisation settings. Under Status Pages the display settings screen decides which checks are available to publish at all, across every page you own. Availability, SSL, domain expiry, malware and blacklists are on by default; the rest are off until you choose to publish them. Modules you have switched off in Settings also stay hidden here.
2. The individual page. Each status page then has its own Checks shown on this page list on its Manage screen, so you can publish PageSpeed for one client and not another, or hide accessibility on a single site while a rebuild is underway.

The page-level list only ever narrows what your organisation settings already allow. Turning a check on for one page cannot override a check you have switched off across the account, which means the account-wide setting is always a safe backstop.

Showing user journeys

If you run journey tests on a site, the page can report on them. The card counts how many journeys are passing out of the total and shows when they last ran, for example "4 of 5 journeys passing, last run 3 August 2026". Where a journey is failing, the page names that journey and nothing else. The steps, the URLs, the selectors and the failure details all stay inside your dashboard.

Journeys are off by default in your display settings, so nothing appears publicly until you decide it should. A journey that has never produced a pass or a fail is ignored, so a test you have only just written does not show up as a problem.

Showing what the issues actually are

By default a check on a status page says only that it found something: a state, and a count. That is deliberate, because anyone with the link can read the page.

The Manage screen has an opt-in setting, Show what the issues are. Turn it on and the page also prints up to three short finding titles under a check, plus a count of anything beyond that. It applies to seven checks:

• Availability. The dates in the 90-day window that recorded a failure.
• Blacklists. The names of the lists the domain appears on.
• Content. Your own label for a watched item, and whether it changed or failed. Never the watched value, the selector or the page.
• Compliance. The rule that failed. Never the quoted page copy or the suggested fix.
• SEO health. The finding title, and the path of a broken or redirecting link. Never the full URL or the evidence.
• Accessibility. The human-readable message. Never the selector, the HTML snippet or the remediation.
• PageSpeed. The field metrics already summarised on the score row.

Treat everything this setting reveals as public. If you want the extra detail for a client but not for the world, set a password on the page first.

Passwords and the page link

Every page has an unguessable link, which is enough for most sites. Two further controls exist when it is not:

• Access password. Set one password on the page and visitors have to enter it before they see anything. Leave it blank for a public page, or remove it later to make the page public again.
• Regenerate the link. If the link has been shared too widely, or a client relationship ends, regenerate it. The old URL stops working at once and a new one takes its place.

Email subscribers

A status page can invite visitors to subscribe for updates. When subscriptions are enabled on a page, a visitor enters their email, confirms it (a double opt-in, so nobody is signed up without agreeing), and is then on the list. Every subscriber email carries a one-click unsubscribe link, so leaving is as easy as joining.

Behind the scenes, a scheduled job emails confirmed subscribers when a relevant alert is recorded for the site, specifically:

• The site going down, and then recovering.
• An SSL certificate expiring soon.
• The domain being blacklisted.

Each notice is a clean, branded email with a link back to the status page. You can also see and remove subscribers from the page's settings, and turn subscriptions off entirely for a page while keeping the page itself public.

Creating a status page

1. 1
   Open Status Pages from your dashboard and choose to create one.
2. 2
   Pick the site it is for. Only monitored sites without a page already appear in the list.
3. 3
   Give it a title and, if you want, a custom message. Fill in the company and account-manager contact details you would like shown.
4. 4
   Under Checks shown on this page, turn on the checks this page should publish. Anything switched off in your display settings stays hidden whatever you pick here.
5. 5
   Decide whether to turn on Show what the issues are. Leave it off unless you want finding titles readable by anyone with the link.
6. 6
   Set an access password if the page should not be open to everyone, and decide whether to enable email subscriptions.
7. 7
   Save, then share the page's link. The page is live immediately and updates itself from your monitoring data.

Editing a page from the site itself

You do not have to go to the Status Pages screen to change a page. Open the site, go to its Status Page & Reports tab, and press Edit status page. The same settings open in a modal: the title, the message, the contact details, which checks appear, the issue-detail setting, subscriptions and the password. Saving brings you back to the tab you started on.

The tab also shows whether the page is active or paused, whether it is password protected, and the public link with a copy button. Subscribers and the link itself are managed on the full status page screen, which the tab links to. If the site has no page yet, the tab offers to create one.

Managing pages over time

You can disable a page temporarily (it goes offline but keeps its settings and subscribers) and re-enable it later, edit its details and checks at any time, or delete it entirely. Because everything is driven from live monitoring data, an enabled page always reflects the current state without any manual updating on your part.

Where to set this up

Good to know

• A page shows only the checks you enable, and your account-wide display settings always win, so you never expose more than you intend.
• Checks with no results yet never appear, whatever is switched on.
• Security and malware findings are never detailed on a status page. Journey tests name a failing journey and nothing else.
• "Show what the issues are" is off by default and prints at most three finding titles per check, plus a count of the rest.
• Set an access password on a page if the detail is for a client rather than the public.
• Subscriptions use double opt-in and one-click unsubscribe; you can also remove a subscriber yourself.
• Subscriber emails fire on downtime, recovery, SSL expiry and blacklisting.
• Regenerating the link instantly invalidates the old one.
• Only sites you monitor for uptime can back a status page.