Choose your Android keystore (.jks / .keystore) or a .p12 / .pfx file and see every key inside it - the alias, the owner, the validity dates and the SHA-1 and SHA-256 fingerprints that Firebase and Google services ask for. No Android Studio and no command line needed.
The fingerprint belongs to the key (its certificate) inside the keystore, not to the file. A keystore can hold several keys, each with its own alias and its own fingerprints - the tool lists all of them. A copy of the same keystore always gives the same fingerprints.
In the old JKS format the certificates are stored in plain form, only the private keys are protected, so the fingerprints can be read without the password. In a PKCS12 (.p12 / .pfx) file the certificates are encrypted too, so the password is needed. If you type a password for a .jks, the tool checks that it is right.
No. The tool only reads the certificates. It never opens or decrypts the private key, and the file and the password stay inside your browser.
Google Play requires the signing key of a new app to be valid until after 22 October 2033. A key made with a short validity (for example 25 years from today is fine, 1 year is not) would be rejected, so the tool warns you.
If you also choose an APK, the tool compares its signing certificate with every key in the keystore. A match tells you that this keystore (and this alias) is the one that signed that APK.
JKS (.jks, .keystore), JCEKS, and PKCS12 (.p12, .pfx) created by keytool, OpenSSL or Android Studio. A PKCS12 file that uses the old Triple-DES encryption for its certificates (some Windows exports) is not supported yet - convert it with keytool or openssl first.