Environment Config Auditor

Paste your .env and, optionally, .env.example. The auditor reports syntax problems, missing variables and settings that are risky in production, values never leave your browser.

Examples:

Findings

How it works

Both files are parsed with the rules that Laravel (phpdotenv), Symfony Dotenv, Node's dotenv and Docker env files share: comments, the export prefix, quoted and multi-line values and inline comments. Syntax that one of these loaders rejects or reads differently is reported with its line number.

The keys of .env are compared with .env.example. A variable missing from .env usually means a failed deploy or a silent fallback to a default; a variable missing from .env.example means the next developer will not know it exists.

Security checks depend on the profile, which is detected automatically (Laravel, Symfony, Node.js, Docker): debug mode in production, a missing or malformed APP_KEY, weak or placeholder secrets, empty database passwords, wildcard CORS, credentials inside URLs and strings that look like real API keys.

The checks are heuristics. They do not know your infrastructure, so treat the findings as a review checklist, not a verdict.

When it helps

  • Before a deploy: make sure production has every variable the new release expects.
  • When onboarding a developer: compare their local .env with the project's .env.example.
  • After a framework upgrade: spot variables that were renamed in the new .env.example.
  • In a security review: catch APP_DEBUG=true, default passwords and test keys on a live server.

Frequently asked questions

// 01 Is it safe to paste a production .env here?

The file is processed only in your browser: nothing is uploaded, stored or logged, values of secret-looking variables are masked on screen, and the exported report contains keys and findings, never values. If your company policy forbids pasting secrets into any web page, replace the values with placeholders, the syntax and key comparison still work.

// 02 Why is an unquoted value with spaces an error?

Laravel's phpdotenv refuses to load such a file ("Encountered unexpected whitespace"). Wrap values containing spaces in double quotes: APP_NAME="My Shop".

// 03 Why is a # inside a value flagged?

Node's dotenv (since version 15) treats # as the start of a comment even in the middle of an unquoted value, while phpdotenv only does so after a space. PASSWORD=abc#123 therefore loads differently in different stacks. Quote values that contain #.

// 04 Does a clean report mean my configuration is secure?

No. The auditor catches common, recognisable mistakes. It cannot judge network exposure, file permissions on the server or whether a strong-looking secret was leaked elsewhere.

QR code for a PayPal donation

Did this save you time?

The tools and simulations are free, ad-free and need no sign-up. If they helped you, you can send a contribution for coffee and new tools.

Donate via PayPal

What happens to your data

Privacy policy (in Czech) 
  • The tools process your input with JavaScript on your device. Nothing you paste is sent to the server, stored or logged.
  • The exception is the SPF/DKIM/DMARC check: it asks public DNS (Cloudflare, Google as a fallback) directly from your browser. Only the domain name is sent.
  • Analytics (only if you accept analytics cookies) records anonymous events such as "a tool was opened". Never your input or results.
  • No ads or advertising scripts run on the tool and simulation pages.

Need a hand?

I build and maintain web applications in Laravel and PHP. If something on these pages is giving you trouble in a project, get in touch.

Get in touch