OSINT - Cities with hundreds of names | How OSINT investigators miss hidden clues
- Nico Dekens | dutch_osintguy
- 4 days ago
- 10 min read
You think you know Amsterdam?
You don’t.
Even I, born and raised in Amsterdam, don't know.
If you’re an investigator, analyst, or journalist working digital cases around Europe (or globally), and you’re only searching for “Amsterdam” in your datasets, you’re already blind to half the internet.

Because Amsterdam doesn’t just live as Amsterdam.
It is a city that hides behind a hundred aliases.
In this blog I will focus on Amsterdam because its close to home. But please read this blog as if it was your city. Many cities will have many aliases that you might know but also many that you may have never heard of about.
This post is a guide how language masks location, how alias awareness unlocks hidden signals, and how to wire Boolean + regex to catch them across open web, social media, and the dark web.
Cities With Many Faces
In any OSINT investigation, words matter. Especially the words people use to not say something directly.
Amsterdam is one of the most multilingual, multicultural, and symbolically loaded cities on the planet. It’s referenced in memes, rap lyrics, Telegram chats, darknet listings, graffiti, flight logs, and tourism posts, all with completely different vocabularies.
From Mokum to 020, from Venice of the North to The Red Zone, the Dutch capital wears more masks than any other European city.
So if your keyword lists, alert systems, or (AI) monitors only look for “Amsterdam” you’re missing Mokum’s entire shadow world.
How You’re Missing the Signal
Let’s get tactical.
Imagine you’re monitoring extremist chatter about upcoming protests in the Netherlands.
Someone writes on Telegram:
“Meet at the Dam. Bring the banner.”
You might flag that “Dam” clearly means Dam Square.
But what if someone writes:
“020 crew meeting tonight, same place.”
“Freedom City calling again.”
“Dropping gear near Mokum North.”
Most systems won’t catch that, because they’re not built to think like locals.
That’s where tradecraft comes in.
Each alias is a coordinate in language space. Miss the coordinate, miss the movement.
• “020 crew tonight” → likely Amsterdam meet-up
• “Drop near Mokum North” → logistics in Amsterdam-Noord
• “Freedom City calling” → activism wrapped in symbolism
• “A-Base secure” → coded reference to Amsterdam-based ops
OSINT is semantic situational awareness. Tools don’t replace thinking, they amplify it, assuming you feed them the right vocabulary.
OSINT Blind Spot: When AI Doesn’t Speak Street
Automated keyword lists and large language models are powerful, but they’re not cultural.
They don’t understand that “Mokum Alef” is the same city as “Venice of the North.”
They don’t see that “Zone020” or “A-Base” or XXX-city in darknet chatter refers to Amsterdam’s criminal logistics hub.
When you train models, collect data, or run entity recognition, linguistic diversity is the enemy of lazy automation.
That’s why real analysts build human-informed dictionaries.
The Amsterdam Keyword Intelligence Project
To test this idea, I built a dataset of 136 names, slang, translations, and coded references that all point to Amsterdam, curated from social media, music, dark web slang, street culture, and multilingual contexts.
I turned that into three operational tools:
1. Boolean search list - ready for use in Google, X/Twitter, Reddit, or general OSINT scrapers
2. Regex list for dark web - for pattern-matching in Tor forums, leaks, and underground datasets
3. Combined pipeline list - for Elastic, ShadowDragon, or Python automation
Together, they form a linguistic map of Amsterdam’s digital footprint - from tourist hashtags to trafficking codewords.
1. Common English Variants
1. Amsterdam
2. The Dam
3. Dam City
4. The ’Dam
5. A’dam
6. A-Dam
7. AMS
8. Amstel City
9. Canal City
10. Venice of the North
11. Sin City of Europe
12. The Free City
13. The Capital
14. The Dutch Capital
15. The City of Canals
16. The Northern Venice
17. The Tulip Capital
18. The City of Bikes
19. Freedom City
20. Weed City
2. Dutch / Local Terms & Slang
21. Mokum (most common local slang; Yiddish origin)
22. Mokum Alef (original Yiddish term for “place A”)
23. Dam
24. Centrum
25. De Hoofdstad (literally “The Capital”)
26. De Dam (referring to Dam Square)
27. 020 (Amsterdam’s telephone area code)
28. De 020
29. De Grachtengordel (the Canal Belt, used symbolically)
30. De Pijp (used as a metonym for the city in youth slang)
31. Noord
32. West
33. Zuid
34. Oost
35. Binnen de Ring (“inside the ring road” – used locally for central A’dam)
36. Mokum Town
37. De Mokumse Stad
38. Groot-Mokum (Greater Amsterdam)
3. Translations & Foreign Variants
39. Ámsterdam (Spanish)
40. Amsterdam (French, German, Italian)
41. Амстердам (Russian)
42. أمستردام (Arabic)
43. 阿姆斯特丹 (Āmǔsītèdān, Chinese)
44. アムステルダム (Amusuterudamu, Japanese)
45. 암스테르담 (Ameuseuteldam, Korean)
46. אמסטרדם (Amstardam, Hebrew)
47. Амстэрдам (Amstėrdam, Belarusian)
48. Amstırdam (Turkish variant)
49. Амстэрдам (Bulgarian)
50. Amsterdão (Portuguese)
51. Амстэрдам (Ukrainian)
52. Amsterdamski (Slavic stylized variant)
4. Indirect or Descriptive References
53. Holland’s Heart
54. The City of Tolerance
55. The Port
56. The City of Light (used in graffiti circles, contrasting Paris)
57. City by the Amstel
58. Amstel Town
59. The Water City
60. The Bridge City
61. The Northern Star
62. The City of Sin
63. Red City
64. Red-Light Capital
65. Coffee City
66. The City of Dreams
67. Rainbow City (used by LGBTQ+ travelers)
68. The Smoked City (used in cannabis culture)
69. The Dutch Metropolis
70. The Ganja Capital
71. The Bike Capital
72. The Capital of Vice
73. Canal Metropolis
74. Old Port City
5. Online / Hashtag / Modern Variations
75. #Ams
76. #Mokum
77. #020
78. #DamLife
79. #DamSquad
80. #ADam
82. #Damsterdam
83. #FreeCity
84. #Amstel
85. #CanalLife
86. #InTheDam
87. #TheDamLife
6. Music, Art, and Subculture References
89. Mokum Records (used as cultural identifier)
90. The Scene (Dutch hip-hop term for A’dam)
91. Amsterdoom (metal scene nickname)
92. The Zone (used by underground graffiti artists)
93. Zone020 (graffiti tag shorthand)
94. Mokum Core (hardcore music slang)
95. Mokum Mafia (street slang, not necessarily criminal)
96. The North Hub (trap/hip-hop slang for Amsterdam North)
97. The Damside
98. The Canal Side
99. The Dutch Venice
100. Capital of Sound (DJ culture)
101. Dutch Underground
7. Dark Web / Underground or Coded Usage
102. “A-Base” – coded reference for Amsterdam in darknet forums (observed in Tor contexts)
103. “Base20” or “Zone20” (derived from 020)
104. “Northern Port” – occasionally seen in trafficking or logistics chatter
105. “Tulip Point” – euphemism used in smuggling ops or crypto laundering talk
106. “The Red Zone” – can mean Red Light District, sometimes used in dark web chats
107. “Delta North” – rare coded reference in activist/leftist comms for Amsterdam HQs
108. “M-City” – abbreviated use in Telegram/underground groups
109. “The A Port” – obfuscated version for “Amsterdam Port”
110. “Zone Mokum” – hybrid slang used in graffiti/underground logs
8. Travel, Business, and Institutional Codes
111. AMS (IATA airport code)
112. EHAM (ICAO airport code)
113. AMST (UN/LOCODE abbreviation)
114. NL-AMS (postal/ISO notation)
115. Amstelveen (used sometimes to imply “greater Amsterdam”)
116. Metropoolregio Amsterdam (MRA – government term)
117. Amsterdam-Randstad (common in EU policy and business)
118. North-Holland Capital
119. Greater Dam Area
120. ARA (Amsterdam-Rotterdam-Antwerp port triangle)
9. Creative or Symbolic Phrases
121. The Golden City
122. The City of Merchants
123. The Diamond City (historical reference)
124. The City on the Amstel
125. The Dutch Venice
126. The North Sea Gate
127. The Window City (reference to the Red Light District)
128. Old Mokum
129. Amstel Haven (fictional poetic name)
130. City of Smoke and Water
131. The Floating City
132. The Delta City
133. The Dutch Doorway
134. City of Tolerance
135. Holland’s Gateway
136. The Harbor of the North
The list is available for download as Boolean, Regex and combined list at the end of this blog.
Real-World Applications
Here’s how it changes the game:
1. Terrorism & Extremism Monitoring
A cell might plan to meet “in the Capital” or “in 020.”
If your system only watches for Amsterdam, you’ll miss early indicators of gatherings, planning, or logistics.
2. Human Trafficking & Exploitation
Dark web chatter mentioning “Red Zone” or “Tulip Point” can signal Amsterdam-based movement through the port or Red Light District networks.
Regex pattern matching exposes it.
3. Drug & Arms Logistics
Terms like “Northern Port,” “A-Base,” or “Zone Mokum” often appear in Telegram or Tor markets referencing shipment hubs in or near Amsterdam.
4. Influence Operations
Activists or foreign agents referencing “Freedom City” or “City of Smoke” use symbolic language to invoke Amsterdam’s liberal image - without ever naming it.
Words Are Coordinates
Think about that for a second. Every alias, slang term, or cultural phrase is a coordinate in language space. When you don’t track those, you lose the map.
In OSINT, semantic awareness is situational awareness.
Your job isn’t to scrape everything. It’s to understand what’s being said when it’s not being said directly.
That’s the line between an amateur and a professional analyst. Maybe more importantly it's the line between scratching the surface versus digging deep.
Local Language
Another thing to think about is how a local from that country, area or city would talk. What word(s) would they use to name the city or area they live in?
If we take Amsterdam we know that that is a City in the Netherlands. People speak Dutch in the Netherlands. So your first go to would most likely be the native language most people speak in that country.
But if we take Amsterdam it is also a fact that when you are in the City center most people speak the English language because of the high amounts of tourists visiting the city and expats living there.
Next it is smart to try and understand if a city has certain people living in areas that originate from a different culture or country. For example Amsterdam has certain neighbourhoods and areas where high amounts of people Northern Africa (Morocco) live. They often still speak Arabic with their peers in the physical and digital world. Thinking of this will help you formulate the right keywords in the right language.
Real-World Scenarios (Geo + OSINT)
1) Protest Early Warning (Europe / Netherlands)
Problem: You monitor public order risks.
Missed signal: A Telegram post says, “020 meet, flags only.”
Fix: Your alias list maps 020 → Amsterdam, triggers an alert near Dam Square.
Boolean:
("020" OR "Mokum" OR "A’dam" OR "The ’Dam") AND (meet OR rally OR "bring flags" OR "gather")Action: Cross-reference with transport strikes & weekend fixtures. Overnight you pivot from “no data” to “probable gathering”.
2) Human Trafficking Route (Benelux Triangle)
Problem: Fragmented chatter: “Red Zone needs drivers”, “Tulip Point 3am”.
Fix: Regex mapping Red Zone/Tulip Point → Amsterdam (logistics euphemism) connects posts across two markets and one WhatsApp dump.
Regex:
(?i)\b(red\s+zone|tulip\s+point|northern\s+port|a[- ]?base)\bAction: Overlay detections with Port of Amsterdam cargo movements and short-term rentals in De Wallen (Amsterdam's Red Light district). You now have timing + location + role requests.
3) Narcotics Distribution
Problem: Dark web vendor claims “Northern Port” availability, cross-posted as “Zone020 drop”.
Fix: Alias mapping links Amsterdam stock to Antwerp pickup windows; stock likely in Amsterdam-West warehouses.
Regex:
(?i)\b(zone\s?020|northern\s+port|a[- ]?base)\bAction: Create entity graph: vendors ↔ couriers ↔ drop windows ↔ slang alias clusters. Prioritize nights matching EHAM/AMS cargo spikes.
4) Influence Operations (Symbolic Language)
Problem: Coordinated “Freedom City” posts across multilingual sock puppets/bots.
Fix: Freedom City resolves to Amsterdam in your dictionary: content pushes a protest narrative exploiting the city’s liberal image.
Boolean:
("Freedom City" OR "City of Smoke" OR "City of Tolerance") AND (march OR vigil OR occupy)Action: Attribute clusters by time-zone and language errors; map cross-posting to a single content farm.
Here’s a small sample from the dataset:
Alias | Category | Context |
Mokum | Dutch slang | Historic Yiddish word for “safe place” |
020 | Numeric code | Amsterdam’s phone area code |
A’dam / A-Dam | Slang | Shortened local name |
The ’Dam | English slang | Common among tourists |
Venice of the North | Tourism | Used in official materials |
The Red Zone | Dark web slang | Often references Red Light District |
Tulip Point | Codeword | Used in illicit trade channels |
Zone020 | Graffiti / darknet slang | Tag shorthand for Amsterdam |
The Free City | Cultural | Used in activism and art |
Mokum Core | Music subculture | Hardcore / Gabber scene rooted in Amsterdam |
Now imagine every city having its own lexicon like this.
It’s not just language, it’s intelligence. And please do not forget to translate these words into other languages (Russian, Chinese, Dutch, Spanish, French, Arabic etc. etc.)
How to Use It in Your Workflow
Drop these keyword lists into:
• Your Python OSINT scrapers
• Elastic or Splunk pipelines
• Obsidian note graphs
• Streamlit dashboards
And build Boolean chains like:
("in Mokum" OR "020" OR "A’dam" OR "the ’Dam" OR "De Pijp") AND ("meeting" OR "drop" OR "arrived" OR "photo")Or dark web regex filters such as:
(?i)\b(mokum|020|a['’]?dam|red\s+zone|tulip\s+point|zone020)\bThese hit hidden references to Amsterdam across open web, social media, and dark web layers.
Drop-In Queries You Can Steal
Open Web / Social (Boolean)
("Mokum" OR "020" OR "A’dam" OR "The ’Dam" OR "De Pijp" OR "Amsterdam-Noord")AND (meet OR drop OR rally OR "looking for" OR "arrived in" OR "HQ in")Dark Web / Logs (Regex)
(?i)\b(mokum|020|a['’]?\s?dam|red\s+zone|tulip\s+point|zone\s?020|northern\s+port|a[- ]?base)\bNeighbourhood Pivot (Dutch language - short term renting or storage combined with neighbourhood names)
("Amsterdam West" OR "Amsterdam-Zuid" OR "Binnen de Ring" OR "Grachtengordel")AND (huur OR "korte termijn" OR opslag OR "bezorgen")Multilingual Sweep
("Ámsterdam" OR "Амстердам" OR "أمستردام" OR "阿姆斯特丹" OR "アムステルダム" OR "אמסטרדם")AND ("miting" OR "reunion" OR "القاء" OR "集会" OR "集結" OR "vigil" OR "protesta")Implementation Playbook
1. Ingest the alias list into your pipeline (CSV → Python/Elastic/ShadowDragon Monitor).
2. Tag each hit with the resolved place = Amsterdam + the alias used (for cultural attribution).
3. Cluster by alias family (slang / tourism / code) to spot audience & intent.
4. Geo-bias by time (e.g., AMS morning/evening) to rank likelihood of in-person activity.
5. Enrich with flight (AMS/EHAM), port, and event calendars.
6. Review false positives; tune the dictionary (keep human-in-the-loop).
OSINT Isn’t About Tools
Tools can’t replace curiosity. Tools can't replace thinking
They don’t know that “Dam” is more than a river barrier, it’s an entire ecosystem of meaning.
As analysts, we need to move beyond tool-based thinking and embrace semantic tradecraft. Understanding how people disguise places, names, and operations through culture and code.
Because when your target says “Meet at Freedom City,”
you’d better know where to look.
The Bigger Lesson
This isn’t just about Amsterdam.
It’s about every place, every culture, every coded network online.
The way people talk is intelligence.
So the next time you run a search, ask yourself:
“Am I chasing the name or the meaning?”
You can download the wordlist(s) for Amsterdam here:
1 Boolean
2 Regex
3 Combined