Daily reminder that if you fail at least 1 of these tests then you are fully exposed to the botnet

>fully exposed to the botnet
>links cloudflare

Attached: 1567304042946.jpg (598x331, 16K)

>using a botnet to check if you're exposed to the botnet
>ishiggydiggy

Attached: ishiggydiggyUsagi.jpg (335x329, 59K)

>Using 1.1.1.1 to get away from the botnet
user, I...

ESNI only works with cloudflare at the moment
Non CF sites still use plaintext SNI because no one else supports it

It has happened, multiple times in my country, and is still happening.
Jow Forums, TPB, and nyaa.si are blocked in Australia.

>using JewFlare to escape the botnet
out of the frying pan and into the fire

Just change your DNS you monkey

reminder that this very website runs Cloudflare
you might as well use their DNS to visit it

Those people don't use this site

>Australians don't use this site
if only

>set up Nightly and try this shit
>pass test
>nobody is listening
>try and access Sankaku without a VPN
>THIS WEBSITE IS BLOCKED

What's the fucking point?

>try using 1.1.1.1 for fast & secure DNS.
>try using our botnet DNS, it's secure, just trust us
kys OP

cloudflare is an NSA honeypot and organized crime racket

>your resolver validates
Why do I give a fuck, isn't the whole point that you can't trust your resolver?

It's a bit sad. NSS is the only library supporting it so far thanks to Firefox, but nobody is using that on the server side, and nothing else implements it because it's still a draft standard (which has incompatible revisions) – the best thing I've found so far is some fork of OpenSSL, which comes with a proof-of-concept curl fork supporting ESNI.
github.com/ctz/rustls/issues/199
github.com/openssl/openssl/issues/7482#issuecomment-527881762
Also I assume that the requirement to publish non-ephemeral public encryption keys in DNS (which already needs to be encrypted anyway so domain names don't leak through it instead, how convenient that Cloudflare also runs a DoH resolver!) and to use an IP with lots of different domains for optimal deniability doesn't make it any more popular, either.

Icecat android failed all 3 for me

>your browser support an unfinished draft of a not-yet-done standard
>you're not fully exposed to the botnet if your DNS server is cloudflare ;^)
sure

hi

Attached: file.png (1283x1007, 72K)

>trusting a botnet
ISHYGDDT

And then you don't pass the test though.

>nyaa.si
why

I have network.trr.mode at (5) and don't pass any of those except for the TLS 1.3. I'd rather not use botnet features than being "secure".

Hello, are you using IE11?

Attached: poop.png (1440x848, 208K)

i am using iridium browser, sir.

I would think a Chromium based browser would pass all 4 tests. interdasting

>use our botnet 1.1.1.1 dns goy
LOL

Cloudflare is botnet anyways, use OpenNIC

Ohhh...
Oh nooo...

Attached: 1559425557436.png (741x505, 82K)

> exposed to the botnet
> a test that's designed to make morons use 1.1.1.1 and install google chrome
consider going to your tallest building op, climb up to the top of it and jump, you sad fucking shill. make sure to do some flips and shit on the way down. what a useless cunt.

hooray for non-repudiation

>not using 8.8.8.8
are you even trying

Cloudflare is botnet, you should fail the first test if you care about privacy.
Run your own DNS server.

I have to change my dns to come here

only DoH failed because unbound hasnt implemented it yet, and i dont want to set up dns-proxy or some other shit
>secure dns (?)
fuck you cloudfare, i'm not telling shit

Attached: Screenshot_20190919_182906.jpg (1177x319, 78K)

>Sir please contact us your DNS provider for try usings 1.1.1.1 very needful DNS.

u forgot them britbongs