SSH Client Configuration Audit

Explain a supplied SSH configuration, including shadowed settings and declared risks.

On-device No sign-up Free to use

Review SSH settings controls

?

Up to 200,000 characters and 5,000 lines. Host blocks and the options listed on this page are explained. Include and Match are refused. Very costly wildcard combinations stop with a matching-limit error.

?

The name you would type on the command line, such as git.example.com. Host patterns are matched against this name.

Drop your text file here

or choose one from your device

Optional, up to 200,000 bytes. A chosen file replaces the pasted text above and is read locally only; nothing is uploaded, executed or contacted.

    Processed in your browser. Your inputs stay on this device.

    Showing an example. Change the fields, then use review ssh settings to update it.

    Result

    Showing an example.

    Review the supplied jumpserver block, including agent forwarding, host checking and the discarded known_hosts file.

    4 options apply to jumpserver; 3 need a closer look; 1 file-level note.

    Loading the tool. Your result will appear here.

    https://usefreetools.net/ssh-client-configuration-audit · 20 November 2026

    Was this helpful?

    How to use SSH Client Configuration Audit

    1. Paste the supported SSH client configuration or select its UTF-8 file. A selected file replaces the pasted text.
    2. Enter the target name you would pass to ssh, such as jumpserver, then run Review SSH settings.
    3. Read matching Host blocks, selected options and shadowed scalar values in file order. IdentityFile and CertificateFile collect distinct paths instead.
    4. Review declared risks and file-level notes against the original configuration. The report masks private-key paths and local commands and does not execute or connect.

    Example: SSH Client Configuration Audit

    Review the supplied jumpserver block, including agent forwarding, host checking and the discarded known_hosts file.

    You add
    SSH client configuration: # Work hosts Host *.example.com User deploy IdentityFile ~/.ssh/id_ed25519_work StrictHostKeyChecking yes Host jumpserver HostName jump.example.net ForwardAgent yes StrictHostKeyChecking no UserKnownHostsFile /dev/null; Target host you would connect to: jumpserver
    You get
    4 options apply to jumpserver; 3 need a closer look; 1 file-level note.

    Options

    SSH client configuration
    Up to 200,000 characters and 5,000 lines. Host blocks and the options listed on this page are explained. Include and Match are refused. Very costly wildcard combinations stop with a matching-limit error.
    Target host you would connect to
    The name you would type on the command line, such as git.example.com. Host patterns are matched against this name.
    Or choose a local SSH config file
    Optional, up to 200,000 bytes. A chosen file replaces the pasted text above and is read locally only; nothing is uploaded, executed or contacted.

    Supported inputs and limits

    • Declared supported Host/configuration subset only.
    • No Include/Match expansion, shell execution, host contact or complete OpenSSH environment audit.
    • Optional local UTF-8 config replaces pasted text.
    • Most options use the first value;
    • IdentityFile and CertificateFile add distinct declared paths in file order.
    More details

    Include and Match are refused.

    A shared matching-work limit stops unusually costly Host patterns.

    Where your input is processed

    This tool does not upload your inputs. See the limits for anything saved on your device.

    Read the effective supported values in order

    Matching Host blocks are considered in supplied file order. Most supported scalar settings keep their first obtained value, while IdentityFile and CertificateFile accumulate distinct paths from matching blocks. This is the tool’s supported subset, not a reading of other configuration files or an installed SSH environment. Include and Match are refused; commands and host connections are never executed.

    Questions about SSH Client Configuration Audit

    Are Include files opened?

    No. Include and Match are refused in this supported subset.

    Will proxy commands run?

    No. The review does not execute commands.

    Is this my actual SSH configuration?

    Only the supplied text and supported target semantics are modeled. Other files and runtime conditions are unverified.

    Page updated · Project managed by Tony Hines · Report a problem with SSH Client Configuration Audit