HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
pirate
sites-using-cloudflare
Security & Privacy2017–2017
pirate / sites-using-cloudflare · Archived

sites-using-cloudflare

:broken_heart: Archived list of domains using Cloudflare DNS at the time of the CloudBleed announcement.

7Distinct people
26Mentions
0Explicit recommenders
1.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

:broken_heart: Archived list of domains using Cloudflare DNS at the time of the CloudBleed announcement.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval26 dated mentions

Observed mentions: 2017-02-24 02:02:44 UTC to 2017-02-25 14:39:03 UTC.

0369122017-02-24 00:00:00 UTC to 2017-02-24 03:00:00 UTC (exclusive): 12 mentions; 1 submissions, 11 commentsFeb 24, 00:002017-02-24 03:00:00 UTC to 2017-02-24 06:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2017-02-24 06:00:00 UTC to 2017-02-24 09:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2017-02-24 09:00:00 UTC to 2017-02-24 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-24 12:00:00 UTC to 2017-02-24 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-24 15:00:00 UTC to 2017-02-24 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-24 18:00:00 UTC to 2017-02-24 21:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsFeb 24, 18:002017-02-24 21:00:00 UTC to 2017-02-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-25 00:00:00 UTC to 2017-02-25 03:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-02-25 03:00:00 UTC to 2017-02-25 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-02-25 06:00:00 UTC to 2017-02-25 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-25 09:00:00 UTC to 2017-02-25 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-25 12:00:00 UTC to 2017-02-25 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 25, 12:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 24, 00:002017-02-24 00:00:00 UTC2017-02-24 03:00:00 UTC12111
Feb 24, 03:002017-02-24 03:00:00 UTC2017-02-24 06:00:00 UTC707
Feb 24, 06:002017-02-24 06:00:00 UTC2017-02-24 09:00:00 UTC211
Feb 24, 09:002017-02-24 09:00:00 UTC2017-02-24 12:00:00 UTC000
Feb 24, 12:002017-02-24 12:00:00 UTC2017-02-24 15:00:00 UTC000
Feb 24, 15:002017-02-24 15:00:00 UTC2017-02-24 18:00:00 UTC000
Feb 24, 18:002017-02-24 18:00:00 UTC2017-02-24 21:00:00 UTC202
Feb 24, 21:002017-02-24 21:00:00 UTC2017-02-25 00:00:00 UTC000
Feb 25, 00:002017-02-25 00:00:00 UTC2017-02-25 03:00:00 UTC101
Feb 25, 03:002017-02-25 03:00:00 UTC2017-02-25 06:00:00 UTC101
Feb 25, 06:002017-02-25 06:00:00 UTC2017-02-25 09:00:00 UTC000
Feb 25, 09:002017-02-25 09:00:00 UTC2017-02-25 12:00:00 UTC000
Feb 25, 12:002017-02-25 12:00:00 UTC2017-02-25 15:00:00 UTC101

What Hacker News says

26 sources
"...the leaked information is from any website which was using the service..." Potentially, yes. Not just HTTPS, but those are obviously the more worrying cases. It's not possible to know the totality of information that has been leaked, though efforts are being made to try and list affected / potentially affected sites.[1] My advice would be: For any sites you're worried about (ie hosted on CF and you have an account), log out of all sessions on all devices, and reset your password. Don't share passwords between sites either; if you're using 1password now, you can use unique & complex passwords for everything. [1] eg https://github.com/pirate/sites-using-cloudflare
In Ask HN: What are the implications of CloudFlare leak?
Just received an email from Glidera, a Bitcoin exchange. This is the first service to ask me to reset my password. I wonder why Uber, NameCheap, FitBit, and many others have yet to warn their users? Is Cloudflare downplaying this? > Hi [Username], > A bug was recently discovered with Cloudflare, which Glidera and many other websites use for DoS protection and other services. Due to the nature of the bug, we recommend as a precaution that you change your Glidera security credentials: > Change your password > Change your two-factor authentication > You should similarly change your security credentials for other websites that use Cloudflare (see the link below for a list of possibly affected sites). If you are using the same password for multiple sites, you should change this immediately so that you have a unique password for each si
Read the rest
te. And you should enable two-factor authentication for every site that supports it. > The Cloudflare bug has now been fixed, but it caused sensitive data like passwords to be leaked during a very small percentage of HTTP requests. The peak period of leakage is thought to have occurred between Feb 13 and Feb 18 when about 0.00003% of HTTP requests were affected. Although the rate of leakage was low, the information that might have been leaked could be very sensitive, so it’s important that you take appropriate precautions to protect yourself. > The actual leaks are thought to have only started about 6 months ago, so two-factor authentication generated before that time are probably safe, but we recommend changing them anyway because the vulnerability potentially existed for years. > Please note that this bug does NOT mean that Glidera itself has been hacked or breached, but since individual security credentials may have been leaked some individual accounts could be vulnerable and everyone should change their credentials as a safeguard. > Here are some links for further reading on the Cloudflare bug: > TechCrunch article: https://techcrunch.com/2017/02/23/major-cloudflare-bug-leake... > List of sites possibly affected by the bug: https://github.com/pirate/sites-using-cloudflare/blob/master... > If you have any questions or concerns in response to this email, please contact support at: support@glidera.io
In List of Sites Affected by Cloudflare's HTTPS Traffic Leak

Showing the 15 most recent of 26 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.