Photo: MODIS Land Rapid Response Team, NASA GSFC, Wikimedia Commons, Public Domain (file photo: satellite view of the Strait of Hormuz region, not from Friday’s reported events).
WASHINGTON / STRAIT OF HORMUZ — Friday, Nov. 6, 2026. President Donald Trump spent Thursday warning that Washington will soon decide whether to “go further” against Iran, while Friday afternoon open-source accounts reported explosions near Qeshm Island, anti-aircraft activity, a hypothesized HIMARS strike, and a “Code 100” military dispersal alert for southern Iran. Separately, reporting described a White House security session that reportedly included Joint Chiefs Chairman Gen. Dan Caine. Those developments are escalation signals. Checked Friday evening, they are not independent proof of a new declared U.S. offensive or a confirmed attack order.
What is confirmed and what is not
Trump told reporters in the Oval Office Thursday that Washington would “make a decision” on whether to “go further” with strikes to ensure Iran’s nuclear program “will never happen again,” adding he would “rather not destroy the rest of the country if possible, but maybe I will have to. You’ll know soon enough,” according to Axios. Axios, citing two U.S. officials, said Thursday’s meeting with national security advisers was Trump’s first Iran session with that group since the Nov. 3 midterms. Options under discussion included new strikes, continued economic pressure, or a deal with significant Iranian concessions. The same report said U.S. Central Command was finalizing preparations for possible major combat operations but had not received a new directive, and that the USS Theodore Roosevelt strike group would be in Singapore from Friday and was not expected in CENTCOM’s area before mid-November.
Still unverified Friday evening: that Iran’s government issued a formal civilian “Code 100” evacuation; that Friday’s reported Qeshm blasts were a U.S. Army/USMC HIMARS strike; and that any White House meeting with Gen. Caine itself equals a decision to attack. Anti-aircraft fire, if accurately reported, does not prove munition type or who fired.
Trump’s decision window and the Caine report
Axios remains the clearest contemporaneous account of Trump’s public line and the options under review. Separately, Yeshiva World reported Nov. 5 that Trump was holding a White House security briefing with Gen. Dan Caine and other officials, citing West Wing arrivals that “reportedly” included Caine and saying the session was “believed” related to Iran. That is reported imagery and inference, not a published White House schedule confirmation of the agenda. A senior-officer visit amid an ongoing war signals deliberation, not an execute order. Readers tracking the conflict can follow the Iran war tracker and the domestic politics hub at Iran news.
Iran International: U.S. official urges civilians away from IRGC sites
In a Nov. 6 report (20:26 GMT, updated 21:53 GMT), Iran International said a U.S. military official speaking to the outlet urged Iranian civilians to remain indoors and stay away from Islamic Revolutionary Guard Corps positions “if military tensions escalate.” Iran International attributed to that official claims that the IRGC was placing weapons and command centers in residential areas, that leaders were “hiding in fortified facilities and underground bunkers,” and that “the safest place for Iranian civilians during heightened tensions is inside their home.” Those quotes are Iran International’s interview reporting, not a Pentagon press release. The piece linked the warning to Iran International’s earlier March investigation of military use of civilian sites and noted Iranian officials deny human-shield allegations.
Iran International also wrote that Trump said Friday talks with Iran were ongoing and that Qatar’s prime minister urged a “good” rather than perfect deal. Other Reuters, Bloomberg, Axios, or Financial Times strands summarized in that article should be credited to those original outlets. Diplomatic pressure around Hormuz also intersects the economic warfare picture tracked across World News.
Qeshm reports: AAA from Osint613, HIMARS hypothesis from Osinttechnical
At 4:09:26 p.m. ET, open-source account Osint613 (@Osint613) posted that “4 explosions were just heard on Qeshm Island,” that a surface-to-air missile was “being reported” launched, and that “AAA activity [was] recorded as well,” credited to contributor @BeamTracker_ (post). Unverified claim, Osint613 (unverified social / OSINT) Those claims could not be independently verified through wire services the same hour. Earlier Friday (9:05:34 a.m. ET), Osint613 relayed an IRGC claim that a U.S. MQ-1 was downed over Qeshm and noted it “has not been independently confirmed” (post). Unverified claim, IRGC (Iranian military / party to the conflict)
@Osinttechnical at 4:55:11 p.m. ET cited “Explosions, missile launches, and an airstrike on Qeshm Island after Iranian forces reportedly fired at a drone … overnight” (post). Unverified claim, Osinttechnical (unverified social / OSINT) At 5:00:45 p.m. ET, replying to itself, the same account wrote that “Local media indicates that it may have been a missile strike from an Army/USMC HIMARS” (post). “May have been” and “local media” are not U.S. confirmation of a HIMARS attack.
Early-week context: Reuters reported limited U.S. “defensive” Qeshm strikes around Nov. 2 after Iranian surface-to-air missile use against U.S. assets, with Iranian state media IRNA reporting explosions. Claim by IRNA (Iranian state media); confirmed by Reuters That establishes recent fighting near the island; it does not authenticate Friday’s HIMARS hypothesis.
Shin’s “Code 100” — military dispersal, not a confirmed civilian evacuation
At 4:50:12 p.m. ET, Shin (@hey_itsmyturn) posted: “Code 100 [Highest level of alert] issued for evacuation and dispersal for southern provinces of Iran,” marking a “[Delayed Post via FromIran · 120-second delay]” (X post; FromIran incident). Unverified claim, Shin / FromIran (unverified social / subscription feed) The public FromIran title was “Military movement alert” (published 4:48:11 p.m. ET); the full report is paywalled, so underlying sourcing beyond Shin’s public summary could not be independently verified. At 4:51:36 p.m. ET, Shin added: “As explained before: this is for military forces” (post). If accurate, that points to military evacuation or dispersal — not a corroborated general civilian evacuation of southern provinces. Shin’s bracketed gloss “Highest level of alert” is Shin’s characterization, not a confirmed Iranian government communiqué.
Bottom line: Trump’s decision rhetoric, adviser meetings including a reported Caine visit, CENTCOM readiness without a confirmed execute order, Iran International’s civilian-warning interview, and Friday’s Qeshm and Code 100 open-source cluster show heightened tensions. They do not confirm a new major U.S. offensive, a verified HIMARS strike on Friday, or an official countrywide civilian Code 100 evacuation. Osint613 also relayed a Yedioth Ahronoth contingency about possible Israeli Lebanon operations if Iran fighting resumes (post) — contingency reporting, not proof that front has reopened.
Sources
- Axios — Trump meets national security team; Iran war decision coming “soon”
- Iran International — U.S. urges Iranians to stay away from IRGC positions if tensions escalate
- Yeshiva World — reported Trump–Caine White House security briefing
- Reuters — U.S. ‘defensive’ strikes on Qeshm Island (early-week context)
- Shin — Code 100 post · Shin — military forces clarification · FromIran incident
- Osint613 — Qeshm explosions / SAM / AAA · Osinttechnical — “may have been” HIMARS
Read next in Iran
Most read this week
- Abdul El-Sayed and the Muslim Brotherhood Claims: What’s Confirmed and What Isn’t
- Stock Futures Erase a 2.4% Overnight Drop as Markets Digest Democrats’ Sweep of Congress
- Spain Transport Minister Óscar Puente Quits 26 Days Before Election Over Crash That Killed 69
- GM Korea’s Sales Jump 26.6% on Chevrolet Exports as Hyundai Slips 6.3% and Korean Factory Growth Cools
- Boston Plans to Close 3 Schools in 2028 as Enrollment Drops as Much as 58%
Latest
- Business Report: Payrolls Jump 165,000 as Nasdaq Rebounds 1% After AI Rout, Nov. 6, 2026
- Ravens Finalize Brissett Trade After Third Straight 20-Point Blowout
- Hinojosa’s Data Center Moratorium Pledge Jolts Chip Stocks
- Apple Cuts Engineers’ Daily AI Cap From $300 to $200
- Google Commits $17 Billion to First Wyoming Data Center Near Cheyenne