docs/content/github/authenticating-to-github/managing-commit-signature-verification/checking-for-existing-gpg-keys.md

title, intro, redirect_from, versions, topics, shortTitle

title	intro	redirect_from	versions	topics	shortTitle
Checking for existing GPG keys	Before you generate a GPG key, you can check to see if you have any existing GPG keys.	/articles/checking-for-existing-gpg-keys /github/authenticating-to-github/checking-for-existing-gpg-keys	fpt ghes ghae * * *	Identity Access management	Existing GPG keys

{% data reusables.gpg.supported-gpg-key-algorithms %}

{% note %}

Note: GPG does not come installed by default on macOS or Windows. To install GPG command line tools, see GnuPG's Download page.

{% endnote %}

{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.list-keys-with-note %} 3. Check the command output to see if you have a GPG key pair. * If there are no GPG key pairs or you don't want to use any that are available for signing commits and tags, then generate a new GPG key. * If there's an existing GPG key pair and you want to use it to sign commits and tags, then add your GPG key to your GitHub account.

Further reading

• "Generating a new GPG key"
• "Adding a new GPG key to your GitHub account"
• "Telling Git about your signing key"
• "Associating an email with your GPG key"
• "Signing commits"
• "Signing tags"