
How to Check PHP Version on Windows 11 and in XAMPP
Step lists to check your PHP version on Windows 11 and XAMPP, fix the not recognized error, and see how it relates to the PHP on your live host.
Web Design
Most guides to an expired certificate are written by certificate sellers for server teams, and they walk you through a manual renewal. Most small business sites never renew by hand: the platform does it, and an "expired" warning means that automatic renewal broke. This guide starts there. Platform rules and dates were read on their makers' pages on 14 November 2026.
When your site shows "Your connection is not private" because the certificate expired, do this in order. Check the warning from a second device on a different network, so you know it is your site. Click the padlock or warning icon and read the expiry date and issuer. If the issuer is your website platform's provider, fix the domain connection (DNS records, forwarding, CAA records) and let the platform reissue the certificate, which can take up to 48 hours. If you bought the certificate or run your own server, renew it with your certificate authority or host and install it. Then set up an outside check so you hear about the next problem before your visitors do.
About us: Amariq builds and looks after websites on Webflow, Framer, WordPress, Shopify, Squarespace, Wix and plain static hosting, and connects domains and DNS as part of every launch. The platform rules below come from each maker's help pages, read on 14 November 2026.
We searched Google (US, English) on 14 November 2026. The first page was an SSL checker tool, then certificate sellers and security firms: Sectigo (24 July 2025), Keyfactor (20 June 2024), Sematext, CrowdStrike (1 August 2022) and SSL Trust, plus Tenable's scanner plugin, a Microsoft Q&A thread, Reddit and Quora. Google's AI summary gave three steps: renew, install, verify.
The pages share one picture: a person with a paid certificate who creates a certificate signing request, sends it to the authority, validates the domain and installs the files. That is right for a server team. It does not fit most small business sites, which run on a platform that issues free certificates automatically and never asks for a signing request. Webflow's help says this outright: "You don't need to generate a CSR." None of the ranking pages explains why a platform's automatic renewal fails or how to fix it.
One claim on Sectigo's page also needs care. It says that once a certificate expires, communication is shown in plaintext. An expired certificate does not switch off encryption by itself. What fails is the browser's check of the certificate, so the browser stops the visit with a full-page warning. For your business the result is the same, because most visitors leave, but the fix is a trust problem, not a broken lock.
echo | openssl s_client -connect www.example.com:443 -servername www.example.com 2>/dev/null | openssl x509 -noout -issuer -dates
As an example, we ran it on our own site on 14 November 2026. It showed an issuer of Google Trust Services, valid from 24 September 2026 to 23 December 2026: a 90-day certificate issued on the day the site moved to its current host, which renews it automatically.
| Your setup | Who issues and renews it | What you do |
|---|---|---|
| Webflow, standard hosting | Webflow, automatically, while DNS points to Webflow | Fix the DNS; Webflow renews |
| Webflow Enterprise with an uploaded certificate | You | Webflow does not renew custom certificates; upload a new one before expiry |
| Squarespace | Squarespace, free, for domains pointing to a Squarespace site | Fix the domain connection; wait up to 48 hours |
| Shopify | Shopify, free, for every domain added to Shopify | Fix the A and CNAME records; third-party certificates are not allowed |
| Own server with Let's Encrypt | Your server's renewal tool | Find out why the scheduled renewal stopped |
| Paid certificate from an authority or host | You, through the seller | Renew, validate and install the new certificate |
If your domain points somewhere else, the platform cannot help. Squarespace states that its SSL covers only domains pointing to Squarespace websites, and that a Squarespace domain pointing elsewhere needs a certificate from that other host.
| Cause | What happens | Source |
|---|---|---|
| DNS no longer points to the platform | The platform cannot prove it controls the domain, so it cannot renew | Webflow: renews "as long as the DNS records are continuously pointed to Webflow" |
| A CAA record leaves out the platform's authority | The authority is not allowed to issue | Webflow, Squarespace and Shopify help pages |
| Domain forwarding with SSL switched off | The forwarded address shows a warning | Squarespace troubleshooting page |
| Third-party DNSSEC setup | Squarespace cannot guarantee it works with its SSL | Squarespace troubleshooting page |
| Custom certificate on Webflow | Not renewed by Webflow | Webflow SSL hosting page |
| Own server, renewal job stopped | Nothing renews and, since June 2025, Let's Encrypt sends no warning | Let's Encrypt, 22 January 2025 |
DNS changes are the usual trigger. A new email provider, a domain transfer or a tidy-up of old records can quietly remove the record that points the site to the platform. Our guide to DNS records shows what each record does, and our domain transfer guide lists the records to copy before a move.
Webflow. In the site settings, check the domain status. Compare the A and CNAME records at your domain registrar with the values Webflow shows, and correct any that were changed. If you use CAA records, add Webflow's certificate providers as its help page describes. Webflow notes that it does not renew certificates in advance, so a monitoring tool may warn you before anything is actually wrong.
Squarespace. Its troubleshooting page lists the order: if the domain is new, wait 48 hours; then make sure the site is set to Secure in the SSL panel; check for mixed content; confirm the domain is connected; for Squarespace domains, check the default records are intact; for third-party domains, check the records at your provider. After any change, wait 48 hours and test in a private window. If the domain uses forwarding, open the forward and turn its SSL toggle back on if it is off.
Shopify. Shopify issues a free certificate when your A record and CNAME point to Shopify, which can take up to 48 hours. "SSL pending" during that time is normal; "SSL unavailable" after it means something is blocking. If you must keep CAA records, Shopify asks for letsencrypt.org, pki.goog (with cansignhttpexchanges=yes) and ssl.com on each one. Shopify does not accept certificates from elsewhere.
Your own server with Let's Encrypt. Let's Encrypt's certificates last 90 days by default, and its FAQ recommends renewing every 60 days. Check that the scheduled renewal job still runs, run it by hand, read the error, and reload the web server after it succeeds. The most common errors trace back to the same causes as above: DNS, a CAA record, or a firewall blocking the validation request.
A paid certificate. Log in to the seller or your host, renew, complete the domain validation (email, a file on the site or a DNS record), then install the new certificate where the old one was. Sectigo suggests starting 30 days before expiry.
example.com and www.example.com should land on the secure address.Our guide to SSL certificate cost shows which platforms include a certificate and what paid ones cost. If you would rather not watch any of this yourself, our monthly maintenance plan guide lists what a care plan should cover, certificate and domain checks included.
If your site is showing a certificate warning right now, send us the address and tell us where it is hosted. We will find whether the cause is DNS, a CAA record, forwarding or the certificate itself, and tell you what to change, or change it for you if you give us access. For sites we build, we connect the domain, check the certificate and redirects at launch, and keep the domain, hosting and analytics accounts in your name. Work is priced from the scope rather than by the hour, paid 40% to start, 30% at design approval and 30% before launch, and the finished site belongs to you once the last payment is made. See our Webflow maintenance service or our website optimization service.
Browsers stop visitors with a full-page warning such as "Your connection is not private". Most people leave at that point, so forms, sales and bookings stop until the certificate is replaced.
It depends on who issued it. On Webflow, Squarespace and Shopify, fix the domain connection and the platform reissues the certificate for free. On your own server, run your renewal tool. For a paid certificate, renew with the seller, validate the domain and install the new files.
Usually because the platform could no longer prove it controls the domain. A DNS record was changed or removed, a CAA record blocks the platform's certificate authority, or forwarding was set up with SSL switched off.
Both say up to 48 hours for a newly connected domain. Squarespace asks you to wait 48 hours after any change before testing again.
Some browsers let a visitor click through the warning, but few do, and they should not enter personal or payment details. Treat an expired certificate as the site being down.
Click the icon to the left of the address bar and open the certificate details, or run the openssl command shown above. Your platform or certificate seller's dashboard also shows the date.
No. Let's Encrypt ended its expiration emails on 4 June 2025, citing reliable automation, privacy and cost. Use your own monitor instead.
The CA/Browser Forum, where certificate authorities and browser makers set the rules, approved a phased cut. Sectigo's summary gives 200 days from 15 March 2026, 100 days from 15 March 2027 and 47 days from 15 March 2029.

Step lists to check your PHP version on Windows 11 and XAMPP, fix the not recognized error, and see how it relates to the PHP on your live host.

What a website backup must include, how often to take one, and what Webflow, Wix, Squarespace, Shopify and WordPress keep for you. Checked 14 Nov 2026.

Website security checklist for small business: 20 checks split by who does them, you, your platform or your developer. From CISA and Google. Checked 16 Nov 2026