Skip to main content
Free · No signup · Real nginx -t + Gixy

Test & Validate NGINX Configuration

Check NGINX config syntax, find security misconfigurations, and see which known CVEs affect your NGINX version, all in one pass. Share the result with a unique URL.

  • Gixy security analysis
  • 63 official nginx.org advisories, updated 2026-10-24
  • Cached 1 hour, kept only if you save
nginx.conf

Problems

0

Paste a config, enter a version, or both

  • SyntaxReal nginx -t with line numbers
  • SecurityGixy: SSRF, header injection, alias traversal and more
  • Known CVEsYour version against every nginx.org advisory
  • CVE triggersFlags when your config contains the vulnerable pattern

Then click Validate, or .

CLI
nginx -T 2>/dev/null | curl -sF 'c=<-' https://www.getpagespeed.com/n
✨ Want NGINX Plus features at a fraction of the cost? Meet NGINX Extras — HTTP/3, Brotli, ModSecurity, PageSpeed & 100+ modules! Learn More →

Security Analysis

Gixy-powered detection

Known CVE Check

Version vs nginx.org advisories

Shareable URLs

Unique link for each config

CLI Support

Pipe from nginx -T

Location Tester

Debug path matching

Check Your NGINX Version for Known CVEs

How it works

Enter the version from nginx -v, or paste nginx -V output above your config. We match it against every advisory on nginx.org and show the release that fixes each one.

Config-aware

Some NGINX CVEs need a specific config pattern to be reachable. When you also paste your config, Gixy checks for that pattern and marks the CVE with the exact line.

Distro packages

Debian, Ubuntu and RHEL backport security fixes without changing the version number, so a version-only match can overstate exposure. Packages from the GetPageSpeed repository track upstream releases, so the version is accurate.

How to Test Your NGINX Configuration

Test Syntax Locally

Before reloading NGINX, always test your configuration:

nginx -t

Validates syntax and reports errors with line numbers. Exit code 0 means success.

Dump Full Configuration

To see the complete config with all includes resolved:

nginx -T

Shows effective configuration. Pipe to this tool for security analysis.

Common Test Errors

  • unknown directive — typo or missing module
  • unexpected "}" — mismatched braces
  • host not found — DNS issue (often OK)
Found issues in your config?

Our NGINX experts audit your complete production setup. Detailed report from $499; audit with implementation from $999.

Get Your Audit
Need more NGINX modules?

Install Brotli, ModSecurity, GeoIP2, PageSpeed and 100+ pre-built modules for RHEL, AlmaLinux, Rocky, Debian, Ubuntu & more.

View Plans
NGINX Extras Ebook: become an expert today.
Did you know? NGINX Extras add PageSpeed, Brotli and 80+ modules!

Need Pre-Built NGINX Modules?

Get HTTP/3, Brotli, ModSecurity, PageSpeed, and 100+ modules for RHEL, Rocky Linux, Debian & Ubuntu. Ready to yum install or apt install.

Get Repository Access

FAQ

Is my NGINX configuration stored?

Not permanently. To make repeat checks of the same config fast, the sanitized config and its results are cached for up to one hour, then deleted automatically. It is only stored beyond that if you click Save & Share, and you choose whether that link is unlisted or public and when it expires.

Where does the CVE data come from?

From the official NGINX security advisories published on nginx.org. Each result links to the advisory and shows the stable or mainline release that fixes it.

My distro package shows CVEs. Am I vulnerable?

Not necessarily. Debian, Ubuntu and RHEL backport security fixes without changing the NGINX version number, so check your vendor security tracker. Packages from the GetPageSpeed repository follow upstream releases, so their version number is accurate.

What does Gixy check?

Gixy is a static analyzer for NGINX configuration. It finds misconfigurations such as SSRF through proxy_pass, HTTP response splitting, alias path traversal, add_header redefinition and host header spoofing.

How to Use the NGINX Config Checker

Paste your NGINX configuration into the editor above and click Validate. The tool analyzes your configuration for syntax errors and security vulnerabilities in seconds.

You can also validate directly from your server’s command line:

nginx -T 2>/dev/null | curl -sF 'c=<-' https://www.getpagespeed.com/n

This command dumps your full NGINX configuration and sends it to our validator, returning results directly in your terminal.

What Security Issues Does It Detect?

This nginx config checker uses Gixy, a powerful static analyzer for NGINX configurations. The same analysis runs inside your editor through the Gixy IDE plugins for VS Code and JetBrains. Here it detects common security misconfigurations:

  • HTTP Response Splitting – Detects user-controlled values in response headers that could allow header injection attacks
  • SSRF via resolver – Identifies configurations where attackers might exploit DNS resolution to access internal services
  • Path Traversal – Finds alias directives that could allow reading files outside the intended directory
  • Version Disclosure – Warns when server_tokens exposes your NGINX version to attackers
  • Missing Security Headers – Checks for Host header validation to prevent host header attacks
  • Referrer/Origin Leaks – Detects potential information leakage through improperly configured proxy headers

Common NGINX Configuration Mistakes

Even experienced administrators make these mistakes:

  1. Using $uri in redirects – Can lead to CRLF injection. Use $request_uri instead.
  2. Overly permissive alias paths – Always ensure location and alias paths end consistently (both with or without trailing slashes).
  3. Missing internal directive – Error pages and internal locations should use internal to prevent direct access.
  4. Improper regex in location blocks – Test your location patterns with our built-in Location Tester tool.

Why Use a Configuration Validator?

Manual review of NGINX configurations is time-consuming and error-prone. An automated validator helps you:

  • Catch syntax errors before deploying to production
  • Identify security vulnerabilities that manual review might miss
  • Save time by getting instant feedback on configuration changes
  • Learn best practices through detailed explanations of each issue
  • Collaborate effectively by sharing configurations with your team

Location Block Testing

The built-in Location Tester helps you understand how NGINX matches requests to location blocks. Enter a test URI path (like /api/users or /images/logo.png) and see exactly which location block would handle that request.

This is invaluable for debugging complex routing configurations with multiple location blocks, regex patterns, and prefix matching.

Share and Collaborate

After validation, save your configuration to get a unique shareable URL. You can:

  • Share configs with team members for review
  • Fork existing configurations to create variations
  • Set expiration times for temporary configs
  • Choose between public and unlisted visibility
  • NGINX Extras – Pre-built NGINX modules including Brotli, PageSpeed, ModSecurity, and 50+ more
  • GetPageSpeed Blog – NGINX tutorials, performance tips, and security guides
  • Repository Access – Get our RPM repository for enterprise-grade NGINX packages