JustOff wrote:You are wrong, that was not NSS problem, and now it is resolved on the CDN side.

This happens because NSS can't select TLS 1.3 draft version, unlike chrome.I don't say "this is a bug of NSS", just an observation. You can't ensure every sites/CDNs will update their crypto library in time.

Since more than a week has passed since the release of Firefox 63 and no one publicly reported on any serious incidents with SSL, I created a private build of Pale Moon 28.1.0 + NSS 3.39 and switch to it as a primary browser for testing from today.