Laravel

Explore Laravel’s PHP application framework, database-backed development and environment configuration, with context on deploying and maintaining a custom web app.

Updated 8 September 2026

What Laravel is used for

Laravel is a PHP framework for building web applications. It supplies conventions and tools for application development rather than a ready-made site with fixed pages. Its documentation covers configuration, databases, migrations and the surrounding development workflow.

For an internal approval system, the framework provides a foundation while the project defines the records, permissions and approval steps. The business workflow remains application code that a team must design and maintain.

Configuration and database changes

Laravel separates environment-specific settings from application code and provides migrations for evolving a database. Development and production may use different credentials or services even when they run the same codebase.

For example, adding a required field involves more than drawing a new input. Existing database records, validation and the release order all need to be considered so the deployed application can read and write data safely.

Preparing a Laravel deployment

Configure the server to expose the intended public directory, keeping application configuration and private files out of the document root. Verify database connectivity and the environment values used in production.

Test the entire workflow with a normal user account. An administrator completing a form does not establish that permissions, validation and error recovery work for the people who will use the application every day.

How DNSTrace.dev detects Laravel

Detection reads the final HTTPS response and the first bytes of its markup. One matching signal is reported as strong evidence; two or more independent signals are reported as confirmed.

  • laravel_session cookie — The default session cookie name, set on responses that start a session.
  • XSRF-TOKEN cookie — Laravel's cross-site request forgery token, supporting evidence alongside the session cookie.
  • PHPSESSID absence — Laravel manages its own session cookie rather than using the PHP default, which is why the framework and the language are reported separately.

What a detection proves

The application is built on Laravel.

What it does not prove

The framework version or the hosting arrangement. A site that renames its session cookie, a common hardening step, becomes undetectable by this signal.

Common questions about Laravel

Is Laravel a CMS like WordPress?

Laravel is an application framework. A CMS can be built on it, but installing Laravel does not by itself provide a finished editorial website or a particular business application.

Why does a Laravel site sometimes show nothing?

The session cookie is only set when a session starts, and the cookie name can be changed in configuration. Either removes the signal.

Is Statamic detected as Laravel?

Statamic is built on Laravel and is identified separately from its own x-powered-by value. Both can appear.

Server languagePHP

Open source, the PHP Group

Content management systemCraft CMS

Pixel & Tonic, Inc.

Application frameworkDjango

Open source, Django Software Foundation

Application frameworkExpress

Open source, OpenJS Foundation

Check a domain

Run a full lookup to see the delivery layer, the detected application stack, live TLS and the announcing network side by side.

Run a lookup →Application stack →Evidence model →