Config linter

Paste an nginx-style configuration to find unclosed braces, missing semicolons, duplicate directives and empty blocks.

Runs in your browser ยท nothing is sentLogs & configNew

Paste a configuration to see the result.

How to use

  1. Copy the configuration you want to check.
  2. Paste it into the tool.
  3. Review the findings: unclosed blocks, duplicate directives, empty blocks.
  4. Check the directive table to verify the block structure.

Common scenarios

Checking a configuration before applying it

Find a forgotten closing brace or a duplicate "listen" line before actually applying a configuration change.

Cleaning up an inherited configuration

Find empty blocks and duplicate directives in a configuration you did not write yourself, as a first step toward cleanup.

About this tool

Paste a configuration in the common "block with { } and statements ending in ;" style (nginx, and similar formats), and the tool checks the structure: unclosed or extra closing braces, a possibly missing semicolon at the end, duplicate directives within the same block (for example "listen" twice in one server block), and empty blocks that are likely leftovers from editing. This is a syntax check: the tool does not know the specific directives of nginx, Apache or HAProxy, only the block structure. Nothing is sent anywhere; the configuration stays in your browser.

๐Ÿ”’ Your input stays in your browser and is never sent anywhere.

Frequently asked questions

Does this check whether my nginx configuration works?

No, this is not a replacement for "nginx -t". The tool only understands the general block/semicolon structure, not which directives are valid or what they mean.

Why is a duplicate directive flagged when it is sometimes intentional?

In some configurations a repeated directive (for example several "listen" lines in different contexts) is intentional, but within the exact same block that is rarely the case. Review the finding in context before removing anything.

Does this work for Apache or HAProxy configurations too?

The structure check (braces, semicolons) works for any format using the same syntax convention. Apache typically uses a different style (<Directive> ... </Directive> without semicolons), which this linter is not built for.

What to do next

Also useful

Found a problem or have a suggestion? Tell us