Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)
7 years ago
I noticed I couldn't connect to archive.is, eventually I figured out it was an issue with cloudflare DNS, 1.1.1.1. Checking nslookup confirms this:
nslookup archive.is 1.1.1.1 Server: 1.1.1.1 Address: 1.1.1.1#53
Non-authoritative answer: Name: archive.is Address: 127.0.0.4
nslookup archive.is 8.8.8.8 Server: 8.8.8.8 Address: 8.8.8.8#53
Non-authoritative answer: Name: archive.is Address: 94.16.117.236
Cloudflare is returning a localhost address which prevents you from accessing the website.
We don’t block archive.is or any other domain via 1.1.1.1. Doing so, we believe, would violate the integrity of DNS and the privacy and security promises we made to our users when we launched the service.
Archive.is’s authoritative DNS servers return bad results to 1.1.1.1 when we query them. I’ve proposed we just fix it on our end but our team, quite rightly, said that too would violate the integrity of DNS and the privacy and security promises we made to our users when we launched the service.
The archive.is owner has explained that he returns bad results to us because we don’t pass along the EDNS subnet information. This information leaks information about a requester’s IP and, in turn, sacrifices the privacy of users. This is especially problematic as we work to encrypt more DNS traffic since the request from Resolver to Authoritative DNS is typically unencrypted. We’re aware of real world examples where nationstate actors have monitored EDNS subnet information to track individuals, which was part of the motivation for the privacy and security policies of 1.1.1.1.
EDNS IP subsets can be used to better geolocate responses for services that use DNS-based load balancing. However, 1.1.1.1 is delivered across Cloudflare’s entire network that today spans 180 cities. We publish the geolocation information of the IPs that we query from. That allows any network with less density than we have to properly return DNS-targeted results. For a relatively small operator like archive.is, there would be no loss in geo load balancing fidelity relying on the location of the Cloudflare PoP in lieu of EDNS IP subnets.
We are working with the small number of networks with a higher network/ISP density than Cloudflare (e.g., Netflix, Facebook, Google/YouTube) to come up with an EDNS IP Subnet alternative that gets them the information they need for geolocation targeting without risking user privacy and security. Those conversations have been productive and are ongoing. If archive.is has suggestions along these lines, we’d be happy to consider them.
Honestly, Cloudflare choosing not to hastily slap a band-aid on a problem like this just makes me feel more compelled to continue using 1.1.1.1.
I hesitate to compare this to Apple calling themselves “courageous” when removing the headphone jack, but in this case, I think the word is appropriate. I’ll happily stand behind you guys if you take some PR hits while forcing the rest of the industry to make DNS safer – since it is understandable, admittedly, for users to conclude that “Cloudflare is blocking websites, sound the alarms!” at first glance.
For the moment, I also do trust CloudFlare's intentions, but it's wrong to classify this as some kind of stoic resolve in not "slapping a band-aid on a problem" since that's exactly what they did after their business decision about not responding to "any" queries.
3 replies →
Please note that incentive to "hastily slap a band-aid" did appear, but was overcome by the team. At least, they deserve praise for honesty.
Apple's move is solely based on greed. Sell people a product they eill easily lose as well as having a limited lifetime. Easy money.
Say you remove/don't proxy the ECS information, and I get some generic, non-geo-location aware response back. In the majority of cases, wouldn't my next step be to open a TCP connection to the IP in the response, and immediately leak my full IP address to the other end? While I get (and appreciate!) the concern for the user's privacy, I'm having a hard time seeing what practical effect not proxying the subnet the user is on has?
(This is not meant to suggest that archive.is's DNS response is appropriate, or that CF's setup is inappropriate.)
(Just to check my understanding of ECS: it's an extension to DNS that sends the user's subnet in the request, and gets relayed with the request, s.t. an authoritative server can respond with a geo-location appropriate response/IP.)
> Say you remove/don't proxy the ECS information, and I get some generic, non-geo-location aware response back. In the majority of cases, wouldn't my next step be to open a TCP connection to the IP in the response, and immediately leak my full IP address to the other end?
That assumes that the nameserver and the actual server are run by the same party which quite often is not the case.
3 replies →
Alternatively:
Cloudflare simply is making a subversive play against their competitor CDNs. Client subnet of a DNS request is used for initial rough mapping by Cloudflare competitors such as Akamai (definitely) and I believe Fastly ( and probably others) . Stripping it easily adds at least a few milliseconds to the time to first byte and most likely results a request re-routing on the second or third request.
After all, no other CDN is operating a well used public resolver.
As this is related to CDN, I am gonna leave it here.
The irony is one.one.one.one is marketed as getaway to faster internet, while making CDNs that use GeoDNS slower.
All it takes is a bad route to a far away cloudflare POP to make your internet really slower. Case in point. [1]
I really don't find why no EDNS is considered private, as it only sends the IP subnet.[2] And on IPv6 the IP is far more protected.
If you care that much about privacy, you should be using a VPN.
[1] https://pastebin.com/raw/QnbWXU1a
[2] https://tools.ietf.org/html/rfc7871#section-11.1
1 reply →
Google has its own public DNS and CDN, I'm pretty sure that counts.
2 replies →
Thank you for your comment.
Since HTTPS traffic already reveals communicating IPs to nation-state actors, could you clarify what attack vector removing user IP info from authoritative DNS queries protects against?
In what way does Cloudflare publish its PoP geolocation? Is it a Cloudflare-specific API? Why not fake EDNS subnet info by providing the PoP’s?
I notice of course that Google, Facebook, and Netflix still work on 1.1.1.1. Does this mean they’re currently using Cloudflare PoP geolocation in lieu of EDNS subnet information?
Its preventing the DNS authority to know the IP of who is making the request.
CloudFlare decided its DNS should be the authority to the end user and Archive.is's DNS should be the authority only to CloudFlare. CloudFlare is breaking the bond between the end user and the Service provider.
What CloudFlare is doing is centralizing authority to itself rather allowing authority to be distributed to all owners of the domains as intended. An argument can be made that by using 1.1.1.1 you are granting CF permission to act in this role - some users may even prefer it.
3 replies →
An example of something that Cloudflare's approach provides some protection from: http://dnscookie.com/
> We publish the geolocation information of the IPs that we query from. That allows any network with less density than we have to properly return DNS-targeted results.
The operator of archive.is claims that they suffer from a "massive mismatch" between those query IPs and actual traffic. Any idea why? [Is that claim wrong? Is archive.is to blame? Is cloudflare to blame? Are ISPs badly routing the DNS queries?]
Do you have stats on how well the geolocation works in practice?
Well no, CloudFlare doesn't get to talk about not "violating the integrity of DNS" after you stopped responding to "any" queries in violation of the standard. You started by doing your own thing and then proposed a change to the standard to fit your business decision. [0]
[0] https://www.rfc-editor.org/info/rfc8482
There's a difference between changing results (or adding) and not supporting a feature that is dangerous and rarely used. Kind-of like banning handguns vs. providing unknownly modified guns.
3 replies →
They also stopped responding to all DNS queries for some neonazi asshats because of public pressure and politics. They're definitely jerks but they still should be treated like any other customer unless they're actively breaking the law.
Thanks for the detailed response! I think your team is handling this the right way.
@eastdakota what about just failing without response on archive.is calls so the second resolver address configured in the client will be used? I understand this is also a DNS integrity violation, however the result for the end user would be either the same if they don’t have a second resolver configured or enhanced if they do.
The current effect is I stop using 1.1.1.1 when I need archive.is (often) and set it back the next time I’m messing with my network settings.
DNS either has integrity or it doesn’t. We get a response from an Authoritative server and, as a Resolver, we believe our responsibility is to return it. If we start making exceptions because of bad PR, how can you trust us to do the right thing when the stakes are even higher (e.g., nationstate pressure)?
As an aside, I used to think that when Emerson said that “a foolish consistency is the hobgoblin of little minds” he meant that we were foolish to try and be consistent. Increasingly I wonder if instead he meant that when you’re trying to reason with people who may not have the same detailed knowledge of a problem as you, there’s an enhanced importance to being consistent. Unfortunately, most policy makers globally don’t have a detailed understanding of how technical systems like DNS work, so we think it’s especially important we be consistent.
3 replies →
If you're going to that much trouble I suggest you just hardcode an IP address for archive.is into /etc/hosts. I've only had to change it once in the whole time I've used Cloudflare DNS (i.e. since the first day it was public).
If you use dnsmasq, you can special case archive.is to not be resolved via 1.1.1.1.
Also: it'd be nice if CloudFlare made a secondary DNS resolver (1.1.2.2?) that didn't pass along EDNS information, as a backup for websites like archive.is (and for anyone who cares about privacy).
3 replies →
I just added an entry for archive.is in my etc/hosts.
5 replies →
If you're for integrity of DNS, why did you suspend the free speech of the admittedly bigoted, hateful neonazis on dailystormer?
https://blog.cloudflare.com/why-we-terminated-daily-stormer/
"Earlier today, Cloudflare terminated the account of the Daily Stormer. We've stopped proxying their traffic and stopped answering DNS requests for their sites. We've taken measures to ensure that they cannot sign up for Cloudflare's services ever again."
I'll keep using non-logging, encrypted OpenNIC servers, since you seem to selectively censor instead of only blocking terrorists and cp.
How does doing this censor them?
The Daily Stormer is free to get their business elsewhere and it's still up on the internet. Cloudflare didn't want to be associated to this kind of content, and thus terminated their business relation.
We don't NEED Cloudflare to keep the internet integrity (if we did, it will go pretty badly...) but we do need DNS to keep the internet integrity.
> I'll keep using non-logging, encrypted OpenNIC servers, since you seem to selectively censor instead of only blocking terrorists and cp.
Why are you censoring Cloudflare? /s
I don't think this argument is well stated, so I'll give it a shot.
CloudFlare is very basic infrastructure and there are a handful of companies providing such infrastructure, thus a group can be effectively deleted from the Internet if these companies decide or are pressured to do so. (Example of pressuring: Patreon dropped some accounts at the behest of Mastercard.)
So maybe the real question is, "does this notion of the integrity of DNS extend to other basic infrastructure services?"
Why not just send the subnet of the machine at cloudflare doing the querying?
The full IP of the Cloudflare resolver doing the recursive resolution is already provided to the authoritative server, as the source IP for the DNS query traffic.
7 replies →
Could you use your own subnet in the EDNS that matches client's country or could you let user configure what data would be shared?
Ongoing work with big companies to replace existing technologies don't convince me. Though, neither does whining when the authoritative nameserver itself is returning bogus responses.
The experience for the user is that the page just keeps loading indefinitely, while showing a blank page. Is there nothing Cloudflare could do to inform the browser about the situation, so that the browser can show some kind of a message to the user? As it stands, to the user it just looks like their connection died.
I don't see what they can do, short of sending fake DNS replies with their own webserver IPs, which is worse for the integrity of DNS.
2 replies →
Awesome response! Is there already a blog post on this?
Such a post might A) get better SEO than an HN thread for 'cannot access archive.is [or ...]' and B) help change its behaviour.
If the govt of your jurisdiction (American I assume?) commanded you to censor a certain domain or block of IPs with a court order, what exactly happens? I'm not sure if this has been done on the DNS level before but do you guys have a plan in case it ever does happen?
Jurisdiction would include every place where they have a business presence. Their page https://www.cloudflare.com/en-au/about-overview/ lists quite a few international phone numbers, which may or may not correspond with offices and subsidiary companies in those locations.
I assume they'd just have to go along with such legal demands, or withdraw from the relevant country, unless the penalty for not complying was very small.
It will probably become an issue some day. In Australia, for example, courts can issue DNS bans of particular sites to individual ISPs. You can avoid these bans entirely by using a service like Cloudfare DNS.
Or you know you Piss off CloudFare CEO and he directs them to censor a site... Which has happened in the past
6 replies →
Are there any other known sites that don't work with 1.1.1.1 but work fine on other resolvers?
Typically, if you experience that, it’s because DNSSEC fails. 1.1.1.1 enforces DNSSEC. As does 8.8.8.8 in most, but not all, cases. Many other DNS resolvers do not enforce DNSSEC. Archive.is (and its directly affiliated sites) are the only exception like this I am aware of. And, to be clear, as a policy the 1.1.1.1 DNS does not block any sites from resolution.
I (random HN user) happen to know of lancaster.ac.uk (there was a comment thread a while back where this was mentioned).
2 replies →
Thanks for the explanation. One more reason to keep using you instead of anything else.
tl;dr: Don't use 1.1.1.1 if you use any services that use DNS geolocation to bring you resources from the closest datacentre. These include: Office 365, Netflix, Facebook, Google services, ...
Huh, don’t see many CEOs writing and talking like this. And I don’t think a flunky wrote this.
Wow, I'm totallly not on the x company awesome today- x company terrible tomorrow with x = cloudflare but I'm impressed that you guys are doing due diligence!
archive.is is a very important tool in online extremism research and you've taken money from far-right extremists, your explanation for why it's inaccessible seems incomplete.
This is probably where I get banned from Hn but it has to be said - to posture as if you care about end users while in the same breath taking money from extremists and turning over personal identifiable information to far-right outlets like DailyStormer, is disingenuous at best and I can think of other ways to describe it which are less charitable.
You also host and protect 8chan.
https://twitter.com/ncweaver/status/1124091916520497153
https://twitter.com/klarajk/status/1122625367490146304
https://twitter.com/Riverseeker/status/1122612031234945024
https://twitter.com/slpng_giants/status/1123592717341200384
https://twitter.com/NathanBLawrence/status/10562868097418199...
https://twitter.com/NJDemocrat/status/897147112273608705
https://twitter.com/InvestMib/status/1123308004873515015
https://twitter.com/jwz/status/1124415034610860033
This is amusing, They Banned the DailyStormer which I why I will never support them. While I disagree 100% with the DailyStormer it is not up to cloudflare to decide who can and can not speak, who can and can not access the internet.
The concept of Free Speech is the most important right we have as humanity, while I may not agree with some peoples words I will fight for their right to say those words
And do not even come at me with "well they are private company" we impose all kinds of regulations on private companies when it comes to basic human rights like free speech and Free Association for example private companies can not refuse service based on race, sex, age, etc.
yet you WANT them to censor content, censor speech. You want them to apply your left authoritarian world view to legal speech, and yes everything you have cited is LEGAL SPEECH in the USA.
If there are actual threats, True Threats as defined in US law, then the police should be involved and the people arrested. If there is defamation or other illegal speech then the courts should be involved
It should NOT be the position of private companies to regulate speech online
Platform Access Is A Civil Right. https://humanevents.com/2019/05/03/platform-access-is-a-civi...
14 replies →
I think the tone of this comment as "courageous" is especially humorous coming from a throwaway account.
2 replies →
Encrypting dns is bad for end users. Please cut this shit out. You are acting like you are defending against the NSA, but in reality we will have a bunch of shitty IoT phoning data to indecipherable IP addresses without any meaningful defense of consumer privacy.
It is hostile to customers who want to troubleshoot wtf apps are doing.
Normal DNS queries aren't encrypted. It's normal queries on port 53.
Users/programs/IoT can choose to use DNS-over-TLS or DNS-over-HTTPS, but that's not Cloudflare's fault.
Nothing in his response is about encrypting DNS. Go grind your axe elsewhere.
In my country, government/ISP blocks websites and changes the DNS results of 8.8.8.8 since it is not encrypted. If ISP can create a valid certificate, that browsers trust [1], they may be able to access my Gmail or Github account.
[1] https://www.zdnet.com/article/mozilla-to-chinas-wosign-well-...
The problem is the archive.is (and other TLDs) server not returning any Good IP if the EDNS client subnet isn't present.
Would like to point out that Cloudflare's resolver is EDNS compliant, it just doesn't send the client subnet.
See: https://twitter.com/archiveis/status/1018691421182791680 (picture of tweet https://aws1.discourse-cdn.com/cloudflare/optimized/3X/8/2/8... )
Based on that tweet, the owner has a personal grudge against Cloudflare and is choosing to return bad results.
I take back every bad thing I have ever said about mailing lists - at least it was easier to follow the drama than these damn twitter links.
My issue with mailing lists is the browsing experience. It's very difficult to view conversations, especially compared to Gmail's threaded view. Seems like something an open source project could solve!
Text of tweet by @archiveis:
"Having to do" is not so direct here. Absence of EDNS and massive mismatch (not only on AS/Country, but even on the continent level) of where DNS and related HTTP requests come from causes so many troubles so I consider EDNS-less requests from Cloudflare as invalid.
For additional context, here is the Cloudflare explanation about EDNS client subnets:
> EDNS Client Subnet > >1.1.1.1 is a privacy centric resolver so it does not send any client IP information and does not send the EDNS Client Subnet Header to authoritative servers.
Cloudflare's requests are of course perfectly valid, with @archiveis actively deciding not to service them.
12 replies →
> requests come from causes so many troubles
Given they serve their pages over tor, I don't buy that explanation at all. Assuming location of client == location of CloudFlare source would give them a rough match in most cases. In tor they're almost guaranteed to be wrong.
Ah yes, the huge trouble of a website that is a few MS slower as opposed to just not working at all.
I’m not sure I see what kind of logic goes into this argument.
Furthermore let's see this report:
https://ednscomp.isc.org/ednscomp/6ed2aca587
EDNS Compliance Tester says that archive.is has some issues.
https://dnsflagday.net
> Minor problems detected! > This domain does not support latest DNS standards.
Could they send "generic" subnet or even better could they let user choose the subnet?
For those curious about what is going on here...
Cloudflare has decided for privacy reasons they will not relay eDNS0 client subnet data - which yes, can reveal a portion of the IP of the requestor - but is used by CDN services in order to provide nearest servers or (in some cases) country specific content.
My guess here is archive.is feels they have some need to restrict what content is provided to where in the world, and as a result, without ECS in the request, takes you to a cname which essentially null routes you back to your local loop interface.
Source: Founder of DNSFilter.com - we support ECS, I coded it.
>My guess here is archive.is feels they have some need to restrict what content is provided to where in the world
Couldn't that be done later, by blocking the actual HTTP TCP connections instead of blocking the DNS requests? Maybe it's an efficiency issue, that they want the higher-efficiency blocking by DNS rather than lower-efficiency blocking during HTTP TCP, but that seems a little strange to me.
This has been a known issue for a while.
Unfortunately, Archive.is has to fix it from their nameservers and we cannot do anything from our side. You can ready more about it here: https://community.cloudflare.com/t/archive-is-error-1001/182...
Disclaimer: I work at Cloudflare
The person or persons running the site have a history of very stubborn behaviour. I do appreciate the service they are running.
One time they blocked the whole Finland because the owner had problems with customs and somehow related the incident with Russia while saying Finnish gov and bur businesses can never be independent.
Archive.is is very interesting. I was checking and they block (by responding back with 127.0.0.3):
- 1.1.1.1
- Neustar DNS
- AdGuard DNS
But they don't block Quad9 or CleanBrowsing that also do not send the EDNS subnet. Very curious way of blocking itself out of the Internet. OpenDNS blocks it (sends to their block page):
https://dnsblacklist.org/?domain=archive.is
Would love to hear from someone from archive.is what is going on.
I remember reading this a while back. It sounded more that archive.is was blocking Cloudflare (or at least not supporting it): https://community.cloudflare.com/t/archive-is-error-1001/182...
Does anyone know why archive.is would block Cloudflare? Is it a technical issue, or does the owner of archive.is have some kind of grudge against them?
Cloudflare uses "privacy" and "caring about users" as excuses to sabotage competing CDNs (including whatever CDN is used by archive.is).
Most recursive DNS severs on Internet can be categorized in two groups: local DNS servers, offered by Internet providers to their users, and enormous "generic" DNS like Google's 8.8.8.8. When someone makes a DNS request to those servers, they will in turn forward it to DNS servers of web page you are requesting. Content Delivery Networks use DNS to determine, which server should serve your request: if your DNS request arrived from Africa, CDN's DNS server will return IP in Africa. Of course, _users_ don't send DNS requests to CDN's server — recursive DNS servers do. In the past almost everyone used DNS, offered by their Internet provider, — CDN's had to use GeoIP or even static lists of providers to determine origin of that request. When world-wide DNS servers like Google's 8.8.8.8 started to gain popularity, that approach was broken, so EDNS was developed.
Cloudflare is a CDN. They are selling their CDN services for money. At the same time they are encouraging end users to use free DNS server, that does not support EDNS on purpose (they admit so on their website). In effect they are creating a situation, when competing CDNs are at disadvantage and can't determine, what country user comes from. Cloudflare itself does not suffer from that disadvantage, because they control both 1.1.1.1 and DNS, used by their clients' websites.
1 reply →
Hard to tell from the outside, but archive.is did blacklist the whole of Finland a while back - due to personal grudge.
2 replies →
Looks like it's a known issue https://community.cloudflare.com/t/archive-is-error-1001/182..., yet not been fixed for at least a year
In response to that "unfixed" issue, they noted - in a timely manner, last year - that archive.is is returning bad IPs to them, which is preventing them from serving good IPs:
https://community.cloudflare.com/t/archive-is-error-1001/182...
> Nameservers responsible for archive.is (ben.archive.is, anna.archive.is) are returning answers tailored to the IP address of the requestor.
And indicate that anyone who knows how to contact archive.is can ask them to resolve the issue:
> If you have a contact on the domain owner, you can ask them to fix this.
EDIT: This is knowingly blocked by archive.is. Reasoning and discussion elsewhere in post comments. No need to contact archive.is about it, they’re clearly aware.
Just like we consider it the kernel's fault if user applications break due to a change, I think it's the DNS resolver's fault if they're using a protocol that some popular sites don't support.
As soon as I realized they were causing this issue I just switched away. Other DNS providers don't have this issue.
17 replies →
Cloudflare DNS does not support EDNS Client Subnet[1], so archive.is returns invalid IP address for Cloudflare IPs[2]
[1] https://developers.cloudflare.com/1.1.1.1/nitty-gritty-detai...
[2] https://twitter.com/archiveis/status/1018691421182791680
So much talk about DNS and no one suggested simple workaround for this :-) If anyone wants to use 1.1.1.1 and still access arhive.is, simply add this line to your /etc/hosts file.
134.119.220.26 archive.is
Previous discussion here: https://news.ycombinator.com/item?id=17742457
Why doesn’t archive.is return a valid alternate IP for DNS queries that don’t have the EDNS0 information? They can host an apology page on that IP that tells the user why they aren’t getting the content they are looking for and suggest solutions for using a different open DNS service if the user is willing to use one that provides their client subnet.
I don't get why people use 1.1.1.1 8.8.8.8 etc, for more then debugging. Why tell Google et.al about every site you visit !? And get slightly slower, less accurate and less resilient DNS lookups ...
Many people are otherwise using their ISP's DNS servers, which are often even worse with regards to performance and reliability. Long ago I did tech support for an ISP, and I'd say that 9/10ths of our "outages" were due to our overworked ancient DNS servers failing. I'd go off-script when I took calls during those kinds of outages, and just help people set 4.2.2.2 in their router's DNS settings the moment I saw a strong signal in the line test and hosts not resolving. Managers made snide comments about that not being the official procedure and "not displaying confidence in $ISP", but it fixed the problem.
Because what you get is often faster, more accurate and more resilient compared to the junk DNS run by most ISPs.
And because most site visits start with a Google search anyway.
And finally, because I am comfortable with their privacy statement : https://developers.google.com/speed/public-dns/privacy
I live in New Zealand where all the ISPs and mobile carriers provide fast and reliable DNS resolvers. I've looked into switching to alterntive DNS providers but every one of them are slower than my ISP's resolver. I'm aware that the sitation is quite different in the US and certan other countries, but I wish more Americans were aware that junk ISP-provided DNS servers seem to be an issue exclusive to certain countries (such as the US). I think it would be an intrerestin exercise to figure out why they occur in certain countries and not in other countries.
1 reply →
Because in certain countries the ISP has to respect the legal regulations and so the DNS server provided/defined by each provider will block/redirect certain web sites. These could be torrent trackers, subtitle distribution sites, political and/or religious sites and so on... In some parts of the world alternate DNS servers allow people to access all sites :-)
Not to mention that some ISPs redirect users to pages full of ads when a domain doesn't exist or use DNS to MITM users and inject ads into pages.
I use it because I'd rather tell Google than my government, which is not on friendly terms with either US or Google.
I’m curious. What DNS server do you use? Or do you just memorize the IPs of the websites you want to visit? :P
you can run PowerDNS Recursor locally (or any DNS non stub resolver).
it's not that slower.
Cloudflare returns a proper response for me.
It's possible your ISP is intercepting all traffic for port 53 and sending it to their own nameservers (which do send client subset) instead of you actually taking to cloudflare's 1.1.1.1 at all.
Links for documented instances of this practice?
6 replies →
If you don't mind could you look through: https://ooni.torproject.org/about/risks/
And if they sound acceptable run https://ooni.torproject.org/install/
It'll show you more about likely interception of your traffic.
Not for me:
https://developers.cloudflare.com/1.1.1.1/nitty-gritty-detai...
>EDNS Client Subnet
>1.1.1.1 is a privacy centric resolver so it does not send any client IP information and does not send the EDNS Client Subnet Header to authoritative servers.
What does this mean?
https://tools.ietf.org/html/rfc7871
In Firefox I'm using DNS over HTTPS ( https://mozilla.cloudflare-dns.com/dns-query ) and there is no issue accessing archive.is. Actually I wanted to query archive.is manually but I don't know how to do it in DoH.
Firefox is likely falling back to your local resolver (the default) when it can't find a domain.
archive.org works fine with 1^4. What is the advantage of using archive.is?
Archive.org, the Internet Archive, and archive.is, a webpage capture service that seems to have a primary name of "Archive.today", are wholly separate concerns, offerring different services.
Interesting, I thought archive.is was an alternate domain of the Internet Archive, but it seems they are completely different people[1].
[1] https://en.wikipedia.org/wiki/Archive.today
Yes, but what is the difference between the two? That's really my question. Sorry if it wasn't clear.
Because you usually want to use the service that has the snapshot you want to view. And that isn't always archive.org. But it is my first place to go as well.
oh I thought my local pdns instance was misconfigured.. interesting
[flagged]
"Eschew flamebait. Don't introduce flamewar topics unless you have something genuinely new to say. Avoid unrelated controversies and generic tangents."
https://news.ycombinator.com/newsguidelines.html
...you know that Cloudflare terminated their service, right?
https://blog.cloudflare.com/why-we-terminated-daily-stormer/
And even if they hadn't, how would that make them "Nazi-friendly"? I've always supposed Cloudflare is meant to be neutral. They only kicked out DS because they were stupid enough to pretend CF was endorsing them.
And well, in any case this is unrelated to this thread...
I tried Cloudflare's DNS for a week or so and noticed lots of sites that were blocked. I ended up creating my own DNS server that I run on a VPS.