Paste your ufw status verbose output and click Audit.
Paste sudo ufw status verbose or sudo nft list ruleset. See traffic funnel and audit findings.
🔒 Runs 100% in your browser — your files never leave your device
Paste your ufw status verbose output and click Audit.
Run sudo ufw status verbose on your server and copy the full output.
Paste it into the tool and click Audit. The traffic funnel and audit findings appear instantly.
Review findings for high-risk open ports, missing default-deny, and IPv4/IPv6 mismatches. Nothing leaves your browser.
Run sudo ufw status verbose in your terminal and paste the full output into the tool.
High-risk ports are commonly targeted by automated scanners and attackers. This tool flags ports 22 (SSH), 23 (Telnet), 3389 (RDP), 5432 (PostgreSQL), 3306 (MySQL), 6379 (Redis), and 27017 (MongoDB) when open to Anywhere.
UFW should block all incoming traffic by default unless explicitly allowed. If your default policy is allow, any port not covered by a rule is open to the internet.
If you allow a port for IPv4 but not IPv6 (or vice versa), traffic on the uncovered protocol can bypass your rules. This tool flags ports where one protocol is covered and the other is not.
No. All processing happens in your browser. Your UFW output is never sent to or stored on any ConfigClarity server.
Yes. Paste the output of
sudo nft list ruleset and the tool will
auto-detect nftables format. It checks for missing default
drop policy on the input chain, high-risk ports open to
Anywhere, missing loopback and ct state established rules,
and rules without comments. UFW and nftables formats are
both supported — the tool detects which one you pasted.