Dabiq, Syria
town in Syria

Dabiq (Arabic: دابق [ˈdaːbiq]) is a town in northern Syria, about 40 kilometres (25 mi) northeast of Aleppo and around 10 km (6.2 mi) south of Syria's border with Turkey. It is administratively part of the Akhtarin nahiyah (subdistrict) of the A'zaz District of Aleppo Governorate. Nearby localities include Mare' to the southwest, Sawran to the northwest, and Akhtarin town to the southeast. In the 2004 census, Dabiq had a population of 3,364. The town was the site of the battle of Marj Dabiq in 1516, in which the Ottoman Empire decisively defeated the Mamluk Sultanate.
In Islamic eschatology, it is believed that Dabiq is one of two possible locations (the other is Amaq) for an epic battle between invading Christians and the defending Muslims which will result in a Muslim victory and mark the beginning of the end of times. The Islamic terrorist group Islamic State believes Dabiq is where an epic and decisive battle will take place with Christian forces of the West, and have named their online magazine after the village. After being driven out of the town of Dabiq by the Turkish military and Syrian rebels in October 2016, IS replaced this publication with a new one named Rumiyah.
History
During Caliph Sulayman's reign (715–717), Dabiq, near the Arab–Byzantine frontier, succeeded Jabiyah's role as the main Umayyad military camp in northern Syria.
Dabiq was visited by Syrian geographer Yaqut al-Hamawi in the early 13th century, during Ayyubid rule.
The public source identifies “Dabiq, Syria” as town in Syria. This brief keeps that definition visible, then builds a research path around Dabiq, Syria and town.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Dabiq, Syria”, the useful work is to connect “town in Syria” to the records capable of establishing context and consequence.
The strongest evidence will usually combine a dated visual record with documents produced by the authority responsible for the place. The source revision retrieved here is dated Sep 3, 2026. The linked authority identifier is Q128731. Authority coordinates are 36.537, 37.268. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2004, 1516 and 2016.
Modern boundaries and familiar names can conceal earlier jurisdictions or structures that do not align with the present site. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “Dabiq, Syria”, its source revision and the description used here.
- Expand the search: follow Dabiq, Syria primary sources, Dabiq, Syria archive and Dabiq research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Dabiq, Syria”?
- Which authority defined the place, boundary or structure at the relevant date?
- Which earlier names or jurisdictions may reveal additional records?
Search terms from this dossier
This entry incorporates text from “Dabiq, Syria” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.