Update:

There are now Foxbleed and Chromebleed extensions to reveal website vulnerability:

http://www.thewindowsclub.com/browser-extensions-protect-heartbleed

I am using the  one for Chrome. In the 12 sites I visit daily, only one hasn't fixed it. And it is a small site, and I was a bit surprised.  I also read somewhere (could be cnet) that the *fix* really might not fix it all. 

Not surprising about the small site. You should probably email the webmaster of that site (and then change your password and not logon again until it's fixed).

I think you meant this piece:

http://www.cnet.com/news/akamai-heartbleed-patch-not-a-fix-after-all/

"The crux of the issue, Pinckaers argues, is that while Akamai protects three critical values in an RSA key -- a long, algorithm-created string of numbers designed to create an encrypted connection -- three other values, known as intermediate extra values, are accessible because they weren't "stored in the secure memory area."

"As the...values were not stored in the secure memory area, the possibility exists that these critical values for the SSL keys could have been exposed to an adversary exploiting the Heartbleed vulnerability," Akamai's Ellis said. "Given any CRT value, it is possible to calculate all 6 critical values."

Akamai is now heading back to the drawing board. Ellis says that his company has already started rotating SSL certificates that are vulnerable to protect its customers. Ellis says that some certificates will rotate quickly, while others will take a bit longer."

 

All is not well in internet land.

I also have the one for Chrome.