Why Does Resource Guru Use a 128-Bit TLS Connection Instead of a 256-Bit One?
We prefer 128-bit AES encryption instead of 256-bit because AES-128 is faster, and because there is no effective increase in security by increasing to 256-bit, even when considering quantum threats. The chance of a successful attack on either AES-128 or AES-256 are both effectively zero. We’re not alone, the giants of the web use 128-bit.
Google
YouTube
Amazon
X (formerly Twitter)
We also accept AES-256 and ChaCha20 encryption standards over TLS v1.2 or v1.3, if your browser or HTTP client negotiates it.
If you’re using Chrome when you’re on any of the sites above, you can see your 128-bit connection to the site by opening the Security tab of Developer Tools (View Menu > Developer > Developer Tools), where it lists “The connection to this site is encrypted and authenticated using … AES_128 …”
ChatGPT and Grok provide further information about encryption on the web, but agree that for the web, AES-128 is generally preferred.
Learn more
Security and Data Protection
Setting Up SSO (Single Sign On)
Setting Permissions