Every number on this page is read from the scoring code that runs the site, so it always matches the scores you see.
Each report gets a score from 0 to 100 when it is collected. It is a ranking, not a probability: it says how strongly the headline points to a security event that is happening or about to happen at a place we watch, how trustworthy the source is and how many outlets carry it. The site treats stories scoring 15 or more as Important, and 25 or more as hot: shown in red and eligible to be sent as an alert. A story's score is the score of its strongest report.
The score starts at 0. Each step either adds points or multiplies the running total, in this order. The words are read from the headline and the first 500 characters of the article; reports in other languages are translated to English first.
| Step | What it does | Number |
|---|---|---|
| Severity | Threat words, by category (table below): the category's weight for each matching word, up to 3 words per category. Each term from the server's watch list (IRGC, Hezbollah, Houthi, Home Front Command, CENTCOM, NOTAM, Fordow, Natanz, hijack, squawk 7500, El Al, Ben Gurion) adds 4. | +weight × words |
| Timing | A threat category (Aviation, Civil-defence warning, Hijacking & hostages, Military buildup, Nuclear, Strikes & weapons, Threats & warnings) together with a near-term timing cue (tonight, within hours, next week) multiplies the score. Not for investigations, politics, plans or rhetoric. | ×1.5 |
| Timing cues | Each timing cue in the text adds points (table below). | +0 to +3 |
| Place | Names a watched place: points, then a boost. | +2, then ×1.4 |
| Names only places outside the watch list. | ×0.75 | |
| Names no place at all: probably off-topic. | ×0.6 | |
| Format | Analysis, explainer, opinion or live page; a plan with a distant or conditional horizon; rhetoric; an investigation or trial; politics; an anniversary piece. See section 5. | ×0.2 to ×0.6 |
| Source reliability | Every source has a rating from 0 to 1. The multiplier is 0.6 + 0.8 × rating. | ×0.6 to ×1.4 |
| Corroboration | Each extra outlet carrying the story when it is scored adds 0.15, counting up to 7 outlets. | ×1 to ×1.9 |
| Collector weight | A few feeds that repeat whole pages (travel advisories, digests) carry a weight below 1 set in the configuration. | ×weight |
| Recency | Published more than 2 days before it was collected. | ×0.5 |
| Critical event | A flat bonus for events that must never be buried (the alert line is 25): the first critical report about a place in 12 hours gets it. Not for analysis or investigations. | +30 |
| Cap | The score never goes above 100. | ≤ 100 |
Words match as written in the report, in English. A few of each category's words:
| Category | Weight | Example words |
|---|---|---|
| Strikes & weapons | 3 | airstrike, air strike, missile, ballistic |
| Violence | 2 | strike, strikes, attack on, attacks on |
| Military buildup | 3 | mobiliz, reservists, call-up, troop buildup |
| Civil-defence warning | 2.5 | travel advisory, do not travel, leave the country, shelter |
| Threats & warnings | 2 | ultimatum, red line, red lines, declaration of war |
| Diplomacy | 1 | ceasefire, truce, negotiation, talks |
| Nuclear | 3 | enrichment, uranium, nuclear facility, nuclear test |
| Aviation | 3 | squawk 7500, 7500, emergency landing, forced landing |
| Hijacking & hostages | 3 | hijack, hostage, hostages, kidnap |
| Military air activity | 2.5 | refuelling aircraft, refueling aircraft, aerial refuel, strategic bomber |
| Shipping & maritime | 2 | tanker, shipping, vessel seized, boarded |
| Cyber | 1.5 | cyberattack, cyber attack, ddos, hackers |
| Unrest | 1.5 | protest, demonstration, riot, general strike |
| Explosions reported | 8 | — |
| Economy | 1 | oil price, brent, crude, insurance premium |
Explosions reported is not a word list: it is a report of explosions heard at a watched country (“Explosions heard in Sirik”). It gets the category weight but not the critical bonus, because a single report is a claim; independent confirmation (section 4) can take it over the alert line.
| Cue | Points | Counts as near-term |
|---|---|---|
| Near-term timing (tomorrow, within days) | +2 | yes |
| Named day ahead | +2 | yes |
| Imminent wording | +3 | yes |
| Scheduled event | +1 | no |
| Mentions a date | +0.5 | no |
| Anniversary | +0 | no |
This server watches: Israel, Iran, Lebanon, Gaza, Judea and Samaria, Syria, Iraq, Yemen, Jordan, Saudi Arabia, UAE, Qatar, Egypt, Turkey, Strait of Hormuz, Red Sea / Bab el-Mandeb. Whole regions watched as well: Europe.
Anywhere: a hijacked aircraft or ship, squawk 7500, an aircraft shot down, missiles or drones hitting an airport, airliner, embassy or nuclear plant, ships attacked according to UKMTO, attacks on oil and gas sites, ballistic missiles fired at a target, a nuclear test, a declaration of war, a chemical or dirty-bomb attack, attacks toward Mecca or Medina. Only at the watched places listed above, not across whole regions, because elsewhere the same words are routine: ships struck, fired on or seized, interceptions of drones or missiles, strikes on bases and ports, sirens sounding, named nuclear sites hit. The headline must describe the event itself: anniversaries, archive pieces, films and commentary are excluded.
These two headlines are scored live by the same code, as reports from a source rated 0.8, carried by one outlet. The “What counted” column is what the scoring records, word for word; the same table appears under “Why this score?” on every story.
| Step | What counted | Effect | Running total |
|---|---|---|---|
| Severity | kinetic: struck, projectile | +6 | 6 |
| Severity | maritime: tanker | +2 | 8 |
| Place | names a watched place (Strait of Hormuz) | +2 | 10 |
| Place | watched-place boost | ×1.4 | 14 |
| Source reliability | source reliability 0.80 | ×1.24 | 17.4 |
| Corroboration | 1 outlet when scored | ×1 | 17.4 |
| Critical event | critical event: tanker struck | +30 | 47.4 |
| Final score — hot: marked red and can be sent as an alert | 47.4 | ||
| Step | What counted | Effect | Running total |
|---|---|---|---|
| Severity | kinetic: strikes on | +3 | 3 |
| Severity | violence: strikes | +2 | 5 |
| Place | names a watched place (Iran) | +2 | 7 |
| Place | watched-place boost | ×1.4 | 9.8 |
| Format | a reported plan or option with a distant or conditional horizon, not an event | ×0.5 | 4.9 |
| Source reliability | source reliability 0.80 | ×1.24 | 6.1 |
| Corroboration | 1 outlet when scored | ×1 | 6.1 |
| Final score — below Important: shown under All only | 6.1 | ||
The first reports an event at a watched place and gets the critical bonus. The second names a watched place and strike words, but reports a plan, not an event, so it is halved and stays far below Important.
Outlets are the distinct news outlets carrying a story. The more there are when a report is scored, the higher it scores (step “Corroboration”).
Independent origins are what actually confirms a story. Ten outlets re-running one wire agency's report are one origin, and an outlet whose headline shares 80% or more of its words with a report already counted is a copy. Wire agencies recognised by their credit line: AFP, Anadolu, ANI, AP, Bloomberg, dpa, Fars, IRNA, Kyodo, PTI, QNA, Reuters, SPA, Tasnim, TASS, WAFA, WAM, Xinhua, Yonhap. “Why this score?” on each story shows both numbers: “Sources: 9 outlets, 3 independent”.
Confirmation. A report is scored once, when it arrives. When a story reaches 3 independent origins (counting its reports from the last 48 hours), its 5 strongest reports are scored again with the number of origins as the outlet count, and may now cross the alert line. This applies only to events at watched places (Aviation, Civil-defence warning, Critical event, Explosions reported, Hijacking & hostages, Military air activity, Nuclear, Shipping & maritime, Strikes & weapons), not to rhetoric, protests, talks or economic news. A score is only ever raised this way, and the critical bonus is not given a second time.
The tension index (0–100) says how much is happening at a place right now. It adds up the scores of the stories that name the place, giving the last few hours the most weight.
| Hours ago | Counts as |
|---|---|
| 0 | 40 |
| 3 | 20 |
| 6 | 10 |
| 12 | 2.5 |
Scale. A few places carry far more news than the rest, so the sum is scaled logarithmically: index = 100 × log(1 + sum) / log(1 + 1000), and a sum of 1000 or more is 100.
| Decayed sum | Index |
|---|---|
| 5 | 26 |
| 25 | 47 |
| 100 | 67 |
| 300 | 83 |
| 1000 | 100 |
| Level | Index |
|---|---|
| Critical | 80–100 |
| Severe | 60–79 |
| High | 40–59 |
| Elevated | 20–39 |
| Calm | 0–19 |
Trend. The sum for the time window you chose is compared with the window just before it: rising when it is more than 1.3× the earlier one, falling when the earlier one was more than 1.3× it, “new” when the earlier window had nothing. Each place lists its 3 strongest stories.
3-day comparison. The last 3 days are split into rolling 24-hour windows, each summing its stories' strongest scores. The last 24 hours are compared with the average of the 2 days before: 1.3× or more is rising, 0.77× or less is falling.
◆ About to happen. A story counts as about to happen when it has a near-term timing cue (tonight, within hours, next week, by Friday, “imminent”, “preparing to”) and a category from Civil-defence warning, Military air activity, Military buildup, Strikes & weapons, Threats & warnings. The cue must be in the headline, unless the story scores 25 or more and 2 or more outlets report it. Politics never counts, and plans and rhetoric carry no near-term cue.
OSINT Swarm is an automated reading of public reports: news feeds, Telegram channels and open data, read by fixed word rules and partly machine-translated. It does not verify events on the ground. It can miss events, score a story too high or too low, and raise false alarms. A score ranks reports against each other; it is not the probability that something will happen.
It is not an official warning system. In Israel, follow the Home Front Command (Pikud HaOref) and official channels for civil-defence instructions.
Scores are automated estimates, not advice. Any use of them is at your own responsibility: see the terms of use.
Questions or a score that looks wrong: [email protected].