Let's Encrypt bans certificate usage in any US sanctioned territory [pdf]

https://letsencrypt.org/documents/LE-SA-v1.7-June-04-2026-diff.pdf

by piskov • 1 month ago

454 378 1 month ago

piskov4• 1 month ago

You are not a person or entity that is: (a) located in, organized under the laws of, or ordinarily resident in any country or territory that is the target of comprehensive U.S. sanctions; (b) a prohibited or restricted party under U.S. or other applicable sanctions and export control laws and regulations; or (c) owned or controlled by or acting on behalf of anyone described in (a) or (b). You agree to use Let’s Encrypt Certificates and any services provided by or on behalf of ISRG in compliance with applicable U.S. export control and sanctions laws and regulations

theamk6• 1 month ago

Makes sense, they are US company. I am surprised it took them that long.

rwmj3• 1 month ago

"US company must obey US law" doesn't make for a very interesting headline.

ceeam• 1 month ago

"The world should stop trusting the US companies" OTOH...

ohmg• 1 month ago

The headline is more « US law is batshit and extends well beyond its borders with real world consequences »

floper_a• 1 month ago

That's just another reminder that no one from outside of US should deal with US companies.

bigfishrunning4• 1 month ago

Of course not! just find viable alternatives to Microsoft, Apple, Mozilla, YCombinator, Google, Intel, AMD, ...

In all seriousness, as an American I'd love to see a healthier, more well-distributed tech industry, but I don't see many companies stepping up to provide competing services. It's my understanding that china has alternatives to many of these products/services, but I really don't see how anyone in Europe could possibly use a US-free internet.

p0w3n3d2• 1 month ago

that's why the world need to wake up. With the due respect of any political beliefs here, in the course of politics any country can be deemed the US enemy (or any other country's enemy as a matter of fact), so for example firing the 3/4 of the company because we have Claude and ChatGPT (US based) is a major business continuation flaw...

account427• 1 month ago

It is however a reminder that "just use LE" is not a valid response to concerns about protocols/APIs/browsers/etc requiring TLS.

42droids• 1 month ago

Has anyone got any experience with Zero SSL? https://zerossl.com/ It seems like a good EU alternative.

472828472• 1 month ago

EU? There’s almost zero information on the company, no privacy policy? The only place I found any mention is the footer, “HID Global Corporation, part of ASSA ABLOY”. Assa Abloy seems Swedish but HID Global is a US company as far as a quick search goes. But without a proper company info page and privacy policy I wouldn’t consider it anywhere near a “good alternative” regardless.

slau2• 1 month ago

HID was originally American and Scottish, but became fully American in 1994.

HID was acquired by Assa Abloy in 2000. No idea whether that means we now consider it Swedish.

ZeroSSL used to be Austrian until their acquisition in 2024.

I used to work for a company that got acquired by HID. It looks like HID has retained their original offices in some form.

nomadwastaken3• 1 month ago

The privacy policy is under legal in the footer, exactly where I'd expect it to be honest. It also gives the company registration: > 1.1. We, ZeroSSL GmbH, FN 443956b (the “Company“) and below that the company address (registered in Austria).

Don't get me wrong, I agree that there is some lack of "who actually runs/controls this", especially on the about page where I expect such things to be.

At the very least it's not as transparent as I'd wish from a CA. E.g their Certificate Agreement is from Sectigo, so are they involved? No mention anywhere else from what I can see.

ZeroSSL2• 1 month ago

Jumping in here since we’ve been seeing more mentions of ZeroSSL lately, likely related to the recent CA/B Forum discussions around 1‑year certificates and ACME automation.

- We’re based in Austria (ZeroSSL GmbH). The company was acquired by HID in 2024, which is part of Assa Abloy (Sweden).

- We’re not positioning ourselves as a purely EU-based CA substitute, and we generally don’t market it that way.

- For DV certs specifically, we act as a distributor. Under the hood these are Sectigo-issued certificates, similar to how other providers (for example Namecheap) operate.

Happy to clarify further if useful.

slau2• 1 month ago

3 90-day ACME certs for free. 180€/year for unlimited 90-day certs and 5 yearly ones.

That’s a pretty steep increase. I would almost be more interested in a monthly fee per cert.

nomadwastaken3• 1 month ago

From their docs[0] this doesn't seem to apply if using ACME, but they don't exactly make that clear...

By using ZeroSSL's ACME feature, you will be able to generate an unlimited amount of 90-day SSL certificates at no charge, also supporting multi-domain certificates and wildcards. Each certificate you create will be stored in your ZeroSSL account.

[0] https://zerossl.com/documentation/acme/

nickf3• 1 month ago

ZeroSSL aren't an EU-based alternative, unfortunately.

patrakov• 1 month ago

It's Sectigo under the hood.

linsomniac• 1 month ago

There was some subtle issue with ZeroSSL's implementation of ACME that I ran into with, IIRC, lego and domain certs and there was a ~5 year old lego open issue about it. That was a couple years ago, might be fixed, but my understanding at the time was that it was an issue with Zero's ACME implementation, so there may be dragons.

matharmin2• 1 month ago

I use them in some cases to avoid the rate limits on LetsEncrypt, and they have better support for some older platforms (like ancient Android versions), and I'm pretty happy so far. I have a paid account to support them, but it's not a requirement for ACME certs. It works without issue with Kubernetes Certbot, and seamless to switch between ZeroSSL and LetsEncrypt.

I can't comment on the EU part though - not that relevant in my case.

m2f2• 1 month ago

Is this a canary?

What's gonna happen if I were to begin or continue using one letsencrypt certificate from ... Greenland? Cuba? The EU?

Has letsencrypt been served with a subpoena?

rafram5• 1 month ago

Neither Greenland nor the EU has been sanctioned by the US.

nitwit005• 1 month ago

They haven't been sanctioned, yet, but we live in a time where that's a real possibility.

malfist• 1 month ago

So far

tempfile• 1 month ago

It is not exactly an outlandish suggestion that this may happen.

_ache_• 1 month ago

Yet.

piskov4• 1 month ago

Have you heard about the judge from international court or whatever it is called?

https://www.france24.com/en/americas/20250820-us-hits-icc-wi...

tialaramex5• 1 month ago

Has letsencrypt been served with a subpoena?

While it's certainly possible that ISRG has been served a subpoena because it appears the US DOJ is now a mix of hacks and incompetent buffoons, it wouldn't matter because the whole point is that they don't know anything - what you told them is literally logged publicly for everybody to see without even knowing how to spell "subpoena" let alone issue one.

Some people have this insane idea that somehow the CA has some secret which either they minted and sent to the CA, or the CA minted and gave them a copy and so the US government could get this secret with a subpoena - but the whole fucking point of a Public Key Infrastructure is that we're using Public Key Encryption, if we were OK with everybody having secrets all over the place this entire thing wouldn't be needed.

basilikum3• 1 month ago

They have the secret of the private keys used to sign certificates.

Looking at LavaBit^1 I really would not be so comfortable. The world and especially the US has not gotten more free since then.

[1]https://en.wikipedia.org/wiki/Lavabit

toast09• 1 month ago

Some people have this insane idea that somehow the CA has some secret which either they minted and sent to the CA, or the CA minted and gave them a copy and so the US government could get this secret with a subpoena

LetsEncrypt certainly doesn't, but I've seen certificate storefronts that generate the key on their side and provide you the key and the certificate, so you don't have to figure out how to generate a key.

RyeCombinator2• 1 month ago

Actalis https://actalis.com/ is a good EU alternative.

gapan2• 1 month ago

No it isn't. Not unless it's free.

This is the main reason letsencrypt is so popular.

crote• 1 month ago

They do have a free plan with unlimited ACME DV certs, though! Not marketed very well and no wildcard certs, but it does exist.

RyeCombinator2• 1 month ago

There is a free offering.

DoctorOetker• 1 month ago

active eavesdropping (e.g., monster-in-the-middle attacks)

is this standard MitM, or is it some crucially distinct variation?

thephyber2• 1 month ago

Man in the Middle Wiki:

Also known as a monster-in-the-middle,[1][2] machine-in-the-middle,[3] meddler-in-the-middle,[4] manipulator-in-the-middle,[5][6] person-in-the-middle[7] (PITM), or adversary-in-the-middle[8] (AITM) attack.

walletdrainer• 1 month ago

Those sources feel more than slightly contrived.

Towaway69• 1 month ago

Sanctioned has a double meaning here[1]:

2. officially or formally ratified or confirmed.
3. penalized, especially by way of discipline or to force compliance with legal obligations.

So who can use lets encrypt? Those that are penalised or those that are confirmed.

[1] https://www.dictionary.com/browse/sanctioned

thephyber2• 1 month ago

If you click the link…

[You certify to LetsEncrypt that] …
You are not a person or entity that is: (a) located in, organized under the laws of, or ordinarily resident in any country or territory that is the target of comprehensive U.S. sanctions; (b) a prohibited or restricted party under U.S. or other applicable sanctions and export control laws and regulations; or (c) owned or controlled by or acting on behalf of anyone described in (a) or (b). You agree to use Let’s Encrypt Certificates and any services provided by or on behalf of ISRG in compliance with applicable U.S. export control and sanctions laws and regulations.

gossamer• 1 month ago

It took me a minute to understand the original post because the verb sanction means both itself and basically the opposite of itself. It would be better to say "any territory that the US has levied sanctions against". I thought LetsEncrypt had banned its usage in the US! The word for words like sanction is contronym.

Panzerschrek• 1 month ago

Does it mean that russian/iranian web-sites using letsencrypt stop working and need to change their certificate provider?

altairprime• 1 month ago

Depends on whether LE is compelled to terminate service to BGP AS numbers hosted in U.S.-sanctioned countries, and whether LE continues operating out of the U.S..

trumpdong18• 1 month ago

It works like this. The US gov sends LE a nastygram saying they must terminate service to sanctioned entities. LE either does that or several people go to jail. The USgov doesn't care how it happens, as long as they can't find any evidence that any sanctioned entities are LE customers.

piskov4• 1 month ago

They already revoced certificates for some russian sites

pratyahava2• 1 month ago

any details on that? links to people reporting it?

leosarev2• 1 month ago

I hope not. We don't have any alternatives yet.

CaliforniaKarl• 1 month ago

https://www.actalis.com/activate-free-plan maybe?

account427• 1 month ago

Depending on how you are supposed to read "You agree to use Let’s Encrypt Certificates and any services provided by or on behalf of ISRG in compliance with applicable U.S. export control and sanctions laws and regulations." it could mean that you are not even allowed to use LE certificate to provide services to sanctioned entities as a random non-US company/person.

idoubtit2• 1 month ago

Couldn't LE have a branch in Europe or anywhere outside the USA and its minions?

Because they're betraying their own goals, as stated in their About page: “It is a service run for the public’s benefit. [...] Anyone who owns a domain name can use Let’s Encrypt to obtain a trusted certificate at zero cost. [...] Let’s Encrypt is a joint effort to benefit the community, beyond the control of any one organization.” Now they own they are under the control of a political organization.

Here is the paragraph Let's Encrypt added to their Subscription Agreement on 2026-06-04:

You are not a person or entity that is:
(a) located in, organized under the laws of, or ordinarily resident in any country or territory that is the target of comprehensive U.S. sanctions;
(b) a prohibited or restricted party under U.S. or other applicable sanctions and export control laws and regulations;
or (c) owned or controlled by or acting on behalf of anyone described in (a) or (b).
You agree to use Let’s Encrypt Certificates and any services provided by or on behalf of ISRG in compliance with applicable U.S. export control and sanctions laws and regulations.

cassianoleal6• 1 month ago

They could, but if the branch didn’t follow these laws, the main US branch would still be liable.

cromka2• 1 month ago

It's about time SOME entities start moving from US entirely.

mfuzzey• 1 month ago

Just close down completely in the US and move to the EU

trumpdong18• 1 month ago

What if the branch in Iran was the main branch?

skissane• 1 month ago

It depends on the legal structure.

If they set up a subsidiary in Europe, they could be held liable for actions of European subsidiary.

If an independent org is stood up in Europe, with European directors, staff and funding, legally independent of US org, and the US org just provides advice/assistance to Europe org without ability to control it-legal liability for US org for Europe org’s decisions is less likely. Of course, ask a lawyer-but if you openly say “we are doing this to work around US sanctions” you could still be liable; if you say “this has nothing to do with sanctions this is about resilience of global digital infrastructure and European digital sovereignty” then under what legal theory is the US org liable?

PunchyHamster• 1 month ago

completely independent entity would be far better option. Protocol is open after all, just need pointing to different vendor

belorn2• 1 month ago

Let's encrypt is not some code or even a company that you can split into different branches. Their existence is one based on trust relations that let's encrypt has with browsers and operative systems. It is in one part similar to both domain names and IP address space, in that the technical aspects of creating alternative roots is almost trivial in comparison to getting the trust that is required for an alternative root to be accepted by the rest of the world.

Let say someone created an Russian Let's Encrypt. It has all the technical aspects as regular LE in that you can request a certificate and get one through an acme challenge. That is all great and all, but no browser will recognize it as valid. No operative system will recognize it as valid. The Russian state might add the new LE as valid for government computers, but the real work would be to get any other participants in the world to do the same. The issue is not a technical one but rather a social one that is built on trust.

When Russia invaded Ukraine there was a major discussion if IANA/ICANN should have disconnected Russia from domain names and IP addresses. That discussion ended on a decision to not do that because the symbolic benefit was deemed minor compared to the harm to the system in large, especially once the war end. If you got two roots, then a domain name or IP address can now suddenly have two locations, and it would be a massive pain to try fix it even if people wanted to fix it. Certificate Authorities do not share this trait since there can be an almost unlimited number of roots and none of them can conflict with each other (assuming no hash collision). If Russia spins up a new CA then people can use that one today if they want to, and they can continue to do so after the war has ended.

orthoxerox• 1 month ago

Russia already has its own root CA, the issue is that state-owned root CAs are by definition not safe from MITM attacks by the same government.

throw-the-towel2• 1 month ago

It shouldn't be located in Europe (because, as you said, US minions are no better than the US itself). Instead it should move to a neutral country, somewhere like Singapore or Uruguay.

hparadiz3• 1 month ago

Suddenly the idea of having a CA hosted in space on a satellite issuing certs seems like a good idea.

everfrustrated• 1 month ago

There are other non-US equivalents to Lets Encrypt.

pxeger1• 1 month ago

How are they going to enforce this?

nickf3• 1 month ago

I would imagine, as a CA that issues only DV certs, they'd disallow issuance to various ccTLDs, and perhaps stop newAccount registrations with email addresses at those ccTLDs. That's about as much as they could do - IP-blocking by region is ineffective and crude at best.

morpheuskafka5• 1 month ago

The question is, will that be enough? If OFAC can demonstrate that even with such restrictions, sanctioned entities are frequently obtaining certificates, they may be forced to require account creation or something else as a means of limiting that.

They also likely would have to implement some kind of domain name screening, just like banks have to block transfers that mention "Havana" or "Tehran".

They are currently not doing anything, even ccTLD blocks. They have issued certificates for .kp domains this month and in August of last year.

Igrom• 1 month ago

It seems that, as soon as you transact with a sanctioned entity, you are globally in breach of the agreement and risking the revocation of all your certificates — also the ones for non-sanctioned countries.

Front matter:

   - it is called a "Subscriber Agreement" and not anything that suggests that its scope is a single certificate

   - it's a "contract [...] regarding Your [...] rights and duties relating to [...] Certificates" - plural

2.1 "Term":

  - "[the agreement] will remain in force during the entire period during which *any* of Your Certificates are valid" - plural

3.1 "Warranties":

  - "[by] requesting, accepting, or using *a* Let’s Encrypt Certificate" - plural

trumpdong18• 1 month ago

I said hi to an Iranian today. Lets see if LE revokes my website.

diimdeep2• 1 month ago

the reach is by rough estimates ~2.5–6 million websites globally, 2–5 million of those in Russia and 0.3-1 million in Iran

Whatever USofA, it's not hard to have their own cosmodrome and certificates.

Tangential, in 2026 website certificates feel like nothing, disposable automation artifact, toxic max-security[1], vehicle for those who rent seek, fingerprint.

[1] https://tom7.org/httpv/httpv.pdf

axiologist• 1 month ago

This somehow confirms my gut feeling that digital certificates are mainly a means to enforce exclusion on behalf of the certificate authority ownership. It is a tool to prevent people from taking full ownership and control of whatever is affected by digital certificates, be it software, firmware, hardware, or as in this case SSL/TLS. That's digital tyranny in disguise.

MarleTangible• 1 month ago

I always saw it as a trust-chain and think that anyone is welcomed to create a root certificate and distribute it to whomever trusts them. Most simple services may not need TLS, but with the ISPs eavesdropping on our communication, a form of secure communication is required and the currently best solution we have requires a trust-chain to be built.

Parodper10• 1 month ago

We could, and should, switch to DANE. Or else, switch to how X.509 was supposed to be used, with each country running a CA for their nationals.

account427• 1 month ago

Do we also need to put all our letters into strongboxes before we send them?

Maybe we should have solve the ISP snooping problem by making that illegal instead.

thaumasiotes2• 1 month ago

I always saw it as a trust-chain and think that anyone is welcomed to create a root certificate and distribute it to whomever trusts them.

Note that phones already try to prevent you from using a certificate that you provide yourself.

happosai• 1 month ago

It is such a great improvement that ISPs cannot eavesdrop us anymore... only for everyone to terminate TLS at cloudflare so they (and thus US government) can now eavesdrop everyone.

lesostep2• 1 month ago

The problem is that finding a root source of trust aren't easy this days. LE was neutral, now nobody is.

Russian government issued their new root certificate years ago.

Nobody trusted it enough to request a certificate from them or install it on their computers. Including almost all of the russian residents.

If Let's Encrypt enforces the rules, as written in pdf, a lot of people would lose a choice.

Frankly, even publishing a statement like that would make the scales of trust tip for some.

palmotea• 1 month ago

This somehow confirms my gut feeling that digital certificates are mainly a means to enforce exclusion on behalf of the certificate authority ownership. It is a tool to prevent people from taking full ownership and control of whatever is affected by digital certificates, be it software, firmware, hardware, or as in this case SSL/TLS. That's digital tyranny in disguise.

I think the "digital tyranny" is a side effect, not the main goal. They're "mainly a means" to prevent certain kinds of MITM attacks.

account427• 1 month ago

You could that with a much saner approach like DANE.

watwut• 1 month ago

I always thought the main goal was to force people to pay money for certificates.

belorn2• 1 month ago

While it seems like certificate authority has the primary control here, the real control lies in browsers and operative systems in which certificate authorities are trusted. Users also have, at least for the moment, control to add or remove certificate authorities, even if that control is slightly less clear for devices like smart phones.

Digital certificates that signs software packages are used to enforce exclusion by some manufacturers. Let's encrypt is not in that space to my knowledge, but it is a place where you the owner do not have the right to determine which certificate authority should be trusted, and generally the only one that is trusted is the manufacturer. Its arguable if we even should be calling such entities a certificate authority, even if they technically are the owner of the root certificate that signs the package.

hulitu• 1 month ago

the real control lies in browsers and operative systems in which certificate authorities are trusted

Wasn't Let's encrypt a Mozilla child ?

The real control lies at who defines what is trusted.

kube-system13• 1 month ago

The entire point of a trust model is to exclude people. That's the stated goal.

If you want encryption without trust, just use self-signed certs.

134153• 1 month ago

The problem is that the current trust model is totally untrustworthy.

lxgr4• 1 month ago

If you don't care about who you're talking to, why use certificates at all?

phoe-krk• 1 month ago

And now imagine that one of the Trump tantrums contains an announcement of sanctions against the European Union.

marcosdumay2• 1 month ago

He already announced sanctions against Spain. And took them back when Germany announced that sanctions against one EU country meant sanctions against them all.

karteum• 1 month ago

Can anyone explain me what went wrong with http://www.cacert.org/ and why they are not supported by any major browser ?

em-bee• 1 month ago

the wikipedia page has links to projects that removed CAcert where reasons are stated. the main one being that CAcert didn't complete a security audit or because they were not yet accepted by mozilla (because of the lack of an audit, but also because CAcert actually withdrew the request to be included). one group removed it because CAcert has a strict root redistribtion license that they can't follow.

LWN has a good writeup on the audit situation as of 2014: https://lwn.net/Articles/590879/

ezbie2• 1 month ago

What in the actual fuck?

cynicalsecurity2• 1 month ago

This actually makes sense. No freedom for the enemies of freedom.

mswphd• 1 month ago

love thought-terminating cliches. really helps keep from actually thinking ever.

cynicalsecurity2• 1 month ago

Your comment reads like a thought-terminating cliché. If Russia occupied your city, killed your family and friends and left you homeless, you might reconsider giving freedom to those who take it away from others. Unfortunately, sanctions are often very easy to evade.

CrzyLngPwd• 1 month ago

But what if you're the baddies?

bigfishrunning4• 1 month ago

Then try not to be completely dependent on the products of a company that is under the control of your enemy.

hinata083• 1 month ago

the list of ppl under US sanctions is staggering

Europe starts to shield itself from the risk since Nicolas Guillou, the French ICC judge who issued a warrant against bibi got sanctioned (France officially protested about this case)

China is being successful at blocking US firms out of their supply chains (they already use Linux on Loongarch processors with some homemade architecture and pioneer RISC V), since a bunch of their companies also got sanctions for supplying the governement

US stands so much for freedom that it's the first country to refuse immigration to FIFA world cup teams and athletes, with Iranians not allowed to stay between games and Somali goalkeeper being turned away at the border. Germany itself didn't do for the 1936 Olympics.

So at best, they're only shooting themselves in the foot by showing any US component in a supply chain is a risk, while using US clouds were already a risk of loss of revenue from FISA requests to undercut your bid and rot your company and using US dollars for trade was already a liability

In the meantime, US companies can do anything, break any financial law and abuse every human right, they'll just sign DPAs to avoid prosecution

jalospinoso• 1 month ago

The uninteresting version of this is “US entity follows US law.”

The interesting version is that Web PKI is not just cryptographic infrastructure. It is also a policy distribution system. A browser trust store, a CA, a subscriber agreement, revocation rules, export controls, and sanctions law all end up in the request path of "can this site speak HTTPS to normal users?"

That does not make Let’s Encrypt uniquely bad. Any CA has some jurisdiction, owners, contracts, root-program obligations, abuse process, and legal exposure. Moving the CA changes the governance surface; it does not remove governance.

But it does mean "just use Let’s Encrypt" is not a neutral answer when protocols, browsers, APIs, app stores, or regulators effectively require TLS. The operational dependency is not only ACME uptime and certificate issuance. It is also jurisdictional continuity.

The hard product question is what failure mode we want:

1. Web PKI: power concentrates in CAs, browsers, and root programs. 2. DANE/DNSSEC: power shifts toward DNS operators, registries, registrars, and governments. 3. Self-signed / TOFU / pinning: power shifts toward application-specific trust and worse UX. 4. Multiple CAs: better resilience, but still bounded by browser trust stores and legal chokepoints.

There is no apolitical trust system here. There are only different control planes with different failure modes.

The practical ask from Let’s Encrypt should be clarity: issuance vs renewal vs revocation, existing certs vs future certs, domain location vs subscriber location, hosting location vs user location, and how they interpret “use” of a certificate. Without that, operators are left guessing whether this is a narrow compliance clause or a broad infrastructure-risk event.

Insimwytim• 1 month ago

Iran is blocking internet for months, US ...bans creation of secure connections - that'll show 'em!

Russian quasi-government structures are spending quadrillion of rubles on a TSPU (censorship system) to spy on Russian residents, US ...helps them by making snooping on what is currently encrypted traffic possible by banning accessible encryption!

gnerd00• 1 month ago

wait until you find out about Facebook!

jaas5• 1 month ago

Let's Encrypt certificates continue to be available in both Iran and Russia, just not for the Iranian and Russian governments.

The terms of service update to clarify what we have always done, comply with relevant law, has not changed the situation for either country.

joshuaissac• 1 month ago

Let's Encrypt certificates continue to be available in both Iran and Russia, just not for the Iranian and Russian governments.

According to https://news.ycombinator.com/item?id=48457280 it affects all people ordinarily resident in those territories, not just their governments:

You are not a person or entity that is:
(a) located in, organized under the laws of, or ordinarily resident in any country or territory that is the target of comprehensive U.S. sanctions;
[other 'or' conditions]

john_strinlai• 1 month ago

you should update the documents to reflect this stance.

"You are not a person or entity that is: (a) located in, organized under the laws of, or ordinarily resident in any country or territory that is the target of comprehensive U.S. sanctions; "

this says nothing (edit: specific) about government (edit: only), and is applicable to normal people in those areas.

saeedesmaili• 1 month ago

[Iranian here] Completely agreed. Reminds me of how US banned citizens and businesses in Iran from using cloud infrastructure like AWS or digital ocean, leading to people and businesses moving to the government-sponsored local cloud services, and that made it super easy for the government to block internet access whenever they want without essential services like banking, ecommerce, online taxi booking, food delivery etc being disrupted.

grishka• 1 month ago

TSPU isn't for spying, it's for censorship enforcement and everything else that makes the experience of using the internet here miserable without a VPN. It's SORM that's for spying. And Roskomnadzor is very much part of the government.

mikrotikker• 1 month ago

You could look at it equally as the USA saving those citizens because if the authoritarian discover they are using LE they could suffer imprisonment

ComputerGuru• 1 month ago

This is bullshit on par with the Chinese firewall, meant to effectively prevent the (entire!) western world from information by parties deemed persona non-grata. SSL certificates are supposed to be about security, not geopolitics.

I'm pretty sure a LE server hitting an Iranian or North Korean endpoint and validating a crypto challenge does not break any OFAC or EAR rules, and no money changes hands. And if a non-US entity wants to do it, the US would just sanction them. Microsoft and Mozilla are certainly not going to include a North Korean or Russian state CA in the root trusted certs (and if they did, the US government could just threaten them with sanctions, too).

Hard not to say "we warned you" about making self-signed certs completely unusable in favor of a very centralized approach.

wnevets2• 1 month ago

Maybe consolidating ~60% of the web's certificates on to a single provider was a mistake.

patmorgan23• 1 month ago

Well good thing everyone using the provider is using an open protocol and it's stupid easy to switch

wnevets2• 1 month ago

Which free CA should I use instead of lets encrypt that has same browser support?

pratyahava2• 1 month ago

can you please suggest any alternatives to switch to? i hardly can find any alternative which provides free service and is a non-profit org at the same time.

trumpdong18• 1 month ago

Before this, they were all unencrypted and you had to pay to get a cert. I guess we could go back to that - now knowing that every unencrypted connection is being MITMed (the world is so much more hostile now)...

greatgib• 1 month ago

To be put in perspective with their push for very short live certificates, like 7 days, with the argument that anyone can easily get certificate from at any time.

But in fact, little by little you have all the stacks needed to be able to isolate some entities from internet at the us request in a very short time

CobrastanJorji2• 1 month ago

Let's Encrypt’s mission is to create a more secure and privacy-respecting web, except for people residing in countries with the most need for a more secure and privacy-respecting web. Sure, that's great.

That said, pretty sure this is stems from the insane US legal requirement to not export SSL technology to enemy countries. I'm sure some of y'all are old enough to remember when web browsers came in "international friendly" versions that supported 40 bit encryption, or "fancy secure" versions with 128 bit encryption.

rzerowan• 1 month ago

Seems in all thing tech at the moment the US legal system is accelearting a great split and erectinga digital iron curtain, from AI models to the more mundane like TLS certs. Its been standard for a while for many Linux distros based in the US to toe the party line - like RedHat having notices pretty similar to this one by LE. Seems any meaningful Open Projects will have to choose what path they want to take, be like RISC-V and relocate or LE and others and enforce the divide.

xxpor3• 1 month ago

The RISC-V move was laughable. It’s still US tech, developed largely with DARPA funds.

thayne3• 1 month ago

It isn't just the US. China, Russia, the EU, and Australia and probably others are all increasingly trying to create virtual walls of various forms in the internet.

throwaway858252• 1 month ago

If you truly need a secure and private web you should be using tor.

Izmaki• 1 month ago

Say what, now?

Anonymity and encrypted communication are two very, very different things. Have one but not the other and you're essentially handing off your private data incl. passwords to whoever that has a tap on the communication between you and the server can fetch them, too. Have the other but not the one and everyone will know who you are, but they can't eavesdrop.

dsl• 1 month ago

pretty sure this is stems from the insane US legal requirement to not export SSL technology to enemy countries

This is most likely OFAC. Lets Encrypt could apply for a license to do business with sanctioned entities, and given their use case it would most likely be approved.

https://ofac.treasury.gov/ofac-license-application-page

greyface-4• 1 month ago

OFAC regulates commerce, not speech. Let's Encrypt is not doing "business", they're operating a free informational service. Lots of organizations interpret any information exchange as subject to OFAC regulation, and you and Let's Encrypt have good company in this interpretation, but I think it's unnecessarily ceding ground.

bhhaskin• 1 month ago

It could also be an easy way to not have to implement backdoors for the government/military.

lxgr4• 1 month ago

What "backdoor" would Let's Encrypt even implement? That's not how a CA works.

They might be compelled to issue a certificate to an unauthorized (by browser PKI policies, not local law) entity, but that would be very conspicuous due to Certificate Transparency.

loloquwowndueo• 1 month ago

I’m actually old enough to remember how PGP code was exported as a book printout because exporting computer code for cryptography with strong keys in digital form was disallowed but a book was fine (protected by first amendment rights). The printout was scanned abroad to reconstitute the source and build pgp legally.

jaas5• 1 month ago

Let's Encrypt continues to be available to almost every vulnerable population in the world, including those that need it most. I say almost as I'm hesitant to speak in absolutes regarding a topic as complex as this.

Most of our sanctions-related blocks apply only to the governments of certain sanctioned countries, not their general population.

This subscriber agreement update was intended to better reflect our legal requirements. It does not reflect a major change in the service we provide. Our compliance program does evolve over time, and part of that is communicating about it better in our terms of service. It's clear from some of the comments here that we have more work to do to make that text more understandable, we'll work on that.

That said, pretty sure this is stems from the insane US legal requirement to not export SSL technology to enemy countries. I'm sure some of y'all are old enough to remember when web browsers came in "international friendly" versions that supported 40 bit encryption, or "fancy secure" versions with 128 bit encryption.

It doesn't.

notamario• 1 month ago

When you say “our legal requirements” do you mean requirements LE imposes in its agreements or requires imposed on LE by governments?

FireBeyond2• 1 month ago

Most of our sanctions-related blocks apply only to the governments of certain sanctioned countries, not their general population.

The agreement very plainly says otherwise:

You are not a person or entity that is: (a) located in, organized under the laws of, or ordinarily resident in any country or territory that is the target of comprehensive U.S. sanctions

The general population of those countries are absolutely "persons" "located in" a "country or territory that is the target of comprehensive U.S. sanctions."

communicating about it better in our terms of service. It's clear from some of the comments here that we have more work to do to make that text more understandable, we'll work on that.

This tries to frame it as a comprehension issue. It's not.

The wording in your agreement is actually quite clear. I think it's reckless, if not disingenuous to frame this as "we really only mean government entities".

Apropos of anything else, it's also not how US sanctions work - they are absolutely aimed at both the populace as well as the government itself.

CobrastanJorji2• 1 month ago

Thanks for responding, and to clarify, I am confident that Let's Encrypt is shared as widely as they are able. Could you explain what that requirement does stem from?

morpheuskafka5• 1 month ago

You issued a certificate for North Korea's email infrastructure as recently as six days ago:

https://crt.sh/?id=26878583197 (06/04/2026 smtp.star-co.net.kp) https://crt.sh/?id=20256841119 (08/11/2025 *.star.net.kp)

Star Joint Venture is the manager of the .kp TLD and one of DPRK's two email providers (the other is silibank.net.kp) [1], used as the official email for various government bodies ex. ipa817@star-co.net.kp (IP Office), kscost@star-co.net.kp (Sci/Tech Commission), ksf@star-co.net.kp (Ministry of Culture and Sports), mhs-ip@star-co.net.kp (Atomic Energy). It is also widely used by those universities and companies that engage with the outside world.

How did you determine that issuing a certificate to this domain or any .kp domain was compliant with the general ban on exporting goods and services to DPRK?

cpud362• 1 month ago

Let's Encrypt continues to be available to almost every vulnerable population in the world, including those that need it most. I say almost as I'm hesitant to speak in absolutes regarding a topic as complex as this.
Most of our sanctions-related blocks apply only to the governments of certain sanctioned countries, not their general population.

It doesn't work that way.

Blocking governments from getting certs doesn't hurt them in the slightest. The government can just create their own pki.

But it hurts the general population instead. People do not live in vacuum, they still need to access government sites. And thus people are forced to install root certificates of questionable trust.

When Let's Encrypt blocks government entities, it instead puts respective vulnerable population in even less secure environment.

Although, given the current events, I am not sure Let's Encrypt continues to deserve the trust it had.

bigiain• 1 month ago

Some (well, at least one) of us are old enough to have owned one of these:

http://www.cypherspace.org/adam/uk-shirt.html

A t-shirt with a Perl script that implemented RSA encryption strong enough to be technically illegal to export from the US.

(I must sadly admit to being too cowardly/sensible to have taken that shirt to the US in the late 90s...)

greyface-4• 1 month ago

And if you missed the original run, you can buy a reprint from Adam's current company: https://store.blockstream.com/products/rsa-t-shirt

tolciho• 1 month ago

I wore the rsa-dolphin t-shirt all over the place and nobody batted an eye back then, but a dolphin made up of ASCII characters is quite a bit less obvious than the one you linked.

OpenBSD being based in Canada ships strong crypto, but has had a sometimes troubled relationship with certain regimes.

https://www.openbsd.org/lyrics.html#34

dd8601fn• 1 month ago

DeCSS printed on stuff was a thing for a while, too.

wodenokoto2• 1 month ago

Let's Encrypt’s mission is to create a more secure and privacy-respecting web, except for people residing in countries with the most need for a more secure and privacy-respecting web. Sure, that's great.

If complying with the law gets in the way of the mission I’m not sure that counts as a change to the mission.

Supermancho2• 1 month ago

If complying with a law gets in the way of the mission I’m not sure that counts as a change to the mission.

It's already illegal to use in NK, but if it's the US, well it's time to steer the mission around it? Gross.

__s• 1 month ago

http://www.geekytattoos.com/illegal-tattoos-rsa-tattoos

tattoo yourself with crypto code to become munitions

golem14• 1 month ago

I mean, noone is stopping someone to clone letsencrypt - it shouldn't be very hard.

Google had a similar dilemma - do they want to offer a (censored) service in China, and have a hope of keeping some marketshare, or not (and be kicked out immediately).

In this case though, it seems to be an unforced move by letsencrypt ? Or was it compelled by LEAs?

p0w3n3d2• 1 month ago

  to not export SSL technology to enemy countries

sounds like to not export mathematics

jjav• 1 month ago

This is why, as someone who works in security and encryption and has implemented web server TLS stacks and such, I still oppose the "always-https" idea.

TLS is awesome, one of the most valuable developments in Internet history. But, it is important to undewrstand that it is a double edged sword. Requiring a CA, which in practical terms means requiring a publicly known CA, is a choke point of freedom.

nikolay• 1 month ago

Yeah, let everybody build and use their own services, and then the US will end up having less control and visibility. Great tactics!

niemandhier• 1 month ago

It their right to do that.

But can we still trust them?

I am not well versed in how their systemwide certificate issuance works: If they have to add this to their terms to comply with their government, could the same government use pressure to leverage let’s encrypt to do harm.

trumpdong18• 1 month ago

Yes, of course it could and it will. I don't think the US government has ever missed an opportunity to be corrupt and break shit for stupid reasons.

OutOfHere• 1 month ago

I had the parent organization of LetsEncrypt (Internet Security Research Group) in my Will, but after reading this, I will remove it immediately. US sanctions harm too many innocent people.

VortexLain• 1 month ago

Now this is very bad, as bad as it can get. As soon as all local services will stop working in sanctioned countries, those countries' governments will force all users to either install a root certificate or lose access to all local services and websites. And then it will be possible to use that root certificate for MITM attacks. In the worst case scenario, after the majority of users will install the root certificate, state DPIs will MITM all traffic and will block all un-MITMable traffic.

yurish• 1 month ago

Don't understand why you have been downvoted. Russian government have already attempted to push forward their root certificate for banking using Yandex browser, now this.

trumpdong18• 1 month ago

Sounds like the sanctions worked.

mrweasel• 1 month ago

This should be one of those things that should be an quick EU win. Running Let's Encrypt is $3-4mill a year, the EU probably uses that on pencils.

The EU could easily bootstrap a Let's Encrypt competitor if it truly cared about removing dependencies on US based entities.

xxpor3• 1 month ago

Do you really think the EU wants to sign up for PR that’s essentially “the US is being too mean to Russia” right now?

flumpcakes• 1 month ago

I think the EU should do it regardless of Russia. The EU should invest in its own technology and not depend so much on an increasingly undependable ally.

zajio1am2• 1 month ago

Yes, but EU would have to convince Google and Apple to get a new root certificate to browsers.

toast09• 1 month ago

Not really. They just have to convince an existing CA that cross-signing their CA won't make Google and Apple mad.

Cross-signed roots are common. Just takes money and maybe audits, but it's the same audit they'd need to get in the browser root stores anyway.

joemi2• 1 month ago

Is Let's Encrypt the only provider of SSL certificates?

Genuine question! Because I assumed there were other places you could get a SSL certificate, but people in this thread seem to be implying that without Let's Encrypt, there's no way for people in those sanctioned territories to get a cert.

herbst• 1 month ago

If nothing has changed it's still the only one that's free and instant. Back in the day you'd had to pay $10/y and install manually

kube-system13• 1 month ago

https://zerossl.com/

Fnoord2• 1 month ago

Is Let's Encrypt the only provider of SSL certificates?

No.

nicce• 1 month ago

There are some options. actalis.com is European alternative but free tier is a bit less than Let's Encrypt.

hinata083• 1 month ago

If it was a genuine question, the genuine answer is it's the provider that democratised streamlined ACME certificate verification and made it for free

No account, no payment, a single bash command or a certbot that runs regularly and you have your own globally recognised certificate

Historically, providers used to make the most frictions so that they could justify absolutely crazy fees for signing any certificates. It doesn't goes down well in DevOps, it doesn't work with indies who don't have 3 to 4 digits figures to blow in httpS, everyone including organisations ended up making certificates authorities of their own to sign stuff... and let's encrypt was successful at making certificates easy, free and actually secure

cyounkins• 1 month ago

Gotta love the word 'sanction'. It is it's own antonym! "The committee sanctioned the new policy." (approved it) "The committee sanctioned the rogue nation." (penalized it)

lmm6• 1 month ago

There are many autoantonyms in traditional English, e.g. cleave.

rerdavies• 1 month ago

Is this actually new? Looks like a standard US export restriction for encryption technology to me. These sorts of restrictions have been around since the '90s.

Let's Encrypt becomes subject to US export restrictions on cryptography if they are a US company, or if they post anything to github or post anything to major app stores. Every app I have ever posted to Google Play has had to submit a form to the US government declaring what use they make of cryptography.

These restrictions have been in force since that late 1950s (with a long and complicated history with respect to computer cryptography). This particular text looks like a boilerplate restriction, that's required to comply with US EAR export requirements to me.

lmm6• 1 month ago

Organisations that are serious about promoting privacy should have been avoiding the US since the '90s and/or '50s, but the second best time to reincorporate in a safe jurisdiction is today.

fluoridation3• 1 month ago

A certificate is not cryptography, though, it's a number. The entity requesting the certificate already has the cryptographic software installed on their servers, as do the clients trying to connect to them. There's nothing technologically special about the number, it's all in the realm of the social contract, in that it has been blessed by a chain of trust.

yreg• 1 month ago

Everything is a number.

ale42• 1 month ago

Time for a non-US equivalent of Let's Encrypt?

trumpdong18• 1 month ago

How will you get Mozilla and Google to trust it?

Especially since sanctions are transitive. Mozilla and Google, being US companies, are actually not allowed to trust any entity whose purpose is to work around sanctions. Their members could go to jail for that.

markhahn• 1 month ago

huh? the linked document shows that bullet item as deleted.

ebiederm• 1 month ago

Weird. The copy I read says they have just deleted that section of their user agreement.

jldugger• 1 month ago

Took me a minute to parse the headline -- Sanctioned as as in "imposed penalty" (ie "sanctions"), not as in dictionary definition #2 "official permission or approval".

Perhaps because "US territories" are a thing, perhaps because it's way more newsworthy if LE bans the US, or perhaps im just a dummie.

guhcampos• 1 month ago

The title was a bit misleading.

When I read it, I interpreted it as "let's encrypt bans certificate usage in - any territories endorsed by the US". Took me reading a couple comments to understand it actually meant "territories under US sanctions".

trumpdong18• 1 month ago

We all knew something like this was coming when we decided to centralise the web around Let's Encrypt.

In reality of course you can probably just ignore this as long as you request the certificate from a proxy in a nonsanctioned country and you don't stick out to the government.

aussieguy1234• 1 month ago

Dictators love it when their citizens can't use encryption. It makes them much easier to control and monitor.

Dibby053• 1 month ago

All they can do is disable support for certain ccTLDs, but other than that, it's unenforceable.

That's why many tech companies echo these laws overtly and with a lot of fanfare... They know they have no real control over who uses their services, so this is a way to signal their good faith and best effort in advance, in case they end up caught up in some foreign cyberbullshit.

morpheuskafka5• 1 month ago

I had been meaning to post somewhere that they issued a certificate to kza.org.kp a few months ago but didn't really seem worthy of its own thread.

I am no lawyer, but while there do appear to be some exemptions for communication related services, it's not clear that this qualifies as LE isn't actually providing telecommunications, just a certificate file. And it's not even an issue of the encryption itself, North Korea is under a general embargo so any exports or trade whatsoever is restricted by default.

As an aside, many of North Korea's web servers appear to be old enough to have Heartbleed based on their banner versions, but most don't actually have HTTPS in the first place.

rswail• 1 month ago

For all the people commenting, the ITAR rules still apply for TLS, if you want to use TLS in an app for iOS/Android, one of the requirements is to get an ITAR exemption as part of the app review [1].

The US sanctions are imposed on entire nations (eg Iran), so LetsEncrypt have no option but to state in their conditions that their service is not available. They don't have a choice as a US organization operating under US law.

Whether they choose to enforce that through technical means (eg blocking IPs etc) is up to them.

[1] https://developer.apple.com/documentation/security/complying...

mrsssnake• 1 month ago

Why when connecting to a TLS website service that does not have a CA signed certificate, I am welcomed with "Secure connection failed, browser not trusting the ceritifate. Do you want to continue?", without showing me the actual certificate fingerprint?

On desktops browser displaying the fingerprint/hash requires clicks, on mobile is not implemented and on native apps practically not existing.

The keys should be shown, so they could be verified manually in person or via other channel. Just like the SSH do. Someone say people would just click "accept" without a thought, but the button is already here, just no information what actually is accepted.

someguyornotidk• 1 month ago

A lot of the pushback browser vendors got for locking APIs behind so-called "secure contexts" was because everyone (including them) knew this would happen. If there is a centralized system, some politician will manage to find a way to fuck with it.

Iran and other tyrannical governments can easily set up their own CAs and force their citizens to use them. Iran likely already has this infra in place. This ban does nothing but highlights LE as the liability it is. The decades-old certificate authority scheme is no longer fit for purpose and needs to go.

If you're a web developer, consider offering your site through public key-addressable networks. Reticulum and Tor are good options that work today.

cekanoni• 1 month ago

this is big blow to the Internet society very disappointing to read this..

boomlinde• 1 month ago

What other CAs implement ACME? Are there any free alternatives outside the US?

ysmoradi• 1 month ago

PLEASE DON'T DO THIS )":

gnunicorn• 1 month ago

It was a great hack, but it was always just that: a hack. We all always knew that the "certificate authority"-hierarchy is broken and can easily be abused by the ones in power. I appreciate everything that the let's encrypt peeps have done for the world, but the cert authority system really needs an overhaul.

rurban• 1 month ago

Hello! The US is the enemy of democracy. If someone should be banned, then them.

Let's Encrypt bans certificate usage in any US sanctioned territory [pdf]

Related Stories