DevOps tools
10 browser-based tools for infrastructure and deployment workflows — lint, format, validate, and build config files without uploading anything. No signup, no cloud, nothing leaves your device.
DevOps tools
-
Dockerfile Linter
Check Dockerfiles for common mistakes, security issues, and best-practice violations.
Open tool →
-
NGINX Config Formatter
Format and indent NGINX configuration files for readability.
Open tool →
-
.env Formatter
Validate, sort, and format .env environment variable files.
Open tool →
-
.htaccess Builder
Generate Apache .htaccess rules for redirects, HTTPS, auth, and more.
Open tool →
-
GitHub Actions Linter
Validate GitHub Actions workflow YAML structure and common mistakes.
Open tool →
-
SSH Keygen Builder
Build the right ssh-keygen command for RSA, Ed25519, or ECDSA keys.
Open tool →
-
Port Reference
Browse and search the well-known port numbers with protocol and service details.
Open tool →
-
SSL Cert Decoder
Paste a PEM certificate to decode subject, issuer, and validity dates in your browser.
Open tool →
-
DNS Record Builder
Build and format A, AAAA, CNAME, MX, TXT, and other DNS zone file records.
Open tool →
-
.gitignore Builder
Select languages and frameworks to generate a combined .gitignore file.
Open tool →
Why browser-only DevOps tools?
Infrastructure configuration files often contain sensitive data: environment variable values, SSL private key paths, server hostnames, and authentication credentials. Uploading these to an online linter or formatter means trusting a third party with production secrets. The tools on this page run entirely in your browser — paste freely, audit thoroughly, and share nothing.
These tools are designed for the moments between commits: quickly checking a Dockerfile before pushing an image, formatting an NGINX config block before a deploy, or building a DNS record string before updating your zone file. Fast, private, and always available.
Choosing the right tool
For container workflows: start with the Dockerfile Linter to catch mistakes before building. For web server work: use the NGINX Formatter or .htaccess Builder. For CI/CD: validate your pipelines with the GitHub Actions Linter. For security: decode SSL certificates or generate SSH keygen commands. For DNS: use the DNS Record Builder. For project setup: generate .gitignore files and format .env files.
Frequently Asked Questions
- Do my config files get uploaded to a server?
- No. Every DevOps tool on this page runs entirely in your browser using JavaScript. Your Dockerfiles, NGINX configs, SSH keys, and certificates never leave your device — not even temporarily.
- Can I use these tools with sensitive production config?
- Yes. Because all processing happens locally in your browser, it is safe to paste production configuration files, SSH key comments, SSL certificates, and .env files without risking exposure to third parties.
- Does the Dockerfile linter cover all best practices?
- The Dockerfile linter checks for the most impactful best practices: correct instruction order, combined RUN statements, avoiding the latest tag, using COPY over ADD, setting a non-root USER, and more. For a comprehensive audit, pair it with Hadolint in CI.
- Can the SSL cert decoder handle certificates from any CA?
- Yes. The decoder parses the PEM-encoded DER binary directly in your browser. It works with certificates from any Certificate Authority — Let's Encrypt, DigiCert, Comodo, self-signed, or any other CA.
- What DNS record types does the DNS Record Builder support?
- The builder supports A, AAAA, CNAME, MX, TXT, NS, CAA, and SRV records. It outputs the zone file format and the matching dig command for verification.
- Which .gitignore templates are included?
- Templates cover the most common stacks: Node.js, Python, Java, Go, Rust, PHP, Ruby, .NET/C#, Xcode/iOS, Android, React, Docker, Terraform, and a generic OS template for macOS and Windows system files.
- Do these tools work offline?
- Yes. All computation runs locally once the page has loaded. The tools continue to work with no network connection after the initial page load.
- Which SSH key type should I generate?
- Ed25519 is the modern default — it is fast, small, and secure. Use RSA 4096 when connecting to older servers that do not support Ed25519. Avoid RSA 1024 and DSA entirely as both are considered weak.