A file named tools.php3 is a web script written for PHP 3 [1]. The extension marks the generation of the language the code targets, the version announced in June 1998 [2]. FileInfo, a file-type reference last updated in December 2018, describes a .php3 file as a web page whose PHP code a server-side PHP engine parses to generate the HTML a visitor receives, and notes that such scripts were often used in combination with a database such as MySQL [1].

Found in an old project folder, an inherited hosting account or a scan report, this file asks one practical question. A server hands a .php3 file it has not mapped to PHP back as a plain file [4], the kind you can open and read in any text editor [1]. A host whose configuration still maps the extension runs the file through its PHP engine [3]. Open the file, read it, then request it by URL on the host; that one request tells you which of the two situations you are in, and whether you are holding dead weight or live code.

The name is 1990s PHP history

PHP began in 1994 as a set of CGI binaries Rasmus Lerdorf wrote to track visits to his online resume, and he named that first suite of scripts Personal Home Page Tools [2]. He released its source code to the public in June 1995 [2]. The word tools in your filename reads as generic utility-script naming of that era, and the extension identifies the format [1].

PHP 3.0 arrived in June 1998, when the new PHP Development Team announced it as the official successor to PHP/FI 2.0. By the time of that announcement it was already installed on more than 70,000 domains around the world, and at its peak it ran on approximately 10 percent of the web servers on the Internet [2]. That mainstream share helps explain why such files can still surface in backups and inherited accounts. The era ended in May 2000, when PHP 4.0, built on a rewritten core engine called Zend, was officially released and took the current-version spot PHP 3 had held [2].

Why the file does not run unless the host still maps .php3

Where a host has not mapped .php3 to PHP, the page the script was built to produce never appears, because PHP executes only in the file extensions an administrator explicitly assigns to it. The PHP manual's security chapter spells out that mechanism; administrators configure servers such as Apache to parse specific filetypes through PHP, either in an .htaccess directive or in the server configuration itself, and for that to work the files must be renamed to the mapped extensions [3]. Apache's own documentation covers the other side of the same rule. Normally, all files are simply served by the server, and only certain file types are handled separately, with the default handler sending a file as static content; handlers can also be configured explicitly, based on filename extensions or location [4].

Put together, those two documents leave tools.php3 one of two outcomes on any given host. If the host maps .php3 to PHP, the server runs the file through its PHP engine. If it maps only .php, which is where PHP pages generally live today [1], the server hands back the file itself, in one form or another [4]. One URL request distinguishes the two; a page the server generates, even a PHP error page, means the engine is running the file, and the file itself coming back means it is not.

The age question is just as settled. PHP's official supported-versions page, checked on 12 November 2026, lists exactly four supported branches, 8.2 through 8.5, with security support for 8.2 ending 31 December 2026 [5]. Every branch receives two years of active support followed by two years of security-only fixes, and branches past that point are marked end of life, where users may be exposed to unpatched security vulnerabilities [5]. PHP 3 appears in none of them [5]. Even PHP's own current tooling points the same way; the built-in development server returns standard media and document types from a fixed extension list, and no PHP extension appears in that list, .php3 included [6].

What to do with tools.php3, in order

The sequence starts on your own screen, where nothing can execute, and moves outward only after you know what the file does.

  1. Open the file in a text editor. Any plain editor shows the code, because .php3 files are editable plain text [1]. Note what the script connects to; PHP 3-era scripts were often used together with a MySQL database, so database calls, includes and file paths in the code tell you what this one touched [1].

  2. Request the file by URL on the host where it lives. A page the server generates, even a PHP error page, means the host runs .php3 files through its PHP engine, and the file is live code. The file itself coming back means it is inert on that server, and the remaining question is only who can read its contents at that URL [4].

  3. If the goal is to revive the script, plan a port. Copying the file to .php makes the server attempt to run it, since renamed files are what mapped extensions execute [3]. The rename opens the work; PHP 8.0, first released in 2020, was another major update of the language [2], and PHP publishes a migration guide for every branch it currently supports [5]. Expect the code to need changes, and use those guides as the map.

  4. If the file is a keepsake or a backup, keep it out of the web root. A file the server never maps still sits at a public URL on live hosting, and static content is served to anyone who requests it [4]. Moving the file off the web root removes that URL.

The risk depends on the host and the contents

An idle tools.php3 carries one of two risks. On a host that still maps the extension, the file executes as unsupported code; PHP 3 stopped being the current version in May 2000 [2], and no PHP 3 branch appears in any supported set today [5]. On a host that maps only .php, the exposure is the file's contents at a public URL [4].

The extension dates the file, and its contents and one URL request decide the response. A tools.php3 that reads as a small 1998 utility and comes back as the file itself is dead weight you can archive off the web root. One that comes back as a page the server generated is live PHP 3-era code facing requests, and the safe response is to retire it or port it before the next visitor arrives.