Item logo image for Cloudbleed Indicator

Cloudbleed Indicator

Item media 2 screenshot
Item media 3 screenshot
Item media 1 screenshot
Item media 2 screenshot
Item media 3 screenshot
Item media 1 screenshot
Item media 2 screenshot
Item media 1 screenshot
Item media 2 screenshot
Item media 3 screenshot

Overview

Test any page and see if it is using CloudFlare or not. Inspired by Feb 2017 Cloudbleed security incident.

Featured at Product Hunt: https://www.producthunt.com/posts/cloudbleed-indicator-for-chrome Cloudbleed Indicator does not fix the issue, it recognises it using Google Public DNS (DNS-over-HTTPS). If the cloud icon is bleeding, you might consider: - changing your password, - using 2-step verification (if available), - leaving the site altogether. Cloudbleed (also known as CloudLeak and CloudFlare Bug) is a security bug discovered on February 17, 2017 affecting Cloudflare's reverse proxies, which caused their edge servers to run past the end of a buffer and return memory that contained private information such as HTTP cookies, authentication tokens, HTTP POST bodies, and other sensitive data. Some of this data was cached by search engines.

4.3 out of 56 ratings

Google doesn't verify reviews. Learn more about results and reviews.

Review's profile picture

Ben LeeFeb 27, 2017

This is not a CloudBleed indicator, it's a CloudFlare indicator. CloudBleed only impacted very few sites and people. This is just scaremongering.

1 out of 3 found this helpful
Replier's profile picture

Stas KuleshDeveloperMar 1, 2017

Isn't some of the data may still be available via search engine cached versions? Google may have cleared that up, but there are plenty of alternative ones like Yandex.ru. Please correct me if I'm wrong. I'm thinking in terms of insurance-like premiums. The CF system had 1 incident, by definition (incidents/year) they're less reliable, than others, that did not have anything of that sort happening recently. CB incident is not adding more credibility to CF, that's for sure. Some of the US banks have been hit hard by 2008, and I, as a new customer, would probably prefer the ones that did not get involved too much in junk bonds bonanza. To the existing customers, the extension suggests: change your password, use 2-step verification (which is almost always a good idea), to the newcomers – these guys are using the software, that is probably less reliable now because of CB. Scary? I don't know. Rational But I see what you mean now, thanks for sharing.

Review's profile picture

David KravitzFeb 27, 2017

I do feel safe now

1 out of 3 found this helpful

Details

  • Version
    0.9
  • Updated
    February 27, 2017
  • Offered by
    Stas Kulesh
  • Size
    14.23KiB
  • Languages
    English
  • Developer
    Sliday Limited
    12C Cranbrook Place Auckland 1071 NZ
    Email
    stas@sliday.com
  • Trader
    This developer has identified itself as a trader per the definition from the European Union.

Privacy

The developer has not provided any information about the collection or usage of your data. To learn more, see the developer’s privacy policy.

Support

Google apps