Amazon Question?

09 Nov 2021 | US Navy Vet

[US Navy Vet]

This site can’t provide a secure connectionwww.amazon.com uses an unsupported protocol. ERR_SSL_VERSION_OR_CIPHER_MISMATCH

[US Navy Vet]

That is what I am getting when going to Amazon.

[rarestia]

What version of Windows are you using? What browser?

[Harmless Teddy Bear]

Defund Commiezon.

Shop elsewhere.

[qwerty1234]

You sure you are not going to a spoofed site? It is working fine for me.

[rarestia]

A quick scan of the site shows that they’re only using TLS1.0 with very specific ciphers. If you’re using an older operating system or an older browser, it’s possible your system doesn’t support the newer ciphers:

443/tcp open https
| ssl-cert: Subject: commonName=*.peg.a2z.com
| Subject Alternative Name: DNS:amazon.co.uk, DNS:uedata.amazon.co.uk, DNS:www.amazon.co.uk, DNS:origin-www.amazon.co.uk, DNS:*.peg.a2z.com, DNS:amazon.com, DNS:amzn.com, DNS:uedata.amazon.com, DNS:us.amazon.com, DNS:www.amazon.com, DNS:www.amzn.com, DNS:corporate.amazon.com, DNS:buybox.amazon.com, DNS:iphone.amazon.com, DNS:yp.amazon.com, DNS:home.amazon.com, DNS:origin-www.amazon.com, DNS:origin2-www.amazon.com, DNS:buckeye-retail-website.amazon.com, DNS:huddles.amazon.com, DNS:amazon.de, DNS:www.amazon.de, DNS:origin-www.amazon.de, DNS:amazon.co.jp, DNS:amazon.jp, DNS:www.amazon.jp, DNS:www.amazon.co.jp, DNS:origin-www.amazon.co.jp, DNS:*.aa.peg.a2z.com, DNS:*.ab.peg.a2z.com, DNS:*.ac.peg.a2z.com, DNS:origin-www.amazon.com.au, DNS:www.amazon.com.au, DNS:*.bz.peg.a2z.com, DNS:amazon.com.au, DNS:origin2-www.amazon.co.jp
| Issuer: commonName=DigiCert Global CA G2/organizationName=DigiCert Inc/countryName=US
| Public Key type: rsa
| Public Key bits: 2048
| Signature Algorithm: sha256WithRSAEncryption
| Not valid before: 2021-10-06T00:00:00
| Not valid after: 2022-09-19T23:59:59
| MD5: 43af a8e9 6cda 9c08 f1a5 9dfa 269d 67f7
| SHA-1: 0804 0755 c8b6 852a 5db9 45a2 b380 5711 11de fd2d
| ssl-enum-ciphers:
| TLSv1.0:
| ciphers:
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (secp256r1) - A
| TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
| compressors:
| NULL
| cipher preference: server
| TLSv1.1:
| ciphers:
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (secp256r1) - A
| TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
| compressors:
| NULL
| cipher preference: server
| TLSv1.2:
| ciphers:
| TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (secp256r1) - A
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (secp256r1) - A
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (secp256r1) - A
| TLS_RSA_WITH_AES_128_GCM_SHA256 (rsa 2048) - A
| TLS_RSA_WITH_AES_128_CBC_SHA256 (rsa 2048) - A
| TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
| compressors:
| NULL
| cipher preference: server
|_ least strength: A

[cgbg]

I am getting “provide proof of vaccination before proceeding”....

;-)

[Pollard]

Amazon is for researching and reading reviews. Then you can try to buy the same thing from the manufacturer’s/publisher’s website or buy on ebay from someone who’s in a red state.

[PROCON]

I’m on a Brave browser and Amazon is working fine for me.

[Grampa Dave]

No problem with 3 internet providers/browsers.

[mass55th]

I use Macs, and when I have a problem with a website, I delete the cookies in my cache for that site, and then try the page again. I’m on Safari, and Amazon is working fine for me.

[Chad C. Mulligan]

FWIW I’m running XT-Pro (Service Pack 2) with Firefox 52. No problems with Amazon.

I can’t ever remember getting a product I found on Amazon at a better price/delivery. I use Amazon a LOT, because I’m mobility handicapped and thus cannot shop in brick-and-mortar stores. Avoiding Amazon would be massively counterproductive, and nobody, least of Bezos wouldn’t notice if I stopped buying. Unlike evilBay, I’ve never had a problem with Amazon that wasn’t resolved to my complete satisfaction.

[Myrddin]

Last year a release of Firefox required TLS 1.3 or an SSL connection could not be completed. Lots of the web developers at my company had an overnight problem. The solution was to set the options on Firefox to use TLS 1.2 and allow permissive downgrade. That relieved the immediate pain. It took time to upgrade the server side to support the TLS 1.3 that that browser was demanding.

See the link for details on how to set the acceptable TLS ranges.