A phpinfo page is a one-line PHP script that dumps your account's full PHP configuration: version, loaded extensions, memory limits, upload limits, and every ini setting currently in effect. It's the fastest way to confirm what PHP is actually doing on your domain, not what you assume it's doing. Create it, check it, then delete it. Leaving it live exposes your file paths and server details to anyone who finds the URL.
Create the file
Log in to portal.flashcloud.com, open your hosting service, and launch File Manager (or use the File Manager tool inside cPanel). Navigate to the document root for the domain you want to check, usually public_html or a subfolder for an addon domain.
Create a new file named phpinfo.php and add this as its only content:
<?php phpinfo(); ?>
Save it, then visit https://yourdomain.com/phpinfo.php in a browser. You'll get a long page listing your PHP version, configured extensions, and every directive currently applied to requests on that domain.
What you're actually checking
The two sections people usually want are near the top: the PHP Version line and the Configuration File (php.ini) Path block. Below that, search the page (Ctrl+F or Cmd+F) for the directive you care about, things like upload_max_filesize, post_max_size, memory_limit, or max_execution_time. Each one shows a "Local Value" (what's active for this account) and a "Master Value" (the server default).
If the version shown isn't the one you expected, switch it from the PHP Version tile in the portal, which lets you set PHP per domain from 7.4 through 8.3. If you need to change an actual limit like upload size or memory, that's not done through phpinfo; the page is read-only. Go to cPanel → Software → MultiPHP INI Editor and edit the value there, either in Basic mode or by hand in Editor mode for your domain's home directory.
Why not leave it up
A public phpinfo page hands out more than PHP settings. It reveals your server's file system paths, the exact module and extension versions installed, environment variables, and sometimes internal IP or configuration details, all useful reconnaissance for anyone probing your site for a known vulnerability in a specific software version. Search engines will also index it if you leave it reachable long enough.
There's no safe way to "hide" it with a weird filename either. Bots scan for common paths like phpinfo.php, info.php, and test.php constantly. Treat the file as temporary from the moment you create it.
Delete it when you're done
Go back to File Manager, select phpinfo.php, and delete it. If you created it inside a folder with directory indexing or caching in front of it, do a hard refresh on the URL afterward to confirm it now returns a 404 instead of a cached copy of the page.
If you only needed one specific value and didn't want to leave any file behind at all, you can skip the browser step and check the same information from the command line over SSH with php -i | grep memory_limit (swap in whatever directive you need), which reads the CLI PHP config and never touches the document root.
When to open a ticket
If phpinfo shows a PHP version or extension state that doesn't match what you set in the portal, or a setting in MultiPHP INI Editor isn't taking effect after you save it, open a ticket from Support → New ticket in the portal. That's a configuration mismatch worth a second set of eyes rather than something to keep troubleshooting blind.