Rosa's Bakery (sample)
3 important issues should be fixed soon.
Since the last check-up (16 October 2026)
- Fixed Visitors are not sent to the secure (https) version (rosas-bakery.example)
What to fix, most urgent first
Possibly outdated software with a known security problem: PHP 8.2.20
Why it matters: The server reports a version with a published security problem. Version numbers can be hidden or kept old while fixes are applied, so this needs confirming with your host.
What to do: Ask your host to confirm the version and update to a fixed release (8.2.35, 8.3.36, 8.4.27, 8.5.12).
WordPress 7.0.1 has 4 known security holes, 4 used by attackers
Why it matters: Attackers run automated tools that find sites on versions with published holes and break in, often within days of the news. Some holes let them change pages or take over the site without a password.
What to do: Update WordPress to 7.0.8 or later (Dashboard > Updates) and turn on automatic updates for WordPress itself.
The certificate expires in 9 days
Why it matters: When the certificate expires, browsers show a full-page warning and most visitors leave.
What to do: Ask your host to renew it before that date and to turn on automatic renewal.
Browsers are not told to always use the secure version (HSTS)
Why it matters: Without this setting, someone on the same network can push a visitor onto an unencrypted connection before the secure page loads.
What to do: Ask for the Strict-Transport-Security header with a max-age of at least 15552000 (180 days). Only turn it on once the whole site works over https.
Other sites can show your pages inside theirs
Why it matters: A fake site can load your page invisibly and trick visitors into clicking buttons on it, such as "buy" or "delete". This is called clickjacking.
What to do: Ask for the header X-Frame-Options: SAMEORIGIN, or frame-ancestors 'self' in the content security policy.
Some cookies are missing protection flags
Why it matters: Cookies without the Secure flag can travel over unencrypted connections, and cookies without HttpOnly can be read by scripts on the page. Login cookies need both.
What to do: Ask your developer to set the Secure and HttpOnly flags on cookies, plus SameSite=Lax.
The server runs Ubuntu 20.04, which is past its normal support
Why it matters: The server's operating system no longer gets security updates, so holes in it and in the software it runs stay open.
What to do: Ask your host whether paid extended security updates are active for this server, and plan the move to a supported release.
The server reveals its software version
Why it matters: Showing the exact version tells attackers which known weaknesses to try first.
What to do: Ask your host to hide the version number (for example server_tokens off in nginx, or ServerTokens Prod in Apache).
The site announces the technology behind it (X-Powered-By)
Why it matters: Announcing the technology and its version helps attackers pick what to try.
What to do: Ask your developer to remove the X-Powered-By header (for PHP: expose_php = Off).
No content security policy
Why it matters: This setting limits which scripts may run on your pages. It is the main defense if harmful code gets in, for example through a hacked plugin or a comment form.
What to do: Ask your developer to add a Content-Security-Policy header. It needs care so the site keeps working, so start with the report-only version.
No referrer policy is set
Why it matters: When visitors click a link to another site, the full address of your page can be passed along, sometimes with private details in it.
What to do: Ask for the header Referrer-Policy: strict-origin-when-cross-origin. Modern browsers already behave this way by default, so this is low priority.
Results by website
rosas-bakery.example
| Important | Possibly outdated software with a known security problem: PHP 8.2.20 Reported in the X-Powered-By header. Advisory: https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w |
| Important | WordPress 7.0.1 has 4 known security holes, 4 used by attackers CVE-2026-63030 (critical, used by attackers); CVE-2026-119977 (high, used by attackers); CVE-2026-87902 (high, used by attackers); CVE-2026-60137 (medium, used by attackers). Seen in: the site's RSS feed |
| Important | The certificate expires in 9 days Valid until Nov 1 08:00:00 2026 GMT |
| Recommended | Browsers are not told to always use the secure version (HSTS) header missing |
| Recommended | Other sites can show your pages inside theirs no X-Frame-Options or frame-ancestors |
| Recommended | Some cookies are missing protection flags without Secure: PHPSESSID |
| Recommended | The server runs Ubuntu 20.04, which is past its normal support worked out from Apache 2.4.41 in the Server header; support ended on 31 May 2025; paid extended support runs until 23 Apr 2030 |
| Tip | The server reveals its software version Apache/2.4.41 (Ubuntu) |
| Tip | The site announces the technology behind it (X-Powered-By) PHP/8.2.20 |
| Tip | No content security policy header missing |
| Tip | No referrer policy is set header missing |
| Passed | Visitors are sent to the secure (https) version HTTP 301 to https://rosas-bakery.example/ |
| Passed | Browsers are told not to guess file types nosniff |
| Passed | The certificate is trusted Issued by C=US, O=Let's Encrypt, CN=R11 |
| Passed | The connection uses modern encryption TLSv1.3, TLS_AES_256_GCM_SHA384 |
| Note | This address forwards visitors to another address HTTP 301 to https://www.rosas-bakery.example/ |
| Note | Software found: WordPress 7.0.1, Apache 2.4.41 read from the home page, its headers and 1 more public file |
What this check-up covered
- Whether visitors are sent to the secure (https) version of the site.
- The security settings the site sends with its pages: HSTS, content security policy, protection against framing, file-type guessing, referrer policy and cookie flags.
- Software versions the server reveals, compared with published security problems.
- The site's certificate: whether it is trusted, when it expires, its key strength and the encryption version.
Not covered
- Pages behind a login, and anything that needs a password.
- Attempts to break in (a penetration test).
- Plugins, themes and other software the server does not announce.
- Live certificate revocation checks.
- Anything not listed on the signed permission form.