certscore.org · 7 checks shown of 7 watched · last read 31 seconds ago · page generated 19 Oct 2026, 16:25 UTC
all 4answering on the latest pass
This page renders straight from the runner's readings; each row says how often it is read. Latest reading 19 Oct 2026, 16:25 UTC. Percentages below count the last 30 days. Speed, email records and browser protections are shown for information and advice; they never raise an alert.
October 2026 so far: home page up 100% of the time, no interruptions.
Everything watched
Each row says how often it is read. The count beside every percentage is the number of
readings behind it; a percentage without its denominator is not a fact.
Browser protectionschecked daily80msall goodchecked daily, last read 19 Oct 2026, 03:05 UTC
Can people find you132msall good7929 of 7929 readings clean since 22 Sep 2026, 02:59 UTC (100%), counting the last 30 days, checked every 5 minutes
Certificatechecked daily116mscould not readno readings yetThe certificate for certscore.org is issued and renewed automatically by the service that sits in front of your site, so it does not expire the way a hand-managed one can. We cannot read its date from where we stand, and there is nothing for you to do.
Email recordschecked daily109msadvicechecked daily, last read 19 Oct 2026, 03:05 UTCcertscore.org has both records, but its DMARC policy is set to "none", which asks other mail services to do nothing about a forgery. It reports, it does not protect.
Home page256msall good36494 of 36494 readings clean since 22 Sep 2026, 02:59 UTC (100%), counting the last 30 days, checked every minute
Speed around the worldchecked hourly586msfor informationchecked hourly, last read 19 Oct 2026, 15:34 UTCMeasured from 8 places. Fastest from Sydney at 162 ms, slowest from London at 586 ms. Normal for both, judged against each place's own last week.
Web address renewalchecked daily488msall good27 of 27 readings clean since 22 Sep 2026, 02:59 UTC (100%), counting the last 30 days
What has happened
The most recent interruptions, newest first, up to twenty-five. Written by the runner as each happened, not afterwards. Only a page or form not loading, the address not being found, the certificate and the renewal are interruptions; speed, email records and browser protections never are.
Nothing yetNo interruption has been recorded since watching began. When one happens it is written here, with the time it started, the time it ended, and what we actually saw. Nothing is edited out afterwards.
Follow these updates:RSS feedadd it to Slack:/feed subscribe https://status.certscore.org/feed.xml
This page is public: anyone with the address can read it. What it shows is decided by CertScore, who can hide any row from it while we keep watching that row.