stopmurderingjournalists.com

Stop Murdering Journalists presents an explicitly advocacy-driven, pro-Palestinian viewpoint that accuses Israel of carrying out what the site calls "the worst journalist mass-murdering spree in human history." Its homepage states plainly that "Israel is on a journalist mass-murdering spree." Readers should treat the site as campaign and memorial material rather than neutral news reporting, and should verify individual cases against independent sources before citing them.

How the framing shows up on the page

The site's language choices signal its stance before a reader reaches any data:

• "Mass-murdering spree" — the central claim is stated as fact in the site's own voice, not attributed or hedged.
• "Journalist martyrs" — victims are described with a term of reverence, which frames the dead as casualties of a cause rather than as subjects of a neutral incident log.
• A single accused party — the framing attributes the killings to Israel as a pattern, rather than presenting each death as an individually investigated case with identified responsibility.

This is the vocabulary of a memorial and human-rights campaign, not of a wire service. That does not automatically make the underlying records wrong, but it does mean the site is arguing a case.

What the site actually contains

Beneath the headline claim, the site functions as a filterable database of individual deaths. The visible structure includes:

Each record follows a short pattern, for example: "Hossam Zidan | حسام زيدان — Killed by an Airstrike at home — Lebanon — 28 May 2026," or "Amal Shamali | أمال شمالي — Killed by Tank or Mortar Fire at home — Gaza — 9 Mar 2026." Some entries note "at home"; others do not. The weapon field sometimes reads "Unknown Weapons," which indicates the site is not claiming certainty in every case.

How to read it critically

Because the site is making an accusation, the useful question for a reader is not whether the framing is sympathetic but whether each record holds up. Practical checks:

1. Pick a specific entry and search the journalist's name in English and Arabic against established press-freedom trackers and news archives.
2. Note the weapon classification. "Unknown Weapons" entries carry less evidentiary weight than "Airstrike" entries, and neither tells you who fired.
3. Check the date against known events. A death dated to a period of active hostilities is easier to corroborate than one in a quiet month.
4. Separate the count from the claim. A database of 368 names is a list; the assertion that they constitute a deliberate mass-murder campaign is an interpretation the site supplies, not something the list itself proves.

Who the site is for

The site is built for readers already sympathetic to its framing — people looking for a memorial, a campaign resource, or a name-by-name record to share. It is not structured as a neutral reference: there is no visible methodology page in the supplied material, no sourcing notes per entry, and no statement of how deaths were verified or attributed. A reader who wants a defensible citation should use the site as a starting point for names and dates, then confirm each case through independent reporting and press-freedom organizations that publish their methodology.

The Stop Murdering Journalists database lists journalist deaths from October 2023 through dates shown as late as September 2026, and its location filter covers Gaza, Lebanon, the West Bank, Yemen, Iran, and Syria. The site states that the view shows "all 368 journalist martyrs in the database," so the list is a cumulative record rather than a rolling recent-events feed. The most recent entries visible in the excerpt are dated 30 September 2026 (Gaza) and 28 May 2026 (Lebanon), while the earliest month offered in the filter is October 2023.

Time Range: What the Dates Show

The month filter runs continuously from October 2023 to September 2026, which tells you the site intends to cover the whole period since late 2023, not just a recent window. Entries in the excerpt are not strictly chronological in display order, so the top of the list is not necessarily the newest death. Examples of the spread:

Two practical points follow. First, because future-dated entries appear (2026), the list is updated over time and the "current" end of the range depends on when you view it. Second, the filter's month list is the most reliable way to see the full span; scrolling the entries alone can mislead you about what is newest.

Regions: What Each Location Covers

The location filter offers six options, and the excerpt shows entries for at least four of them:

• Gaza — the largest share of visible entries, mostly airstrikes, with some tank or mortar fire.
• Lebanon — numerous entries, often airstrikes described as "at home."
• West Bank — fewer visible entries; at least one attributed to "unknown weapons."
• Yemen, Iran, and Syria — available as filter options, though the excerpt does not show individual entries for them.

If you need a count per region, use the location filter one at a time rather than reading the combined list; the excerpt does not give per-region totals.

How Complete Is the List?

The site presents the 368 figure as the total in its database, which is the number to cite if you are describing the site's own scope. Completeness in the sense of independent verification is a separate question: the entries record name, date, location, and a stated cause (airstrike, tank or mortar, small arms, or unknown), but the excerpt does not show sourcing or methodology for each case. Treat the list as the site's documented record, and check individual entries against other reporting if you need corroboration.

Checking the Range Yourself

1. Open the database view and confirm the total shown (the excerpt states 368).
2. Use the Month filter to select October 2023 and then the latest available month; this brackets the time range.
3. Use the Location filter one region at a time to see which regions actually have entries, rather than assuming all six do.
4. Use the Weapon filter to separate airstrike deaths from tank/mortar, small arms, and unknown causes.

The main pitfall is assuming display order equals chronology, or that every filter option has entries behind it. Verify both with the filters before drawing conclusions about recency or regional spread.

Each record in the Stop Murdering Journalists database identifies a journalist by name in English and Arabic, then states where they were killed, the weapon or cause listed, the date of death, and gender. The site presents these as filterable fields above a running list of entries, and its current count is 368 journalist martyrs.

The fields in a single record

Every entry follows the same short format. Using one listed record as an example:

The name appears first in Latin script, followed by the Arabic form. The cause is written as a phrase beginning "Killed by…", and the location and date close the entry. Gender is not printed in the visible line but is one of the database's filter categories, so it is recorded per person.

How the database is organized

The page is built as a filterable list rather than a set of narrative profiles. Five filter groups sit above the entries:

• Location — All Locations, Gaza, Lebanon, West Bank, Yemen, Iran, Syria
• Weapon — All Weapons, Airstrike, Unknown, Tank or Mortar, Small Arms
• Month — a month-by-month range running from Oct 2023 through Sep 2026
• Gender — All Genders, Male, Female
• Apply Filters — the control that runs the selection

Selecting values in these groups narrows the list; the default view shows all 368 records. This means the same person can be found by place, by cause, by date, or by gender, and combinations of filters (for example, airstrikes in Lebanon in a given month) produce a subset.

What the cause field captures

The weapon categories are broad, not forensic. "Airstrike" is the most common label in the visible entries. "Tank or Mortar" appears, for instance, in the record for Amal Shamali, killed at home in Gaza on 9 Mar 2026. "Unknown" is used where the cause is not established, as with Marwan Harzallah in the West Bank on 28 Mar 2026 and Yahia Barzaq in Gaza on 30 Sep 2025. "Small Arms" is a listed category even though it does not appear in the excerpted entries. Some airstrike records add "at home," indicating the strike hit a residence — for example, Hossam Zidan in Lebanon on 28 May 2026 and Mohammad Sherri in Lebanon on 18 Mar 2026.

What the location field captures

Location is recorded at the country or territory level: Gaza, Lebanon, the West Bank, Yemen, Iran, or Syria. The visible entries skew heavily toward Gaza and Lebanon, with the West Bank appearing less often. No city or district is given in the record line itself.

What the date field captures

Each record carries a single day, month, and year. The filter's month list spans Oct 2023 to Sep 2026, and the visible entries fall across that range — from Oct 2023-era records through late 2025 and into 2026. Dates are the basis for the month filter, so a reader can pull, say, all entries from March 2026.

Reading a record correctly

A few conventions matter if you plan to cite or count from the database:

1. The cause is a category, not a finding. "Airstrike" or "Unknown" reflects how the site classifies the death, not an independent investigation. Treat the label as the site's attribution.
2. "At home" is a location detail, not a separate field. It sits inside the cause phrase and signals a residential strike.
3. Names are given in two scripts. Use the Arabic form when matching against Arabic-language sources; transliterations of the English form vary.
4. Gender is filterable but not shown in the line. To count by gender, apply the filter rather than reading entries.
5. The total is a live count. The page states 368 journalist martyrs at the time of the excerpt; filtering changes the number shown, so record the filter state alongside any figure you quote.

Where the records come from

The site's own framing is that Israel is committing "the worst journalist mass-murder spree in human history," and the database is presented as documentation of that claim. The records themselves are structured facts — name, place, cause, date — while the framing is the publisher's. For a reader who wants the underlying data rather than the argument, the filterable list is the usable part: it lets you isolate a location, a weapon type, a month, or a gender and see the matching names and dates.

The site's database page lets you narrow the list of 368 recorded journalist deaths using four filters — Location, Weapon, Month, and Gender — which you combine and then confirm with an Apply Filters action. This is useful when you want to look at one country, one type of weapon, one time window, or one gender rather than the full list. The filters are dropdown-style selectors shown above the victim entries; the page does not describe any saved searches, export options, or login requirement, so treat it as a browsing tool for the on-page list.

What each filter controls

Each filter starts at its "All" setting, which is the unfiltered view. The month list is not continuous in the visible data — it runs from October 2023 to September 2026 but skips some months, so only months that appear in the dropdown can be selected.

Step-by-step: narrowing the list

1. Open the database view. The victim list appears under the heading "Stop Murdering Journalists," with the filters directly above the entries.
2. Set Location. Choose a single place, such as Gaza or Lebanon, or leave it at All Locations.
3. Set Weapon. Choose Airstrike, Tank or Mortar, Small Arms, or Unknown. Leave it at All Weapons to include every cause.
4. Set Month. Pick one month from the dropdown, or keep All Months.
5. Set Gender. Choose Male or Female, or keep All Genders.
6. Apply the filters. Trigger the Apply Filters action. The list below should refresh to show only entries matching every condition you set.

Expected result: a shorter list of victim entries, each showing a name in English and Arabic, the weapon that killed them, the location, and the date. For example, selecting Lebanon plus Airstrike plus April 2026 should return entries such as Amal Khalil (22 Apr 2026), Ghada Dayekh (8 Apr 2026, at home), Suzan Khalil (8 Apr 2026, at home), and Mohamed Washah (8 Apr 2026, Gaza — which would not appear if Location is set to Lebanon).

How the filters combine

The filters work together as an intersection, not a union: a victim must match every filter you set. Setting Location to Gaza and Weapon to Airstrike returns only Gaza victims killed by airstrikes, not all Gaza victims plus all airstrike victims elsewhere. This matters when a month has entries across several countries — March 2026, for instance, includes Lebanon, West Bank, and Gaza entries, so adding a Location filter is the fastest way to isolate one country's records for that month.

A practical sequence for a narrow question is to start with the most restrictive filter (usually Month or Location), apply it, then add the next filter and apply again. That way you can see how many entries each added condition removes.

Common sticking points

• Nothing changes after selecting options. The list only updates after the Apply Filters action is triggered; changing a dropdown alone does not refresh the results.
• A month you expect is missing. The Month dropdown only lists months present in the data. If a month is absent from the list, there are no records for it in the database, so it cannot be selected.
• "Unknown" is a real weapon category. If you filter by Weapon, note that Unknown is a separate option from Airstrike and the others. Victims recorded with an unclear cause will not appear under a specific weapon filter.
• "At home" is not a filter. Some entries note that the killing happened "at home," but this appears in the entry text, not as a selectable filter. To find those cases, filter by location and month, then read the individual entries.
• Gender and location interact. Filtering by Female and a single location returns only women recorded in that place; if the result is empty, widen the month or location rather than assuming the data is wrong.

What the filtered list shows you

Each result gives a name in Latin and Arabic script, the weapon, the location, and the date of death. That combination is enough to answer questions like "which journalists were killed in Lebanon by airstrikes in the first half of 2026" or "how many entries are recorded for Gaza in January 2026." The page presents the database as a record of journalist deaths attributed to Israeli action across Gaza, Lebanon, the West Bank, Yemen, Iran, and Syria, with dates running from October 2023 onward.

Stop Murdering Journalists (stopmurderingjournalists.com) is an advocacy website that documents journalists killed across Gaza, Lebanon, the West Bank, Yemen, Iran and Syria. Its central feature is a browsable database of 368 named victims, each entry recording location, weapon type, date and gender. The site frames these deaths as a mass-killing campaign rather than isolated incidents. It is useful if you want to look up a specific journalist, scan casualties by country or time period, or understand the site's claim before deciding whether to cite or share it.

What the site contains

The homepage opens with a single assertion — that Israel is committing "the worst journalist mass-murder spree in human history" — and then moves directly into the database. There is no separate about page, methodology section or sourcing note visible in the page content, so the records themselves are the substance of the site.

Each victim entry follows the same pattern:

• Name in both English and Arabic, e.g. "Muhammad Al-Najjar | محمد النجار"
• Cause of death as a weapon category, e.g. "Killed by an Airstrike," "Killed by Tank or Mortar Fire," "Killed by Unknown Weapons," "Killed by Small Arms"
• Location, e.g. Gaza, Lebanon, West Bank
• Date of death, e.g. 30 Sep 2026
• Gender, available as a filter

Some entries add a detail about where the person was killed — several Lebanon records note "at home."

How to browse and filter

The database is organized around four filters, each with an "All" default:

To use it, set one or more filters and apply them; the list narrows to matching records. The default view returns all 368 entries, newest first — the top of the list shows deaths dated September 2026 and works backward.

What the records show at a glance

Scanning the unfiltered list gives a rough sense of the pattern the site is presenting:

• Airstrikes dominate the weapon categories in the visible entries, with tank or mortar fire and "unknown weapons" appearing less often.
• Lebanon and Gaza account for most recent entries, with a dense cluster of Lebanon deaths in March, April and May 2026, and Gaza deaths spread across late 2025 and early 2026.
• Dates extend into the future relative to most readers' present — entries run through September 2026 — so treat the timeline as the site's own record rather than a verified historical sequence.

What to keep in mind before relying on it

The site is a campaign resource, not a neutral registry. Its framing is stated outright in the opening line, and the page provides no visible citations, sourcing methodology or correction process. That does not make the names unusable, but it does mean you should treat each entry as a claim to verify rather than a settled fact.

Practical checks before citing or sharing an entry:

1. Cross-reference the name and date against reporting from established press-freedom organizations or news outlets covering the same incident.
2. Note the weapon category — "Unknown Weapons" entries carry less specificity than "Airstrike" ones.
3. Check the date against your own timeline, since the database includes months beyond the current period.
4. Attribute the figure of 368 to this site specifically rather than presenting it as an independently confirmed count.

Who it is for

The site suits readers who want to look up whether a particular journalist appears in this record, see how the site groups casualties by country and cause, or evaluate the claim it makes before deciding whether to reference it. It is less suited to anyone needing a sourced, methodologically documented dataset — for that, the names here are a starting point for verification, not an endpoint.