Known-Hosts Change Comparer

Compare supplied known_hosts files and filter changed, added or removed pins.

On-device No sign-up Free to use

Compare host pins controls

?

Up to 500 records / 500,000 UTF-8 bytes. RSA, Ed25519 and P-256 records; revoked/CA markers and opaque version 1 hashed names.

?

Exact host tokens and key types are compared. Names are never resolved and an added key is not evidence of an attack.

Drop your file here

or choose one from your device

One UTF-8 file. The selected file takes priority over earlier text.

    Drop your file here

    or choose one from your device

    One UTF-8 file. The selected file takes priority over later text.

      ?

      The JSON download retains the complete comparison and the displayed subset.

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

      Showing an example. Change the fields, then use compare host pins to update it.

      Result

      Showing an example.

      Add new.example while leaving the existing demo.example Ed25519 pin unchanged.

      Added 1, removed 0, changed 0, unchanged 1 host/type records.

      Loading the tool. Your result will appear here.

      https://usefreetools.net/known-hosts-change-comparer · 20 November 2026

      Was this helpful?

      How to use Known-Hosts Change Comparer

      1. Paste the earlier and later known_hosts text, or select one UTF-8 file for either state. A selected file replaces the text on that side.
      2. Choose All, Changes or a specific record state, then run Compare host pins.
      3. Compare the recorded host token, marker, key type and fingerprint sets. Different types or markers are separate records; hashed tokens are matched only when identical.
      4. Download the JSON to retain the complete comparison and selected view. Confirm an expected key independently before making any separate SSH-file change.

      Example: Known-Hosts Change Comparer

      Add new.example while leaving the existing demo.example Ed25519 pin unchanged.

      You add
      Earlier known_hosts text: demo.example ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAECAwQFBgcICQoLDA0ODxAREhMUFRYXGBkaGxwdHh8g; Later known_hosts text: demo.example ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAECAwQFBgcICQoLDA0ODxAREhMUFRYXGBkaGxwdHh8g new.example ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAECAwQFBgcICQoLDA0ODxAREhMUFRYXGBkaGxwdHh8g; Records to display: All
      You get
      Added 1, removed 0, changed 0, unchanged 1 host/type records.

      Options

      Earlier known_hosts text
      Up to 500 records / 500,000 UTF-8 bytes. RSA, Ed25519 and P-256 records; revoked/CA markers and opaque version 1 hashed names.
      Later known_hosts text
      Exact host tokens and key types are compared. Names are never resolved and an added key is not evidence of an attack.
      Earlier known_hosts file (optional)
      One UTF-8 file. The selected file takes priority over earlier text.
      Later known_hosts file (optional)
      One UTF-8 file. The selected file takes priority over later text.
      Records to display
      The JSON download retains the complete comparison and the displayed subset.

      Supported inputs and limits

      • Up to 500 records and 500,000 UTF-8 bytes per state, with supported RSA, Ed25519 and P-256 keys.
      • Identifiers use the exact host token, marker and key type.
      • Multiple keys per identifier are retained.
      • Version-1 hashed names remain opaque; different salts can prevent matching the same underlying hostname.
      • Selected files replace pasted text on their side.
      More details

      The display filter leaves the complete JSON comparison intact.

      No host contact, hostname recovery, attack determination or pin replacement is performed.

      Where your input is processed

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

      A changed pin needs investigation

      A legitimate rotation, a changed endpoint or an unwanted key can all produce a difference. Confirm the expected key through an independent channel before accepting it. Hashed host fields are opaque here: only identical recorded identifiers can be matched, and the tool does not recover their hostnames.

      Questions about Known-Hosts Change Comparer

      Does a change mean an attack?

      No. It identifies a change in the supplied pins and requires independent confirmation.

      Can hashed hostnames be recovered?

      No. They are compared opaquely without revealing their original names.

      Are records updated automatically?

      No. The page exports a review report and does not modify SSH files.

      Page updated · Project managed by Tony Hines · Report a problem with Known-Hosts Change Comparer