DKIM ArchiveContribute
This page lets you contribute to the DKIM Archive site, part of the Proof of Email project.
You can contribute to the project by uploading domains and selectors from your own Gmail account or from a TSV file. The data will be used to build the archive of current and historical DKIM records.
Ways to contribute to the archive:
Upload from Gmail
To upload directly from your Gmail account, visit the Upload from Gmail page.
When you sign in with your Gmail account and press Start, the site will extract the DKIM-Signature field from each email message in your Gmail account. A signature can look something like this:
DKIM-Signature: v=1; a=rsa-sha256; d=example.net; s=brisbane; c=relaxed/simple; q=dns/txt; i=foo@eng.example.net; t=1117574938; x=1118006938; l=200; h=from:to:subject:date:keywords:keywords; z=From:foo@eng.example.net|To:joe@example.com| Subject:demo=20run|Date:July=205,=202005=203:44:08=20PM=20-0700; bh=MTIzNDU2Nzg5MDEyMzQ1Njc4OTAxMjM0NTY3ODkwMTI=; b=dzdVyOfAKCdLXdJOc9G2q8LoXSlEniSbav+yuU4zGeeruD00lszZ VoG4ZHRNiYzRIn the example above, the domain is example.net and the selector is brisbane. These are the values that will be extracted and uploaded to the archive.
Upload from TSV file
To upload from a file created from an exported archive from any email provider (including Gmail), visit the Upload from TSV file page.
When you upload from a TSV file, the domain and selector pairs are taken directly from the file and uploaded to the archive.
Use the API
You can contribute to the archive by using the API. You find the API specification and can try out the endpoints in the API Explorer.
Privacy and security
Read the Privacy policy
Disclosure regarding Limited Use:
DKIM Archive's use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy, including the Limited Use requirements.