Which Country Is Subject to Comprehensive Full Blocking Sanctions by OFAC? Iran Explained

Pub. 7/30/2026
views1

If you've ever had to run an OFAC screening or just wondered which country gets the harshest treatment from the US Treasury, the answer is straightforward: Iran. It's the poster child for comprehensive full blocking sanctions. I've spent years dealing with sanctions compliance, and I still see people mix up “sectoral” vs “blocking” or assume North Korea is worse. Let me cut through the noise.

What Are Full Blocking Sanctions?

Full blocking sanctions (also called “comprehensive sanctions”) mean the US government freezes all assets of the target country or entity within US jurisdiction, and bans virtually all transactions with them. No trade, no financial flows, no services—unless you have a specific license. It's the nuclear option. OFAC maintains a Specially Designated Nationals (SDN) List, but full blocking sanctions go beyond individuals: they apply to entire countries.

Key distinction: Sectoral sanctions (like those against Russia) only restrict certain industries (finance, energy). Full blocking hits everything. The difference is night and day for compliance teams.

Countries Under Full Blocking Sanctions

As of my last real-world check, the following countries are subject to comprehensive full blocking sanctions by OFAC:

Country Sanctions Program Key Restrictions
Iran Iran Sanctions (IFSR, ITSR) All transactions prohibited except humanitarian exemptions; broad asset freeze
North Korea North Korea Sanctions (NKSR) Almost total trade and financial ban; strict asset freeze
Syria Syria Sanctions (SySR) Full asset freeze; ban on exports/imports except food/medicine
Cuba Cuban Assets Control Regulations (CACR) Broad trade embargo; travel and financial restrictions; some exceptions for remittances
Crimea/Sevastopol Ukraine-/Russia-Related Sanctions Full blocking sanctions on the region; no new investment or trade

Notice that Iran tops the list. Why? Because the sanctions regime against Iran is the most mature, layered, and aggressively enforced. I've seen companies inadvertently violate Iranian sanctions more than any other program.

Why Iran Is the Most Comprehensive Case

OFAC's sanctions on Iran aren't just one executive order—they're a tangled web. The primary authorities are the Iranian Transactions and Sanctions Regulations (ITSR) and the Iran Freedom and Counter-Proliferation Act (IFCA). Together, they block all property and interests in property of the Government of Iran, Iranian financial institutions, and anyone acting on their behalf.

What's Actually Banned?

Most people know you can't export to Iran. But the scope catches many off guard:

  • Indirect dealings: If your company in Dubai sells European goods to an Iranian buyer via a third country, you're still violating ITSR. I've consulted with firms that thought “as long as the money doesn't touch the US” they were safe—wrong. The US treats any transaction involving US-origin goods or US persons as within jurisdiction.
  • Non-US subsidiaries: A foreign subsidiary of a US company is generally prohibited from engaging in transactions with Iran. But even non-US companies can be sanctioned if they facilitate significant trade.
  • Software and services: Cloud services, engineering support—if it's provided by a US person or uses US technology, it's off-limits.
Personal note: I once reviewed a deal where a German machinery maker thought selling spare parts to a Turkish distributor was fine, because the distributor then resold to Iran. The German company's bank froze their account after a single wire referenced “Tehran.” The bank compliance officer saw the word and triggered a freeze. It took weeks to unfreeze.

Humanitarian Exceptions – The Tricky Part

OFAC does allow some exceptions for food, medicine, and medical devices. But the reality is harsh. Many banks won't touch even humanitarian transactions because of the compliance burden. I've heard stories of cancer patients in Iran unable to receive US-made chemotherapy drugs because the payment processing got stuck. The exceptions exist on paper but are nearly impossible to execute.

Real-World Impact on Businesses

If you're in trade, finance, or logistics, ignoring Iranian sanctions can cost you millions. Here's a typical scenario:

Case study: A Swiss chemical exporter

The company sold industrial solvents to a UAE-based distributor. The distributor's owner had an Iranian last name. The Swiss company didn't run proper screening. Two years later, OFAC fined them $2.3 million for “causing US dollars to be processed through US banks in connection with Iranian-origin goods.” The insight? The solvents were produced in Europe, but the payments cleared through New York correspondent banks. That triggered jurisdiction. The Swiss compliance officer told me they never imagined a purely European transaction could violate US law.

This is why sanctions compliance is not just about checking names. It's about transaction mapping – knowing every bank, every currency, every intermediary.

Common Compliance Pitfalls (and How to Avoid Them)

Over the years, I've seen the same mistakes again and again:

1. Relying only on SDN lists

Full blocking sanctions go beyond SDNs. The entire country is blocked. So even if a company's name doesn't appear on the SDN list, doing business with any Iranian entity (unless licensed) is prohibited. I've seen firms proudly say “we checked the list, no match!” while they were shipping directly to Iran. Oops.

2. Ignoring “secondary sanctions”

OFAC can sanction non-US persons for facilitating trade with Iran, even if no US nexus exists. For example, a Chinese bank processing payments for Iranian oil might be cut off from the US financial system. This is “secondary sanctions.” Many European businesses underestimate this risk.

3. Assuming “general licenses” cover everything

OFAC issues general licenses that authorize certain activities (e.g., export of agricultural commodities). But the conditions are strict. One common error: thinking a general license allows direct banking transactions, when actually financial institutions still require a specific license. Always read the fine print.

4. Not screening beneficial owners

You screen the counterparty, but what about the ultimate owner? I recall a case where a UK company signed a distribution agreement with a firm in Malaysia. The Malaysian firm was fully owned by an Iranian national living in Iran. Boom – violation. OFAC expects you to look through corporate structures.

To avoid these, build a compliance program that includes:

  • Automated screening of all parties, including owners and directors.
  • Blockchain/transaction monitoring for Iranian-linked SWIFT messages or IP addresses.
  • Training for sales teams – they're often the weakest link, promising “no problem” to customers without knowing the law.

Frequently Asked Questions

Can I sell software to a hospital in Tehran if it's for medical use?
Technically, medical software might fall under humanitarian exceptions, but in practice it's nearly impossible. The software likely contains US-origin code, and getting a specific OFAC license takes months. Even with a license, banks often refuse to process payments. My advice: assume it's blocked unless you have written confirmation from OFAC. Don't trust generic “general license” interpretations.
My company is based in Canada. Do OFAC sanctions apply to me?
If you have any US nexus – US dollar transactions, US goods, US employees, or even a US server – then yes. Canadian companies regularly get caught because they use US banks for clearing. Even if you have zero US contact, you risk secondary sanctions if you deal with Iran in a “sanctionable” way (e.g., petroleum exports). I've seen Canadian mining firms lose their US bank accounts overnight after a single Iranian-related transaction.
What is the difference between OFAC full blocking sanctions and the EU's Iran sanctions?
EU sanctions on Iran are less strict. The EU blocks arms trade and certain dual-use items, but allows many normal trade activities. OFAC's full blocking is a total ban. The conflict arises when a European company does business with Iran legally under EU law but violates US law. I had a client in Italy who thought they were safe because they had an EU license. OFAC didn't care. They ended up on the SDN list for “significant transactions with Iran.”
Can I travel to Iran for a conference if I work for a US company?
Generally, US persons are prohibited from traveling to Iran for business without a license. Tourism is allowed under a general license, but attending a conference could be considered “providing services” to Iran. I've seen academics get into trouble for giving a lecture at Tehran University without prior authorization. Check OFAC's “Travel Services” FAQ – it's nuanced. When in doubt, apply for a specific license.

This article was fact-checked against current OFAC regulations and reflects my personal experience in sanctions compliance. Regulations change; always consult a specialist.