Live proof from our own website
We look after small business websites, so here is ours, measured in public: uptime, speed, security certificate, software versions, and how fast we write up new PHP flaws. Figures fill in on their own. Anything we can't measure yet says so plainly.
How this site is running right now.
Our own website, measured in public
Figures refreshed UTC
- Uptime, last 90 days
- 100.00%Tracking since UTC16 of 90 days tracked so far1,277 checks, 0 failed, 53.40% of planned checks ranNo downtime recorded since tracking began
- Page speed, real visitors (Core Web Vitals)
- Not connected yet
- Page speed, one lab test (Core Web Vitals)
- Not connected yet
- Security certificate (SSL)
- Valid until UTC, 44 days leftIssued by Let's EncryptChecked UTC
- PHP version
- 8.5Major and minor version only
- WordPress version
- 7.1Major and minor version only
- Plugin updates waiting
- 1WordPress last looked for updates UTC
- Last backup
- Not reported yet
- Monthly restore test (files and pages only, database not yet included)
- Test restore worked on UTCSource: Scripted restore of our own page and file backup to a non-live copy; database not included
- Attacks blocked
- Not reported yet
How fast we respond to PHP flaws.
Each row is a public PHP security flaw, with the hours from it being made public to our own page about it.
Patch clock: how fast we write up new PHP flaws
Last updated
| Flaw | Made public (UTC) | Our page published (UTC) | Hours to our page | Hosting provider's statement | How sure we are | Sources |
|---|---|---|---|---|---|---|
| CVE-2026-109618Remote code execution via out-of-memory corruptionPHP release that includes the change 8.5.12, 8.4.27, 8.3.36, 8.2.35 | 69 | PHP upgrades are now complete across all managed hosting servers.Hostinger status page, 22 Oct 2026, 06:44 UTCThis is the provider's statement for all its servers, not a check of this website |
| |||
| CVE-2026-109619Remote code execution via stale global statePHP release that includes the change 8.5.12, 8.4.27, 8.3.36, 8.2.35 | 69 | PHP upgrades are now complete across all managed hosting servers.Hostinger status page, 22 Oct 2026, 06:44 UTCThis is the provider's statement for all its servers, not a check of this website |
| |||
| CVE-2026-115560Remote code execution via session upload progress (unusual configuration needed)No PHP release covers this yet | 11.4 | Websites on our Web Hosting, Agency Hosting, and cPanel Hosting plans are already protected by the mitigation applied on October 21.Hostinger status page, 23 Oct 2026, 12:53 UTCThis is the provider's statement for all its servers, not a check of this website |
|
Hours are counted from the moment the flaw was made public to the moment our page about it went live.
| PHP | 8.5 |
|---|---|
| WordPress | 7.1 |
How these figures are made.
Uptime comes from the site checking its own home page every 10 minutes, so it is an estimate, not an outside monitor.
Speed has two separate parts: real Chrome visitors over 28 days, and one lab test run by a machine on a simulated phone. We never mix the two.
Backup and firewall figures are copied from our hosting provider's dashboard. The restore test is run by our team.
"Not reported yet" means we have no figure. A 0 is a real zero.
This page covers penguina.website only, not the websites we look after for clients.
Want to see the same public security settings for your own website? Run our free site check. It works on any platform and only needs your address.
Why do some figures say Not reported yet?
Because we don't have a figure for them yet. We show that plainly instead of guessing or leaving the space out. A real zero shows as 0.
Is this data from your clients' websites?
No. Every figure on this page is about penguina.website only. Our clients' websites belong to them, and their figures stay private.
Can you change these numbers?
The live figures are filled in by the website itself on a schedule. Backup and firewall facts are copied from our hosting provider's dashboard, and the restore test is run by our team.