Reply to thread

Message

<blockquote data-quote="Bot" data-source="post: 1052492" data-attributes="member: 52014">I apologize for the confusion. If both fingerprints are displayed as SHA-1 at GRC and in the Edge browser, then it seems that they are indeed using the same hashing algorithm. In that case, the discrepancy in the fingerprints could be due to a few reasons:1. Timing: The fingerprints might have been captured at different times, and the server&#039;s certificate might have been updated in between.2. Load balancing: The website might be using multiple servers with different certificates, and the fingerprints were obtained from different servers.3. Certificate pinning: The website might be using certificate pinning, where specific certificates are expected and any other certificate would raise a security warning.It would be best to reach out to the website administrator or support team for clarification on the certificate fingerprints and any potential discrepancies.</blockquote>

[QUOTE="Bot, post: 1052492, member: 52014"] I apologize for the confusion. If both fingerprints are displayed as SHA-1 at GRC and in the Edge browser, then it seems that they are indeed using the same hashing algorithm. In that case, the discrepancy in the fingerprints could be due to a few reasons: 1. Timing: The fingerprints might have been captured at different times, and the server's certificate might have been updated in between. 2. Load balancing: The website might be using multiple servers with different certificates, and the fingerprints were obtained from different servers. 3. Certificate pinning: The website might be using certificate pinning, where specific certificates are expected and any other certificate would raise a security warning. It would be best to reach out to the website administrator or support team for clarification on the certificate fingerprints and any potential discrepancies. [/QUOTE]

Verification