- Newest
- Most votes
- Most comments
I haven't seen SSHFP records used widely, but they're used to publish the public SSH keys used as fingerprints to verify that when you're connecting to an SSH host, a man-in-the-middle attack will be exposed by the bad actor not having the private encryption key matching the public fingerprint. That prevents them from impersonating the legitimate SSH/SFTP/etc. server.
If you aren't using SSH to connect to the hosting provider and only using them for email, the SSHFP record shouldn't be needed.
Route53 does not support SSHFP records. The record types that are supported by Route53 are documented here: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/ResourceRecordTypes.html
You can always reach out to AWS, through your account team contacts, and ask them about considering this as feature request.
Then as Leo mentioned, you do not need to add them if you do not want too, they are not widely used.
Relevant content
- asked 2 years ago
- asked 3 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Thanks for the specific answer.