Are the websites of French town halls up to date?

On 15 and 16 November 2026, I read the home page of every website of their own that town halls in France declare in the official government directory, once each, like any visitor. 19,854 websites answered. Here is what they show of their software, with the base of every figure. Two things before you read: the PHP version can only be read on one website in four, and no town is named.

Read the PHP version of a website
  • 19,854 town hall websites read
  • 48.3% run WordPress
  • 35.6% without PHP fixes, of 4,887 sites
  • Aggregated figures, no town named
  • Survey of 15 and 16 November 2026
  • Data by department (CSV, CC BY)

Key figures

What French town hall websites let you see

Each figure comes with its base, that is the number of websites it is calculated on. A website, here, is a distinct address: a merged commune or a group of communes can carry the website of several town halls.

  • Town halls in the official directory35,733

    Every “town hall” record of the French government directory, in 101 departments, overseas included (803 of them delegated or annex town halls).

    13,363 without a declared website, 728 pointing to a Facebook page or a ready-made platform, 21,642 declaring a website of their own

  • Websites read19,854

    The 20,865 distinct websites declared by these 21,642 town halls, one read of the home page each.

    95.2% of the 20,865; 1,011 did not answer properly (error response, domain not found, invalid certificate, timeout)

  • WordPress48.3%

    The 19,854 websites read.

    9,592 websites. Far behind: Joomla 4.0% (798), Drupal 3.4% (670), TYPO3 3.3% (648), SPIP 1.0% (206); 16.6% (3,299) not identified

  • PHP version visible24.6%

    The 19,854 websites read.

    4,887 websites, one in four. The PHP figures below only apply to them

  • PHP that no longer receives security fixes35.6%

    The 4,887 websites that show their PHP version. Without fixes: PHP 8.1 and older.

    1,739 websites: PHP 5.x 361, PHP 7.0 to 7.3 384, PHP 7.4 684, PHP 8.0 140, PHP 8.1 170

  • PHP 8.29.3%

    The 4,887 websites that show their PHP version.

    454 websites, which lose their fixes on 31 December 2026. On 1 January 2027, 44.9% (2,193 of 4,887) will be without fixes if nothing changes

  • Joomla on a branch without fixes58.8%

    The 580 Joomla websites whose version can be read, out of 798 (72.7%).

    341 websites on Joomla 1.x, 2.5, 3 or 4, including 248 on Joomla 3

  • WordPress two or more major versions behind27.0%

    The 5,155 WordPress websites whose version can be read, excluding a shared platform (see the box under the table).

    1,393 websites; 68.9% (3,554) are on the latest major version, 7.1

  • Without valid https4.6%

    The 19,854 websites read.

    913 websites, 682 of them because of an invalid certificate (expired, issued for another name…), the others not answering over https

Read this before quoting a figure: the PHP version can only be read on one website in four (4,887 of 19,854), and the 35.6% only applies to those websites. A website behind a firewall, a CDN or a host that hides this information does not show up, and it is mostly older hosting that shows its version: across all websites, the share would probably be lower. This is neither a ranking of towns nor a list of websites: no town is named, on this page or in the file.

WordPress: 1,059 websites are identical (same version 6.6.1, same server, one shared installation). It is very probably a single shared platform, so a single technical decision: I leave it out to talk about websites managed one by one. Counting it, the share two or more major versions behind would be 39.5% (2,452 of 6,214).

By department

The 15 French departments where I read the most websites

For each share, the count in brackets. The share of PHP without fixes is calculated on the department’s websites that show their version, often a few dozen: a few points between two departments mean nothing. All 101 departments are in the downloadable file.

  • 59 · Nord39%

    650 town halls in the directory, 125 of them without a declared website; 499 websites read. WordPress: 37% (185), Joomla: 4% (22).

    55 of 140 websites that show their PHP

  • 60 · Oise24%

    682 town halls in the directory, 151 of them without a declared website; 494 websites read. WordPress: 50% (249), Joomla: 3% (13).

    36 of 147 websites that show their PHP

  • 38 · Isère31%

    521 town halls in the directory, 58 of them without a declared website; 438 websites read. WordPress: 51% (225), Joomla: 3% (15).

    31 of 101 websites that show their PHP

  • 62 · Pas-de-Calais33%

    892 town halls in the directory, 453 of them without a declared website; 406 websites read. WordPress: 41% (166), Joomla: 3% (12).

    37 of 112 websites that show their PHP

  • 80 · Somme27%

    778 town halls in the directory, 344 of them without a declared website; 405 websites read. WordPress: 47% (191), Joomla: 0% (0).

    6 of 22 websites that show their PHP

  • 67 · Bas-Rhin33%

    517 town halls in the directory, 98 of them without a declared website; 394 websites read. WordPress: 55% (215), Joomla: 5% (18).

    34 of 103 websites that show their PHP

  • 33 · Gironde50%

    538 town halls in the directory, 109 of them without a declared website; 392 websites read. WordPress: 43% (168), Joomla: 7% (26).

    33 of 66 websites that show their PHP

  • 77 · Seine-et-Marne22%

    509 town halls in the directory, 105 of them without a declared website; 391 websites read. WordPress: 60% (236), Joomla: 2% (9).

    29 of 134 websites that show their PHP

  • 71 · Saône-et-Loire36%

    569 town halls in the directory, 173 of them without a declared website; 375 websites read. WordPress: 25% (95), Joomla: 1% (4).

    20 of 55 websites that show their PHP

  • 76 · Seine-Maritime46%

    737 town halls in the directory, 316 of them without a declared website; 353 websites read. WordPress: 41% (144), Joomla: 4% (13).

    40 of 86 websites that show their PHP

  • 57 · Moselle32%

    726 town halls in the directory, 344 of them without a declared website; 349 websites read. WordPress: 44% (152), Joomla: 3% (11).

    39 of 121 websites that show their PHP

  • 31 · Haute-Garonne33%

    587 town halls in the directory, 230 of them without a declared website; 332 websites read. WordPress: 48% (159), Joomla: 4% (13).

    29 of 89 websites that show their PHP

  • 35 · Ille-et-Vilaine40%

    352 town halls in the directory, 16 of them without a declared website; 308 websites read. WordPress: 73% (224), Joomla: 2% (5).

    20 of 50 websites that show their PHP

  • 68 · Haut-Rhin37%

    370 town halls in the directory, 39 of them without a declared website; 301 websites read. WordPress: 47% (142), Joomla: 5% (16).

    28 of 76 websites that show their PHP

  • 24 · Dordogne34%

    533 town halls in the directory, 176 of them without a declared website; 298 websites read. WordPress: 43% (129), Joomla: 6% (18).

    26 of 76 websites that show their PHP

All 101 departments, to download: one row per department, with the town halls in the directory, those without a declared website, the websites read, the WordPress and Joomla shares, the websites that show their PHP and, among them, those without fixes. No town, no website address, no provider in the file. CC BY 4.0 licence: cite “Dibodev, survey of 15 and 16 November 2026” with a link to this page.

Small counts: Paris, Hauts-de-Seine, Seine-Saint-Denis and the overseas departments have fewer than 40 websites read. Their shares should not be discussed on their own.

Limits

What these figures do not say

I put them here rather than at the bottom of the page, because they change how the figures read.

  • One website in four shows its PHP

    24.6% of the websites read (4,887 of 19,854). The others sit behind a firewall, a CDN such as Cloudflare or a host that hides the information. Older hosting shows it more often: extended to all websites, the “without fixes” share would probably be overestimated.

  • The version announced by the server

    It is the one the server writes in its answer. A host can serve another one without updating that line.

  • Clusters of identical websites

    772 websites from one platform for communes (all on PHP 8.4.27), 1,059 identical WordPress 6.6.1 websites, 449 identical websites made with the same generator: a single technical decision weighs on hundreds of websites. Excluding the platforms for communes, 42.5% of the websites that show their PHP are without fixes (1,708 of 4,016).

  • Websites not identified

    16.6% of the websites read (3,299) remain not identified: custom-built website, or a tool that leaves no visible trace. 21 websites read at the start of the survey could not be reclassified after a fix to the detection.

  • A few duplicates

    90 of the 19,854 websites read (0.45%) lead to the same website as another address (with and without “www”, or a redirect to a shared website) and are counted twice. Effect on the shares: less than half a point, not corrected.

  • Gaps in the directory

    13,363 town halls declare no website in it, and some do have one; a town hall can also declare an outdated website. The version can be read on 64.8% of WordPress websites and 72.7% of Joomla websites.

What it means for a town hall

What you can do for your town’s website

Read the PHP version, read the Joomla version if the website uses it, then plan the update. The first two only need the website’s address, with no access to its administration. The third is decided with the provider or the host.

  • Read the website’s PHP version

    Enter the website’s address: the free tool reads the PHP version when the server shows it. PHP 8.1 and older no longer receive security fixes, PHP 8.2 loses them on 31 December 2026.

    Read the PHP version 
  • If the website runs Joomla, read its version

    A second free tool reads the Joomla version from the public file made for that. Joomla 3 and Joomla 4 no longer receive fixes, Joomla 5 receives them until 12 October 2027.

    Read the Joomla version 
  • Plan the PHP update

    Before 31 December 2026 if the website runs PHP 8.2 or older: update the website, then change the PHP version, after a backup and a test on a copy.

    See the “PHP update” page 
  • For a Joomla website, one version at a time

    The move goes one branch after the other, up to Joomla 6, which receives security fixes until 16 October 2029. Plan it together with the PHP update.

    See the “Joomla update” page 

The dates

End-of-support dates, read at the source

A version “without fixes”, here, is a version its project no longer fixes. Each date links to the project’s official page.

31 December 2025

PHP 8.1 and older: no fixes at all

PHP 8.1 has been end of life since 31 December 2025, PHP 8.0 since 26 November 2023, PHP 7.4 since 28 November 2022 and PHP 5.6 since 31 December 2018.

Source: PHP, unsupported branches

12 October 2027

Joomla 5, then Joomla 6

Joomla 5 receives security fixes until 12 October 2027, Joomla 6 until 16 October 2029. Latest versions at the time of the survey: 5.4.10 and 6.2.

Source: Joomla, release roadmap

17 August 2023

Joomla 3, discontinued

Official support for Joomla 3 ended on 17 August 2023. The older 1.x and 2.5 branches are also counted as without fixes.

Source: Joomla Magazine, July 2023

WordPress 7.1.4

The latest WordPress version

Latest version released at the time of the survey, read on the official wordpress.org interface. The latest major version is therefore 7.1.

Source: WordPress.org, versions

Who made this survey: me, Léo Guillaume, freelance developer near Rennes, France. I update websites running PHP, WordPress and Joomla for small businesses, freelancers and non-profits, remotely.

Does a figure look wrong? Write to me, I fix it and date the fix.

Method

How this survey is made

A single read of each website’s home page, like any visitor. No attempt to get into a website, no login page opened.

  1. List

    The official directory, town hall by town hall

    Full export of the French government directory, filtered on the “town hall” records, read on 15 November 2026. For each town hall, the first declared website that is neither a ready-made platform nor a social network, then a single row per website address.

  2. Read

    One home page, once

    A single request for the home page of each website, over https then http if needed, waiting 12 seconds at most. No page is kept, only the few pieces of information taken from it.

  3. Tool

    What the page shows

    The website’s tool is recognised from the traces it leaves in the page (WordPress, Joomla, Drupal, TYPO3 or SPIP folders), from the “generator” tag, then from the platforms for communes. The WordPress version comes from that tag or from the core files.

  4. Versions

    PHP and Joomla

    The PHP version comes from the information the server sends with the page. For Joomla, a second request reads the public version file that Joomla installs on every website. Never more than two requests per website.

  5. Check

    A count, then a check by hand

    Count per website address, each share with its base. 30 websites drawn at random were read again by hand on 16 November 2026: no difference on the tool, the version or PHP.

Frequently asked questions

French town hall websites: your questions

How do I find out which PHP version my town’s website uses?

The simplest way: ask the website’s provider or host, who sees it in their customer area. Without access, the free tool on this website reads it when the server shows it, which happens on one town hall website in four (4,887 of 19,854 in this survey). If it does not show it, that says nothing about the version in use.

What happens on 1 January 2027?

PHP 8.2 no longer receives security fixes after 31 December 2026. The website keeps working, but a security problem found afterwards will no longer be fixed in that version. Among the French town hall websites that show their PHP, 9.3% run PHP 8.2 (454 of 4,887): if nothing changes, 44.9% (2,193 of 4,887) will be without fixes on 1 January 2027, against 35.6% today.

Why only one website in four?

Because most servers do not tell their PHP version: firewall, CDN such as Cloudflare, or a host that hides the information. 24.6% of the websites read show it (4,887 of 19,854). Older hosting shows it more often, so the 35.6% share would probably be lower across all websites. I give it for what it is: a measure on a quarter of the websites.

Why leave out 1,059 WordPress websites?

Because they are identical: same version 6.6.1, same server, one shared installation. It is very probably a single shared platform, so a single technical decision, not 1,059 websites managed one by one. Without them, 27.0% of the WordPress websites whose version can be read are two or more major versions behind (1,393 of 5,155); with them, 39.5% (2,452 of 6,214).

Which tools do French town hall websites use?

WordPress first: 48.3% of the websites read (9,592 of 19,854). Far behind come Joomla 4.0% (798), Drupal 3.4% (670), TYPO3 3.3% (648) and SPIP 1.0% (206), next to the platforms for communes and the website builders. 16.6% (3,299) remain not identified.

Where do town hall Joomla websites stand?

The version can be read on 580 of the 798 Joomla websites (72.7%). 58.8% of them (341 of 580) are on a branch without fixes, and Joomla 3 alone accounts for 248. 20.3% (118) already run Joomla 6. On the PHP side, 52.4% of the Joomla websites that show their version are without fixes (140 of 267).

Is my town’s website on a list?

No list is published. The page and the file only give totals, for France and by department: no town, no website address, no provider. For your town’s website, the two free tools on this website answer from its address alone.

Can these figures be reused?

Yes. The figures and the file by department are under the CC BY 4.0 licence: cite “Dibodev, survey of 15 and 16 November 2026” with a link to this page. Keep the base of each figure, especially for PHP: 35.6% of the 4,887 websites that show their version, not of the 19,854 websites read. A mistake? Write to me, I fix it and date the fix.

Unsure about your town’s website?

Send me its address. I tell you in writing within 24 hours which versions it uses and what to plan before 31 December 2026, with no commitment.