We support numerous PHP extensions to aid in the development of your website, and to help make your PHP enabled website operate faster and more efficient. Currently we support 8 versions of PHP on our Windows shared services. Instead of maintaining a static list of all loaded and available PHP extensions—which can change with server updates and security patches—you can view our PHPinfo output for each PHP version at dedicated URLs. This delivers the authoritative, real-time view of the exact configuration running on the servers.

PHP extensions are compiled libraries that extend the core PHP runtime with additional functions and classes. On Windows they are implemented as DLL files loaded through the php.ini configuration. Having the right extensions pre-installed removes the need for custom builds, reduces deployment friction, and ensures consistency across all accounts on the shared platform. Common capabilities enabled by these extensions include improved database access, image processing, XML handling, encryption, caching, and compression. Without them many popular PHP applications would fail or run with degraded performance.

#Accessing Official PHPinfo Pages

The PHPinfo report is the single source of truth for the PHP build on our Windows servers. It lists every compiled extension, version details, configuration directives, environment variables, and loaded modules. We publish these reports for each of the 8 supported PHP versions rather than attempting to document them manually.

For PHP 5.2.x visit: https://phpinfo.aspnix.com/52. Equivalent pages exist for the remaining PHP versions; replace the path segment with the appropriate version identifier or contact support for the exact link if needed. Load the page in your browser to see sections such as "Loaded Extensions" and "PHP Core" that detail what is available.

#Creating a Local PHPinfo File for Your Site

When diagnosing issues specific to your account or PHP version selector, create a temporary diagnostic file in your web root. This reports the exact configuration used by your live site rather than the generic version pages.

php 
<?php
phpinfo();
?>

Save the snippet above as phpinfo.php, upload it via FTP or the file manager, then request it through a browser. The output matches the official pages but reflects any per-account settings. Delete the file immediately after use; leaving it publicly accessible exposes server paths, loaded modules, and configuration that attackers can leverage.

#Checking Extension Availability Directly in Code

Hard-coding assumptions about extension presence leads to runtime errors. Use PHP's built-in functions to test for required modules at the start of your application or during bootstrap. This practice is especially important on shared hosting where you cannot modify the global php.ini.

php 
if (extension_loaded('gd')) {
    // Use image functions
    echo 'GD extension is available.';
} else {
    // Graceful fallback or error
    error_log('GD extension required but not loaded');
}

// Alternative check for specific functions
function_exists('imagecreate')

The extension_loaded() call is fast and safe to use in production. For opcode cache or performance modules, also inspect get_loaded_extensions() to enumerate everything active in the current request. Differences between PHP versions can be significant; an extension present in 5.2.x may be replaced by a native implementation or moved to PECL in later releases.

#Performance and Security Considerations on Windows

Windows shared hosting uses the FastCGI or ISAPI interface for PHP, which interacts differently with extensions than Apache on Linux. Some extensions incur higher overhead due to thread safety requirements. Enabling only the extensions your application actually needs keeps the PHP process footprint smaller and improves response times.

  • Review the PHPinfo page for your chosen version before migrating an application from another host.
  • Test for required extensions during deployment rather than at runtime to catch issues early.
  • Never rely on phpinfo() output in production code or leave diagnostic files on the server.
  • Be aware that Windows file paths and permission models differ; extensions dealing with filesystem or external processes may require adjusted code.

If an extension critical to your project does not appear in the PHPinfo for any available version, the configuration is intentionally limited for stability and security on the shared platform. In such cases evaluate upgrading the application to use built-in alternatives or consider a VPS environment with full control.

#Practical Takeaway

Start by visiting the PHPinfo URL for the PHP version your site currently uses. Cross-reference the loaded extensions against your application's requirements. Add runtime checks for critical modules and remove the diagnostic file when finished. This workflow ensures compatibility, avoids unexpected errors, and lets you take full advantage of the extensions we have enabled across all 8 PHP versions on Windows shared hosting.