.
//
// Also add information on how to contact you by electronic and paper mail.
//
// If your software can interact with users remotely through a computer network,
// you should also make sure that it provides a way for users to get its source.
// For example, if your program is a web application, its interface could display
// a "Source" link that leads users to an archive of the code. There are many
// ways you could offer source, and different solutions will be better for different
// programs; see section 13 for the specific requirements.
//
// You should also get your employer (if you work as a programmer) or school,
// if any, to sign a "copyright disclaimer" for the program, if necessary. For
// more information on this, and how to apply and follow the GNU AGPL, see .
?>
Let's add a decentralized DNS proof to your OpenPGP keys.
Update DNS records for your website
Add the following TXT record to the DNS records of the (sub)domain you want to prove control over (make sure to replace FINGERPRINT):
openpgp4fpr:FINGERPRINT
No specific TTL value is required.
Update the PGP key
First, edit the key (make sure to replace FINGERPRINT):
gpg --edit-key FINGERPRINT
Add a new notation:
notation
Enter the notation (make sure to replace DOMAIN, don't include https://):
proof@metacode.biz=dns:DOMAIN?type=TXT
Save the key:
save
Upload the key to WKD or use the following command to upload the key to keys.openpgp.org (make sure to replace FINGERPRINT):
gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT
And you're done! Reload your profile page, it should now show a verified domain.