Hosting provider PHP warning

Had an email from your hosting provider saying your website uses an old or unsupported PHP version? You have not done anything wrong. PHP is the language your website’s code runs on, and every version eventually stops getting security fixes.

Start a rescue request → A person reviews every request. No obligation.

What the email means

Hosts keep the software on their servers up to date. When a PHP version stops getting security fixes, they plan to remove it. The email is telling you that your site still uses that version, and that either the host will move it to a newer one or you need to.

The site itself is usually fine today. The risk is that when the host makes the change, older code may not work on the newer version.

Deadlines and what happens on the day

Most warnings include a date. On or after that date the host may switch your site to a newer PHP version automatically, start charging to keep the old one, or both. Look in the email for:

  • The date the change happens
  • The version you are on now and the one the host is moving you to
  • Whether there is a fee to stay on the old version

Make sure the new version is supported

Hosts sometimes move sites to a version that is newer but has already lost its own security support. The version you end up on should be a currently supported one. The table on this page shows which versions get security fixes today and until when.

Also worth knowing: when a host switches PHP version, settings such as the memory limit, upload size and timezone don’t always carry over, and scheduled tasks (cron jobs) may keep running on the old version. We check those as part of the move.

What to send us

You don’t need any technical knowledge to get started. Paste the host’s email into our form along with your website address. If you know them, these help too:

  • Who your host is, if the email doesn’t say
  • What the site is built with, such as WordPress or a custom system
  • Who looks after the hosting: you, someone in your business, an IT provider or an old developer

Please remove passwords and account numbers before you paste the email. If we need access later, we arrange it securely once you agree to go ahead.

What happens next

A person reads your request, checks the site and replies with what needs doing, a quote, and how the timing fits your host’s date. The work is done on a private staging copy after a full backup, so your live site keeps running until the tested version is ready.

PHP versions and their support dates

Bug fixes come first; after that a version gets security fixes only, then nothing at all.

VersionReleasedBug fixes untilSecurity fixes untilStatus
PHP 5.6 28 Aug 2014 19 Jan 2017 31 Dec 2018 No longer supported
PHP 7.0 3 Dec 2015 4 Jan 2018 10 Jan 2019 No longer supported
PHP 7.1 1 Dec 2016 1 Dec 2018 1 Dec 2019 No longer supported
PHP 7.2 30 Nov 2017 30 Nov 2019 30 Nov 2020 No longer supported
PHP 7.3 6 Dec 2018 6 Dec 2020 6 Dec 2021 No longer supported
PHP 7.4 28 Nov 2019 28 Nov 2021 28 Nov 2022 No longer supported
PHP 8.0 26 Nov 2020 26 Nov 2022 26 Nov 2023 No longer supported
PHP 8.1 25 Nov 2021 25 Nov 2023 31 Dec 2025 No longer supported
PHP 8.2 8 Dec 2022 31 Dec 2024 31 Dec 2026 Supported
PHP 8.3 23 Nov 2023 31 Dec 2025 31 Dec 2027 Supported
PHP 8.4 21 Nov 2024 31 Dec 2026 31 Dec 2028 Supported
PHP 8.5 20 Nov 2025 31 Dec 2027 31 Dec 2029 Supported

Dates from php.net. Your host may offer only some of these versions.

Questions

Is the email from my host genuine?

Hosting providers do send these, but scam emails sometimes copy them. Don’t click links asking for passwords or payment. Log in to your hosting account the usual way and look for the notice there, or call your host.

What if I ignore it?

The host will usually make the change anyway on the date given. If the site’s code is not ready, it may show errors or a blank page, often at an inconvenient time.

Do I have to change hosts?

Usually not. Most sites can stay where they are. If your host cannot offer a currently supported PHP version, we will explain your options.

How it works

  1. 01

    Tell us what’s happening

    Share your web address, paste the warning from your host, or describe the problem. No PHP knowledge needed.

  2. 02

    We review

    A person looks at what you sent and works out what needs checking.

  3. 03

    We recommend a plan and quote

    You get the recommended approach, a clear scope and a price, including anything that needs further investigation.

  4. 04

    We test and upgrade once agreed

    Where feasible, changes are tested on a separate copy before going live. Nothing starts until you approve.

Let’s get your site on supported PHP.

Tell us what’s happening. A person replies.

I received a warning →