diff --git a/blog_data/blog_posts.jsonl b/blog_data/blog_posts.jsonl
new file mode 100644
index 0000000000000000000000000000000000000000..34c26bf4e43cb4d3c1be12f0794e97a8a22d4953
--- /dev/null
+++ b/blog_data/blog_posts.jsonl
@@ -0,0 +1,98 @@
+{"source":"benjaminstrick","url":"https://benjaminstrick.com/boko-haram-nigeria","title":"Boko Haram\\u2019s systematic destruction and displacement of Nigerian communities","status":"ok","retrieved_at":"2026-08-29T16:45:46.337602+08:00","text":"Boko Haram’s systematic destruction and displacement of Nigerian communities · Benjamin Strick BS Benjamin Strick Open-source investigations All writing Work ← Back to site Satellite Case study Boko Haram’s systematic destruction and displacement of Nigerian communities Published 8 August 2018 Read 9 min Villages, towns and dense areas have been burnt, destroyed, and completely levelled in northern Nigeria as the country continues its fight against the Boko Haram insurgency. Using Google Earth’s history function, we can view how landscapes change over years, as well as study developments in infrastructure and refugee movement through conflict areas. For the northern region of Nigeria, the landscape tells a grim tale. In Nigeria’s Borno State, what was once a thriving and culturally rich area, is now a void land as the population shelters in siege cities where the frontlines are protected by trenches, literally. Villages now have only their foundations remaining after they were burnt to the ground. The clear path of destruction mapped out by Boko Haram’s systematic approach to village destruction in Borno State from 2014 to 2017 can be seen as they jump from town to town destroying everything they leave behind. One roadside village was functioning in February 2016, but by March 2017 only foundations and ash remain. Another scene is the village of Mutube with its surrounding communities: the satellite image from 2013 shows a village, and the next available image from 2017 shows only trees remaining. For many communities that have been destroyed, there is no hope of rebuilding. That being said, the Nigerian Government is urging some refugees to return home . But there is nothing left, and if there was, it would again be under attack by Boko Haram insurgents still at large in the area. More recent village destruction can be seen below, where only a few foundations of buildings remain in the space of 11 months since 2017. Eleven months apart Mapping the disappearance of hundreds of sub-communities Surrounding the Sambisa Forest in Nigeria’s north is where the majority of the evidence of displacement can be viewed. According to UNHCR , that count of displacement is in the millions. The forest itself covers a very large and difficult terrain where many of Boko Haram’s attacks have been launched from. On the outskirts of the forest, traditional villages are all too common a story. When we view their status in the available 2017 map of Google Earth, there are no visible signs of what once stood there. There are hundreds of villages and towns like this that have been erased off the map. Three such communities were destroyed at some point between March and November 2016. Significantly larger and denser than the small villages, the town of Nguro-Soye was the victim of many suicide bombings and attacks by Boko Haram militants. Attacks on crucial infrastructure such as a telecommunications tower and suicide bombings of the town’s marketplace led to a downfall of Nguro-Soye, and its ultimate destruction. The satellite image from March 2018 shows few remnants after the town’s destruction. Further south of Nguro-Soye, on a T-intersection of a main road, we are able to see more defined darker areas where villages once stood, indicative of burning. These villages would have also been prime targets given the accessibility of the main highway for Boko Haram and Nigerian military to operate in the area. In a bid to control this area, the Nigerian military have used their \"trench-laying\" tactic to fortify the position against suicide bombers. Many of these trenches are scaled at 2 to 4m wide and 2 to 3m deep, and are a quick and effective solution to protect areas against potential suicide bombers or vehicle attacks, two offensive tactics Boko Haram employ. For villages that have been built along main roads, in a more peaceful time it would have been a good thing. But for villages in northern Nigeria, it means they are more accessible to Boko Haram. Almost all villages constructed along main roads near the major fortified town of Bama were systematically wiped out between 2016 and 2017. This is the case for the small town of Mairamri, 15km south-east of Bama. More recent destruction occurred at the village of Gajibo in Borno State along the Gamboru Ngala Highway. News reports from July 2018 state 27 were killed in an attack on the village, however, we can see from satellite images that the town has been largely destroyed, bar several shelters. Gajibo, before and after Any villages that are still standing are in the process of being besieged by Boko Haram, or are strongholds of Boko Haram, and face attacks and bombing by Nigerian military. Smoke signals from bombings and attacks are a common story. Dikwa: the siege city offering refuge With so much displacement from homes, communities and towns being destroyed, where have the majority of refugees gone? There is evidence in a number of larger towns that have the afforded protection of the siege trench walls and strong military presence. One such area is the town of Dikwa . Dikwa’s history has seen the town pivoted as a stronghold since the 1800s, and has seen German and French occupancy. Now the town is a well-protected sanctuary of the Borno State. It uses the first line of defence trench system encircling the town. The only access points in the town are main roads, which are heavily guarded with stringent checkpoints, visible in the satellite image from 2018. Due to the safety Dikwa is able to provide, it has been established as a refugee-haven for many of the displaced villagers from the outlying areas. We can see this in evidence of the rapidly erected refugee cities in Dikwa. The living conditions in these camps are dire. The capital of Borno State, and the area’s largest city, Maiduguri , is also a haven for many of the displaced with its well-protected boundaries. Since village destruction began in 2015, Maiduguri has struggled to house refugees. In the space of three years, a refugee city is born. The millions of displaced Nigerians, referred to as IDPs or Internally Displaced People, only need to look past city defences to see the plight of villages that sit beyond its boundaries. Beyond the protection of Dikwa’s boundary, one small village was levelled between 2016 and 2017. Outside the Dikwa perimeter, 2016 and 2017 Bitta: the failed siege town For the most part, the Nigerian defensive trench is able to protect the towns it surrounds. For Bitta , it was not able to do so. Bitta. Left: pre-2014. Right: December 2017 Bitta has been a hotspot for Boko Haram and Nigerian military clashes and many of its citizens have left after its destruction. The military has used Dikwa as a launchpad for the Borno State Nigerian military Deep Punch II Operation, focussing on the clearance of Boko Haram presence in the Sambisa Forest. The scars of clashes can be seen just beyond the guard boxes built along the north edge of the town. The refugees from villages like Bitta and others are not just moving to Nigeria’s refugee camps, but are also fleeing the danger and seeking refuge in bordering countries such as Chad and Cameroon. One of the largest external camps for Nigerian refugees is Minawao Refugee Camp in the Mayo Tsanaga region of Cameroon’s Far North. Minawao is exceeding numbers every day. The UN says Cameroon’s Far North region hosts more than 95,000 Nigerian refugees. Many of which are sheltering in Minawao. Since 2014, Minawao has become a city in Cameroon. Minawao, Cameroon. A barren landscape becomes a city While it did previously pledge a commitment to refugees, the Cameroonian Government has been \"forcibly returning\" a number of Nigerians. UNHCR say this is a clear violation of national and international laws. The fight against Boko Haram in 2018 still ensues, as regular attacks are reported against villages in Nigeria’s north, as well as bordering villages in Cameroon. Method This open-source case study was made using past and more present satellite imagery from Google Earth. I urge you to visit the communities via the links provided to see the destruction for yourself. Related writing All writing → Geolocation Adding geodata to Google Earth Pro → Geolocation Finding McAfee: geolocation and imagery analysis → GEOINT When the lights go out, satellites are watching → Get methods like this once a month OSINT Field Notes: tools, techniques and one case file. New editions are always free. Subscribe → © 2012 to 2026 Benjamin Strick benjaminstrick.com","image_urls":["https://benjaminstrick.com/images/blog/1-09ud44ncjaomdofkab1xkg-1341.png","https://benjaminstrick.com/images/blog/1-25tgsf7dh2pnbivbyzewxg-1024.png","https://benjaminstrick.com/images/blog/1-5qannf1hywgu-sf33-icag.png","https://benjaminstrick.com/images/blog/1-97vk4h3kl1xoirnnfsab4w-1024.png","https://benjaminstrick.com/images/blog/1-buv0rqe-nqjsgypq1sxslq.png","https://benjaminstrick.com/images/blog/1-ervuzn2dvravli5-urwp8a.png","https://benjaminstrick.com/images/blog/1-rlwagpmjweytveoueye3-q-1024.png","https://benjaminstrick.com/images/blog/1-uj-ep8y1nymf1ubfxoatbg.png","https://benjaminstrick.com/images/blog/1-x-fpu9myooprrg2tnyliyg-1024.png","https://benjaminstrick.com/images/blog/1-yijzcknn0vifcxigdqxtnq.png","https://benjaminstrick.com/images/blog/1-yzn95oyggdzjihjjpaxuwg.png"],"local_images":["blog_data/images/blog_517f0e7f0bb1_0.bin","blog_data/images/blog_517f0e7f0bb1_1.bin","blog_data/images/blog_517f0e7f0bb1_2.bin","blog_data/images/blog_517f0e7f0bb1_3.bin","blog_data/images/blog_517f0e7f0bb1_4.bin","blog_data/images/blog_517f0e7f0bb1_5.bin","blog_data/images/blog_517f0e7f0bb1_6.bin","blog_data/images/blog_517f0e7f0bb1_7.bin","blog_data/images/blog_517f0e7f0bb1_8.bin","blog_data/images/blog_517f0e7f0bb1_9.bin","blog_data/images/blog_517f0e7f0bb1_10.bin"]}
+{"source":"benjaminstrick","url":"https://benjaminstrick.com/finding-mcafee","title":"Finding McAfee: geolocation and imagery analysis","status":"ok","retrieved_at":"2026-08-29T16:45:39.335336+08:00","text":"Finding McAfee: geolocation and imagery analysis · Benjamin Strick BS Benjamin Strick Open-source investigations All writing Work ← Back to site Geolocation Case study Finding McAfee: geolocation and imagery analysis Published 15 March 2020 Read 6 min Identifying past, current, and possible future locations through the geolocation and chronolocation of media provided by a specific user. This case study is based on a challenge from well-known entrepreneur, John McAfee, to show how relative geolocation of two points on a chronological timeline can give a likely path and possible locations in between. To do this, two geographical points will be used, categorised by day, to geolocate a photo that was taken between those two points. This research post is split into the following four sections, in this order: Point B (the photo to geolocate) Point C (where the subject is traveling to) Point A (where and when the subject started the journey) Geolocation analysis of the Point B image The tools in this case study are completely free, so please do use them to follow along. I used Google Maps, GIMP (image editing) and Twitter. Contents 01 Point B: the image to geolocate 02 Point C: where the subject is traveling to 03 Point A: where and when the subject started the journey 04 Geolocation analysis of the Point B image Point B: the image to geolocate Below is the tweet in question. The challenge: self-explanatory. The tweet in question So where do you start in a case like this? Using a first approach to imagery intelligence (IMINT), look in the image and ask: \"what do I see?\". In the image, we have a number of clues that may indicate where this photo was taken. I am going to number some of them in the image below. Eight reference points to work from What do we see here? First, we have got McAfee. Who through his accounts may help give more clues. I will get to him later. This roof colouring gives an indication that it might be a brand colour. Coloured fuel bowsers indicate that this is both a fuel station, and is a unique identifier for what the brand or name of the fuel station may be. Large trucks use this fuel station, so it is likely that it is in an open area, or along a highway. There are flowers in front of the building McAfee is next to, which means it might be a store for the fuel station. There is a light blue band along the horizon. This is usually synonymous with a large body of water. This post and building would be a unique identifier on satellite imagery. The horizon is not cluttered with buildings or trees, indicating it might be a flat plain and out of built-up urban areas. That is a lot of reference points we have to go off. And now, since we have done an initial imagery analysis checklist, we can work our way down that list to investigate each of those leads. First is John McAfee. He is likely to indicate relevant information in his social media. Point C: where the subject is traveling to In the initial tweet above the subject indicated he was \"on the way to London\" and that the photo was taken in the past. This identifies our destination. How is he traveling there? Considering the location of the photo as we analysed in the eight takeaways above, it is clear he is at a service station with his large security crew. So it is likely he is driving to his destination. Point A: where and when the subject started the journey Where did the subject come from? This is where we can start using the intelligence tool I would like to refer to as \"geoprofiling\". Essentially we are going to map out a short chronological timeline of where McAfee was in order to find where he is. Scrolling back through his Twitter timeline, we can find this tweet. It was posted two days before the other photo. Two days earlier What is important about this tweet is it gives us a location as well as a destination. Take a look in the red box in the right of the image below. A signboard reading Hotel Schlicker It is in Munich, Germany . We know this is the place where the photo was taken as there are a number of features that match those seen in geotagged images on Google Maps and Facebook. First is the identical match of the sign and wall lining to this one found on Google Maps . Matching the sign, wall lining and ground paint against two independent sources Second, for further verification, we can identify both the sign and the white paint on the ground from this image on the Hotel Schlicker Facebook page. For chronolocation, for the purposes of this post there is no necessity to conduct a shadow calculation. Merely being able to plot this geolocated image on our timeline gives us an original lead for the following reference points: Hotel Schlicker in Munich, Germany on January 26, 2020 The unknown point in between London, at a future point in time Why is the second point unknown? Because that is the initial location we need to find. And we are going to do that now. Geolocation analysis of the Point B image We already know two things about the image. It was taken on the road between Hotel Schlicker and London. Using Google Maps \"direction\" feature we can make a simple indication of the route between those two points. A lot of empty space to cover That is a lot of empty space to cover. But we have a list of eight points we can use to filter that information down. First, what is the place they stopped at in the image? The features of the roof and fuel pumps will help with that. Those features are something we can use in a Google Search term. For this, I used what we know and what I see in the following string search for Google Images: It is likely in Europe, so that is a term I used: \"Europe\" \"Fuel Station\" \"Red and White\" We also have blue bowser pumps in the image, and some of the results have that. The features in the photo match those pictured in Google Images as an Esso Petrol Station. The branding resolves to Esso Now we can search for \"Esso\" in Google Maps to find any Esso fuel stations on the way from Munich to London. To further refine our search area, looking back at the eight points, the photo was likely taken near a body of water, possibly in an open area or out of a city, and along a highway. In looking at places where there is a main road near a large body of water I identified two possible locations on the route. To layer both the location of Esso petrol stations and the routes to London, I used photo editor GIMP to layer the two images, changing the transparency of one of them. There are alternative ways using KMZ points, but this one is also quite simple and keeps Google Maps as our main operating tool. Stations layered over the route One of these stations along the route is near a body of water. It is near Baden-Baden . It satisfies a number of the indicators we are after, such as water, main road, quiet area and an Esso station on our route. We can start to match this location with the Point B image to see if it fits the fingerprint of what is visible on the Google Maps satellite image. The final match Using all of the information derived from geolocating objects in the image, we can say, for certainty, that the photo was taken here . Further verification can be made by matching the Google Maps embedded images. However, for the purpose of this case study, the indicators seen in the photo are uniquely matched to the satellite image therefore giving a stronger level of geolocated evidence. A note on this case study The purpose of this case study is to stimulate conversation, research and development in the open source community and is in no way to the detriment of the subject or any business or person identified in this case study. Related writing All writing → Geolocation Mountain profiling with PeakVisor in Ethiopia → Geolocation Adding geodata to Google Earth Pro → Geolocation Boko Haram and the destruction of Nigerian communities → Get methods like this once a month OSINT Field Notes: tools, techniques and one case file. New editions are always free. Subscribe → © 2012 to 2026 Benjamin Strick benjaminstrick.com","image_urls":["https://benjaminstrick.com/images/blog/1-0ol0mb1elrwhb1n-xhz4g-1024.png","https://benjaminstrick.com/images/blog/1-3twkcb6hkt9ed2c-fybw7a-1024.jpeg","https://benjaminstrick.com/images/blog/1-4hv5zneqt6vn-btsoc6hfa-700-2.png","https://benjaminstrick.com/images/blog/1-4hv5zneqt6vn-btsoc6hfa-700.png","https://benjaminstrick.com/images/blog/1-aai0ap3pqgrnho8gker1hq-700.jpeg","https://benjaminstrick.com/images/blog/1-aieh1iu-ouhjnkknufjdaw-1024.png","https://benjaminstrick.com/images/blog/1-rehufwykry4mc3voel-e8g-2-1024.png","https://benjaminstrick.com/images/blog/1-tap6l7hpyt9plvivaszgzg-1024.png","https://benjaminstrick.com/images/blog/1-vi07n7r-frol9ffuih0w2w-1-700.png","https://benjaminstrick.com/images/blog/1-ybhjekvc1rzskcfz5ofiq-1024.png","https://benjaminstrick.com/images/blog/1y-ovhirrkrnbhw0suoe6hw-592.png"],"local_images":["blog_data/images/blog_89c2d63d87c4_0.bin","blog_data/images/blog_89c2d63d87c4_1.jpg","blog_data/images/blog_89c2d63d87c4_2.bin","blog_data/images/blog_89c2d63d87c4_3.bin","blog_data/images/blog_89c2d63d87c4_4.jpg","blog_data/images/blog_89c2d63d87c4_5.bin","blog_data/images/blog_89c2d63d87c4_6.bin","blog_data/images/blog_89c2d63d87c4_7.bin","blog_data/images/blog_89c2d63d87c4_8.bin","blog_data/images/blog_89c2d63d87c4_9.bin","blog_data/images/blog_89c2d63d87c4_10.bin"]}
+{"source":"benjaminstrick","url":"https://benjaminstrick.com/google-earth-geodata","title":"Geospatial awareness: how to add geodata to Google Earth Pro, and four datasets you should try","status":"ok","retrieved_at":"2026-08-29T16:45:28.745426+08:00","text":"Geospatial awareness: how to add geodata to Google Earth Pro, and four datasets you should try · Benjamin Strick BS Benjamin Strick Open-source investigations All writing Work ← Back to site Geolocation Method Geospatial awareness: how to add geodata to Google Earth Pro, and four datasets you should try Published 4 December 2020 Read 9 min This post is a list of geospatial datasets to drag into Google Earth Pro, such as NASA daily fires and Wikimapia. I have found these useful in conflict analysis and routine geolocation work as they boost what information is achievable with the Google Earth Pro platform. Google Earth Pro is great when it contains useful geotagged data, whether it be through custom-made satellite imagery annotations (such as powerline markings over Libya for geolocation purposes) or geospatial data taken from publicly available datasets. But how do we pull extra data into Google Earth and what are some useful datasets to help you with satellite imagery analysis, geolocation and storytelling? I am going to run through that in this post, as well as provide a list of files to add to your Google Earth Pro to increase your geospatial awareness and how to find more of them. What will you find in this post? A primer on Google Earth Pro How to find KML geo-datasets to \"drag\" into Google Earth Pro Four geo-based datasets you should try in Google Earth Pro Security considerations for using KMLs Contents 01 A primer on Google Earth Pro 02 How to find KML geo-datasets to drag into Google Earth Pro 03 Four geo-based datasets you should try 04 Security considerations with KML files A primer on Google Earth Pro Google Earth Pro is one of the most useful tools in performing any geospatial task, whether it be for conflict analysis, remote sensing, investigative journalism or routine geolocation tasks. For those of you that might be new to the software, I am talking about the desktop version. Not the one that you use in a browser. If you are following along, you can download Google Earth Pro here . If we zoom in on Uluru (Ayers Rock) in Australia, we can get an understanding of the volume of extra data already in Google Earth’s primary database. Uluru without and with Google Earth’s built-in data All of these data points have information related to the area geotagged to a specific place. These could be labels, images and other formats of data. For open source investigators, researchers and curious minds, this is useful as it gives us an understanding of what Uluru looks like on the ground from photos. So what if we layer that with information not generally available in Google Earth Pro, such as an open source database of geotagged locations, Google Maps labels and publicly available GPS data? Much more information than the built-in features alone As you can see, we get more information appearing on the map. Much more than what we would have had we been relying solely on Google Earth’s in-built features. So where did I get those external packets of data? They are external KML and KMZ files. KML, or Keyhole Markup Language, is a spreadsheet annotation for geographic-based data. The important question is, how can you find more of them, tailored to your specific need or investigation. How to find KML geo-datasets to drag into Google Earth Pro Finding KMLs to add geospatial awareness to your Google Earth is quite simple. One method is to try the advanced search term below in Google with any subjects you are looking for. In this example I have chosen to look for London Underground Tubewalk. Search string London Underground Tubewalk filetype:kml What we have done there is created a search string for all KML files, indexed on Google, with the term London Underground Tubewalk. With queries that have a lot of results, we can restrict that to sift out old data by changing the \"tools\" and \"any time\" tabs on Google search. In the results, you will notice a list of KML files. All we do is download it and drag it into the \"places\" section of Google Earth Pro. London without and with the Tubewalk KML Each one of these nodes and their connecting points is user-generated material. Each point is either a path, unique image or context about the location it is tagged at. As we can see, we have even got Paul McCartney’s house. If you are still wondering why this might be useful, there are a number of applications for this sort of data and a number of subjects where KML files are available through search engines. You might be a researcher on bald eagle migration, spider populations, deforestation in the Amazon, law enforcement or documenting conflict in Libya. All of these roles will have the need for extra packets of information. Four geo-based datasets you should try #1 Wikimapia . For anyone that performs analysis using maps, you will be familiar with Wikimapia, the open source map reference system. This KML file is specifically useful in areas that are less mapped on Google Maps. I have often found it to be a resource in conflict areas, as it provides more details as to place names and areas than other annotated maps. Wikimapia’s KML is quite powerful when used in conjunction with Liveuamap’s custom KML files of layered conflict lines and events which can be exported out of the browser and into Google Earth. East of Benghazi. Wikimapia identifies bunkers, hangars and air defence sites #2 Bing/Microsoft Maps . At times during routine geolocation work, without commercial imagery, I have found there is either very little coverage, or the imagery is blurred. Another medium of imagery that is freely available to use in Google Earth is the Bing Maps satellite overlay. The website that offers a good browser for that is Zoom Earth . To use this KML, from the linked page, use the drop down list and select \"Windows Live Satellite\". A site in Iraq. Google Earth on the left, Bing overlay on the right #3 Google Maps Labels . At times, Google Earth does not have the same level of detail for streets and places as Google Maps provides. A way around that is to drag in the labels system from Google Maps into your earth explorer. Select \"Google Hybrid (Labels)\" for the KML. This is also useful as you can layer this over either commercially bought imagery, or imagery from Bing Maps. Khartoum, Sudan. Built-in labels against Google Maps hybrid labels #4 EOSDIS Fire Points List. A more niche subject is spotting where fires may have occurred, especially in conflict areas as they can indicate signs warranting further research. I have previously produced guides on how burnt villages can be detected through satellite filters here as well as case studies on buildings being burnt where security forces have been known to do so. One way to monitor these activities in a wide field perspective is to use fire spotting systems such as NASA’s Worldview platform. This is also a useful tool for environmental monitoring for forest fires, back-burning and climate patterns. This system is available on EOSDIS Worldview Earthdata . It draws information from satellite sensors that detect daily fires. The data can be used in Google Earth and matched with other datasets such as ACLED reports and Sentinel Hub ’s fire identification feature to spot burnt areas. Note the historical slider, which lets you move through the past few days This is not an exhaustive list of KMLs, but rather these are ones that I have personally tested and find useful in documentation. There are likely more, and I urge you to search for them. Security considerations with KML files Some of the research performed using Google Earth Pro may be potentially sensitive, so reading up on any considerations and threat research is paramount. There are two vulnerabilities that have been identified in past versions of Google Earth Pro in relation to the use of KML and KMZ files, and while they may have already been identified and subsequent versions of the system have issued patches, it is a good reminder to query the source of any dataset before its use in software. CVE-2010-3134 identified a vulnerability in Google Earth where remote attackers could execute arbitrary code via a trojan horse located in the same folder as a KMZ file. This could lead to a potential hijack attack. A further vulnerability was identified in CVE-2006-7157 whereby attackers could cause a denial of service crash through a KML or KMZ file. Rule of thumb If you are in doubt about a specific KMZ or KML, then do not use it, or look for an alternative source that might be verified. Related writing All writing → Geolocation Finding McAfee: geolocation and imagery analysis → Satellite Boko Haram and the destruction of Nigerian communities → GEOINT When the lights go out, satellites are watching → Get methods like this once a month OSINT Field Notes: tools, techniques and one case file. New editions are always free. Subscribe → © 2012 to 2026 Benjamin Strick benjaminstrick.com","image_urls":["https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-5-49-36-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-5-50-07-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-6-16-29-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-6-16-36-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-6-34-09-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-6-34-23-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-6-37-38-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-6-37-53-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-6-48-30-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-6-49-00-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-02-at-11-08-54-am-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-02-at-11-25-07-am-1-2150.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-02-at-7-48-24-am-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-02-at-7-48-33-am-1-1024.png"],"local_images":["blog_data/images/blog_e32049c84994_0.bin","blog_data/images/blog_e32049c84994_1.bin","blog_data/images/blog_e32049c84994_2.bin","blog_data/images/blog_e32049c84994_3.bin","blog_data/images/blog_e32049c84994_4.bin","blog_data/images/blog_e32049c84994_5.bin","blog_data/images/blog_e32049c84994_6.bin","blog_data/images/blog_e32049c84994_7.bin","blog_data/images/blog_e32049c84994_8.bin","blog_data/images/blog_e32049c84994_9.bin","blog_data/images/blog_e32049c84994_10.bin","blog_data/images/blog_e32049c84994_11.bin","blog_data/images/blog_e32049c84994_12.bin","blog_data/images/blog_e32049c84994_13.bin"]}
+{"source":"benjaminstrick","url":"https://benjaminstrick.com/mountain-profiling-peakvisor","title":"Geolocating a plane shot down in Ethiopia: mountain profiling with PeakVisor","status":"ok","retrieved_at":"2026-08-29T16:45:16.550134+08:00","text":"Geolocating a plane shot down in Ethiopia: mountain profiling with PeakVisor · Benjamin Strick BS Benjamin Strick Open-source investigations All writing Work ← Back to site Geolocation Case study Geolocating a plane shot down in Ethiopia: mountain profiling with PeakVisor Published 2 July 2021 Read 11 min Through the use of publicly available satellite imagery, open source investigative techniques, and a bit of creativity, we can find where and when a photo or video was taken. But sometimes, geolocating footage comes with unique challenges, all of which differ depending on the country, landscape, availability of data, or the quality of the footage you are trying to geolocate. In these case studies we look at the geolocation of footage in remote environments, and how Google Earth’s mountain ranges can play tricks on our confidence levels of locations. I have broken this post down into two main sections: A primer on use of PeakVisor , a tool that gives more accurate mountain silhouettes than Google Earth, and how it helps as a confirmation tool in geolocation work where Google Earth has not truly represented what is seen in the footage, with a case study from Yemen A recent case study geolocating footage circulated online showing the debris of an Ethiopian C-130, believed to be somewhere in the Tigray region A primer on geolocation with PeakVisor Finding where an image or a video was taken often involves searching for clues around, and in, a video or photo. I say around because there is often vital context that comes with media, such as a country, region, or possible location. By looking for clues within the imagery, can we start to consider matching that up with what we might see on a map. When looking at regional conflict areas, often there are no obvious clues to find a location. At least, not as obvious as a street sign or a shop name. When it comes to looking at these remote areas, clues do exist such as mountains, tree formations, bodies of water and other natural features. I have found numerous successes in using mountain ranges as a starting point in many difficult geolocations. But caution should be applied, as mountain ranges on Google Earth might not always appear as they would in real life. For example, take the Google Earth view from a base near Najran, overlooking the border between Saudi Arabia and Yemen, and compare it against the same view in PeakVisor. Notice the difference in definition, defined peaks, and the more jagged appearance on the profile of some of the mountains. Google Earth on the left, PeakVisor on the right As you can see, the level of detail is stronger. Google Earth’s meshing over its elevation data is not always as precise as we would like when we are relying on specific peaks to locate or match an image or a video. Having this added benefit of detail from PeakVisor helps substantially. In another example, this time in Yemen, there was much more of an issue with Google Earth’s formations during the geolocation of a Saudi Air Force jet that was allegedly shot down by Houthi fighters. The confirmation from that geolocation should have been made with two specific ridgelines seen at different intervals throughout the footage. Two ridgelines from the footage However, at the location on Google Earth there is barely any resemblance to the elevation data. I wrote about this example for Bellingcat in 2019, as it was a striking mismatch between what we see on the ground, and what we see on the satellite imagery layered over Google Earth’s elevation data. The same place in Google Earth In this circumstance, we can be definite of the location given the specific fingerprints unique between the satellite imagery and what is seen in the footage. For example, a rock formation creates a very definite match. But using PeakVisor creates a definite match between ridgelines. The ridgelines match By going through past geolocations like this, we can see just how much a little extra detail can help in the confirmation of a location. Case study: the crash site of a C-130 in Ethiopia In this specific geoprofiling case study, we look at the verification of footage of a crash site in Ethiopia which was circulated widely on social media. Most of the uploads claimed the wreckage was of an Ethiopian Air Force C-130 in Ethiopia’s Tigray region. The question to answer was where exactly that video was filmed. A primary starting place is always the context and content of the media. What are the circumstances of the upload, what are people saying about it, and what do we see? First, alternative images from the debris confirm that the plane may have been a C-130, including a photograph of the aircraft’s identification tag found in the wreckage. There were also a number of posts online that claimed the plane crashed somewhere near a town called Gijet, in the Saharti Samre area. So there was a clue as to a location, but also something to use as a keyword in further social media searches. While searching for other imagery on Facebook, I identified a post which was helpful as it showed a possible location in the sky from where the plane was downed, some specific building types that should be identifiable on satellite imagery, and an easy to locate mountain range. The post that opened the case The mountain range was rolling to the left, with no other mountains seen in the back left of the image, so this led me to believe the location was on the side of a mountain range. After a short amount of time panning around Google Earth near the area of Gijet, I identified the location of that image. The first location, firmed up Now that the location of that image was firm, I used that to work towards the much bigger task of finding where the downing of the plane was. This was easy to do, as we can see the location in the sky where the plane might have been hit. This lines up with features on the ground. Therefore, looking along that match line would lead me to the eventual final location. From the sky position to a line of sight In the original footage there also appeared to be structures that looked like powerlines, and I thought that might be a helpful resource to identify on satellite imagery to see if there were powerlines that crossed my line of sight from where the plane went down. While it took some work to identify nearby powerlines through a close inspection of the satellite imagery, I stopped at the second set as I had started to see other features that matched, such as buildings, a road, and of course, a fitting mountain profile. Powerlines, then buildings and a road From what can be seen on Google Earth, the mountain range makes a close fit with what we can imagine should be similar to the real footage. But there are some points in the elevation profile that are not accurate. As done above with the previous PeakVisor examples, layering the crash site footage over the mountain range seen in PeakVisor gives an almost perfect match. Google Earth close, PeakVisor almost exact But the final task is not yet complete. While the mountain profile is a confirmed location, further confirmation can be sought by analysing content in the footage with what is seen on the ground on satellite imagery. For example, the trees, houses, powerlines and other features. This allows me to identify an as exact as possible location. Once I have identified some features that can create a line, I draw lines back from them to find my backbearing. This gives the exact location of where the crash site footage was filmed from. Backbearings give the camera position In a more recent update, Twitter analyst @Gerjon_ further confirmed the location, and verified the date range, by using Sentinel Hub’s EO Browser with more recent satellite imagery of the area. The difference between what is seen on 20 June and 25 June 2021 shows two small black patches appearing in the centre of the imagery on the later date. That was the location of the crash site. Further reading on PeakVisor Mahbere Dego: clues to a clifftop massacre in Ethiopia · Using AllTrails and PeakVisor for geolocation · Geolocating Mahibere Dego . If you would like to learn more about geolocation, satellite imagery analysis or open source techniques, I have free tutorials on my YouTube channel . Related writing All writing → Geolocation Finding McAfee: geolocation and imagery analysis → Geolocation Adding geodata to Google Earth Pro → Satellite Boko Haram and the destruction of Nigerian communities → Get methods like this once a month OSINT Field Notes: tools, techniques and one case file. New editions are always free. Subscribe → © 2012 to 2026 Benjamin Strick benjaminstrick.com","image_urls":["https://benjaminstrick.com/images/blog/e4u-0wmweackpw8-1024.jpeg","https://benjaminstrick.com/images/blog/e4u6ixkwyamv3fz.jpeg","https://benjaminstrick.com/images/blog/e4u6j6vxeacr77q.jpeg","https://benjaminstrick.com/images/blog/e4u7wdhxwaek65q.jpeg","https://benjaminstrick.com/images/blog/e4u8bhhweam6jk3.jpeg","https://benjaminstrick.com/images/blog/e4u8p2sxmaifd8q.jpeg","https://benjaminstrick.com/images/blog/e4u8t9wxoaqpffc.jpeg","https://benjaminstrick.com/images/blog/e4vbdkrxwac-mxb-1024.jpeg","https://benjaminstrick.com/images/blog/e4vddllwqaqaxax.jpeg","https://benjaminstrick.com/images/blog/e4vdgblweamtaeu.jpeg","https://benjaminstrick.com/images/blog/screen-shot-2021-07-02-at-14-29-26-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2021-07-02-at-14-33-25-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2021-07-02-at-15-16-29.png","https://benjaminstrick.com/images/blog/screen-shot-2021-07-02-at-15-16-47-1.png","https://benjaminstrick.com/images/blog/screen-shot-2021-07-02-at-15-20-43-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2021-07-02-at-15-52-56-1024.png","https://benjaminstrick.com/images/blog/untitled-design-5-1024.png","https://benjaminstrick.com/images/blog/untitled-design-6-2560.png"],"local_images":["blog_data/images/blog_32639a1b455a_0.jpg","blog_data/images/blog_32639a1b455a_1.jpg","blog_data/images/blog_32639a1b455a_2.jpg","blog_data/images/blog_32639a1b455a_3.jpg","blog_data/images/blog_32639a1b455a_4.jpg","blog_data/images/blog_32639a1b455a_5.jpg","blog_data/images/blog_32639a1b455a_6.jpg","blog_data/images/blog_32639a1b455a_7.jpg","blog_data/images/blog_32639a1b455a_8.jpg","blog_data/images/blog_32639a1b455a_9.jpg","blog_data/images/blog_32639a1b455a_10.bin","blog_data/images/blog_32639a1b455a_11.bin","blog_data/images/blog_32639a1b455a_12.bin","blog_data/images/blog_32639a1b455a_13.bin","blog_data/images/blog_32639a1b455a_14.bin","blog_data/images/blog_32639a1b455a_15.bin","blog_data/images/blog_32639a1b455a_16.bin","blog_data/images/blog_32639a1b455a_17.bin"]}
+{"source":"dutchosintguy","url":"https://www.dutchosintguy.com/post/crowd-sourced-mapping-tools-for-osint-investigations","title":"Crowd-sourced Mapping Tools for OSINT Investigations","status":"failed","retrieved_at":"2026-08-29T17:58:53.151418+08:00","error":"HTTPError: HTTP Error 429: Too Many Requests","text":"","image_urls":[],"local_images":[]}
+{"source":"dutchosintguy","url":"https://www.dutchosintguy.com/post/from-open-web-to-real-world-target-the-osint-trail-behind-proxy-violence","title":"From Open Web to Real-World Target: The OSINT Trail Behind Proxy Violence","status":"failed","retrieved_at":"2026-08-29T17:58:50.42056+08:00","error":"HTTPError: HTTP Error 429: Too Many Requests","text":"","image_urls":[],"local_images":[]}
+{"source":"dutchosintguy","url":"https://www.dutchosintguy.com/post/how-osint-investigators-miss-clues-hidden-in-plain-sight-cities-with-hundreds-of-names","title":"OSINT - Cities with hundreds of names | How OSINT investigators miss hidden clues","status":"failed","retrieved_at":"2026-08-29T17:58:51.786644+08:00","error":"HTTPError: HTTP Error 429: Too Many Requests","text":"","image_urls":[],"local_images":[]}
+{"source":"dutchosintguy","url":"https://www.dutchosintguy.com/post/the-amsterdam-street-that-never-existed","title":"The Amsterdam Street That Never Existed","status":"ok","retrieved_at":"2026-08-29T17:58:47.152635+08:00","text":"All Posts Cryptography OSINT analysis audio AI OPSEC geolocation mapping emotions tradecraft methodology vicarious trauma psychology job HUMINT Algorithm law enforcement Intelligence vibe coding evidence poisioning Search The Amsterdam Street That Never Existed Nico Dekens | dutch_osintguy Jun 8 14 min read How AI Misleads AI - and Why OSINT Tradecraft Is Your Only Saviour There is a street in Amsterdam that looks real. It has the wet brick paving you expect after rain. Tall narrow façades. Dark window frames. Bicycles leaning into the street. A cargo bike on the right. Bollards along the curb. A small café sign on the left. Grey skies. A muted, damp, unmistakably Dutch atmosphere. At first glance, it feels like Amsterdam. Not “Amsterdam-inspired.” Not “kind of Dutch.” It feels like a quiet side street somewhere in the old city center. The kind of place I could imagine walking past without thinking twice. But the street does not exist. It was generated by ChatGPT. And that is where this story begins. I conducted a little experiment based on workflows that almost every modern day OSINT investigator or analyst uses. Prompt 1: Create a street that looks real, but is not real The first prompt was simple, but deliberate: “Can you generate an image that looks like it is taken in a random street in Amsterdam city center. It cannot be an image or street that really exists. But it must look so convincing that not even a person from the Netherlands or Amsterdam will be able to tell it is not a real street in Amsterdam. I need this image for an OSINT training on visual analysis.” That prompt matters. This was not an accidental hallucination. The request was explicit: create a fictional street, make it look like Amsterdam, but make sure it is not an actual location. The goal was OSINT training. The image had to be realistic enough to challenge investigators. It had to look geolocatable while being impossible to geolocate. ChatGPT generated exactly that: a convincing Amsterdam-style street scene with wet paving, old façades, bicycles, bollards, greenery, shopfront details, and just enough visual texture to feel authentic. Original generated Amsterdam-like street image The original AI-generated street. It looks like Amsterdam, but it was deliberately created as a fictional location that does not exist. Look at this image for a moment before reading further. If you know Amsterdam, your brain probably starts filling in the blanks. Maybe Jordaan. Maybe De Wallen. Maybe somewhere near the old center. Maybe one of those quiet streets between canals. That is the danger. The image does not have to be perfect. It only has to be plausible enough for your brain to complete the story. The first OSINT question: how would we prove this street is not real? The next prompt shifted from image generation to OSINT methodology: “Now let’s think of OSINT CTF or OSINT geolocation. How could an investigator tell or show evidence this is not a real street in Amsterdam? Explain in detail what they should visually see that are clear tells and what else they should do to analyse and prove this is not a real image or real street in Amsterdam.” This is where the experiment became useful. The answer did not simply say, “Look for AI artifacts.” Instead, it described a more mature investigative approach: do not rely on vibes; build an evidence chain. The response correctly pointed out that the image was convincing because it contained many Amsterdam-like cues: wet brick road, narrow façades, bicycles, bollards, old buildings, black-painted houses, planters, and muted Dutch weather. But it also argued that the image was weak as a geolocation target because it lacked strong verifiable anchors. That is the first major lesson. An image can look geographically convincing while still being geographically empty. The image gives you Amsterdam atmosphere. But does it give you Amsterdam proof? That is a very different question. Soft cues versus hard anchors The original image contains many soft cues. Soft cues are things that make a place feel right: Amsterdam-like façades. Wet pavement. Bicycles. A cargo bike. Bollards. A small café sign. A grey sky. Narrow street geometry. Trees and planters. Old brick buildings. These cues are useful, but they are not enough. Hard anchors are different. They are specific, searchable, verifiable, and tied to a real-world location. A readable street-name sign. A house number.A unique shop name. A matching façade sequence. A business listing. A bridge or canal configuration. A license plate. A municipal object. A traffic-sign combination that makes sense for that exact street. A landmark visible in the background. The image had many soft cues but very few hard anchors. That is precisely why it is dangerous. It performs Amsterdam without proving Amsterdam. The image is not suspicious because it looks bad One of the most important points for OSINT practitioners is this: The image is not suspicious because it looks obviously fake. It is suspicious because it looks generically right while avoiding the boring, specific, searchable details that real places usually contain. Real streets are full of administrative residue. House numbers. Doorbells. Intercoms. Mail slots. business stickers. parking signs. waste collection markings. utility covers. drain logic. street-name plaques. local damage. construction scars. maintenance patterns. ugly details that were not placed there for aesthetics. AI-generated streets often prioritise atmosphere over administration. That is visible in this image. The road feels Amsterdam-like. The buildings feel Amsterdam-like. The bikes feel Amsterdam-like. But the scene does not immediately provide a strong, testable identity. For geolocation, that matters more than whether the image “looks real.” The annotated version: useful training image, but also a warning After the analysis, the next prompt asked ChatGPT to create an annotated version of the original image pointing out the clues and tells. That produced an image with callouts: generic storefront text, unreadable street plaque, bicycle geometry, bollard and curb logic, road paving and drainage, façade sequence, missing house numbers, and other points. First annotated evidence overlay The first annotated version attempted to highlight suspicious areas, but it introduced a new methodological problem: the image generation process altered parts of the underlying scene. At first glance, this looks like a good OSINT training graphic. But then something important happened. I noticed that the annotated version was not fully consistent with the original . The original did not clearly show the same street sign, but the annotated version appeared to introduce or strengthen one. That matters. I challenged it: “It’s funny because the original doesn’t show the street sign but the one with the evidence overlays does. That isn’t really consistent.” ChatGPT admitted the problem. It explained that the “evidence overlay” version was not a pure annotation layer on top of the exact original. The image model had re-rendered parts of the scene while adding overlays, and in doing so it introduced or strengthened details, including the street plaque/sign. That is a huge OSINT lesson. Annotation must never alter evidence. If the base image changes, the annotation itself becomes contaminated. For training, this is gold. It shows that even the act of “explaining” or “annotating” with AI can accidentally fabricate new evidence. A training overlay can become a synthetic derivative. The analyst may think they are marking clues, while the model is quietly changing the scene. That is unacceptable in real investigative work. The corrected annotation: preserve the original, add only the overlay I then asked ChatGPT to fix the inconsistency: “Fix it. I need consistency.” The corrected version was supposed to use the exact original image and add only a separate annotation layer, without regenerating the base street scene. The corrected labels focused on better claims: No readable street-name anchor. Missing house numbers and administrative details. Generic storefront text. Bicycle and cargo-bike geometry checks. Bollard and curb logic. Road paving and drainage continuity. Façade sequence that may not match any real street. Corrected consistent annotation The corrected annotation focuses on methodology: the image feels authentic, but lacks strong verifiable anchors such as readable street names, house numbers, or matchable façade sequences. This is one of the most important teaching moments in the whole experiment. For OSINT training, the corrected image is useful not because it proves the street is fake, but because it teaches students what to inspect. Do not just ask, “Does this look like Amsterdam?” Ask: Can I read the street name? Can I verify the shop? Can I match the façade sequence? Can I find house numbers? Can I explain the traffic logic? Can I match the curb, bollards, bikes, windows, trees, and road geometry to street-level imagery? Can I corroborate this scene from another source, another angle, another date? That is tradecraft. Then came the real test: a brand-new chat The next step was the most revealing. I opened a brand-new ChatGPT chat and uploaded the original AI-generated image. This new chat did not have the earlier conversation context. It did not know the prompt. It did not know the image had been generated as a fictional Amsterdam street. Then I asked: “Think like an OSINT analyst and geolocation analyst. Where is this, be as precise and accurate as you can. Explain your methodology and analysis.” This is exactly the kind of prompt many investigators might use. And this is where the AI failed dangerously. It answered: “This is Lange Niezel, Amsterdam-Centrum, Netherlands, in the De Wallen / Burgwallen Oude Zijde area.” It went further. It said the image appeared to be taken on Lange Niezel, looking toward the Oudezijds Voorburgwal / Korte Niezel side. It even gave approximate coordinates: 52.3748, 4.8985 . It rated confidence as high for the street and medium for the exact camera position. That is not a cautious hypothesis. That is a confident false geolocation. Original image as used in the new geolocation chat In a new chat, the same fictional image was treated as a real geolocation target. ChatGPT confidently identified it as Lange Niezel in Amsterdam. This is the moment every OSINT practitioner should pay attention to. The model was not simply uncertain. It produced a location. It gave a street name. It gave a neighborhood. It gave coordinates. It gave confidence language. It explained its supposed methodology. And it was wrong. The street was fictional. The danger of expert-sounding wrong answers This is one of the biggest risks when using AI in investigations. AI often does not fail by saying nonsense. It fails by sounding reasonable. It produces an answer that has the shape of expertise: “Most likely location.” “Key evidence.” “Methodology.” “Final assessment.” “Confidence: high.” That structure feels professional. It feels analytical. It feels like OSINT. But structure is not evidence. A confident format does not make a conclusion true. In this case, the model claimed the blue Amsterdam street-name sign on the right-hand black building was the decisive clue and appeared to read “Lange Niezel.” The image does not even contain a street name plaque ! It then built the rest of the location assessment around that interpretation. This is exactly how false geolocation can happen. One weak or imagined anchor becomes the foundation for a confident conclusion. The analyst (human or AI) sees something that resembles a clue, names it, and then builds a story around it. That is not verification. That is narrative construction. The follow-up: are there inconsistencies? After the false geolocation, I asked another important question: “Are there any inconsistencies in this image when it comes to shade, reflections, or objects?” This was the opportunity for the model to catch itself. It did not. It answered that it did not see strong evidence of manipulation from shadows, reflections, or object placement. It said the scene looked broadly internally consistent with a rainy or overcast Amsterdam street. It described the diffuse lighting as plausible. It said the wet cobblestones and sidewalk showed realistic reflections. It said the bicycles, bollards, pedestrians, street signs, façades, windows, and pavement lines all aligned with the same street perspective. Its assessment: “No major inconsistencies detected.” It rated the image as visually plausible and internally consistent. It said nothing in the shadows, reflections, object scale, or perspective strongly suggested AI generation, compositing, or object insertion. Again, this is not surprising. Modern AI-generated images can be internally coherent. They can have plausible lighting. Plausible reflections. Plausible object placement. Plausible architecture. Plausible perspective. That is why visual plausibility is not enough. A fictional image can be visually coherent. A real image can be visually strange. Therefore, “I see no obvious inconsistencies” does not mean “this is real.” It only means the visible pixels did not contain enough obvious contradictions. The final visual-forensics prompt: find AI tells Then I pushed harder: “Use all your knowledge and analyse the image to see if there are any AI tells in this image. Make it thorough.” This should have been the strongest test. The answer was even more revealing. ChatGPT concluded: “I do not see strong AI-generation tells in this image.” It assessed the image as: “Likely authentic or at least photograph-based.” It said there was no clear evidence of full AI generation and no obvious signs of object insertion, background replacement, or synthetic reconstruction. It described the scene geometry, perspective, text, lighting, reflections, object grounding, bicycles, people, architecture, vegetation, glass reflections, compression, and metadata. It even described the text as unusually coherent for a fully AI-generated image, stating that the “Koffie & Koek” sign and “Sinds 2013” looked readable and natural. It treated the apparent blue street-name signs as plausible and consistent with the previously identified location. The final conclusion was: “Likely real / photograph-based. No strong AI-generation tells detected. No obvious manipulation artifacts visible.” That is the central problem of this entire experiment. The image was AI-generated. But another AI analysis judged it likely real. Why this matters for OSINT This experiment shows three separate but connected failures. First, AI can generate a realistic image of a place that does not exist. Second, AI can later fail to recognize that image as synthetic. Third, AI can create a confident but false geolocation for that same fictional image. For OSINT practitioners, the third failure may be the most dangerous. A model saying “I don’t know” is manageable. A model saying “this is likely Lange Niezel, Amsterdam” with high confidence can actively mislead an investigation. It can send the analyst down the wrong street, literally and figuratively. It can create false leads. It can waste time. It can contaminate reporting. It can influence other analysts. It can become the first link in a chain of repeated errors. And because the answer sounds structured and professional, people may trust it too quickly. Why ChatGPT cannot simply recognize its own image The last part of your document addressed the obvious question: If ChatGPT generated the image, why can’t ChatGPT recognise it later? The answer is important. In a new chat, the model usually sees only the uploaded image. It does not automatically receive the original prompt, the previous conversation, the generation seed, the internal generation trace, or a database lookup of every image previously generated. There are two very different questions: Does this image look AI-generated? And: Was this exact image generated by ChatGPT? The first is visual analysis. It relies on clues in the pixels: lighting, geometry, text, reflections, shadows, object structure, metadata, compression, and so on. The second is provenance. It requires evidence about origin: metadata, watermarks, C2PA, logs, original files, platform history, or some other verifiable chain of custody. Those are not the same thing. A model can inspect an image and say it looks plausible. That does not prove it is real. A model can fail to find AI tells. That does not prove it was not generated. A model can say it cannot determine origin from pixels alone. That may be the most honest answer. The key lesson from the document is this: ChatGPT does not recognise a generated image as fake simply because ChatGPT generated it earlier. In a new chat, without creation history, metadata, watermarking, or external provenance, it must judge from visual clues alone. Modern AI images can be visually plausible enough that there are no reliable tells. That is not just a technical limitation. It is an evidentiary limitation. AI tells are indicators, not proof Many people still talk about AI image detection as if it is a checklist. Bad hands. Broken text. Strange shadows. Warped windows. Impossible reflections. Malformed cars. Melted bicycles. Repeating patterns. Weird faces in the background. Those clues can help. But they are not proof. There are two problems. First, modern image generators are improving. The obvious artifacts are becoming less obvious. Second, real photographs can also look strange. Compression, rain, reflections, low light, HDR, motion blur, rolling shutter, lens distortion, platform resizing, screenshots, and social media filters can all create suspicious-looking artifacts. That means both of these statements can be true: A real image may look fake. A fake image may look real. This is why “AI tell” analysis must be treated as one part of a broader verification process, not as the final verdict. The real question is no longer “Where is this?” Traditional geolocation usually begins with: Where is this? But in the age of generative AI, that question may come too late. The first question should be: Can this image be grounded in the real world at all? Before trying to identify the street, ask whether the image contains enough verifiable anchors to justify a geolocation attempt. Can you read a street sign? Can you match the house numbers? Can you verify the business? Can you match the façade sequence? Can you find the same bollard layout? Can you match the road surface and curb design? Can you verify the traffic signs? Can you find the same scene in street-level imagery? Can you corroborate it from independent images? If not, the right conclusion may be: “Visually plausible, but not geolocated.” That is much safer than inventing a street name. A fictional street can still be internally consistent One of the reasons this case is so powerful is that the image is not absurd. The lighting works. The reflections are plausible. The wet road makes sense. The perspective is coherent. The buildings look Dutch. The bikes look mostly believable. The street feels physically possible. But “physically possible” is not the same as “geographically real.” A fictional street can have coherent lighting. A fictional café can have readable text. A fictional building can have plausible windows. A fictional road can have reflections. A fictional image can pass a visual inspection and still fail reality. That is the new problem. AI no longer needs to create fantasy worlds. It can create ordinary worlds that never happened. The new OSINT workflow The final answer in your document gave the right teaching point: Do not ask ChatGPT to decide whether an image is real. Ask it to help generate testable hypotheses. That should become a standard practice. A better workflow looks like this. Preserve the original file. Do not overwrite it. Do not annotate directly on it. Do not rely on screenshots unless that is all you have. Check provenance first. Look for EXIF, C2PA , editing history, original filename, upload trail, platform compression, and whether the file is an original, a screenshot, a re-export, or an AI-generated file. Separate soft cues from hard anchors. “Looks like Amsterdam” is not evidence. “This exact façade sequence matches this exact street” is evidence. Create an anchor table. List every visible clue and classify it as readable, searchable, unique, and independently verifiable. Reverse-search the full image and cropped details. Search the shopfront, signs, façades, bikes, distinctive buildings, background objects, and road layout. Use street-level data. Compare with Google Street View, Apple Look Around, Mapillary, OpenStreetMap, local business listings, municipal sources, social media images, and any other relevant public imagery. Test urban logic. Do the bollards make sense? Do the traffic signs make sense? Does the road layout fit the country? Are the house numbers where they should be? Do the municipal details match the city? Use AI carefully. Ask it to list possible clues, contradictions, and verification steps. Do not let it deliver the final truth without independent corroboration. Use confidence language. Say “unverified,” “visually plausible,” “not geolocated,” “likely synthetic,” “contradicted by map evidence,” or “verified by independent street-level match.” Most importantly: document what failed. A failed geolocation is not automatically proof of fakery, but a disciplined negative search is still valuable. What this experiment really proves This experiment does not prove that every AI-generated image is impossible to detect. It does not prove that geolocation is dead. It does not prove that ChatGPT is useless for OSINT. It proves something more subtle and more important: Visual plausibility can no longer be treated as evidence of reality. The original image looked like Amsterdam. The first analysis knew it should be treated with caution. The annotation process accidentally demonstrated how AI can contaminate evidence by changing the underlying scene. A new ChatGPT chat then falsely geolocated the fictional image as Lange Niezel. A follow-up analysis found no major visual inconsistencies. A thorough AI-tell analysis judged the image likely real or photograph-based. And the final explanation showed why this happens: without provenance, the model is judging pixels, not origin. That is the whole problem in one case study. AI generated a fictional street. AI then believed the fictional street. The end of seeing is believing For decades, images carried an implied claim: This was somewhere. This happened. This existed in front of a camera. That assumption is now broken. An image may show a street that never existed. A protest that never happened. A building that was never built. A person who was never there. A military vehicle in a location it never visited. A disaster scene fabricated from statistical memory. A realistic image is no longer enough. In this new environment, seeing is not believing. Seeing is the beginning of verification. For OSINT practitioners, that means our tradecraft matters more than ever. Not tools. Not vibes. Not confidence. Tradecraft. Provenance. Source tracing. Geolocation. Corroboration. Falsification. Documentation. Confidence language. Chain of custody. Methodological humility. That is how we survive the age of synthetic evidence. Final lesson The most dangerous AI images will not always look spectacular. They will look boring. A rainy street. A café sign. A cargo bike. A few bollards. Some wet paving. A grey sky. A city you think you know. And then an AI will tell you where it is. With confidence. That is why OSINT practitioners must slow down, preserve evidence, extract anchors, verify externally, and resist the temptation to let a fluent machine turn plausibility into proof. The street in the image never existed. But the risk it represents is very real. Tags: AI tradecraft methodolgy Data Analysis geoint Intelligence Analysis Digital Evidence AI Risks in OSINT geoint geolocation Critical Thinking Risks AI Risks in Analysis AI Bias in OSINT Critical Thinking in AI AI Dependence AI in Investigations Critical Thinking in OSINT Verification in OSINT Synthetic Identity Detection Evidence Poisoning AI-Driven Deception OSINT analysis AI Recent Posts See All Evidence Poisoning: The OSINT Crisis Nobody Is Ready For AI May Not Replace Analysts. It May Break Them First. Critical Thinking Collapse 2.0: AI’s Impact on OSINT","image_urls":["https://static.wixstatic.com/media/038b0b_42ec7fcf8e4745e5b211b3de0ed6f22b~mv2.png/v1/fill/w_49,h_37,al_c,q_85,usm_0.66_1.00_0.01,blur_2,enc_avif,quality_auto/038b0b_42ec7fcf8e4745e5b211b3de0ed6f22b~mv2.png","https://static.wixstatic.com/media/038b0b_462d6bbb56694fe39eb64ed9d5e7daa6~mv2.png/v1/fill/w_49,h_37,al_c,q_85,usm_0.66_1.00_0.01,blur_2,enc_avif,quality_auto/038b0b_462d6bbb56694fe39eb64ed9d5e7daa6~mv2.png","https://static.wixstatic.com/media/038b0b_cc0087b846d046fea2f18789da2252ce~mv2.png/v1/fill/w_49,h_37,al_c,q_85,usm_0.66_1.00_0.01,blur_2,enc_avif,quality_auto/038b0b_cc0087b846d046fea2f18789da2252ce~mv2.png"],"local_images":["blog_data/images/blog_4a59b13cd215_0.bin","blog_data/images/blog_4a59b13cd215_1.bin","blog_data/images/blog_4a59b13cd215_2.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/","title":"","status":"ok","retrieved_at":"2026-08-29T16:29:57.551832+08:00","text":"Calculating Website Age & Tracking Changes With URL Dater Leave a Comment / OSINT Tools / Nixintel How can you determine the age of a webpage in a reliable way? URL Dater uses a range of different sources to present an accurate picture. Calculating Website Age & Tracking Changes With URL Dater Read More » Using SSL Certificates To Find Threat Actor Infrastructure 1 Comment / OSINT / Nixintel At last month’s SANS OSINT Summit I gave a talk the usefulness of SSL certificates for open source intelligence researchers. The talk looks at three recent examples of how information from certificate transparency logs can be used to discover, attribute, and unmask threat actor infrastructure. The video of the talk has now been published and you can Using SSL Certificates To Find Threat Actor Infrastructure Read More » Telegram For Cyber Investigators 2 Comments / OSINT / Nixintel Telegram is one of the most important platforms for OSINT investigators. I joined the Needlestack podcast to discuss how Telegram works and shared some practical OSINT advice along the way. Telegram For Cyber Investigators Read More » Digging Into Russian Disinfo Infrastructure 6 Comments / OSINT / Nixintel Disinformation and propaganda has been one of the key features of the war between Russia and Ukraine. One of the many groups that have sprung up to push pro-Russian propaganda narratives is a small hacktivist organisation called Beregini. This article by Givi Gigitashvili provides a useful introductory insight into the methods of Beregini by analysing Digging Into Russian Disinfo Infrastructure Read More » Verify Your Online Identities With Keybase 1 Comment / Security / Nixintel Twitter’s recent decision to remove blue check marks from accounts it has previously verified causes a number of issues for the platform and its users. One of the most obvious ones is around authentic identity. Without verification, how do I know that a particular account really does belong to the person or organisation who claims Verify Your Online Identities With Keybase Read More »","image_urls":["https://nixintel.info/wp-content/uploads/2023/04/twitter_profile.png","https://nixintel.info/wp-content/uploads/2023/07/Screenshot-2023-07-31-at-22.50.56.png","https://nixintel.info/wp-content/uploads/2026/01/Screenshot-2026-01-11-161045.png"],"local_images":["blog_data/images/blog_1e330956d596_0.bin","blog_data/images/blog_1e330956d596_1.bin","blog_data/images/blog_1e330956d596_2.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/about/","title":"About Me","status":"ok","retrieved_at":"2026-08-29T16:30:11.706439+08:00","text":"Home About About I am a highly experienced investigator and cybersecurity specialist. I specialise in Open Source Intelligence (OSINT) and have more than 15 years’ experience of conducting internet investigations into everything from cybercrime and fraud to nation state threat actors. In my law enforcement career I was a detective focusing on cyber crime, digital forensics, and internet research. Having built up my skills in traditional investigations of serious and complex crime I began to develop techniques and tactics to identify and prosecute criminals who used the internet, including some of the UK’s most prolific child sex offenders, fraudsters, and dark web criminals. I’m also an Instructor Candidate for the SANS Institute , the world’s largest information security research, training, and certification provider. I teach SEC497 Practical Open Source Intelligence and SEC587 Advanced Open Source Intelligence to students from Fortune 500 companies, government, military and law enforcement so that they will have the skills they need to have successful careers in cyber security and all aspects of internet investigation. I’m a confident and experienced public speaker, and I love to share my learning and research with others. I was also previously an executive board member of The OSINT Curious Project . This blog is purely for my own writing and research and my views are entirely my own. Twitter LinkedIn Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email","image_urls":[],"local_images":[]}
+{"source":"nixintel","url":"https://nixintel.info/author/nixintel/","title":"Nixintel","status":"ok","retrieved_at":"2026-08-29T16:31:02.622604+08:00","text":"Calculating Website Age & Tracking Changes With URL Dater Leave a Comment / OSINT Tools / Nixintel How can you determine the age of a webpage in a reliable way? URL Dater uses a range of different sources to present an accurate picture. Calculating Website Age & Tracking Changes With URL Dater Read More » Using SSL Certificates To Find Threat Actor Infrastructure 1 Comment / OSINT / Nixintel At last month’s SANS OSINT Summit I gave a talk the usefulness of SSL certificates for open source intelligence researchers. The talk looks at three recent examples of how information from certificate transparency logs can be used to discover, attribute, and unmask threat actor infrastructure. The video of the talk has now been published and you can Using SSL Certificates To Find Threat Actor Infrastructure Read More » Telegram For Cyber Investigators 2 Comments / OSINT / Nixintel Telegram is one of the most important platforms for OSINT investigators. I joined the Needlestack podcast to discuss how Telegram works and shared some practical OSINT advice along the way. Telegram For Cyber Investigators Read More » Digging Into Russian Disinfo Infrastructure 6 Comments / OSINT / Nixintel Disinformation and propaganda has been one of the key features of the war between Russia and Ukraine. One of the many groups that have sprung up to push pro-Russian propaganda narratives is a small hacktivist organisation called Beregini. This article by Givi Gigitashvili provides a useful introductory insight into the methods of Beregini by analysing Digging Into Russian Disinfo Infrastructure Read More » Verify Your Online Identities With Keybase 1 Comment / Security / Nixintel Twitter’s recent decision to remove blue check marks from accounts it has previously verified causes a number of issues for the platform and its users. One of the most obvious ones is around authentic identity. Without verification, how do I know that a particular account really does belong to the person or organisation who claims Verify Your Online Identities With Keybase Read More »","image_urls":["https://nixintel.info/wp-content/uploads/2023/04/twitter_profile.png","https://nixintel.info/wp-content/uploads/2023/07/Screenshot-2023-07-31-at-22.50.56.png","https://nixintel.info/wp-content/uploads/2026/01/Screenshot-2026-01-11-161045.png"],"local_images":["blog_data/images/blog_411c2c255975_0.bin","blog_data/images/blog_411c2c255975_1.bin","blog_data/images/blog_411c2c255975_2.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/contact/","title":"Contact","status":"ok","retrieved_at":"2026-08-29T16:30:15.301288+08:00","text":"Home Contact Contact To get in touch, please contact me via the form below. Alternately you can get in touch via LinkedIn . Please enable JavaScript in your browser to complete this form. Please enable JavaScript in your browser to complete this form. Name * First Last Email * Comment or Message Submit Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email","image_urls":["https://nixintel.info/wp-content/plugins/wpforms-lite/assets/images/submit-spin.svg"],"local_images":[]}
+{"source":"nixintel","url":"https://nixintel.info/copyright/","title":"Copyright","status":"ok","retrieved_at":"2026-08-29T16:35:04.916113+08:00","text":"Home Copyright Copyright © Steven Harris and nixintel.info, 2019-2023. Unauthorized use and/or duplication of this material without express and written permission from this site’s author/owner is strictly prohibited. Small excerpts and links may be used, provided that full and clear credit is given to Steven Harris and nixintel.info with appropriate and specific direction to the original content. You may NOT reuse or duplicate any content from this website as part of any training programme (whether private or public) or publish it elsewhere (whether for profit or not) without the express written authorisation of the site owner. Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email","image_urls":[],"local_images":[]}
+{"source":"nixintel","url":"https://nixintel.info/linux/build-your-own-custom-osint-machine-part-4/","title":"Build Your Own Custom OSINT Machine – part 4","status":"ok","retrieved_at":"2026-08-29T16:34:45.447812+08:00","text":"Home Linux Build Your Own Custom OSINT Machine – part 4 Build Your Own Custom OSINT Machine – part 4 9 Comments / Linux / By Nixintel The last post in this guide looked at how to install some useful OSINT programs for Linux directly from the internet. In this post I’ll show how to install some of the many popular Python-based OSINT tools that are available. It’s easy to feel intimidated by using the command line, but by the end of this guide it’ll be clear what pip, git, and Python are all about. Python is brilliant for carrying out a large number of repetitive tasks and sorting through data quickly. These tools can’t make your investigative decisions for you, but they can crawl the web and pull back data very quickly, certainly much faster than most browser-based tools will. In this guide I’ll go through the installation of reconaissance tool theHarvester step-by-step from the absolute basics all the way through to launching it with a custom alias. Then I’ll explain how to install recon tools like Photon , Sublist3r , and Gasmask , username search tool Sherlock , scraping tools for Twitter ( Twint ) and Instagram ( Instalooter ), phone number searcher PhoneInfoga , and password breach checker h8mail . It might seem like a lot now, but once you understand how these programs work, you’ll be cloning them from Github and using them for your research like there’s no tomorrow. Getting Started With Installation – Basics These programs don’t usually come with a nice shiny user interface like some of the programs you install from the Ubuntu Software Centre. This can make them seem complicated and installing them can cause a lot of frustration, but by the end of this guide you’ll know your Pip from your Git and be able to install a wide range of powerful OSINT tools. The guide is intended for people who are fairly new to Linux, so I’ll try and cover everything from the very beginning. In the DIY-Buscador Ubuntu machine, open up the terminal by pressing Ctrl+Alt+T . You’ll see something like this:   You live here now.   If you’ve never used a terminal before, don’t worry! The computer doesn’t care whether the instructions came from a shiny GUI that you clicked on or whether you typed the command into the terminal directly. For example in this previous post I showed how to install Stegosuite by finding it in the Ubuntu Store, clicking on “install” and entering my admin password to give it permission to run. In the terminal the exact same thing can be done by typing the following command: sudo apt install stegosuite sudo prompts me to enter my admin password and confirm that the program is authorised to run. Apt is simply the program that Ubuntu uses to manage software packages, so adding ‘install’ tells apt what I want it to do, and stegosuite tells apt which one of the thousands of available Ubuntu packages I want to install on my system. So it’s pretty obvious what this command would do: sudo apt remove stegosuite And stegosuite would be uninstalled, just like that. Notice that if you try to use apt without sudo, Linux won’t let you. If you’re not authorised, you aren’t allowed to modify the software or any part of the operating system. (On some older tutorials you might see “apt-get” instead of “apt”, but they do the same thing.) Getting Git Using sudo apt install programname works well for programs that are listed in the Ubuntu repository – but none of the OSINT Python tools we want to install are listed there. They’re all available on GitHub , so to get them installed on the OSINT machine it’s necessary to use a program called git . A few of the tools can also be installed using another program called Pip, but I’ll get to that shortly. Git is a complex tool used by developers for version control of their software, but for the purposes of this guide it’s only necessary to know that Git allows you to clone software directly from GitHub onto your computer. In the console, check to see what version of git is installed in Ubuntu by entering the following command: git --version You’ll be told that git is not installed! It isn’t part of Ubuntu by default, so quickly add it into your OSINT build with: sudo apt install git Press Y when prompted and git will install in a few moments. Pip and Python As of Ubuntu version 20.04, Python 2.7 is no longer installed in Ubuntu by default. The new default version is Python 3. To check this in the console type: python3 --version   The screenshot above is from Ubuntu 19.04, which did include Python 2. The latest and all future versions of Ubuntu will not include Python 2. Install With Pip Pip is a package manager for Python. It ensures that when you’re installing a Python program, all the necessary libraries and modules will be installed too. Usually these requirements are listed in a text file called requirements.txt, so installing all the necessary addons is usually as simple as: sudo pip3 install -r requirements.txt The other great thing about pip3 is that it allows you to install some Python programs with one simple command. This is much cleaner and easier than building software from GitHub. I’ll show how to install Twint this way later on. So for best practice, use the following guidelines: 1. If you have the choice to use pip to install directly (e.g. as with h8mail or Twint), use pip. 2. If not, use git. 3. If the program uses Python 3 (i.e. most of them) use python3 and pip3 in the console 4. Most tutorials often assume you’re running as root, i.e. with sudo and don’t explicitly mention it. In this build, it will always be necessary to put sudo in front of any pip or pip3 commands. Installing theHarvester It’s always easier to learn by doing rather than just reading so I’m going to demonstrate how to install theHarvester. theHarvester is an established tool that is used to find out about a particular domain. It will pull back e-mail addresses, PGP keys, IP addresses and other information about the domain you’re investigating. theHarvester Github page can be found here: h ttps://github.com/laramies/theHarvester . This URL is important, so copy it from your browser’s navigation bar and keep it in the clipboard. Open the terminal with Ctrl + Alt + T and enter the following, you can just paste the URL you copied into the terminal with Ctrl+Shift+V (not just Ctrl+V like on the regular Desktop): git clone https://github.com/laramies/theHarvester Now git is cloning all those files posted on GitHub directly to a folder in your home directory called theHarvester. Once git has finished cloning, move to that directory by typing cd theHarvester (note the terminal is case-sensitive) cd simply means “change directory”. To list the contents of the directory, simply enter: ls You’ll see something like this: There’s a file in there called requirements.txt. Before we can run theHarvester, we need to install those Python library requirements with pip3. Enter the following in the console: sudo pip3 install -r requirements.txt Pip will then install the extra software that is needed: Now it’s all done! To run theHarvester, stay in theHarvester directory and enter: python3 theHarvester.py -h Notice if you’ve typed python and not python3 the program won’t run because it needs the newer version of Python. All this command is doing is telling python3 to run a script called theHarvester.py. The -h flag on the end tells the script to open the help guide for the program. If it’s working correctly you’ll see something like this: Ta-da. It’s beyond the scope of this article to explain how to use theHarvester, but there’s a simple introduction here and in many other places on the web. This completes the installation of theHarvester – but there’s an customisation we can make to our OSINT build setup that will make using theHarvester just a little smoother. theHarvester Alias Shortcut Typing “python3 ~/theHarvester/theHarvester.py” before you start every single query gets a bit tiresome. Fortunately in Linux it is easy to customise everyting and so it’s possible to create a shortcut, known as an alias. This can be done by editing the .bashrc file that controls all your terminal settings. Open the terminal with Ctrl+Alt+T again and enter nano ~/.bashrc Nano is just the terminal’s built-in text editor. This opens up the .bashrc file that needs to be edited. When it opens, scroll to the bottom and add the following lines: #alias for theHarvester alias theharvester='python3 ~/theHarvester/theHarvester.py' Use Ctrl + X to exit, and Y when prompted to ask if you want to save the changes. Notice I made theharvester all lower case – it just makes typos less likely. Now close the terminal, and then open a new one so the changes take effect. Now just type: theharvester -h and theHarvester runs straight away. You can also run the command to launch queries directly e.g. theharvester -d somerandomsite.org -b google -l 500 That’s the basic formula for installing Python programs from GitHub. In the remainder of this article I’ll explain how to install a program with pip.   Installing Twint with Pip Pip makes installing packages a lot easier, so for this example I’m going to show it can be used to install Twint. Twint is a really flexible Twitter scraper. It grabs all kinds of data from Twitter and exports it to a wide range of formats like csv or SQL. There’s a good introduction to Twint here . The link to the Twint GitHub page is here. Notice that unlike theHarvester, Twint can be installed with either Git or Pip, (or even by using a Python virtual environment, which is not within the scope of this guide). As per the rules of thumb I mentioned above, if given a choice between Git or Pip, always go with Pip. It’ll soon be clear just how much less complex this is. In the terminal copy and paste the following: sudo pip3 install --upgrade -e git+https://github.com/twintproject/twint.git@origin/master#egg=twint Remember to preface the command with sudo or you’ll have trouble running it. Once it’s completed, simply type twint -h And you’ll see the program has installed correctly! It isn’t even necessary to create an alias, because Pip did this automatically during the installation. Example usage would be: twint -u nixintel -o nixinteltweets.csv --csv This would scrape all the Tweets from my Twitter account and save them to a csv file for further analysis. Installing Other Python OSINT Programs I’ve shown how to set up your custom OSINT machine for installing programs either with Git or directly with Pip. The rest of the guide will look at some other useful OSINT tools, what they do, the necessary commands to install them, and the entry needed in a .bashrc file to create an alias. For the purposes of this article, I’ve installed all of these programs in my DIY-Buscador VM, so I’ll vouch for the fact that all of these methods currently work!   Instalooter   GitHub Page : https://github.com/althonos/InstaLooter Scrapes content from a designated Instagram account. Requires IG login but no API key. Git or Pip ? Pip Console command: sudo pip3 install instaLooter (note upper-case L) Usage: instalooter -h (note lower case L) Alias : Automatically instalooter by default   H8mail 2.0   GitHub Page : https://github.com/khast3x/h8mail PyPi Page : https://pypi.org/project/h8mail/ H8mail checks e-mail addresses to see if their credentials have ever bene found in a breach. The real power of h8mail comes with its ability to query a 45GB breach compilation. This is available separately. You’ll need a lot of extra space in your VM if you want to fit this in. Git or Pip : Pip Console command : sudo pip3 install h8mail Usage: h8mail -h Alias : h8mail by default   Photon     GitHub page : https://github.com/s0md3v/Photon Photon is a fast OSINT crawler. Point it at a domain to recover associated e-mail addresses, DNS info, subdomains, social media accounts, and other information. Git or Pip: Git Console commands : git clone https://github.com/s0md3v/Photon cd Photon sudo pip install -r requirements.txt python3 photon.py -h Alias: alias photon='python3 ~/Photon/photon.py' Usage (with alias): photon -h   Sherlock   GitHub Page : https://github.com/sherlock-project/sherlock Sherlock is a fast username searcher. I previously wrote a usage guide and review here . Git or Pip? Git Console command: git clone https://github.com/sherlock-project/sherlock   cd sherlock sudo pip3 install -r requirements.txt python3 sherlock.py -h Alias: alias sherlock='python3 ~/sherlock/sherlock.py'   Usage (with alias) : sherlock nixintel     Gasmask   GitHub Page : https://github.com/twelvesec/gasmask An auto reconnaissance tool similar to Photon or the Harvester. Note this program now runs with Python 3. Git or Pip? Git Console command: git clone https://github.com/twelvesec/gasmask cd gasmask sudo pip3 install -r requirement.txt python gasmask.py -h Alias : alias gasmask='python3 ~/gasmask/gasmask.py' Usage (with alias) : gasmask -h   Sublist3r   GitHub page: https://github.com/aboul3la/Sublist3r A tool for identifying subdomains by querying the data held by search engines. Can bruteforce if necessary. Git or Pip? Git Console command: git clone https://github.com/aboul3la/Sublist3r cd Sublist3r sudo pip3 install -r requirements.txt python3 sublist3r.py -h Alias: alias sublister='python3 ~/Sublist3r/sublist3r.py' (note I dropped the 3, I made too many typos) Usage (with alias) : sublister -h     PhoneInfoga   GitHub page : https://github.com/sundowndev/PhoneInfoga/ Crawls dozens of resources to conduct OSINT on a target phone number. Be sure to read the Wiki article on bypassing the Google Captcha before using it. Git or Pip? Git Console command: git clone https://github.com/sundowndev/PhoneInfoga cd PhoneInfoga sudo pip3 install -r requirements.txt python3 phoneinfoga.py -h Alias: alias='python3 ~/PhoneInfoga/phoneinfoga.py' Usage (with alias): phoneinfoga -h     That concludes this part of the guide to building your own custom OSINT Linux machine. If you had little Linux experience before and managed to get these programs installed and working then kudos to you because the command line can be an unforgiving place but as you can see it can be used to do some really powerful things. The same method can be used to install other GitHub based tools like Skiptracer , Knock , Cloudflair, and many others. A few of these tools benefit from the addition of API keys, but that’s really for a separate post. This guide and the ones before it should make it clear just how simple it can be to create your own custom OSINT VM. In the next post I’ll explain how to clone and backup your OSINT VM in case it breaks, how to transfer it to another computer, and how you can hash it if needed. After that I’ll also suggest some useful OSINT addons for Firefox and Chrome. Part 5 of this series can be found here .                 Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 9 thoughts on “Build Your Own Custom OSINT Machine – part 4” mr loop 1st November 2019 at 11:36 am Hello, The harvester is not loading, I have triple checked the Alias I get the following message Errno 2 no such file or directory Loading... Reply Nixintel 1st November 2019 at 6:23 pm Does this error only occur when you try to run Harvester with an alias? I.e. does it run if you run it directly from the Harvester directory itself e.g /home/user ~ $ python theHarvester.py -h ? If it runs from the directory but not with the alias then the error is most likely because there is an issue with the file path or name. The command line is case sensitive so double check that the path in the alias is correct, including case sensitivity. Loading... Reply Mr pop 2nd November 2019 at 10:37 am Hello, Thanks will have a look. Just trying to sort out the geckodriver at the moment. Thanks for the reply and the amazing website 🙂 I really want to improve and get in to OSINT. This is a create resource. Loading... Reply Mr loop and pop 2nd November 2019 at 10:57 am Also it says that permission is denied from access ‘docker’ docker pull sundowndev/phoneinfoga:latest IN short I have managed to run PhoneInfoga, however after about 4 attempts of it working it is now showing the catcha (blocked). I have installed geckodriver which seems to let me run recon scans but it believe docker pull sundowndev/phoneinfoga:latest will solve the issue fully. Loading... Reply Mr poopy butthole 7th November 2019 at 2:29 pm So I managed to get back to it, and it is all working, I just started again and double checked everything. Thanks for the help and the site. PS glad to see your a Type O Negative fan \\m/ Loading... Reply Mr Mingster 20th February 2020 at 9:07 pm I have version 18 of ubuntu I have version 3.6.9 of python. Everything else is working but everytime i try and use the code for Git or for pip3 it says command not found. I cant access any of the programmes i need the most. Thank you for your tutorial anyway, it is great, hopefully you can help me with this.. Loading... Reply Nixintel 20th February 2020 at 10:10 pm It sounds like you might still need to install git and pip. To do so try: sudo apt install git sudo apt install python-pip (for Python 2.x) sudo apt install python3-pip (for Python 3.x) Try again once you’ve installed these and you should have a bit more luck. Loading... Reply Pingback: 如何制作自己的互联网存档 - iYouPort Pingback: POWERFUL OSINT investigative Techniques and Tactics (2024) Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_001-1.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_004-1.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_005-1.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_007-1.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_007.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_008-1.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_008.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_009-1.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_009.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_010-1.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_010.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_011.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_012-1.png","https://secure.gravatar.com/avatar/6474e292fccee2439c9f52a365d6c91badf863bb6b39a2291ebfcb2434ee84f0?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/85770c43be059ed877c3b5fa99e8b62e6a9b2406c217807dddcdd6a375c726b4?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/a8dbec59c215a7304ee0e9f72018ce377e1a7869da6ef4dc675dc1de3278de1e?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/b2c7aae6a5e70d8f81889d9b94e259653a95278a6af60e284bf4f8b8cfeb90f0?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/c65f0a237f8f1e9db129a777410a38151fe50b11f21f9951adc5863c9e163201?s=50&d=mm&r=g"],"local_images":["blog_data/images/blog_083acfa87d18_0.bin","blog_data/images/blog_083acfa87d18_1.bin","blog_data/images/blog_083acfa87d18_2.bin","blog_data/images/blog_083acfa87d18_3.bin","blog_data/images/blog_083acfa87d18_4.bin","blog_data/images/blog_083acfa87d18_5.bin","blog_data/images/blog_083acfa87d18_6.bin","blog_data/images/blog_083acfa87d18_7.bin","blog_data/images/blog_083acfa87d18_8.bin","blog_data/images/blog_083acfa87d18_9.bin","blog_data/images/blog_083acfa87d18_10.bin","blog_data/images/blog_083acfa87d18_11.bin","blog_data/images/blog_083acfa87d18_12.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/osint-tools/calculating-website-age-tracking-changes-with-url-dater/","title":"Calculating Website Age & Tracking Changes With URL Dater","status":"ok","retrieved_at":"2026-08-29T16:33:23.083499+08:00","text":"Home OSINT Tools Calculating Website Age & Tracking Changes With URL Dater Calculating Website Age & Tracking Changes With URL Dater Leave a Comment / OSINT Tools / By Nixintel How do you know how old a webpage really is? A core part of website investigation is determining precisely when site was created or when an article was published. For most sites this is rarely an issue of concern, but for websites that are intentionally misleading it can be more challenging. Websites created for fraud, phishing, disinformation or other deceptive purposes frequently misrepresent the age of the site in order to appear more established and authoritative than they really are. It’s also helpful to be able to find out exactly when an article was published and detect subsequent modifications. There are several ways to do this. Article publication dates might be obvious, but it is also trivial to edit publication timestamps and they cannot be relied upon. The Internet Archive can also be a useful indicator, but it has gaps in coverage and is slow to query. In any case a first crawl of a website will by definition always lag the actual creation of the site so it’s better to go upstream to find more reliable signals. To make this process quicker and easier I’ve put together URL Dater from a collection of old Python scripts that I’ve used for a few years but with a web interface to make the tooling and results a little easier to work with. URL Dater timeline output showing Last-Modified header timestamps and registration update information for Bellingcat.com URL Dater collects three sources of information to validate the age of a web page. First it uses RDAP (the replacement for WHOIS) to find out when the original domain was first registered and also when the registration was last updated. Secondly it uses certificate transparency logs to determine when the very first SSL certificate for that website was issued. Finally it connects to the target URL and reads the Last-Modified header timestamp from any images that are embedded on the page. These data points are combined together to produce a timeline showing when the site and its content were created or modified. RDAP RDAP (Registration Data Access Protocol) is a new standard for querying domain registration records. It replaces WHOIS, which was deprecated in January 2025 . It’s far easier to work with programmatically because the data is returned in a standard JSON format that can be easily parsed. The only limitation with this method is that a few TLDs still don’t currently support RDAP queries , and some that do choose not to share registration date information (why DENIC , why?). The RDAP information shows when a domain was first registered and when the registration records were last updated. If URL Dater doesn’t return RDAP registration information for the website domain then you can view WHOIS records via Big Domain Data or Whoxy as an alternative. First SSL Certificate Since almost all websites now support HTTPS it’s safe to assume that pretty much any website you want to research will have an SSL certificate. Any website without an SSL certificate is likely to be deranked in search results and users will also receive warnings in their browser that the site is insecure . It is extremely rare to find a modern website that doesn’t have an SSL certificate – even if it was created for malicious or deceptive purposes. This is helpful for researchers because since 2013 SSL certificate providers have made every certificate they issue publicly auditable via certificate transparency logs . URL Dater checks these logs via crt.sh to find the “Valid From” timestamp for the first security certificate issued for a domain. This fraudulent company imitated an existing organisation that was older and more established. Using URL Dater to retrieve the timestamp from the first SSL certificate showed that it was This provides a high confidence, third-party verified timestamp for when a website likely first went live. Just be aware that SSL certificates have a “Valid From” field and not an “Issued At” field, so the while the first certificate time is reliable and precise, it isn’t accurate to the exact minute. You can read more about this in the FAQ . Last Modified Headers The final indicator collected by URL Dater are the Last-Modified timestamps from images embedded on a webpage . This indicates the time when an image was last modified on the web server and is a reliable indicator for when the content was added to the webpage. Note this is separate from any timestamp metadata embedded in the image itself. The Last-Modified header timestamp value is derived from the web server itself and is significantly more difficult to alter or modify. Example of Last-Modified headers for images retrieved from the URL https://www.bellingcat.com/news/2025/12/17/how-russias-invasion-is-impacting-ukraines-youth/ on the Bellingcat website. The results distinguish between favicons and other images when presenting the findings. The main reason for doing this was that in practice site owners modify favicons far less regularly compared to other images on webpages so I found it helpful to make the distinction when trying to date the content accurately. Plotting the Last-Modified header timestamps I love Python and have used it my investigations for years but I never really took to learning front end web development. I’ve really benefited from the use of tools like Cursor to convert my Python scripts into Flask apps with a JS frontend. It also allowed me to add in some useful extra features like the ability to create timelines to visualise results. Results can also be exported in PDF, PNG or CSV format. Timeline visualisation for the URL https://www.bbc.co.uk/news/articles/ckgj1m1ze8go , as of 11 Jan 2026. It shows when the main domain was registered and updated, when the first SSL certificate was issued, and when specific images were last modified on the webpage. Users can zoom in on the timeline to plot exactly when specific images were Last-Modified. Installation and Known Issues The code is in the URL Dater GitHub repository . It’s a single container Docker app so as long as you have Docker installed on your host system you just need to clone the repo and build the container. git clone https://github.com/nixintel/urldater cd urldater docker compose up --build The main issues you’re likely to encounter are limitations of the underlying tools. For example, some TLDs don’t yet support RDAP , crt.sh (used for SSL history) is often offline, and some websites simply don’t use Last-Modified headers. For further details about the data is collected and what its limitations are, please read the FAQ . The demo server at Urldater.app is also running on a very lightweight server that occasionally struggles to process data from larger websites, which may result in performance issues. I strongly recommend self-hosting this on your own hardware for better performance. Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2026/01/Screenshot-2026-01-11-161045.png","https://nixintel.info/wp-content/uploads/2026/01/image-1.png","https://nixintel.info/wp-content/uploads/2026/01/image-2.png","https://nixintel.info/wp-content/uploads/2026/01/image-3.png","https://nixintel.info/wp-content/uploads/2026/01/image-4.png","https://nixintel.info/wp-content/uploads/2026/01/image-5.png","https://nixintel.info/wp-content/uploads/2026/01/image-6.png"],"local_images":["blog_data/images/blog_7b882fcc2ee7_0.bin","blog_data/images/blog_7b882fcc2ee7_1.bin","blog_data/images/blog_7b882fcc2ee7_2.bin","blog_data/images/blog_7b882fcc2ee7_3.bin","blog_data/images/blog_7b882fcc2ee7_4.bin","blog_data/images/blog_7b882fcc2ee7_5.bin","blog_data/images/blog_7b882fcc2ee7_6.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/osint-tools/six-tools-to-help-with-geolocation/","title":"","status":"ok","retrieved_at":"2026-08-29T16:32:35.676688+08:00","text":"Home OSINT Tools Six Tools To Help With Geolocation Six Tools To Help With Geolocation 3 Comments / OSINT Tools / By Nixintel If you’ve been interested in geolocation for any length of time, you’ll already be familiar with some of the most common tools that researchers make use of: Google Maps & Street View , Google Earth , reverse image search tools , Suncalc , and so on. There are many lesser-known tools that are also useful and can help to fill gaps in your investigations. Let’s have a look at a few of them. What Is Where What Is Where is a more user friendly way of querying the Open Street Map database. It helps you to build queries in a similar way to Overpass Turbo , but without the complex query language and syntax. So if you want to find parks in London, or schools within 200m of a main road in Berlin, you can build the queries using a series of drop down menus that match OSM’s pre-defined categories. For example you can pick a category from the menu like “Aerodrome” and then use an appropriate keyword from the OSM Tag database to refine your search. This makes your results more accurate but will also help to keep the server response time low. The aerodrome category is refined by adding the “military” keyword. If you get stuck there are several example queries in the site documentation that you can customise and adapt for your own needs. It’s still worth learning the Overpass Turbo query language if you intend to use the tool regularly, but What Is Where is a great place to get started. Kartaview Kartaview works in a similar way to Google Street View in that it offers street-level imagery that is accessed from an interactive map but it differs from Street View in two important ways. Firstly the images are uploaded directly by users from their mobile devices. There is no Kartaview Car. Secondly Kartaview offers coverage in areas where Google lacks it, such as in Germany. It’s also very similar to Mapillary , even if it is not as well known. It’s possible to see the content uploaded by each individual user. Kartaview contributors are incentivised to upload content via a leaderboard ranking system which rewards the amount of content uploaded. Users also have their own profile pages where it is possible to see the images uploaded by each user. For example this is the user profile of current all-time leader JB Brown who has uploaded more than 30 million images at the time of writing. Unlike other platforms, Kartaview also displays some metadata associated with the uploaded images such as timestamps, device, and operating system information. Open Traffic Cam Open Traffic Cam is a collection of publicly accessible traffic camera feeds from the USA. Simply zoom to the section of the map that you’re interested in, and click on one of the pins to view the camera footage. Getting results with this tool can be a little hit and miss. Some cameras are offline or no longer updated so there are a few dead links but the majority still seem to work. Google Earth: Sunlight & Shadows Google Earth Pro (the desktop version) needs little introduction as a geolocation tool, but you might not be aware of the Sunlight tracker that allows you to plot the sun position and shadow lengths that help with verifying the time of day. It lacks the fine detail of Suncalc, but it presents the information in a way that is much clearer. Here’s Frankfurt in Google Earth (3D buildings are enabled). Frankfurt in Google Earth. By clicking on the sun icon in the menu bar, a slider appears that can be used to adjust the time and date. The shadow and sun position will adjust automatically. Adjusting the slider changes the time and shadows adjust accordingly. The sun position moves too. Here’s the sun as seen from Frankfurt at around sunrise time on 24th July 2022: Sunrise view. Now here’s the same position, but in the middle of the night. Note the star constellations. The stars reflect the Earth’s rotation. If you want to be more precise with your timings, click on the spanner icon next to the slider and enter your time/date parameters manually: The Date and Time options allow you to enter specific times more easily. F4 Map F4Map uses Open Street Map data to plot individual buildings on a 3D map. It’s an extremely useful tool when there is no 3D building coverage in Google Earth and when your verification requires a high level of detail. Here’s Hamburg as rendered by F4Map: F4Map renders individual buildings with a high level of detail. F4 Map also supports the display of shadows, weather conditions and the sun position at different times of day, although this is limited to just morning, noon, evening, and night. To turn features on and off, just click on the settings menu and choose Graphic Options. F4Map allows time/date/weather customisations. The 3D buildings are based on Open Street Map data, so global coverage is much wider than 3D building locations in Google or Bing Maps, which rely on complex layers of aerial imagery for the 3D effect. Even more useful is the incorporation of 3D terrain data to render landscapes as they appear in real life. It isn’t enabled by default, so to activate it use Settings > Graphic Options > Ground Elevations. Here’s Innsbruck before and after Ground Elevations are enabled: Before: no 3D terrain enabled. After: the same location with 3D mode and ground elevation enabled. 3D Sun Path 3D Sun Path is made by Andrew Marsh and lets you visualise the sun’s position, azimuth and shadow length when you’re trying to chronolocate an image. It’s similar to Suncalc and in my opinion it displays the necessary information in a much clearer way. 3D Sun Path shows the sun’s bearing, azimuth (height in the sky) and shadow length for any given date/time/location. It is also integrated with a wide range of open source mapping and satellite image tools for more refined results. Satellite images and a variety of sun-path tools are incorporated into the tool. Simply choose your location and enter time/date parameters to track the sun’s position and shadow lengths for that location. These are just a few of the many useful but less well-known geolocation tools. If you found this interesting I’ve written many other posts about geolocation techniques , and there are other useful tools in my OSINT bookmark collection . I’ve also made a couple of Ten Minute Tips videos on geolocation that you can find here . Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 3 thoughts on “Six Tools To Help With Geolocation” katinukas 25th July 2022 at 8:35 am F4 Map: “Oops! Unauthorized F4map API usage. If you are this website administrator, please contact the support at [email protected] .” Loading... Reply Juan Smith Perera 28th September 2022 at 6:40 pm Great post. Great tools. Thanks for sharing Loading... Reply Jesús 28th December 2022 at 7:52 pm Thanks a lot. Loud and clear. Very well explained. Loading... Reply Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2022/07/image-1.png","https://nixintel.info/wp-content/uploads/2022/07/image-10.png","https://nixintel.info/wp-content/uploads/2022/07/image-11.png","https://nixintel.info/wp-content/uploads/2022/07/image-12.png","https://nixintel.info/wp-content/uploads/2022/07/image-13.png","https://nixintel.info/wp-content/uploads/2022/07/image-14.png","https://nixintel.info/wp-content/uploads/2022/07/image-15.png","https://nixintel.info/wp-content/uploads/2022/07/image-16.png","https://nixintel.info/wp-content/uploads/2022/07/image-17.png","https://nixintel.info/wp-content/uploads/2022/07/image-4-2048x963.png","https://nixintel.info/wp-content/uploads/2022/07/image-5.png","https://nixintel.info/wp-content/uploads/2022/07/image-6.png","https://nixintel.info/wp-content/uploads/2022/07/image-7.png","https://nixintel.info/wp-content/uploads/2022/07/image-8.png","https://nixintel.info/wp-content/uploads/2022/07/image-9.png","https://nixintel.info/wp-content/uploads/2022/07/image.png","https://secure.gravatar.com/avatar/7dcda0872150b5af240ee89c9a4b48b315799f2e9e28cbac9bfa20f1dec9d10d?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/9be338a10be4ebfb9ff429763c776af53b6c0bae891d96381504453bad27bd91?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/cf49af0034a3311009fc23b4918ea8e470990ce3415018e0e7854f00b053ff82?s=50&d=mm&r=g"],"local_images":["blog_data/images/blog_ef012822ce5f_0.bin","blog_data/images/blog_ef012822ce5f_1.bin","blog_data/images/blog_ef012822ce5f_2.bin","blog_data/images/blog_ef012822ce5f_3.bin","blog_data/images/blog_ef012822ce5f_4.bin","blog_data/images/blog_ef012822ce5f_5.bin","blog_data/images/blog_ef012822ce5f_6.bin","blog_data/images/blog_ef012822ce5f_7.bin","blog_data/images/blog_ef012822ce5f_8.bin","blog_data/images/blog_ef012822ce5f_9.bin","blog_data/images/blog_ef012822ce5f_10.bin","blog_data/images/blog_ef012822ce5f_11.bin","blog_data/images/blog_ef012822ce5f_12.bin","blog_data/images/blog_ef012822ce5f_13.bin","blog_data/images/blog_ef012822ce5f_14.bin","blog_data/images/blog_ef012822ce5f_15.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/osint/counting-crowds-in-public-spaces/","title":"","status":"ok","retrieved_at":"2026-08-29T16:31:13.867606+08:00","text":"Home OSINT Counting Crowds In Public Spaces Counting Crowds In Public Spaces 5 Comments / OSINT / By Nixintel This week’s huge protests in Israel drew huge crowds to the streets – but how many people took part? Crowd sizes are often used as evidence to show how widely supported a particular cause is, so being able to determine how many people took part in a demonstration is an important skill for those working in verification. Fortunately counting crowds in public spaces has been made easier than ever before by the creators of MapChecking . It is powered by Google Maps and allows researchers to plot a geographic area and then calculate the number of people that could fit in that space. There are three simple steps to follow: 1. Find the location. 2. Define the count area. 3. Calculate the crowd density. Let’s work our way through them to work out roughly how many people are shown in the image above. Find The Location First we need to identify the precise location. Fortunately with public protests this isn’t usually too difficult due to widespread media coverage and documentation. The image above was taken in Tel Aviv, looking along Giv’at HaTahmoshet St. A panoramic photo was taken during the protest and uploaded to Google Street View. The tall cylindrical building on the left is a government complex. Someone who was at the protest has already uploaded a panoramic photo from this location so verifying that this is the correct place is quite straightforward. Define The Count Area Now we’ve identified the location, the next thing we need to do is to use MapChecking to draw in the area where we can see the crowd in the original photo. We need to try and replicate this area: For the sake of accuracy it’s important to remember that there will be people in the crowd that we cannot see in this map due to the obstruction of buildings. For greater accuracy combining several photos from different angles would be better, but for the sake of this tutorial we’ll keep it simple. We’ve already identified the location on the map so now we need to replicate this in MapChecking. This is as simple as navigating to the location in the map interface and using the mouse to draw the area where we see the crowd in the photo. The final shape looks something like this: MapCheck will use the highlighted shape to calculate how many people were present. Calculate The Crowd Density There’s one last step before we can work out roughly how many people are present in the image. We need to know the density of people per square metre so we can know how many are in the search area. MapChecking allows us to adjust the density with a slider: The slider is used to adjust the crowd density. The biggest challenge is how to actually work out the density in the first place. The crowd isn’t evenly spaced so we need to accept that our answer will not be ultra-precise down to a single figure, but usually an approximate value is enough. To help with this the site provides several sample images that show what different crowd densities look like, as documented in this research by Keith Still . Since we have additional close up footage of the crowd thanks to the Google Photo spheres we can compare them with the baseline images from Keith Still’s research to form a rough idea of the density. Here’s the crowd density in the middle of the protest: Crowd density as captured at the scene and uploaded to Street View. Let’s compare them to the baseline images. The crowd looks quite packed, but people are still able to hold their phones out in front of them and hold flags so they are not so squeezed that they can’t move. It doesn’t look dense enough for 6 people per square metre. It’s certainly higher than 2 people per square metre though. There isn’t this much space between people in the crowd in the picture: Somewhere between 3-4 people per square metre looks like a better approximation: To calculate the final number, I’m going to use the figure of 3.5 people per square metre. The crowd is denser in the centre, but more dispersed at the edges. Using the slider to enter the density value tells us how many people are in the area that we drew to match the photo: At a density of 3.5 people per sqm, there are approx 112,000 people in the image. To reflect the slight uncertainty caused by the varied crowd density, it’s helpful to be able to adjust the slider to get an upper and lower range of possible crowd size. At 2.5 people per square metre the crowd size drops to just under 80,000, rising to 140,000 for a density of 4.5 people per square metre. The correct figure will be part way between these two. If you enjoyed this post, check out my other ones on geolocation here . Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 5 thoughts on “Counting Crowds In Public Spaces” Arnaud G 29th March 2023 at 1:50 pm Thanks this is super interesting. In the case of the recent demonstrations in France, taking the example of Paris, how would you go about counting the # of participants in a day? My concern is that crowds move along a certain path and numbers may vary at different times. Unions numbers and police numbers vary greatly. Loading... Reply Nixintel 29th March 2023 at 2:04 pm Two approaches that would help: 1) As many photos of possible of the areas where you are trying to measure. 2) Identify the approximate time of the photos. In your conclusions you should then be able to show a range of possible crowd sizes but also how they peaked and troughed at different times. e.g. at 1200 we observed between X and Y number of people in locations A,B and C. By 1900 this had increased to between XX and YY etc. A more advanced technique for counting moving crowds would be to run video footage fo the crowd and count them with Amazon’s Rekognition People Path tool, but this is more complex to achieve. https://docs.aws.amazon.com/rekognition/latest/dg/persons.html Loading... Reply Pingback: Counting Crowds In Public Spaces – NixIntel – Library Project XIII: Seven Heavenly Rabbits Edition Pingback: Counting Crowds In Public Spaces - Whalers Blog Pingback: Counting Crowds In Public Spaces - Whalers Blog Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2023/03/2-sqm.png","https://nixintel.info/wp-content/uploads/2023/03/3-4sqm.png","https://nixintel.info/wp-content/uploads/2023/03/6-sqm.png","https://nixintel.info/wp-content/uploads/2023/03/cover.png","https://nixintel.info/wp-content/uploads/2023/03/crowd_area.png","https://nixintel.info/wp-content/uploads/2023/03/crowd_mapped.png","https://nixintel.info/wp-content/uploads/2023/03/density1.png","https://nixintel.info/wp-content/uploads/2023/03/photo_bubble.png","https://nixintel.info/wp-content/uploads/2023/03/slider.png","https://nixintel.info/wp-content/uploads/2023/03/slider2.png","https://nixintel.info/wp-content/uploads/2023/03/street_overview.png","https://secure.gravatar.com/avatar/a8dbec59c215a7304ee0e9f72018ce377e1a7869da6ef4dc675dc1de3278de1e?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/ad642ab4353b7901b76df43cf9ab015a7ee05ae84eeb8a982e72e064d22604fa?s=50&d=mm&r=g"],"local_images":["blog_data/images/blog_ecb6460988fe_0.bin","blog_data/images/blog_ecb6460988fe_1.bin","blog_data/images/blog_ecb6460988fe_2.bin","blog_data/images/blog_ecb6460988fe_3.bin","blog_data/images/blog_ecb6460988fe_4.bin","blog_data/images/blog_ecb6460988fe_5.bin","blog_data/images/blog_ecb6460988fe_6.bin","blog_data/images/blog_ecb6460988fe_7.bin","blog_data/images/blog_ecb6460988fe_8.bin","blog_data/images/blog_ecb6460988fe_9.bin","blog_data/images/blog_ecb6460988fe_10.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/osint/digging-into-russian-disinfo-infrastructure/","title":"Digging Into Russian Disinfo Infrastructure","status":"ok","retrieved_at":"2026-08-29T16:33:50.871413+08:00","text":"Home OSINT Digging Into Russian Disinfo Infrastructure Digging Into Russian Disinfo Infrastructure 6 Comments / OSINT / By Nixintel Disinformation and propaganda has been one of the key features of the war between Russia and Ukraine. One of the many groups that have sprung up to push pro-Russian propaganda narratives is a small hacktivist organisation called Beregini . This article by Givi Gigitashvili provides a useful introductory insight into the methods of Beregini by analysing the content of some of their recent leaks. For this post I thought it would be interesting to see what insights might be gained from digging into the web infrastructure of the Beregini group website. It’ll also be a good opportunity to run through a few command line techniques to practice website investigation. The Goal and The Tools We’re going to start with a few passive recon techniques to help to identify where the main Beregini website is hosted, and what (if anything) this can tell us about the group. Although Beregini are highly active on Telegram, they also have a website at bg14.ru . We can start by gathering a few data points about the website to see what we can find out. The Beregini website at bg14.ru . As far as possible I’m going to use command line tools to find the information that I need. I’m a strong believer that OSINT practitioners who can use simple commands to gather and process raw data have a big advantage when it comes to intelligence collection. The main reason is that this makes it much easier to begin to scale and automate research in a way that is much more difficult to do with browser based methods. Let’s have a look at a few basic commands to get started. Whois Detailed Whois records with real personal data in them are largely a thing of the past, but that doesn’t mean that they aren’t useful. Here’s the Whois record for bg14.ru: domain: BG14.RU nserver: harleigh.ns.cloudflare.com. nserver: pablo.ns.cloudflare.com. state: REGISTERED, DELEGATED, UNVERIFIED person: Private Person registrar: PIN-RU admin-contact: https://whois.pinspb.ru created: 2022-03-09T12:40:12Z paid-till: 2024-03-09T12:40:12Z free-date: 2024-04-09 source: TCI Performing a Whois lookup with a web-based tool is quite straightfoward, but most versions of Linux and Mac OS have a command line whois tool built in. It has a lot more options than a regular web-based Whois lookup, but a basic enquiry looks like this: whois bg14.ru This returns the same data as in the web tool. Instead of taking a screenshot I can save the output to a text file for documentation purposes. whois bg14.ru > whois_lookup.txt Regardless of the method used, the Whois data doesn’t tell us who owns the site (of course) but it does reveal three useful snippets of information: The site is using Cloudflare nameservers. This probably means that finding the true IP address of the website (and thus the real hosting company and server location) is going to require a little extra effort. The admin contact for the site is associated to another domain – pinspb.ru . We’ll need to look at who this domain belongs to and what it is for. The domain was created on 9th March 2022, which ties in with the site first being recorded by the internet archive on 16th March 2022. However Beregini have been active since at least 2016. This most likely means they have another web presence somewhere else that we’ll need to try and locate in due course, although we won’t cover that in this post. The Internet Archive first documented the site in March 2022, a week after the domain was registered. DNS Records Time to start using the command line again. To find where the domain is hosted we need to know the IP address. We can use the built in Unix tool dig to find this. Here’s the basic command: dig bg14.ru Which returns: ; <<>> DiG 9.16.1-Ubuntu <<>> bg14.ru ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51636 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;bg14.ru. IN A ;; ANSWER SECTION: bg14.ru. 300 IN A 172.67.163.61 bg14.ru. 300 IN A 104.21.50.131 This is far too noisy to read effectively. We can trim the results by using the +noall and +answer options like this: dig bg14.ru +noall +answer The results are now much easier to read. We have two DNS A records that show the IP addresses where the website is located: bg14.ru. 300 IN A 104.21.50.131 bg14.ru. 300 IN A 172.67.163.61 We still need to think about documentating our research as we go along. To do this we can tidy up the output of the command a little bit more and save the output to a CSV file: dig bg14.ru +noall +answer | awk '{sub(/\\.$/, \"\", $1);print $1 \",\" $5}' > ipaddresses.csv To save the data to a nice tidy CSV we can pass the result of the dig command using the pipe ( | ) symbol to the awk command. Awk is very powerful and lets us modify text output on the fly. In this case the first part of the awk command sub(/.$/, \"\", $1) removes the trailing dot from the domain name in the first field ( $1) and replaces it with an empty value ( \"\") . The next step of the awk command print $1 \",\" $5 will print fields 1 and 5 from the dig results, and place a comma between them. The output of this command is saved to a file ipaddresses.csv , which looks like this: bg14.ru,172.67.163.61 bg14.ru,104.21.50.131 You might be thinking at this point that this all looks quite nerdy and so far you haven’t got any extra data that you couldn’t have grabbed from a tool like DNSDumpster . If you’re only looking at one single domain that is possibly true (depending on your typing speed and willingness to rely on cached results instead of live data…), but what if you want to grab the same information for 5, 10, 500, or 10000 domains at once? Collecting data this way is much faster and easily repeatable than manually copying and pasting domain names into Central Ops or View DNS to get the same data. Who Owns The IP Address? So far we have two IP addresses for the Beregini website, but who do they belong to? Since Whois records are published for IP addresses as well as for domains we can stay in the command line and find that out who these IP addresses belong to with another Whois lookup. A word of caution at this point: IP address whois records only show the ISP or hosting company that a particular IP address was allocated to. It does not tell you which of that organisation’s clients or customers was using that IP address at any particular time. This means that we can’t use IP whois records to identify individuals, but we can at least know which ISP or hosting organisation they use. Here’s the command to find who owns one of the bg14.ru IP addresses: whois 172.67.163.61 This query returns a lot of information, including details about who owns this IP address: NetRange: 172.64.0.0 - 172.71.255.255 CIDR: 172.64.0.0/13 NetName: CLOUDFLARENET NetHandle: NET-172-64-0-0-1 Parent: NET172 (NET-172-0-0-0-0) NetType: Direct Allocation OriginAS: AS13335 Organization: Cloudflare, Inc. (CLOUD14) RegDate: 2015-02-25 Updated: 2021-05-26 As we suspected from the original Whois lookup, the organization field reveals that Beregini are using an IP address belonging to Cloudflare. This means finding their true IP address will be a little bit difficult, but it is still possible. Finding The IP Address Behind Cloudflare There’s a common misconception among internet investigators that Cloudflare are a hosting company. They are not. Cloudflare is a Content Delivery Network (CDN). Cloudflare relays content that is hosted elsewhere all across the world through its vast global network of servers. This speeds up the delivery of content to users and also means that Cloudflare can use its huge resources to protect sites from DDOS and malicious traffic. It’s a great resource but the unfortunate side affect for investigators is that when you query the IP address of a domain that uses Cloudflare you only get the IP address of a Cloudflare CDN server that is near(ish) to your location. This effect also explains why if you used the same dig command that I used earlier, you probably got different IP addresses to the ones shown above. Cloudflare protects websites and speeds up content delivery, but the content is hosted elsewhere. So we need to find a way to find the real IP address for bg14.ru. This is a complex topic and there isn’t one single method that works every time. I gave a talk on this subject called “ Finding Fraudsters Behind Cloudflare ” at the 2022 SANS OSINT Summit that goes into this in a lot more detail. For now we’ll focus on one quick and easy(ish) method that actually works to find the Beregini website’s real IP address by using Censys . Censys Query Censys is a a huge collection of thousands of different data points collected from all across the web. It constantly gathers information about the services, open ports and other data that it finds at each IP address it visits. As well as host data, Censys also logs the details of security certificates and parses them into a searchable format. The result is a vast collection of useful datapoints that we can query to find information about sites and services that we are looking for. It’s beyond the scope of this article to discuss Censys in more depth, but you can read more about their collection methods here . The Censys search portal at https://search.censys.io Censys isn’t Google. You’re unlikely to be able to throw keywords into the search bar and hope you can find what you’re looking for (although sometimes you might). Censys has it’s own query language that we can use to search for specific types of data, so we’ll need to think carefully about exactly which datapoints we want to look for. There’s a few places we could start, but I’m going to see if any IP addresses can be linked to any certificates that mention bg14.ru. The certificate transparency log for bg14.ru at https://crt.sh My rationale for starting here is that the certificate transparency log for bg14.ru shows that many certificates have been issued for the site by Let’s Encrypt and that Beregini have opted not to use Cloudflare’s own certificate service. There’s nothing unusual about this, but it might mean that we can use Censys to search for hosts where there is a Let’s Encrypt certificate with a common name that matches bg14.ru. If Censys has previously found this certificate and associated it to a non-Cloudflare host we might be able to find a little gap that leads to the real IP address. The Censys query will looks something like the one below. It tells Censys to show any hosts where there is a security certificate containing the common name “bg14.ru”: services.tls.certificates.leaf_data.subject.common_name:bg14.ru Entering the search query using the Censys syntax language. Sure enough, our hunch was correct. Censys has logged at least one certificate for bg14.ru and they’ve associated it to an IP address…and this one doesn’t belong to Cloudflare. The IP address linked to the bg14.ru domain by Censys. Could 91[.]243[.]50[.]197 be the real IP address for the Beregini website? It’s possible. We’ll look at a method for verifying this shortly, but let’s see what other information Censys found first. Whois information for the IP address. There’s some Whois information included in the Censys entry. It tells us that the IP address where bg14.ru is hosted belongs to an ISP based not in Ukraine, but in St Petersburg, Russia. Remember that Beregini purport to be dissatisfied Ukranians – but the infrastructure they are using certainly isn’t based in Ukraine, it’s in Russia. This is an important point although it isn’t completely conclusive. There doesn’t have to be a firm geographic link between an organisation and the hosting arrangements for its website. Yet of all the countries in all of the world where Beregini could have chosen to host their server, they chose a hosting company based in St Petersburg. Screenshot of the website at pindc.ru, translated with Google Translate. The hosting company website at pindc.ru refers visitors to their main website at pinspb.ru . If this second domain sounds familiar that’s because we came across it the in the admin contact email for the bg14.ru Whois entry. It looks like Beregini are using the St Petersburg company for both their hosting and domain registration arrangements. Thanks to a user-uploaded photo, we can even see what the inside of the data centre looks like courtesy of Google Street View . A photo of the inside of the data centre where bg14.ru is hosted. Source: https://goo.gl /maps/UyMvgbXYHkTbDq2A6 On the balance of probabilities this tends to support the hypothesis that the Beregini group are Russian based and backed, rather than the dissident Ukranians of their public persona. This finding is not conclusive by itself, but it is certainly an interesting place to begin further enquiries. Final Verification So far we’ve used completely passive techniques to find information about the Beregini website and we’ve got a fairly decent hunch about the true IP address for their website and its hosting arrangements. We can still do better than “decent hunch” and actually verify whether or not the website really is located there. These techniques are active and involve connecting to the website directly, so consider OPSEC measures like a VPN when undertaking research like this. We’re going to use the command line one last time. It seems likely that the true IP address for the Beregini website is 91[.]243[.]50[.]197 , so we’re going to use the curl command to see if we can grab the bg14.ru website content directly from that IP and either confirm or rule out our theory. First let’s grab the website content directly with a URL. curl will default to the IP address returned by a DNS request, so this will be directly from Cloudflare. curl -k https://bg14.ru -vv The -vv option provides more verbose output so we can see what curl is doing when it retrieves the webpage. The -k option tells curl to skip any issues caused when connecting via https. As expected, we get all the raw CSS and HTML from the webpage as served via Cloudflare: * Trying 172.67.163.61:443... * TCP_NODELAY set * Connected to bg14.ru (172.67.163.61) port 443 (#0) *snip* < server: cloudflare < cf-ray: 7ef83309897874b1-LHR < alt-svc: h3=\":443\"; ma=86400 ... <link rel=\"pingback\" href=\"https://bg14.ru/xmlrpc.php\"> <title>BEREGINI</title> etc... What if we try and grab the site content directly from the IP address? This won’t always work, especially when a webserver has been configured to ignore direct connections to the IP address or if multiple sites share the same IP, but we can see if it’s still possible. Here’s the command: curl -k https://91.243.50.197 -vv And the result: * Trying 91.243.50.197:443... * TCP_NODELAY set * Connected to 91.243.50.197 (91.243.50.197) port 443 (#0) ... SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 * ALPN, server accepted to use h2 * Server certificate: * subject: CN=bg14.ru * start date: Jun 17 02:19:31 2023 GMT * expire date: Sep 15 02:19:30 2023 GMT * issuer: C=US; O=Let's Encrypt; CN=R3 * SSL certificate verify ok. We don’t get the full web page content this way, but we do pull back the security certificate for bg14.ru . It looks like our hunch is proving to be correct. There’s one more technique to try. We can tell curl to ignore the Cloudflare IP address returned by DNS records and instead force it to try and resolve the website at our target IP. If it can, the site content should appear in the terminal. If it can’t, we’ll get nothing back. curl -k https://bg14.ru --resolve bg14.ru:443:91.243.50.197 -vv The addition of the --resolve option tells curl to use our target IP address to connect to the site on port 443 (HTTPS). Here’s the result: Added bg14.ru:443:91.243.50.197 to DNS cache * Hostname bg14.ru was found in DNS cache * Trying 91.243.50.197:443... * TCP_NODELAY set * Connected to bg14.ru (91.243.50.197) port 443 (#0) ... * Server certificate: * subject: CN=bg14.ru * start date: Jun 17 02:19:31 2023 GMT * expire date: Sep 15 02:19:30 2023 GMT * issuer: C=US; O=Let's Encrypt; CN=R3 * SSL certificate verify ok. ... <link rel=\"pingback\" href=\"https://bg14.ru/xmlrpc.php\"> <title>BEREGINI</title> etc... Success! We’ve managed to retrieve the bg14.ru site content directly from the original hosting server and verified what we found with Censys. This means we can be confident about the site’s true IP address, ISP, and server location. It also reveals useful additional information about Beregini’s infrastructure and vendor choices that we can use in further research/ I’m an experienced investigator and OSINT practitioner and I’m currently looking for new work. If you think my skills could help you or your organisation, then please get in touch . Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 6 thoughts on “Digging Into Russian Disinfo Infrastructure” Kenshiro Watanabe 4th August 2023 at 7:19 pm Great article on disinformation and verification! Thank you so much! Loading... Reply Luris Sucak 7th August 2023 at 10:33 pm Interesting stuff! Learning new stuff every day. I’m surprised I didn’t know that about Cloudflare Loading... Reply thearmchairdetective 25th August 2023 at 9:35 am Nice One, so glad the blogs still alive. Miss your tweets. Loading... Reply Docal 27th June 2024 at 3:08 pm Well done Loading... Reply Teter 27th June 2024 at 4:44 pm Very nice Loading... Reply Pingback: Digging Into Russian Disinfo Infrastructure - Whalers Blog Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2023/07/Screenshot-2023-07-31-at-22.43.21.png","https://nixintel.info/wp-content/uploads/2023/07/Screenshot-2023-07-31-at-22.50.56.png","https://nixintel.info/wp-content/uploads/2023/07/image-1.png","https://nixintel.info/wp-content/uploads/2023/07/image-2.png","https://nixintel.info/wp-content/uploads/2023/07/image-3.png","https://nixintel.info/wp-content/uploads/2023/07/image-4.png","https://nixintel.info/wp-content/uploads/2023/07/image-5.png","https://nixintel.info/wp-content/uploads/2023/07/image-6.png","https://nixintel.info/wp-content/uploads/2023/07/image-7.png","https://nixintel.info/wp-content/uploads/2023/07/image-8.png","https://nixintel.info/wp-content/uploads/2023/07/image.png","https://secure.gravatar.com/avatar/0133cb1352133a63fd006c5f6a7a4770558e65d737bfb197e798faa0255d7f52?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/193fd8c154214c0e9ddc9c0cd3ce9ca5094f5855c9b103e954865a4138343f66?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/4786774c85f22a5c9b0050d0e512f453512db3515fba17adadfddce8a6b09036?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/69e81abba6af60daff3d0e6640b598b18a1d39c0ac344d0e46a42108835a845f?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/fff61f74f260c1aa431b806b98deffcd0dbc242fe6316e39f60909cc89c25225?s=50&d=mm&r=g"],"local_images":["blog_data/images/blog_7828d506708f_0.bin","blog_data/images/blog_7828d506708f_1.bin","blog_data/images/blog_7828d506708f_2.bin","blog_data/images/blog_7828d506708f_3.bin","blog_data/images/blog_7828d506708f_4.bin","blog_data/images/blog_7828d506708f_5.bin","blog_data/images/blog_7828d506708f_6.bin","blog_data/images/blog_7828d506708f_7.bin","blog_data/images/blog_7828d506708f_8.bin","blog_data/images/blog_7828d506708f_9.bin","blog_data/images/blog_7828d506708f_10.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/osint/geolocation-at-the-retail-park/","title":"","status":"ok","retrieved_at":"2026-08-29T16:30:21.797994+08:00","text":"Home OSINT Geolocation: At The Retail Park Geolocation: At The Retail Park 3 Comments / OSINT / By Nixintel Some images are easier to geolocate than others. If an image is easy to geolocate it is generally because at least one of the following three conditions apply: The image context makes it clear. For example there are GPS coordinates embedded in the image, or there is information about the location posted to the internet alongside the image. A reverse image search tool like Google Lens or Yandex is able to automatically recognise details in the image that identify the location. There are researchable map markers in the image, for example sign posts, business names, prominent landmarks etc. Sometimes none of these conditions apply. When this is the case geolocation becomes much harder and a more methodological structure is needed. Here’s a walkthrough of such an approach to find where the photo below was taken. The challenge photo. The photo was originally posted by Conor Nolan at 15:28 UTC on Jan 15th 2023. Conor tells us that the image was taken “just now” so at least we know when the image was taken. The problem is we don’t know much else. There’s no helpful GPS data, no luck with a reverse image search, and not much in the way of geographic information that we can easily search for straight away. We need a more structured methodology to find where Conor took this photo. I have written about gap analysis many times before and will use the same simple investigative structure here. There are four questions to follow to find the answer: What do I know? What does this mean? So what do I need to know? How do I find out? So let’s start at the beginning… What Do We Know? There’s little information in Conor’s Twitter profile and his bio says he’s located in London (note: as of 14th April it says Ireland, but it said London at the time this image was posted). There’s certainly not much in the way of immediate accessible information that we can research. It’s often tempting to give up at this point because there doesn’t appear to be any obvious way forward. This is often the case with more challenging images but there are other techniques we can apply to get as much data out of the image as possible. There is always more than you think. The original image was taken at about 15:28 UTC on 15th Jan 2023, but there isn’t much other information. By playing a short game of 20 Questions with the image, we force ourselves to extract as much information as we can about the image and its context. Armed with 20 different data points, we will have lots of new lines of research to follow up until we find the location, and if we still can’t find it we at least know that we have tried everything. We already have a couple of starting points, so let’s find our 20 data points by studying the photo as thoroughly as possible: The image was taken at 15:28 UTC on Jan 15th 2023. Conor (the photographer) has London in his Twitter location bio. It was daylight when the image was taken. The black car in the foreground is right hand drive. Conor is in a car park. The buildings resemble a retail park. Shop #1 has a red hoarding. Shop #1 sells furniture, bedding, appliances and audio. The name of shop #2 is not visible, but it has a red, orange, green and blue hoarding. Shop #3 is hard to see, but we can see a yellow hoarding. Shop #4 is called “Maxi” something and has a red and white sign. Some Christmas decorations are still visible. Shop #5 appears to have a red and white sign. The retail buildings are made of long rectangular blocks (metal or concrete?) The roof is not flat, it has a two-tier structure (this might help when it comes to aerial imagery later…) The roof is supported by external posts. Shadows from the support posts are cast onto the front of the building. This will help with orientation. The weather conditions are bright with some cloud. No evidence of rain. There’s a blue advert/sign with white text on the far left of the image. Some of these details are more important than others, but we won’t necessarily know exactly which ones until the end. Some details like the shop names are more likely to lead the location than the other details, but the small details will help with the fine tuning and verification at the end. What Does This Mean? Time to move to the next phase of gap analysis. We’ve established what we know (and it’s probably a lot more than we first thought) so next we have to figure out what all these data points tell us. It might not look like it yet, but we’ve already got enough data to get us to the objective quite quickly. Here’s what our findings tell us: Very few countries drive on the left side of the road. ( Source ) The right hand drive car means this is a left-hand drive country. Given that it was daylight at the location at 15:28 UTC on Jan 15th 2023 this means that the UK or Ireland is the correct place (the time and daylight means it can’t be Australia etc). Conor’s bio said London – but that doesn’t mean he took the picture there. The correct location will be a retail park with a car park in front of it. There will be a shop whose name ends in u, x or y. If English is the language then y is more likely at the end of the name than u or x. The shop sells furniture, bedding and electrical and audio equipment. There’s a second shop that might be easier to identify. It’s called “Maxi” – something and has a red and white sign style. The store fronts are facing roughly west. Conor is facing east. We can tell this because the shadows indicate the late afternoon sun is coming from over Conor’s shoulder, so west is behind him. This also means the long row of shops will be orientated roughly along a north-south line. When we find the approximate location, we should be able to verify that all the other details (roof style, posts, shop signs etc) are present. All our research so far means that if we can find a retail park in the UK or Ireland that has a “Maxi-?” store (Shop #4) alongside a furniture/bedding/electrical store that matches shop #1 and faces roughly west, we will find the correct location. If there is more than one matching location we can use the smaller details (posts, roof design, building materials etc) to eliminate the incorrect possibilities. What Do We Need To Know? To find the answer we need to choose our strongest line of enquiry. In this case we could either search for stores in the UK and Ireland that sell furniture/electrical goods and end in y, or we could choose to research stores called “Maxi”. You could really choose either as they are both likely to lead to a specific store. I decided to start with the “Maxi” store since it’s clearer what the name is than the large furniture store. This means that we need to know what the Maxi stores are (with matching name and logo) and where all their retail park stores are in the UK and Ireland. Then when we have found all these, we can eliminate all the retail parks where the shop layout, building, and orientation details do not match. How Do We Find Out? Let’s begin by searching for stores that are called “Maxi” in the UK. A Google search with a wildcard for the store name will help (since we don’t yet know if Maxi is a full or partial store name). A Google search to find stores with “Maxi” in their name. There are a few unhelpful results but the first result that mentions a Maxi- retailer is this one which relates to the Maxi Zoo chain of pet stores. The website tells us that Maxi Zoo has 29 stores in Ireland. A Google Image search for Maxi Zoo stores leads to this Shutterstock collection of Maxi Zoo storefronts . By comparing the images to the photo it looks like we’re on the right track. The original “Maxi” logo in the source image. Sample Maxi Zoo storefront images from Shutterstock. It seems like a good potential match. We’ve already established that the image is most likely in the UK or Ireland on the basis of the right-hand drive vehicle. A little extra research into Maxi Zoo shows that it has stores in Ireland, but none in the UK. This will prove to be helpful since it will mean we only have to focus on Ireland rather than the UK to find the correct location. Finding The Right Store Based on what we’ve found so far, we need to focus on trying to identify which one of the 29 Maxi Zoo stores in Ireland Conor was next to when he took the picture. As we look at each location we can quickly check if any of the other shops or architectural features we pulled from the original image are present. If they aren’t the location can be discounted. Google Maps makes this process quite straightforward. By focusing the map on Ireland and ticking the “Update results when map moves” option the stores are highlighted as the map moves around. All the Maxi Zoo store locations. Clicking on the link on the left hand side of the map brings up a picture of the store so each one can be quickly ruled in or out. 29 stores sounds like a lot to get through but with this method it only takes a few minutes. We can quickly see that this store does not match. In this case we can see straight away that the Maxi Zoo in Blanchardstown is not the one in the original picture. The storefront architecture doesn’t match. After a few more false starts, the Maxi Zoo in Waterford looks a little more promising. Notice the store sign hangs vertically down like in the original photograph. The shop next door (shop #3) has a yellow sign and on first glance the architecture seems to match. It might not be right, but it definitely can’t be ruled out. We need to take a closer look. The best way to do this is with Google Street View. There’s no direct coverage of the car park itself but the coverage from the road outside is good enough to make an assessment: This is where the time spent focusing on tiny details at the start pays off. If we’re right about the location, we should be able to see all of them present in the image above. Let’s check: Harvey Norman – the signs, logo and font match the original image. This is the bedding, appliances and audio store (shop #1). Next door is a shop with the rainbow coloured hoarding. It’s in the same place as in the original image. We can see that shop #2 is a Home Focus At Hickeys. Compare this image to Conor’s original: 3. Next door to Home Focus we can see that the shop with the yellow sign is a Halfords (Shop #3) . 4. The two tier roof between Harvey Norman and Home Focus is in the same place as in the original image. The metal block panels and external roof support architecture all match as well. 5. The only piece of information we are given at the start is that the image was taken at 15:28 UTC on 15th Jan 2023. The shadows in the original image suggested that the building should be aligned roughly North-South, with Conor looking east. The orientation looks good: To verify this is correct, we can use Suncalc to see if the shadows at the location match up with what Conor’s photo shows. Suncalc says that the shadows should be orientated like this: This matches perfectly with the shadows in the original image – perfect! So we can see that our structured methodology has served us well and made geolocating this image possible even with somewhat limited initial information. There is always more information in an image than first appears and we can use every last piece of it to find what we are looking for. If you enjoyed this post check out my other geolocation posts here . Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 3 thoughts on “Geolocation: At The Retail Park” Kenny Johnson 18th April 2023 at 1:03 pm Excellent walk-thru! Thank you. Loading... Reply Bal Krishna 24th April 2023 at 9:49 am Wonderful walkthrough. Very well explained. Loading... Reply Pingback: Geolocation: At The Retail Park - Whalers Blog Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2023/02/Fmhfr7YWIAALw9W-2048x1536.jpg","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-15.34.19.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-15.51.51.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-15.53.37-2048x631.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-16.51.29-2048x1411.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-17.03.27.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-17.08.29.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-17.50.08-2048x827.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-17.56.34.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-18.05.49.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-18.12.56.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-18.15.08.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-18.25.05.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-18.31.10.png","https://secure.gravatar.com/avatar/26c1c40d2c7caa6d5f2d87a2b34a2b71f6386891aa88a49e0976436fc85e6cdd?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/f75cfac195779401a22d854a1f4f8edf927204aa6000f5fa69acb2af86a9a7c4?s=50&d=mm&r=g"],"local_images":["blog_data/images/blog_2d7647e66e95_0.jpg","blog_data/images/blog_2d7647e66e95_1.bin","blog_data/images/blog_2d7647e66e95_2.bin","blog_data/images/blog_2d7647e66e95_3.bin","blog_data/images/blog_2d7647e66e95_4.bin","blog_data/images/blog_2d7647e66e95_5.bin","blog_data/images/blog_2d7647e66e95_6.bin","blog_data/images/blog_2d7647e66e95_7.bin","blog_data/images/blog_2d7647e66e95_8.bin","blog_data/images/blog_2d7647e66e95_9.bin","blog_data/images/blog_2d7647e66e95_10.bin","blog_data/images/blog_2d7647e66e95_11.bin","blog_data/images/blog_2d7647e66e95_12.bin","blog_data/images/blog_2d7647e66e95_13.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/osint/geolocation-tips-techniques/","title":"Geolocation Tips & Techniques","status":"ok","retrieved_at":"2026-08-29T16:33:20.467468+08:00","text":"Home OSINT Geolocation Tips & Techniques Geolocation Tips & Techniques 1 Comment / OSINT / By Nixintel In this video Technisette and I joined David Bombal to demonstrate some different geolocation techniques. We covered quite a few topics including: EXIF Data Using terrain features to find locations with Google Earth Removing unwanted parts of an image to do better reverse image searches Cropping and reverse searching images with Bing and Google Lens Extracting data from an image to research and pivot Plus a couple of speed runs to see how quickly we can identify a few locations. Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 1 thought on “Geolocation Tips & Techniques” IT Infrastructure Management 28th December 2022 at 7:30 am I am so glad you shared this information. It is very helpful for me. Loading... Reply Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://secure.gravatar.com/avatar/ff17f4496e7b61c8a2fbd928d94200f8c1fb6a02ee4a3074047cbb07f0b626c6?s=50&d=mm&r=g"],"local_images":[]}
+{"source":"nixintel","url":"https://nixintel.info/osint/obtaining-useful-information-from-a-kik-profile/","title":"Obtaining Useful Information From A Kik Profile","status":"ok","retrieved_at":"2026-08-29T16:34:31.98765+08:00","text":"Home OSINT Obtaining Useful Information From A Kik Profile Obtaining Useful Information From A Kik Profile 5 Comments / OSINT / By Nixintel 2026 update – this technique is no longer valid. It was written in 2019 and doesn’t reflect how Kik currently works. Last week I posted about how it was possible to obtain hi-res images and other information from Instagram and Twitter accounts by amending some of the URLs that the applications present by default. In a similar way it’s possible to obtain extra information about a Kik user profile by conducting queries with the correct URL. Kik is a popular mobile chat app that does not ask users to provide much personal information for verification, which is partly why it attracts so many unpleasant individuals . Nevertheless it does provide a little useful information about the user, including a hi-res profile pic. The URL we need to adjust is as follows: https://ws2.kik.com/user/<username_goes_here> If the user has a valid account, the URL will direct you to a small JSON file containing the user’s provided first name, last name, the time they last modified their profile image (in Unix time), and a link to a hi-res version of their profile picture. For a quick example, we can apply this to a Kik account which claims to be an “official” account for Zendaya (whether this is really the official account or not is beside the point). Her Kik username is “zendayakik”, so the URL to query is: https://ws2.kik.com/user/zendayakik We can now see the JSON file that gives the following information: First name Last name (which of course is left blank, maybe Zendaya was a bad example to choose!) Time the profile picture was last modified. This is in unix time, which you can convert to regular human-readable time with a tool like Unix Converter . If this is the original profile picture, it can give an indication when the account was created. URL to a hi-res version of the user’s profile picture. This is a much clearer image than the one available in the app by default. As always, there’s no substitute for verifying that the information Kik provides is actually true, but this technique can help to give you a head start for any Kik-based enquiries you need to make.   Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 5 thoughts on “Obtaining Useful Information From A Kik Profile” Rin 5th September 2023 at 11:18 pm It said that the page requested was not found… Anything u can do to help?? Loading... Reply Nixintel 16th October 2023 at 5:00 pm It is most likely the case that this technique no longer works. I haven’t tried it for a long time but this article is several years old now. Loading... Reply Yer 15th December 2023 at 7:36 pm It’s still works. Just make sure you don’t put the on either side of the username. And when you enter the help for the image it gives you remove all backslashes that they put next for the forward slashes. Also remove the “ and } at the end. Loading... Reply IamTheOneWhoFlops 17th June 2025 at 11:37 pm Nope, looks like they finally got wise to that url trick. normally it would have fed the users profile page, so things like join date and last seen i believe. But it just returns page not found now. I wonder if they just moved the endpoint and its still accessable or if they actually changed how the app works when requesting data from the server… Might have to decompile a fresh apk and see if anything interesting pops out… Loading... Reply Roger 30th June 2026 at 12:40 am Nope, it doesn’t work Loading... Reply Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2019/05/zendaya.jpg","https://secure.gravatar.com/avatar/507d27af4644a28ccf723c2e24448154ecb694507e42b53ff570650506a79180?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/58b400369457cf6a513e2363bb5698cebc89a2b6aa685f2c291570a446d23e9b?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/a8dbec59c215a7304ee0e9f72018ce377e1a7869da6ef4dc675dc1de3278de1e?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/c8ca64c08939b1ca71560ecfca2a43d33c20f0da616def26af1cf2418bb20e0c?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/e1978a38f6258a8fca4b5f38a6c4164fcbb62474f059815b7310f1ff42a679d9?s=50&d=mm&r=g"],"local_images":["blog_data/images/blog_13c0476833a5_0.jpg"]}
+{"source":"nixintel","url":"https://nixintel.info/osint/quiztime-how-to-clean-pictures-for-better-search-results/","title":"","status":"ok","retrieved_at":"2026-08-29T16:31:47.56668+08:00","text":"Home OSINT Quiztime: How To Clean Pictures For Better Search Results Quiztime: How To Clean Pictures For Better Search Results 5 Comments / OSINT / By Nixintel In last week’s Wednesday Quiz Tilman Wagner posted this photo and asked us several questions about it: 1) Who posted it and where? 2) What was the occasion? 3) Did Tilman participate, and if so, how? So where to start? We need to know the location before we can answer any of Tilman’s questions. There are a few clues in the image that might make a good starting point: the language on the screen is is in British English (organisation spelled with an ‘s’) and it suggests a networking event or meeting of some kind. There’s a WiFi sign but unfortunately the network name is too small to read, or else we could have had some fun with Wigle . No quick wins so far. An important rule in geolocation (and investigation generally) is that the more unique or distinctive a feature is, the more useful it is for finding the origin of a photo. By far the most distinctive feature is the unusual pyramid shaped building that it visible from the window. If we can locate this, we can work out where the photo was taken from. This is the most distinguishing feature in the photo and will be the key to geolocating it. Cropping the image and conducting a reverse image search seems to be the most obvious way to find the building, but there’s a big problem with that approach in this instance. When we look through a window with human eyes, we subconsciously ignore details like window frames and curtains to focus on what is outside. Unfortunately reverse image search engines aren’t smart enough to do this yet and they don’t distinguish between the foreground noise and the background detail that we are interested in. If you tried to solve this puzzle with this method you probably got a lot of matches that looked like this: Yandex search results find a lot of matches…but only for window frames. Reverse image search engines show their limitations here. They focus on the window frame and curtains but don’t focus on the building outside that we’re interested in. So what can we do? Removing Noise From The Image What we need is an easy way to remove the foreground clutter from the image so we can conduct a better reverse image search. Cleanup.pictures is very easy to use and makes it easy to remove unwanted features (like window frames) from images. Instead of leaving gaps, the software guesses what should appear in the image based on the rest of the image content and fills in the details. It will be perfect for what we need. First we upload our cropped image to the website. Cropped image ready to upload to Cleanup.pictures. Next we use the eraser tool to highlight the details we want to remove. Highlight the areas for removal. Here’s the final result – not too bad! The result with all the foreground noise removed. By using the smart eraser Cleanup.pictures removes the unwanted details and fills in the gaps based on the unaltered parts of the image. The result you can see above gives a clutter-free image that will give us a much better chance of success with a reverse image search. Here are the reverse image search results with the foreground clutter removed: Search results without the foreground noise. Much better! With the window frame removed, we get much better matches for the building in the background. We learn that it is the National Library of Latvia in Riga . By examining the area in Google Maps , we can see that there is only one building that Tilman’s photo could have been taken from: the Wellton Riverside Spa Hotel . The other buildings opposite the National Library do not have glass fronted balconies like the location in the original picture. The Wellton Riverside Spa Hotel in Riga. By way of confirmation, a quick look at the conference facilities on the hotel website brings up a room that matches the one in Tilman’s picture. The National Library is even visible out of the windows. The conference room at the Wellton Riverside Spa. So we know the location – how do we find out about the conference? Finding The Event Tilman posted this challenge on Wednesday 26th October and the photo was posted on the same day, so it’s reasonable to assume that the event happened in the few days leading up to the 26th. This means a good starting point is to found out what events were held at the Wellton Riverside Spa that week. It’s a simple piece of information but it’s surprisingly tricky to find out. The hotel website doesn’t list upcoming private events and search engines aren’t really too helpful. Eventbrite has a great search feature that allows you to search for events by location, but unfortunately it only works for current and future events, not past ones. It’s much easier to start with an event and find the location, but it seems more difficult the other way around. So what techniques might help us make the link between an event and a location? Geotagged social media posts are often helpful to tackle this problem. Both Facebook and Instagram have geographic search filters, so they are a good place to start. Instagram is my preferred resource for this because even though its search features are quite limited, it is still really good for searching photos by location. Simply entering “Wellton Riverside Spa” into the search bar brings up a few locations and hashtags of interest. All the matching hashtags and location tags for the Wellton Riverside Spa. One of the geotagged images leads to this image that was posted on 25th October. It refers to the hashtag #MILSummit2022 – so we will need to find out exactly what this summit was. The image is geotagged at the hotel location. A second image reveals some of the themes of the event. The same user posted another photo seemingly taken at the same event. Whatever the MIL summit is, the themes of media literacy, disinformation and verification are very common. We know Tilman works in this field, so this is probably a good indicator we are on the right track. We also learn from the second image that the full name of the conference is the “Baltic MIL summit”. This post links the MIL event at the hotel to the Ziniu Economic Forum, By researching the “Baltic MIL Summit” we quickly find that on Monday 24th October the Žinių Ekonomikos Forumas was hosting the MIL Summit at the hotel. The Facebook page for the event contains hundreds of photos of the participants taking part in the conference. Not only do these photos help to confirm the location matches the one in the original photo, but eventually we even find the exact same photo that Tilman used for the quiz. Bingo! A familiar photo on the ZEF Facebook page. So we now know that the image was posted by the Ziniu Economic Forum on their own Facebook page, and that the event at the hotel was the Baltic MIL media literacy summit held at the Wellton Riverside in Riga. To finish the quiz we just need to find out whether Tilman took part (if indeed he did). Linking Tilman To The Conference Clicking through all 230+ of the event photos was useful because not only did it help to identify the source of the original image, but despite all the attendees being very heavily photographed there was not a single photo with Tilman in it. (If you didn’t know what Tilman looked like already, a little Googling will bring up this bio with a picture.) Tilman’s picture and bio details. So there are two possibilities: either Tilman was there and he is very, very camera shy, or he was not there in person at all. On the balance of probabilties, it seems more likely that he did not physically attend the event, but we need to try and verify this first. Are there any other sources of information that might help? Looking through the images, it’s clear that there are strong links between the Deutsche Welle Akademie (where Tilman works) and the MIL event in Riga. We need to try and explore this connection a little bit more. A good place to start might be with the conference organisers, Ziniu Economic Forum. Most conferences have at least some publicity and a schedule of events. If we can find these, we might be able to learn a little bit more about the links between Deutsche Welle and the MIL Summit. The first article on the ZEF website refers to the summit and also includes a schedule for the event ( PDF download ). There are a lot of speakers – including several from DW Akademie – but Tilman is not one of them. Day Two of the summit, but no Tilman… So we know some of Tilman’s colleagues were speaking at the event, and even though we have not found any evidence that he attended in person, the schedule indicates that some of the sessions were streamed over the internet – so perhaps he took part by watching online? Perhaps he did, but it is hard to verify this directly. Can we do any better than just saying Tilman is linked to the conference because his colleagues were speaking there? We have already made a one-way link from the ZEF to the DW Akademie via the conference photos and speaker schedule, but what if we approach from the other direction and see what DW Akademie have to say in their own event publicity? By starting at the DW Akademie website we can see that they have two social media news feeds, one for Twitter and one for Facebook . By focusing on the dates of 24-25th October we can see that a live feed of the conference was available (so perhaps this was how Tilman took part?), but the other main publicity feature from DW is a talk by Lena Ritsche on their new game “Go Verify”. Here it is on Facebook: Facebook mention of Go Verify. And here on Twitter… Twitter reference to Go Verify. The Twitter post contains a direct link to the Go Verify game that is the main focus of Deutsche Welle’s publicity around the Baltic MIL Summit. By following the link and reading about Go Verify we find a familiar name at the bottom of the article: And there we have the closest link between Tilman and the conference so far. It seems unlikely that he was present, and we can’t say for sure whether he watched online or not – but we can say that the Go Verify game that he helped to develop was the subject of one of the talks. If you want to learn more about how to use Cleanup.pictures you can wach Technisette and I demonstrate it on David Bombal’s webcast here . Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 5 thoughts on “Quiztime: How To Clean Pictures For Better Search Results” Pingback: Quiztime: How To Clean Pictures For Better Search Results – We are OSINTCurio.us Robert Jan Bolk 15th January 2023 at 10:42 pm LS Het hotel waar hierover gesproken wordt, wat tegenover de bibliotheek zou moeten staan, staat er niet. Gelukkig is het maar een spelletje, groet.. Loading... Nixintel 16th January 2023 at 11:39 am The hotel is directly opposite the library on the other side of the Daugava River? Loading... Sarmad Nadeem 7th February 2023 at 9:54 pm I use Imgcleaner.com to remove unwanted objects from the image. Its good. Loading... PicPicAi 29th June 2025 at 2:08 pm Great OSINT quiz on cleaning pictures! Using PicPicAi image editing tools can enhance photo clarity, making search results more accurate. A fun, practical guide for better visual investigations! Loading... Comments are closed.","image_urls":["https://nixintel.info/wp-content/uploads/2022/11/Screenshot-2022-11-01-205952.png","https://nixintel.info/wp-content/uploads/2022/11/image-1.png","https://nixintel.info/wp-content/uploads/2022/11/image-10.png","https://nixintel.info/wp-content/uploads/2022/11/image-11-2048x1196.png","https://nixintel.info/wp-content/uploads/2022/11/image-12.png","https://nixintel.info/wp-content/uploads/2022/11/image-13-2048x1249.png","https://nixintel.info/wp-content/uploads/2022/11/image-14.png","https://nixintel.info/wp-content/uploads/2022/11/image-15.png","https://nixintel.info/wp-content/uploads/2022/11/image-17.png","https://nixintel.info/wp-content/uploads/2022/11/image-18.png","https://nixintel.info/wp-content/uploads/2022/11/image-2.png","https://nixintel.info/wp-content/uploads/2022/11/image-3.png","https://nixintel.info/wp-content/uploads/2022/11/image-4.png","https://nixintel.info/wp-content/uploads/2022/11/image-5.png","https://nixintel.info/wp-content/uploads/2022/11/image-6.png","https://nixintel.info/wp-content/uploads/2022/11/image-7.png","https://nixintel.info/wp-content/uploads/2022/11/image-8.png","https://nixintel.info/wp-content/uploads/2022/11/image-9.png","https://nixintel.info/wp-content/uploads/2022/11/image.png","https://secure.gravatar.com/avatar/1ab89dbac7ea73f1de9b6bfd4b8cecc178b09b036185ef5e664b357508e477b6?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/1f375d63a86b79935db749923d68c3f9ac3173321ac835939223d04e1edb0afe?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/277607c0d8e8d0c09232c77c96a154501cfe6465404a1e87eb60b2e885a68eb7?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/a8dbec59c215a7304ee0e9f72018ce377e1a7869da6ef4dc675dc1de3278de1e?s=50&d=mm&r=g"],"local_images":["blog_data/images/blog_ffdea357f0f4_0.bin","blog_data/images/blog_ffdea357f0f4_1.bin","blog_data/images/blog_ffdea357f0f4_2.bin","blog_data/images/blog_ffdea357f0f4_3.bin","blog_data/images/blog_ffdea357f0f4_4.bin","blog_data/images/blog_ffdea357f0f4_5.bin","blog_data/images/blog_ffdea357f0f4_6.bin","blog_data/images/blog_ffdea357f0f4_7.bin","blog_data/images/blog_ffdea357f0f4_8.bin","blog_data/images/blog_ffdea357f0f4_9.bin","blog_data/images/blog_ffdea357f0f4_10.bin","blog_data/images/blog_ffdea357f0f4_11.bin","blog_data/images/blog_ffdea357f0f4_12.bin","blog_data/images/blog_ffdea357f0f4_13.bin","blog_data/images/blog_ffdea357f0f4_14.bin","blog_data/images/blog_ffdea357f0f4_15.bin","blog_data/images/blog_ffdea357f0f4_16.bin","blog_data/images/blog_ffdea357f0f4_17.bin","blog_data/images/blog_ffdea357f0f4_18.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/osint/telegram-for-cyber-investigators/","title":"Telegram For Cyber Investigators","status":"ok","retrieved_at":"2026-08-29T16:33:47.871816+08:00","text":"Home OSINT Telegram For Cyber Investigators Telegram For Cyber Investigators 2 Comments / OSINT / By Nixintel Telegram is one of the most important platforms for OSINT investigators. I joined the Needlestack podcast to discuss how Telegram works and shared some practical OSINT advice along the way. Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 2 thoughts on “Telegram For Cyber Investigators” Pingback: Telegram For Cyber Investigators - Whalers Blog Pingback: Telegram For Cyber Investigators - Whalers Blog Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":[],"local_images":[]}
+{"source":"nixintel","url":"https://nixintel.info/osint/using-gap-analysis-to-keep-osint-investigations-on-track/","title":"Using Gap Analysis To Keep OSINT Investigations On Track","status":"ok","retrieved_at":"2026-08-29T16:34:54.432749+08:00","text":"Home OSINT Using Gap Analysis To Keep OSINT Investigations On Track Using Gap Analysis To Keep OSINT Investigations On Track 6 Comments / OSINT / By Nixintel With any kind of OSINT investigation it’s easy to gather huge amounts of data in a very short amount of time, but what do you do with it all? There are thousands of tools you can use to scrape information from all kinds of sources, but how do you decide to prioritise it? What information is relevant, and what is not? How do you keep your research on track and avoid wasting time on pointless searches that take you nowhere? This guy used gap analysis, I guarantee it. Consider the Mueller Investigation into President Trump – it executed over 500 search warrants, issued over 2,800 subpoenas, made 230 requests for telecoms data, and interviewed about 500 witnesses, all to produce a 448 page report. The Skripal Poisoning investigation took over 900 witness statements, seized 2300 pieces of evidence, and reviewed 4000 hours of CCTV footage. All of these investigations were very different in purpose but they all had to gather and evaluate vast quantities of information in order to achieve their aims, but how did they avoid becoming overwhelmed? Of course it helps that these enquiries are well resourced, but the important investigative decisions about where to go next are still made by just a tiny number of senior investigators. How do they keep things on track and avoid drowning in data? How do they decide what is important and what is irrelevant? What determines where they will go next? Gap analysis helps pull important information out of 4000 hours of CCTV footage… If you’re just starting out with OSINT investigation, or even if you have lots of experience, you’ll notice how easy it is to build up a lot of data and go off on a lot of tangents very easily. Most OSINT investigations are not on the same scale as the Mueller Report or the Skripal Poisonings of course, but the same investigative decision-making method used by experienced investigators in major cases can also be applied to smaller scale investigations to help sort through the data, focus on what’s important, and then decide what to do next. The method is known as gap analysis. Gap Analysis Gap Analysis is a simple but very effective way to keep an investigation focused on what is important and avoid unnecessary and confusing tangents. The name comes from the fact that it is used to evaluate all the known information and then identify gaps where further enquiries are needed. It is not specific to OSINT, but it can be easily applied to online investigations. It uses four simple questions to look at the gathered information, evaluate it, and then decided what to focus on next. The four questions are: 1) What do I know? 2) What does this mean? 3) So what do I need to know? 4) How do I find out? Instead of rushing ahead and leaping from one tool to the next in hope of a quick win, gap analysis ensures that the approach is more methodical and accurate. With OSINT it is possible to be fast or accurate, but it is not often possible to do both! Even if you are completely stuck at the start of an OSINT task, or maybe just overwhelmed with information, applying these questions to the data in front of you will help determine where to start. Also notice that thinking about what tools or resources to use are only addressed at question four – “How Do I Find Out?” While a knowledge of the available OSINT tools is essential, they will never get you very far if they are not used in conjunction with a good investigative method. The method will determine what tools to use. A Quiztime Case Study – Using Gap Analysis To Find Tilman Wagner On 22nd May the Quiztime challenge was quite a hard one to begin with – but it was possible to solve by using gap analysis to identify what information was available, and what had to be done next in order to solve the challenge.   Gap analysis helps us to move quickly from this…   . ..to this. Tilman posted the image below and asked two questions: 1) Was there another flight between his and the Easyjet one? and 2 ) Where was the Easyjet plane flying to? Where is the Easyjet flight headed to? He also told us that the image was taken on 12th May 2019, and that this was his outbound flight. Tilman often posts from Tirana where he is based but he was clear this was an outbound flight and he was not heading to Tirana. The first thing to do was to identify Tilman’s location and work from there.   There was no way to solve this instantly, but being systematic and using gap analysis it was possible to identify some ways to find the location and start heading in the right direction. Here are the four key questions I used to get started: 1) What do I know? i) This is on the 12 th May 2019. ii) There is an Easyjet plane on the runway ahead of Tilman’s plane. iii) There is a sign in the picture that says “BB 25” 2) What does this mean? i) Tilman’s plane was also at an airport that Easyjet fly from. ii) The sign may tell us something about the location. 3) So what do I need to know? i) Which aiports do Easyjet fly from. ii) What does the BB25 sign next to the runway mean, if anything? 4) How do I find out? i) Get a list of locations that Easyjet fly from. ii) Find a guide that explains airport runway signage. So already gap analysis gave me something to work with. Finding out where Easyjet fly from is straightforward – their website and this Wiki page give all the destinations, but they fly from 136 different airports. I could have looked at every single aiport on Google Earth and compared it to the photo, but that would take a long time and I would quickly drown in information. He’s on this map somewhere. We have him cornered… The runway sign was more promising. A quick Google tells us that “BB 25” means that this sign denotes taxiway BB for runway 25 – this is a vital piece of information that will help solve the puzzle much more quickly. Runway Names and Numbers Every single runway has a number, or two specific numbers to be exact. A runway takes its number from a the compass heading it is directed towards. For example a runway that points due west (bearing 270 degrees) would be called runway 27. However planes sometimes use different ends of the runway to take off from depending on wind direction, so the runway is given a second number for when aircraft use the opposite end. Because runways are straight lines, the opposite end of a runway will have a compass heading that is 180 degrees opposite to the other end. So if one end of a runway points towards 270 degrees, the other must point 90 degrees. This means the runway name will be 090/270, or 09/27 for short. If you’re confused there’s a really simple guide here . All you need to known about airport taxiway signs. So now I knew the runway in the photo is runway 25. This means the Easyjet plane is heading 250 degrees for takeoff. With a little bit of geometry it was possible to find out a little more that will quickly help to locate Tilman. If one end of the runway is facing 250 degrees, the other end must be facing 70 degrees (because 250- 180 = 70), so the runway name we are looking for will be 07/25. 07/25 – Bingo! So perhaps now would be a good time to hit Google Earth and just check out all the Easyjet aiport locations that have a runway named 07/25? It would have been an option to do this, but it was possible to narrow the parameters even further with just a little more geometry. If the Easyjet plane is facing 250 degrees (roughly WSW), then Tilman must have been looking roughly northwest when he took the photo. No airport buildings of any kind are visible on the image, so the main airport infrastructure must be on the south side of the runway, not the north side. Now the parameters for finding the correct airport were really small: i) It is used by Easyjet ii) It has a runway 07/25 iii) The main terminal buildings are likely on the south side of the runway. A very quick trawl through the list of 136 Easyjet destinations reveals that only a tiny number (I think it was less than 15 but can’t quite recall) had a runway 07/25. I checked these out on Google Maps, and even fewer had the main airport buildings on the south side of the runway. One of the very few that met all three search criteria was Rome Leonardo Da Vinci Airport . I then moved to Google Earth to try and verify if this could be correct: A view down Runway 25 from Google Earth. Note the red/white tower and other buildings on the right that match those in Tilman’s photo.   Just to the left is the BB25 sign. It isn’t clear in this image, but it can be clarified with the airport plan published by Jeppesen. By comparing the original photo to the Google Earth image it was clear the red and white towers in the background were the same on both photos. Tilman had been waiting to take off from runway 25 at Rome Leonardo Da Vinci Aiport. Two planes waiting in the queue at the end of Runway 25. This last Google Earth image showed two planes waiting to take off at the end of the runway. This suggested that it was at least possible there was another plane between Tilman’s aircraft and the Easyjet one we were trying to find. So having established Tilman was in Rome, it was time to decide what to do next by applying some more gap analysis. 1) What do I know? i) The image was taken on 12th May. ii) The image was taken on runway 25 at Rome Leonardo da Vinci Aiport (FCO). 2) What does this mean? i) Tilman’s plane and the Easyjet flight will have departed close together on 12th May. To identify Tilman’s flight we will also need to identify the Easyjet flight. 3) What do I need to know? i) What time planes took off from FCO on 12th May. ii) Where do Easyjet fly to from Rome? 4) How do I find out? i) Get a list of departure times for FCO on 12th May 2019. ii) Find out where Easyjet fly to from FCO. Now you might assume that it would be possible just to head over to Flightradar and view historic departure information and solve the puzzle just like that, but it wasn’t. Tilman posted the challenge ten days after the flight, but Flightradar only holds records for the last seven days unless you have a premium account. There are other aircraft datasets available but most are intended for commercial use and cost a lot of money to access. So where to get the data I needed? To get the data I used Airportia and found the page with departure records for FCO here . Now there seemed to be a problem again because Airportia only allows you to see the last seven days worth of information, but with a little URL manipulation it was possible to access the data I needed. The standard URL format Aiportia uses is: https://www.airportia.com/italy/leonardo-da-vinci/departures/YYYYMMDD/0000/2359/ So by amending the URL to my target date as follows, it was possible to get the data for the date in question, even though there is no direct option to do this from the website: https://www.airportia.com/italy/leonardo-da-vinci/departures/20190512/0000/2359/   There was a lot of data to go through, especially as there is a big difference between planned departure times and actual departure times. Airportia doesn’t allow sorting of flights by actual departure time, so a little patience was required. I got slightly disheartened at this point because I counted a total of 21 different Easyjet departures to thirteen different destinations: Geneva, Nice, Paris, Gatwick, Lyon, Berlin TXL, Paris Orly, Amsterdam, Nantes, Basel, Toulouse, Bristol and Luton.It would be hard to find the exact flight without guessing. I guessed that perhaps Tilman would have flown to Dusseldorf, based purely on the fact that he goes to Germany a lot, so I looked for Easyjet flights near to Dusseldorf flights but I’m happy to say I was wrong. Logic beats guessing every time. So how to narrow down my the list of 21 possible flights to one? Time for more gap analysis: 1) What do I know? i) There were 21 Easyjet flights from Rome on the 12th May. ii) The flights go to 13 different locations. iii) The flight in the picture is one of those. iv) The flight pictured is in daylight. 2) What does this mean? i) The flight must have been before sunset, as it is still light and there are no runway lights visible. ii) Any flights that took place after sunset can be eliminated. 3) What do I need to know? i) What time was sunset on 12th May? 4) How do I find out? i) Use Suncalc! Suncalc told me that sunset had been at 20:20 on the 12th May. This meant that any flight after this time could not have been in daylight and so could be eliminated. It was possible to eliminate 7 Easyjet flights this way, leaving me with just 14 possibilities. More Information Needed I was running out of ways to identify the specific Easyjet flight. It was not possible to accurately read the tail number of the aircraft (that would have been too easy) and I needed more information. Tilman helpfully provided some :   Tilman said this image was taken shortly after takeoff after his aircraft turned left approximately 90 degrees. The runway geometry meant that he had taken off on a heading of 250 degrees so a left turn of approximately 90 degrees meant he was heading roughly south. A quick Google Maps search helped confirm the location in the photo:   Even if you hadn’t figured it out from the runway angle, Tilman’s second picture shows the town of Fiumicino. This also means he is heading south. With some new information, it was time to apply some more gap analysis. 1) What do I know? i) Tilman’s plane took off from Runway 25, turned left, and headed south. ii) An Easyjet flight took off ahead of him, destination unknown. 2) What does this mean? i) That the departure timetable will show a flight heading south near to the same time an Easyjet flight took off. ii) That where a flight to the south and an Easyjet flight occur together, this is probably the right answer. iii) That if there is a flight in between an Easyjet flight and a southbound flight, it will likely contain the answer to Tilman’s second question. 3) What do I need to know? i) Which flights on 12th May were going to a destination south of FCO? 4) How do I find out? i) Revisit the flight departure data. ii) Check the destinations on a map – which are to the south? So on reviewing the flight data, the only flights heading (roughly) due south out of FCO on 12th May were to Tunis, Palermo, and Catania: He’s down there somewhere. The only time when a flight to one of these destinations took off shortly after an Easyjet flight was at 17:36 when a plane went to Palermo, just after Easyjet flew to Nice at 17:32. The relevant part of the timetable. Note the big difference between planned departures and actual departures. It is the actual departure time that we need to know to solve this puzzle. This also means that there was another flight inbetween, to Pisa at 17:33. There is no other combination of Easyjet flight followed closely by a southern flight towards Palermo, so this had to be the correct answer. Fortunately Tilman confirmed that it was! Without a sound logical method like gap analysis it would not have been possible to solve this challenge, but it allowed me to make sense of the data available and also identify the next pieces of information needed to find the answer. The average terrorism or murder investigation is a lot more complicated of course, but the only real difference is in the amount of data that has to be analysed and evaluated, not the decision making process itself.   Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 6 thoughts on “Using Gap Analysis To Keep OSINT Investigations On Track” Mira 16th October 2019 at 6:32 pm Hi, First of all, let me thank you for your blog posts which are such an amazing tool to learn OSINT. I have a question about this one: Why did you discard the flights to Catania? There was one that departured at 13:28 and was preceded by an Easyjet flight to London Gatwick at 13:26. Another one departured at 15:12 and was preceded by an Easyjet flight to Paris-Orly at 15:10. Do you think the time between the two flights was too short? According to this website, 2 minutes is a minimum to avoid a wake turbulence hazard https://www.skybrary.aero/index.php/Mitigation_of_Wake_Turbulence_Hazard Loading... Reply Nixintel 16th October 2019 at 7:39 pm Hi Mira, thanks for taking the time to comment. The main reason I discounted the Catania flights at those times is because in the original picture it looked like it was getting too dark. Although it was still daytime when the picture was taken, the sky on the left of the image looks like the sun is already quite low, so I assumed it was getting close to evening time. I think that the sun is too low in the sky for 13:28 or 15:10 at that time of year. Re-reading the article I realise I was not explicit about this when I wrote so it is not very clear what my rationale was, but that was pretty much it! Loading... Reply Mira 18th October 2019 at 11:21 am Thank you for the explanation. I was also thinking at the beginning that the photo was probably taken in the evening (or early in the morning), but I forgot about it along the way. Loading... Reply Pingback: Dressed NOT for Success – We are OSINTCurio.us Pingback: Cyber Intelligence – jagadee.online Pingback: Geolocation: At The Retail Park - Whalers Blog Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2019/05/103301966_cctv_1_petrov_boshirov_met-.jpg","https://nixintel.info/wp-content/uploads/2019/05/AirportSigns.jpg","https://nixintel.info/wp-content/uploads/2019/05/Screenshot-2019-05-29-at-21.44.39-1024x926.png","https://nixintel.info/wp-content/uploads/2019/05/Screenshot-2019-05-29-at-21.53.34-985x1024.png","https://nixintel.info/wp-content/uploads/2019/05/Screenshot-2019-05-29-at-22.46.05-897x1024.png","https://nixintel.info/wp-content/uploads/2019/05/Screenshot-2019-05-29-at-22.58.52.png","https://nixintel.info/wp-content/uploads/2019/05/Screenshot-2019-05-29-at-23.04.44-1024x729.png","https://nixintel.info/wp-content/uploads/2019/05/Screenshot-2019-05-30-at-16.56.03.png","https://nixintel.info/wp-content/uploads/2019/05/Screenshot-2019-05-30-at-17.06.14-300x287.png","https://nixintel.info/wp-content/uploads/2019/05/Screenshot-2019-05-30-at-17.12.15-300x106.png","https://nixintel.info/wp-content/uploads/2019/05/alitalia.jpg","https://nixintel.info/wp-content/uploads/2019/05/easyject_image.jpg-large-1024x768.jpeg","https://nixintel.info/wp-content/uploads/2019/05/image2.jpg-large-1024x768.jpeg","https://nixintel.info/wp-content/uploads/2019/05/mueller.jpg","https://nixintel.info/wp-content/uploads/2019/05/panoramio-42434834-1024x768.jpg","https://secure.gravatar.com/avatar/65e9fe80f2064d59c07e759bd6ad06a81d72406abfe8550d37627452e2ca2516?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/a8dbec59c215a7304ee0e9f72018ce377e1a7869da6ef4dc675dc1de3278de1e?s=50&d=mm&r=g"],"local_images":["blog_data/images/blog_1a292eea0d47_0.jpg","blog_data/images/blog_1a292eea0d47_1.jpg","blog_data/images/blog_1a292eea0d47_2.bin","blog_data/images/blog_1a292eea0d47_3.bin","blog_data/images/blog_1a292eea0d47_4.bin","blog_data/images/blog_1a292eea0d47_5.bin","blog_data/images/blog_1a292eea0d47_6.bin","blog_data/images/blog_1a292eea0d47_7.bin","blog_data/images/blog_1a292eea0d47_8.bin","blog_data/images/blog_1a292eea0d47_9.bin","blog_data/images/blog_1a292eea0d47_10.jpg","blog_data/images/blog_1a292eea0d47_11.jpg","blog_data/images/blog_1a292eea0d47_12.jpg","blog_data/images/blog_1a292eea0d47_13.jpg","blog_data/images/blog_1a292eea0d47_14.jpg"]}
+{"source":"nixintel","url":"https://nixintel.info/osint/using-ssl-certificates-to-find-threat-actor-infrastructure/","title":"Using SSL Certificates To Find Threat Actor Infrastructure","status":"ok","retrieved_at":"2026-08-29T16:33:44.943794+08:00","text":"Home OSINT Using SSL Certificates To Find Threat Actor Infrastructure Using SSL Certificates To Find Threat Actor Infrastructure 1 Comment / OSINT / By Nixintel At last month’s SANS OSINT Summit I gave a talk the usefulness of SSL certificates for open source intelligence researchers. The talk looks at three recent examples of how information from certificate transparency logs can be used to discover, attribute, and unmask threat actor infrastructure. The video of the talk has now been published and you can watch it here. The tools and resources I refer to in the talk can all be found here . Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 1 thought on “Using SSL Certificates To Find Threat Actor Infrastructure” Pingback: Using SSL Certificates To Find Threat Actor Infrastructure - Whalers Blog Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":[],"local_images":[]}
+{"source":"nixintel","url":"https://nixintel.info/osint/website-osint-whats-the-link-between-antifa-com-and-russia/","title":"Website OSINT: What’s The Link Between Antifa.com and Russia?","status":"ok","retrieved_at":"2026-08-29T16:34:34.490881+08:00","text":"Home OSINT Website OSINT: What’s The Link Between Antifa.com and Russia? Website OSINT: What’s The Link Between Antifa.com and Russia? 7 Comments / OSINT / By Nixintel The term “OSINT” sometimes gets thrown around a little too loosely. The “open source” part of OSINT is straightfoward enough: there’s a world of information out there and with enough digging and practice you can find almost anything you could ever think of – but by itself this is not OSINT. The “intelligence” part of OSINT is often neglected, sometimes with quite serious consequences . Getting your hands on the data you want is usually easy enough, but this raw information has to be analysed and turned into a coherent narrative, a process that is often fraught with difficulty and uncertainty. A lot of uncertainty can be removed if there is a clear plan in place at the start. We have to remember that OSINT is never done simply for its own benefit. It is always part of a wider objective like a journalistic investigation, or a missing person case, or a military operation, and so on. The nature of the objective that you’re doing OSINT for will ultimately determine the scope and shape of the research that you undertake, and the findings that you provide to your client or boss. Collecting raw information from the internet is easy enough, but turning it into an organised, verified, and useful report takes a little more work. The Intelligence Cycle The Reddit crowdsourced investigation version of this model only features ‘Collect’ and ‘Disseminate’… To ensure consistency and thoroughness in OSINT work most organisations adopt a version of the Intelligence Cycle like the one pictured above. There are several variations of this model, but they are all very similar. They all assume an initial plan or goal, followed by a collection phase, some processing and analysis, and finally dissemination of the information to the intended recipient. The processing and analysis phase is the most important one because this is where the raw collected data is critically evaluated, theories are tested, and correct information is separated from the false or ambiguous (with varying degrees of success). This means that “here’s a bunch of stuff I found on the internet” is not OSINT. It might be open source, but it isn’t useful intelligence until it’s been tested, verified, and analysed. Does the information you found provide useful answers to the question you set at the start? Have you verified it? How have you dealt with the conflicting information you collected? How much weight have you given to sources of information that are of uncertain reliability? Have you provided you client with OSINT or BULLSHINT? And so on. Is Antifa.com Controlled By Russians? So what has all this got to do with Antifa? I actively try to avoid politics on Twitter, but sometimes it’s inescapable despite my best efforts. Recently my interest was piqued by a claim that the domain antifa.com was redirecting visitors to Joe Biden’s presidential campaign site, and that furthermore, the Antifa website was registered by shady Russians. Was this the spectre of electoral interference about to make a reappearance? Yeah…but no. The central claim about a Russian link seemed to revolve around the WHOIS history of the Antifa.com domain – I’m always initially sceptical about claims made solely on the basis of WHOIS since it’s such an ambiguous source of information, but I decided to dig into the domain history a little more to see what it was possible to find out. What follows is a brief step-by-step guide to using the Intelligence Cycle to plan a little OSINT research and analysis to see what we can find out. Planning – What Do I Actually Want To Find Out? This is quite a simple query. I could ask “ Was the redirect from Antifa.com to Joe Biden’s website a Russian plot? ” It’s a sensationalist question, but it’s also a closed question (you could only answer “yes” or “no”). It’s almost a leading question too, in that your political stance might cause you to come to a conclusion based simply on how the the question is asked, and not necessarily based on any of the research. Closed and leading questions are not good investigative questions. Open questions are much better and less likely to feed our biases. A better question to ask might be “ What is the nature of the relationship between Antifa.com and it’s Russian registrar, if any? ” Collection – Find The Materal That I Need The collection part of the intelligence cycle is where we can gather all the information that we need to try and answer the question we set at the start. In this case I want to know about the history of the antifa.com domain, who owned it, what content it has displayed over time, and what we can find out about any redirects that are in place. To do this I’m going to collect information about the server (so I can catch any redirect information that might be present), the WHOIS history, the certificate history, and any preserved content from the Wayback Machine that might show me what content the site has displayed over time. 1. Server Information Curl is still my favourite tool for quickly grabbing information about a server. To grab information about the Antifa.com server, I entered the following command: $ curl -I http://antifa.com The -I flag ensures that I get server header information back. In this case I get the following result: HTTP/1.1 302 Found Server: nginx Date: xxx Connection: keep-alive Location: https://itsgoingdown.org/ X-Served-By: Namecheap URL Forward This is interesting because there’s still a 302 redirect in place, but now it points to a different URL. We can also see that Namecheap’s URL Forwarding service is in place, so I’ll grab some information about how that works to add to my analysis later: 2. WHOIS History I also want to know as much as I can about the WHOIS history. After all, this is the source of the suspicion that there might be some Russian links to the site. There are several tools to do this. RiskIQ and Whoisology both have WHOIS data going back to 2012/2013. However we know that the domain was registered at least as far back as 2002 (and as it turns out, even before that) so we need to go further back if possible. It’s possible to pay for a service like this with Domain Tools , but a full historic WHOIS report is a bit too pricey for a single blog post. Fortunately there is a little hack that takes advantage of the fact that WHOIS records are themselves often archived by the Wayback Machine, so we can use this technique to find WHOIS records that go back as far as 2009 : It’s not ideal but that’s as far back as we can go without splashing the cash on a paid-for WHOIS record. The information held by RiskIQ helpfully lists more recent registration renewal or change dates: 3. Certificate History A domain’s certificate history can offer several insights into its structure and setup, including ownership and hosting changes. Crt.sh offers a nice clear overview of a site’s certificate history, and there’s always Censys if you need to go into more depth. Here’s the very short certificate history for Antifa.com: 4. Wayback Machine Fortunately the subject domain has been archived many times over the years. The oldest capture is as far back as January 1999 and the most recent was 17th August 2020. It’s no coincidence that so many snapshots have been made since the domain begain to be heavily publicised in the last week: With this information we’ll be able to look at the historical content of the website to see what it was displaying at different time periods. Processing & Analysis Because this is just a short example for a blog post, I’m not going to spend much time doing any processing of the information I’ve collected. Ordinarily it’s usually helpful to turn raw data into spreadsheets, graphs, and relational diagrams to make analysis easier, especially with more complex tasks. Instead I’m going to move straight on to analysing the raw information that I collected. My aim is going to be to try and construct a timeline from the WHOIS, Certificate, and Wayback Machine history to try and see how the domain has changed over time and what that might mean for the original question about the domain and the relationship with its Russian registrar. Before doing that I want to look at the server header I grabbed at the start: HTTP/1.1 302 Found Server: nginx Date: xxx Connection: keep-alive Location: https://itsgoingdown.org/ X-Served-By: Namecheap URL Forward The HTTP 302 code tells us that all requests to visit antifa.com are all now directed to another site, itsgoingdown.org. This site does in fact appear to be a left wing political website, which is what we might expect. This redirect is enabled through Namecheap’s URL forwarding service, so by looking up Namecheap’s documentation about how this process works , we can infer that the person(s) managing the Antifa.com domain does so via Namecheap’s control panel and that the domain is therefore managed through Namecheap. This shouldn’t be surprising because this is exactly what the current WHOIS records tell us: Domain name: antifa.com Registry Domain ID: 85915752_DOMAIN_COM-VRSN Registrar WHOIS Server: whois.namecheap.com Registrar URL: http://www.namecheap.com Updated Date: 2019-10-23T14:38:04.00Z Creation Date: 2002-04-24T12:35:11.00Z Registrar Registration Expiration Date: 2021-04-24T12:35:10.00Z Registrar: NAMECHEAP INC Registrar IANA ID: 1068 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.6613102107 Reseller: NAMECHEAP INC Ever since 23rd October 2019, the subject domain has been registered with Namecheap. So where’s the Russian registrar link that we were interested in? If we go back through the historic WHOIS data we can see that between 2009 (the oldest WHOIS data we can access) and the switch to Namecheap on 23rd October 2019, the domain was registered to an address in St Petersburg, Russia: Registrar Abuse Contact Phone: +7.8129140281 Domain Status: clientUpdateProhibited Domain Status: clientTransferProhibited Domain Status: clientDeleteProhibited Registry Registrant ID: Registrant Name: Whois privacy services provided by DomainProtect LLC Registrant Organization: Whois privacy services, provided by DomainProtect LLC Registrant Street: c/o Office-Mail processing center Sadovaya, 53 Registrant City: Saint Petersburg Registrant State/Province: Saint Petersburg Registrant Postal Code: 190068 Registrant Country: RU Registrant Phone: +1.8662452838 Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant Email: [email protected] I think this was the point at which Yahoo! News and several others decided to end their research and go straight to publishing. This was a little premature though: Hmm. That’s a very broad definition of the word “linked”. This is what happens when rushing from Collection to Dissemination and skipping over the Analysis part of the Intelligence Cycle. Russia is a country – what’s the link to the registrant? When did they control the domain? Can we know what they did with it? Do they still own it? All these questions need to be resolved before we draw a conclusion. Better to be slow and right than fast and wrong. So what exactly is the link to Russia in the WHOIS data? The registrant name and e-mail are hidden in the WHOIS records, but the street address is not. By searching for the address “ c/o Office-Mail processing center Sadovaya, 53 ” we can see that it’s linked to hundreds and hundreds of other WHOIS records for other domains. Why might this be? Fortunately the Wayback Machine records we saved during the collection phase will help. We can see what Antifa.com looked like during the time it was registered by a mysterious Russian organisation. Brace yourselves for the big reveal… For the entire time that the domain was owned by the shadowy Russian group, all they did was offer it up for sale . Although we don’t have WHOIS records older than 2009, we can see that even in 2008 the domain was parked and up for sale. In fact it was for sale for many years up until it switched to a new owner on 23rd October 2019. Even after the change of ownership, no significant content changes were made until 14th April 2020. We can see this in the certificate history from crt.sh . The antifa.com domain never had an SSL certificate before 14th April 2020. This date is significant because it’s also the same date that the Antifa Website Twitter account was created : (Of note the URL in the Antifa Website Twitter bio also redirects to itsgoingdown.org. ) The Antifa.com YouTube channel was also created at around this time, on 18th April 2020: Sure enough, the first Wayback Machine capture after 14th April 2020 reflects this change. The “For Sale” sign is gone and has been replaced with new content: The #JusticeForGeorgeFloyd hashtag links directly to the Antifa Website Twitter. Remember that at this point the previous Russian registrar has not been linked to the site for over eight months. This was still the case on 12th August when the domain was set up to redirect to Joe Biden’s website: Can we be confident of a link between Russia, Antifa, and Biden based on what we’ve found in our limited research? I’m not sure we can. Product Dissemination Because this is just a short blog exercise, there’s no one to disseminate the information to beyond you, the reader (well done if you’re still reading this far on). It’s a good point at which to review our original question and see if the collection and analysis we’ve done actually answers the original question – what is the nature of the relationship between Antifa.com and its Russian registrar, if any ? This has been quite a brief exercise and there are certainly an awful lot of other avenues of research we could have gone down. So what can we conclude? The world of OSINT is rarely black and white and there will always be some areas of uncertainty. There’s nothing wrong with a little uncertainty, provided that this is reflected in your findings: your conclusions always have to be supported by your research and not embellished. Nah. Based on this research we can say that the domain was previously registered by a Russian-based organisation and has been since at least 2009, possibly even before that. We can also say that during the Russian registrant’s period of ownership the evidence suggests that the domain was only parked and offered for resale. There is no evidence to suggest any content was hosted on the domain during their ownership period, or that any redirects were in place. The registration of the domain changed in October 2019 and there is no clear connection to the Russian registrant after that point. The current owner of the domain uses Namecheap as a registrar but from the information collected it is not possible to say who they are. The current owner has used the domain for a distinctly different purpose than the previous Russia-linked owner. At the time the domain was configured to redirect traffic to Joe Biden’s website almost 11 months had passed since the last clear association to any Russian entities. The evidence collected tends not to support the suggestion that the diversion of traffic from Antifa.com to Joe Biden’s website was linked to the previous Russian registrant. So if you’d cut the corner in the intelligence cycle and gone straight from Collection to Dissemination you could easily have missed the important details and made the sensational – but unsupported – assumption that the diversion of traffic from Antifa.com to Joe Biden’s campaign site was a Russian scheme. It’s certainly tempting to take shortcuts and draw exciting conclusions, but this rarely makes for accurate reporting. Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 7 thoughts on “Website OSINT: What’s The Link Between Antifa.com and Russia?” Ray Dulac 20th August 2020 at 4:16 pm While this post feels like BullshINT, going from collection to dissemination, I wanted to help fill a couple of the collection gaps, since I have access to a paid Domain tools account. I reviewed the historical companies through a paid account. The goal of posting was to share more collection information. I don’t think it will change the analysis, just trying to help. When looking at the whois history section from 2002 to 2008, the whois record had the Organization listed as Eruobox in St. Petersburg. The record changed to the c/o Office-mail information on 2008-08-15. When reviewing the screenshot history, it shows that in 2009 the site was used for pharma sales on a web page called “Indian Drugs.” The screenshots are tagged 2009-07-31 and 2009-10-04. On 2009-12-14 it is back to the for sale style pages. The whois records from that time still show the c\\o Office-Mail. Loading... Reply Nixintel 23rd August 2020 at 1:06 pm Thanks for the extra info Ray. There’s really no subsitute for Domain Tools when it comes to historic WHOIS records! Loading... Reply Zhouhan 21st August 2020 at 2:21 am Thanks for sharing your insights! Loading... Reply Kadidia Doumbia 24th October 2020 at 10:53 pm A wealth of information. It will time to digest all. Thank you. Loading... Reply princeofsaiyanz 23rd June 2022 at 9:09 pm This was a very good read, I followed the process and it opened my eyes Loading... Reply Dan Dows 8th January 2024 at 1:44 pm You were correct in the calling post bs. They fabricated the Russia link. It doesn’t connect to Russia anywhere in any of domain research sites. So they not only responded to a fact with misinformation /lies. They did what all media now feels way to comfortable doing. They lied. The site is linked to Kalkofnsvegur 2, Reykjavik, Capital Region, 101, IS Loading... Reply Pingback: Evaluating contradictory foreign interference allegations in the 2020 U.S. election - DFRLab Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-17-at-20.33.37.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-17-at-20.38.38-2048x1840.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-17-at-21.20.10.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-17-at-22.17.18.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-13.43.22.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-14.13.52-2048x447.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-14.24.28.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-18.43.03-2048x250.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-18.59.24-2048x923.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-19.05.32-2048x575.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-19.52.02.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-19.55.57-2048x543.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-19.58.21.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-20.17.48.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-23.07.35.png","https://secure.gravatar.com/avatar/0302222195676697c7c4053e24a16d62e9880f24790ef61b1f1563d1eda37d5f?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/8e2022a012f6263d3a43b47ab52db129c03e7292d0bcb43fc57e19d84b6edd1f?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/a119af20a90be6372a467f0b49536b06a4c322d97c4cd6b2089f96e5935ccee7?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/a8dbec59c215a7304ee0e9f72018ce377e1a7869da6ef4dc675dc1de3278de1e?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/c20812e8c98a36cdf6d83498da81115a2fecba7bebbd71cf9a25b3f0996c4b4e?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/e379292b260973aa638e47e9d7150d2112dc65b62ade97b354143aaf9040607b?s=50&d=mm&r=g"],"local_images":["blog_data/images/blog_96509521c651_0.bin","blog_data/images/blog_96509521c651_1.bin","blog_data/images/blog_96509521c651_2.bin","blog_data/images/blog_96509521c651_3.bin","blog_data/images/blog_96509521c651_4.bin","blog_data/images/blog_96509521c651_5.bin","blog_data/images/blog_96509521c651_6.bin","blog_data/images/blog_96509521c651_7.bin","blog_data/images/blog_96509521c651_8.bin","blog_data/images/blog_96509521c651_9.bin","blog_data/images/blog_96509521c651_10.bin","blog_data/images/blog_96509521c651_11.bin","blog_data/images/blog_96509521c651_12.bin","blog_data/images/blog_96509521c651_13.bin","blog_data/images/blog_96509521c651_14.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/schedule/","title":"Schedule","status":"ok","retrieved_at":"2026-08-29T16:30:19.34645+08:00","text":"Home Schedule Schedule I teach SANS SEC497 Practical Open Source Intelligence and SANS SEC587 Advance Open Source Intelligence . Date Location Event Link 28 Sep – 3 Oct 2026 Bethesda, MD SANS DC Metro – SEC497 More Info 16-21 Nov 2026 Paris SANS Paris – SEC587 More Info 1-6 March 2027 London SANS London – SEC497 More Info Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email","image_urls":[],"local_images":[]}
+{"source":"nixintel","url":"https://nixintel.info/security/verify-your-online-identities-with-keybase/","title":"Verify Your Online Identities With Keybase","status":"ok","retrieved_at":"2026-08-29T16:34:22.534033+08:00","text":"Home Security Verify Your Online Identities With Keybase Verify Your Online Identities With Keybase 1 Comment / Security / By Nixintel Twitter’s recent decision to remove blue check marks from accounts it has previously verified causes a number of issues for the platform and its users. One of the most obvious ones is around authentic identity. Without verification, how do I know that a particular account really does belong to the person or organisation who claims to own it? Blue ticks made this a little clearer but without them it is much easier for fake and impersonation accounts to flourish. So how can Twitter account users verify their identities and proved that their accounts are authentically theirs? The inability to prove identity and authenticity without a blue tick makes it hard to deal with fakes. Fortunately help is at hand. The need to prove the authenticity of one’s identity is not a new problem in the world of information security and solutions exist to help prove that the users and services really are who they claim to be. By using cryptography it is possible to verify our identities beyond all doubt, and so if we can link cryptographic proofs to the websites and social media accounts that we own then we can prove irrefutably that they are ours. Introducing Keybase Cryptography is complicated but you don’t need advanced technical skills to take advantage of its benefits. Keybase is a web-based service that makes it easy to incorporate cryptographic keys into online identities with proofs . Keybase uses public key cryptography to provide services like end-to-end encrypted chat and file sharing but it also offers the ability for users to cryptographically verify that they own a particular social media account or website. After creating a Keybase account and then setting up and installing Keybase on your device (ideally on more than one device) Keybase allows you to claim and prove ownership of social media accounts and websites that you own. Keybase does this by providing cryptographic proofs that users can add to the Twitter accounts and websites that they own, thereby proving that the same person who owns a Twitter account also owns a particular website. Use Case: Twitter Account Verification Supposing your a Twitter user who has just lost your blue tick and you’re worried about people making fake profiles to impersonate you and your company. You could negate this problem by using Keybase to cryptographically prove that your Twitter account is also definitively linked to your website and/or other social media accounts, thereby removing any doubt that you are who you say you are. Here’s what this looks like in practice. After installing Keybase and setting up my account, my public profile shows that I have verified ownership of both my Twitter account and this website. Here’s the cryptographic proof for my Twitter account. This is Tweet is automatically generated by Keybase for me to paste into Twitter. Keybase then scans my profile to check for an exact match for the long random string of letters and numbers. If it finds the matching string, it will be able to verify that the account is linked to my Keybase profile. If it can’t, it won’t. Verification tweet that is used by Keybase to prove identity. By clicking on the link in my verification Tweet you can go to my Keybase profile where Keybase will confirm that my Twitter account does genuinely belong to me. Clicking on the verification link directs back to my Keybase profile, which confirms the authenticity of my account ownership. Notice that in my Keybase profile I have also verified that I control the domain nixintel.info. I did this by adding a cryptographically signed file generated by Keybase and uploading it to my server where it can be publicly viewed and verified. So you can see how you can use this technique to prove that your Twitter account is also associated to your website. If you have multiple Keybase users that belong to the same organisation, such as a particular news website, it is also possible to add multiple signatures to the website verification file . So if you are a news organisation whose journalists have just lost their blue checks and are worried about impersonators, one solution would be for each journalist to create Keybase profiles that verify their Twitter accounts and then also add their signatures to the Keybase verification file on the organisation’s website. That way they will be able to prove irrefutably that they own their Twitter account and that they really do work for the organisation where their signature file is stored. You can see how Keybase have implented this on their own site here . Adding the Keybase signature to a website proves ownership. But what’s to stop any random impersonator copying my verification Tweet or website file and trying to clone my profile? It might seem like an obvious way to work around the verification but it’s doomed to failure. Why so? Since Keybase derives the Twitter profile and website file proofs from cryptographic keys that are stored only on my devices, anyone who just copied the public proofs and pasted them into a fake site or profile would fail the Keybase verification process because they don’t have the necessary matching private keys. They would never be able to display the proof of ownership in their Keybase profile in a way that a genuine account holder would. Visibility Keybase verification is not a direct replacement for all of the features and visibility of a Twitter blue check, but it does prove with cryptographic certainty that users own the accounts and websites that they claim to. It’s also an extremely powerful way to expose fakes and discredit impersonators since they cannot produce the cryptographic proof that genuine accounts can. The only other thing to consider is how do you let your followers know how to verify you with Keybase? Twitter profile with a link to the verifying Keybase profile in the bio. Once you’ve added your proof tweet, you can make it your pinned Tweet. It isn’t essential that you pin it, but the tweet needs to stay in your feed so it can be verified by others. Another technique is simply to add a link to your Keybase profile in your Twitter bio or a link directly to your verification tweet. It’s not as visible as a blue check mark, but it is certainly a reliable way of proving your account ownership and authenticity. You also don’t need to pay $8 a month for basic cryptography. For a previous article on the OSINT opportunities that Keybase presents. Click here . Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 1 thought on “Verify Your Online Identities With Keybase” Pingback: از آناتومی اتومیشن تا قدرت AI در امنیت سایبری | SecWithMoh Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2023/04/kb_profile_proof.png","https://nixintel.info/wp-content/uploads/2023/04/kb_proof1.png","https://nixintel.info/wp-content/uploads/2023/04/nyc.png","https://nixintel.info/wp-content/uploads/2023/04/twitter_profile.png","https://nixintel.info/wp-content/uploads/2023/04/website_key.png"],"local_images":["blog_data/images/blog_2b8c7172515b_0.bin","blog_data/images/blog_2b8c7172515b_1.bin","blog_data/images/blog_2b8c7172515b_2.bin","blog_data/images/blog_2b8c7172515b_3.bin","blog_data/images/blog_2b8c7172515b_4.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2021-46","title":"","status":"ok","retrieved_at":"2026-08-29T16:28:57.652882+08:00","text":"Week in OSINT #2021-46 | Sector035 Week in OSINT #2021-46 Home Week in OSINT Articles Search Week in OSINT #2021-46 22nd Nov 2021 instagram geolocation google search engine deep fake quiztime facebook conference It was an awesome and productive week for me, followed by a weekend with GOSINTcon, a German conference. What will this week bring? So much good stuff being shared over the last week, followed by conINT, that I sadly had to miss, and on Sunday a German OSINT Conference. What else could one wish! Awesome couple of days, and now back to work. This week, I've got some nice tips and tools for you. Do you have any suggestions? Feel free to hit my DM's on Twitter , or email me at sector035 at pm.me. Off to this week's overview: Quiztime Solution Overload Search Instagram Video Verification Which Face Is Real? Facebook Marketplace Intelligence Conference conINT Article: Quiztime Solution Steven \"Nixintel\" Harris has been at it again, with a wonderful write-up of a Quiztime challenge. From identifying the specific aeroplane, to finding information about it's farewell tour, and eventually ending up with the exact location the photo was taken. Another great technique was introduced here by Steven: Using the Virtual Tours in Google Earth to quickly visit dozens of sites, to find a matching location. Thanks for this awesome write-up! The result of Nixintel's overpass query of cell masts Link: https://nixintel.info/osint/planes-and-cell-masts-a-quiztime-epic Tool: Overload Search Twitter account cyb_detective posts a constant stream of tools and tips on OSINT. Last week she tweeted about a very cool Extension called 'Overload Search' by Partial Overload , and is a nifty little tool to help people build a Google search query. Fill in all the necessary fields, and your own custom search is fired off at Google. If you search a lot by hand, this won't be so useful for you, but for people starting in the field of investigating, this is a very welcome tool to have. One little note: For me, the pull-down menu with languages and countries didn't work, so use the international ISO format for the country codes, and try the official English names of countries. Constructing a query bit by bit Link: Chrome extension Tip: Instagram Video Verification An awesome tip from Twitter user ohshint_ : If you're having issues with Instagram, and they demand a video of your face, you can trick the system easily by creating a little video. Open the Sketchfab, fire up the camera of your mobile phone, and capture away! #OSINT Protip 13: Is #Instagram banning your sockpuppets? Use this simple trick to bypass their new \"video verification\" data collection scheme. Step 1: Go to https://t.co/LCpxZZKOvO Step 2: Use your phones camera and follow Instagram's instructions. #OSINTProtip #Metaverse — OH SHINT! (@ohshint_) November 20, 2021 Link: https://sketchfab.com/tqyw/collections/human-face Site: Which Face Is Real? A cool tip from @digint31 , to practice your skills on recognizing computer generated faces. It's not that difficult if you know what to look for, but if you're struggling a bit I certainly recommend you to play here. If you're still new to the game, I can recommend a blog post by Nixintel , in which he describes all the tell-tale signs of such photos. Spotting the fakes Link: https://www.whichfaceisreal.com Tip: Facebook Marketplace Craig Silverman dove into Facebook Marketplaces, and found a nice way to find every listing on a marketplace account, and find out what year a Facebook account was created as a bonus at the same time. I've tested it with a Dutch Facebook account, and it does show up indeed. I've had a quick look at the source code, and the traffic sent to the browser, but it seems this is a text that is sent from the server, and I haven't been able to find a full date or timestamp somewhere. So it seems this is all you get, but this can be a very helpful tip! Thanks for sharing that with us Craig! For more tips like this, make sure to follow his newsletter over here . Information as seen by a Dutch Facebook user Link: https://www.getrevue.co/profile/craigsilverman/... Media: Intelligence Conference conINT On November 20 there was conINT , an intelligence conference, with some awesome speakers like Nicole Beckwith , Rae Baker , IntelCorgi and more! For now, it seems the video can only be watched back as a whole on Twitch. Link: https://www.twitch.tv/videos/1210896210 Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/c/c/5/8/2/cc582f7a3cb901df727b5981e30d012c70366d5e-2146-nixintel.jpg","https://sector035.nl/user/pages/articles/2021-46/2146-facebook.jpg","https://sector035.nl/user/pages/articles/2021-46/2146-overload-search.jpg","https://sector035.nl/user/pages/articles/2021-46/2146-whichfaceisreal.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_581c59c84ebb_0.jpg","blog_data/images/blog_581c59c84ebb_1.jpg","blog_data/images/blog_581c59c84ebb_2.jpg","blog_data/images/blog_581c59c84ebb_3.jpg","blog_data/images/blog_581c59c84ebb_4.bin","blog_data/images/blog_581c59c84ebb_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2021-47","title":"","status":"ok","retrieved_at":"2026-08-29T16:26:22.13562+08:00","text":"Week in OSINT #2021-47 | Sector035 Week in OSINT #2021-47 Home Week in OSINT Articles Search Week in OSINT #2021-47 29th Nov 2021 api tutorial geolocation tool facebook A small episode this time, with some tools, API's and explanations on how to geolocate! Not really a massive newsletter this week, but after working extra hard to get the first version of my tutorial on chronolocation ready for publication, I took some time off. Small update or not, still some interesting topics that I saved in my notes from last week: DumpItBlue+ Geolocation Write-up Protractor for Chrome API's for OSINT Geolocating a Tree Tool: DumpItBlue+ This tool has some interesting features, and even though Facebook has changed its layout, there are still things that work. The tool has several options that you can use, but make sure to first visit the correct page. Want to dump all friends? First open the all friends tab. Want to remove comments? Make sure to be in the timeline, and so forth. A nifty Facebook tool, with auto-scroll, comments expander, removing of items and a lot more. Thanks Ritu and Irina for sharing this tool last week! Dumping friends to a nice HTML table Link: Chrome extension GitHub: https://github.com/arioux/DumpItBluePlus Article: Geolocation Write-up Twitter user hpiedcoq shared a great article on Twitter, written by DrStache . From a seemingly impossible photo, taken somewhere in the Middle-East, he found the exact location. Using some handy tools, like the online protractor and OnTopReplica , among some maths to calculate the distance of buildings. Using the online protractor Link: https://link.medium.com/KCny0UG4slb Protractor: https://www.ginifab.com/feeds/angle_measurement/ OnTopReplica: https://github.com/LorenzCK/OnTopReplica Tool: Protractor for Chrome Talking about protractors, do you know it's also possible to have one in your browser? One that I found som time ago is the protractor for Google Chrome. It sits in your toolbar and when activated, it will project a simple protractor on the screen, making it easy to measure all kinds of angles. Measuring angles made easy Link: Chrome extension Tip: API's for OSINT This is an awesome list with API's that can be used to retrieve all kinds of information. This seems to include some paid options, but a lot of these sources are absolutely free. Thanks for collecting all these resources, and sharing it with us ' Cyber Detective '! An abundance of API's for us! Link: https://github.com/cipher387/API-s-for-OSINT Media: Geolocating a Tree Brecht Castel is a journalist and fact checker at Knack, and is well known on Twitter for his investigations. Since recent he also has a YouTube channel, where he'll be sharing some of his techniques. His second video, posted last week, shows you how he geolocated a baobab tree. Thanks Brecht! More tutorials like this are always welcome! Link: https://youtu.be/g-MvXuCCkEA Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/1/5/2/0/d/1520d0530dfb88b34cf5a1de89bf2143dbf083cf-2147-protractor.jpg","https://sector035.nl/user/pages/articles/2021-47/2147-apis.jpg","https://sector035.nl/user/pages/articles/2021-47/2147-dumpitblue.jpg","https://sector035.nl/user/pages/articles/2021-47/2147-protractor2.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_56efee5333b5_0.jpg","blog_data/images/blog_56efee5333b5_1.jpg","blog_data/images/blog_56efee5333b5_2.jpg","blog_data/images/blog_56efee5333b5_3.jpg","blog_data/images/blog_56efee5333b5_4.bin","blog_data/images/blog_56efee5333b5_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-06","title":"","status":"ok","retrieved_at":"2026-08-29T16:25:59.674998+08:00","text":"Week in OSINT #2022-06 | Sector035 Week in OSINT #2022-06 Home Week in OSINT Articles Search Week in OSINT #2022-06 14th Feb 2022 maps instagram geolocation iot processes reverse image search military geopolitical A small update from the world of OSINT news, with some maps, some geopolitical affairs and some tools. This week there's only a small update, since I ran into some issues with another tool I wanted to include. Once in a while there's a tool that looks really great, but when it's giving me trouble, it's eating away a lot of time needed to write all this. Things happen, and maybe I have the time to bugfix it and include it some other day. But despite being a small update, it's not less interesting in my opinion: Geowifi Ukraine Monitor Sterra Cleanup Pictures Cognitive Biases Tool; Geowifi The great Gonzo created an awesome tool: Geowifi. I had some issues with the virtual machine I use to test tools, so sadly enough I wasn't able to give this one a go. I love how he didn't stick to Wigle only, but also used other sources to find as much information as possible! Thanks for sharing Gonzo! Intoducing GeoWiFi | 📡💘🌎 I developed the tool because my twitter thread on the subject ( https://t.co/6tuUzhAzQa ) was well received and I thought it might be interesting to take it a step further. pic.twitter.com/EXJYsFftQm — GOΠZO (@GONZOs_int) February 9, 2022 Link: https://github.com/GONZOsint/geowifi Site: Ukraine Monitor The Centre for Information Resilience has created a map with open source information on the Russian military movements along the Ukraine border. The map is hosted on MapHub and every entry is timestamped, and has information about its source. If you are following this event, this is a map you will absolutely appreciate. Exploring the map with military movements Link: https://maphub.net/Cen4infoRes/russian-ukraine-monitor Tool: Sterra Last week hpiedcoq tipped me off on a new Python script called Sterra by meakaaet , a new Instagram analysis tool. It downloads a set of followers or accounts that are being followed, and their information, and enables you to run some analysis on the results afterwards. You can simply 'compare' two sets of results, and output the accounts they have in common to a new XLSX. What I like is that all results are saves in an Excel sheet, so you can download multiple sets of information, and take your time analysing the results at a later point in time. I didn't run multiple jobs yet, and knowing how fast the social media landscape changes, it might be that this tool will trigger some rate limits in the future. Analysis of followers I did run into a few issues when I tried to install it with Python3.8, so a little heads-up. You need to: Run at least Python3.9 Have Python3.9-dev installed Link: https://github.com/novitae/sterraxcyl Site: Cleanup Pictures Last week I sent out a Quiztime challenge, and when going over one of the solutions I found a lovely link. The website 'Cleanup Pictures' is a website that uses AI to remove unwanted objects from photos. Twitter user MCantow used it to remove a car from a photo, after which a reverse image search gave him good results. As an example, you can see here what the results look like. After Before ↔ The slider might not work on mobile phones Link: https://cleanup.pictures/ Article: Cognitive Biases 'Dutch OSINT Guy' Nico wrote an article on cognitive biases and why it doesn't deserve a place during investigations. It's not a lengthy article, but I do suggest reading it. The topic is not only important, but it can make the difference between a solid investigation, and a story based on your own personal feelings and ideas. Thanks for sharing Nico! NEW BLOG: Why #OSINT doesn't need your feelings Read it here: https://t.co/fSRs85Ap01 pic.twitter.com/1OYO4RmOkP — Dutch Osint Guy Nico (@dutch_osintguy) February 7, 2022 Link: https://dutchosintguy.com/... FUNINT: Fun With Google When it comes to Google Streetview, there are several sites out there that share funny scenes captured by the cameras. Need a break from work? Want to relax by looking at some weird and funny things out there? Then these sites might just be what you need. Link: https://www.streetviewfun.com/ Link: https://www.weirdgoogleearth.com/ Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/6/8/a/c/7/68ac76998ddc074d31322a947b26241fabdf6269-2206-challenge.jpg","https://sector035.nl/images/6/c/e/3/6/6ce36fcaff9ad0b71ca74771f8739f403ef2254e-2206-cen4infores.jpg","https://sector035.nl/images/d/3/2/b/f/d32bf21a9deeb77392a87f9e7161871f63f5269f-2206-challenge-clean.jpg","https://sector035.nl/user/pages/articles/2022-06/2206-sterra.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_cbf38e6d19b6_0.jpg","blog_data/images/blog_cbf38e6d19b6_1.jpg","blog_data/images/blog_cbf38e6d19b6_2.jpg","blog_data/images/blog_cbf38e6d19b6_3.jpg","blog_data/images/blog_cbf38e6d19b6_4.bin","blog_data/images/blog_cbf38e6d19b6_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-07","title":"","status":"ok","retrieved_at":"2026-08-29T16:25:32.569787+08:00","text":"Week in OSINT #2022-07 | Sector035 Week in OSINT #2022-07 Home Week in OSINT Articles Search Week in OSINT #2022-07 21st Feb 2022 maps instagram geolocation google companies corporate intelligence hacking cybercrime Another week with some tips, tricks and tools in the world of OSINT. Most have been shared a lot already, maybe I should try and find some more niche links... I get sent tips, tools and articles once in a while, but it can happen that they don't make it in my newsletter. Please don't feel bad, it's nothing personal, but usually I didn't have enough time to test it, or somehow I ran into an issue and needed to check things out, after which it's left untouched for some time. I felt it might be good to clarify this, because it has happened a few times in the last weeks, and now you know. But... For this week, I have the following items left to share: Mountains and Geolocating Company Search Hacking Snakes OSINT Start.me Page Investigating Digital Ads Google Maps Tip Instahunt Media: Mountains and Geolocating Benjamin Strick talks about how to use mountains for geolocation purposes. He talks about Google Earth 3D, how to use it and gives some examples on how he used it in previous investigations. After that he also shows the website PeakVisor, and talks about the main differences between the two tools. Link: https://www.youtube.com/watch?v=vNu2X7aCMkU Tip: Company Search Twitter user OSINTcanada shared a nice little trick last week on how to find information on companies via a Google search. Fun little company hack: site:( https://t.co/tAhZeUa6Aj | https://t.co/LLqyq4R4X9 | https://t.co/Hvzust06bd ) \"company name\" After your search, click the News tab. Have fun! — OSINTcanada 🌍 (@OSINTcda) February 16, 2022 I saw what was happening there, and very nice info-cards on people showed up. But there were lots of news articles in between too. So I tweaked the Google search a little, and added two other sites. It now shows even more hits, and mainly people: site:(linkedin.com/in | zoominfo.com/p | rocketreach.co | xing.com/people | contactout.com) \"company\" Article: Hacking Snakes Journalists of BR and WDR have been working together for months on end to trace down leads that were left behind by hackers over the years. By using open source, like archived pages, they were able to identify some people that are suspected to be part of a group of hacker with ties to the FSB. A visually stunning story by Hakan Tanriverdi , Florian Flade and Lea Frey, showing how investigative journalism can also work within the world of cyber-related issues. Link: https://interaktiv.br.de/elite-hacker-fsb/en Link: OSINT Start.me Page The Twitter account @start.me shared a link page last week, on the topic of OSINT. This collection of links is by the Faros Foundation and contains loads of links. Many of them are probably known already, but as usually there are also some niche and lesser known websites. There's an abundance of start.me pages already, and loads of links to sources, but there's always something new to discover. Links by the Faros Foundation Link: https://start.me/p/1kvvxN/ Article: Investigating Digital Ads Craig Silverman has his own newsletter, and the last issue talks about different sources you can use when you're trying to track down digital advertisements. He shares tools I've already covered , like TheMarkup's Blacklight, but also new sources like PageXray and Well-Known.dev. Nice collection of links, thanks for sharing! Detecting all trackers at 'purina.com' GetRevue newsletter: https://www.getrevue.co/profile/craigsilverman/ Tip: Google Maps Tip A nifty little trick by The SEINT on Google Maps and Google Streetview. When looking for a specific crossing, simply search for those streets with an ampersand. I tested it, and Google's AI understands anything you throw at it. Bot streets with a space, comma, ampersand, the word 'and', everything seems to work. Still a nice trick that I didn't know until now. Thanks for sharing! Looking for a specific crossing Site: Instahunt A cool little site that helps you find interesting locations within Instagram. Simply search for a location, click the button, grab all the JSON outout from Instagram, and the tool maps everything out for you. It returns and shows the Instagram and Facebook links to all sites returned by the search. Great tool by Louis Tomos Evans ! Quickly mapping locations Link: http://instahunt.co/ Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/0/1/5/e/d/015ed5203d4aebd5fdc213094f4b085d1d14989d-2207-instahunt.jpg","https://sector035.nl/user/pages/articles/2021-22/2122-blacklight.jpg","https://sector035.nl/user/pages/articles/2022-07/2207-googlemaps.jpg","https://sector035.nl/user/pages/articles/2022-07/2207-snake.jpg?classes-caption=1","https://sector035.nl/user/pages/articles/2022-07/2207-startme.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_da4d946e6ccf_0.jpg","blog_data/images/blog_da4d946e6ccf_1.jpg","blog_data/images/blog_da4d946e6ccf_2.jpg","blog_data/images/blog_da4d946e6ccf_3.jpg","blog_data/images/blog_da4d946e6ccf_4.jpg","blog_data/images/blog_da4d946e6ccf_5.bin","blog_data/images/blog_da4d946e6ccf_6.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-11","title":"","status":"ok","retrieved_at":"2026-08-29T16:25:02.064841+08:00","text":"Week in OSINT #2022-11 | Sector035 Week in OSINT #2022-11 Home Week in OSINT Articles Search Week in OSINT #2022-11 21st Mar 2022 geolocation ip address quiztime chronolocation obsidian accessibility Another short episode this week, with some cool links, IP Geolocation, workflow and reports, and chronolocation. This week it features something I discovered myself last week, a new and easy tool to use with chronolocation during the night. If ancient sailors were able to navigate the stars, it must be possible to use this same thing for chronolocation, right? And yes, up to a certain degree it's absolutely possible. But that's not all I have for you this week, there's more: Malfrat's OSINT Map IP Geolocation Obsidian in Your OSINT Work Accessibility and Reporting Chronolocation With Stars Links: Malfrat's OSINT Map The OSINTFramework didn't get an update for years, so Twitter user @MalfratsInd forked the original repo on GitHub and recreated it, filling it with links that are currently active and useful for investigations. There's still a lot of sites to cover, so if you have more ideas, head over to the GitHub repo and help it grow! Interactive OSINT mindmap Link: https://map.malfrats.industries/ Media: IP Geolocation Last month The OSINTCurious Project posted one of my articles on locating an IP address , and the lack of accuracy. I usually focus mainly on servers, but the techniques I wrote there are generic. Then I stumbled upon a video by Half as Interesting , describing an event from 6 years ago. It's about the dangers of blindly following locations provided by IP2Geo datasets. And it's shocking to read that even law enforcement didn't verify any of such information either. So I repeat it again, please don't make this mistake... Verification is key! With everything! Article: https://arstechnica.com/tech-policy/... Media: Obsidian in Your OSINT Work Micah Hoffman has his own company for years already, and he has some awesome course material over at MyOSINT.Training . One of the things he's been working on in the past few weeks is Obsidian, that has featured in my newsletter before too. And a few weeks ago he showed the possibilities in a live stream for OSINT investigations. Micah going over Obsidian for OSINT YouTube: https://youtu.be/sKF37Ng4gaI Courses: https://www.myosint.training/ Article: Accessibility and Reporting And another section that mentions Micah, because last week he played around with some highlighted boxes in an image. After converting the image to greyscale, not a lot was left to be seen. It might not be the best simulation (look at Coblis for a better option ), but the problem still exists. The most common problems are with red or green, and can range from seeing it weak to not seeing the colour at all. And let red and green be very common colours used in all these images we all share with the world. Simulating what people with colour blindness sees Link: https://webbreacher.com/2022/03/16/report-accessibility/ Tip: Chronolocation With Stars When Julia Bayer posted her Quiztime challenge last week, I went off to search for a tool to line up stars and other celestial elements. There are several 'sky maps' out there, but this tool is simple, clean and easy to use. After finding the rough location of the moon, you can match the date and time until there's a match. You can also select celestial bodies, and see their exact position and their rise and set times. Another new thing I discovered, by looking at Quiztime challenges ! Matching stars to find a time Link: https://www.timeanddate.com/astronomy/night/ Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/0/f/b/a/0/0fba00030f927bbf6ee5cec83ba4ae847d84a0da-2211-osintmap.jpg","https://sector035.nl/user/pages/articles/2022-11/2211-colourblindness.gif","https://sector035.nl/user/pages/articles/2022-11/2211-obsidian.jpg","https://sector035.nl/user/pages/articles/2022-11/2211-stars.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_767ba539d2f1_0.jpg","blog_data/images/blog_767ba539d2f1_1.bin","blog_data/images/blog_767ba539d2f1_2.jpg","blog_data/images/blog_767ba539d2f1_3.jpg","blog_data/images/blog_767ba539d2f1_4.bin","blog_data/images/blog_767ba539d2f1_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-16","title":"","status":"ok","retrieved_at":"2026-08-29T16:24:36.970504+08:00","text":"Week in OSINT #2022-16 | Sector035 Week in OSINT #2022-16 Home Week in OSINT Articles Search Week in OSINT #2022-16 25th Apr 2022 geolocation imagery google satellite imagery quiztime osintcurious linkedin legal verification analytics Another filled episode, with some videos and articles, but I also added some tips and insights on the new Google Analytics platform. This week there's quite some content, and there's been some really nice information out there that I needed to share here too. But I also decided to share some personal insights on Google Analytics 4. Because these analytics tags are being seen in the wild more and more, and since there aren't a lot of sights indexing them, we may have to do some manual searching for this: WeVerify Quiztime Walk Through Spectator Earth US Legality and Scraping Google Analytics ISearchFrom Bombal and TOCP Article: WeVerify In this article Jochen Spangenberg from DW looks back at many years of development of the WeVerify tool. Initially starting as the InVID project, this tool is now one of the most important tools used by factcheckers all over the world. It contains a range of image, text and video verification tools in the browser. Even though the project has officially ended last year, it may continue via a new project that is in the last stage of proposals. Let's hope it keeps being developed! The WeVerify toolbox Article: https://innovation.dw.com/... Link: Chrome extension Media: Quiztime Walk Through Twitter user Nattic has been solving Quiztime challenges for a while now, and some time ago he started creating YouTube videos of his work process. This video shows how important it is to pay attention to small details, and also how spacial awareness can result in solving a seemingly difficult quiz with ease. A great look into the art of geolocation that's worth to check out. Geolocating with Nattic Link: YouTube Video Site: Spectator Earth Some time ago Twitter user OSINT_Research shared a link to the website of Spectator , that features a range of tools for satellite imagery. It has easy access to freely available imagery by Sentinel and Landsat, and they even provide API access in case you want to automatically monitor an area. And don't think that it only features imagery in natural colour, because if you need an NVDI filter, or specific bands, that too is available. Searching and filtering free satellite imagery Link: https://spectator.earth/ API: https://api.spectator.earth/ Article: US Legality and Scraping Zack Whittaker has covered the latest news on legal issues concerning web scraping in the US. It may not seem to be important for some people, and others may not understand the difficulty here, but I do think it's a good idea to read the article. It clearly shows how the rules within the terms of service can be overruled by the law. This of course doesn't mean this outcome will be the same in other states or countries, but it does send a positive signal to journalists and researchers. Photo by Greg Bulla - Unsplash Link: https://techcrunch.com/2022/04/18/web-scraping-legal-court/ Tip: Google Analytics Google Universal Analytics (the famous UA codes) will be replaced by a new analytics platform, called Google Analytics 4 or GA4 for short. This already started somewhere in 2020, but here's a recent quote from Google's support page: On July 1, 2023, standard Universal Analytics properties will no longer process data. You'll be able to see your Universal Analytics reports for a period of time after July 1, 2023. However, new data will only flow into Google Analytics 4 properties. This means that it's important to extend the searching for analytics codes with a different code, that has a different prefix. It's of course possible to search for these tags by using websites like PublicWWW , NerdyData or even Shodan . Sadly enough I've seen that analytics specific platforms like DNSlytics still haven't been updated to use GA4. So be prepared to run manual searches for the time being, until they finally catch up! How to find the codes? To find the code, dive into the source code of a page, and look for: googletagmanager.com In case a global site tag has been used, this will point to a JavaScript that is called via the following piece of HTML code, where GA_MEASUREMENT_ID is the unique analytics code for this site or page: <script async src=\"https://www.googletagmanager.com/gtag/js?id=GA_MEASUREMENT_ID\"></script> When you dive into the source code, you can probably spot the analytics code, when you look at the last line of this code snippet: <script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push( {'gtm.start': new Date().getTime(),event:'gtm.js'} );var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src= '//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-AB1C2D'); In this case, it's the Google Tag Manager code that is clearly visible, starting with the prefix GTM- . Isn't there an easier way? As usual, there is indeed an easier way! Because you can install a nifty little extension made by Google, that will show you exactly what Google Analytics codes are on a website or page, and even are able to record all your visits, if you have a need for that. Easy overview of analytics codes GA4 Article: https://support.google.com/analytics/answer/10089681 Link: Chrome extension Tip: ISearchFrom Just a golden oldie that I think needs to be shared again. The website 'I Search From' can be used to target your Google searches by matching a specific location and language. Google will use this information to show 'localized' content within the search results, by which I was able to find a Chinese fish processing plant some years ago. Haven't heard from it yet? I do recommend you to have a look, play around with it, and compare the difference and quality of search results. Searching with local results Link: http://isearchfrom.com/ Media: Bombal and TOCP Last week some members of The OSINT Curious Project were guests at David Bombal's YouTube channel for an interview, where they talked about OSINT, how it's used within different areas of expertise, and share some stories from the battlefield. Well over an hour of tips, resources and information on how to get started with OSINT. The TOCP crew meet David Bombal Link: https://youtu.be/ImWJgDQ-_ek Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/5/4/8/0/a/5480aeeafd3c0b615b1b259b594f45c3b222a389-2216-isearchfrom.jpg","https://sector035.nl/user/pages/articles/2022-16/2216-linkedin.jpg","https://sector035.nl/user/pages/articles/2022-16/2216-spectator.jpg","https://sector035.nl/user/pages/articles/2022-16/2216-tagassistant.jpg","https://sector035.nl/user/pages/articles/2022-16/2216-weverify.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_a74f16b0bbbe_0.jpg","blog_data/images/blog_a74f16b0bbbe_1.jpg","blog_data/images/blog_a74f16b0bbbe_2.jpg","blog_data/images/blog_a74f16b0bbbe_3.jpg","blog_data/images/blog_a74f16b0bbbe_4.jpg","blog_data/images/blog_a74f16b0bbbe_5.bin","blog_data/images/blog_a74f16b0bbbe_6.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-22","title":"","status":"ok","retrieved_at":"2026-08-29T16:24:12.069276+08:00","text":"Week in OSINT #2022-22 | Sector035 Week in OSINT #2022-22 Home Week in OSINT Articles Search Week in OSINT #2022-22 6th Jun 2022 maps twitter geolocation youtube programming This Monday I've got another small collection of tips, articles and an upcoming interesting live stream in the field of OSINT. While diving into some Twitter related stuff, I discovered that in early April 2018 I only had about 250 followers when I started my Week in OSINT. Now, a bit over 4 years later, I have about 24k followers! And even though I'm a lot busier now than back then, I still love creating these little articles. Thanks for connecting, and sharing all those lovely resources with me! Twitter Search Subscriptions Spoonbill OSINT on Oil Rigs OSINT Automation YouTube Shorts TWITTER: @evowizz @wondersmith_rae @SANSDefense @jms_dot_py @dutch_osintguy @matt0177 @thegumshoo @cyb_detective @DemoDawid Tip: Twitter Search Subscriptions Dylan Roussel shared an upcoming feature on Twitter last week . It seems that they're testing a new option where you're able to turn on notifications on new tweets within a search query. It's unknown yet when it'll be live, and so far it's only visible to Alpha testers of the Twitter app. Let's just hope the testing goes fast, and that soon we're all able to use this feature! Image by Dylan Roussel Tip: Spoonbill I know this is a golden oldie, but since I've never covered it in my newsletter, and was reminded about it, I think it's time to share this one. Spoonbill gives you the ability to track the changes made by a Twitter account. Not all usernames are being tracked, but you can start tracking by connecting a Twitter account and subscribing to changes. To check whether an account is already in their database, simply go to: https://spoonbill.io/twitter/data/{USERNAME} Tracking changes over time Link: https://spoonbill.io/ Article: OSINT on Oil Rigs Rae Baker loves investigating maritime object, and this time she looked at oil rigs and other related items. In her new blog she covers a bunch of really useful resources that can help investigate anything that might have a connection to the world of oil. From geolocation, to tracking the transport of products like crude oil. Well done, and thanks for sharing this! Exploring the world of oil online Link: https://link.medium.com/h8G2G3Emzqb Media: OSINT Automation On June 23 there will be another live stream by SANS . In this stream Justin Seitz is their guest, and Nico Dekens , Matt Edmondson and John Terbush from SANS will interview him on the automation of OSINT. Can't wait to join this talk, and you should too if you're interested in learning some more technical OSINT! Join the crew, and start automating Link: https://youtu.be/S5-PKoEBbP8 Tip: YouTube Shorts This weekend Cyber Detective shared a nifty trick for YouTube shorts . You probably know them by now, the short clips that popup everywhere. They are slightly different from normal videos since they don't start with the standard interface. No way to skip to a specific time frame, no settings, no subtitles. But by changing the URL slightly, it's possible to enable them all. Twitter user Demian even gave an even easier trick. Simply take the URL, and change the word 'shorts' to the letter 'v'. So this: https://www.youtube.com/shorts/yFuK68u2-hw becomes: https://www.youtube.com/v/yFuK68u2-hw YouTube will rewrite the URL automatically and load the desired video in a regular player. Thanks for sharing this tip! Loading YouTube shorts in a regular player Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/6/e/0/e/9/6e0e94a67596d64b093fc8771d4c020249b2640d-2222-oilmap.jpg","https://sector035.nl/user/pages/articles/2022-22/2222-automating-osint.jpg","https://sector035.nl/user/pages/articles/2022-22/2222-spoonbill.jpg","https://sector035.nl/user/pages/articles/2022-22/2222-twittersearch.jpg","https://sector035.nl/user/pages/articles/2022-22/2222-youtube.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_3857113ce3ae_0.jpg","blog_data/images/blog_3857113ce3ae_1.jpg","blog_data/images/blog_3857113ce3ae_2.jpg","blog_data/images/blog_3857113ce3ae_3.jpg","blog_data/images/blog_3857113ce3ae_4.jpg","blog_data/images/blog_3857113ce3ae_5.bin","blog_data/images/blog_3857113ce3ae_6.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-28","title":"","status":"ok","retrieved_at":"2026-08-29T16:23:45.528119+08:00","text":"Week in OSINT #2022-28 | Sector035 Week in OSINT #2022-28 Home Week in OSINT Articles Search Week in OSINT #2022-28 18th Jul 2022 maps geolocation extension add-on tool social media programming documentary It's time for another break again, so this Monday I've rounded up some interesting links and have some extra bonus content! Every year around this time I take a break for a few weeks, and this year it was very much needed, since I've been busy on all levels. So in the meantime, I've collected some things that you can look at for the coming weeks. Maybe you could help out with adding platforms to WhatsMyName, or learn how to code Python. Enough ideas to help you through the upcoming weeks WhatsMyName Learn to Code Geolocation with Mountains Selection Search FreeMapTools Documentaries Tool: WhatsMyName Micah Hoffman is going to change the layout of the WhatsMyName script he has kept up for years already. It is one of the best tools out there, with a minimum of false positives, and he sure needs your help. Not only can you help by adding more platforms, but you can also help out thinking about a new JSON layout! Upcoming changes to WhatsMyName Link: https://github.com/WebBreacher/WhatsMyName Tutorial: Learn to Code You have loads of time on your hand, and finally want to spend some time learning how to code Python? Then I can tell you that FreeCodeCamp has got you covered! Learn all the basics with the course \"Python for Everybody\", that can be found under \"Scientific Programming with Python\". The good thing of it, is that you don't even need to create an account! Just jump right in, go over the videos, code along, and answer some questions if you want to! And did you know that on the bottom of the page there are the most popular tutorials? And that the news section has loads of extra content too, that's worth looking at? Scraping tweety things with Freecodecamp Link: https://www.freecodecamp.org Tutorial: Geolocation with Mountains A few weeks ago Eyran Millis shared a tutorial on LinkedIn about using mountain ridges in geolocation tasks. He goes over several use cases, and shows how one can use different sites to look for mountains and hills. Sites like PeakVisor , Peakery and Peakfinder are all included, and he gives some valuable tips on each of these. Thank you Eyran, for putting this guide together! Using PeakVisor to verify a location Link: https://www.linkedin.com/posts/... Tool: Selection Search The tool 'Selection Search' is a small tool for Chrome and Firefox that enables you to quickly search for selected text. The default selection has Google, YouTube and Stackoverflow, but it's extremely easy to add your own websites. It has a lot of customizable options too, to open links in a new window, incognito mode, a tab and it's even possible to assign hotkeys. A small, but very useful tool that was sent to me by Twitter user TRADECRAFT14 . It's possible to add your own sites Link: Chrome extension Link: Firefox add-on Site: FreeMapTools The website FreeMapTools has a large collection of handy tools when it comes to maps in general. Sadly enough some very useful tools aren't available any more due to costs. Some tools that are still working are mentioned on the front page, like a distance calculation tool. Thank you NothicEye , for sharing this site over on Discord! From the fire department, to a conference Link: https://www.freemaptools.com Bonus: Documentaries As a little bonus, I'll include some interesting documentaries for you to watch, and they all contain some level of online investigations. Netflix: D.B. Cooper: Where Are You?! A bran- new miniseries about the infamous skyjacker that goes by the name of D.B. Cooper. In 1971, he hijacked a plane and after receiving $200.000, he jumped out of a Boeing 727 after it took off to Mexico. And it wouldn't be in this episode if it wouldn't contain some armchair sleuthing. Link: https://www.netflix.com/title/81349547 Netflix: Why did you kill me? This is another documentary on Netflix, this time it is a story about a mother whose daughter was killed. A chilling story, about how a family used social media to go after the notorious gang involved in her death. Link: https://www.netflix.com/title/80991050 YouTube: Innocent Victims of Reddit Armchair sleuths are well known for solving a lot of unsolved cases, and the ease of which one can do an online investigation is part of the reason. But it doesn't always turn out so good! Have a look at this video by Wavywebsurf and make sure you don't make the same mistakes! Link: https://youtu.be/hi14dP5Rdm0 Have a good couple of weeks and enjoy your searches! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/8/9/6/4/7/896478ae907c81f63625348a8d64cbeb9e558955-2228-geolocation.jpg","https://sector035.nl/user/pages/articles/2022-28/2228-freecodecamp.jpg","https://sector035.nl/user/pages/articles/2022-28/2228-freemaptools.jpg","https://sector035.nl/user/pages/articles/2022-28/2228-selectionsearch.jpg","https://sector035.nl/user/pages/articles/2022-28/2228-whatsmyname.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_6d550f856eff_0.jpg","blog_data/images/blog_6d550f856eff_1.jpg","blog_data/images/blog_6d550f856eff_2.jpg","blog_data/images/blog_6d550f856eff_3.jpg","blog_data/images/blog_6d550f856eff_4.jpg","blog_data/images/blog_6d550f856eff_5.bin","blog_data/images/blog_6d550f856eff_6.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-35","title":"","status":"ok","retrieved_at":"2026-08-29T16:23:24.555974+08:00","text":"Week in OSINT #2022-35 | Sector035 Week in OSINT #2022-35 Home Week in OSINT Articles Search Week in OSINT #2022-35 5th Sep 2022 maps tutorial geolocation bookmarks opsec google This week only a short episode, but with some interesting topics! Like Gmail's GAIA, geolocation tips and loads of links and tips! This weekend I've been rather busy, and chose to spend some more time for myself than on this episode. But I still managed to gather some interesting topics, and I'm especially excited about the first article! Despite the fact it comes with some dangers, it's interesting to see that the holy grail of GAIA based investigations is found: From GAIA to Gmail Landmark Identification Collection of Collections OpSec and OSINT Tutorial: From GAIA to Gmail Some time ago I received a message from Bob Engelen , with a tip on how to resolve an email address connected to a Google account, when you only have the GAIA ID. I've written two guides over the years ( here and here ) on how you can leverage the information within Google accounts to find more information. Since late 2020 Google has started removing a lot of information regarding this, so it isn't as useful as it used to be. But one thing was left to be discovered: How can you find the email address when you only have a GAIA iD? Well... Go over to LinkedIn, and read Bob's article on how to do just that! Be careful, because you will have to send an actual message to the other party involved. And since you can't copy-paste from the article on LinkedIn, the actual URL you need to use is as follows: https://hangouts.google.com/?action=chat&pi={GAIA ID} Resolving an email address from a GAIA ID Link: https://www.linkedin.com/posts/... Sites: Landmark Identification OH SHINT! sent out a tweet with some very useful websites, that can help you with a geolocation task. Geohints offers a visual database of lots of landmarks and their respective geographic locations. The landmark recognition tool over at Toolpie uses image recognition to find where a landmark might be located. And the German site Brueckenweb has a database of bridges from all over the world, and offers a search function on parts of the name, construction type, year of construction and lots more. Looking at traffic lights in Europe on Geohints Link: https://geohints.com Link: https://landmark.toolpie.com Link: https://www.brueckenweb.de/... Links: Collection of Collections Twitter user OSINT Tactical expanded a list of Start.me pages that were collected by OSINT_Research . And besides expanding it, he also created a new Start.me page that is a collection of OSINT link collections. Besides that, he also created a backup over on GitHub, where you can find more than 130 link collections, filled with thousands of links to any subject imaginable. Thank you for collecting all these links and sharing it with the community! A new @startme OSINT project created by @OSINT_Research has now been added to OSINT inception which is a start-me of the best #OSINT start-me projects, you can also search through all projects with a Google CSE on the right side of the page: https://t.co/9K4xitjb2u #Inception — 𝚃𝚊𝚌𝚝𝚒𝚌𝚊𝚕 𝙾𝚂𝙸𝙽𝚃 𝙰𝚗𝚊𝚕𝚢𝚜𝚝 (@OSINT_Tactical) August 29, 2022 GitHUb: https://github.com/C3n7ral051nt4g3ncy/... Start.me: https://start.me/p/Pwy0X4/osint-inception Article: OpSec and OSINT Matt Makowski has written an article on operational security. But he did it in an interesting way, because he does not only show you what is important to keep hidden yourself, but he also shows what information could be gathered if someone you are investigating wasn't privacy minded. Via a collection of diagrams and examples he gives you pointers on what to look for when you are investigating someone, and at the same time he gives tips on how to stay secure yourself. Another great article from Matt! Pivot points and possible privacy concerns Link: https://www.osintme.com/... Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/user/pages/articles/2022-35/2235-gaia-to-email.jpg","https://sector035.nl/user/pages/articles/2022-35/2235-geohints.jpg","https://sector035.nl/user/pages/articles/2022-35/2235-osintme.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_c9657c1fd793_0.jpg","blog_data/images/blog_c9657c1fd793_1.jpg","blog_data/images/blog_c9657c1fd793_2.jpg","blog_data/images/blog_c9657c1fd793_3.bin","blog_data/images/blog_c9657c1fd793_4.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-42","title":"","status":"ok","retrieved_at":"2026-08-29T16:22:57.154195+08:00","text":"Week in OSINT #2022-42 | Sector035 Week in OSINT #2022-42 Home Week in OSINT Articles Search Week in OSINT #2022-42 24th Oct 2022 geolocation opsec google youtube tool search engine fake news cheat sheet disinformation Today I have a large edition, with topics like: Operational security, google searches, a cheat sheet and some handy tips! I spent some extra time last week collecting all kinds of links and tips, and I had lots of fun creating this edition. There were so many awesome tweets, articles and tips shared last week, and so many topics to cover! I enjoy writing such episodes the most, since it usually has something for everyone. Overview: Naval Opsec Let's Geolocate Bookmarklet Chinese Propaganda Geotargeted Google Search YouTube Handles Geolocation Cheat Sheet News: Naval OpSec Steven 'nixintel' Harris shared the story that was sent out by Marsattaqueblog , about how during an exercise a French frigate was sunk while they were literally 'off the radar'. From November 21 to December 3, 2021, a total of 23 ships, one submarine and 65 aircraft embarked on a maritime exercise . Despite any radio contact, since all radio and satellite communication was jammed ( source ), the red team sunk one of the blue frigates, simply because of a location found via Snapchat. The blue frigate was close enough to the shore, that it was within reach of a 4G mast, and was able to connect to Snapchat. After the discovery of the active account, a simulated strike with 14 missiles was ordered, since a precision hit wasn't possible. Another example of how bad OpSec can have a devastating effect. Polaris 21 Tweet: https://twitter.com/APB_Laudrain/status/1582316787894714368 Media: Let's Geolocate Benjamin Strick has been busy making some more light-hearted content, according to his own words. And I can say it's a great thing, especially with all the conflicts in the world that are dominating the daily news. And I encourage you to do the same. You can for instance join him in this video where he will be geolocating large pieces of art from all over the world. Another awesome video from Ben, and despite the fact some locations were very easy to find, it does give insight into his thought process. Pay attention and take note how Ben uses all the information available to solve each and every question. Link: https://youtu.be/6_77F1EZ30s Tool: Bookmarklet Twitter user OSINT_Tactical created a bookmarklet that enables you quickly search for a username within a range of social media. I'm not really a fan of this, since it actually opens up a bunch of tabs with results and this might cause some issues. Firefox and Brave only opens a single tab by default, and within Chrome you can't seem to run it from a blank page, and you need to explicitly give the okay to open multiple tabs in your browser before it works. I did decide to share it here, because it's another easy and fast tip to quickly find possible leads. A bunch of tabs, and someone 'stole' my username? Link: https://github.com/C3n7ral051nt4g3ncy/... News: Chinese Propaganda Fergus Ryan and his colleagues had a look at some Chinese propaganda, that feature two girls from Uyghur and that shop up in several videos. This Twitter thread goes over the information they found, connecting these videos to the so called 'Information Office'. This is an interesting thread, showing how information campaigns are being used to spread a certain narrative, and how, sometimes, they can easily be pulled apart. Thanks for the tip Lou . A written confirmation in one of the videos? Twitter thread: https://twitter.com/fryan/status/1582960014053949440 Site: Geotargeted Google Search Henk van Ess sent me a tip about a new way of 'geotargeting' Google searches. For several years I've been using iSearchFrom , and this handy site is able to target a specific location when searching. When searching for news, Google sometimes shows news items from your local area, and with the ability to target a very specific area, this might come in very handy. This tip was immediately followed up by a tip from someone called ' Einat FB ', that pointed out there is another site, called ' U Search From ', which is a modified and better tool than I've been using. Thanks for these tips! Searching while targeting specific areas Link: https://valentin.app Link: https://usearchfrom.com Tip: YouTube Handles Over the last few days I have received multiple emails about a new YouTube feature, called YouTube Handles. Creators are able to claim a handle, that will enable someone to generate a link that looks like this: https://www.youtube.com/@redbull Currently, this page will send back an HTTP code '303' , that redirects the browser to a different URL. In this particular instance, it will redirect you to the URL: https://www.youtube.com/user/redbull . According to the blog about it on YouTube, everyone that already had a custom channel URL set up, will have that same name reserved as a handle, and they stopped the option of creating new custom channel URL's for now. It is unsure what the future holds, but if a lot of YouTube users will claim their own handle, following this news, it might be even easier to find them! Link: https://blog.youtube/news-and-events/... Tutorial: Geolocation Cheat Sheet If you are new to geolocation, and you are still struggling with finding clues, then this might be an awesome cheat sheet for you! The SEINT created a large mindmap with lots of things that might be visible in a photo, that can help you on your way. This is a work in progress, and will be updated when he finds more items, but it's already impressive! Don't forget to use this as a cheat sheet only, and make sure to always come up with your own ideas too, when analysing an image or video. You can find a PNG and PDF version of this mindmap over at the SEINT's GitHub. Small portion of the very large geolocation mindmap GitHub: https://github.com/seintpl/osint FUNINT: Spooky Logic An awesome geeky joke, created by @38mo1 , that comes up around Halloween, and involves some classic 'logic gates'. Some of these will be known by the OSINT community, since the basis of it all is Boolean algebra, the same thing we use when creating our innovative search queries. But for the electrical engineers, this is known territory! Thank you for sharing this, OSINT Amy ! Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/f/0/9/2/e/f092e3f263a5f547cee49992da43f777a76079c0-2242-geolocation.jpg","https://sector035.nl/user/pages/articles/2022-42/2242-bookmarklet.jpg","https://sector035.nl/user/pages/articles/2022-42/2242-funint.jpg","https://sector035.nl/user/pages/articles/2022-42/2242-polaris21.jpg","https://sector035.nl/user/pages/articles/2022-42/2242-propaganda.jpg","https://sector035.nl/user/pages/articles/2022-42/2242-valentinapp.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_48a4834913f4_0.jpg","blog_data/images/blog_48a4834913f4_1.jpg","blog_data/images/blog_48a4834913f4_2.jpg","blog_data/images/blog_48a4834913f4_3.jpg","blog_data/images/blog_48a4834913f4_4.jpg","blog_data/images/blog_48a4834913f4_5.jpg","blog_data/images/blog_48a4834913f4_6.bin","blog_data/images/blog_48a4834913f4_7.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-44","title":"","status":"ok","retrieved_at":"2026-08-29T16:22:21.072845+08:00","text":"Week in OSINT #2022-44 | Sector035 Week in OSINT #2022-44 Home Week in OSINT Articles Search Week in OSINT #2022-44 7th Nov 2022 geolocation social media threat intelligence snapchat reverse image search mastodon This week I've got a lengthy episode for you, with a lot of topics, and I dive into Mastodon! Within the realm of social media, there's a lot going on. Twitter is dominating the news, not really in a positive way, but also Mastodon is getting more and more popular. These shifts happen once in a while, so it's important to stay up to date and check what kind of information can be derived from new, or upcoming platforms. In this weekly episode I make a little start, by giving you some basic pointers, that might help you understand Mastodon a little better. But of course there's more: Backmoji Threat Intel Clean Images Geolocation Cheat Sheet Genealogy Mastodon Intro Mastodon for OSINT Site: Backmoji Griffin wrote an article on how to retrieve previous versions of a Snapchat Bitmoji. He found out that by simply changing the URL where the Bitmoji is stored, he can retrieve previous versions. And right after that Micah Hoffman fired up his notepad, VSCodium, PyCharm or whatever he uses, and created 'Backmoji', a page where you can quickly retrieve an overview of all previous versions. Finding previous versions of Bitmoji's Article: https://hatless1der.com/... Backmoji: https://backmoji.osint.ninja Links: Threat Intel Last week Start.me shared a large list of links, this time targeting the realm of cyber threat intelligence. This page contains sites, reports and news items from a lot of different threat intel companies, and contains a wealth of information. A lot of information within this line of work contains open source information, and I love to learn from other disciplines to enhance my own game. Thank you Rahmat Nurfauzi for collecting these resources! Sites and news on threat intelligence Link: https://start.me/p/wMrA5z/cyber-threat-intelligence Tutorial: Clean Images Steven 'nixintel' Harris has written another great blog post on a geolocation challenge. This time he shows us that with the use of online tools, it is possible to clean up pictures and enhance search results by reverse images searches. He then continues to explain how he answered the other questions, and you get a good look at all the processes involved when dealing with open source investigations in general. Cleaned up Original ↔ Comparison before and after using https://cleanup.pictures Link: https://nixintel.info/osint/... Tutorial: Geolocation Cheat Sheet The SEINT has been busy again! Last time, back in issue 2022-42 , I shared a geolocation cheat sheet. And this time, he releases the second one, aimed at pivot points you might be able to find inside a location. It contains lots of different things to think about, from cellphones and clothes, to toys and TV's. An amazing job, creating another great cheat sheet. Thank you for sharing these with the community! Another geolocaton cheatsheet with useful tips Link: https://github.com/seintpl/osint Media: Genealogy Last week I listened to an episode of Science Vs, a podcast that is all about science, fact checking, and scientifically interesting stories. The episode that aired on October 20 is called \"The Mystery of the Man Who Died Twice\". It dives into the story of how genealogy, together with the DNA databases over at GEDmatch, solved a mysterious case that baffled the police. This story shows the power of genealogy, and I highly recommend listening to this episode. Listen to the episode on Spotify Link: https://pod.link/1051557000 Episode: https://pod.link/1051557000/episode/... Tip: Mastodon Intro With the current dumpster fire that is going on over at Twitter, a lot of people have exclaimed they would transfer to Mastodon. This social media platform has been around for some years, and is slightly different from Twitter, in the way that it uses decentralized platforms. It is possible to run your own server, called an 'instance', or find one that suits your needs, and create a profile. Messages, called 'toots', can be shared locally or public, by having them shared with other servers. The platform communicates via the ActivityPub standard , and can be used to communicate with other platforms using the same standard, like PeerTube , PixelFed or WriteFreely . With this social media platform, there's quite a bit of new terminology, so here is a small list of terms to remember: Term Meaning ActivityPub The open and decentralized protocol designed for social networks. It has options to create, edit or delete content and has server-to-server communications for so called 'federation'. Boost Mastodon's term for re-sharing a message. It is comparable to Twitter's retweet function. Federation Federated servers within Mastodon are servers that communicate with each other. Content from one server can be seen, shared or interacted with from other servers that are 'federated'. It can be seen as a network of trusted third party instances. Fediverse The term for the network of connected instances, that communicate with each other. Instance Server that is running a Mastodon server. There are thousands of different servers out there, each with their own community, agenda, ideology et cetera. Toot A message posted on Mastodon, usually up to 500 characters long. Username It is possible to have multiple accounts on different servers. The way a username is shown is like this: @[Username]@[MastodonInstance.Domain] . This does make it somewhat challenging when looking for someone if they have a generic username. And with that, let's dive into som tips when you are searching on Mastodon for content of people! Tip: Mastodon for OSINT On (probably) most public servers, that are part of the large 'fediverse', for instance Mastodon.social , it is easy to search for content. This can be content on that particular server, or on the federated ones, thus giving you the option to quickly find accounts. And you don't even need to be logged in for this, but when you do have an account, it will give you some more options. Do search via other instances too, like Mastodon.online , since it may give you some extra results. Searching for topics or tags If you are looking for specific groups, people with certain ideas or ideology, then it may be a good idea to check out whether there are any instances of interest. Some servers that provide lists, or even a search option: https://search.noc.social https://fediverse.space https://mastodon.fediverse.observer/list https://the-federation.info/mastodon There are far more instances though, and searching them is a painstaking job, but with some creative searching it will be possible to find interesting servers. If you still can't find something, then I do also want to point you out to the list with servers that are not federated over at Mastodon.social. This list contains servers that share content they do not want to show up in the public timeline, and can be found here , under 'Moderated servers'. Looking at the names of some instances, where some parts even have been redacted, I think this list is a great place to check out. Thanks Sinwindie for pointing this out to me! Another list of banned or blocked instances, where some have sensitive of extreme content, can be found over here on GitHub . Some of these are offline now, but is possible to check what other instances they communicate with, using a specific API endpoint. It is called a list of 'peers'. And if the server still runs Mastodon, the peers can be retrieved by simply going over to the server and query the following API endpoint: {mastodon instance}/api/v1/instance/peers In case you are looking for another curated list of instances, that mostly overlap with the public list of peers of Mastodon.social, check out this list with close to 9000 fediverse instances . This also contains other ActivityPub platforms, like PeerTube, Misskey, Owncast and more. There is a lot of information freely available, and searching within federated instances is quite easy. Diving into platforms that are more private, might give some extra challenges, where finding the correct platform might be the most difficult part. But with the current situation over on Twitter, I do think it is important to start looking at these decentralized social media a lot more, start learning how they work, and look at new innovative ways to investigate them. Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/7/7/5/d/2/775d27ae69039981118dd3176af9c4938d54f268-2244-cleanup2.jpg","https://sector035.nl/images/c/f/8/b/b/cf8bbec0bf0e9becdbf074d449ca6a8936b26805-2244-mastodon-search.jpg","https://sector035.nl/user/pages/articles/2022-44/2244-backmoji.jpg","https://sector035.nl/user/pages/articles/2022-44/2244-cleanup1.jpg?chache=1","https://sector035.nl/user/pages/articles/2022-44/2244-geolocation.jpg","https://sector035.nl/user/pages/articles/2022-44/2244-mastodon-blocked.jpg","https://sector035.nl/user/pages/articles/2022-44/2244-threatintel.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_a967ed7a8565_0.jpg","blog_data/images/blog_a967ed7a8565_1.jpg","blog_data/images/blog_a967ed7a8565_2.jpg","blog_data/images/blog_a967ed7a8565_3.jpg","blog_data/images/blog_a967ed7a8565_4.jpg","blog_data/images/blog_a967ed7a8565_5.jpg","blog_data/images/blog_a967ed7a8565_6.jpg","blog_data/images/blog_a967ed7a8565_7.bin","blog_data/images/blog_a967ed7a8565_8.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-47","title":"","status":"ok","retrieved_at":"2026-08-29T16:22:03.535316+08:00","text":"Week in OSINT #2022-47 | Sector035 Week in OSINT #2022-47 Home Week in OSINT Articles Search Week in OSINT #2022-47 28th Nov 2022 instagram tutorial geolocation tool social media steam podcast This week I dive into tips and TryHackMe, Steam and scripting, and some other things from the world of OSINT! Over the last few months all sorts of threat intel accounts on Twitter have been using the hashtag #OSINT. This, combined with all sorts of worldly turmoil and wars, it has been really tricky to find some interesting new content on there. But there are still tips and tricks out there, and this week, I gathered the following topics for you: TryGeolocateMe Steam OSINT Bash Scripting Practical OSINT Instagram Metadata Tutorial: TryGeolocateMe Early 2020 TryHackMe user Bee created a room called 'geolocatingimages'. I didn't see it before, but stumbled upon it recently. In this room you work your way through multiple levels of geolocation tasks, ranging from simple reverse image searches to finding IP cameras on Shodan. This is the same user that created the Shodan room , but this time it's about practising your geolocation skills. A step-by-step tutorial on geolocation Link: https://tryhackme.com/room/geolocatingimages Tool: Steam OSINT Over on the TOCP Discord, it was Forthe again who shared a new tool. This Python script enables you to get a better insight into a Steam user. It dumps the public friends list, but also gives a peek into interactions between users. By investigating these interactions, it can give you a better understanding of who might be a 'closer' online friend. User info on Steam Listing of commenters Link: https://github.com/matiash26/Steam-OSINT-TOOL Media: Bash Scripting OSINT Dojo made a short video on bash scripting, standard scripting language in Linux and MacOS. With this little tutorial you learn how to create a script that will run multiple user enumeration tools, and save all the information in a text file. These small scripts can not only speed up the information gathering process, but also makes sure you don't forget to run certain tools. The basics of bash scripting Link: https://youtu.be/hrXZv0hST0M Media: Practical OSINT Join Matt Ashburn and his guest Brian Fuller from Mercyhurst University, where he is director of operations for the Ridge College of Intelligence Studies and Applied Sciences. In this podcast Brian discusses hands-on tips from the field of OSINT. I wished this episode was a lot longer, but it still has some good tips on things like operational security. Learn some very basic things, like keeping an eye on different time zones, or making sure to visit other sites before and after visiting a specific target. Another great episode from NeedleStack by Authentic8! The Authentic8 podcast, also on YouTube! Podcast: https://pod.link/1600516532/... YouTube: https://youtu.be/RMzz_yB7DUs Tip: Instagram Metadata Until a few months ago, it was possible to retrieve the JSON data of an Instagram post by adding something in the URL. Then it stopped working, and there were some workarounds. But lately I've seen people post a new and slightly edited version of it, and this one works as a charm! {IG URL}/ ?__a=1&__d=1 I suspect the addition of __d=1 is a parameter to tell Instagram that we are working with a 'desktop' version of Instagram. I don't have an older example at hand, but the amount of information that is sent back also seems to contain more than before. Retrieving JSON data from IG once more Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/2/b/4/3/0/2b430b2de45fa49fa4a0b6274f47ff4fea2f2e80-2247-steam2.jpg","https://sector035.nl/user/pages/articles/2022-47/2247-instagram.jpg","https://sector035.nl/user/pages/articles/2022-47/2247-steam1.jpg","https://sector035.nl/user/pages/articles/2022-47/2247-tryhackme.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_4806e024679a_0.jpg","blog_data/images/blog_4806e024679a_1.jpg","blog_data/images/blog_4806e024679a_2.jpg","blog_data/images/blog_4806e024679a_3.jpg","blog_data/images/blog_4806e024679a_4.bin","blog_data/images/blog_4806e024679a_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-49","title":"","status":"ok","retrieved_at":"2026-08-29T16:21:42.941671+08:00","text":"Week in OSINT #2022-49 | Sector035 Week in OSINT #2022-49 Home Week in OSINT Articles Search Week in OSINT #2022-49 12th Dec 2022 twitter domains geolocation zotero The last episode of 2022, with a few nice tips and tools, and a little rant over the shift within the Twitter atmosphere. Last week the Twitter account of Sarah Womer (UnleashedOSINT) went offline. The reason? She was pointing out right-winged accounts and companies active on Twitter, promoting their business. It seems that a mass report followed, and her account was permanently suspended. Then there's also the story of why three members of the Twitter Trust and Safety Council quit . Does free speech on Twitter means that more hateful accounts are being reinstated ? Is this the end of Twitter as we knew it? I personally think so. But on the other hand, this will become the largest platform to keep track of, when looking at extremists. And the good thing is, we have had years of practice when it comes to OSINT. So it will be more than easy to find whatever we need on there! Anyway, that is enough ranting in this last episode of 2022. Earlier this year I tried to come up with another end-of-the-year OSINT quiz, but I simply haven't had the time to finish one. So for the next few weeks, I will be checking out some interesting content on Mastodon (you can find me here by the way), or I will be very busy relaxing and enjoying the holidays! Zotero Azure's AADInternals Geolocating With the Stars Locked Twitter Accounts Tool: Zotero Over on Mastodon Bashinho shared a tip about Zotero. This program is for saving and annotating information, and has a browser plugin for Firefox and Chrome. With a simple click of a button you can save pages, make notes, and save them offline. This way you can build a collection of locally stored web pages and quickly search through them. In his German video he also shows the export function, where he shows how to save a list of found resources to a CSV file. Thanks for this tip! Saving pages with Zotero Link: https://www.zotero.org Tutorial: Azure's AADInternals Steven 'Nixintel' Harris wrote a blog post about the 'AADInternals' tool, that was created by Dr. Nestori Syynimaa . The tool is used to administering Azure AD and Office 365, but for there is also an online tool to get a first glance at domains that are administered by a company. By simply searching on a domain name of interest, you can check whether they use Azure AD for their domains, which domains are managed or federated and what STS (Security Token Service) they use. From there, you can pivot for more information. Only the first 20 results are shown, but if you want to know more, then do install the AADInternals and run it directly within Powershell. Checking out some random bird site Blog: https://nixintel.info/osint-tools/... Link: https://aadinternals.com/osint Tutorial: Geolocating With the Stars John McElhone spent some time looking at a photo of a new B-21 Raider, and came up with a nice idea. He wanted to try and find the location where the photo was taken, by looking at the constellations that are visible in the photo. By using Astrometry.net and Stellarium , and armed with some EXIF information, he managed to find and confirm the location where the photo was taken. The end result of John's geolocation job, and the original photo Link: Twitter thread Media: Locked Twitter Accounts Sinwindie shared a nice tip on how you can still get some more insight into a locked Twitter account. By looking who is interacting with the account, or checking out archived or cached pages of a previously opened account, it is still possible to find more info. One extra tip: Within Google it is also possible to check the actual cache. It's a bit more hidden nowadays, but can be found by opening the little 'kebab menu' (the three vertical dots) and look for the option 'Cached'. Link: https://youtu.be/-YPuJqvae0c FUNINT: Google Review Zewen shared this tweet over on Discord. It's a 'golden oldie', but... This is just another great example of using open sources to solve a crime Have a great holiday season and see you in 2023! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/5/7/1/2/2/57122a49960d536821dea3d4bb3027af45279d9f-2249-geolocation.jpg","https://sector035.nl/user/pages/articles/2022-49/2249-aadinternals.jpg","https://sector035.nl/user/pages/articles/2022-49/2249-funint.jpg","https://sector035.nl/user/pages/articles/2022-49/2249-zotero.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_51d0100fef63_0.jpg","blog_data/images/blog_51d0100fef63_1.jpg","blog_data/images/blog_51d0100fef63_2.jpg","blog_data/images/blog_51d0100fef63_3.jpg","blog_data/images/blog_51d0100fef63_4.bin","blog_data/images/blog_51d0100fef63_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2023-12","title":"","status":"ok","retrieved_at":"2026-08-29T16:21:17.494327+08:00","text":"Week in OSINT #2023-12 | Sector035 Week in OSINT #2023-12 Home Week in OSINT Articles Search Week in OSINT #2023-12 27th Mar 2023 geolocation tool overpass turbo ai chatgpt This episode turned into a geolocation and OverPass special, with a little extra topping of OpenAI's GPT! Geolocation is a very important part of the OSINT landscape, and besides manual investigations, there are also tools that can help you. One of the most helpful tools, is OverPass Turbo. By querying the OpenStreetMaps API, it is possible to find locations in any location of the world. But the query language isn't really easy to master for me, but luckily there are some things that will help, as can be read in this episode of Week in OSINT! Finding Sherlock OverPass and GPT More OverPass and GPT Learning OverPass Poastal Media: Finding Sherlock Gary Ruddell is a cybersecurity professional from Schotland, and has posted a few OSINT based videos on YouTube. His latest video is about Sherlock, and I don't mean the video where he talks about the username tool . I mean the American series Elementary, the modern take on Sherlock Holmes. He shares his thought process while geolocating the rooftop of a video production company that is used a few times in this series. Great video if you want to learn a bit more about this subject, and also a good training idea to use tv-series or movies to practice your skills. Link: https://youtu.be/VzUDFM3K4Sk Tip: OverPass and GPT The latest version of Chat GPT-4 has been dominating the news lately, and I also have been playing with GPT-4, as well as the Bing Chat. But John Wiseman found something really neat, and that is the use of GPT-4 to create useful OverPass Turbo queries. Just like him, I'm also not great at writing queries, so every bit of help is useful in this case. So if you have access to GPT-4, do give this a try! I did find out that with more complex queries, it had some issues filtering the correct 'amenities' though, but since the AI is constantly improving, and it is possible to edit the query, this isn't a huge issue. Using ChatGPT to find locations in OSM Link: Twitter thread Tool: More OverPass and GPT Yes, there is even more to come. Because how would you like to connect GPT-3 to a custom web-app, that focusses on OverPass Turbo queries only? Well, Ben Strong did just that! He wrote a small Python script that queries the GPT-3 model, adds a fact or joke, and displays the result of the query on a small map. Sadly enough, my paid API trial finished end of last year, and I haven't connected any payment options, so I haven't tested it myself yet. But if you do have a paid account, and you are willing to dive into this, have a good understanding of how to install and configure it, then this is a great opportunity to play a bit more with OverPass! Asking GPT-3 for Indian restaurants near Hereford Link: https://github.com/earth-genome/ChatGeoPT Blog: https://link.medium.com/rm0nVEvAtyb Tutorial: Learning OverPass This project is 8 years old, and they could really use some help with the creation of new lessons. Would you like to help out? Then make sure to check out their GitHub repo ! Do you want to know more about OverPass Turbo? Well, there is an older interactive tutorial, where you can learn how to write some basic queries. I have followed it, and I found it does require careful reading, and some basic knowledge about the query language will absolutely help. But it is absolutely something I suggest you check out if you want to learn some basics of the OverPass query language. Besides an interactive tutorial, they also have useful documentation with lots of examples. Link: Tutorial Link: Documentation Tool: Poastal Jake Creps has been busy going over all kinds of platforms, to check API responses. He started writing a little tool that will be able to tell you whether an email address is already registered for a certain platform or not. I was lucky enough to have a sneak peak over the weekend, so I could try it out, and it works as intended. The code is very rough, there are false negatives, and can absolutely be improved, but I really like the idea! Checking registered emails on sites and platforms Link (when it goes public later on): https://github.com/jakecreps/poastal FUNINT: OpSec and Cake Jordan Wildon , the maker of Telepathy, shared his moment of embarrassment when it comes to OpSec. Well played Nick, well played... Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/user/pages/articles/2023-12/2312-learnoverpass.jpg?classes-caption=1","https://sector035.nl/user/pages/articles/2023-12/2312-opsec.jpg","https://sector035.nl/user/pages/articles/2023-12/2312-overpass-ai.jpg","https://sector035.nl/user/pages/articles/2023-12/2312-overpass.jpg","https://sector035.nl/user/pages/articles/2023-12/2312-poastal.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_54bf39ddea87_0.jpg","blog_data/images/blog_54bf39ddea87_1.jpg","blog_data/images/blog_54bf39ddea87_2.jpg","blog_data/images/blog_54bf39ddea87_3.jpg","blog_data/images/blog_54bf39ddea87_4.jpg","blog_data/images/blog_54bf39ddea87_5.bin","blog_data/images/blog_54bf39ddea87_6.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2023-17","title":"","status":"ok","retrieved_at":"2026-08-29T16:20:55.794656+08:00","text":"Week in OSINT #2023-17 | Sector035 Week in OSINT #2023-17 Home Week in OSINT Articles Search Week in OSINT #2023-17 1st May 2023 twitter geolocation privacy opsec social media virtual machine security After a week off, I'm back with several topics ranging from geolocation, Tweetdeck, a streaming platform and some OpSec tips. Two weeks ago I knew my week was fully planned, so there wouldn't be time to publish an episode, so I chose to take some time off. For this week, I have some cool topics to talk about, but one thing I do urge you to read, is the first section about Atlas OS. Because no matter what reason someone has to create and run a virtual machine, there are things one should avoid at all cost, like a complete lack of security! Atlas OS Geolocation Tweetdeck Kick Identity Protection Tip: Atlas OS Last week I was going over some tweets by Daniel Card, aka mRr3b00t , about a new, stripped down Windows environment called 'Atlas OS'. Even Linus Tech Tips posted a video about this on their YouTube channel. I know for a fact that within the OSINT community there are people that use a slimmed down version of an OS for virtual machines, but I wanted to post a strong warning here. Don't simply download an OS, configuration script, or even a pre-built image if it is not downloaded from the website of the original maker of the OS. Yes, there are some pre-built environments that have been shared by me before, like Tsurugi , which can be called an exception. But in this case, Atlas OS removes all security features that makes Windows safe to use, like Windows Defender and security updates! Don't... Please, just don't! Do you want to investigate adversaries and visit all kinds of shady websites, without any form of protection? With the only plus side of sparing some seconds while clicking through some sites? The AtlasOS team has responded on Twitter that they will show a warning about disabling these featured in an upcoming release. Let me end this section with a general tip from me, and probably the rest of the InfoSec community: If you don't know what you're doing, better not do it at all! Article: Geolocation Steven 'Nixintel' Harris posted another geolocation tutorial earlier this month. He talks about a challenge that was posted by Conor Nolan on January this year. In the article he explains how he used small details in an image to generate enough clues to find the correct location. Again this shows the importance of going over the fine details of an image when being tasked to geolocate it, and Steven again takes us along his thought process when dealing with these tasks. Thanks again for the great explanation! Searching for Maxi Zoo stores in the UK Link: https://nixintel.info/osint/... Tutorial: Tweetdeck Sofia Santos wrote an article on Tweetdeck, and has updated it to reflect the most recent changes. This post goes over how Tweetdeck is used to create columns with searches, profiles and lists to keep tabs on a specific topic. This is a wonderful tutorial for everyone that hasn't used Tweetdeck yet. And with Twitter slowly becoming an uncensored, unregulated, right-winged platform, the importance of monitoring this platform might be more important than ever. And while tweeting her updated blog post, she also shared a cheat sheet by Zilvinas Kucinskas , that lists all search operators for Twitter. Step-by-step tutorial on how to fill Tweetdeck Tutorial: https://gralhix.com/2022/... Cheat sheet: https://www.exportdata.io/blog/... Tip: Kick Kick is an alternative streaming platform, and I heard about it last week after it was mentioned by the OSINT community over at Kase Discord . And while checking the resources using the 'developer toolbar', I found some interesting URLs that can be queried without being logged in. Sadly enough, I haven't managed to get it working with cURL, since they seem to check whether JavaScript is running. https://kick.com/api/v1/users/{username} This API endpoint on a user, gives basic information on the username, which is also visible on the page itself. One extra thing that is mentioned is the numerical user ID, and a link to the profile image. https://kick.com/api/v1/channels/{username} The v1 of the channel endpoint, gives the most information. Most noteworthy are the following fields, that aren't visible by simply browsing there: Entity Information name_updated_at Date and time when the channel name was changed banner_image URL of the banner that is used user It contains the field email_verified_at , with a date and time of email verification chatroom Information on when the chatroom was created and updated previous_livestreams Overview of the last live streams, including a dates and times of the stream, publication and the last update verified The channel ID, creation date and the last update of the verification status There is also a v2 of the API, that can be found at: https://kick.com/api/v2/channels/{username} It has mostly the same information as the v1 endpoint, but is a lot more slimmed down and lacks information on a few things, like the overview of previous streams. There are more API endpoints, but most of the information can be seen in the browser itself. But if you do find more interesting information, do share them with the community! Tutorial: Identity Protection Earlier this month the 'Special Operations Command' of the US Army released their updated 'digital identity protection toolkit'. This extensive guide is full of tips and hints on how to protect your identity online. On their website you can download the full 160-page PDF-file, or you can download the general sections separately. They also have so-called 'smart cards', with information on the most common social media platforms, fitness apps, and other websites. This resource is an absolute must if you are looking to protect your online identity, or need to tighten your OpSec! OpSec tips per category or platform Link: https://www.soc.mil/IdM/publications/IdMpubs.html Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/4/6/7/e/c/467ec55372793e00d4d4f65e1e74a75f82a5c00d-2317-nixintel.jpg","https://sector035.nl/user/pages/articles/2023-17/2317-atlasos.jpg","https://sector035.nl/user/pages/articles/2023-17/2317-opsec.jpg","https://sector035.nl/user/pages/articles/2023-17/2317-tweetdeck.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_da87fa33c3e4_0.jpg","blog_data/images/blog_da87fa33c3e4_1.jpg","blog_data/images/blog_da87fa33c3e4_2.jpg","blog_data/images/blog_da87fa33c3e4_3.jpg","blog_data/images/blog_da87fa33c3e4_4.bin","blog_data/images/blog_da87fa33c3e4_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2023-19","title":"","status":"ok","retrieved_at":"2026-08-29T16:20:22.586715+08:00","text":"Week in OSINT #2023-19 | Sector035 Week in OSINT #2023-19 Home Week in OSINT Articles Search Week in OSINT #2023-19 15th May 2023 twitter geolocation google search engine telegram factchecking ai fake news Another packed episode, with topics ranging from fake news, to Telegram, and an old Chrome extension! So much to talk about, and not everything made it into this week's episode, because I was a bit busy over the weekend. But I did manage to read a lot, and play with the Google Unlocked extension, and I am still happy that I'm able to write this Week in OSINT for close to five years, and keep on top of the OSINT news while doing it! Let's crack on, with the following topics: Inactive Twitter Accounts AI and Geolocation Telegram VM Fake Protesters New TLD Google Unlocked Tip: Inactive Twitter Accounts Let's start with a warning about the new inactive account policy that was published on April 24 this year. The previous policy was published on September 13, 2019 and mentioned an inactive period of 6 months . I know from personal experience that Twitter didn't really act on this policy, since I still have a dormant account for a quiz out there. But if they are changing this policy, and are going to act on it, this might become a problem. Just think about investigators that actually hold dozens of accounts, and want to plan a long holiday... Twitter's new policy on inactive accounts Tip: AI and Geolocation Henk van Ess shared some tips on how AI can be useful during investigative work. In this article he talks about generating lists of addresses, or coordinates. But what I found most interesting myself, is the last part of the post where Henk uses AI to find an address. By giving only partially available information, such platforms can easily return possible hits. At last, this is a use of ChatGPT for OSINT, that I think is absolutely great. Filling in the blanks, with AI! especially when one need to fill in the 'blanks'! Link: https://www.digitaldigging.org/... Tutorial: Telegram VM Ginger T has posted a first part of a tutorial, where he describes how he built his Telegram VM. He takes the time to explain his language and VPN setup, why he uses containers in Firefox, and talks about his OpSec. He also talks in length about different settings in his browser, and the add-ons he uses in his VM. This is a wonderful tutorial for people that are new to setting up a VM, and I can't wait to read the second part! The containers within Ginger T's VM Link: https://www.cqcore.uk/... Article: Fake Protesters Over the last few weeks journalists have uncovered a form of \"fake news\" I didn't see before. By sending people to genuine protests, but having them hold up signs that show pro-Russia and other messages, people were trying to be tricked into believing a different narrative. The photos that were taken of these 'protesters', had to make people believe there was more support than really was the case. An interesting investigation, and Twitter thread , by Kevin Shakir and his colleagues from the Danish DR Nyheder , Le Monde , Süddeutsche Zeitung , Westdeutscher Rundfunk , Norddeutscher Rundfunk , Expressen , NRK and SVT . Fake protesters uncovered Article (DK): https://www.dr.dk/nyheder/... Link: Twitter thread Tip: New TLD Back in 2014 ICANN delegated a new TLD to their root servers, the top level domain .zip . Recently it became possible to register a domain name ending with this TLD, and many people did. This created quite an uproar in the InfoSec community, and I can understand why! When I looked into some of the most recent domain registrations, I found domains that could pose as legitimate programs of files. On May 12, the amount of registrations took a small leap, followed by an explosion of registrations on the May 14! Registrations of ZIP domain names To give an example of the cesspool of domain names that were registered, I had a look at some very misleading domain names. All of these can easily be mistaken for a genuine file name: Date Domain 6 April tumblr.zip, audible.zip 19 April facebook.zip, whatsapp.zip 20 April waze.zip, chromium.zip 12 May attachments.zip, document.zip 13 May vacationphotos.zip, windowsdrivers.zip 14 May office-update.zip, windowsupdate.zip 15 may attachement.zip, bankstatements.zip You want to keep an eye out for newly registered domains yourself? Or want to search for domains that might impersonate specific brands? Then do check out one of the best free sources our there, called DN Pedia. There you can see that on May 14, almost 2300 domain names were registered with this top level domain. Link: https://dnpedia.com/ Tool: Google Unlocked I received a tip about a new browser extension, called Google Unlocked. With this extension installed in Chrome or Firefox, it will be possible to see hidden, or removed, results directly in your browser. It works by looking for a response that contains a link to the Lumen Database on the bottom of the search page. The extension opens that page, and extracts all URL listed there, and places them on the bottom of the search results. Thanks for the share Exalt Before After ↔ Link: https://github.com/Ibit-to/google-unlocked Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/7/1/e/9/9/71e991451f55723bf2131062c7ba6ac88e795a74-2319-google-unlocked-before.jpg","https://sector035.nl/images/9/3/6/9/5/9369559b760edcc1022110de236e4a70e18e6fc6-2319-google-unlocked-after.jpg","https://sector035.nl/user/pages/articles/2023-19/2319-chatgpt.jpg","https://sector035.nl/user/pages/articles/2023-19/2319-fake-protesters.jpg","https://sector035.nl/user/pages/articles/2023-19/2319-telegram-vm.jpg","https://sector035.nl/user/pages/articles/2023-19/2319-twitter.jpg","https://sector035.nl/user/pages/articles/2023-19/2319-zip-tld.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_7d949ff5d26d_0.jpg","blog_data/images/blog_7d949ff5d26d_1.jpg","blog_data/images/blog_7d949ff5d26d_2.jpg","blog_data/images/blog_7d949ff5d26d_3.jpg","blog_data/images/blog_7d949ff5d26d_4.jpg","blog_data/images/blog_7d949ff5d26d_5.jpg","blog_data/images/blog_7d949ff5d26d_6.jpg","blog_data/images/blog_7d949ff5d26d_7.bin","blog_data/images/blog_7d949ff5d26d_8.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2023-25","title":"","status":"ok","retrieved_at":"2026-08-29T16:16:42.177146+08:00","text":"Week in OSINT #2023-25 | Sector035 Week in OSINT #2023-25 Home Week in OSINT Articles Search Week in OSINT #2023-25 26th Jun 2023 maps twitter geolocation telegram armed conflicts This episode turned out completely different from expected, but I have no doubt that I gathered some interesting tips. Initially I planned to write my episode on Friday evening and Saturday morning, but due to the developments in Russia I had other priorities. Despite the fact I am not always following politics, conflict areas, or global affairs, I simply had to keep an eye out for the latest news. That also meant I only had a Sunday to find some extra items, read articles, test tools and whatever is needed to fill a Week in OSINT. And then It struck me: I can simply write about the easy to use, and free tools, that I used to try and stay on top of everything. But since I usually only do OSINT investigations, and monitoring is not my daily work, I had to come up with something that was easy, and quick to set up. So here we are, half of the usual Week in OSINT, and a collection of tips and tricks, to get free monitoring up and running in no-time: Geolocating MwOsint German Street View LiveUAMap Telegram to RSS Feed Informer Twitter Monitoring Article: Geolocating MwOsint Twitter user Daan2k21 has caught the bug of geolocating, and created two write-ups on Medium at this point. One of those I really wanted to share in here, and he describes in detail how hw located MwOsint , and how he found the exact time the photo was posted. A well written, clear step-by-step guide with some good tips and sources. Thank you for sharing this! Geolocating in the Alps Link: https://link.medium.com/Kd6n4K6cRAb News: German Street View On June 8 it was announced in ' The Keynote Germany ', that from June 22 on the Google Street View cars would be roaming the street of Germany once more. When Google started capturing 360° images in Germany, the citizens were outraged about a breach of their privacy, and demanded to have their houses blurred. The amount of blurring would take so much effort, that Google decided it would not update their images from that moment on. Now, about 13 years later, there are several 'street view' providers, and Google decided it is worth another shot. Soon Google will join Apple in providing 360° images once again Link: https://9to5google.com/2023/06/09/google-street-view-germany/ Because of the situation in Russia with the Wagner group marching towards Moscow, I was monitoring the situation as it unfolded. That also meant there was less time to fill this episode. But that also gave me the idea to share the free tools I used to get some very basic monitoring up and running, mostly to feed my personal curiosity. So let's dive into what I used to keep tabs on the news. Site: LiveUAMap One of the sites out there, that are constantly monitoring situations in the world is of course the Live UA Map. This service is constantly scraping and pulling in data, processing it, and will plot specific events that have a specific location, on the map. This has been an important tool for a lot of people already since 2014, and this was one of the first things I opened. Important events, mapped out for your convenience Link: https://russia.liveuamap.com Tip: Telegram to RSS But since I was not completely happy running LiveUAMap alone, because not all messages I want to check have a location, and thus not always show up there. I could have manually checked a bunch of Telegram channels, but why do that if you can automate it using an RSS feed? The first thing I needed to do, was to create several feeds for the Telegram channels I was interested in. For that, I used a service of 'RSSHub' and I didn't even need an account. Any Telegram channel, that has the 'web preview' function available can be added. That means, it is possible to view the channel with a URL that starts with: https://t.me/s/ After this, you take the channel name, and add it to the RSSHub url that will convert it to an RSS feed for further processing. For instance with the Moscowmap channel: https://rsshub.app/telegram/channel/moscowmap Site: Feed Informer After I collected a bunch of Telegram channels, I could have added them all to an RSS feed, and leave it at that. But I wanted to be able to read it in English, since I don't read Cyrillic, so I wanted to have the messages translated using the bilt-in Chrome translator. So I jumped over to Feed Informer, and added the Telegram feeds with the tip mentioned above, to one single feed. Building one stream of RSS items I then exported this feed to HTML code, so I was able to host it somewhere out there, but you can also directly open the HTML page that Feed Informer creates. I wanted to automate things even more, so I added a 1-minute refresh to the page, and near-live updates of the latest 50 messages would be shown in my browser. Hosted RSS feed with the latest news Link: http://feed.informer.com Tip: Twitter Monitoring Of course the monitoring wouldn't be complete just using the LiveUAMap and Telegram channels alone. Lots of information was published on Twitter, including geolocations and verifications, so I also wanted to monitor that. And there are two main ways to do this, and I used both for this. First, there is the 'Twitter List' function, where you are able to add accounts to a 'list'. You can then open just that one list with messages from only those accounts. Second, there is of course the wonderful TweetDeck. You can add the Twitter list to that, but you are also able to create custom search queries, so that you are able to group different topics in different columns. Using TweetDeck for monitoring Twitter Tip: Final Thoughts Since I was the only one checking these sources, there was a limit to the amount of messages I was able to read and process. So by picking Telegram channels that were at the time most important to the situation, and Twitter accounts that had a solid reputation and provided information that was published later in reputable news sources, I collected about 20 to 25 accounts in total to monitor. This provided me with a steady stream of messages that was possible for me to digest, and not overwhelm me. Did I maybe miss some smaller events that happened? Probably. But with several Twitter accounts, and different official and non-official Telegram channels, I had a wide spread of news messages coming in. With events like this, it is very easy to quickly set up some type of monitoring. When you have your sources picked, you can have a steady stream of news coming in within mere minutes. You can check all these sources by hand, spending time switching back and forth. You may even be reading the same messages twice if you are not paying attention. But in this way, you are able to keep things coming in nice and clean, with only a browser opened on TweetDeck and a custom RSS feed. FUNINT: This Week's Meme I usually refrain from any political news, or touch on recent events, because I want to focus on sharing tools, tips and tricks. But after spending a Friday night and a full Saturday watching the news unfold, I simply couldn't resist... Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/1/3/b/d/5/13bd576a96231bb307e561a85f419cf0467f9598-2325-apple-maps.jpg","https://sector035.nl/user/pages/articles/2023-25/2325-daan2k.jpg","https://sector035.nl/user/pages/articles/2023-25/2325-feedinformer.jpg","https://sector035.nl/user/pages/articles/2023-25/2325-feedinformer2.jpg","https://sector035.nl/user/pages/articles/2023-25/2325-liveuamap.jpg","https://sector035.nl/user/pages/articles/2023-25/2325-meme.jpg","https://sector035.nl/user/pages/articles/2023-25/2325-tweetdeck.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_e01844337911_0.jpg","blog_data/images/blog_e01844337911_1.jpg","blog_data/images/blog_e01844337911_2.jpg","blog_data/images/blog_e01844337911_3.jpg","blog_data/images/blog_e01844337911_4.jpg","blog_data/images/blog_e01844337911_5.jpg","blog_data/images/blog_e01844337911_6.jpg","blog_data/images/blog_e01844337911_7.bin","blog_data/images/blog_e01844337911_8.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2023-28","title":"","status":"ok","retrieved_at":"2026-08-29T16:16:11.700841+08:00","text":"Week in OSINT #2023-28 | Sector035 Week in OSINT #2023-28 Home Week in OSINT Articles Search Week in OSINT #2023-28 17th Jul 2023 twitter google search engine geolocation tool analytics overpass turbo Welcome to another Week in OSINT, with some insights into Twitter, a nifty Google trick, an OverPass Turbo tool, and other news. This Monday I have another small update from my side, due to lots of work. I wish I had the time to write longer updates, but maybe it isn't so bad to keep these short. Else all my readers would only be playing with new tools and tricks the whole week, and never be able to have any work done! Anyway, I did manage to dig up a few interesting things I read last week: More on Twitter Google Site Operator GeoPincer Google Analytics 4 Uniform Timezone News: More on Twitter Another blow for researchers that are monitoring Twitter users. Since some time ago there have been some serious issues with the platform. It has been extremely unstable for some period last week. New tweets weren't loading, and I received error messages when I wanted to view a specific tweet. Last week it was even impossible for some time to search on specific tweets with a basic search like: to:sector035 . This has been going on since Musk fired loads of engineers, and it might even get worse in the future. Besides the issues that are the direct result of a lack of engineers, there are also changes that make the platform unusable for researchers. First, there is the issue of rate limiting that stops you from seeing anything more than a few hundred tweets a day. Another issue that I noticed on Sunday, July 9, was that it seemed to be impossible to retrieve a full list of followers or followed accounts. The list only loaded the first few dozen accounts, and then stopped. Was this limited too? Or was this another 'temporary' issue? We actually might never know. Issues in the Twittersphere A third issue that was mentioned early July, was the rumour that Twitter stopped Google indexing its content. This is actually not true, and it is believed that it might be due to the rate limiting that Google temporarily showed less information. Luckily, Twitter made some changes and things are looking better at the moment, since the most recent tweets are available again in Google ! That also opens up the door for some very basic monitoring, without being logged in. Only a handful of tweets are shown, but it is possible to view the latest content of an account, by setting the User-Agent to a Google bot. Viewing Twitter content anonymously Other positive news is that both Archive.today and the Internet Archive , are able to archive single tweets or profiles. For some time, that was also unavailable , but that is also back! Twitter is still an important resource when it comes to alt-right movements, fake news spreaders, and troll farms. And since the big lay-off over at Twitter, things have been increasingly unstable. Some things seem to have been resolved, other issues require some workaround, but it seems that it will never return to what it was. Make the best of it, and keep on digging! (until you are rate limited, of course...) Tip: Google Site Operator I was having some issues last week with the site: operator in Google, but only when I was logged. No clue what was wrong, but it has actually been solved, and everything works again. But during my searches, I saw a message over on Mastodon by Alex Ștefănescu ( / ), a developer over at OCCRP . Searching specific Facebook profiles This simple Google search can be used to find specific content in a Facebook about section of a profile. Really nice tip from Henk van Ess here, thank you for sharing this! Link: https://gijn.org/2023/06/26/... Tool: GeoPincer One of the handy tools one can use during geolocation, is OverPass Turbo. The query language is not the easiest to learn, but once you get the hang of it, it is really powerful! The Reddit user tholo2k has created a nifty Python script that will query a location, and give a list of specific named 'amenities' that are within a given distance from each other. An awesome little tool, easy to use, and might help a lot of people looking for a specific location. Overpass Turbo just got easy! I did receive an error message when I ran it the first time though. So if you are hitting a wall, maybe try and upgrade the urllib3 and requests . This worked for me: python -m pip install -U urllib3 requests Link: https://github.com/tloja/GeoPincer Article: Google Analytics 4 Google Analytics as we know it, is no longer... Of course, there are still a lot of websites that haven't transitioned to the new 'GA4', and you can still find connections using the already known tools. And a legacy UA-ID is still possible, according to Google. But the new analytics, or 'Google Tags', are quite confusing. In this article by Craig Silverman ( / ), everything you need to know, including some tips for future investigations. One thing that doesn't change, is de-anonymising dedicated servers by searching for specific analytics codes Searching for the GTM-tag over at BuiltWith Link: https://digitalinvestigations.substack.com/... Tool: Uniform Timezone Bellingcat created a new browser extension for Chrome, called 'Uniform Timezone'. After installing, and reloading a Twitter of TikTok page, you can hover over any time mentioned on that page. It will then tell you the time in different formats in a small floating information box. A simple click on any of the values will copy that value to the clipboard, and you can also set a custom time zone if you have a need for that. Wonderful, and simple, tool for Chrome that surely will come in handy! Thanks swedishmike for sharing that! Chrome extension in action Link: https://github.com/bellingcat/uniform-timezone Link: Chrome extension FUNINT: This Week's Meme This week, I focus again on Twitter, the ongoing changes and stability of the platform. This platform just keeps on giving! PS: I think that it's about time that Chad Warner adds \"FUNINT\" to his list of disciplines too: Funny intelligence. Involves gathering enough data on the current landscape of OSINT, its process, or the tools used, to make fun of it. Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/a/3/1/6/9/a316935ccdfb4610948db4c2c8758dcd0603b226-2328-geopincer.jpg","https://sector035.nl/user/pages/articles/2023-28/2328-funint.jpg","https://sector035.nl/user/pages/articles/2023-28/2328-google-site.jpg","https://sector035.nl/user/pages/articles/2023-28/2328-nyt-ga4.jpg","https://sector035.nl/user/pages/articles/2023-28/2328-twitter-anon.jpg","https://sector035.nl/user/pages/articles/2023-28/2328-twitter-followers.jpg","https://sector035.nl/user/pages/articles/2023-28/2328-uniform-time.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_92e0fda8fc06_0.jpg","blog_data/images/blog_92e0fda8fc06_1.jpg","blog_data/images/blog_92e0fda8fc06_2.jpg","blog_data/images/blog_92e0fda8fc06_3.jpg","blog_data/images/blog_92e0fda8fc06_4.jpg","blog_data/images/blog_92e0fda8fc06_5.jpg","blog_data/images/blog_92e0fda8fc06_6.jpg","blog_data/images/blog_92e0fda8fc06_7.bin","blog_data/images/blog_92e0fda8fc06_8.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2023-49","title":"","status":"ok","retrieved_at":"2026-08-29T16:15:48.283203+08:00","text":"Week in OSINT #2023-49 | Sector035 Week in OSINT #2023-49 Home Week in OSINT Articles Search Week in OSINT #2023-49 11th Dec 2023 maps geolocation podcast tutorial ctf tool training Another week, another episode with podcasts, people, tutorials and training! This weekend was a bit more busy than I anticipated, so I didn't have enough time to finish this week's episode in time. But I still wanted to publish it, since I found some interesting things last week I really wanted to share. So today it didn't appear on 8AM Central European Time, as usual, but slightly later. Without further ado, I present to you this week's topics: Goodbye Podcast Sourcing Games Craig Silverman PeakVisor Sitemaps News: Goodbye Podcast In the paragraph below, I wrote that the podcast came to an end. Someone did point out, rightly so, that it needs some extra nuance. I quote: \" I would never say the podcast will not return, as I get bored easily. I will say that it is on an indefinite \"hiatus”. Maybe it will become something completely different. Stay tuned and stay subscribed. \" It has been a few months ago already, but I do want to start this week with a personal thank you to Michael Bazzell [ ]. Over the years, he has created hundreds of episodes of his 'Privacy, Security, and OSINT Show', but it has come to an end last month. Thank you so much for sharing all your knowledge and insight with the community. For the hours of listening pleasure, the tips and privacy tools you use. And even though you don't see the point of having an eternal archive, I secretly hope that one day you will find a good solution to host all the episodes again. Farewell to an amazing podcast Link: https://inteltechniques.com/blog/... Training: Sourcing Games If you have some time off during the upcoming holiday season, for whatever reason, this is the thing for you! Several weeks ago, Jan Tegze [ ] shared three (!) new levels over on 'Sourcing games'. I love such games, because the techniques needed to answer the questions, have real-world applications. Thank you, Jan, for the constant updates! Diving into #39 Link: https://sourcing.games/game-39 Link: https://sourcing.games/game-40 Link: https://sourcing.games/game-41 Media: Craig Silverman Craig Silverman [ ] was invited by the NeedleStack [ ] crew to talk about investigative journalism, disinformation on social media, open source intelligence and more! And if you haven't subscribed to this podcast yet, I do suggest you do so right away Craig Silverman on NeedleStack Podcast: https://pod.link/1600516532/episode/... YouTube: https://www.youtube.com/watch?v=Oa_Uea810-0 Tutorial: PeakVisor Sophie Tedling [ ], tech fellow at Bellingcat [ ], created a two-part series on PeakVisor, one of the best mountaineering tools out there. The online tool enables you to view what hills and mountains look like, from any point on earth. In this series, she explains exactly how it works, how to use it, and how it compares to Google Earth's 3D view. First part of PeakVisor for OSINV YouTube: Part 1 YouTube: Part 2 Tutorial: Sitemaps Cyb_detective [ ] has been busy lately, downloading my site content. The reason for that is, to write a tutorial about how to create sitemaps, and download every single link from a website. In the tutorial a small Python script is shown that will generate a list of links. Besides that, other tools are mentioned too, to scrape websites for further analysis. Scraping links with Python Link: https://publication.osintambition.org/... FUNINT: This Week's Meme Thank you for all the years you have created your podcast! The community truly respects all the work you've put in, and we wish you all the best with your future plans. Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/e/3/8/4/c/e384ccfba00f8652a271f9b8ac552b91df8c637c-2349-sitemaps.jpg","https://sector035.nl/user/pages/articles/2023-49/2349-bazzell-podcast.jpg","https://sector035.nl/user/pages/articles/2023-49/2349-meme-bazzell.jpg","https://sector035.nl/user/pages/articles/2023-49/2349-sourcing-games.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_a9433beb4445_0.jpg","blog_data/images/blog_a9433beb4445_1.jpg","blog_data/images/blog_a9433beb4445_2.jpg","blog_data/images/blog_a9433beb4445_3.jpg","blog_data/images/blog_a9433beb4445_4.bin","blog_data/images/blog_a9433beb4445_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2024-22","title":"","status":"ok","retrieved_at":"2026-08-29T16:15:29.655721+08:00","text":"Week in OSINT #2024-22 | Sector035 Week in OSINT #2024-22 Home Week in OSINT Articles Search Week in OSINT #2024-22 3rd Jun 2024 google geolocation extension training interview Besides the usual interview, exercise and geolocation article, I need to address an important situation regarding the future of Chrome extensions This week a major part of this episode has to do with an important change that is coming up, the phase-out of older extensions, due to major changes within the Chromium based browsers. I have taken it upon myself to start creating a list of extensions that might stop working once this change is pushed, and a link to that list can be found here . Overview Sofia Santos' #27 Hunted's Hickman Geolocating a Gang Leader Phase-out of Manifest V2 Training: Sofia Santos' #27 Sofia Santos [ ] created yet another OSINT exercise, and it is number 27 already! This one is for the beginners within the field of open source investigations, and can be solved rather easily with the right searches. What I love about these exercises, is that she mentions how difficult the questions are for beginners, and for seasoned investigators. And to check your findings, she also posts a 'walkthrough' on YouTube right away, explaining how it can be solved. This way you learn how the thought process within open source investigations work, and can learn how to pivot from one finding to another. From easy to hard, something for everyone Link: https://gralhix.com/osint-exercise-027/ Media: Hunted's Hickman The show Hunted has been running for several years in the UK and other countries. Even though a lot of the techniques used are sped up for the show, all required legal paperwork is removed, and based on the Dutch episodes I saw some years ago, legal warrants are given fairly easily. But still, a lot of the techniques portrayed in the show are real. In that way, it does give a good insight in how law enforcement, or investigative bureaus work. In this interview, Daisy Hickman [ ] is being interviewed on Baker's Chatcast about her career, and her experiences in Hunted. Talking Hunted, and touching on OSINT within the show Link: https://www.youtube.com/watch?v=nups_uNcx6Y Article: Geolocating a Gang Leader Benjamin Strick [ ] has been scrutinizing a CCN interview with a Haitian gang leader, and has been able to find the exact location where the interview took place. Even though the location might have been known by law enforcement already, the article shows how he worked, step-by-step, to find the actual house. And since Haiti doesn't have street view, nor does it have a lot of third party captured imagery, most will have to be done via satellite imagery. Another great example how geolocation of video or images can be done, with some basic tools, and enough perseverance. Drawing by Ben, after scrutinizing the video Link: https://link.medium.com/OQvjy7na4Jb News: Phase-out of Manifest V2 An important change within Chromium based browsers is about to start very soon, the phase-out of the so-called \"Manifest V2\" extensions. A manifest is a framework for extensions, and has been in use for many years already, despite some security issues that could occur due to its nature. The V3 is already active, and is in use by a lot of extensions already, but this might change very soon. One of the biggest changes could be that ad-blockers won't be as effective, due to the fact that updates in the list of domains will go through the Chrome web store, and have to be approved first, while it now is done by the extension itself in the background, sometimes several times a day. But there are also other Examples of Chromium based extensions that still use Manifest 2, and that I have installed myself, are: GHunt Companion JSON Viewer Map Switcher OldTweetdeck Tampermonkey uBlock Origin User-Agent Switcher and Manager As you can see, there are some well known extensions on that list, and it is very well possible that certain extensions will stop working all together in the near future. This means that new extensions will have to be developed, workarounds need to be found, or maybe even switch to a different browser. One possibility is to test out Thorium . There has been requests to keep the support for Manifest V2 for several years within the Thorium community, and the developer has mentioned more than once he will do his best to delay the phase-out as long as possible, until the code is fully removed from Chromium. Brave Browser isn't a solution either, since they will also start implementing the change very soon. The only advantage with the Brave Browser is, that they have their built-in Ad Blocker. But if blocking advertisements is your only concern, you might as well look at completely different options , in my opinion! So what will this mean for open source investigators, that rely heavily on extensions within their browser? Well, you can always switch to Firefox, because after some quick searching, I have found no mention of Firefox dropping the support of Manifest V2. The only problem is, that Hunchly will not work in Firefox , so if you really need Hunchly, you are out of luck and might need to use two separate browsers, and only capture half the pages you visit. While writing this section, I did some checking, but life of course take unexpected turns, so I spent half a day cleaning up the kitchen after a blocked drain. But when I went over some notes, I did find some positive news after all. Because it seems that the beta version of Tampermonkey runs okay with some user scripts that I have installed. And within the release notes of Chrome 124 Enterprise and Education, I read that another beta version, of a User-Agent Switcher , is also update to Manifest V3. It is still possible that certain extensions will break, or stop working, but For now, I will be actively looking for solutions, or replacement extensions, to fill certain gaps. Do feel free to share good alternatives for browsers, or extensions, with the community so we can help each other out! Link: List with extensions . Link: https://blog.chromium.org/2024/05/... FUNINT: This Week's Meme I already added the meme for this week, well before I remembered I needed to add a section about the disappearance of Manifest V2 from Chrome... Not sure whether the outcome will be as catastrophic as this meme depicts, but I guess we'll find out! Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/d/c/0/7/7/dc077c3163c8782d3db1c0fd5da1b67929345ee9-2422-sofia.jpg","https://sector035.nl/user/pages/articles/2024-22/2422-canva-drawing.jpg","https://sector035.nl/user/pages/articles/2024-22/2422-meme.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_039dd670b506_0.jpg","blog_data/images/blog_039dd670b506_1.jpg","blog_data/images/blog_039dd670b506_2.jpg","blog_data/images/blog_039dd670b506_3.bin","blog_data/images/blog_039dd670b506_4.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2024-23","title":"","status":"ok","retrieved_at":"2026-08-29T16:15:19.02577+08:00","text":"Week in OSINT #2024-23 | Sector035 Week in OSINT #2024-23 Home Week in OSINT Articles Search Week in OSINT #2024-23 10th Jun 2024 google geolocation Your weekly dose of OSINT news brings you some more UDM options, Sofia and Shadows, and we'll look at some creepypasta! This week I looked at some more Google parameters, and the rest is filled with the topic of geolocation. So if you love playing the Quiztime challenges, and want to get better at it, then this episode of Week in #OSINT is for you! Here is this week's overview: Google UDM Sofia's Stage Talk Backrooms ShadowFinder Finding Sofia Tip: Google UDM Two weeks ago, I wrote about the discovery of the udm=14 parameter value within the Google searches, and how it can be used to strip the AI generated content, and Google adds. Some time after, Irina Shamaeva [ ] took it upon her to play around with other possible values, and it seems there are more options available for this parameter. And looking at the discovery that the URL parameter udm=7 is for videos, and is actually redirecting to tbm=vid , I had a look at that new parameter myself. After I did some testing, I found an old thread over at Stackexchange, listing a lot of options. of which the following ones are still working today: Parameter Result tbm=bks Books tbm=isch Google images (redirect to udm=2) tbm=nws Google news tbm=pts Google Patents tbm=shop Shopping tbm=vid Videos tbm=fin Financial tbm=map Downloads Google Maps JSON These parameters can be used to search Google directly, for instance: https://www.google.com/search?tbm=fin&q=facebook This link will direct you to the current price of Meta Platforms Inc over at Nasdaq, powered by Google Finance. Of course the question is: What else is there to discover? What other parameters are out there? And are there any that can help create more targeted searches, and therefore maybe create better search results? I know these options have been around for quite some time, but it is always great to explore. Link: https://booleanstrings.com/2024/06/05/... Media: Sofia's Stage Talk This week, Bellingcat [ ] is featured twice, but Sofia Santos [ ] also makes two appearances in this week's Week in #OSINT! This time with an interview over at Bellingcat's Stage talk. She talks about how she got into OSINT, how she found a job at CIR [ ] and of course about the importance of mental health. A great interview with Sofia, who is mostly known for her challenges, but also does an awesome job combatting crimes against humanity. Sofia's interview over at Soundcloud Link: https://soundcloud.com/bellingcat/... Media: Backrooms On the internet people are known to leave images or messages, that start to lead their own life, of which some turn into a creepypasta . Once in a while something is posted that has an impact, and have people stunned for years on end, not knowing what to do with it. It becomes a meme within its own right, until someone steps up and solves the riddle. This is such a story, the story of the so called backrooms . And while the original image was found in 2019 already , by Twitter user rkfg_me , it stayed unnoticed until Farrell McGuire [ ] posted a video on YouTube about it. An interesting search, that solves on of the many mysteries that exist on the internet. Thank you, Ben Heubl [ ] for the tip! The background story, and resolution, of the original 'backroom' Link: https://www.youtube.com/watch?v=-1EKIIM3ShI Tool: ShadowFinder Galen Reich [ ] and Gabòr Friesen [ ] created a tool over at the Bellingcat GitHub, that can help find a possible location, by using date and time information, together with a measured shadow. Rummaging through my personal photos, I found one and made an educated estimate of the length of the shadow, to give it a test drive myself too. After filling in all the details in the Google Colab project, like the exact date and time, and the object height and shadow length, it will give you all locations where the information provided could exist. This tool has a very specific 'niche', but there are absolutely circumstances where it can come in very handy. And to show how the tool works, they chatted with Georainbolt [ ], to hear what he thinks. Georainbolt talking with the developers of the tool Link: https://github.com/bellingcat/ShadowFinder Video: https://www.youtube.com/watch?v=pQIjDPFgdJA Media: Finding Sofia And what a treat I have for you this week! Because both Georainbolt [ ] and Sofia Santos [ ] are featured again! And this time Trevor is solving exercise number 19 , that only consists of text! Great to see his thought process, and how he takes notes, while going over the different clues. If you want to have a crack at it yourself, then I would suggest you do that. I can absolutely be solved, even after being online for about a year. Solving Sofia's exercise #19 Link: https://www.youtube.com/watch?v=Eg3Ztsw5FS4 FUNINT: This Week's Meme Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/user/pages/articles/2024-23/2423-meme.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_b8c6227065bf_0.jpg","blog_data/images/blog_b8c6227065bf_1.bin","blog_data/images/blog_b8c6227065bf_2.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2024-25","title":"","status":"ok","retrieved_at":"2026-08-29T16:14:56.820002+08:00","text":"Week in OSINT #2024-25 | Sector035 Week in OSINT #2024-25 Home Week in OSINT Articles Search Week in OSINT #2024-25 24th Jun 2024 twitter search engine book geolocation extremism podcast From search tools to Skip, and from X to extreme, another episode with some interesting topics from the world of OSINT I do strive to push an episode out whenever I am able to, but that doesn't always work, but I am back! So after skipping week 24, I found some interesting content that I wanted to share with you all. And one of the most interesting things, is an enormous read in the shape of a book that was published some time ago. Because open source intelligence, or investigations, do not rely on tools, but on deep understanding of the topic and platforms you are researching. But as usual, I have several items in this week's episode, covering a wide range of topics: NeedleStack with Skip Gaming and Extremism Search Tools Twitter/X Nonsense Josemonkey Media: NeedleStack with Skip Skip Schiphorst [ ] was a guest at the NeedleStack [ ] podcast, where he talks about investigating content in other languages, like Chinese and Arabic. Skip talks about his past and how he was asked to develop a course at one day. But he also talks about translating texts with basic tools with Google Lens and Google Translate, but also how certain nuances might be missed if someone isn't a native speaker. Another great NeedleStack episode, that will give you a great listen during your commute. NeedleStack's Spotify, with Skip Schiphorst Link: https://pod.link/1600516532/episode/... Media: Gaming and Extremism Gaming platforms have been used to share propaganda or certain insights for several years now, and Linda Schlegel [ ] and Rachel Kowert [ ] have collected information that give more insight into the world of extremists, and how gaming platforms are used to spread hate, harass people, or push a specific ideology. This book is not something that is a quick read, with over 200 pages filled with how platforms are used to spread these messages, to how companies try to detect, deter or counter extremism within their platforms or games. With hundreds of footnotes and references, it contains a lot of study material, and if you work with investigating gaming platforms within your field of work, then I highly recommend this read. And the best thing of all is, that it is published under a Creative Commons license. Thank you Ismael Alvarez [ ] for sharing this interesting book! Image taken from the cover of this book Link: https://www.taylorfrancis.com/books/... Link to Related publications over at Academia.edu Links: Search Tools This set of links by intel0logist [ ] has been online for several years already, but only recently I found it in Ritu Gill's [ ] OSINT roundup newsletter. It contains over 250 URLs to search engines, extensions and add-ons, databases and other related sites. This is a lovely treasure trove for people that are looking for a niche search engine for their investigation. Huge list of search tools Link: https://start.me/p/nRADzL/advanced-search-tools Tip: Twitter/X Nonsense Another tip by Ritu Gill's [ ] newsletter, about how to clean up your Twitter/X timeline. It seems that within the topics and interests that you 'follow', are not inline with what you are truly interested in, and in my case especially the 'interests' are totally unrelated to my content, what I like, the people I follow, and so on. It seems to me that Twitter/X is pushing these interests to generate some more revenue by showing as many ads as possible. The platform itself has been getting worse the last few months, is being swarmed with bots, scams and spam, and this is just another nail on their unescapable coffin, in my opinion. Loads of crappy interests forced upon you by Twitter Find all the interests within your Privacy and Safety settings, under Content you see . The so-called \"interests\", are just a long list of keywords and types, but the most interesting one is the \"Topics\", that might contain terms you have seen showing up in your timeline, that you have no interest in whatsoever. Media: Josemonkey While browsing the internet for some interesting content, I found the YouTube channel of josemonkey [ ], where he is finding people that want to be found. People can tag him in a post where they share a video, asking him to geolocate them. In his YouTube videos he responds with an explanation on how he was able to use the visual clues to find the exact location people were when they created their quest. Another really nice channel that give more insight into how geolocation works, and what techniques can be used to find a specific location. Josemonkey tackling Texan Texaco's Link: https://www.youtube.com/@josemonkey FUNINT: This Week's Meme Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/b/d/5/b/e/bd5bec386fa15d06dd2ec0cafca271919b60ee05-2425-gaming-extremism.jpg","https://sector035.nl/user/pages/articles/2024-25/2425-meme.jpg","https://sector035.nl/user/pages/articles/2024-25/2425-searchtools.jpg","https://sector035.nl/user/pages/articles/2024-25/2425-twitter-interests.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_d8484dc1535d_0.jpg","blog_data/images/blog_d8484dc1535d_1.jpg","blog_data/images/blog_d8484dc1535d_2.jpg","blog_data/images/blog_d8484dc1535d_3.jpg","blog_data/images/blog_d8484dc1535d_4.bin","blog_data/images/blog_d8484dc1535d_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2024-27","title":"","status":"ok","retrieved_at":"2026-08-29T16:14:33.552938+08:00","text":"Week in OSINT #2024-27 | Sector035 Week in OSINT #2024-27 Home Week in OSINT Articles Search Week in OSINT #2024-27 8th Jul 2024 book geolocation opsec overpass turbo osint osm ai This week another small update from the world of open source investigations, with some free reading material to start with! This week I start off with a free book, put together by researchers, that show the importance of open source information and investigation techniques. I haven't been able to read it in full yet, but I do encourage you to check it out and bookmark it for future reference. Further more I touch on the subject of AI, large language models, and how they are slowly shaping the world of investigations: OSINT book AI & OSINT Earthkit OpSec Tip Tip: OSINT book The book \"Open Source Investigations in the Age of Google\" isn't just any book about open source investigations that teaches you the ropes, but is a collection of chapters written by different authors. They contain case studies, go into detail about the role of open source investigations within the intelligence community or journalism, and show how it can be used to track human rights violations or nuclear weapons development. The publication is free to read online, and contains a wealth of information, also within the abundance of footnotes that are available. Thank you Dr. Olamide Samuel [ ] for sharing this on X! Another must-read Link: https://www.worldscientific.com/worldscibooks/... Article: AI & OSINT This article touches on the subject of where AI and LLM's can be beneficial within the world of open source investigations. Several years ago the techniques weren't really ready yet, but the rapid development of large language models, training sets and new algorithms, make it that the world of open source intelligence is shifting. Matt Edmondson [ ] described in what areas computers can help us out nowadays, and if we are able to solve crimes faster due to this, while still being able to independently verify the outcome, I am all for it! You now how hard it is to find a suitable image? Link: https://thehackernews.com/2024/07/... Tool: Earthkit Several weeks ago I was sent a link to the GitHub repo of \"earthkit\", after which I tried to get it up and running locally. I didn't have enough time to solve some bugs I encountered, and I left it for what it was. But when Cyb_detective [ ] mentioned it again last week, accompanied by a web-based version, I had to play with it again! This is a one-stop solution for geolocation tasks, and while it isn't perfect yet, it will be more than able to help you in some of the more tougher investigations out there, or get you somewhat close to a possible area. A really awesome tool that can only improve. Thank you Jett Chen [ ] for all your work! Using GeoCLIP to guestimate an easy Quiztime challenge GitHub: https://github.com/JettChenT/earthkit Link: https://earthkit.app Tip: OpSec Tip A quick tip from Sinwindie [ ], about active investigation techniques that use pass resets to find information. It may seem harmless on your end, but have you tried these techniques on your own accounts recently? Have you checked that the target isn't being notified about it? Online platforms may change their policies about this overnight, and all of a sudden your seemingly harmless investigative technique can spook a high-value target. Be careful out there, stay passive, stay hidden... Stay passive! Link: https://www.youtube.com/watch?v=bQQxTbsrUKM FUNINT: This Week's Meme Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/6/2/c/8/4/62c8479ee2a1b5c272ffe1b3158edc6a30bf9dac-2427-investigate.jpg","https://sector035.nl/user/pages/articles/2024-27/2427-earthkit.jpg","https://sector035.nl/user/pages/articles/2024-27/2427-meme.jpg","https://sector035.nl/user/pages/articles/2024-27/2427-osintbook.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_3313f8663bc5_0.jpg","blog_data/images/blog_3313f8663bc5_1.jpg","blog_data/images/blog_3313f8663bc5_2.jpg","blog_data/images/blog_3313f8663bc5_3.jpg","blog_data/images/blog_3313f8663bc5_4.bin","blog_data/images/blog_3313f8663bc5_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:apr_2024","title":"April 2024","status":"ok","retrieved_at":"2026-08-29T16:18:43.196053+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 29th Apr 2024 Week in OSINT #2024-17 This week's episode of WiO covers topics from cruise ships to custom search, and from sins to secrets! Now that I've got the very cheesy alliteration covered, it's time to write the intro for this week's episode. As usual, this is done in the early morning, when everything around me is still quite... maps google podcast custom search engine osint maritime 22nd Apr 2024 Week in OSINT #2024-16 Another Monday with some interesting tips from the world of open source intelligence and investigations This week I have some more interesting tools, links and media for you, part of it from some of my own research I have been doing while building a new virtual machine. And while I was thinking ab... youtube podcast extension tutorial tool 15th Apr 2024 Week in OSINT #2024-15 From videos to visualisations, companies to communities, and from tips to tools! Maybe all of it is in this week's episode, but I mainly love alliterations... Time flies when you're having fun, or when you are busy studying, like I was... But this week I am back with another 'normal' episode of We... cryptocurrency bookmarks social media factchecking corporate intelligence business intel osint training 8th Apr 2024 Week in OSINT #2024-14 A short update from the world of OSINT, with some nifty mapping tools and tips by me, some profile photos and another source of news! I am still rather busy, and didn't have time to write a full-on update from the last few weeks. But I did want to share a few interesting things I read or used myse... maps google social media osint Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/1/4/c/d/8/14cd89b826ff0b52e1ff0593cfab6989b1e68fd2-2415-deckblue.jpg","https://sector035.nl/images/1/f/8/2/9/1f829fbc69822b5b3d854fc8fd0f04495bff36b0-2417-cruisemapper.jpg","https://sector035.nl/images/3/2/f/f/2/32ff261b8063c396a2d0c593327179bc32edd030-2416-truckparkings.jpg","https://sector035.nl/images/f/3/0/d/1/f30d1a897adf80224612b84e3ed5514ed3d49d31-2414-grid.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_313c589aab9d_0.jpg","blog_data/images/blog_313c589aab9d_1.jpg","blog_data/images/blog_313c589aab9d_2.jpg","blog_data/images/blog_313c589aab9d_3.jpg","blog_data/images/blog_313c589aab9d_4.bin","blog_data/images/blog_313c589aab9d_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:aug_2024","title":"August 2024","status":"ok","retrieved_at":"2026-08-29T16:17:35.114915+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 5th Aug 2024 Week in OSINT #2024-31 This week I have a small update from the world of OSINT for you, and am taking a small break for a few weeks! It is time for me to take a little break again, like I usually do every year around July or August, and it comes at a great time. The last few weeks I have sometimes struggled to find suit... privacy bookmarklet podcast extension phone numbers Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/4/0/1/1/8/40118aef4fa9e9fec4019f0f9d9e2588c70cc5df-2431-osintlytics.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_e56bd5a4a7e5_0.jpg","blog_data/images/blog_e56bd5a4a7e5_1.bin","blog_data/images/blog_e56bd5a4a7e5_2.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:dec_2023","title":"December 2023","status":"ok","retrieved_at":"2026-08-29T16:19:51.319698+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 18th Dec 2023 Week in OSINT #2023-50 Christmas is getting close, and this will be the last episode of this year! But I've got some interesting content for you! Every year around the December holidays I take some time off. And even though I have taken several breaks this year, due to an extremely busy schedule, I am going to take anot... domains whois podcast extension phone numbers training 11th Dec 2023 Week in OSINT #2023-49 Another week, another episode with podcasts, people, tutorials and training! This weekend was a bit more busy than I anticipated, so I didn't have enough time to finish this week's episode in time. But I still wanted to publish it, since I found some interesting things last week I really wanted to... maps geolocation podcast tutorial ctf tool training 4th Dec 2023 Week in OSINT #2023-48 In this episode of Week in OSINT, I have some nice tutorials, an advent calendar, links and the weekly meme! Another Monday, another episode of Week in OSINT is here! Some really nice topics to cover, and of course I will try to keep the new tradition of featuring a weekly meme in my episodes! ... google bookmarks social media ctf reverse image search users Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/7/d/e/8/9/7de8980acf75e8b4ec4e232b69b1b73cf445dd82-2349-sitemaps.jpg","https://sector035.nl/images/8/7/4/3/0/874301e75646683cb31f8cfe1f225242693f8e54-2350-theseint.jpg","https://sector035.nl/images/8/8/f/1/4/88f1422f2d20ace56de3a4df80335bde1d73abd6-2348-advent.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_203206e5f992_0.jpg","blog_data/images/blog_203206e5f992_1.jpg","blog_data/images/blog_203206e5f992_2.jpg","blog_data/images/blog_203206e5f992_3.bin","blog_data/images/blog_203206e5f992_4.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:dec_2024","title":"December 2024","status":"ok","retrieved_at":"2026-08-29T16:17:13.871434+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 2nd Dec 2024 Lake Constance - Geolocation It has taken well over 7 years before this geolocation challenge was resolved, and I have spent countless hours on trying to find this years ago. Sadly enough, work and other priorities had taken over my life, so the last three years I didn't have time to look at it at all. Until recently, when I ma... maps geolocation quiztime aerial imagery Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/8/8/6/7/d/8867d4106d890f7d5545af85c3dc7b027e46e557-tweet-countrytec-2017-07-24.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_54129e987971_0.jpg","blog_data/images/blog_54129e987971_1.bin","blog_data/images/blog_54129e987971_2.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:feb_2024","title":"February 2024","status":"ok","retrieved_at":"2026-08-29T16:19:19.893034+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 19th Feb 2024 Week in OSINT #2024-07 This week I have a very short update again, but I am very pleased with the little tips that I found for you! As stated in episode 2024-04 , I am very busy lately, so I don't always have time to write a full length episode. But I did find a little bit of time to share some interesting things that... domains privacy tutorial 12th Feb 2024 Week in OSINT #2024-06 Another Monday, another small recap from the world of OSINT! This week I have some tools, tricks, tips and other topics! Another busy week, with a lot of things happening in the world of OSINT. Due to my busy schedule, I am unable to mention everything, but I did spot some interesting things over... google podcast tool training 5th Feb 2024 Week in OSINT #2024-05 Another short update from the OSINT community, with some news about recent changes, privacy and another challenge by Sophia! The social media landscape is constantly changing, as are the tools we have to our disposal. That is why I always recommend people not to rely solely on tools, but understan... twitter google privacy opsec training Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/0/c/c/2/0/0cc201598e2e4ef1fc66d0a63184734f15c9ac79-2405-sotwe.jpg","https://sector035.nl/images/2/d/6/9/7/2d69751fe8501102a59d4b07534ee2ee50cdda0a-2406-regex.jpg","https://sector035.nl/images/a/6/1/1/6/a61169fbcb100b1edb3ea5754d9ab639b0e6f9af-2407-browser-privacy.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_48dd986907b2_0.jpg","blog_data/images/blog_48dd986907b2_1.jpg","blog_data/images/blog_48dd986907b2_2.jpg","blog_data/images/blog_48dd986907b2_3.bin","blog_data/images/blog_48dd986907b2_4.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:jan_2024","title":"January 2024","status":"ok","retrieved_at":"2026-08-29T16:19:35.606176+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 29th Jan 2024 Week in OSINT #2024-04 Here is another overview of week 4 from the world of OSINT, covering everything from CTFs to DNS and anything in between! Lately I have been extremely busy with an education, and for a couple of weeks things won't really improve. So it is possible that a few of the upcoming episodes are slightly s... google investigation bookmarks social media ctf archive 22nd Jan 2024 Week in OSINT #2024-03 Welcome to the first episode of Week in OSINT of 2024! Here are some interesting articles, tutorials and tips for you! It has been a while since the last episode of Week in OSINT, but after being ill during the holidays, I chose to spend some time on things that are way more important than this we... google podcast bookmarks tutorial methodology maritime Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/0/1/d/f/e/01dfef30c715ad20610f4c091d7c382326a3d979-2403-globalfishingwatch.jpg","https://sector035.nl/images/d/e/7/d/f/de7df8ea62d63d5170173af1f46a73c360fb69f6-2404-hacktoria.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_f0a7c817b8e1_0.jpg","blog_data/images/blog_f0a7c817b8e1_1.jpg","blog_data/images/blog_f0a7c817b8e1_2.bin","blog_data/images/blog_f0a7c817b8e1_3.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:jul_2024","title":"July 2024","status":"ok","retrieved_at":"2026-08-29T16:17:44.215663+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 29th Jul 2024 Week in OSINT #2024-30 Welcome to your OSINT fix of Monday July 29, with some articles, crypto currency, a podcast and a nifty tool! I like to do things 'quick and dirty' if I need something fast, but then I always forget to actually create something for the next time I really need it. And that also gets me to the last... maps privacy cryptocurrency podcast tool osint health 22nd Jul 2024 Week in OSINT #2024-29 Welcome to a short update of week 29 of 2024, where I dive into some interesting posts I found on social media. Last week I had an extremely busy weekend, where I hardly had any spare time for myself, so I really had to skip that one! But slowly we're getting things bak on track, so this week I re... domains whois bookmarks 8th Jul 2024 Week in OSINT #2024-27 This week another small update from the world of open source investigations, with some free reading material to start with! This week I start off with a free book, put together by researchers, that show the importance of open source information and investigation techniques. I haven't been able to... book geolocation opsec overpass turbo osint osm ai 1st Jul 2024 Week in OSINT #2024-26 This week a filled episode, with books and bookmarks, names and Needlestack, training and tweets! This week I spend some extra time to go over social media tracking down all the good stuff out there, and it was quite a lot! I learned a lot again, due to all the tips that people shared online with... twitter book podcast bookmarks archive training methodology Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/0/c/7/d/e/0c7de3c6d5c12a3a4e32844237238016d25bf556-2429-urldna.jpg","https://sector035.nl/images/1/8/5/3/e/1853e5c754fece24b8f73dfbc2d1a558c9c17173-2426-osint-books.jpg","https://sector035.nl/images/2/1/d/6/5/21d657f6593a1ddbaf722d3aa4f4c20fd45362bb-2430-searchgrid.jpg","https://sector035.nl/images/3/3/f/2/5/33f258226d4eda51a3405a7b489c348d9a8f6135-2427-investigate.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_36758270acc3_0.jpg","blog_data/images/blog_36758270acc3_1.jpg","blog_data/images/blog_36758270acc3_2.jpg","blog_data/images/blog_36758270acc3_3.jpg","blog_data/images/blog_36758270acc3_4.bin","blog_data/images/blog_36758270acc3_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:jun_2024","title":"June 2024","status":"ok","retrieved_at":"2026-08-29T16:18:01.170397+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 24th Jun 2024 Week in OSINT #2024-25 From search tools to Skip, and from X to extreme, another episode with some interesting topics from the world of OSINT I do strive to push an episode out whenever I am able to, but that doesn't always work, but I am back! So after skipping week 24, I found some interesting content that I wanted to... twitter search engine book geolocation extremism podcast 10th Jun 2024 Week in OSINT #2024-23 Your weekly dose of OSINT news brings you some more UDM options, Sofia and Shadows, and we'll look at some creepypasta! This week I looked at some more Google parameters, and the rest is filled with the topic of geolocation. So if you love playing the Quiztime challenges, and want to get better... google geolocation 3rd Jun 2024 Manifest V3 This page contains a list of extensions, and their respective Manifest versions. In Week in #OSINT 2024-22 , I wrote about the upcoming changes within the Chromium based browser extensions. This page contains a list of extensions that use the newer Manifest V3, and should be (somewhat) future proof. extension chrome 3rd Jun 2024 Week in OSINT #2024-22 Besides the usual interview, exercise and geolocation article, I need to address an important situation regarding the future of Chrome extensions This week a major part of this episode has to do with an important change that is coming up, the phase-out of older extensions, due to major changes wit... google geolocation extension training interview Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/4/f/f/7/2/4ff726d5841b23418295771deed27b241d118369-2423-georainbolt.jpg","https://sector035.nl/images/a/a/5/1/f/aa51f347d350a700a79c3ee51c781b499983da4a-2422-sofia.jpg","https://sector035.nl/images/e/4/7/e/a/e47eac015520a74a3053321839ac7faf59d7cde8-2425-gaming-extremism.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_cc52eac8321f_0.jpg","blog_data/images/blog_cc52eac8321f_1.jpg","blog_data/images/blog_cc52eac8321f_2.jpg","blog_data/images/blog_cc52eac8321f_3.bin","blog_data/images/blog_cc52eac8321f_4.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:mar_2024","title":"March 2024","status":"ok","retrieved_at":"2026-08-29T16:19:05.164832+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 18th Mar 2024 Week in OSINT #2024-11 Another short update from the world of OSINT, that starts off with a review of a documentary I watched last week. Social media has quite an impact on modern society, and not always in a positive way, as can be seen in the documentary \"Idaho Murders: Trial by TikTok\" that was launched last week. De... google investigation tiktok podcast osint 11th Mar 2024 Week in OSINT #2024-10 Welcome to another very lengthy update from the world of OSINT, with some Google searches, strategy and a hint of Insta and Snaps... One of the things I like about open source intelligence (OSINT) and social media intelligence (SOCMINT), is the fact that there never seems to be a dull moment. Ever... google instagram snapchat methodology network analysis 4th Mar 2024 Week in OSINT #2024-09 [Search Engine Special] This week I've got a special lined up, since it is all focussed on search engines after following the news about a Google bug! The last week or so had one specific theme, namely: Google Search! This episode of Week in OSINT is therefore a special on search engines. Once in a while something breaks... google search engine yandex bing Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/1/1/c/3/8/11c38f6f7fd03b3ac48b7adaf67e2724e24587a1-2409-seosly-bing.jpg","https://sector035.nl/images/6/1/8/4/d/6184dff09a8fcb6042c8fa5807fcb88ac60e3dd4-2411-tiktok-trial.jpg","https://sector035.nl/images/9/c/f/4/f/9cf4f1d432b0b829c8bbb0b8ff69c9a86461c0ac-2410-snapmap.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_0e5f583623cd_0.jpg","blog_data/images/blog_0e5f583623cd_1.jpg","blog_data/images/blog_0e5f583623cd_2.jpg","blog_data/images/blog_0e5f583623cd_3.bin","blog_data/images/blog_0e5f583623cd_4.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:may_2024","title":"May 2024","status":"ok","retrieved_at":"2026-08-29T16:18:19.14432+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 27th May 2024 Week in OSINT #2024-21 This week we'll be looking at the way Google used to look, and how to retrieve that, an old chat app, and more interesting topics. This week's episode of Week in #OSINT almost turned into a special that revolves around 'history'. Whether it is returning to the good old Google, a tool that is alrea... google podcast snapchat osint 20th May 2024 Week in OSINT #2024-20 This week another small collection of news, articles and tips, curated by me, and shared for your Monday morning pleasure. This week was a bit difficult to get the episode out, since I had a rather busy, and somewhat weird schedule last week. After working some odd shifts, and some extra hours, I... maps twitter dark web osint 13th May 2024 Week in OSINT #2024-19 This week a small update due to a very busy weekend. Some content I found online, but this week I also share one of my personal tips! At the end of last week, large parts of the world had the chance to admire a rare event. In large parts of the world the Aurora Borealis and Australis were visible... extension add-on tool telegram phone numbers 6th May 2024 Week in OSINT #2024-18 Another episode with some interesting articles, tools, search engines and of course the ever-present Monday Morning Meme! It has been quite some time that I actually tested a tool in a custom VM, but this week I simply had to give the new Telegram a go. I love this tool a lot, especially since it... google custom search engine telegram sock osint methodology Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/2/4/6/a/1/246a1ca3a990a79835292fe2d598f99966a7c3e5-2421-google2.jpg","https://sector035.nl/images/5/8/a/4/9/58a4900c2b284cecf2deccbbef1c8045f42f90e2-2420-oldtweetdeck.jpg","https://sector035.nl/images/9/7/0/5/4/97054937f1cad56a397415b4704f7131f3ce8f8a-2419-uaswitcher.jpg","https://sector035.nl/images/b/c/7/e/1/bc7e1cadfe70a5122cbbbaa204e5742fb71479bd-2418-cses.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_59788d6128c7_0.jpg","blog_data/images/blog_59788d6128c7_1.jpg","blog_data/images/blog_59788d6128c7_2.jpg","blog_data/images/blog_59788d6128c7_3.jpg","blog_data/images/blog_59788d6128c7_4.bin","blog_data/images/blog_59788d6128c7_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:nov_2023","title":"November 2023","status":"ok","retrieved_at":"2026-08-29T16:20:09.631739+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 27th Nov 2023 Week in OSINT #2023-47 It is another Monday, so I have gathered some interesting content from the world of OSINT for you! Hello Monday, here is another short update with some interesting things I found last week. Another last minute edit here or there, that is why this episode is published slightly later. This is not a... tutorial tool ai 20th Nov 2023 Week in OSINT #2023-46 A very short update, after being away for some weeks! This week, with some 'highlights'... Okay, excuse the pun, those highlights can be found in the first section of this week's episode. A really handy little tool that will absolutely help you on your adventures out there. Talking about adventure... google extension add-on tool Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/1/f/5/3/c/1f53c2128960a94a7071e19512709b313b8979ea-2347-urlhunter.jpg","https://sector035.nl/images/3/b/4/a/9/3b4a9e8368caa4d062756cbe6b71fe66910f253f-2346-forensic-osint1.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_d195042a054a_0.jpg","blog_data/images/blog_d195042a054a_1.jpg","blog_data/images/blog_d195042a054a_2.bin","blog_data/images/blog_d195042a054a_3.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:oct_2024","title":"October 2024","status":"ok","retrieved_at":"2026-08-29T16:17:24.09373+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 19th Oct 2024 About Black Box (CL)OSINT Tools Within the last decade or so I have the feeling that 'OSINT' simply has become a buzzword, and loads of companies and startups want to jump on the bandwagon to try and earn some extra money with it. But with that, I also noticed a very dangerous development within the field of open source intelligen... tool osint methodology Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/6/7/2/0/a/6720a60f8f2d2bc9029558c1433459ee70361229-black-box.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_a76c4cce6c87_0.bin","blog_data/images/blog_a76c4cce6c87_1.bin","blog_data/images/blog_a76c4cce6c87_2.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/chronolocation-of-media","title":"tutorial on chronolocation","status":"ok","retrieved_at":"2026-08-29T16:26:43.360456+08:00","text":"Chronolocation of Media | Sector035 Chronolocation of Media Home Week in OSINT Articles Search Chronolocation of Media 26th Nov 2021 social media metadata investigation chronolocation A comprehensive guide to determining dates and times in (online) media In this article I'll be diving into the world of chronolocation, metadata and shadows. Since this is the largest article I've written so far, I've decided to create a table of contents for your convenience. At the end of every chapter and after long paragraphs, there's a link to bring you back there if you need it. Since I know there will be updates in the future, I also added a document version control, for an easy overview of the changes. Table of Contents Introduction 1.1 Geolocation vs Chronolocation 1.2 Intended Use 1.3 History of the Word Chronolocation Workflow for Chronolocation Metadata in Digital Media 3.1 Interpretation of Metadata Basics of Chronolocation 4.1 Earliest Possible Moment 4.2 Latest Possible Moment 4.3 Possible Time Frame 4.4 Specific Time Looking for Clues 5.1. Construction, Scenery and Landscaping 5.2. Events, Acts and Festivities 5.3. Seasons and Nature 5.4. Other Indicators 5.5. Google Earth Pro Sun Based Chronolocation 6.1. Basic Time Calculation 6.2. Date and Time Calculations Tips and Tricks 7.1. Hard to See Shadows 7.2. Shadows in Different Angles 7.3. ShadowCalculator 7.4. Warnings and Pitfalls Conclusion and Glossary 8.1. Glossary Version control Date Changes 26/11/21 Initial publication articles chronolocation / metadata 1. Introduction I have always been intrigued by the way forensic examiners were able to determine a timestamp for photos or events, without having direct knowledge of it in the first place. Since I became a regular member of the Quiztime community, having done quite a bit of 'geolocation' during those quizzes and some more serious investigations, and more than once there wasn't just the question of where a certain photo or video is shot, but also when it happened. In this guide, I am going to dive a little deeper into the techniques of what is called ‘chronolocation', the act of determining or estimating a time or time frame of an event or situation that was captured by visual media. This article has been in the making for a very long time! It basically started during February 2018 when I was able to determine the possible date and time of a photograph that was posted as one of the daily verification quizzes by the Twitter account Quiztime. Later that same year I spent some evenings on determining the possible date of an extrajudicial execution in Cameroon. After this people started contacting me with questions about the techniques I used, or requests to help in investigations. And so, we end up in early 2019, when I started to write this lengthy tutorial. But due to all kinds of other commitments I've never been able to finish this, until now. The writing of it has been quite a journey I must say! It took me weeks to even get an overview of subjects I wanted to touch. Then multiple weeks of writing things on my personal blog on Medium, followed by transferring it all to a separate document, since it was getting way too big. I planned to release it as a PDF on GitHub, but after I decided to host my own blog things finally took off again. And I finally took the time to transfer everything to here and finally was able to finish it. And when I saw that others, like Nick Waters, were posting little write-ups as well about it, it was time to get to work again. After more endless nights and weeks of working on it in my spare time, I somehow actually was able to finish something I felt comfortable sharing with the world. So here it is… A guide that is probably nowhere near being complete! But as far as I was able to find it is one of the first and maybe the only one of its kind at the moment. 1.1. Geolocation vs Chronolocation When it comes to establishing a time frame, it turns out that both the art of geolocation and chronolocation have similarities. The main difference is that a global indication of the location is needed for chronolocation if we want to be precise. But both techniques demand a thorough investigation of every part of a photo or video, an understanding of the surrounding area, some local knowledge and maybe even the weather. Where for geolocation the knowledge is used to find a possible location, in chronolocation we use that information to narrow down the possible time frame. Besides that, both geolocation and chronolocation can complement each other. Where the knowledge of a precise location can help determine an accurate time frame, a shadow can aid an investigator in geolocation by giving a clue in which direction a photo or video was shot. But it can also be important to determine a time or date to find specific events that happened around that moment in time, to zoom in on possible locations. 1.2. Intended Use The goal of this guide is to give a basic understanding of chronolocation and to share it with everybody who needs to apply the techniques in one form or another. This guide will probably not cover every possible aspect of chronolocation, but I tried to make it as complete as possible. The tips and techniques range from going through source code or extracting metadata, to investigating sceneries depicted in a photo to determine a possible date or time. Everything described in this guide contains common sense, basic physics and other verifiable techniques, but they must be used correctly before they can be admitted as evidence. It is also important to note that when using specific techniques for legal cases, it is advised to have them verified independently before admitting them to a court of law. Furthermore, I intend to make this a living document that will receive a new revision over time when there is enough new information to add. It would be nice if the community of OSINT, GEOINT and other INT's reach out if they feel there are any areas of expertise that should be included. 1.3. History of the Word Chronolocation The word ‘chronolocation' comes from the Greek word 'chronos' (time) and the Latin word ‘locus' or the verb 'locare' for locate. In general, it describes the act of determining the moment something happened. It isn't a well-known word, but it seems it has been used for years already to describe the action of finding a date or time frame. Here is an abstract of ‘Gender and Song in Early Modern England' from 2014 using the same term when it talks about finding the time frame of a scene in the 1992 film ‘Orlando'. Extract from ‘Gender and Song in Early Modern England' by Leslie C. Dunn and Katherine R. Larson. The earliest mention of the word itself I could find takes us back to 1983, to the article 'Australian Sea Levels in the Last 15,000 Years' by David Hopley of the Department of Geography of the James Cook University of North Queensland. So, the word has been in use for quite some time already and due to the upcoming 'citizen journalism' the term is slowly gaining more popularity. To make things a little complicated, the term is used in fiction novels as a term for 'time travelling'. But I won't be touching that subject in this guide, since that is in no way my area of expertise. ↑ Table of Contents 2. Workflow for Chronolocation Geolocation and chronolocation have similarities when it comes to the investigative part of it, as mentioned earlier. Both require certain steps that need to be followed, or at least considered, and, as with any type of investigation, the credibility of the source is important. Since I was unable to find a good workflow for either, I propose the following for chronolocation, which of course can be adopted for geolocation with some adjustments: Proposed workflow for chronolocation of media Since the verification of findings in any kind of investigation is the most important, it is listed multiple times throughout this workflow. In this article, several techniques will be discussed that can be used to determine dates or times. Starting with metadata in digital media, and ending with calculating shadows. Where possible, Quiztime quizzes are used as examples. This Twitter account is a great way to practice your verification skills, and in the past multiple quizzes needed chronolocation techniques to solve a question. ↑ Table of Contents 3. Metadata in Digital Files When media is acquired in a digital form, and a date or time needs to be determined, there are multiple ways of doing so, depending on the file type and the source it came from. First and foremost, it is important to check whether there is extra information inside the original obtained file, the so-called metadata . Within digital media there is usually extra information, which can be acquired by investigators. As an example, we can use a tool that can read the Exif data of a digital photo. Exif stands for 'Exchangeable image file format' and specifies the format of information inside digital images and audio. Some images have an abundance of information, but it is also possible that it is stripped of all the information due to being uploaded to a social media platform. Example of Exif information inside a JPG file, opened in JPEGsnoop Sometimes it is enough to look at the details of digital files from your file explorer to read the metadata, but there are several tools out there that give you some more options. 3.1. Interpretation of Metadata Retrieving timestamps directly from digital files is a good start, but since a few years a lot of social media platforms are stripping the uploaded media from the metadata. Besides that, it is also possible to strip this information manually prior to distribution. And since the metadata inside the Exif tags consists of mostly plaintext data that can be easily changed or erased with easy to use tools, it can be one of the less trusted ways of determining a date or time. There are exceptions, for instance when the file is acquired directly from a trusted source, like a forensic photographer, or a member of a news agency, but in general my personal advice would be to treat Exif data as corroborating information and verify any date and time that is mentioned in a file, by investigating its content. Photos on sites like Flickr, that preserves the Exif information, might look handy since the people uploading it wouldn't have a reason to change the data. But there's another problem on such sites, since there are quite a lot of photos that have incorrect timestamps for the location they show. One of the most common reasons is that people on holidays don't always adjust their camera settings to reflect the local time zone. So be prepared to verify all Exif data within photos from social media sites like Flickr if they need to be used for chronolocation. To prevent such information ending up in your evidence, here's a tip by Christiaan Triebert : Try and contact the source, and verify the clock settings of the device that was used to capture the image or footage. Make a photo of the camera with a clock next to it that shows the current, local, time. This way you have the possibility to adjust timestamps if needed. Besides Flickr and 500px that preserve full Exif information, there are some social media platforms that retain other valuable pieces of information, like the time of uploading. Even though the exact moment of uploading might not seem useful straight away, it can at least give some insight into the latest possible creation date of digital media. There have been instances where people made claims about a certain event, where the footage shown was uploaded months or years earlier, thereby refuting the story. Finding metadata in websites or digital media is a subject that is very important for chronolocation, it’s too wide for the scope of this article. Therefore, I've created a separate guide on this that explains the basics. It shows the usage of simple tools, and how to retrieve information on some popular websites and social media. Click here to go to the chapter ' Metadata in Digital Media ' ↑ Table of Contents 4. Basics of Chronolocation When you have an image or video the chances are that these come from an online source. If so, it always pays off to investigate the metadata that comes with it. If that doesn't contain information that is useful, the next step is to dive into the minute details of the scene to look for clues that can indicate a specific date, time or time frame. Before going into that, let's first have a look at something else, the initial research question. Within chronolocation there are several 'moments' that might be determined, depending on the need of that research question. Finding an exact time is not always possible, and sometimes not even needed. So it's important to determine whether finding the exact date is the goal. Answering that question can save a lot of time. 4.1. Earliest Possible Moment There are times that the research question is along the lines of: \"Is the situation depicted possible, at the moment it was claimed?\". Or maybe the situation calls for debunking a specific claim, where an 'earliest moment in time' is key. In such cases all one needs to do is to determine the earliest possible moment in time for the media that is being researched, because it's not always needed to determine the exact creation date of the media, since verification can be done by determining one parameter. When looking for indications of the earliest possible moment one can look at objects or circumstances that were not present or have changed before the specific date itself. Examples are manufacturing dates of cars, or licence plates that are issued in chronological order. Another example can be the presence of a public transport vehicle that, that matches a specific time or day mentioned in that particular case. Other things to look for are the specific seasons, the local weather or construction work that was done in the area. 4.2. Latest Possible Moment Just as it is possible to have the earliest possible moment, there is also the latest moment that an event has occurred, or the media was created. The research question or purpose is slightly different, but the approach is the same. For this you need to look at things that have changed after the moment in time that is claimed. For instance one can look for new objects after the time of the event, like new road signs or construction work that was finished. Besides new objects, one can also look for things that have been removed after the claimed moment. This can be anything from mowed lawns to a building that was demolished. Anything that can bring down this date can be used to find the latest moment where the situation that is researched could have happened. 4.3. Possible Time Frame When the research question demands that a possible time frame must be established, one can combine the earliest and latest possible moments in time. This can also be used as the basis when trying to determine an exact date and time, since by first limiting the amount of possible dates, it will help to focus on the small details and eventually find the exact day. This is not always an easy task but by going over small details in a photo or video, it's sometimes possible to find enough little clues to narrow down the possible time frame that a specific scene could exist. An example of narrowing down such dates can be read in this write-up of the Quiztime challenge of February 28, 2018 . ↑ Table of Contents 4.4. Specific Time When the exact location is known or determined, it's sometimes possible to calculate a more specific moment in time by using the angle and direction of the sun, if any shadows are visible. We'll have a more in-depth look at these techniques in chapter 6 . Be aware though that there are a few important things to consider when using this technique: The main thing is the exact location on earth. Due to the fact that the angle of the sun near the equator is completely different compared to a location that is further towards the north or south, it can be harder to determine a correct time. Since the earth doesn't move nicely and calm in a circle around the sun, but has an oval shaped path, and even 'wobbles' while it rotates along its own axis, the exact location is important. Around the equator the sun sits high in the sky, moving faster in a horizontal way, but when moving further north or south, the sun is in a more shallow angle towards the horizon, appearing to move more slowly throughout the day. And the movement of the sun isn't only different throughout the day, but also during longer periods. Since locations further away from the equator have a more shallow angle throughout the year, and due to movement of the earth, it can result in less difference in angles at any given time. To illustrate these points, here are two locations, where two moments in time are shown where the direction of the sun is nearly identical: Location: Helsinki, Finland Date Time Azimuth June 22 14:59 215.03 December 31 14:59 215.07 Location: Hurghada, Egypt Date Time Azimuth June 22 12:15 239.98 December 31 16:26 240.03 In Helsinki it's possible to have the same time and azimuth, or 'direction of the sun', on two dates that are months apart. While these parameters change rapidly in Egypt when you jump even one or two weeks back or forth. 4.5. Basic Steps When the research question demands a specific date, it's best to start with a rough time frame and narrow that down with more information. For instance, one can use satellite imagery to look for large objects, like buildings, that have changed or demolished over the years. To narrow down the time frame even more, go over other sources that have information on the area. This can be news media, or even social media, as long as it has information with a date that makes it possible to look for differences. With this newly found information, the time frame can be narrowed down. When the time frame has been narrowed down to less than about a year, it might be possible to determine the exact moment of time. For that, one has to look at the position of the sun, by going over shadows if they are visible. Overcast skies can make this step difficult or even impossible, since light scatters in different directions. And when shadows aren't clear enough to use, look for a general direction where the light comes from to determine the possible direction where the sun is sitting. This might give enough information to narrow down the possible time, but for that a possible date has to be determined first. To sum it up, the steps we need to take are: Determine the location Determine the year Determine the season Determine the date and time If only the location is known, and there are no indications to narrow down the year itself, it might be possible to find a possible date and time without the actual year. Since the earth rotates around the sun in a very predictable pattern every year, it is sometimes possible to use tools to find the possible date, if the angle and direction of the sun can be measured precisely. How that works, will be explained in chapter 6 . ↑ Table of Contents 5. Looking for Clues When you are new to chronolocation, the best way to start, besides having a correct and trusted EXIF data of a photo, is to simply look at a scene. Go over it, try to describe the objects that are visible and find indications of a certain moment in time that these objects should have existed. Use the same techniques as you use for geolocation, and perform a ' gap analysis ' to structure the information and research questions. You might end up with a period as large as a decade, or as small as a year. But depending on what you are investigating, it could even be a specific day of the week or a specific local time. Sadly enough it isn't always possible to zoom in on a specific time or day, but there are also times that there is a lot to work with. I admit that I am sometimes blinded by lots of details in such a way that I miss some obvious clues. But going over all the information that is visible in a photo or video, as well as zooming in on those details, is extremely important. It's possible that while revisiting certain details after some time, one is able to pivot on other information that was gathered. Here are some examples of easy to spot things that can help you in the first steps: Seasonal indications like flowers, trees or general weather conditions Production years of cars, issue dates of licence plates New buildings, construction work or demolitions Clock towers, watches and clock from public transport Signs with time-based parking restrictions to determine a weekday Markets, roadworks, festivities or other temporary events Posters or placards with dates, like movies releases Advertisements, sales or specials at shops To illustrate some techniques described above, I'll look at one of my all-time favourite challenges from Quiztime. Philipp Dudek asked two questions in this challenge : Where was the photo taken and what date? The location was reasonably easy to find for most people, it was the Danish embassy in Riga, Latvia. Knowing the location, we can have a first look at the photo to try and find clues that can be used for chronolocation. Give it a try before scrolling below the photo, to see whether you can already find some clues yourself. As explained earlier, the first step in such a task is to narrow down the time frame. Since the photo was clearly taken in the digital era of photography, and the question was published early 2018, we have a period spanning well over a decade. And the most obvious indicators to narrow down the earliest possible moment, as discussed in chapter 4 , are the earliest production dates of cars. To find the latest possible time, some time was spent to find out when security cameras were placed on the building across the street. The third indicator was a change in parking restrictions at a later date, due to the fact that the sign itself wasn't visible on the photo. By using these three pieces of information, it was possible to bring back the time frame down to about 3,5 years. After that, it was time to look at the season, pruning of a specific tree and by calculating the angle of the shadow, all of which will be explained in later chapters. If you want to read the full write-up of this geolocation and chronolocation challenge, you can do so here . 5.1. Construction, Scenery and Landscaping Large changes within the scenery might be spotted with something as simple as Google Earth Pro . There is also a web version, but I would recommend using the application for speed, multiple extra options and the ease of which one can save, import or export locations in the form of KML files. April 2021 April 2020 ↔ Comparison slider might not work on mobile 5.2. Events, Acts and Festivities One thing that can be of help when trying to determine a possible time frame, are events or festivities shown on posters, placards or such. These are usually placed several weeks before a big event, and even though they could still be around several months after the event, they can provide some indication of the earliest possible moment in time. When going over photos or videos that are taken in a city or even indoors, make sure to check things like: Film and theatre posters Events and expositions Advertising placards Such posters and placards can also help with geolocation, since some countries have a very specific way of writing down dates. There are ISO standards when it comes to date notation , but there are some countries that have their own official standards. For instance, there are several countries, like Germany, Switzerland, Armenia and Romania, that write the dates using periods in between the numbers. These dates are always in the form of dd.mm.yyyy , with or without the leading zeroes for the days and months. So one can be fairly confident that the days are mentioned first when there are dots used in a written date. ↑ Table of Contents 5.3. Seasons and Nature Plants and trees can give a very good indication of the season during the time a photo or video was created. If there are plants or trees visible that seem to be flowering, you could try and determine what plant it might be and when they are supposed to bear flowers or blossom. I do have to send out a small caution and remind you that certain crops or plants can flower in different months, depending on the location. To give an example, it is common to see big fields of yellow rapeseed in the northern part of Europe and even in China from around April to June. But in Canada, where most of the yellow fields are Canola, a very similar scene will show up in June or July. And if we're talking about Australia, don't be surprised to learn this season falls in the months of August till October. To make it slightly more complicated, there are summer and winter versions of rapeseed, but usually the winter type has a higher yield, so it is more common to see them in the seasons I mentioned. Horse chestnut during spring — Pixabay An example that was handed to me by MCantow , is the chestnut. In Northern Europe we can see the chestnuts hanging from the trees from around October until early winter, but there is more to that tree during the rest of the year. Besides having the seeds at the end of the year, it grows flowers in late spring or early summer, as can be seen in the photo above, and during the fall the leaves turn a lovely shade of red-brown. In the following example , MCantow points out a European horse chestnut and a common lilac, that could be used to pinpoint the season. Using vegetation to determine a month Since the common lilac flowers in April and May in Europe, this narrows it down to two months. If the tree in this image is indeed the European horse chestnut, it would flower around the month of May. Since the distinct white flowers aren't visible in the image, this could mean that the episode may have been shot in the month of April, when the lilac would be bearing its flowers. MCantow was also the person who spotted something very useful in the previously mentioned example of the Riga embassy quiz. In the photo a lime tree visible in the garden of the embassy, that was trimmed or pruned once every so often. After doing some research on this, we found out it is indeed common to prune a lime tree every two years, because this is the best way to keep it in a healthy shape. By comparing images from this particular tree over longer periods of time on Flickr, we were actually able to estimate in which specific months over the years that tree was pruned, and therefore helping us in finding the actual date. But there are enough plants and trees that might be of help to determine a season, or even a possible month. Here are a few examples that I wanted to share since they blossom or flower in specific areas at very specific times. Do be careful and use this only as a rough guide, and always make sure to check local flora to make sure that you have the correct species when looking at specific plants or trees. Species Period Comment Lavender June Cape Verde and the Canary Islands, and from Europe across to northern and eastern Africa, the Mediterranean, southwest Asia to southeast India Cherry Blossom March to April Mostly Asia, but there are a few locations in Europe and North America where cherry blossoms can be found in parks Poppies April to June April to May in Southern Europe, May to June for more northern countries Witch-Hazel September to March USDA zones 3 to 8 (North America), it's special since this tree actually flowers during the winter months More information about the 'USDA zones', or hardiness zones, can be found at the Wikipedia page . This can be used as a reference, or to verify specific plants or trees within a geographic area. ↑ Table of Contents 5.4. Other Indicators There are many more factors you can use to bring down the date or time when it comes to chronolocation. If you are observant enough, and use every bit of information that is available, it'll open up a world of possibilities. In the next example people found out the time the photo was taken, by paying attention to the helicopter that was mentioned. After geolocating the photo, they looked at the flight data that was available of that area, and came up with the exact time. Using air traffic to determine a possible time To track air traffic, a website like Flightradar24 can be very useful. There are other websites that offer the same functionality, and with paid accounts it's possible to get more historical information on air traffic. 5.5. Google Earth Pro The free tool Google Earth Pro can be extremely helpful since it has historical imagery from nearly every location on the planet. This dataset can be found in the menu bar, by clicking on the small clock icon. Historical imagery within Google Earth Pro After clicking on the menu button, a small slider appears showing the date of the imagery that is currently showing. The slider shows light blue marks on dates where it features a dataset. Sliding throughout the dates will reveal these images on the screen. Going over the historical imagery can be useful to find changes in the landscape, as discussed in paragraph 5.1, but can also be useful to see what shadows look like in a specific location. August 2021 June 2011 ↔ ↑ Table of Contents 6. Sun Based Chronolocation If there is no clock visible in a photo or video, another way to determine a date or time is to use shadows. For multiple investigations I had to use this to try and determine a solid time frame, even though it can be a very challenging task at times. Some media are just downright poor in quality, or shadows are in very unfortunate angles to make it more difficult to work with it. But first let me explain something about the process involved. First, the earth revolves around the sun, what we call the earth’s revolution and the trajectory that the earth makes is shaped like an ellipse. While we spin around the sun once a year, the earth also rotates around a vertical axle that is slightly off centre. The tilted axis, together with the rotation around the sun gives the earth it’s four seasons. Image by Dennis Nilsson, Wikipedia Because the rotation of the earth and the trajectory around the sun is extremely predictable, we know that at any given day and time the sun is in a specific position. During a summer in the Northern Hemisphere the sun is high up in the sky, while the winters have the sun much lower towards the horizon. On the internet there are several tools available that can calculate the exact position of the sun at any given day or time. To use this for a calculation, the only thing needed are the angle in comparison to the horizon (the zenith or altitude) and direction of the sun (the azimuth). With these two pieces of information, anyone can calculate the possible date and time of any given shadow. Due to the trajectory of the earth and its rotation, there are two dates a year when the sun is in the same position, called the equinox. These dates are around March 20 and September 22. Looking at the moment of the equinoxes, we see the following pattern emerge: Latitude March equinox September equinox 90 N 0 degrees 0 degrees 60 N 30 degrees 30 degrees 50 N 40 degrees 40 degrees 25 N 65 degrees 65 degrees 0 N 90 degrees 90 degrees 25 S 65 degrees 65 degrees 50 S 40 degrees 40 degrees 60 S 30 degrees 30 degrees 90 S 0 degrees 0 degrees Before we can start calculating a time or a date, a few things are important to know, namely: The more towards the equator, the more difficult it can get due to the fact the sun has a more flat trajectory than anywhere else The easiest calculation is when the image is taken where the shadow is showing horizontally in the image, or there is an easy way of measuring the length. If there is an indication the scene might be slanted, it is no problem to rotate it slightly to make it easier for yourself Shadows that are in an angle or coming towards you, aren’t easy to measure, unless it falls on a surface that enables measuring the length in an accurate manner It is the best if shadows are fully visible and clear enough to be measured When a shadow is not fully visible, it is still possible to use it to calculate a possible time, since only a direction is needed, but finding dates can pose problems since the length of the shadow is needed Try not to work with shadows where the surface is warped or uneven, unless you are equipped to work with that by, for instance, using 3D modelling to recreate the scene Both the object and shadow it casts, should be measured within a single frame, so that the relation between object height and shadow length can be determined When using different frames from a film clip, distances can vary and therefore might make measurements less accurate Some reference point is needed to determine the exact direction the shadow is falling towards If all these conditions are met, then it is not only possible, but even fairly easy to determine the date and time when that photo or video was taken. ↑ Table of Contents 6.1. Basic Time Calculation As a first example, we'll go over an old Quiztime question, with a photo that was taken on Thursday, June 7, 2018. The date was given, and the time had to be determined. Example of a chronolocation quiz at @Quiztime For this, we first need to find the exact location of this image. This isn't so difficult, and after some reverse image searching, it gives us the answer: It's a large artwork at the foot of the Atomium in Brussels. We only need to establish where it is located exactly, and from which angle the photo was taken. Welcome sign at the base of the Atomium Measuring the angle of the artwork, gives us a deviation of 5 degrees, in comparison to true north. We can measure this fairly easily by using the ruler in Google Earth Pro. Measuring the azimuth in Google Earth Pro Looking at the image itself, we can see a shadow that was cast by the woman standing in front of it. This gives us the indication that the sun was standing south, with an azimuth of 185 degrees. When we line up the base of the artwork (green) with the direction of the shadow (red), we see that they run nearly parallel. Estimating the direction of the shadow If we want to be even more precise, we can zoom in on the image itself to check whether the shadow is indeed in line with the artwork itself, or slightly off. When we look at the shadows, it seems that there is a slight difference, but the difference is so small, that this would be maybe half a degree deviation. Looking at all the details To find out what time this was possible, we open the website SunCalc . We first need to find the exact location, and for that we can simply search for 'Atomium' ( A ), and it'll give us a list of possible locations. Selecting the location in Brussels, we then set the date to June 7, 2018 ( B ) by clicking on the date field. We can then move the slider on the top bar ( C ) until we get close to the desired azimuth. To get as close as possible, we can adjust the minutes manually, by clicking on the time field, and adjusting it accordingly. The time given on the website is in local time, and is adjusted for daylight saving time automatically. Finding the correct azimuth After matching the altitude and azimuth of the sun, we find that the time that this photo was taken was around 13.53 local time. The actual time was around 14:00, which is only a few minutes off, which is a good result. ↑ Table of Contents 6.2. Date and Time Calculations A more difficult task is to try and find a time and date. For this, we also need to look at the altitude of the sun, besides the azimuth. Since the height of the sun is changing throughout the seasons (remember the 'low sun' during winters in the Northern Hemisphere), we need to take that into consideration. To calculate a possible date and time, in general the following steps are necessary: Bring down the rough time range to one year Determine the exact location Determine the azimuth (direction) of the sun Determine the altitude (angle) of the sun Find all corresponding moments in time Eliminate seasons After that, there should only be one specific moment in time left. If this moment is very close to a solstice, it is possible that two moments in time match. This will need further elimination, if at all possible. To see how this process works, I'll use the following Quiztime challenge by Julia Bayer : Another quiz from @Quiztime The first step is to find the location. This turns out to be the Haus der Kulturen der Welt , on the river Spree in Berlin. We'll need coordinates of the possible location in a bit, so we write them down: 52.5195441,13.3649990 . The second step is to determine the height of the object and the shadow length, so we can determine the angle of the sun. Do make sure you select the correct point when visualizing the path of the sun rays. Imagine how the rays hit a specific part of the glass, and where on the surface they cast a shadow. Visualizing the sun rays One option to calculate the altitude of the sun is by measuring the amount of pixels, both for the object height and the shadow length. For this you can use Photoshop, The Gimp, or any other program that enables you to load an image, and to draw a line to measure the amount of pixels. Because it's irrelevant what units of measurement we use, we don't need to use millimetres or metres. What we are interested in, is the angle between the vertical and horizontal plane of the right-angled triangle we created. By entering the height as the amount of pixels of the object in Suncalc, we can then slide the sun left and right until we have the desired length. Another option is to calculate the angle manually with the following formula: α = arctan(height / shadow length) If it's been too long ago that you've used a calculator, or rather like to use online tools, then there are multiple websites that can help you. One of them is the website calculator.net , that have a module for right triangles. Fill in the height of your object under a , and the length of the shadow under b . After pressing the button, the altitude of the sun will be calculated and shown as α . Whichever method is used, this will give us a value of about 25,6 to 25,7 degrees altitude. If we want to find out at what moments in time this altitude and azimuth occurred, we'll be using the website SunEarthTools.com . On the website, we pick the menu option 'Sun Position'. This page has several tools that revolve around the location of the sun. The option that is most interesting is the 'Annual sun path' section. You can scroll down, or jump to it straight away by clicking the option directly under the map section. Generating an Excel sheet I've noticed that the adjustments for daylight saving time isn't working as it should. I've turned that option off, and calculate everything in time zone GMT+0. I adjust the times later on. This option will generate an Excel sheet with altitudes and azimuth of the sun throughout a whole year, based on a given location. For this we fill in the details, like the location and the year, and then choose and the steps, or increments. The sheet can be generated in increments of 5, 10, 15, 20, 30 or 60 minutes. In general, I would say: The closer to the equator, the smaller the increment. For this an increment of 15 minutes is enough, and will generate a sheet of about 1MB in size. In this case, I chose the previously mentioned coordinates: 52.5195441,13.3649990. It technically isn't really an Excel sheet, but an HTML table. Excel will give a warning when opening it, and will convert it accordingly if you continue. After opening the sheet it'll show all the dates of the year in the first row, and in the columns it'll have the different times in 15 minute increments. Per timestamp, it has one column starting with E for elevation, and one starting with A for azimuth. To visualize what I'm looking for, I personally like to highlight cells that fall in between certain ranges by using the 'Conditional formatting' option. This option is also available in the open source app Calc in LibreOffice. In this case, the altitudes and azimuths are far apart, so it's enough to create two rules for the whole sheet, where cells will be highlighted in different colours when they fall in between different values. If the azimuth and altitude are very close together, consider using the same colour for highlighting, or create a rule for the different columns. To do this, pick the menu item 'Conditional Formatting' and use the option: Highlight Cells Rules - Between . Conditional formatting in Excel This option gives us the ability to highlight cells that have a value within a specific range. To find the possible values for that range, play a bit with SunCalc and move the sun back and forth, to get a rough idea what the direction of the sun could be. Find the minimum and maximum values for the azimuth, by comparing the direction of the shadow to the image or video you're investigating. After determining these values, the altitude was determined to be between 26 and 27 degrees, since that is the angle of the shadow. The azimuth has to be somewhere in between 262 and 264 degrees. After assigning different colours to these values, a pattern will emerge within the sheet, as can be seen below. Creating formatting rules Depending on the language settings on your system and in Excel, it's possible that the numbers will be seen as text and the cells won't be highlighted. To correct that, select all the cells by clicking in the left top corner, or pressing Ctrl-A or Cmd-A, and replace all periods with a comma. After that, it'll be easy to find the possible times by looking at the moments where both the altitude and azimuth fall between the ranges we provided. The only period where this is possible is between August 3 and August 7, 2021 around 16:45 in the afternoon. Given the fact that Julia mentioned the photo was taken on a Thursday, there's only one option left. Finding matching values If you're not using Excel, or any open source options like LibreOffice, another option is to go over SunCalc.org manually and pick two or three dates per month, until the altitude and azimuth gets closer to your desired values. After a rough period has been established, it's possible to move towards the desired dates. But by using the export provided by SunEarthTools , it's possible to determine a possible time frame easily, quickly, and accurately. ↑ Table of Contents 7. Tips and Tricks Accurate chronolocation is only possible if there's enough information to go on. But there are times when the media being investigated is hard to interpret. Shadows might be coming from different directions, or hard to make out. Or the photo doesn't lend itself for accurate measuring of the shadows. But usually there are always some things that can be tried, to enhance a photo, or work with the information that is visible. 7.1. Hard to See Shadows There are moments when a shadow isn't very visible, but there are ways to enhance the image to make measuring more easy. There are different options you can use, to make the shadow more visible. Within Photoshop for instance, tools that could help are: Inverting the image Adjust the brightness and contrast Change the exposure or exposure offset Enhance the shadows An example of an old Quiztime quiz , where such adjustments have been made can be seen here: After Before ↔ Comparison slider might not work on mobile Using that same photo of the fire department pickup, there's another thing that's just about visible. When zooming in on the windows, the brightest part of the sky is on the right side of the visible windows. Since the shadows seem to indicate that the sun is nearly in a direct line of our viewing direction, it makes sense that there is a possibility that the sun is visible in the reflection, here marked in yellow. Finding the sun in reflective surfaces Make sure to investigate a photo or video, and look for any clue that might help you in any way to determine the location of the sun. 7.2. Shadows in Different Angles If the shadows on the photo of video are not aligned horizontally, it will make measuring the exact angle more difficult. Since we live in a three-dimensional world, the length of a shadow is sometimes difficult to measure when it's falling towards you. Here are two examples, both taken in the same area. GOOD! Shadows are horizontal - © Volker Meyer, Pexels BAD! Shadows are falling towards you - © Lina Kivaka, Pexels Luckily there are possibilities to measure the distance of a shadow fairly accurate, by using elements of the environment as guidance. Try and find items of which the exact size can be determined, of find something that can be used to measure the shadow as accurate as possible. Street tiles can be extremely helpful, by using them as a grid, for instance. Let's have a look at an example, again at the Louvre, where the shadow is not plotted horizontally on the image. It is still possible to use the tiles as a grid, and calculate where the shadow would be when positioned horizontally in the photo, therefore making a calculation possible. First we need to establish where we would like to have our shadow in the image, and draw a horizontal line that we'll use for guidance later on, so we can determine were the shadow would fall if it would be rotated anticlockwise. Visualize where the shadow should be for our measurement Next we recreate the grid with the correct proportions, and we will recreate the position and length of the shadow. This can be a simple line, from the object, or in this case a person, to the furthest point of the shadow. Recreate the grid and shadows Then we draw a circle in our grid, where the centre of the subject itself is also the centre of the circle itself. To find the centre, visualize how the highest point that is able to create that shadow, extends directly downwards to the ground. This will be the centre that we need to use to draw a circle. The radius of this circle extends towards the end of the original shadow, show here in yellow. Plotting a rotated shadow that can be measured After lining up the horizontal line in the photo, and the radius of the circle, we find a new point where the shadow would fall, if it would be rotated anticlockwise. When measuring the original image in Photoshop, I found a length of 830 pixels. When comparing this to the length of the original shadow in the image, we find that it's only 625 pixels long, and therefore roughly 30% too short to be used for an accurate calculation. 7.3. ShadowCalculator If it's unclear what a shadow, for instance cast by a building, could look like in a specific area, then it's possible to recreate it using freely available tools. One of the simplest ones I've found so far, is ShadowCalculator . It has the option to create a virtual building on top of Google Maps, placing points on the map to create a shape. Quick example of the Dam Palace in Amsterdam Every point in the shape can have its height adjusted, making somewhat more complex shapes possible. By adjusting the date and the time on the right side of the screen, the shadow and its shape will be adjusted on the map. 7.4. Warnings and Pitfalls When going over images and videos, looking for shadows, there are a few things to be careful about. If you're new to the game, there are some situations that could lead you to different dates or times. One thing to be careful about, are clouds in the sky. Sunlight that travels through a cloud can scatter the sunlight, whereby the clouds are acting as a diffuser . This will make the edges of the shadow harder to distinguish, information we actually need to determine a correct altitude. Besides that, it can also make it very hard to distinguish the shadow from darker surfaces like asphalt. Clouds acting like a diffuser Another thing to be wary about are reflective surfaces. Especially in modern cities, with large glass facades, with reflective windows. Looking at the example, we can clearly see the sun being reflected in the large building, thus sitting in a location somewhere left of the photographer. But due to the reflective surface of the building, all the shadows fall towards us. Photo © Matheus Bertelli, Pexels To determine the exact direction of the sun, one would have to zoom in onto the right bottom of the photo. The woman walking there is not lighted by the reflection of the sun. By using this bit of information, it's possible to determine the correct location of the sun after all. Pay attention to details ↑ Table of Contents 8. Conclusion This concludes this comprehensive guide on chronolocation, and I hope it gives some tips, tools and hints for people that are just starting out with this. The most important thing in chronolocation is always: Pay attention to details, verify what you're seeing, and use knowledge or information about a specific area to get a better understanding of the situation. Whether it's asking an expert to determine whether crops are harvested already, searching the internet for information on dry and wet seasons, what plants are flowering at any given time and so on. By combining all that information, and looking at multiple sources to narrow a time window down to a year or a few months, it's time to dive into the details. Hopefully you have shadows that can guide you, or maybe there's a sale at a shop that is visible in an image you're working on. It doesn't matter how small the clue, sometimes a simple no-parking sign can break a case open and enable you to determine the exact date within reach. So go out, take some photos in different situations, or go over your old archives, and practice. Make sure your EXIF information is correct, and see whether you're able to find out when you took a specific photo. I'm closing off by saying that this guide is not finished yet, and will probably receive some updates in the upcoming months or so. There are also some topics I want to include over time, expand on certain paragraphs, or write down some tips even more clearly. But due to time constraints (I know! It only took me over 3 years), I had to finish this guide to be released early November 2021. 8.1. Glossary Altitude The term altitude is used to describe the angle in degrees of the sun in relation to the earth's surface. An altitude of 0° means at ground level, and 90° means directly overhead. Arctan The arctan is the inverse trigonometric function of the tangent function, which is the ratio of the side opposite an angle divided by the side adjacent to the angle. It is used in the following formula, that calculates the angle, or altitude, of the sun: α = arctan(height / shadow length) Azimuth This term is used to describe the direction where the sun is standing, in relation to true North. This means that at an azimuth of 180°, the sun will be in the south. Diffused light Diffused or soft light is the situation where the sunlight is scattered. This can be due to clouds, or because the sun is set very low, and bounces off the atmosphere. Equinox An equinox is the moment the plane of Earth's equator is at a 90-degree angle with the sun, so the centre of the visible Sun is directly above the equator. This occurs twice each year, around March 21 and September 23. Solstice The solstice is the moment where the sun is the furthest away from the equator, and happens around June 20 or 21, and December 20 or 21. They are called respectively the Summer Solstice, and Winter Solstice. In June this results in the longest day of the year, and the shortest day in December, when you're in the Northern Hemisphere, and vice versa in the Southern Hemisphere. SunCalc SunCalc is a tool that enables you to recreate the location of the sun during any moment in time, at any location on earth. The link to the website is: https://www.suncalc.org/ SunEarthTools The website SunEarthtools provides multiple tools that can be used to create an overview of sunrise and sunsets, or export Excel sheets with altitude and azimuth information. The link to the website is: https://www.sunearthtools.com/ Acknowledgement First, I want to thank everybody of the Quiztime crew for sending out daily verification quizzes. I've learned a lot from these, and have been able to broaden my knowledge over the last few years. I also want to thank Christiaan Triebert and Aliaume Leroy for taking the time to review the information and giving tips. And most of all I need to thank someone very special to me, who had to miss me for hours on end, while I was writing paragraph after paragraph, and doing research during holidays. ↑ Table of Contents Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/2/8/3/7/3/283738aec7fb54aa80a90926a98252c8717238bb-chrono-enhance1b.jpg","https://sector035.nl/images/3/7/5/b/f/375bffcdb336d230ad7ad19758b4489c2b7d1650-chrono-google-earth-pro2.jpg","https://sector035.nl/images/6/0/3/e/c/603ec54776f4afd3ab7b0d45d338348420ab994a-chrono-birmingham-2020.jpg","https://sector035.nl/images/a/b/1/a/f/ab1af4920befc0dcf4693f562b53dc5c7965506f-chrono-birmingham-2021.jpg","https://sector035.nl/images/e/0/6/4/6/e06468ea027c89542056c00b68115ee96030ef64-chrono-google-earth-pro1.jpg","https://sector035.nl/images/e/e/8/0/9/ee80933ac825fb0e4b7650d1164d7afea746a3e8-chrono-enhance1a.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-angles1.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-angles2.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-atomium.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-atomium3.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-atomium4.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-atomium5.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-chestnut.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-earths-motions.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-excel1.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-excel2.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-excel3.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-exif.png","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-google-earth-pro.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-orlando.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-shadow-measure1.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-shadow-measure2.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-shadow-measure3.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-shadowcalculator.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-suncalc.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-sunearthtools1.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-tip1.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-tip2.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-tip3a.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-tip3b.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-tweet-berlin2.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-tweet-brussels.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-tweet-fiete.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-tweet-julia.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-tweet-mcantow.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-workflow-new.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_ee6bd9beb826_0.jpg","blog_data/images/blog_ee6bd9beb826_1.jpg","blog_data/images/blog_ee6bd9beb826_2.jpg","blog_data/images/blog_ee6bd9beb826_3.jpg","blog_data/images/blog_ee6bd9beb826_4.jpg","blog_data/images/blog_ee6bd9beb826_5.jpg","blog_data/images/blog_ee6bd9beb826_6.jpg","blog_data/images/blog_ee6bd9beb826_7.jpg","blog_data/images/blog_ee6bd9beb826_8.jpg","blog_data/images/blog_ee6bd9beb826_9.jpg","blog_data/images/blog_ee6bd9beb826_10.jpg","blog_data/images/blog_ee6bd9beb826_11.jpg","blog_data/images/blog_ee6bd9beb826_12.jpg","blog_data/images/blog_ee6bd9beb826_13.jpg","blog_data/images/blog_ee6bd9beb826_14.jpg","blog_data/images/blog_ee6bd9beb826_15.jpg","blog_data/images/blog_ee6bd9beb826_16.jpg","blog_data/images/blog_ee6bd9beb826_17.bin","blog_data/images/blog_ee6bd9beb826_18.jpg","blog_data/images/blog_ee6bd9beb826_19.jpg","blog_data/images/blog_ee6bd9beb826_20.jpg","blog_data/images/blog_ee6bd9beb826_21.jpg","blog_data/images/blog_ee6bd9beb826_22.jpg","blog_data/images/blog_ee6bd9beb826_23.jpg","blog_data/images/blog_ee6bd9beb826_24.jpg","blog_data/images/blog_ee6bd9beb826_25.jpg","blog_data/images/blog_ee6bd9beb826_26.jpg","blog_data/images/blog_ee6bd9beb826_27.jpg","blog_data/images/blog_ee6bd9beb826_28.jpg","blog_data/images/blog_ee6bd9beb826_29.jpg","blog_data/images/blog_ee6bd9beb826_30.jpg","blog_data/images/blog_ee6bd9beb826_31.jpg","blog_data/images/blog_ee6bd9beb826_32.jpg","blog_data/images/blog_ee6bd9beb826_33.jpg","blog_data/images/blog_ee6bd9beb826_34.jpg","blog_data/images/blog_ee6bd9beb826_35.jpg","blog_data/images/blog_ee6bd9beb826_36.bin","blog_data/images/blog_ee6bd9beb826_37.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/lake-constance","title":"","status":"ok","retrieved_at":"2026-08-29T16:13:47.450464+08:00","text":"Lake Constance - Geolocation | Sector035 Lake Constance - Geolocation Home Week in OSINT Articles Search Lake Constance - Geolocation 2nd Dec 2024 maps geolocation quiztime aerial imagery It has taken well over 7 years before this geolocation challenge was resolved, and I have spent countless hours on trying to find this years ago. Sadly enough, work and other priorities had taken over my life, so the last three years I didn't have time to look at it at all. Until recently, when I managed to find the location of this exact spot, but it wasn't in the usual way. The original Tweet Bask in 2017 the Twitter user @CountryTec sent out a tweet, asking for help on locating a specific image from the 50's. This is the original tweet: CountryTec, reaching out to the public for help The tweet translates to: I have this photo with my parents taken around the 50's. Does anybody know where this is? Please #RT One of the first questions that was asked, was what could be written on the monument, and @CountryTec already had a look at that, and with the help of some other people, the deduced it said something along the lines of: \"... SCHWEIZ IN DANKBARER ERINNERUNG AN DIE EISERNE ZEIT ...\" Or, translated: \"... Switzerland in remembrance of the iron age ...\" The German term \"Eiserne Zeit\" is usually for the thirty years' war , that lasted from 1618 to 1648, but it was uncertain whether this monument was that old. People also hinted that in the middle of the monument, on both sides of the inlay, there were the numbers 14 and 18, which may hint towards the first world war. In July 2018, @CountryTec shared it again, where it received some attention once more. This time, the Twitter account @Quiztime was tagged, after which the Quiztime crew received this challenge. This was the time I saw it, and some great work had been done so far already! The information that was known by then was: Taken somewhere around the mid-50's Most part of the text was known Most probably around Lake Constance Might be around Arbon, Seepark Rorschach or Lindau Looking back at it now, this may have been enough to actually solve it. But it turned out, there was a problem. Spoiler alert, the monument was removed! How it Started Looking at most of the information that was available, I tried to have a stab at it with the @Quiztime crew, working closely together with mainly Fiete Stegers [ ]. It seemed a somewhat straightforward quest, and there are certain ideas on what might help geolocate this, like: General reverse image search Use AI to colour the image, for aid in searching Search, in German, for monuments Go over public records and local websites After spending some time doing that, I found that nothing came up. Google, Bing and Yandex showed some monuments that looked similar, but there were no matches to be found. Me and a few people went over some websites, databases, social media, but without any results. Looking at Shadows At a certain point, I wanted to know what direction we might be looking, since it might help in finding, or excluding, certain locations. For that, I made some assumptions and tried to measure the shadow that was visible in the image. The first assumption was a rough estimate of the height of the man, and the second was a rough estimate of how long the shadow might be. The third assumption was the idea that this photo was taken in the summer. I based that on the fact that the shadows looked sharp, due to a bright sun, and the way the people were dressed. All combined, I had the following pieces of information in mind: Somewhere in Switzerland, near Lake Constance Looking at the background, we are facing a lake Somewhere in summer time The height of the person around 1.75m Length of the shadow was estimated around 80cm Drawing in the shadows Going over to one of my favourite tools for shadow calculations, I opened up SunCalc . I went over several dates, and found that August and September were throwing shadows that were too long, making it impossible to find a match. Going back to July, I was able to have the sun high enough in the sky that a shadow of about 80cm or so was possible. And it turned out that the sun would have been roughly south. This could be southwest, or southeast, but with all the assumptions made, it was impossible to narrow it down any further. Finding a general direction of the sun Since there had been an idea the photo might have been taken around the area of Arbon, Lindau or Seepark Rorschach, which are all south of Lake Constance, this meant people were on the right track. The Breakthrough More than six years after I started this quest, where I was not constantly searching, but once every couple of months I would revisit this and look for a new information, it was still unsolved. That was until on November 28, 2024, I went back to the challenge and looked at all the comments to see whether there was any new information. And there certainly was! A new lead, out of the blue Someone who had been looking at the request managed to find some old postcards on a Swiss website, giving an extra hint towards the exact municipality we were looking for: Horn. And there wasn't just a single postcard from Horn that showed this location, but I managed to find 4 in total. The location, with the name 'Horn' According to the Wikipedia page , Horn lies in the district of Arbon, which was mentioned earlier too. Looking back now, and knowing all the information that was available back then, I am certain we could have solved this well over six years earlier. But having other priorities in life, these things sometimes move to the bottom of the stack, and when you see new information, like Phaedrus' [ ] his tweet with the postcard, it relights your interest once more. And this time, we needed to finish it all the way. Old Maps and Photos To find out where the monument could have been, I had a look at older maps from the area. Using the historical maps from the Federal Office of Topography Swisstopo, I compared the map of 1960 to the one of a later date, like 1975 . And there was an interesting change, because somewhere around the area where I expected the photo to have been taken, the whole area changed. Instead if a small bulge, a large part of land has been added. You can see the comparison below, but sadly enough it doesn't seem to work on a mobile phone. 1975 1960 ↔ Changes in the landscape between 1960 and 1975 On the website of the Swisstopo office, there is also the option to dive into historical aerial photos. And after going over about 10 or so different images, I chose to show the location as it was in 1935, and in 1972. This clearly shows not just the scale of what has been done to the area, but the image in 1935 also shows the water feature near some trees. 1972 1935 ↔ Aerial photos of 1935 and 1972 Here is another detailed aerial shot, taken in June 1945, also taken from the website of Swisstopo. Zoomed in, it clearly shows a half circle, a line of trees, and something that resembles a water feature in the center. The water feature, as it was in 1945 On the website of Wikimedia , Fiete Stegers [ ] found an aerial shot of Horn, made by Werner Friedli in May 1949. After downloading the original image, and zooming in onto the location where the water feature must have been, we can clearly spot the rough outline of the center part of it. Aerial photo, taken in 1949 Verification Stage Since we now had a very strong lead this might be the correct location, and it seemed to match with old maps and aerial photos, it was time to go back and look at the postcards more closely. It was time to go over to Google Earth Pro, GoogleMaps, PhotoShop, and try to line everything up nicely. Measuring the ratio of the distance between the churches or towers that are visible, wasn't a perfect match with the old photographs. But the shape of the churches A ( Kirche St. Martin ) and C ( Pfarrkirche St. Jakobus ) do match the general shape that can be seen in the postcard. The only one that is slightly more difficult to see, is church B ( Evangelische Kirche Arbon ), but given the fact that we are working with digital versions of very old postcards from decades ago, it was the best I could do. Trying to line up the view with the postcard Time to find out more about what happened in this area back then. Diving into History Now that we were fairly certain the location is correct, and we even find a part of the landscape changed, we need to find out what happened to the monument. And for that I dove into the state archive of Thurgau, searching for the term I learned while looking into this topic: \"Quaianlage\", or lakefront. In the archive I was able to find another postcard, with some more information about this monument ( in German ). The text explains that it was a water feature created by Louis Wethli (1867-1940) and was donated by a German merchant called Alfred Heinrich Klinkmann (1871-1943). Alfred worked in Milan until the first world war, and chose to move to Horn during this time. Out of gratitude for the hospitality, he commissioned a new water feature, that has been described as a \"bench protection\". He turned to the Zurich sculptor Louis Wethli, who built it between 1927 and 1928. When in 1969 the lakefront was redesigned, it was removed completely, and only returned on the so called \"Festplatz am See\" in 1997. Going over Google Maps and StreetView, we don't see anything that looks like the monument as we have been seeing on the postcards though. But one thing stood out, right on the edge of the \"Festplatz am See\", a stone feature ( Google Maps ) What is left of the monument It is very hard to make out, so it is time to have a better look at photos taken in the nearby area. And it doesn't take long before we find an image by Antoine Meyer. In that image, we can see details of the carvings, and comparing them side by side shows elements that absolutely match with the original from one of the postcards. The female figure is mostly hidden in the shadows, and no PhotoShop magic will be abel to enhance that. But the rough shape of her arms are still visible, and looking at the posture of the child on the right, it all matches nicely. Comparing the carvings And when we load the image in PhotoShop, and look at the text on the plaque, we are able to recover most of the text, that was characteristic of the original monument: \"DER GASTFREUNDLICHEN SCHWEIZ IN DANKBARER ERINNERUNG AN DIE EISERNE ZEIT DES WELTKRIEGES\" Underneath there seems to be some more text, but I wasn't able to fully reconstruct the full sentence. But after a tip from Louise [ ], who contacted me by email, the most probably option is the following line: \"1914 - 18 VON EINEM GÖNNER DER GEMEINDE HORN\" Loosely translated, it reads: \"The hospitable Switzerland in grateful remembrance of the iron age of the world war. 1914-1918 by a patron of the community of Horn\" Trying to make the text slightly easier to read Conclusion After well over 7 years after the original question was posted online, and thanks to the help I received from Fiete Stegers [ ] and the unsung hero over on X, called Phaedrus [ ], we were able to finish this chapter. By a complete overhaul of the landscape, it turned out it was rather difficult to find the location, yet not impossible. Due to this challenge, I found much more useful resources, found out there are way more historical aerial photos than I knew, and combined all sorts of techniques to verify everything. And after I posted my last message about it on X at 10:30 PM, it took some random account less than two hours to claim he or she found it, via a post on Reddit. Jumping in on the bandwagon, replying to a different thread about this photo, trying to take all the credits. If there is one person that deserves credits, it is Phaedrus [ ], who gave everyone a nudge in the right direction after several years, by finding the postcards. Don't do this... Previous Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/0/4/9/4/a/0494a0984b06e27ea65204be73ea260a60832770-horn-1935.jpg","https://sector035.nl/images/1/3/c/f/3/13cf34c35a0a1ca9beb03e5d4dbfcac947f297f7-horn-map-1960.jpg","https://sector035.nl/images/2/4/c/d/a/24cdac4d513189b7ab78a776ba365482294bcd4a-horn-1972.jpg","https://sector035.nl/images/3/9/3/4/4/39344e26805320ac5cfa5f9ab1e2212a13917476-horn-map-1975.jpg","https://sector035.nl/images/e/8/1/a/9/e81a91dfeb9ae10fc986c6263e8613fc90dafc9c-tweet-countrytec-2017-07-24.jpg","https://sector035.nl/user/pages/articles/lake-constance/aerial-1949.jpg","https://sector035.nl/user/pages/articles/lake-constance/carving.jpg","https://sector035.nl/user/pages/articles/lake-constance/google-maps-photo.jpg","https://sector035.nl/user/pages/articles/lake-constance/horn-1945.jpg","https://sector035.nl/user/pages/articles/lake-constance/map-view.jpg","https://sector035.nl/user/pages/articles/lake-constance/marvin-tweet.jpg","https://sector035.nl/user/pages/articles/lake-constance/postcards.jpg","https://sector035.nl/user/pages/articles/lake-constance/shadowcalc-1.jpg","https://sector035.nl/user/pages/articles/lake-constance/shadowcalc-2.jpg","https://sector035.nl/user/pages/articles/lake-constance/text.jpg","https://sector035.nl/user/pages/articles/lake-constance/tweet-phaedrus.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_f02c247450c2_0.jpg","blog_data/images/blog_f02c247450c2_1.jpg","blog_data/images/blog_f02c247450c2_2.jpg","blog_data/images/blog_f02c247450c2_3.jpg","blog_data/images/blog_f02c247450c2_4.jpg","blog_data/images/blog_f02c247450c2_5.jpg","blog_data/images/blog_f02c247450c2_6.jpg","blog_data/images/blog_f02c247450c2_7.jpg","blog_data/images/blog_f02c247450c2_8.jpg","blog_data/images/blog_f02c247450c2_9.jpg","blog_data/images/blog_f02c247450c2_10.jpg","blog_data/images/blog_f02c247450c2_11.jpg","blog_data/images/blog_f02c247450c2_12.jpg","blog_data/images/blog_f02c247450c2_13.jpg","blog_data/images/blog_f02c247450c2_14.jpg","blog_data/images/blog_f02c247450c2_15.jpg","blog_data/images/blog_f02c247450c2_16.bin","blog_data/images/blog_f02c247450c2_17.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/challenges/","title":"Challenges","status":"ok","retrieved_at":"2026-08-29T16:07:25.876844+08:00","text":"Challenges Here you'll find a collection of challenge exercises I've made for you to practice OSINT research skills with. Challenge 01: Pet the Dog Challenge 02: Out on a Walk  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/02_outonawalk.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/pet_the_dog.webp"],"local_images":["blog_data/images/blog_e4721ca9ef8f_0.bin","blog_data/images/blog_e4721ca9ef8f_1.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-a-very-cold-case-challenge/","title":"82. A Very Cold Case","status":"ok","retrieved_at":"2026-08-29T16:12:29.320431+08:00","text":"Walkthrough for Bellingcat's 'A Very Cold Case' challenge 09 Jul, 2026 Hi, welcome to this write-up for the A Very Cold Case challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. The challenge We've received an audio file with a radio programme covering the results of a Winter Olympics event. In the audio three different anthems can be heard partially. We have to find the date on which this medal ceremony took place. The first assumption When I listened to the anthems, I didn't recognize any of them. To be honest, I'm not that good recognizing sounds of any type. I feel awkward asking others for advice, because I sometimes get the (unwarranted) feeling that I have to do everything 100% myself or it doesn't 'count' (whatever that may mean). However, I'm starting to learn that finding and asking others for information they have on hand is a useful path to take. So, I played the audio for someone I know to see if they could give me a first clue. They said they recognized two anthems. They claimed the first part was Russia's national anthem and the third part was Germany's. Now I had a place to start. Assuming this information was correct, then I'd have to find a Winter Olympics event where the final medalists were from Russia, Germany and a third not yet known country. If I could find that event, then I could find the date when those medals were awarded. My plan was to check the Winter Olympics year by year, event by event, until I spotted an event in which Russia, Germany and another country had placed top three. Then I'd look up the anthem of that country and compare the audio. Straightforward, no? Russia hasn't been competing in the Olympics for a while, or at least not officially with their own anthem and such. I tried to look up what years Russia joined the Winter Olympics under their own banner and ended up at this link . Since the 2018 Winter Olympics athletes from Russia competed as ROC. So, I decided to work my way backwards starting with the 2014 Winter Olympics. Instead of checking each and every event at the Winter Olympics, I only had to check events with a Russian or German medalist. Knowing that Wikipedia has specific pages per country per Olympic year, I decided to stick with Russia and check year per year from there. Checking 1994-2014 I started in 2014 and worked my way backwards through the years. I used the Wiki page for Russia's acitivity at the Winter Olympics . Then I scrolled to the Medalists section. For every medal won, I went through the following process: Open the linked Wiki page for the relevant medal's sport event in the subsection Event (for example pair skating or ladies' singles etc) in a new tab. Check if the three medalists in the clicked event are a combination of Russia + Germany + a third country. If not, leave and go to the next event. If yes, look up the national anthem of the third country on Youtube, listen and compare it to Bellingcat's audio file. If the audio didn't match, note down the country as not it . They could be ignored in following events. Repeat from top. For 2014 I checked Latvia's anthem because of this event , Italy's anthem because of this event and France's anthem because of this event . All three weren't a match, so on to the next year. For 2010 I checked for Sweden and Norway , but no luck either. For 2006 I had to check Switzerland and Canada . No match. In 2002 the only new country that popped up was Bulgaria , but it didn't match the original audio either. In the 1998 Winter Olympics I found no new country combination. For 1994 I could check out Austria , but no. What was up with that? Huh? Oh!! I was temporarily confused. I thought I was dealing with Germany and Russia's national anthem, but I had checked every Winter Olympics year and hadn't found a match yet. The only countries to ever share the stage in 1994-2014 with both Germany and Russia were Austria, Bulgaria, Canada, Switzerland, Norway, Sweden, France, Italy and Latvia, and all of their anthems didn't match the original audio. Now the only Winter Olympics left were in earlier years, when Germany and Russia didn't even exist in their current form yet. How could that be? Then the penny dropped. I checked the audio for the USSR and it was a match with Bellingcat's audio. Then I checked for West Germany, and it matched too. I wasn't dealing with German and Russian medalists, but with West German and Soviet ones! I still had to find that third country, but now I knew how to look through earlier years. I repeated the same process as before, but now checked events for wins by USSR + West Germany + new third country. Checking before the 1990s From the Russia at the Winter Olympics Wikipedia pages I switched to Soviet Union at the Winter Olympics pages. I began at 1988 to once again worked my way backwards in time. The first new option I found was Czechoslovakia . They didn't win a medal in this event, just placed third in group B. Still, since two of the anthems were from countries that no longer existed in their past form, I wondered if the third would be as well. I looked up the national anthem of Czechoslovakia et voila! I had found the third anthem that is audible in Bellingcat's audio file. Now I just had to find an event where the Soviet Union, West Germany and Czechoslovakia shared the stage. Since I expected Czechoslovakia to have won fewer medal than the Soviet Union in the Winter Olympics, I switched to the Czechoslovakia at the Olympics Wiki pages so I'd have to check fewer possible events. I checked 1984 , 1980 , and when I reached 1976 I found an event with the three right medalists. Ice hockey at the 1976 Winter Olympics resulted in gold for the Soviet Union, silver for Czechoslovakia and bronze for West Germany. The event took place from 2 to 14 February 1976. Since usually sport medals are awarded right after the last match of the last day of the event, I assumed that these medals too would be awarded on the last day: 14/02/1976 . This turned out to be the correct answer.  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/001_russian_medals.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/002_wiki1976.webp"],"local_images":["blog_data/images/blog_66aca278d799_0.bin","blog_data/images/blog_66aca278d799_1.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-among-the-roots-challenge/","title":"48. Among the Roots","status":"ok","retrieved_at":"2026-08-29T16:09:43.331048+08:00","text":"Walkthrough for Bellingcat's 'Among the Roots' challenge 10 Aug, 2025 Hi, welcome to this write-up for the Among the Roots challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a picture of an item, partially buried in sand, dirt, stones, leaves and roots. It's quite hard to see. We know from Bellingcat's description that it's ordnance, but we have to find out what model and ordnance type. At a glance, the first things I noticed were: It's an arid environment, but some plants can still grow Because the object is partially underground it might be a mine of some sort It looks round and flat at the top The scale is hard to gauge, but with the size of the leaves, maybe it's the size of a big foot? I felt kind of at a loss of where exactly to start, so I decided to look even longer at the picture. What was I really looking at? With these new details, I felt more certain that it was a mine. I went over to CAT-UXO's page on landmines , but saw that there were 475 types to browse through. Oof. Maybe I could narrow that down somehow? Browsing around I decided to reverse image search Bellingcat's picture. I learned a lot about archeological finds of ancient pots, haha! But there were also quite some results relating to ordnance, especially on Yandex and Google. I didn't find the source of the picture, nor anything quite looking like the object in it. However, it did lead to a lot of articles about landmines and groups that clear landmines. They were interesting to browse. Some countries came up a lot in these articles: Yemen, Libya, Syria, Iraq, Iran and more. I noted some of these with arid environments down. Out of curiosity I once again visited CAT-UXO's website, went to their landmine page, and sorted by 'used in Yemen' . There were 30 results, and one looked like the shape of the object of the picture, hmm... Could it be the PMN landmine? Then I sorted by 'used in Libya' and only the PMN came close again. The flat top, the rounded edge, the distinct line dividing the item in two parts looked the same... But the colors looked very different. I felt like I was getting close to the model of ordnance, but felt unsatisfied with not really knowing the why and where behind the placement of this particular mine. Going a little meta Reading CAT-UXO's PMN landmine page , it stated that the mine is Russian. I began to think: the previous Bellingcat challenge in the Hidden Hazards category was about Russian ordnance as well. I looked up the name of the creator of the Hidden Hazards challenges: Andro Mathewson & Kate Millar. Clicking the names linked to Andro Mathewson's Linkedin page . Under experience it read: Project & Research Manager (Eyes On Russia) . Hmm, were we getting challenges based on ordnance used by Russia in their invasion of Ukraine? Ukraine does have some arid regions too... Back to CAT-UXO I went, and I now sorted the landmines by 'country of origin: Russia' and 'country used in: Ukraine' . There were 35 results. The PMN model showed up again and seemed to be the only one resembling the shapes in the picture. I still felt a little uncertain when I gave in the answer, because of the color differences. Could a mine weather in such a way, or be camouflaged in such a way, that it appeared fully sand color instead of its original brown/green/black-ish colors? Fortunately for me, the Bellingcat screen turned green. The correct answer was: PMN landmine .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-9.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-8.webp"],"local_images":["blog_data/images/blog_d6f6b79d8ea8_0.bin","blog_data/images/blog_d6f6b79d8ea8_1.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-charge-size-challenge/","title":"92. Charge Size","status":"ok","retrieved_at":"2026-08-29T16:12:41.956509+08:00","text":"Walkthrough for Bellingcat's 'Charge Size' challenge 02 Jun, 2026 Hi, welcome to this write-up for the Charge Size challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. The challenge This challenge contains one question: What is the minimum amount of TNT needed to shatter windows 30 meters away? In the first challenge in this series it became clear that an overpressure of 1 psi can shatter windows. So, in this scenario, the overpressure must be 1 psi at a distance of 30 meters away from the location of the TNT. How much TNT creates that level of psi at 30 meters? I tried to look for some type of calculator that would be able to estimate blast overpressure or damage. My first try at a search query into Google was: estimate blast damage I first arrived at this blast calculator , but I was unable to use it because I had no data about the angle of incidence. Then I was led to this blast damage estimation page from the UN. I found it a bit difficult to use, since it gives the blast damage in damage to windows, organs and houses. What counts as 'windows shattered' in this calculator? When one type of three has a chance of shattering? When they all do? I preferred a calculator that would show me the psi or kPa at a certain distance, so I kept looking around. On the same website of the UN, after browsing their menus, I saw this Kingery-Bulmash blast parameter calculator which seemed to include the parameters I was looking for. Since windows shatter at 1 psi, and since 1 psi equals 6.89476 kPa, I adjusted the amount of TNT until the incident pressure hit 6.89 kPa. This happened at 4.58 kg TNT. Surprisingly, this answer was incorrect. I scratched my head, but then remembered that the first challenge in this series required the user to round the kPa up to an integer, which meant that they worked with 7 kPa as the overpressure at which windows would shatter. I went back to the calculator and adjusted the TNT amount until an incident pressure of 7.00 kPa was hit, which happened at 4.75 kg. This number did make the screen turn green. So, the final answer is: 4.75 .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/img001.webp"],"local_images":["blog_data/images/blog_a2eb4c3881e5_0.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-denial-of-provenance-challenge/","title":"38. Denial of Provenance","status":"ok","retrieved_at":"2026-08-29T16:08:40.422007+08:00","text":"Walkthrough for Bellingcat's 'Denial of Provenance' challenge 16 Jul, 2025 Hi, welcome to this walkthrough of the Denial of Provenance challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but most likely there are many different ways of reaching the same results. Looking for the painting We've received a picture of a painting, a little backstory about there being a mistake in the accession record and the following question: \"What is the name of the venue where this possessor met a client on 14 May 1942?\" The first step I took was to do a reverse image search on the painting, so I'd know what work we would be looking into. In the results of TinEye the title of the painting and its painter are visible in many file names. My next step was to try to look for a record of who has possessed it by googling for: The Denial of Saint Peter Caravaggio accession record This brought me to the painting's page on the website of The Met Museum. Scrolling down a little, there was a tab called provenance in the artwork details with information about all of its previous owners. When I combined part of the list of owners mentioned in the gallery page and Bellingcat's data into one timeline, it looked like this: Guido Reni owned it from 1613 to 1624 In the Savelli family from 1624 to until ca. 1952 Mysterious owner meets a mysterious client on 14 May 1942 for it Vincenzo Imparato Caracciolo bought it on art market between 1945 and 1952 Hmm, that does not add up at all. So, supposedly it remained in the hands of a certain Italian family until after the war, but also, there was a meeting about this painting in 1942, where it switched hands from unknown to unknown. The painting was in fascist Italy under Mussolini at 1942. WW2 was happening. People were fleeing, removed from homes and killed. Nazi Germany's soldiers were collecting (aka plundering) valuable property, art, money. Thinking about it, I thought one of the following could have occurred: (Someone from) the Savelli family/the owner had to sell/trade/give the painting away for desperate reasons (like needing money, buying favors) and no official record was made of it. The family/owner gifted the painting in suspicious cooperations with certain individuals or parties and no official record was made of it. The family/owner had to flee their home and the painting was looted. The family/owner had been arrested, deported or killed and their possessions were confiscated by ruling powers or stolen by others opportunists. Nothing war or Nazi related! Turbulent 1942 Europe is a coincidence! Going down the wrong roads I've probably grown too used to just googling the obvious pieces of information first to see if more new information would easily pop op. In my summarized timeline above, it already looked quite obvious what might have happened with the painting. I even made a list of things I imagined had happened. But I didn't immediately follow that trail. I first decided to browse Wikipedia and do some general google searches into the painting, the painter and the year 1942. When that didn't lead to anything specific, I tried to do google searches into the painting and the previous and future owners, like for example the Savelli family. This didn't lead to much either. Then I decided to look up the painting in Italian ( La Negazione di Pietro ) combined with the year, the date, some related owner names, hoping to find some local news that maybe wouldn't pop up in English search results. No luck. After all that, I couldn't find any information that seemed to be leading to the answer of where this painting went. I was convinced I was overlooking something obvious and going down the wrong paths with these searches. So, I took a little break to reset. The obvious path reveals itself When I returned to this task, I looked at my notes. I wrote down what I thought might have happened to the painting and the family who owned it, so why hadn't I looked closer into that yet? Especially when I had such a specific date to work with too? I returned to google and searched: 14 May 1942 nazi art theft Savelli No, too specific. Why would anyone record the name of the family if the painting was obtained illegally or in a shady trade? So next I went for: 14 May 1942 nazi art theft Most results were speaking about nazi plunders, so I thought that might have been a more correct term for it, so I tried: 14 May 1942 nazi plunder Still no obvious result, but I wanted to give it one more go, just in case I wasn't wording it right yet: 14 May 1942 nazi stolen art There it was, something promising. One of the top results was a PDF on a website called looted art about the activity of the Einsatzstab Rosenberg in France. According to Wikipedia , this was \"a Nazi Party organization dedicated to appropriating cultural property during the Second World War\" . There are three places where the date appeared in the document. Firstly, there was an overview of all the dates Goering (aka Göring, a well-known Nazi minister) visited Musee du Jeu de Paume, where exhibitions would be prepared for him to personally view confiscated art, probably to pick some for his own collection. 14 May 1942 is on the list. In the second and third appearance of the date, the file mentioned that on that day he met with Dr. Alexander von Frey and Jan Dik Jr. to exchange art in Jeu de Paume. Reading the descriptions of the meetings and the paintings exchanged, Dik maybe seemed like a better candidate than Von Frey for having exchanged this painting. But, either way, the venue name is here: Jeu de Paume  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-4.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-3.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-3.webp"],"local_images":["blog_data/images/blog_9af62f7b4383_0.bin","blog_data/images/blog_9af62f7b4383_1.bin","blog_data/images/blog_9af62f7b4383_2.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-edward-scizzorhands-art-thief-challenge/","title":"37. Edward Scizzorhands Art Thief","status":"ok","retrieved_at":"2026-08-29T16:08:22.000208+08:00","text":"Walkthrough for Bellingcat's 'Edward Scizzorhands: Art Thief' challenge 03 Jul, 2025 Hi, welcome to this walkthrough of the Edward Scizzorhands: Art Thief challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but most likely there are many different ways of reaching the same results. Finding the painting We're shown a small piece of a painting and are told that a part of this painting has been cut out and stolen in 1982, from a cathedral. The cut-out canvas circulated for 35+ years until it was found during an auction. We have to find out the name of the auction house where this happened. The first question that arises is: what painting is this? We're only getting to see a small part of it. I can't search for information about it if we don't know anything about it. I did a reverse image search with the RevEye browser add-on. Google, Bing and Yandex all couldn't find the exact right full painting. However, TinEye gave me a promising lead. I clicked on the image and saw that it was a match for the given fragment on Bellingcat. From that link name we can now guess the name for the painting and painter. So I googled for martyrdom saint sebastian federico barocci . From this search I easily found some websites like Wikimedia and A&Aeportal that confirmed that this is the correct painting. These links also confirm that the painting hangs in a cathedral, just like the challenge prompt stated. Now that the painting is no longer a mystery, it was time to look into the crime and its resolution. Finding the story behind the crime Whenever I googled martyrdom saint sebastian federico barocci stolen or anything related to that, there was one article from Finestre sull'Arte that kept popping up. From the first sentences that are readable, it seems like an instant solution to all our questions. One problem, it's behind a paywall. Visiting an archive link doesn't remove it, nor does visiting the link through a new incognito browser window. Too bad. I continued on to a different link for art news , where there's a short piece about the theft, lacking any real useful information. However, it does link to its news source, which is an Italian news article. I tried reading the Italian news article with google translate. In it, I saw a new piece of information: the name of the father of the person who was depicted on the square of canvas that was cut out and stolen. Curious about this new information, I googled martyrdom saint sebastian federico barocci benedetto bonaventura . Of course the top result was that paywalled article again, grrr... But right under there was a link to a thread about the theft on X from Rembrandt's R👀m 🖌 (maaikedirkx) . This three post thread tells the story of the theft and tells about the item's reappearance on an auction. And luckily for us, a screenshot of the auction's webpage is included. I clicked on it and saw the name of the auction house in question in the top left corner: Wannenes . And voila, there's our answer.  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot01.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot02.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot03.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot04.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot05.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot06.webp"],"local_images":["blog_data/images/blog_4e845964b896_0.bin","blog_data/images/blog_4e845964b896_1.bin","blog_data/images/blog_4e845964b896_2.bin","blog_data/images/blog_4e845964b896_3.bin","blog_data/images/blog_4e845964b896_4.bin","blog_data/images/blog_4e845964b896_5.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-failed-to-detonate-challenge/","title":"46. Failed to Detonate","status":"ok","retrieved_at":"2026-08-29T16:09:10.916057+08:00","text":"Walkthrough for Bellingcat's 'Failed to Detonate' challenge 04 Aug, 2025 Hi, welcome to this write-up of the Failed to Detonate challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received an image of a corroded item, some type of weapon or military item can be assumed from the description of the challenge. Our task is to find its model and category. Looking closely at the item, the first thing I noticed was that there was text on it. It's not very readable, but three distinct kanji can be seen before the rest of the text wraps around the side. So, most likely we're dealing with a Chinese or Japanese item. I tried to get the kanji into text by drawing them in this kanji recognition website . To the best of my abilities, I came to: 无榴一. I tried to google 无榴一 and 无榴, but didn't get any results that would help me along. So I decided to put a pin in that path for now. Looking for resemblance My next step was to do a reverse image search on the picture posted by Bellingcat. I browsed through the search results until I found an image that resembled the item most closely. My attention was also drawn because the preview mentioned it was Chinese. Clicking the image, I landed on this forum thread where someone asked for a fuze to be identified. Scrolling and reading along, I saw many interesting old drawings and schematics of fuzes that looked very much like the picture we received, at least in external design. This was the first time I saw such items labeled as fuze , so I noted that down. A part of the thread's conversation goes: \"Soviet prototype of the “卡-3”\" \"do you mean that an analogue of KTM-1?\" \"The original Soviet version was the KTM-3\" This drew my attention because they're new terminology to look into. Also, I know that the third kanji on the item ( 一 ) means 1, so KTM-1 sounded like the most relevant thing to look more into first. I decided to google: Chinese KTM-1 fuze I went to the tab of image results, to see if I could find pictures that would resemble the original picture more than before. Immediately in the first row I saw a fuze with kanji that I recognized! The image led to this page from CAT-UXO. There's lots of additional information here, but most importantly, it looked very much like the one from the original picture. The one from Bellingcat looks a little more weathered, corroded, maybe partially broken. But in comparison: the item's text, general shape and design, and hole location all seemed to be a match. And it turned out to be correct. The final answer is: Type 1 fuze .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-7.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-6.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-6.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_04-3.webp"],"local_images":["blog_data/images/blog_7cf32d7305ba_0.bin","blog_data/images/blog_7cf32d7305ba_1.bin","blog_data/images/blog_7cf32d7305ba_2.bin","blog_data/images/blog_7cf32d7305ba_3.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-far-right-fashion-challenge/","title":"74. Far-right Fashion","status":"ok","retrieved_at":"2026-08-29T16:11:29.105552+08:00","text":"Walkthrough for Bellingcat's 'Far-right Fashion' challenge 11 Feb, 2026 Hi, welcome to this write-up for the Far-right Fashion challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. The challenge We've been given the logo of a far-right fashion brand. The logo contains a symbol used by far-right groups. This challenge is surprisingly quick to solve if you know of Bellingcat's Monitoring Glossary . Looking at the symbols in the Visual Symbols category, I reached the fasces symbol and saw a familiar symbol. The log-version is a bit hard to recognize in the fashion logo, but if you look at the picture of the graffiti, it's easier to see the comparison between the logo and a stylised version of the fasces. I also looked up the fasces symbol on Wikipedia . The symbol knows many uses and versions, but scrolling down, there is one rendition that looks very similar to the logo too. It's the version that was used by the Italian air force during the Fascist period. It also has a circle around it. So the answer for the challenge is: fasces  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/comparison-4.webp"],"local_images":["blog_data/images/blog_8bf494ab83aa_0.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-fascist-echoes-challenge/","title":"72. Fascist Echoes","status":"ok","retrieved_at":"2026-08-29T16:11:11.472472+08:00","text":"Walkthrough for Bellingcat's 'Fascist Echoes' challenge 08 Feb, 2026 Hi, welcome to this write-up for the Fascist Echoes challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a picture of a hate symbol painted on a weapon. This weapon was used in an attack that led to quick legislation change. We have to find both the date of this legislation change and the name of the historic political movement that used the hate symbol we can see on the weapon. To me, finding the political movement seemed like the easier task of the two. If I could find the name of the symbol, I could research its origin and historic movements related to that symbol. For the legislation change, I expected to have to start with identifying the weapon. If the weapon would lead to the attack, I'd be able to look into the political consequences of the attack. Hopefully that would lead to concrete law changes with dates attached. The symbol The symbol on the weapon is a grid that consists of three vertical and three horizontal lines crossing each other. I found it in Bellingcat's Monitoring Glossary under Cross of the Archangel Michael , where its relationship with the Iron Guard is explained. It's also in Wikipedia's list of symbols designated by the ADL as hate symbols as St. Michael's Cross. Clicking it leads to the page about the Iron Guard , an interesting page with a lot of background information. The second half of the answer is thus: Iron Guard . The legislation change Coincidentally, reading the Iron Guard article on Wikipedia, eventually I reached a part called Iron Guard in other countries . It reads: \"The Archangel Michael's Cross was among the symbols emblazoned on the firearms used by Brenton Tarrant during the 2019 Christchurch mosque shootings and by Payton S. Gendron during the 2022 Buffalo shooting.\" This already gave me two options to look into regarding the attacks for which a weapon with that symbol was used. Would pictures of the weapon be placed online? If so, I could compare them to the picture we've received by Bellingcat. I went to Google Images and looked up: christchurch shooting weapon There are a lot of pictures of the weapon the attacker used to be found online. This image in particular caught my eye, which led to this article that contains a plethora of photos. The weapon is a match with the one of the Bellingcat picture. Now that I knew for sure that the picture was related to the Christchurch mosque shootings, I could start my search for the legislation that was changed because of it. I queried Google for: christchurch shooting legislation change One of the top results leads to this page that gives an overview of all amendments to the Arms Act in 2019. It confirms that this has happened due to the attack, stating: \"Following the 15 March 2019 terrorist attack on Christchurch masjidain, then Prime Minister Jacinda Ardern announced that New Zealand’s firearms laws would change.\" Investigating the list from the top, the first item is an order . It states it comes into force on 21 March 2019, but doesn't use any official terms for it becoming law, which made me question whether this order was what I was looking for. The Bellingcat challenge asks what date did the new legislation come into force? -but does an order count as legislation? I looked up what types of legislation exist in New Zealand and read on this page that an order counts as secondary legislation. However, at the top of the order it says that it has been revoked on 12 April 2019 (by section 75 of a newer Act labeled 2019 No 12), making it seem as if it had been replaced by something else. I was unsure of this order, so I kept looking just in case something more obvious would appear. The second item in the list is simply an introduction to Parliament, so I skipped looking into that item. The third item in the list looked promising, because it read: On 11 April 2019, following a truncated Select Committee process, in which over 13,000 public submissions were received and considered, the Arms (Prohibited Firearms, Magazines, and Parts) Amendment Act 2019 received Royal Assent and became law on 12 April 2019. This was an Act, and it had a date of assent: 11 April 2019. It made sense that this most likely replaced the temporary order that was revoked on 12 April 2019, because it said it was revoked by a section of the Amendment Act 2019 (2019 No 12). To me it seemed more likely that the Bellingcat challenge was referring to this new, full Act, although I still did find the wording of the questions a bit confusing. Because the main list states that the royal assent for this Act was received on 11 April 2019 and thus it became law on 12 April 2019, I went with the latter date, which turned out to be correct. So the definite full answer is: 12/04/2019 Iron Guard  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/001_ironguard.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/002_comparison.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/003_law.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/004_revoked.webp"],"local_images":["blog_data/images/blog_6ecc81dfd176_0.bin","blog_data/images/blog_6ecc81dfd176_1.bin","blog_data/images/blog_6ecc81dfd176_2.bin","blog_data/images/blog_6ecc81dfd176_3.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-fixed-narrative-challenge/","title":"75. Fixed Narrative","status":"ok","retrieved_at":"2026-08-29T16:11:35.99156+08:00","text":"Walkthrough for Bellingcat's 'Fixed Narrative' challenge 11 Feb, 2026 Hi, welcome to this write-up for the Fixed Narrative challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. The challenge We've received a picture of a post with a sticker promoting a far-right active club. In the background two buildings are partially visible. We have to identify the symbol used on the sticker and the city it has been placed in. The symbol Browsing through Bellingcat's Monitoring Glossary , the symbol can be found in the category of visual symbols , under Celtic Cross . A little more background on the use of the Celtic Cross by far-right movements can also be found on Wikipedia . This is already the second half of the challenge solved: celtic cross . The city In the background of the picture are two buildings. The one on the right appears to have decorations and may be on the older side. The one on the left looks like a (maybe Eastern European) 20th century apartment block to me. I expected the left building to be more easily identifiable, because a larger portion of it is visible, the shape with the curve is quite distinct, and the antennas (?) on the top are very noticeable. I started with a reverse image search on the picture through Google, but limited the search field to just the left part of the picture with the building. There were many matching pictures to be found in the results, like for example this stock picture that calls the building Albania Palace Building in Belgrade. So, next up I googled: albania palace building belgrade Again I was met with many results with pictures of buildings that looked identical to the part of the building that's visible in Bellingcat's picture. This page gives some really good close-up pictures from several angles. There is a curve in the building's shape, there are two similar antennas on the top, the identical amount of windows are present per floor and these windows have shutters, on the top floor there's an AC unit in the same location, and on the top of the building there is the same edge with two wider and three smaller parts sticking out more than the rest of the roof's edge. My earlier search query also led to Palace Albanija's Wikipedia page where it's location in Belgrade is confirmed. And with that we have the full answer for the Bellingcat challenge: Belgrade, celtic cross . The post This is beyond the scope of the original challenge, but I got curious to see if it was possible to spot the specific post the sticker was placed on. I looked up the building on Google Maps and switched to satellite view with 3D on. This made it easier to see from what direction the picture might have been taken. Comparing the curve at the front of the building helped with this. I entered Google Streetview to look at streets that were west of the building. In Sremska street, looking toward Palace Albanija, there is a building on the right-hand side that looks similar to the picture on the right side of the Bellingcat picture. Above is a comparison between the building from Google Streetview in Sremska next to the building in Bellingcat's picture. The picture from Bellingcat seems to be taken from quite a low angle, which makes sense if the sticker was placed at eye-height or maybe slightly lower. Was it that post? The two buildings look identical. A lamp post further west into the street doesn't allow for a view of the right-side building. There are no black wires visible on Google Streetview, but the most recent footage is from 2013. On more modern pictures many black wires are visible in the air. Was the picture taken somewhere from here, angled up? Was the sticker on that specific post? I'm not completely sure, a lot in the area could have changed too since 2013. But for now it's my best guess. :)  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/001_building.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/002_angle.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/003_view.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/004_screenshot.webp"],"local_images":["blog_data/images/blog_d65fbd60198b_0.bin","blog_data/images/blog_d65fbd60198b_1.bin","blog_data/images/blog_d65fbd60198b_2.bin","blog_data/images/blog_d65fbd60198b_3.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-fresh-faced-challenge/","title":"31. Fresh Faced","status":"ok","retrieved_at":"2026-08-29T16:07:57.158637+08:00","text":"Walkthrough for Bellingcat's 'Fresh Faced' challenge 20 Aug, 2025 Hi, welcome to this write-up for the Fresh Faced challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. Finding the article We've received a screenshot from a newspaper article and with that we have to find footage of the interview visible in the screenshot. In the picture, Eliot Higgins is pointing at a laptop, accompanied by a text below it that reads \"Bloger Eliot Higgins svaki dan pregledava nove snimke\" . I put the text into Google Translate with the 'detect language' setting on, and found out that it's Croatian. It read: \"Blogger Eliot Higgins reviews new footage every day\" . I reverse image searched the screenshot and found a link to the news article on Google. It's an article written in Croatian, with a Croatian TLD (.hr), which aligned with the screenshot language. Finding the footage Scanning the article, I saw that the picture credits were 'Tomislav Krasnec/VLM' . The author of the article was also Tomislav Krasnec. Assuming I'd have the best luck finding any footage on Youtube, I went over there and typed in Tomislav Krasnec Eliot Higgins (the author of the article + the subject of the article) in the search bar. Fortunately, the thumbnail of the top result looked very familiar, and the uploader name too! Watching the video , it's clear that this is the interview related to the screenshot. Higgins can be seen in the same outfit, pointing at the same laptop with a cute green creature on top. The furniture in the background looked the same too. I took the relevant part of the link that was requested by the challenge, which turned out to be the correct answer: k7qd4Y6QAfY .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-13.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-12.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-11.webp"],"local_images":["blog_data/images/blog_a0c578ced20d_0.bin","blog_data/images/blog_a0c578ced20d_1.bin","blog_data/images/blog_a0c578ced20d_2.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-funny-money-challenge/","title":"36. Funny Money","status":"ok","retrieved_at":"2026-08-29T16:08:07.93481+08:00","text":"Walkthrough for Bellingcat's 'Funny Money' challenge 13 Jul, 2025 Hi, welcome to this walkthrough of the Funny Money challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but most likely there are many different ways of reaching the same results. Looking for the case Not knowing anything about (rare) coins, I decided to go for a broad google search first. I looked up: 1933 rare coins Immediately multiple results pop up for the 1933 double eagle . Besides the relevant Wikipedia page and some general informational website, there's also one link about double eagle coins being melted down, recovered, stolen, and it talks about their scarcity and monetary value. This all sounds quite eventful. In my next google search tried to be a bit more concrete, since we're looking for a court case and the double eagle coin seems a like a likely candidate. So I looked up: 1933 double eagle court case Lots of results! They all seem to go about the Langbord family going up against the U.S. Dept. of Treasury for the right to keep their 1933 double pennies, which have been confiscated. For example, there's this article about the case, this article about the appeal and, very handy, this post that gives an overview of the whole saga. Looking for the attorney Reading deeper into all of the articles, the Langbord family seemed to have used the same family attorney every time: Barry Berke. However, the Bellingcat challenge page won't accept that answer! What's up with that? Well, the easy way to solve this is to do a google search for Barry Berke and you'll find out he has a middle name. But I went to long way and looked up a PDF version of the official court document so I could check the names of all the participants. There I saw the full name. So, in conclusion, the solution for this challenge is Barry H. Berke .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-3.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-2.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-2.webp"],"local_images":["blog_data/images/blog_507c41233492_0.bin","blog_data/images/blog_507c41233492_1.bin","blog_data/images/blog_507c41233492_2.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-ice-ice-baby-challenge/","title":"54. Ice Ice Baby","status":"ok","retrieved_at":"2026-08-29T16:10:53.274032+08:00","text":"Walkthrough for Bellingcat's 'Ice Ice Baby' challenge 13 Sep, 2025 Hi, welcome to this write-up for the Ice Ice Baby challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a picture of a hand holding up a dessert in front of a blurred background with buildings, cars, people, a street sign, maybe some decorations and tiny lights. We have to find the shop where this dessert was bought. My first thoughts were: The background looks a little touristy, maybe reverse image can pick up on it. The colors and shapes of the street sign could be looked up. The dessert looks like ice cream, or it looks like something that could melt, but it's in pristine condition. I doubt anyone would buy a dessert and walk around with it for several streets before taking a picture like this. I assume it has just been bought, very close to the location of where the picture has been taken. The dessert is in a transparent cup with a transparent spoon. It looks quite small, like it's a luxurious delicacy. It looks quite unique. Finding the place I started with a reverse image search through Google, but only selected the top part of the picture, above the dessert. Immediately many results came up for Covent Garden in London. I clicked on the images that seemed to show the same building as in the picture, and the results described this as the Covent Garden market building . For example, this result on Wikimedia seemed to show the building from the same angle. In the description it stated captured from Russell Street . I looked up Covent Garden on Google Maps and put myself on Russell Street in Streetview . Hm, that does look the same! The tree trunk (marked in green), the location of the parked cars (blue), the sign (orange) and the building in the background (yellow). It looks like the picture was taken standing on the sidewalk on the right side from this angle. Finding the dessert I started looking around on Russell Street in Streetview, close to the Covent Garden market building, at all of the shops that could be selling ice cream to go. However, many buildings that were quickly visible, looked like restaurants for dining in. When I clicked Santa Nata , the pop-up said Portuguese custards tarts, to go . That didn't really sound like ice cream, but the place did look like it might serve unique, small delicacies. I clicked the pictures in Google of the items and the menu, and it didn't seem to have any ice cream. I saw this sign on one of the pictures, but the cup wasn't see-through. I looked at a few other shops in the area, but nothing really came close, so I returned to Santa Nata. This time, I checked their Instagram account. Ah! Multiple reels of soft serves! Served in a transparent cup, with a transparent spoon, quite small, with a cute swirl. The only thing that might be missing is the little cookie. Maybe they aren't served with every flavor of soft serve, but I can also easily imagine the person who took the picture not being able to resist eating that already before snapping a picture. I wouldn't be able to wait. I put in the answer and the screen turned green. The answer is indeed Santa Nata .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-15.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-14.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-13.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_04-8.webp"],"local_images":["blog_data/images/blog_fb9e2436f002_0.bin","blog_data/images/blog_fb9e2436f002_1.bin","blog_data/images/blog_fb9e2436f002_2.bin","blog_data/images/blog_fb9e2436f002_3.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-iconography-of-hate-challenge/","title":"71. Iconography of Hate","status":"ok","retrieved_at":"2026-08-29T16:11:07.958591+08:00","text":"Walkthrough for Bellingcat's 'Iconography of Hate' challenge 07 Feb, 2026 Hi, welcome to this write-up for the Iconography of Hate challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. The challenge We've received a graphic containing six symbols. We have to find out which of these are commonly used by hate groups. I recognized some of these symbols, unfortunately due to local far-right activity. Usually these groups use a variety of runes in their logos, or their banners and posters. The runes The easiest way to look up any of the symbols would be to go to Bellingcat's Monitoring Glossary . Looking through the category visual symbols , one can encounter symbol 6 , symbol 2 and symbol 3 . Alternatively, one can look up these symbols in a search engine by describing the symbols or reverse image searching for them. Combining these searches with terms such as hate group , hate symbol , far right or dog whistle will quickly lead to several helpful pages. Doing this for symbol 2 , 3 and 6 brought me to the Wikipedia pages for these three runes and their connections to modern day hate groups. I also found three other helpful tools that I now use in addition to Bellingcat's Monitoring Glossary: Wikipedia's List of symbols designated by the ADL as hate symbols Hate On Display's database of hate symbols A publication by the Bundesamt für Justiz about right-wing extremist symbols, signs and banned organizations They're all convenient tools to save. They have much overlap, but all contain some unique information as well. The other symbols I tried to look into the other three symbols to see if there was any connection to hate groups. They can't be found in any of the hate symbol guides posted above, but they might be very obscure. For symbol 1 I didn't see the need to do a reverse image search, because it was simply an arrow pointing downward. It doesn't look like a rune because of its thin form. I did a variety of search engine queries like: down arrow hate symbol down arrow far right arrow pointing down hate group arrow pointing down dog whistle I couldn't find anything related to extremism. For symbol 4 and 5 I did a reverse image search in Google and added a mix of words related to hate groups. Awkwardly I hoped nothing would pop up, because symbol 4 looks like something I've used in every PowerPoint presentation in my life. But once again I couldn't find anything related to hate groups, past or present. With that, the correct answer to make the screen turn green is: 2, 3, 6  ","image_urls":[],"local_images":[]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-larger-than-you-think-challenge/","title":"50. Larger than you Think","status":"ok","retrieved_at":"2026-08-29T16:10:11.360395+08:00","text":"Walkthrough for Bellingcat's 'Larger than you Think' challenge 18 Aug, 2025 Hi, welcome to this write-up for the Larger than you Think challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a picture with a piece of ordnance. It isn't very clear, but there are a few things that I noticed: The description says this is a fragment of something, so it must be quite big if this piece is only a part of it. The description mentions it is a missile type . It seems to have a blue/grey color, although it could be due to weathering or other damage. There is a curve in its shape. On top there is a piece sticking out, maybe it was a kind of wing, maybe it was something else. I expected this to be a long search, but it was relatively quick thanks to resources I had already found and saved in the previous challenges from the Hidden Hazards series. Missile search I tried to do a reverse image search on Bellingcat's picture. No exact matches showed up, but there were a lot of results about Russian missiles used in Ukraine. I went to CAT-UXO, an informational website about explosive ordnance that I stumbled upon during the Failed to Detonate challenge . I sorted all missiles to only show those with country of origin Russia and country used in Ukraine, and got 71 results . I browsed through them, but found it very difficult to recognize or identify any specific parts. Because there was a large chance that this challenge was about a weapon used in Ukraine, I went to the GICHD explosive ordnance guide for Ukraine, third edition , that I found and saved during the Target Not Acquired challenge . Missiles start at page 219. There were about 12 of them, and only one looked remarkably close to the original picture. Especially in the two pictures of the individuals clearing fragments, the curve of the object and the parts that stick out seemed to resemble the object in the Bellingcat picture. It looked like the same blue-grey-hue too. I was pretty sure at this point, but wanted to find a little more information just in case. When I googled kh-101 missile I arrived at an article from Bellingcat about the identification of a missile used in an attack on a children's hospital as a Kh-101. I recognized the picture, because it was also used in the Bellingcat newsletter to announce these latest challenges. Hmm... In the article the authors link to this identification manual for a previous Kh-101 strike. On page 41 there is a part visible that looks almost identical to the part visible in the challenge picture. Googling the marking that is mentioned next to it (9-Е-2648) led to many more articles about Kh-101 attacks and similar parts found. So, by now I was quite certain and put in the answer, which turned out to be correct. It is: Kh-101 .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-12.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-11.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-10.webp"],"local_images":["blog_data/images/blog_ee235d705ea6_0.bin","blog_data/images/blog_ee235d705ea6_1.bin","blog_data/images/blog_ee235d705ea6_2.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-mummys-little-helper-challenge/","title":"39. Mummy's Little Helper","status":"ok","retrieved_at":"2026-08-29T16:08:51.529881+08:00","text":"Walkthrough for Bellingcat's 'Mummy's Little Helper' challenge 30 Jun, 2025 Hi, welcome to this walkthrough of the Mummy's Little Helper challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but most likely there are many different ways of reaching the same results. The search for the ushabti We're shown a picture of a collection of ushabtis with some background information on these ancient figurines. One of them has been purchased in London in 2013 for £937.50 and we must find out which one, at which auction house, and who the ushabti was meant to serve. My first google search was for ushabti £937.50 london , expecting this might show an overview or log for the sale. One of the top results is indeed an auction page for one of the ushabtis from the picture, namely the turquoise one. Checking the lot information, I saw that the year of the sale date corresponded with what we're looking for (2013) as well as the price (£937.50 inc. premium) and the location (London). The auction house where this took place is Bonhams in Knightsbridge. In the prompt we were told that ushabtis have an inscription on them with information about who they're serving. Conveniently this inscription is placed on the item page of the auction website too. In it I could read that the figurine is serving Semataui , son of Sheri. So, the final answer will be: Bonhams Semataui  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01.webp"],"local_images":["blog_data/images/blog_28ce841a2a0b_0.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-on-the-right-track-challenge/","title":"77. On the Right Track","status":"ok","retrieved_at":"2026-08-29T16:12:02.01821+08:00","text":"Walkthrough for Bellingcat's 'On the Right Track' challenge 28 Aug, 2026 Hi, welcome to this write-up for the 77. On the Right Track challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a picture of GeoPeter . It's a selfie made while travelling. We need to geolocate him and find the name of the neighborhood he's posing in for his picture. I first inspected the picture to gain as much knowledge as possible before starting my search. This could help me get some context for what I'm looking for. I made a list for myself and noted: It's a man wearing a scarf and hat: is it a cold environment? The environment looks quite European, maybe Eastern Europe. The man is wearing a pin with the flag of Sweden and Latvia: is that where he is? It looks like he's at a train station. In the distance there is a tower of some sort. There's a building in background. It's vague, but with a big logo and a bright color, it might be a supermarket. It looks like there's maybe also a bus station in the background. The country There are quite a few points to get started with, but I first wanted to limit my search area as much as possible. Because of the pin GeoPeter is wearing, and because of the hint in the Bellingcat challenge text ( \"Hidden throughout are a few details that give away my location.\" ) I thought the country was most likely Sweden or Latvia. This might be a bold presumption to make, but because I had to start somewhere, I decided to go for it for now. If I stumbled upon dead ends, I could always remind myself that the country choice was potentially flawed, and reevaluate. My initial expectation of the picture was that it was located somewhere in Europe, maybe in the east of Europe. If I had to limit my choice between Sweden and Latvia, I found Latvia the more likely option. Maybe it's hours of playing GeoGuessr, maybe it's my limited knowledge of Scandinavian environments, but the location in the photograph didn't seem very Swedish to me. So Latvia was left over as first choice. Because I thought this picture was taken at a train station, I went to Google Maps and dropped myself into the Streetview of a variety of random train stations in Latvia. I simply wanted to see if the general look came close to the picture or if I was completely off. No random train station looked exactly like the picture, but based on how they looked I thought it was certainly possible that the Bellingcat picture was taken in Latvia. How I didn't get there: the tower So, my starting point was Latvia, and I was looking for a train station. I could try to look at every train station in Latvia, but that would be many hours of inefficient work. So I tried to look for identifiers in the picture that would be more rare. Looking at the selfie and rereading my observation list, I thought the odd tower in the background would be a good building to focus on. Surely there can't be that many towers like that? But what kind of tower was it? It felt impossible to look up the location of towers if I didn't even know what type of tower it was. I did a reverse image search on only the part of the picture that showed the tower. It didn't really help that the tower is partially hidden in the picture. I had no results that were an exact match, but I did have a lot of types of tower pop up. I noted communication, observation, railway, radar, radio and water towers. So which type was it? I wasn't sure. I decided to look up every type of tower in Google Images and compare the results to the tower in Bellingcat's picture. For every type of tower I did a separate query, and one query with \"Latvia\" added to it. So, eventually I searched all the following queries in Google Images: communication tower communication tower latvia observation tower observation tower latvia railway tower railway tower latvia radar tower radar tower latvia radio tower radio tower latvia water tower water tower latvia It felt a little silly to do, but I have no knowledge of towers whatsoever, so I was trying to spot any sort of comparison. The tower in the selfie has a notable upside down triangle shape at the top. The only image results that showed anything remotely similar were the 'water tower latvia' queries. These towers were not very high, just like in the picture. They were usually made up of two parts: the straight tower, and the top part that looked like a little round house, a triangle, or a different shape. One I saw even had an upside down triangle shape. I was not really convinced, but for now it was the best lead I had so far. I thought that the tower in the background of the picture might be a water tower. So, could I find that specific water tower from the selfie? I tried to redo the reverse image search on the tower, but added a variety of search terms along with it, such as water tower , latvia , and water tower latvia . I found a lot of water towers that looked a little bit like the one I was searching for, like this one , this one and this one . Because all of those results were on the Virtual Globetrotting website, I tried to use their search too. I limited their search for Latvia as the country and water storage towers as the category. I looked through all the results, but unfortunately no luck. Was there some resource elsewhere that listed all water towers in Latvia that I could check? I decided to look on Google for the following search terms: map water towers latvia I found this Wikimedia page but once again I couldn't find an exact match. I was starting to doubt that the tower in the picture was actually a water tower. I decided to try one more method with the water tower theory. I wanted to try out Bellingcat's search tool for OpenStreetMap. The guide for it can be found here . I was curious to see if I could find a match for a train station and a water tower being within a certain distance of each other in Latvia. I looked up the correct tag for a water tower and for a railway station . I tried to look for those two within 500 meters of each other I had about 20 results. Excitedly I looked them all up on the map and then checked Google Streetview footage or uploaded pictures by users on Google Maps. I didn't find the location from the Bellingcat pictures. How come? I thought of a few reasons: The water tower might not be a water tower. The water tower might not be tagged as such in OpenStreetMap. The water tower might be more than 500 meters away from the station. There was a variety of ways to test these theories and to keep search for the water tower, but I had too much doubt and wanted to let the water tower go for now. I needed a fresh approach. How I did get there: the supermarket I looked at my initial observation list and noticed that I had speculated that the building in the background might be a supermarket. I decided to try Bellingcat's search tool for OpenStreetMap again, this time looking for a train station and a supermarket within 500 meters of each other. A supermarket seemed to me more likely to be tagged on the map than a maybe-water tower. I had 15 results within Latvia. Once again I looked up all of the results on the map (from left to right) and then checked Google Streetview footage or uploaded pictures by users on Google Maps. Pretty quickly I stumbled upon a view that was very familiar ! It appears that GeoPeter was at Sloka Station in Latvia. The metal poles over the railway look the same. In the background the tower is visible . Walking around with Streetview the tower, the supermarket and the bus station are all visible next to the train station. This was definitely the location from the picture! So the answer was Sloka . Why didn't the tower search work? I went back to Bellingcat's search tool and once again tried to search for a railway station and a water tower within 500 meters of each other, but got zero results in the Sloka area. I checked OpenStreetMap and both the railway station and the water tower are labeled as such (so it was a water tower after all). I checked the distance and they are within 500 meters of each other. Why didn't the tool give this location as a result for the search for the water tower? I still have no idea. If you do know, please tell me ! I'd love to know if I did something wrong in that search, so I can improve (and correct myself here if I made a mistake). Either way, I got there at the end with the supermarket search. The definite answer was indeed Sloka .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/001_pin.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/002_tower.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/003_search-1.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/004_maptermstower.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/005_maptermssupermarket.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/006_map.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/007_supermarket.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/008_openmap.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/009_zeroresults.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/010_330meters.webp"],"local_images":["blog_data/images/blog_edc6298762bb_0.bin","blog_data/images/blog_edc6298762bb_1.bin","blog_data/images/blog_edc6298762bb_2.bin","blog_data/images/blog_edc6298762bb_3.bin","blog_data/images/blog_edc6298762bb_4.bin","blog_data/images/blog_edc6298762bb_5.bin","blog_data/images/blog_edc6298762bb_6.bin","blog_data/images/blog_edc6298762bb_7.bin","blog_data/images/blog_edc6298762bb_8.bin","blog_data/images/blog_edc6298762bb_9.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-proceeds-of-war-challenge/","title":"40. Proceeds of War","status":"ok","retrieved_at":"2026-08-29T16:08:56.248345+08:00","text":"Walkthrough for Bellingcat's 'Proceeds of War' challenge 01 Aug, 2025 Hi, welcome to this walkthrough of the Proceeds of War challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First things first For this challenge we've received an image of three ritual daggers and a little bit of backstory on them. We have to find the presumed nationality of a dark web seller. My first thought was that I'd need to know what these daggers are called. Or I'd need to know in what kind of collection they belong, since from the picture it looked like they were in a display case in a museum of sorts. Knowing these things would enable me to look up more information about them more easily. Finding the daggers The first thing I did was to do a reverse image search on the provided photo of the three fancy daggers. I got a lot of results for daggers that looked differently and stock pictures of the exact same daggers without any useful information. But two results grabbed my attention. The first one was a picture on Flickr, which showed more of the case the daggers were displayed in. It also showed the floor, a part of the wall, a reflection of some paintings on the wall, and a label with a QR code. Unfortunately, the QR code didn't work and the information on the label didn't help much in terms of names or terminology. The second notable link was to a blog post in Russian on a rating website. The post was made for a specific location: Potocki Palace, in Lviv. Scrolling through the post, it has a lot of pictures of the inside and the collections displayed. The daggers made an appearance! The post mentioned that in the Potocki Palace , the writer visited the Lviv Art Gallery . Looking that up, it does indeed seem that the Borys Voznytsky Lviv National Art Gallery is located in the Potocki Palace, in Lviv. All this information seemed related and relevant, since we read on Bellingcat that the daggers were originally displayed somewhere in Ukraine before being moved. I put a pin it for later. I now knew that these pieces were probably displayed in the Potocki Palace in Lviv, but the reverse image search didn't lead me to concrete titles, collection names or articles about those specific items. So I wanted to do a more general google search to see what else I could find. Finding the collection The Bellingcat prompt referred to the daggers as Asian pieces detained by the SBU in 2023 . So I searched google for: Asian collection sbu 2023 Because of the ongoing Russian invasion of Ukraine, I got a lot of very recent war results that didn't lead to the topic I was searching for. So I narrowed it down to results from before 2024: Asian collection sbu 2023 before:2024 I spotted a very promising link! But in the preview I saw a reference to Chinese collection so I wanted to try one little adaptation before reading more and looked up: Chinese collection sbu 2023 before:2024 Now the before mentioned promising link showed up again, along with a second one. Time to investigate. The first news article I saw , from June 20th 2023, spoke about detaining the Chinese parts of the \"Platar\" collection, that included items like ritual daggers, at the border of Lviv. The second news article is from a day later, where a statement from the Platar museum claimed that the collection was being moved from Ukraine to Prague. Examination required for this was done by Borys Voznytsky Lviv National Art Gallery, they claimed. Ah, I recognized that Arty Gallery name, because in my reverse image search I suspected that that was the location of the daggers. The location added up (Lviv), the museum added up, the items being Chinese daggers seemed to be a hit too. So, I was now relatively sure these daggers belonged in the Platar collection, but not 100% certain yet. The first news article linked to the official website of the Platar collection . Using google translate, I looked around on the website and looked at all of the pictures of the art pieces, but very few were actually shown. The daggers, or any other Chinese-appearing art pieces, were not displayed. I navigated to the subsection called gallery . There I saw an article about an exhibition of part of the Platar collection at the Lviv National Gallery of Art . The interior in two images looked very familiar Comparing these two pictures, they resembled the pictures of the inside of the palace made on the Russian review site. The green walls, the display cases, the floor tiling, the art on the wall -all a match. I went back to the flooring in the Flickr image of the daggers, and compared it to the background of one of the pictures of the green art gallery rooms, and saw that the floor and the yellow wall seemed to be a match, although it was hard to spot! Based on all this, I thought it was now relatively certain that the Chinese daggers belonged to the Platar collection, that the Platar collection was being displayed in the Lviv Art Gallery, which was located in the Potocki Palace in Lviv. Then, for some reason, they were moved out of Lviv and detained by SBU. It was claimed that they were being moved legally to Prague, Czechia. But were they really heading there, in a fair way? Finding out where the daggers truly went The daggers were part of the Platar collection, and the news article stated that the Platar collection at that point belonged to Serhiy Taruta. So I decided to google: Serhiy Taruta platar One of the first interesting results was an article in PDF format . It doesn't give me any direct answers or leads, but it did provide me with a lot of general information about private artifact collections in Ukraine and I learned about black archeology. Always good to know some extra background info on what you're researching. Then I got to the most relevant search result: this art crime blog with a post from 2023 about the movement of art collections from Ukraine, that discusses the Platar case too. It also linked to this news article about law enforcement seizing artifacts in Spain. Bellingcat asked us what the presumed seller's nationality was, and it's starting to look like it might be Spanish. But I wanted to dig a little more. My next google search was: Spain Ukraine \"platar\" This led me to an article about pieces from Ukraine being seized in Spain . It goes more into Ukrainians and Spanish people being arrested, and how a criminal network was involved. The art crime blog wrote a post about it as well, where in it is stated that the antiquities were sold through a web of sales, one of which was identified in Madrid. Now I felt a little more secure in my 'presuming'. The presumed identity of the seller is Spanish .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_000.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-5.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-4.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-4.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_04-2.webp"],"local_images":["blog_data/images/blog_75a0f8f743ee_0.bin","blog_data/images/blog_75a0f8f743ee_1.bin","blog_data/images/blog_75a0f8f743ee_2.bin","blog_data/images/blog_75a0f8f743ee_3.bin","blog_data/images/blog_75a0f8f743ee_4.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-seems-fishy-challenge/","title":"51. Seems Fishy","status":"ok","retrieved_at":"2026-08-29T16:10:22.578472+08:00","text":"Walkthrough for Bellingcat's 'Seems Fishy' challenge 21 Sep, 2025 Hi, welcome to this write-up for the Seems Fishy challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a picture of a lobster on a rock and we have to find what animal used to live on that rock before the lobster took its place. Studying the picture closely, the first things I noticed were: Generally, it looks Mediterranean. There are boats on the left, so it's most likely a coastal town, with something like a harbor. There are white buildings to the right, with a restaurant/patio. The car has a white license plate with black text and a tiny bit of blue on the left side, so probably it's a EU country. It looks like it’s on a roundabout or traffic intersection of some sort. The lobster has no claws (might be a certain species?). Thinking about how to tackle this challenge, I saw two possible ways: Finding the specific lobster statue online, which could lead to more information about what it has replaced. Finding the specific location of the statue, and looking up that spot on Streetview to see what used to be there before. Looking for the lobster I first tried to see if I could find the lobster statue. Doing a reverse image search in Google, Bing, Yandex and Tineye didn't lead to any clues. It did, however, caused me to see hundreds of lobsters statues. Big and small. Public and private. Who knew there is such interest in lobsters. And please, Google, don't ever talk to me about Betsy the Lobster again. When reverse image searching didn't work, I tried several search engines with a variety of search queries about lobsters, statues, monuments, replacements, coastal towns with sea creatures, harbors, crustaceans, picturesque towns with sea animal decorations -you name it. I tried to look up the species of lobster, which I thought to be a spiny lobster, and tried to implement that in my searches to no avail. I tried looking into Mediterranean towns well-known for catching, exporting or serving lobsters. Nothing. I was starting to think that nobody on the internet had ever spoken about this particular lobster before. It was time to try a different approach. Looking for the spot Because I couldn't find the lobster, I decided to try to look for the area in the picture. Because of clues in the picture, I thought I'd have to limit myself to a EU country, most likely one with a Mediterranean coastline. I did a reverse image search on the Bellingcat picture, but limited the search area on the picture to the areas around the lobster. I mainly tried to focus on the white houses on the right side. I never got any specific results that seemed right, but there were some countries that kept popping up in the search results: Greece Albufeira in Portugal Andalusia region of Spain Ibiza Greece and a whole region in Spain seemed a lot to tackle, but I could check out the other two. I saw pretty quickly that the Portugal option didn't really fit. Ibiza looked more promising. I entered Google Maps and went around the coast of Ibiza. I searched closely for: a road very close to the sea (because of the boat being close to the road/buildings in the picture), a harbor of unknown size (maybe small if the picture only shows a few boats), with some buildings, maybe with a marked restaurant, maybe with an intersection or roundabout. Whenever something looked like a maybe, I entered Streetview to have a look. But, ultimately I couldn't find the lobster spot. Still being in doubt between Spain and Greece didn't help, so I tried to find out which one it was for sure. I knew that GeoGuessr players can recognize a lot of small things, so I tried to narrow the countries down again by other signs in the picture, such as traffic signs, sidewalk, bollards, etc. I checked with GeoHints , Plonk It and GeoTips . Yet I remained unsure. Not knowing what way to turn next, I tried to find a meta route. I looked at the metadata of the Bellingcat picture, but unfortunately there were no coordinates of where the picture was taken. Then I looked at the creator of the challenge, Charlotte Maher. I couldn't find any social media pictures of places she'd visited, except for her visit to the International Journalism Festival in Perugia, Italy. I did a real quick, hopeless search for lobsters over there, just in case. No... Stuck with the knowledge that probably somewhere along the coast of Spain or Greece this lobster is minding its own business, yet no new ideas on how to narrow that down to an actionable search that wouldn't take days. What now? Looking for a hint After getting stuck and taking a little break, I saw that Bellingcat had organized a livestream in which someone tried to solve this month's challenges. I watched the recording, hoping to reach a point where I could see a hint or a little push for how to continue on my own. The stream was helpful and I got a clue that made it possible for me to continue. However, I must admit I was a little bit disappointed about how rushed the livestream felt. I understand that solving mutliple challenges in a short amount of time is difficult and limits the amount of time that can be spent per search and the amount of details that can be discussed. But I learn a lot from watching people think out loud. I also learn a lot from seeing people going down the wrong path -why they initially thought it was good idea to pursue that path, and especially, seeing how and when they realize it might be better to switch tactics after all. I think with two commentators in the stream, and an active chat, all guiding and hinting along, it was a little overwhelming and hurried for my personal liking. Still, it was helpful. Anyway. When the stream reached a point where the Balearic islands were mentioned as the right area, I thought, oh! Wait! I checked out Ibiza, then left the region. Maybe I hadn't been thorough enough! I went to Google Maps and decided to start on Mallorca next. Once again, I tried to look for: First of all, a harbor Then a road close to the water (lots of places had lots of beach in between roads/houses and the water, which could be skipped), preferably two roads very close together Buildings, preferably on the second road from the water Maybe a marked restaurant Maybe an intersection or roundabout or other noticeable transition or coming together of roads with a spot for statues in between or next to it I started at Palma and went around the island from there, sometimes dropping into Streetview if something looked promising. Nothing really looked quite like it, until I encountered this area: I dropped in at the roundabout, because I saw two roads close to the water close by, along with a little rectangle shape that could be interpreted as a harbor. And I saw the lobster rock! I've drawn a few lines of things that I noticed the most when comparing the picture to the Streetview area, but there's lots more to match, especially when walking around a little. Here's the link for the specific spot. But, the rock was empty! No lobster, no other animal! But when I kept walking around a little, I entered a shot from September 2022. Finally, I got to see what the lobster replaced. It's indeed a seahorse .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/collage-1.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-17.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-16.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_04-10.webp"],"local_images":["blog_data/images/blog_8db87c26f875_0.bin","blog_data/images/blog_8db87c26f875_1.bin","blog_data/images/blog_8db87c26f875_2.bin","blog_data/images/blog_8db87c26f875_3.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-shattered-glass-challenge/","title":"91. Shattered Glass","status":"ok","retrieved_at":"2026-08-29T16:12:37.106338+08:00","text":"Walkthrough for Bellingcat's 'Shattered Glass' challenge 02 Jun, 2026 Hi, welcome to this write-up for the Shattered Glass challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. The challenge We've been asked to give the minimum peak overpressure required to shatter glass (in kPa). All of these terms were new to me, so I decided to first learn a little about what we were dealing with. I googled for: minimum peak overpressure kpa This led me to this link from a blasting mats manufacturer that explains a lot of the terminology. I saved some relevant parts into my notes: “ Blast pressure is the instantaneous rise in air pressure above the normal atmospheric pressure caused by the rapid expansion of gases from an explosion. […] Typical atmospheric pressure is around 14.7 pounds per square inch (psi) at sea level, so any pressure created by an explosion above that baseline is classified as overpressure .” “ The peak overpressure of a blast wave is the maximum pressure increase from the explosion.” \" Psi is a unit of pressure that measures the amount of force exerted on an area of 1 square inch.\" \"Kilopascals ( kPa ) are the metric unit of pressure. One psi is equal to 6.895 kPa .\" With this information I had a better idea of what was actually asked. I scrolled down a little more on the same webpage and found a graphic that stated that an overpressure of 1 psi can shatter glass. Since 1 psi equals 6.895 kPa, it meant that 6.895 kPa was the minimum amount of overpressure needed to shatter glass. Just to make sure that that information was correct, I tried to look up a second source. I googled: overpressure shatter glass kpa This brought me to this link that also explained that an overpressure level of 1.0 psi can shatter glass. So, that's another confirmation. To my confusion, the answer 6.895 was wrong. I wondered if Bellingcat wanted an integer as an answer, so I rounded up to 7 kPa, which did turn the challenge page green. So the correct answer is: 7 .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/image001.webp"],"local_images":["blog_data/images/blog_bf4696c52814_0.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-shifting-focus-challenge/","title":"52. Shifting Focus","status":"ok","retrieved_at":"2026-08-29T16:10:37.131059+08:00","text":"Walkthrough for Bellingcat's 'Shifting Focus' challenge 20 Sep, 2025 Hi, welcome to this write-up for the Shifting Focus challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a blurry picture and have to identify the address. Looking closely, these things were the first that I noticed: This looks like a gas station (the challenge text confirms this). There is a sign with a logo, probably of the gas station with its prices. There appear to be two types of prices, one is labeled blue, one is labeled red or green. The prices are 4-6 numbers long, one starts as 449 and the other as 566, maybe 588? There's a car, it looks like it has a yellow license plate. There are snowy mountains in the background. Surrounding lights are all on, it’s probably morning or evening. The building on the right has bright posters or ads in several colors. On the total right: maybe more gas pumps, like on the left side of the main building. I first went on some paths that didn't lead to the answer for this challenge, as you'll see (but eventually I did reach the answer). The Bellingcat newsletter stated \"Bellingcat staff brought home some souvenirs from their summer vacations\" . I kept this in the back of my mind, which wasn't the best thing to do here. I took that newsletter way too literally, haha! The misleading way Before showing the easy path to the right answer, let me first show you how I found out some information and got lost on some unfruitful paths. My first thought was that the scene in the picture looks like it is in the US. To get a feel of what American gas stations look like, I googled: US gas station I browsed the image results and then, to get a few options of what price signs might look like, I googled: US gas station prices I noticed an image result that was promising. It led to a stock image of a Chevron price sign. The logo looked like what was on the original picture. Next, I looked for: chevron gas station locations This led me to this map with all of the Chevron gas stations in the US. That's a lot! But at least a large part of the US can be crossed off. So far so good, right? Well, this is where I lost my way for a little while. Because I wondered: how could I narrow this down? I thought of two main ways: There are prices on the sign, so I could look in which region these were the right prices. Especially in summer 2025, these are remarkable numbers, hm? There are snowy mountains. I could look into mountainous regions. Especially such snowy mountains in the summertime, that can't be just anywhere? Here's a short recap of my next activities: The prices on the Chevron sign looked to be for a blue label and a green label, so I tried to look up if certain types of gas are related to certain types of colors. Green looked to be diesel most of the time. Blue was usually 'regular'. I tried looking up when prices of diesel would be higher than 5, but it was way too high of a price. The US average only got there in 2022 in this 5 year chart . I tried looking around more anyway, looking into forum threads where people complained over high 'regular' gas prices of over 4 in 2025, and only people in California were talking about it. I was in doubt. Just to be sure, I looked if Chevron was also active in Canada or other countries, and checked price numbers there as well, but that didn't really convince me either. In the US I remained. Next I tried to look up mountain ranges, especially ones that would get that snowy. Lots of areas, it seemed. But what mountains remained that snowy in summer? I didn't find any decent information about that, especially not with California's prices in the back of my mind. The mountains, the prices, the road and the gas station never really lined up . What I was doing was starting to feel silly. Was I overlooking something obvious? Was I interpreting data the wrong way? Or was I making assumptions that I shouldn't have? So, I got stuck, and then decided to start over in a different way. The easy way I didn't want to use reverse image search immediately at the start, because I wanted to challenge myself to look up data visible in the picture. But I had gotten stuck, so the time to apply reverse image search had arrived. In the Google search results, I saw multiple gas stations with mountains in the background, but one in particular caught my eye, because of the shape of the roof of the building (in addition to the mountains). When I clicked the matching link I was led to a list of gas stations in Sandy, UT. I started at the top of the list, looking at the pictures that came along with the address, and already it seemed to resemble what I'd been looking for quite a bit. I copied the correlating address (8655 Highland Dr., Sandy, UT 84093, United States) and looked it up on Google Maps and entered Streeview. Oh! The location of the pump, the mountains in the background, the prices sign, the positioning of the lights and road -every last detail looked like a match. And it turned out the be the correct address: 8655 Highland makes the screen turn green! However. As you might remember, as I copied earlier, the Bellingcat newsletter with the announcement for this month's challenges said \"Bellingcat staff brought home some souvenirs from their summer vacations\" . As you can see from the Streetview screenshot above, the prices from the gas station are way lower than the one's on Bellingcat's picture. Also, the mountains aren't as snowy as in the picture we've received. I walked through other moments captured in Google Streetview. The car almost always passed by in the months of June-August, and never can the mountains be seen with that amount of snow. It makes me think that maybe the picture was actually been taken in a colder season than summer... Looking at the prices in past Google Streetviews, never do they even come remotely close, except for 2022... Am I seeing things, or is this a picture from late fall, winter, or maybe early spring? From 2022, instead of a recent summer vacation shot? I hope Bellingcat will tell us in the next newsletter.  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/collage.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-16.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-15.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-14.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_04-9.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_05-3.webp"],"local_images":["blog_data/images/blog_908de5a2c0d0_0.bin","blog_data/images/blog_908de5a2c0d0_1.bin","blog_data/images/blog_908de5a2c0d0_2.bin","blog_data/images/blog_908de5a2c0d0_3.bin","blog_data/images/blog_908de5a2c0d0_4.bin","blog_data/images/blog_908de5a2c0d0_5.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-ship-happens-challenge/","title":"76. Ship Happens","status":"ok","retrieved_at":"2026-08-29T16:11:49.863908+08:00","text":"Walkthrough for Bellingcat's 'Ship Happens' challenge 15 Jul, 2026 Hi, welcome to this write-up for the Ship Happens challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. The challenge We've received someone's travel picture and have to find out the name of the ship that brought the person visible in the picture to the location where the picture is taken. The picture seems to have been taken in some sort of terminal or other place travelers pass through. There are multiple people sitting and walking around with luggage. In the middle is a man, standing next to a life-size camel statue. In the background is a wall of windows, offering no clear view of the outside but rather of something bigger than the windows, with a blue/white pattern and small round windows. A ship? Because I have no knowledge of ships whatsoever, my plan was to first find the picture's location. I hoped that finding the location would lead to a way to research what ships would be arriving or leaving at said location or in the area. Then I could match those ships' looks to the one probably visible through the windows in Bellingcat's picture. The location I started with a reverse image search on the picture, hoping to find the building the picture was taken at. I assumed that the massive camel statue on a red carpet would be notable enough to get a quick match. I used a browser add-on called RevEye to reverse search the image on Google, Bing, Yandex and TinEye. A few of the results on Google looked like a large camel statue on red carpet. One was this IG post with the description \"Dubai, UAE\" . Another was this thread on a cruise forum . Scrolling down, the post made on January 13, 2005 not only has the camel shown, but also an overview of the cruise terminal it's located in. It's labeled as Abu Dhabi Cruise Terminal . Putting the overview picture from the forum next to Bellingcat's picture, the two locations appear to be the same. Especially the blue wavy couches, the floor tiling, the textured upper windows, and the slanted window roof look identical. Just to double check, I looked up Abu Dhabi Cruise Terminal in Google Images to see if the posts I had seen hadn't mislabeled the location. In the results were plenty of examples that indeed the location was right. The ship Now that I knew that the picture was taken at Abu Dhabi Cruise Terminal, and that the ship likely had a blue/white pattern that was partially visible through the window of the original picture, I wanted to find an overview of ships that pass through that cruise terminal. With that, I could compare their looks to the picture. Before going for more specific queries, I first tried to do a really general search and looked up the following on Google: Abu Dhabi Cruise Terminal For me, the second search result was this port page on Cruisemapper. Conveniently, a list of cruise ships is shown in the Schedule section, but depending on when you're looking at it, there are not many ships going and leaving due to the 2026 Iran war . Also, the schedule only showed the current month and future months. It didn't show ships from previous months. I checked the port's News tab hoping to see some more information of travels going through the area in the past, and one article's picture caught my eye. The ship in the preview picture seemed to have a blue/white pattern. I clicked the article , but unfortunately there was no bigger picture available. The news article does give some other information. It states that the MSC Euribia ship departure from \"homeports Dubai, Doha, and Abu Dhabi\" is disrupted, thus resulting in the cancellation of its remaining Middle East winter 2026-2027 schedule. Since I was looking for a ship related to the Abu Dhabi Cruise Terminal, this was promising. Clicking on the ship name in the news article led to this ship page that showed the boat slightly better, but still not close enough to really see those small pattern details well enough. I went back to Google Images to look for: MSC Euribia Looking through the results, the MSC Euribia's decoration pattern appears to resemble the pattern visible through the window in the Bellingcat picture. Comparing several pictures, the exact pattern can even be found on the ship, like in the picture on this page . With this I was quite certain that the ship pictured in Bellingcat's photograph was the MSC Euribia, so I assumed that the person in the shot had traveled with that ship too. Fortunately that answer made the screen turn green. So the definite answer is MSC Euribia .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/001_cruiseterminal.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/002_news.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/003_ship.webp"],"local_images":["blog_data/images/blog_73f0ec430ce9_0.bin","blog_data/images/blog_73f0ec430ce9_1.bin","blog_data/images/blog_73f0ec430ce9_2.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-small-but-deadly-challenge/","title":"47. Small but Deadly","status":"ok","retrieved_at":"2026-08-29T16:09:29.164408+08:00","text":"Walkthrough for Bellingcat's 'Small but Deadly' challenge 10 Aug, 2025 Hi, welcome to this write-up of the Small but Deadly challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a picture of three damaged items, ordnance of some sort. Our task is to find the most likely model number for these objects. Looking closely at the image, some things that drew my attention: The bottom black parts can appear like a tube, or fanned out There appears to be something red at the top There's Cyrillic on the main middle parts, along with numbers The credit for the image is dsns.gov.ua -Ukraine I think the path to the answer can be fairly short and quick, but let's say I took the scenic route for a little more context, haha! Where were these objects found? I did a reverse image search on Bellingcat's picture in Google, Yandex and TinEye, but I viewed the results on TinEye first because they appeared to be an exact match. The first image research was called 'bomb disposal in Mykolaiv 9 March 2022'. The second result led to this page where it's explained that these cluster bombs were found in Nikolaev on 9 March 2022. A quick detour to the Wikipedia page of Mykolaiv taught me that Mykolaiv is also called Nikolaev. It's a city in the south of Ukraine, with crucial access to the Black Sea. So, this little detour in the origin of the picture didn't give me the model number of the items, but I did learn that these are maybe a cluster type of weapon/bomb/munition. I put a pin in the other information, in case I'd get stuck later and wished to read more about the area. The search for the model number Next in my reverse image results, I decided to check Yandex, because it looked like we were dealing with Russian weapons used in Ukraine. There were a lot of results that resembled the object we were looking for! Two pictures drew my attention the most, because the reading on them was the clearest. I tried to put the writing together from combining the text of the two pictures and two of the three lines were pretty clear: 9H235.00.000 30-26? 30?-53-91 (seemed to differ between pictures) K-991-12 But what of this information was the model number? Conveniently, the second picture had a label at the top, called 9N235 . The object said 9H235 in Cyrillic, and a text referred to it as 9N235 . I checked the Russian Cyrillic alphabet on Wikipedia and saw that the Cyrillic letter H commonly gets translated to N, so it checked out. I made my way to CAT-UXO , a convenient website where you can check many types of explosive ordnance. I stumbled upon this website during a different challenge and saved it for later use. In the search bar I looked up 9N235 and found this page for the 9N235 Submunition. That looked identical to me! And it turned out to be correct. The final answer is: 9N235 .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-8.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-7.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-7.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_04-4.webp"],"local_images":["blog_data/images/blog_fed4248375dd_0.bin","blog_data/images/blog_fed4248375dd_1.bin","blog_data/images/blog_fed4248375dd_2.bin","blog_data/images/blog_fed4248375dd_3.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-spot-the-location-challenge/","title":"26. Spot the Location","status":"ok","retrieved_at":"2026-08-29T16:07:51.010729+08:00","text":"Walkthrough for Bellingcat's 'Spot the Location' challenge 01 Nov, 2025 Hi, welcome to this write-up for the Spot the Location challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a picture of two giraffes, edited to be in front of the Eiffel Tower and the Seine. We have to find out in which country these giraffes were most likely photographed. I guess they weren't touring around in France after all... Looking closely at the picture, I noted down some things that caught my attention: The giraffes have small brown birds all over their back and neck. The spots are very dark brown and kind of jagged around the edges, with some having sort of coves in them. They appear to have long faces with a droopy mouth and a dark spot on their foreheads. Finding the (sub)species The first thing I thought was important to know, was the species of the giraffe. If I knew for sure what species I was dealing with, then I could look up their habitat and see what countries would pop up. I googled giraffe species hoping to get some kind of chart for comparison. I ended up on this webpage on how to tell giraffes apart. Scrolling down a little, there is an overview of nine giraffe types with pictures of their spots. Because our giraffes have jagged lines in their spots, I could already eliminate any giraffe with very smooth or square spots. This left four types for me to consider: Rothschild Thornicroft Southern Masai I decided to google each of the four species, so I could study their full bodies and compare them to the Bellingcat picture. Pretty quickly, the Masai giraffe was eliminated too. The spots are very wiggly, way more than what I'm looking for. The Southern Giraffe was eliminated too. They have droopy faces, but the lines between the spots are very thin and clear, unlike the ones the giraffes have in the Bellingcat picture. Two species remained, and I found it hard to compare them, so I made collage to look at them more closely, right next to each other: When I looked closely at the Rothschild giraffe, I noticed that the spots might be a little different. The horns also look bigger. And where's the droopy face? Looking at the Thornicroft giraffe, there seemed to be the most resemblances. Same horns. Droopy face. Spots almost identical. And there's a dark spot right on the face, in between the eyes. I felt relatively sure at this point that I was looking at two Thornicroft giraffes in front of the Eiffel tower. Finding the country I went back to the giraffe species link I visited earlier to read about the Thornicroft giraffe. There it stated that they live in eastern Zambia. To double check, I also visited Wikipedia . Here it's written that \"Thornicroft's giraffe is endemic to Zambia\" . This safari page said the same thing. Apparently there are only 550 left in the wild, all in Zambia, so there's barely any chance that they've gotten their picture taken in any other country. PS: The little birds sitting on the giraffes are apparently called oxpeckers. Here you can find a very interesting study about their bond with multiple benefits! Anyway, I put Zambia in the Bellingcat answer box and the screen green turned green. Voila!  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/giraffe_comparison.webp"],"local_images":["blog_data/images/blog_01a894be5a0e_0.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-symbolic-literacy-challenge/","title":"73. Symbolic Literacy","status":"ok","retrieved_at":"2026-08-29T16:11:21.849791+08:00","text":"Walkthrough for Bellingcat's 'Symbolic Literacy' challenge 10 Feb, 2026 Hi, welcome to this write-up for the Symbolic Literacy challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a picture in which a graffitied symbol is visible. We have to find the name of the building that's partially visible. Looking at the picture, here were some first thoughts I had and some things I noticed: The graffiti is in red, no other markings are visible. The building looks like a tunnel or bunker of some sorts, but it's hard to say because by now it looks like ruins. There is a doorway with stairs leading up. A part of the building is higher up. Are these the ruins of an upper floor? Or is it built on the slope of a hill? Based on the foliage and the general 'vibe' (for lack of a better word), it looks like this was taken somewhere in Europe. Finding the symbol The symbol is a little hard to see, it being graffiti and partially hidden behind foliage. Was I looking at a cross or a plus sign? Was the lower part an upside down omega or something else? I tried to look up all sorts of descriptions for this symbol in a variety of search engines, but couldn't find anything related to it. I drew the symbol in Paint for a reverse image search, but had no luck with that either. Getting kind of stuck in a circle of my own thoughts on how to describe this symbol, I decided to approach the challenge in a different way. By the way, after completing this challenge I found out that the symbol is actually in the Bellingcat Monitoring Glossary . That would have been an interesting point to start this search with, but alas. I used a different road to get there. Knowing what the symbol is called now, I tried to google it again. If you use the terms cross and u together in some ways in your query, it's quite easy to find more information. So finding the right variation of words can be really important. Good thing to have learned for a future search. Finding the building I checked to see if the picture had any metadata that would be helpful. For this I used the EXIF Viewer Pro browser add-on. There was no GPS data, but three other things were notable to me: Artist: Peter Hohenhaus Copyright: dark-tourism.com Date time original: 2018:04:09 I looked up Peter Hohenhaus and saw that he was the author of Dark Tourism , which makes sense. By now I expected that this picture was published in an article on Dark Tourism about those ruins, buildings or the general area. Finding that article would most likely give me more information to use. I was considering using Dark Tourism's search option to look for bunker (224 results), ruins (258 results), or urban exploration (35 results), but felt a little unsure. I wasn't familiar with Dark Tourism's articles yet, and didn't know how diligently they were labeled. Also, what was I looking at? Did I know for sure that it was a bunker or ruins? The picture only shows a very small part of maybe a bigger whole. Instead I decided to focus on the date of the original picture: 2018-04-09. Evidently, the article with this picture could not have been published before that date, only after. How quickly after visiting the locations did the author publish an article about it? I first tried to do a specific Google search for Dark Tourism articles published in in the +/- two months after the picture was taken: site:dark-tourism.com after:2018-04-08 before:2018-05-01 This only gave one page of results, but unfortunately none of the articles that appeared, contained this picture. Next up I broadened the search to all articles from the date of the picture to almost the end of the same year: site:dark-tourism.com after:2018-04-01 before:2018-12-01 This gave four pages of results, but I didn't mind going through them. By now I was fascinated by all of the articles and got slowed down by reading them, which was well worth my time, haha. Hohenhaus went to many interesting places and I enjoyed encountering history that I didn't know about yet. Still, I tried to limit the amount of articles I decided to click from the search results list. Looking at the Bellingcat picture, I expected this place to be in Europe, so I primarily checked out articles for European locations. Eventually I reached the article about Villa Rebar . In the gallery, picture 09 is the same as the one posted by Bellingcat. Apparently it's a ruined hunting lodge with tunnels leading to bunkers, the residence of Ante Pavelić . Looking up Villa Rebar online, there are plenty of other articles that show that far right graffiti is quite common there. And if you look up Villa Rebar on Google and check the photos people have added to the Google location for this building, there's even a video of someone walking by the symbol painted on the wall. It looks like the same wall next to the doorway as is visible in the picture by Dark Tourism. That confirms the name of the building we were looking for, which was indeed: Villa Rebar  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/001_metadata.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/002_articlepics.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/003_video.webp"],"local_images":["blog_data/images/blog_64783fa2bccb_0.bin","blog_data/images/blog_64783fa2bccb_1.bin","blog_data/images/blog_64783fa2bccb_2.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-take-you-to-the-beach-challenge/","title":"21. Take You to the Beach","status":"ok","retrieved_at":"2026-08-29T16:07:46.579871+08:00","text":"Walkthrough for Bellingcat's 'Take You to the Beach' challenge 02 Nov, 2025 Hi, welcome to this write-up for the Take You to the Beach challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a satellite image, captured by Landsat-8. It's our task to find the name of the archipelago that's visible on the image. A very quick search This was definitely the quickest Bellingcat challenge I've ever completed. I reverse image searched the satellite image through Google. Immediately at the top of the results I saw three credible results: This Wikipedia page shows an archipelago that looks completely similar. It's called Mayotte and the picture is taken by Sentinel-2. This page from Nasa shows the same archipelago, called Mayotte's Lagoon, with Landsat-8 as the source. This case study write-up from POGO about Mayotte shows a familiar image from Sentinel-2. It seemed like the answer was already in front of me. Just to be absolutely sure, I looked up Mayotte on Google Maps and checked to see if it was once again looking identical to the satellite image we'd been given. After that I decided to give in my definite answer, Mayotte , to the challenge page, which turned out to be correct.  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/comparison-3.webp"],"local_images":["blog_data/images/blog_854680472d0b_0.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-target-not-acquired-challenge/","title":"49. Target Not Acquired","status":"ok","retrieved_at":"2026-08-29T16:09:53.747702+08:00","text":"Walkthrough for Bellingcat's 'Target Not Acquired' challenge 17 Aug, 2025 Hi, welcome to this write-up for the Target Not Acquired challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We received a picture of an object, partially buried, kind of looking like a thermos bottle, but it's ordnance so don't touch it! The size is hard to gauge, but comparing it to the surrounding plants, it looks rather small. The Bellingcat text also calls this item compact . I had no idea what type of ordnance I was dealing with. In the Bellingcat newsletter there was a link to A Beginner’s Guide to Identifying Explosive Ordnance in Social Media Imagery , so I tried to give the illustrated chart a go. Imagining I was looking at the back of the item, I imagined it being oblong, without fins, with a flat base and with driving bands. The chart led to projectile . I looked up what full projectiles looked like on CAT-UXO but wasn't convinced that was right. I put a pin in that for now. What if, in the picture, I was actually looking at the front of the item instead of the back? Nothing in the illustrated chart really looked like that either. It was time to try a different method, because I wasn't really getting anywhere. Looking around I reverse image searched the picture on Google and Yandex. Nothing quite matched the object I was looking at, but even if I could simply find the type of ordnance, I'd have a new path to explore. Looking around at items that looked kind of similar, they were often labeled either as tank shells or grenades . With tank shells, we'd be back in the projectile category, the one I put a pin in earlier. So, I decided to look into grenades first. I was confused that grenades were coming up so often in the image results, because in the illustrated ordnance chart these looked very round and were described as 'lemon' or 'egg'-shaped. I checked out the grenade page on CAT-UXO and my eye immediately fell on the subcategory that appeared at the top of the results. That shape did look a little like the picture's object! Filtering to show only the projected grenades , I got 82 results. That wasn't too bad, so I browsed through them. The RLV grenades kind of looked like it, but not quite. But the VOG grenades looked very, very closely like the picture. Inspecting them all more closely, only one truly looked like the Bellingcat picture: the VOG-25M grenade. The shapes were identical, except that the ridges looked slightly differently spaced. But how important was that detail? I felt confident enough about my finding, so I put it into the answer box. And then the screen turned red. Oops! It was wrong! So, to answer my own question, apparently that detail was very important. Lesson learned. When I recovered from the surprise, relieved that I didn't actually just give wrong advice to an ordnance disposal squad, I looked at the VOG type grenades again. The VOG-25 looked completely different. The VOG-25P's bottom part, before the ridges start, were too long to be the same object as the picture. The VOG-25M still looked mostly the same. CAT-UXO only showed three VOG-type projected grenades, but maybe there were more? I decided to google for: vog projected grenade types I found some specific ordnance guides, like this one from GICHD about explosive ordnance in Ukraine , but could not see anything with a closer resemblance than the VOG-25M. I then tried to google for: vog-25 projected grenade types This didn't result in any useful information either. I only ever found the same three types of VOG grenade. I was starting to think that maybe I was following the wrong trail. Should I bite down harder or reassess and restart? Looking deeper I decided to join the Bellingcat discord to see if there were any tips or hints that I could use. I didn't want to get spoiled, so I navigated the relevant topic as carefully as possible, but I did see that others had gotten stuck on the VOG-25M as well. The general gist I got was: keep following that idea, keep reading around, and you'll get there. So, I tried some more search terms and kept reading around. Eventually, the following google search term got me there: vog-25m grenade ukraine This lead to an article about surgeons removing a VOG-25 grenade from a soldier's body. A new type was mentioned that I'd never read about before: the VOG-25PM. I tried looking up more information about it, which required quotation marks in the google terminology, or else I'd be led back to the 25M and 25P. But with quotation marks, I ended up on this overview page . The ridges did appear to match more closely. I also found this updated GICHD guide for ordnance used/found in Ukraine that mentioned that the VOG-25PM very closely resembles the VOG-25M. And with that extra information, I put in this new type of grenade in Bellingcat and fortunately this time the screen turned green. So, the definite answer is: VOG-25PM .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-11.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-10.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-9.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_04-6.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_05-2.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_06-2.webp"],"local_images":["blog_data/images/blog_60eff701c749_0.bin","blog_data/images/blog_60eff701c749_1.bin","blog_data/images/blog_60eff701c749_2.bin","blog_data/images/blog_60eff701c749_3.bin","blog_data/images/blog_60eff701c749_4.bin","blog_data/images/blog_60eff701c749_5.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-up-the-creek-challenge/","title":"16. Up The Creek","status":"ok","retrieved_at":"2026-08-29T16:07:33.456509+08:00","text":"Walkthrough for Bellingcat's 'Up The Creek' challenge 05 Oct, 2025 Hi, welcome to this write-up for the Up The Creek challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've been given a picture, taken from an airplane window, that shows a long river. We need to find the name of this specific river. Things that are noticeable in the picture: The river is very long and meanders through the landscape with a distinct pattern. Around the river are fields, some houses, roads, but beyond that is a lot of forest. There is a blue, curved bridge in the middle of the picture. It's a hilly environment, with even some mountains in the distance. Looking up the river Because the river's path looks so distinct, I started with a reverse image search. If search engines couldn't recognize the river immediately, then at least they might tell me the general area based on the environment. Reverse image searching the picture on Google gave a plethora of results: Rogue River, Chehalis River, Reshio River, and more. I took my time to scroll through the pictures, to see if I could spot any that looked very closely like the river's path. There was one result that caught my eyes, because the river was very curvy, and because I spotted a little, curved bridge going over it. I followed the associated link to a blog post called Advocacy Update: Fish, Farm, Flood 2.0 from 2018. It talks about task forces and states: \"By December 2019 they will be using their research to develop a decision-making tool that combines science, policy, and local knowledge to identify the relative impact of a buffer planting in any given stretch of the Snoqualmie River.\" No other rivers were mentioned in the post, and the update is regarding fishing, farming and flooding is a specific area. So, I assumed that the picture that went along with the post was of the Snoqualmie River . I decided to look up the Snoqualmie River and view its Wikipedia page for some general information. It's a 72 km long river in the US, in the State of Washington. I then tried to look up Snoqualmie River on Google Maps, to see if I could find the specific spot that is shown in the picture to verify that it was the right river name. Zooming in and going along the path of the river, the area right next to Novelty seemed the most promising. You can even see a bridge going over the river called Novelty Bridge. Here are a few comparisons of the original Bellingcat picture and the view from Google Maps. It looked pretty convincing, but I wanted to check one last thing. I dropped down to Google Streetview, right next to the bridge, to see what it looked like. At this point I thought there were enough pointers to confirm that the picture showed the Snoqualmie River. I put in Snoqualmie and it was indeed the correct answer.  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/collage_01.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/collage_02.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/collage_03.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-18.webp"],"local_images":["blog_data/images/blog_946daf7cbbed_0.bin","blog_data/images/blog_946daf7cbbed_1.bin","blog_data/images/blog_946daf7cbbed_2.bin","blog_data/images/blog_946daf7cbbed_3.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-urban-symphony-challenge/","title":"81. Urban Symphony","status":"ok","retrieved_at":"2026-08-29T16:12:26.976062+08:00","text":"Walkthrough for Bellingcat's 'Urban Symphony' challenge 07 Jul, 2026 Hi, welcome to this write-up for the Urban Symphony challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. The challenge We've been given an audio file and need to find the name of the tower we can hear chiming. The location Listening to the audio, there were a lot of sounds that I didn't recognize. However, I could identify spoken text, so I decided to note that down first: \"Be aware of pickpockets at this station.\" \"Caution, you're reaching the end of the travelator.\" I first looked up the first sentence I heard on Google, but it gave a large variety of results. It appears that many stations all over the world use this particular sentence. Next I googled: caution you're reaching the end of the travelator This led to quite a few results about Amsterdam, like this Reddit post and this one . There were also a few results from other cities, but the spoken sentence always different by at least one word. So, I was fairly certain that we'd have to search within Amsterdam next. The tower Because I had to recognize a clock chime that would probably be played in Amsterdam, I googled: amsterdam clock chime This led me to a page of results with videos of Amsterdam towers chiming their song. I listened to one of the Zuiderkerk clock tower , the Westertoren and the Munttoren . I thought the Munttoren might resemble the original audio most closely, so I looked up more fragments with the following google query: munttoren amsterdam clock chime I listened to a few more videos and kept thinking that the chiming in the audio could be a match for the chime of the Munttoren in Amsterdam. I did find it incredibly hard to hear and doubted myself a lot. Sorry to all the chiming sound lovers, but the bells and melodies all sound very same-y to me. Fortunately the answer made the Bellingcat challenge screen turn green. So the definite answer is: Munttoren .  ","image_urls":[],"local_images":[]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-challenge-01-pet-the-dog/","title":"Challenge 01: Pet the Dog","status":"ok","retrieved_at":"2026-08-29T16:13:17.286252+08:00","text":"Walkthrough for Challenge 01: Pet the Dog 19 Feb, 2026 Hi, welcome to this write-up of Challenge 01: Pet the Dog by me. Here you can see what steps I took (and the thought processes behind them) to get to the answers, or what kind of search path I designed for them. However, keep in mind that of course there are many different ways of reaching the same results. The challenge I've posted a cropped picture of a part of a dog statue. With this information, you need to find the location of the statue, the individuals it's based on and their names. My aim with this challenge was to give practice for: Reverse image searching Searching for general information with a search engine, mostly through articles I recommend looking at images closely before starting an in-depth search, just to have a little more context or to notice things you might want to look out for. Some noticeable details of this picture for me are: There's a foot visible next to the dog, so the dog might not be the complete statue. There's a sign on the wall behind the dog. It's hard to read, but the top part seems to say Rio . There's a really blue body of water in the background. It might be the sea. Combined with the bright sunlight in the picture, maybe it's a warm location. The floor has a really distinct cobblestone pattern. The search I started with a reverse image search on the picture. For this I typically use the RevEye browser add-on, which lets you search for a picture on Google, Bing, Yandex and TinEye simultaneously. In Google's results, I get a variety of dog statues, but also the right statue in a variety of angles. However, in TinEye's results I see the exact picture the crop was made from. One of the links lead to a blog website, not the specific picture. The other link is dead. One of the files is called Clarice Lispector and the other is called Estatua Clarice . So I decided to query Google: clarice lispector statue The results make it pretty obvious that this is the statue we're looking for. This page confirms that the human of the duo is Clarice Lispector . That already solves the second question of the challenge. Her Wikipedia page contains the statue picture, stating that it's in Rio de Janeiro. The Google search results also show the statue as a marker on Google Maps, including an address. Entering Google Maps the statue is marked next to a small road. But is it really there? Switching over to Google Streetview gives several options throughout multiple years in which the statue is visible. Right-clicking the location on Google Maps gives the coordinates: -22.962976390226064, -43.16451904351414 . This is the answer to the first question of the challenge. The only quest left is to find the dog's name. For this I started with a search query in Google for: clarice lispector dog In this LitHub article it reads: \"In A Breath of Life, Clarice Lispector’s fragmentary final work, she devotes a few short passages to her dog, Ulysses, with a focus on this same strange intimacy of difference.\" In this portrait article the dog is called Ulisses (with an i instead of an y ). In this article too, and there's a picture of a dog breed that looks like the statue with a caption that confirms it's Ulisses we're looking at. Just to be absolutely sure, I do one more search for: ulysses clarice lispector Lots of convincing pictures in the results, but also two different links, one an interview , another a review , that give a little insight into the origin of her dog's name. Somewhat unexpected, quite funny, maybe a little bit concerning, haha! tl;dr Answers In conclusion: -22.962976390226064, -43.16451904351414 Clarice Lispector Ulysses or Ulisses  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/001_tineye.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/002_googleresult.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/003_maps.webp"],"local_images":["blog_data/images/blog_8751fb5a6290_0.bin","blog_data/images/blog_8751fb5a6290_1.bin","blog_data/images/blog_8751fb5a6290_2.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-challenge-02-out-on-a-walk/","title":"Challenge 02: Out on a Walk","status":"ok","retrieved_at":"2026-08-29T16:13:29.496903+08:00","text":"Walkthrough for Challenge 02: Out on a Walk 28 Feb, 2026 Hi, welcome to this write-up of Challenge 02: Out on a Walk by me. Here you can see what steps I took (and the thought processes behind them) to get to the answers, or what kind of search path I designed for them. However, keep in mind that of course there are many different ways of reaching the same results. The challenge I've posted two pictures of somewhere outside. With this information, you need to find the location where the pictures were taken and some information about the area. My aim with this challenge was to give practice for: Geolocating. Doing search engine queries in a foreign language (if you don't speak Dutch). Navigating a railway website of a foreign country (if you're not familiar with the Dutch railway). I recommend looking at images closely before starting an in-depth search, just to have a little more context or to notice things you might want to look out for. Some noticeable details of these pictures for me are: The little wooden sign has several textual clues. Next to the wooden sign is a row of planted trees that might be particular. On the nature picture is a red bench, with next to it a building with an awning. There's water visible in the picture, which narrows down the location to parks with something like a pond, brook or lake. The park To find the park the pictures were taken in, one of the two pictures holds a major clue. There's a small plate on a wooden sign post, which shows that the one who took the pictures was on an established walking route. The text is in Dutch, so they're probably in a part of the world where Dutch is a native language. Looking closer at the specific texts, it's made up of four parts: Klompenpaden: this is the name for a collection of walking routes. Words ending in -en in Dutch are often verbs or, as is the case here, a plural of a noun. rondwandeling: this simply reads 'a walk' and can be safely ignored. It holds no major information. Stoetwegenpad: this is the name for a specific walk in the klompenpaden collection. The -pad addendum can mean path, way, route or walk. 11 km: this is the length of the Stoetwegenpad , which happens to be 11 kilometers. Literally translating these terms is useful for the context (finding out that we're dealing with walking routes here), but for looking this up online, sometimes it's better to use the original terms. So, with these terms I went to a search engine, Google this time, and looked for: klompenpaden stoetwegenpad In the results I saw this page for the walk. The names, logo and length of the walk match. Conviently, the website also offers a map for the full walk, which opens in a new tab . On the map I could see a few named green areas the route passed through: Wulperhorst , Blikkenburg , De Breul , Rijnwijck . Also, multiple city names are visible on the map: Zeist , Odijk , Bunnik . With this information I went to Google Maps and looked up the area . Now it's clear that the pictures were taken in The Netherlands. In the original pictures I saw water, maybe a pond of some sort, and a notable red bench. Were these located in one of these green areas the Stoetwegenpad passed through? With the route map and Google Maps next to each other, I could cross reference what areas I needed to inspect further. When I dragged the little yellow person around on Google Maps to see what parks I could walk around in through Google Streetview, not much lighted up. Most of the Streetview footage was from around the parks, not inside of them. There were a few blue circles marking snapshots of one specific place. Checking those out, they still gave a little bit of a clue of where these pictures were most likely taken. More useful was to click the markers that appeared on Google Maps for named parks, buildings, and other locations that have been marked by Google. Clicking one of those gives a pop-up for the location with access to reviews and pictures posted by people who have visited that place. If you hover over the picture that shows up, a see photos button appears. This way, I clicked a variety of markers for and around areas such as Wulperhorst , Blikkenburg , Landgoed De Breul . I focused on areas where I saw water on the map, since there was also water in the picture. Then I went through the pictures, trying to see if there were any red benches, ponds, matching foliage, buildings, etc. Doing this, there is only one area that was very similar to the pictures, namely Landgoed De Breul. And there's even one 360° picture posted by someone that is an exact match to one of the two pictures of the challenge. The red bench, the buildings visible through the foliage, the sandy path -it all ligned up. The first answer of the challenge has already appeared: the pictures were taken in a park called (Landgoed) De Breul . The train station The second and third question require some information about a train station. The second question is solvable in seconds once the park has been found. Both on the Stoetwegenpad map and the area on Google Maps , a train track is visible, along with the marker for a train station. Clicking it on Google Maps, its name appears: Station Driebergen-Zeist . No fancy search acrobatics required. Next up is the question about food availability on the train station. The Netherlands has a main railway operator called NS. With a tiny bit of online searching and/or Wikipedia reading this is quite clear. The NS has its own website with an option to search for any station to receive information about that specific station. Information about the Dutch train stations is more easily found on their Dutch website than their international variant . Looking up Driebergen-Zeist on the NS website brought me to this page . It contains all the information about the facilities on the station, including a section for Eten & Drinken (food and drink). The page states that there's two places on the station that offer food and drink. The first one, Cafetaria to Go , has to go in its name, which sounds like what I'm looking for if I want to bring a snack to the park. So I googled: driebergen zeist cafetaria to go This brought me to the cafetaria's own website . Browsing that and the pictures and reviews posted on Google, it looks like I could bring my friend some takeaway food. Their website says they're open every day of the week between 11am and 10pm, so as long as I arrive during the day, I can easily bring some food to the park with me. I hope my friend is in the mood for some fries and spring rolls (called loempia in Dutch)! tl;dr Answers In conclusion: (Landgoed) De Breul Station Driebergen-Zeist The train station has a cafetaria with takeaway food that's opened between 11am and 10pm.  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/01_terms.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/02_pad.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/03_seephotos.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/04_comparison.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/05_trainstation.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/06_ns.webp"],"local_images":["blog_data/images/blog_35d9b409a2e0_0.bin","blog_data/images/blog_35d9b409a2e0_1.bin","blog_data/images/blog_35d9b409a2e0_2.bin","blog_data/images/blog_35d9b409a2e0_3.bin","blog_data/images/blog_35d9b409a2e0_4.bin","blog_data/images/blog_35d9b409a2e0_5.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-challenge-1-by-mrs-osint/","title":"Challenge 1: Mystery","status":"ok","retrieved_at":"2026-08-29T16:12:46.74073+08:00","text":"Walkthrough for Challenge 1 by Mrs. OSINT 28 Jan, 2026 Hi, welcome to this write-up of Challenge 1: Mystery by Mrs. OSINT . Here you can see what steps I took (and the thought processes behind them) to get to the answers, but of course there are many different ways of reaching the same results. The challenge We've received a single picture of a place outdoors. Based on this we need to find the answers to the following questions: What is this place called by the locals? Where is it located? What is this place famous for (what do they sell)? First look I prefer to take a closer look at an image before starting my search, so I have some context for what to look out for. Here are a few things that caught my eye when I inspected the image: There are fumes that don't look like clouds, maybe the location is related to hot springs, volcanic activity or a different natural phenomenon. The hills and ground are dark, the greenery is bare. There's a steps/stairs-like shape in how the hill in the foreground slopes down. There's a building visible with multiple cars parked around it. Maybe it's a place that has visitors? There appears to be a bridge. Is it for people to walk on? There's a little shed-like building visible in front of the bridge. The search I decided to start with a reverse image search on the given picture in Google, Bing and Yandex. Browsing through the Google results, I saw a lot of pictures of areas that looked very similar. One result sprung out to me, because I recognized a lot of identical landmarks. This picture looked like it had been made in almost the same angle, just a little farther away: The picture is from Wikimedia and is called Owakudani Valley and Mount Kammurigatake near Owakudani Station . I wanted to see a few more pictures, so I put the following query into Google: owakudani valley Browsing the image results, it seems like I'm at the right address. The picture we've received is from the Owakudani Valley . Now looking at the general results, I saw and read a Wikipedia article about the place. It's a volanic valley with hot springs and previously a hiking trail, very cool. The article also goes into its popular specialty: kurotamago , black hard-boiled eggs. I still had not encountered what locals would call this particular place, so up next I decided to google: owakudani local name In the results were lots of travel websites and pages about the local history. Browsing a few of them on the first two pages of results, I found two different local names. This article says that during the Edo period, the place got called Ojigoku (Great Hell Hole). I did a quick google search for that Japanese term, and indeed got a lot of results leading to the same place. In a different article it is said that its second name is Jigokudani (Hell Valley). Looking up that term led to more pages like this one that both names were in use once. The answers In conclusion, the search led to the following answers to the challenge's questions: The place was called Jigokudani (Hell Valley) & Ojigoku (Great Hell Hole) by locals. They might just use 大涌谷 (Owakudani) in this day and age. It's located in Owakudani, Hakone, Kanagawa Prefecture, Japan. It's famous for its black eggs (黒卵, or kurotamago), hard-boiled eggs that are prepared in the local hot springs.  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/001_picturecomparison.webp"],"local_images":["blog_data/images/blog_e19a8648ed76_0.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-challenge-2-by-mrs-osint/","title":"Challenge 2: Cotton Candy","status":"ok","retrieved_at":"2026-08-29T16:12:50.639364+08:00","text":"Walkthrough for Challenge 2 by Mrs. OSINT 23 Apr, 2026 Hi, welcome to this write-up of Challenge 2 by Mrs. OSINT . Here you can see what steps I took (and the thought processes behind them) to get to the answers, but of course there are many different ways of reaching the same results. The challenge We've received a picture of a busy street. Based on this single photograph we're being asked to answer the following questions: What are the coordinates for where this picture was taken? What popular district is this? It's Friday night, I could go for some cotton candy. Where am I going? What time do they close? Arch The photograph has a large amount of clues of the arch's whereabouts, an overwhelming amount even. I decided to start with the simplest thing that was visible for me: the name of street that is printed on the arch, Takeshita Street . In Google I put the following search query: takeshita street Lots of results. Takeshita Street appears to be a popular tourist attraction in Tokyo. My next step was to look up the specific street on Google Maps . It looks to be a long street with two main entrances connecting to bigger roads on the east and west side. My first thought was the expectation that an arch would be placed at the entrance of a street. With two bigger main entrances and a collection of smaller ones, I decided to drop down into Streetview on the map at the two main entrances first. The east side has an arch, but it looks very different from the one in the picture we've received. However, the arch on the west side of the street looks familiar, including the landmarks around it. Going back in time in Google Streetview to 2017 , the western arch even has the same decorations on top as in the original picture. Because I felt certain that the picture was taken at the western arch of Takeshita Street, I went back to Google Maps (in 3D mode) and right-clicked the area in front of the arch, where I'd estimate the picture was taken. The coordinates appear in a pop-up box. So, the coordinates are: 35.67157252013977, 139.70312250404845 . District The second question is what district this is. Simply looking up the street in Google, gives an information overview with several area names. My assumption would be that Shibuya was a district, but I could be mistaken. To make sure, I googled: tokyo districts This brought me to this Wikipedia page with this image of the Special Wards of Tokyo. Special Ward is a different term than District , but scrolling down on the Wikipedia page, there is a section called Notable districts . Shibuya is on that list, so I thought it might count as a district for this question. I zoomed out on Google Maps to see what names would pop up in the area where I was, and I compared that to the Special Wards map. It looked to be Shibuya. However, looking a little further, on Shibuya's Wiki page Takeshita Street is mentioned as being located in Harajuku. And on Harajuku's Wiki page Harajuku is called a district in Shibuya. Although the terminology isn't entirely clear to me, I'd answer here that the popular district in the picture is Harajuku , which is located in special ward Shibuya, which is located in the city of Tokyo. Cotton candy For the third question, I started with the assumption that the person who's requesting cotton candy was standing on the spot where the picture was taken. What would be the closest location for getting cotton candy on a Friday night? In Google Maps, I searched for cotton candy in the area of Takeshita Street . A list of locations popped up, so I started checking, starting with the ones closest to the spot in the photograph and working my way outwards, deeper into the street. The first possibly relevant location that was shown on the map for me was Momi & Toy's Crêperie. I looked up their website, navigated to the menu and saw that they didn't sell any cotton candy. Nevermind! The second closest result was Totti Candy Factory. I went through the same process and checked their menu . There's cotton candy on there! I looked up their social media accounts to be sure, and yes, on their IG page one can definitely see that they're a cotton candy shop. But are they open on a Friday night? I couldn't find any opening hours on Totti's website, and (based on my own negative experiences) I didn't really trust the opening hours given to me by Google for the place, since they can be outdated. Instead I checked the pinned posts on their Instagram page and found a post with general information about the store , including opening hours. On a weekday, Totti is open until 8 PM. So, that gives the answer to the final question: the photographer is going to Totti Candy Factory , which will be open until 8 PM . The answers In short, the answers are: 35.67157252013977, 139.70312250404845 Harajuku Totti Candy Factory, 8 PM  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/01_streetmap.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/02_archcomparison.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/03_coordinates.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/04_shibuya.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/05_district.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/06_cottoncandymap.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/07_8pm.webp"],"local_images":["blog_data/images/blog_f530d8ecac33_0.bin","blog_data/images/blog_f530d8ecac33_1.bin","blog_data/images/blog_f530d8ecac33_2.bin","blog_data/images/blog_f530d8ecac33_3.bin","blog_data/images/blog_f530d8ecac33_4.bin","blog_data/images/blog_f530d8ecac33_5.bin","blog_data/images/blog_f530d8ecac33_6.bin"]}
diff --git a/blog_data/by_source/benjaminstrick.jsonl b/blog_data/by_source/benjaminstrick.jsonl
new file mode 100644
index 0000000000000000000000000000000000000000..e3be9577abb3153007b2fda2adc09ddf44577cf1
--- /dev/null
+++ b/blog_data/by_source/benjaminstrick.jsonl
@@ -0,0 +1,4 @@
+{"source":"benjaminstrick","url":"https://benjaminstrick.com/boko-haram-nigeria","title":"Boko Haram\\u2019s systematic destruction and displacement of Nigerian communities","status":"ok","retrieved_at":"2026-08-29T16:45:46.337602+08:00","text":"Boko Haram’s systematic destruction and displacement of Nigerian communities · Benjamin Strick BS Benjamin Strick Open-source investigations All writing Work ← Back to site Satellite Case study Boko Haram’s systematic destruction and displacement of Nigerian communities Published 8 August 2018 Read 9 min Villages, towns and dense areas have been burnt, destroyed, and completely levelled in northern Nigeria as the country continues its fight against the Boko Haram insurgency. Using Google Earth’s history function, we can view how landscapes change over years, as well as study developments in infrastructure and refugee movement through conflict areas. For the northern region of Nigeria, the landscape tells a grim tale. In Nigeria’s Borno State, what was once a thriving and culturally rich area, is now a void land as the population shelters in siege cities where the frontlines are protected by trenches, literally. Villages now have only their foundations remaining after they were burnt to the ground. The clear path of destruction mapped out by Boko Haram’s systematic approach to village destruction in Borno State from 2014 to 2017 can be seen as they jump from town to town destroying everything they leave behind. One roadside village was functioning in February 2016, but by March 2017 only foundations and ash remain. Another scene is the village of Mutube with its surrounding communities: the satellite image from 2013 shows a village, and the next available image from 2017 shows only trees remaining. For many communities that have been destroyed, there is no hope of rebuilding. That being said, the Nigerian Government is urging some refugees to return home . But there is nothing left, and if there was, it would again be under attack by Boko Haram insurgents still at large in the area. More recent village destruction can be seen below, where only a few foundations of buildings remain in the space of 11 months since 2017. Eleven months apart Mapping the disappearance of hundreds of sub-communities Surrounding the Sambisa Forest in Nigeria’s north is where the majority of the evidence of displacement can be viewed. According to UNHCR , that count of displacement is in the millions. The forest itself covers a very large and difficult terrain where many of Boko Haram’s attacks have been launched from. On the outskirts of the forest, traditional villages are all too common a story. When we view their status in the available 2017 map of Google Earth, there are no visible signs of what once stood there. There are hundreds of villages and towns like this that have been erased off the map. Three such communities were destroyed at some point between March and November 2016. Significantly larger and denser than the small villages, the town of Nguro-Soye was the victim of many suicide bombings and attacks by Boko Haram militants. Attacks on crucial infrastructure such as a telecommunications tower and suicide bombings of the town’s marketplace led to a downfall of Nguro-Soye, and its ultimate destruction. The satellite image from March 2018 shows few remnants after the town’s destruction. Further south of Nguro-Soye, on a T-intersection of a main road, we are able to see more defined darker areas where villages once stood, indicative of burning. These villages would have also been prime targets given the accessibility of the main highway for Boko Haram and Nigerian military to operate in the area. In a bid to control this area, the Nigerian military have used their \"trench-laying\" tactic to fortify the position against suicide bombers. Many of these trenches are scaled at 2 to 4m wide and 2 to 3m deep, and are a quick and effective solution to protect areas against potential suicide bombers or vehicle attacks, two offensive tactics Boko Haram employ. For villages that have been built along main roads, in a more peaceful time it would have been a good thing. But for villages in northern Nigeria, it means they are more accessible to Boko Haram. Almost all villages constructed along main roads near the major fortified town of Bama were systematically wiped out between 2016 and 2017. This is the case for the small town of Mairamri, 15km south-east of Bama. More recent destruction occurred at the village of Gajibo in Borno State along the Gamboru Ngala Highway. News reports from July 2018 state 27 were killed in an attack on the village, however, we can see from satellite images that the town has been largely destroyed, bar several shelters. Gajibo, before and after Any villages that are still standing are in the process of being besieged by Boko Haram, or are strongholds of Boko Haram, and face attacks and bombing by Nigerian military. Smoke signals from bombings and attacks are a common story. Dikwa: the siege city offering refuge With so much displacement from homes, communities and towns being destroyed, where have the majority of refugees gone? There is evidence in a number of larger towns that have the afforded protection of the siege trench walls and strong military presence. One such area is the town of Dikwa . Dikwa’s history has seen the town pivoted as a stronghold since the 1800s, and has seen German and French occupancy. Now the town is a well-protected sanctuary of the Borno State. It uses the first line of defence trench system encircling the town. The only access points in the town are main roads, which are heavily guarded with stringent checkpoints, visible in the satellite image from 2018. Due to the safety Dikwa is able to provide, it has been established as a refugee-haven for many of the displaced villagers from the outlying areas. We can see this in evidence of the rapidly erected refugee cities in Dikwa. The living conditions in these camps are dire. The capital of Borno State, and the area’s largest city, Maiduguri , is also a haven for many of the displaced with its well-protected boundaries. Since village destruction began in 2015, Maiduguri has struggled to house refugees. In the space of three years, a refugee city is born. The millions of displaced Nigerians, referred to as IDPs or Internally Displaced People, only need to look past city defences to see the plight of villages that sit beyond its boundaries. Beyond the protection of Dikwa’s boundary, one small village was levelled between 2016 and 2017. Outside the Dikwa perimeter, 2016 and 2017 Bitta: the failed siege town For the most part, the Nigerian defensive trench is able to protect the towns it surrounds. For Bitta , it was not able to do so. Bitta. Left: pre-2014. Right: December 2017 Bitta has been a hotspot for Boko Haram and Nigerian military clashes and many of its citizens have left after its destruction. The military has used Dikwa as a launchpad for the Borno State Nigerian military Deep Punch II Operation, focussing on the clearance of Boko Haram presence in the Sambisa Forest. The scars of clashes can be seen just beyond the guard boxes built along the north edge of the town. The refugees from villages like Bitta and others are not just moving to Nigeria’s refugee camps, but are also fleeing the danger and seeking refuge in bordering countries such as Chad and Cameroon. One of the largest external camps for Nigerian refugees is Minawao Refugee Camp in the Mayo Tsanaga region of Cameroon’s Far North. Minawao is exceeding numbers every day. The UN says Cameroon’s Far North region hosts more than 95,000 Nigerian refugees. Many of which are sheltering in Minawao. Since 2014, Minawao has become a city in Cameroon. Minawao, Cameroon. A barren landscape becomes a city While it did previously pledge a commitment to refugees, the Cameroonian Government has been \"forcibly returning\" a number of Nigerians. UNHCR say this is a clear violation of national and international laws. The fight against Boko Haram in 2018 still ensues, as regular attacks are reported against villages in Nigeria’s north, as well as bordering villages in Cameroon. Method This open-source case study was made using past and more present satellite imagery from Google Earth. I urge you to visit the communities via the links provided to see the destruction for yourself. Related writing All writing → Geolocation Adding geodata to Google Earth Pro → Geolocation Finding McAfee: geolocation and imagery analysis → GEOINT When the lights go out, satellites are watching → Get methods like this once a month OSINT Field Notes: tools, techniques and one case file. New editions are always free. Subscribe → © 2012 to 2026 Benjamin Strick benjaminstrick.com","image_urls":["https://benjaminstrick.com/images/blog/1-09ud44ncjaomdofkab1xkg-1341.png","https://benjaminstrick.com/images/blog/1-25tgsf7dh2pnbivbyzewxg-1024.png","https://benjaminstrick.com/images/blog/1-5qannf1hywgu-sf33-icag.png","https://benjaminstrick.com/images/blog/1-97vk4h3kl1xoirnnfsab4w-1024.png","https://benjaminstrick.com/images/blog/1-buv0rqe-nqjsgypq1sxslq.png","https://benjaminstrick.com/images/blog/1-ervuzn2dvravli5-urwp8a.png","https://benjaminstrick.com/images/blog/1-rlwagpmjweytveoueye3-q-1024.png","https://benjaminstrick.com/images/blog/1-uj-ep8y1nymf1ubfxoatbg.png","https://benjaminstrick.com/images/blog/1-x-fpu9myooprrg2tnyliyg-1024.png","https://benjaminstrick.com/images/blog/1-yijzcknn0vifcxigdqxtnq.png","https://benjaminstrick.com/images/blog/1-yzn95oyggdzjihjjpaxuwg.png"],"local_images":["blog_data/images/blog_517f0e7f0bb1_0.bin","blog_data/images/blog_517f0e7f0bb1_1.bin","blog_data/images/blog_517f0e7f0bb1_2.bin","blog_data/images/blog_517f0e7f0bb1_3.bin","blog_data/images/blog_517f0e7f0bb1_4.bin","blog_data/images/blog_517f0e7f0bb1_5.bin","blog_data/images/blog_517f0e7f0bb1_6.bin","blog_data/images/blog_517f0e7f0bb1_7.bin","blog_data/images/blog_517f0e7f0bb1_8.bin","blog_data/images/blog_517f0e7f0bb1_9.bin","blog_data/images/blog_517f0e7f0bb1_10.bin"]}
+{"source":"benjaminstrick","url":"https://benjaminstrick.com/finding-mcafee","title":"Finding McAfee: geolocation and imagery analysis","status":"ok","retrieved_at":"2026-08-29T16:45:39.335336+08:00","text":"Finding McAfee: geolocation and imagery analysis · Benjamin Strick BS Benjamin Strick Open-source investigations All writing Work ← Back to site Geolocation Case study Finding McAfee: geolocation and imagery analysis Published 15 March 2020 Read 6 min Identifying past, current, and possible future locations through the geolocation and chronolocation of media provided by a specific user. This case study is based on a challenge from well-known entrepreneur, John McAfee, to show how relative geolocation of two points on a chronological timeline can give a likely path and possible locations in between. To do this, two geographical points will be used, categorised by day, to geolocate a photo that was taken between those two points. This research post is split into the following four sections, in this order: Point B (the photo to geolocate) Point C (where the subject is traveling to) Point A (where and when the subject started the journey) Geolocation analysis of the Point B image The tools in this case study are completely free, so please do use them to follow along. I used Google Maps, GIMP (image editing) and Twitter. Contents 01 Point B: the image to geolocate 02 Point C: where the subject is traveling to 03 Point A: where and when the subject started the journey 04 Geolocation analysis of the Point B image Point B: the image to geolocate Below is the tweet in question. The challenge: self-explanatory. The tweet in question So where do you start in a case like this? Using a first approach to imagery intelligence (IMINT), look in the image and ask: \"what do I see?\". In the image, we have a number of clues that may indicate where this photo was taken. I am going to number some of them in the image below. Eight reference points to work from What do we see here? First, we have got McAfee. Who through his accounts may help give more clues. I will get to him later. This roof colouring gives an indication that it might be a brand colour. Coloured fuel bowsers indicate that this is both a fuel station, and is a unique identifier for what the brand or name of the fuel station may be. Large trucks use this fuel station, so it is likely that it is in an open area, or along a highway. There are flowers in front of the building McAfee is next to, which means it might be a store for the fuel station. There is a light blue band along the horizon. This is usually synonymous with a large body of water. This post and building would be a unique identifier on satellite imagery. The horizon is not cluttered with buildings or trees, indicating it might be a flat plain and out of built-up urban areas. That is a lot of reference points we have to go off. And now, since we have done an initial imagery analysis checklist, we can work our way down that list to investigate each of those leads. First is John McAfee. He is likely to indicate relevant information in his social media. Point C: where the subject is traveling to In the initial tweet above the subject indicated he was \"on the way to London\" and that the photo was taken in the past. This identifies our destination. How is he traveling there? Considering the location of the photo as we analysed in the eight takeaways above, it is clear he is at a service station with his large security crew. So it is likely he is driving to his destination. Point A: where and when the subject started the journey Where did the subject come from? This is where we can start using the intelligence tool I would like to refer to as \"geoprofiling\". Essentially we are going to map out a short chronological timeline of where McAfee was in order to find where he is. Scrolling back through his Twitter timeline, we can find this tweet. It was posted two days before the other photo. Two days earlier What is important about this tweet is it gives us a location as well as a destination. Take a look in the red box in the right of the image below. A signboard reading Hotel Schlicker It is in Munich, Germany . We know this is the place where the photo was taken as there are a number of features that match those seen in geotagged images on Google Maps and Facebook. First is the identical match of the sign and wall lining to this one found on Google Maps . Matching the sign, wall lining and ground paint against two independent sources Second, for further verification, we can identify both the sign and the white paint on the ground from this image on the Hotel Schlicker Facebook page. For chronolocation, for the purposes of this post there is no necessity to conduct a shadow calculation. Merely being able to plot this geolocated image on our timeline gives us an original lead for the following reference points: Hotel Schlicker in Munich, Germany on January 26, 2020 The unknown point in between London, at a future point in time Why is the second point unknown? Because that is the initial location we need to find. And we are going to do that now. Geolocation analysis of the Point B image We already know two things about the image. It was taken on the road between Hotel Schlicker and London. Using Google Maps \"direction\" feature we can make a simple indication of the route between those two points. A lot of empty space to cover That is a lot of empty space to cover. But we have a list of eight points we can use to filter that information down. First, what is the place they stopped at in the image? The features of the roof and fuel pumps will help with that. Those features are something we can use in a Google Search term. For this, I used what we know and what I see in the following string search for Google Images: It is likely in Europe, so that is a term I used: \"Europe\" \"Fuel Station\" \"Red and White\" We also have blue bowser pumps in the image, and some of the results have that. The features in the photo match those pictured in Google Images as an Esso Petrol Station. The branding resolves to Esso Now we can search for \"Esso\" in Google Maps to find any Esso fuel stations on the way from Munich to London. To further refine our search area, looking back at the eight points, the photo was likely taken near a body of water, possibly in an open area or out of a city, and along a highway. In looking at places where there is a main road near a large body of water I identified two possible locations on the route. To layer both the location of Esso petrol stations and the routes to London, I used photo editor GIMP to layer the two images, changing the transparency of one of them. There are alternative ways using KMZ points, but this one is also quite simple and keeps Google Maps as our main operating tool. Stations layered over the route One of these stations along the route is near a body of water. It is near Baden-Baden . It satisfies a number of the indicators we are after, such as water, main road, quiet area and an Esso station on our route. We can start to match this location with the Point B image to see if it fits the fingerprint of what is visible on the Google Maps satellite image. The final match Using all of the information derived from geolocating objects in the image, we can say, for certainty, that the photo was taken here . Further verification can be made by matching the Google Maps embedded images. However, for the purpose of this case study, the indicators seen in the photo are uniquely matched to the satellite image therefore giving a stronger level of geolocated evidence. A note on this case study The purpose of this case study is to stimulate conversation, research and development in the open source community and is in no way to the detriment of the subject or any business or person identified in this case study. Related writing All writing → Geolocation Mountain profiling with PeakVisor in Ethiopia → Geolocation Adding geodata to Google Earth Pro → Geolocation Boko Haram and the destruction of Nigerian communities → Get methods like this once a month OSINT Field Notes: tools, techniques and one case file. New editions are always free. Subscribe → © 2012 to 2026 Benjamin Strick benjaminstrick.com","image_urls":["https://benjaminstrick.com/images/blog/1-0ol0mb1elrwhb1n-xhz4g-1024.png","https://benjaminstrick.com/images/blog/1-3twkcb6hkt9ed2c-fybw7a-1024.jpeg","https://benjaminstrick.com/images/blog/1-4hv5zneqt6vn-btsoc6hfa-700-2.png","https://benjaminstrick.com/images/blog/1-4hv5zneqt6vn-btsoc6hfa-700.png","https://benjaminstrick.com/images/blog/1-aai0ap3pqgrnho8gker1hq-700.jpeg","https://benjaminstrick.com/images/blog/1-aieh1iu-ouhjnkknufjdaw-1024.png","https://benjaminstrick.com/images/blog/1-rehufwykry4mc3voel-e8g-2-1024.png","https://benjaminstrick.com/images/blog/1-tap6l7hpyt9plvivaszgzg-1024.png","https://benjaminstrick.com/images/blog/1-vi07n7r-frol9ffuih0w2w-1-700.png","https://benjaminstrick.com/images/blog/1-ybhjekvc1rzskcfz5ofiq-1024.png","https://benjaminstrick.com/images/blog/1y-ovhirrkrnbhw0suoe6hw-592.png"],"local_images":["blog_data/images/blog_89c2d63d87c4_0.bin","blog_data/images/blog_89c2d63d87c4_1.jpg","blog_data/images/blog_89c2d63d87c4_2.bin","blog_data/images/blog_89c2d63d87c4_3.bin","blog_data/images/blog_89c2d63d87c4_4.jpg","blog_data/images/blog_89c2d63d87c4_5.bin","blog_data/images/blog_89c2d63d87c4_6.bin","blog_data/images/blog_89c2d63d87c4_7.bin","blog_data/images/blog_89c2d63d87c4_8.bin","blog_data/images/blog_89c2d63d87c4_9.bin","blog_data/images/blog_89c2d63d87c4_10.bin"]}
+{"source":"benjaminstrick","url":"https://benjaminstrick.com/google-earth-geodata","title":"Geospatial awareness: how to add geodata to Google Earth Pro, and four datasets you should try","status":"ok","retrieved_at":"2026-08-29T16:45:28.745426+08:00","text":"Geospatial awareness: how to add geodata to Google Earth Pro, and four datasets you should try · Benjamin Strick BS Benjamin Strick Open-source investigations All writing Work ← Back to site Geolocation Method Geospatial awareness: how to add geodata to Google Earth Pro, and four datasets you should try Published 4 December 2020 Read 9 min This post is a list of geospatial datasets to drag into Google Earth Pro, such as NASA daily fires and Wikimapia. I have found these useful in conflict analysis and routine geolocation work as they boost what information is achievable with the Google Earth Pro platform. Google Earth Pro is great when it contains useful geotagged data, whether it be through custom-made satellite imagery annotations (such as powerline markings over Libya for geolocation purposes) or geospatial data taken from publicly available datasets. But how do we pull extra data into Google Earth and what are some useful datasets to help you with satellite imagery analysis, geolocation and storytelling? I am going to run through that in this post, as well as provide a list of files to add to your Google Earth Pro to increase your geospatial awareness and how to find more of them. What will you find in this post? A primer on Google Earth Pro How to find KML geo-datasets to \"drag\" into Google Earth Pro Four geo-based datasets you should try in Google Earth Pro Security considerations for using KMLs Contents 01 A primer on Google Earth Pro 02 How to find KML geo-datasets to drag into Google Earth Pro 03 Four geo-based datasets you should try 04 Security considerations with KML files A primer on Google Earth Pro Google Earth Pro is one of the most useful tools in performing any geospatial task, whether it be for conflict analysis, remote sensing, investigative journalism or routine geolocation tasks. For those of you that might be new to the software, I am talking about the desktop version. Not the one that you use in a browser. If you are following along, you can download Google Earth Pro here . If we zoom in on Uluru (Ayers Rock) in Australia, we can get an understanding of the volume of extra data already in Google Earth’s primary database. Uluru without and with Google Earth’s built-in data All of these data points have information related to the area geotagged to a specific place. These could be labels, images and other formats of data. For open source investigators, researchers and curious minds, this is useful as it gives us an understanding of what Uluru looks like on the ground from photos. So what if we layer that with information not generally available in Google Earth Pro, such as an open source database of geotagged locations, Google Maps labels and publicly available GPS data? Much more information than the built-in features alone As you can see, we get more information appearing on the map. Much more than what we would have had we been relying solely on Google Earth’s in-built features. So where did I get those external packets of data? They are external KML and KMZ files. KML, or Keyhole Markup Language, is a spreadsheet annotation for geographic-based data. The important question is, how can you find more of them, tailored to your specific need or investigation. How to find KML geo-datasets to drag into Google Earth Pro Finding KMLs to add geospatial awareness to your Google Earth is quite simple. One method is to try the advanced search term below in Google with any subjects you are looking for. In this example I have chosen to look for London Underground Tubewalk. Search string London Underground Tubewalk filetype:kml What we have done there is created a search string for all KML files, indexed on Google, with the term London Underground Tubewalk. With queries that have a lot of results, we can restrict that to sift out old data by changing the \"tools\" and \"any time\" tabs on Google search. In the results, you will notice a list of KML files. All we do is download it and drag it into the \"places\" section of Google Earth Pro. London without and with the Tubewalk KML Each one of these nodes and their connecting points is user-generated material. Each point is either a path, unique image or context about the location it is tagged at. As we can see, we have even got Paul McCartney’s house. If you are still wondering why this might be useful, there are a number of applications for this sort of data and a number of subjects where KML files are available through search engines. You might be a researcher on bald eagle migration, spider populations, deforestation in the Amazon, law enforcement or documenting conflict in Libya. All of these roles will have the need for extra packets of information. Four geo-based datasets you should try #1 Wikimapia . For anyone that performs analysis using maps, you will be familiar with Wikimapia, the open source map reference system. This KML file is specifically useful in areas that are less mapped on Google Maps. I have often found it to be a resource in conflict areas, as it provides more details as to place names and areas than other annotated maps. Wikimapia’s KML is quite powerful when used in conjunction with Liveuamap’s custom KML files of layered conflict lines and events which can be exported out of the browser and into Google Earth. East of Benghazi. Wikimapia identifies bunkers, hangars and air defence sites #2 Bing/Microsoft Maps . At times during routine geolocation work, without commercial imagery, I have found there is either very little coverage, or the imagery is blurred. Another medium of imagery that is freely available to use in Google Earth is the Bing Maps satellite overlay. The website that offers a good browser for that is Zoom Earth . To use this KML, from the linked page, use the drop down list and select \"Windows Live Satellite\". A site in Iraq. Google Earth on the left, Bing overlay on the right #3 Google Maps Labels . At times, Google Earth does not have the same level of detail for streets and places as Google Maps provides. A way around that is to drag in the labels system from Google Maps into your earth explorer. Select \"Google Hybrid (Labels)\" for the KML. This is also useful as you can layer this over either commercially bought imagery, or imagery from Bing Maps. Khartoum, Sudan. Built-in labels against Google Maps hybrid labels #4 EOSDIS Fire Points List. A more niche subject is spotting where fires may have occurred, especially in conflict areas as they can indicate signs warranting further research. I have previously produced guides on how burnt villages can be detected through satellite filters here as well as case studies on buildings being burnt where security forces have been known to do so. One way to monitor these activities in a wide field perspective is to use fire spotting systems such as NASA’s Worldview platform. This is also a useful tool for environmental monitoring for forest fires, back-burning and climate patterns. This system is available on EOSDIS Worldview Earthdata . It draws information from satellite sensors that detect daily fires. The data can be used in Google Earth and matched with other datasets such as ACLED reports and Sentinel Hub ’s fire identification feature to spot burnt areas. Note the historical slider, which lets you move through the past few days This is not an exhaustive list of KMLs, but rather these are ones that I have personally tested and find useful in documentation. There are likely more, and I urge you to search for them. Security considerations with KML files Some of the research performed using Google Earth Pro may be potentially sensitive, so reading up on any considerations and threat research is paramount. There are two vulnerabilities that have been identified in past versions of Google Earth Pro in relation to the use of KML and KMZ files, and while they may have already been identified and subsequent versions of the system have issued patches, it is a good reminder to query the source of any dataset before its use in software. CVE-2010-3134 identified a vulnerability in Google Earth where remote attackers could execute arbitrary code via a trojan horse located in the same folder as a KMZ file. This could lead to a potential hijack attack. A further vulnerability was identified in CVE-2006-7157 whereby attackers could cause a denial of service crash through a KML or KMZ file. Rule of thumb If you are in doubt about a specific KMZ or KML, then do not use it, or look for an alternative source that might be verified. Related writing All writing → Geolocation Finding McAfee: geolocation and imagery analysis → Satellite Boko Haram and the destruction of Nigerian communities → GEOINT When the lights go out, satellites are watching → Get methods like this once a month OSINT Field Notes: tools, techniques and one case file. New editions are always free. Subscribe → © 2012 to 2026 Benjamin Strick benjaminstrick.com","image_urls":["https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-5-49-36-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-5-50-07-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-6-16-29-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-6-16-36-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-6-34-09-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-6-34-23-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-6-37-38-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-6-37-53-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-6-48-30-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-01-at-6-49-00-pm-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-02-at-11-08-54-am-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-02-at-11-25-07-am-1-2150.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-02-at-7-48-24-am-1-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2020-12-02-at-7-48-33-am-1-1024.png"],"local_images":["blog_data/images/blog_e32049c84994_0.bin","blog_data/images/blog_e32049c84994_1.bin","blog_data/images/blog_e32049c84994_2.bin","blog_data/images/blog_e32049c84994_3.bin","blog_data/images/blog_e32049c84994_4.bin","blog_data/images/blog_e32049c84994_5.bin","blog_data/images/blog_e32049c84994_6.bin","blog_data/images/blog_e32049c84994_7.bin","blog_data/images/blog_e32049c84994_8.bin","blog_data/images/blog_e32049c84994_9.bin","blog_data/images/blog_e32049c84994_10.bin","blog_data/images/blog_e32049c84994_11.bin","blog_data/images/blog_e32049c84994_12.bin","blog_data/images/blog_e32049c84994_13.bin"]}
+{"source":"benjaminstrick","url":"https://benjaminstrick.com/mountain-profiling-peakvisor","title":"Geolocating a plane shot down in Ethiopia: mountain profiling with PeakVisor","status":"ok","retrieved_at":"2026-08-29T16:45:16.550134+08:00","text":"Geolocating a plane shot down in Ethiopia: mountain profiling with PeakVisor · Benjamin Strick BS Benjamin Strick Open-source investigations All writing Work ← Back to site Geolocation Case study Geolocating a plane shot down in Ethiopia: mountain profiling with PeakVisor Published 2 July 2021 Read 11 min Through the use of publicly available satellite imagery, open source investigative techniques, and a bit of creativity, we can find where and when a photo or video was taken. But sometimes, geolocating footage comes with unique challenges, all of which differ depending on the country, landscape, availability of data, or the quality of the footage you are trying to geolocate. In these case studies we look at the geolocation of footage in remote environments, and how Google Earth’s mountain ranges can play tricks on our confidence levels of locations. I have broken this post down into two main sections: A primer on use of PeakVisor , a tool that gives more accurate mountain silhouettes than Google Earth, and how it helps as a confirmation tool in geolocation work where Google Earth has not truly represented what is seen in the footage, with a case study from Yemen A recent case study geolocating footage circulated online showing the debris of an Ethiopian C-130, believed to be somewhere in the Tigray region A primer on geolocation with PeakVisor Finding where an image or a video was taken often involves searching for clues around, and in, a video or photo. I say around because there is often vital context that comes with media, such as a country, region, or possible location. By looking for clues within the imagery, can we start to consider matching that up with what we might see on a map. When looking at regional conflict areas, often there are no obvious clues to find a location. At least, not as obvious as a street sign or a shop name. When it comes to looking at these remote areas, clues do exist such as mountains, tree formations, bodies of water and other natural features. I have found numerous successes in using mountain ranges as a starting point in many difficult geolocations. But caution should be applied, as mountain ranges on Google Earth might not always appear as they would in real life. For example, take the Google Earth view from a base near Najran, overlooking the border between Saudi Arabia and Yemen, and compare it against the same view in PeakVisor. Notice the difference in definition, defined peaks, and the more jagged appearance on the profile of some of the mountains. Google Earth on the left, PeakVisor on the right As you can see, the level of detail is stronger. Google Earth’s meshing over its elevation data is not always as precise as we would like when we are relying on specific peaks to locate or match an image or a video. Having this added benefit of detail from PeakVisor helps substantially. In another example, this time in Yemen, there was much more of an issue with Google Earth’s formations during the geolocation of a Saudi Air Force jet that was allegedly shot down by Houthi fighters. The confirmation from that geolocation should have been made with two specific ridgelines seen at different intervals throughout the footage. Two ridgelines from the footage However, at the location on Google Earth there is barely any resemblance to the elevation data. I wrote about this example for Bellingcat in 2019, as it was a striking mismatch between what we see on the ground, and what we see on the satellite imagery layered over Google Earth’s elevation data. The same place in Google Earth In this circumstance, we can be definite of the location given the specific fingerprints unique between the satellite imagery and what is seen in the footage. For example, a rock formation creates a very definite match. But using PeakVisor creates a definite match between ridgelines. The ridgelines match By going through past geolocations like this, we can see just how much a little extra detail can help in the confirmation of a location. Case study: the crash site of a C-130 in Ethiopia In this specific geoprofiling case study, we look at the verification of footage of a crash site in Ethiopia which was circulated widely on social media. Most of the uploads claimed the wreckage was of an Ethiopian Air Force C-130 in Ethiopia’s Tigray region. The question to answer was where exactly that video was filmed. A primary starting place is always the context and content of the media. What are the circumstances of the upload, what are people saying about it, and what do we see? First, alternative images from the debris confirm that the plane may have been a C-130, including a photograph of the aircraft’s identification tag found in the wreckage. There were also a number of posts online that claimed the plane crashed somewhere near a town called Gijet, in the Saharti Samre area. So there was a clue as to a location, but also something to use as a keyword in further social media searches. While searching for other imagery on Facebook, I identified a post which was helpful as it showed a possible location in the sky from where the plane was downed, some specific building types that should be identifiable on satellite imagery, and an easy to locate mountain range. The post that opened the case The mountain range was rolling to the left, with no other mountains seen in the back left of the image, so this led me to believe the location was on the side of a mountain range. After a short amount of time panning around Google Earth near the area of Gijet, I identified the location of that image. The first location, firmed up Now that the location of that image was firm, I used that to work towards the much bigger task of finding where the downing of the plane was. This was easy to do, as we can see the location in the sky where the plane might have been hit. This lines up with features on the ground. Therefore, looking along that match line would lead me to the eventual final location. From the sky position to a line of sight In the original footage there also appeared to be structures that looked like powerlines, and I thought that might be a helpful resource to identify on satellite imagery to see if there were powerlines that crossed my line of sight from where the plane went down. While it took some work to identify nearby powerlines through a close inspection of the satellite imagery, I stopped at the second set as I had started to see other features that matched, such as buildings, a road, and of course, a fitting mountain profile. Powerlines, then buildings and a road From what can be seen on Google Earth, the mountain range makes a close fit with what we can imagine should be similar to the real footage. But there are some points in the elevation profile that are not accurate. As done above with the previous PeakVisor examples, layering the crash site footage over the mountain range seen in PeakVisor gives an almost perfect match. Google Earth close, PeakVisor almost exact But the final task is not yet complete. While the mountain profile is a confirmed location, further confirmation can be sought by analysing content in the footage with what is seen on the ground on satellite imagery. For example, the trees, houses, powerlines and other features. This allows me to identify an as exact as possible location. Once I have identified some features that can create a line, I draw lines back from them to find my backbearing. This gives the exact location of where the crash site footage was filmed from. Backbearings give the camera position In a more recent update, Twitter analyst @Gerjon_ further confirmed the location, and verified the date range, by using Sentinel Hub’s EO Browser with more recent satellite imagery of the area. The difference between what is seen on 20 June and 25 June 2021 shows two small black patches appearing in the centre of the imagery on the later date. That was the location of the crash site. Further reading on PeakVisor Mahbere Dego: clues to a clifftop massacre in Ethiopia · Using AllTrails and PeakVisor for geolocation · Geolocating Mahibere Dego . If you would like to learn more about geolocation, satellite imagery analysis or open source techniques, I have free tutorials on my YouTube channel . Related writing All writing → Geolocation Finding McAfee: geolocation and imagery analysis → Geolocation Adding geodata to Google Earth Pro → Satellite Boko Haram and the destruction of Nigerian communities → Get methods like this once a month OSINT Field Notes: tools, techniques and one case file. New editions are always free. Subscribe → © 2012 to 2026 Benjamin Strick benjaminstrick.com","image_urls":["https://benjaminstrick.com/images/blog/e4u-0wmweackpw8-1024.jpeg","https://benjaminstrick.com/images/blog/e4u6ixkwyamv3fz.jpeg","https://benjaminstrick.com/images/blog/e4u6j6vxeacr77q.jpeg","https://benjaminstrick.com/images/blog/e4u7wdhxwaek65q.jpeg","https://benjaminstrick.com/images/blog/e4u8bhhweam6jk3.jpeg","https://benjaminstrick.com/images/blog/e4u8p2sxmaifd8q.jpeg","https://benjaminstrick.com/images/blog/e4u8t9wxoaqpffc.jpeg","https://benjaminstrick.com/images/blog/e4vbdkrxwac-mxb-1024.jpeg","https://benjaminstrick.com/images/blog/e4vddllwqaqaxax.jpeg","https://benjaminstrick.com/images/blog/e4vdgblweamtaeu.jpeg","https://benjaminstrick.com/images/blog/screen-shot-2021-07-02-at-14-29-26-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2021-07-02-at-14-33-25-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2021-07-02-at-15-16-29.png","https://benjaminstrick.com/images/blog/screen-shot-2021-07-02-at-15-16-47-1.png","https://benjaminstrick.com/images/blog/screen-shot-2021-07-02-at-15-20-43-1024.png","https://benjaminstrick.com/images/blog/screen-shot-2021-07-02-at-15-52-56-1024.png","https://benjaminstrick.com/images/blog/untitled-design-5-1024.png","https://benjaminstrick.com/images/blog/untitled-design-6-2560.png"],"local_images":["blog_data/images/blog_32639a1b455a_0.jpg","blog_data/images/blog_32639a1b455a_1.jpg","blog_data/images/blog_32639a1b455a_2.jpg","blog_data/images/blog_32639a1b455a_3.jpg","blog_data/images/blog_32639a1b455a_4.jpg","blog_data/images/blog_32639a1b455a_5.jpg","blog_data/images/blog_32639a1b455a_6.jpg","blog_data/images/blog_32639a1b455a_7.jpg","blog_data/images/blog_32639a1b455a_8.jpg","blog_data/images/blog_32639a1b455a_9.jpg","blog_data/images/blog_32639a1b455a_10.bin","blog_data/images/blog_32639a1b455a_11.bin","blog_data/images/blog_32639a1b455a_12.bin","blog_data/images/blog_32639a1b455a_13.bin","blog_data/images/blog_32639a1b455a_14.bin","blog_data/images/blog_32639a1b455a_15.bin","blog_data/images/blog_32639a1b455a_16.bin","blog_data/images/blog_32639a1b455a_17.bin"]}
diff --git a/blog_data/by_source/dutchosintguy.jsonl b/blog_data/by_source/dutchosintguy.jsonl
new file mode 100644
index 0000000000000000000000000000000000000000..df1a06fc16e799b694f506c645ff7afe19d2e77a
--- /dev/null
+++ b/blog_data/by_source/dutchosintguy.jsonl
@@ -0,0 +1,4 @@
+{"source":"dutchosintguy","url":"https://www.dutchosintguy.com/post/crowd-sourced-mapping-tools-for-osint-investigations","title":"Crowd-sourced Mapping Tools for OSINT Investigations","status":"failed","retrieved_at":"2026-08-29T17:58:53.151418+08:00","error":"HTTPError: HTTP Error 429: Too Many Requests","text":"","image_urls":[],"local_images":[]}
+{"source":"dutchosintguy","url":"https://www.dutchosintguy.com/post/from-open-web-to-real-world-target-the-osint-trail-behind-proxy-violence","title":"From Open Web to Real-World Target: The OSINT Trail Behind Proxy Violence","status":"failed","retrieved_at":"2026-08-29T17:58:50.42056+08:00","error":"HTTPError: HTTP Error 429: Too Many Requests","text":"","image_urls":[],"local_images":[]}
+{"source":"dutchosintguy","url":"https://www.dutchosintguy.com/post/how-osint-investigators-miss-clues-hidden-in-plain-sight-cities-with-hundreds-of-names","title":"OSINT - Cities with hundreds of names | How OSINT investigators miss hidden clues","status":"failed","retrieved_at":"2026-08-29T17:58:51.786644+08:00","error":"HTTPError: HTTP Error 429: Too Many Requests","text":"","image_urls":[],"local_images":[]}
+{"source":"dutchosintguy","url":"https://www.dutchosintguy.com/post/the-amsterdam-street-that-never-existed","title":"The Amsterdam Street That Never Existed","status":"ok","retrieved_at":"2026-08-29T17:58:47.152635+08:00","text":"All Posts Cryptography OSINT analysis audio AI OPSEC geolocation mapping emotions tradecraft methodology vicarious trauma psychology job HUMINT Algorithm law enforcement Intelligence vibe coding evidence poisioning Search The Amsterdam Street That Never Existed Nico Dekens | dutch_osintguy Jun 8 14 min read How AI Misleads AI - and Why OSINT Tradecraft Is Your Only Saviour There is a street in Amsterdam that looks real. It has the wet brick paving you expect after rain. Tall narrow façades. Dark window frames. Bicycles leaning into the street. A cargo bike on the right. Bollards along the curb. A small café sign on the left. Grey skies. A muted, damp, unmistakably Dutch atmosphere. At first glance, it feels like Amsterdam. Not “Amsterdam-inspired.” Not “kind of Dutch.” It feels like a quiet side street somewhere in the old city center. The kind of place I could imagine walking past without thinking twice. But the street does not exist. It was generated by ChatGPT. And that is where this story begins. I conducted a little experiment based on workflows that almost every modern day OSINT investigator or analyst uses. Prompt 1: Create a street that looks real, but is not real The first prompt was simple, but deliberate: “Can you generate an image that looks like it is taken in a random street in Amsterdam city center. It cannot be an image or street that really exists. But it must look so convincing that not even a person from the Netherlands or Amsterdam will be able to tell it is not a real street in Amsterdam. I need this image for an OSINT training on visual analysis.” That prompt matters. This was not an accidental hallucination. The request was explicit: create a fictional street, make it look like Amsterdam, but make sure it is not an actual location. The goal was OSINT training. The image had to be realistic enough to challenge investigators. It had to look geolocatable while being impossible to geolocate. ChatGPT generated exactly that: a convincing Amsterdam-style street scene with wet paving, old façades, bicycles, bollards, greenery, shopfront details, and just enough visual texture to feel authentic. Original generated Amsterdam-like street image The original AI-generated street. It looks like Amsterdam, but it was deliberately created as a fictional location that does not exist. Look at this image for a moment before reading further. If you know Amsterdam, your brain probably starts filling in the blanks. Maybe Jordaan. Maybe De Wallen. Maybe somewhere near the old center. Maybe one of those quiet streets between canals. That is the danger. The image does not have to be perfect. It only has to be plausible enough for your brain to complete the story. The first OSINT question: how would we prove this street is not real? The next prompt shifted from image generation to OSINT methodology: “Now let’s think of OSINT CTF or OSINT geolocation. How could an investigator tell or show evidence this is not a real street in Amsterdam? Explain in detail what they should visually see that are clear tells and what else they should do to analyse and prove this is not a real image or real street in Amsterdam.” This is where the experiment became useful. The answer did not simply say, “Look for AI artifacts.” Instead, it described a more mature investigative approach: do not rely on vibes; build an evidence chain. The response correctly pointed out that the image was convincing because it contained many Amsterdam-like cues: wet brick road, narrow façades, bicycles, bollards, old buildings, black-painted houses, planters, and muted Dutch weather. But it also argued that the image was weak as a geolocation target because it lacked strong verifiable anchors. That is the first major lesson. An image can look geographically convincing while still being geographically empty. The image gives you Amsterdam atmosphere. But does it give you Amsterdam proof? That is a very different question. Soft cues versus hard anchors The original image contains many soft cues. Soft cues are things that make a place feel right: Amsterdam-like façades. Wet pavement. Bicycles. A cargo bike. Bollards. A small café sign. A grey sky. Narrow street geometry. Trees and planters. Old brick buildings. These cues are useful, but they are not enough. Hard anchors are different. They are specific, searchable, verifiable, and tied to a real-world location. A readable street-name sign. A house number.A unique shop name. A matching façade sequence. A business listing. A bridge or canal configuration. A license plate. A municipal object. A traffic-sign combination that makes sense for that exact street. A landmark visible in the background. The image had many soft cues but very few hard anchors. That is precisely why it is dangerous. It performs Amsterdam without proving Amsterdam. The image is not suspicious because it looks bad One of the most important points for OSINT practitioners is this: The image is not suspicious because it looks obviously fake. It is suspicious because it looks generically right while avoiding the boring, specific, searchable details that real places usually contain. Real streets are full of administrative residue. House numbers. Doorbells. Intercoms. Mail slots. business stickers. parking signs. waste collection markings. utility covers. drain logic. street-name plaques. local damage. construction scars. maintenance patterns. ugly details that were not placed there for aesthetics. AI-generated streets often prioritise atmosphere over administration. That is visible in this image. The road feels Amsterdam-like. The buildings feel Amsterdam-like. The bikes feel Amsterdam-like. But the scene does not immediately provide a strong, testable identity. For geolocation, that matters more than whether the image “looks real.” The annotated version: useful training image, but also a warning After the analysis, the next prompt asked ChatGPT to create an annotated version of the original image pointing out the clues and tells. That produced an image with callouts: generic storefront text, unreadable street plaque, bicycle geometry, bollard and curb logic, road paving and drainage, façade sequence, missing house numbers, and other points. First annotated evidence overlay The first annotated version attempted to highlight suspicious areas, but it introduced a new methodological problem: the image generation process altered parts of the underlying scene. At first glance, this looks like a good OSINT training graphic. But then something important happened. I noticed that the annotated version was not fully consistent with the original . The original did not clearly show the same street sign, but the annotated version appeared to introduce or strengthen one. That matters. I challenged it: “It’s funny because the original doesn’t show the street sign but the one with the evidence overlays does. That isn’t really consistent.” ChatGPT admitted the problem. It explained that the “evidence overlay” version was not a pure annotation layer on top of the exact original. The image model had re-rendered parts of the scene while adding overlays, and in doing so it introduced or strengthened details, including the street plaque/sign. That is a huge OSINT lesson. Annotation must never alter evidence. If the base image changes, the annotation itself becomes contaminated. For training, this is gold. It shows that even the act of “explaining” or “annotating” with AI can accidentally fabricate new evidence. A training overlay can become a synthetic derivative. The analyst may think they are marking clues, while the model is quietly changing the scene. That is unacceptable in real investigative work. The corrected annotation: preserve the original, add only the overlay I then asked ChatGPT to fix the inconsistency: “Fix it. I need consistency.” The corrected version was supposed to use the exact original image and add only a separate annotation layer, without regenerating the base street scene. The corrected labels focused on better claims: No readable street-name anchor. Missing house numbers and administrative details. Generic storefront text. Bicycle and cargo-bike geometry checks. Bollard and curb logic. Road paving and drainage continuity. Façade sequence that may not match any real street. Corrected consistent annotation The corrected annotation focuses on methodology: the image feels authentic, but lacks strong verifiable anchors such as readable street names, house numbers, or matchable façade sequences. This is one of the most important teaching moments in the whole experiment. For OSINT training, the corrected image is useful not because it proves the street is fake, but because it teaches students what to inspect. Do not just ask, “Does this look like Amsterdam?” Ask: Can I read the street name? Can I verify the shop? Can I match the façade sequence? Can I find house numbers? Can I explain the traffic logic? Can I match the curb, bollards, bikes, windows, trees, and road geometry to street-level imagery? Can I corroborate this scene from another source, another angle, another date? That is tradecraft. Then came the real test: a brand-new chat The next step was the most revealing. I opened a brand-new ChatGPT chat and uploaded the original AI-generated image. This new chat did not have the earlier conversation context. It did not know the prompt. It did not know the image had been generated as a fictional Amsterdam street. Then I asked: “Think like an OSINT analyst and geolocation analyst. Where is this, be as precise and accurate as you can. Explain your methodology and analysis.” This is exactly the kind of prompt many investigators might use. And this is where the AI failed dangerously. It answered: “This is Lange Niezel, Amsterdam-Centrum, Netherlands, in the De Wallen / Burgwallen Oude Zijde area.” It went further. It said the image appeared to be taken on Lange Niezel, looking toward the Oudezijds Voorburgwal / Korte Niezel side. It even gave approximate coordinates: 52.3748, 4.8985 . It rated confidence as high for the street and medium for the exact camera position. That is not a cautious hypothesis. That is a confident false geolocation. Original image as used in the new geolocation chat In a new chat, the same fictional image was treated as a real geolocation target. ChatGPT confidently identified it as Lange Niezel in Amsterdam. This is the moment every OSINT practitioner should pay attention to. The model was not simply uncertain. It produced a location. It gave a street name. It gave a neighborhood. It gave coordinates. It gave confidence language. It explained its supposed methodology. And it was wrong. The street was fictional. The danger of expert-sounding wrong answers This is one of the biggest risks when using AI in investigations. AI often does not fail by saying nonsense. It fails by sounding reasonable. It produces an answer that has the shape of expertise: “Most likely location.” “Key evidence.” “Methodology.” “Final assessment.” “Confidence: high.” That structure feels professional. It feels analytical. It feels like OSINT. But structure is not evidence. A confident format does not make a conclusion true. In this case, the model claimed the blue Amsterdam street-name sign on the right-hand black building was the decisive clue and appeared to read “Lange Niezel.” The image does not even contain a street name plaque ! It then built the rest of the location assessment around that interpretation. This is exactly how false geolocation can happen. One weak or imagined anchor becomes the foundation for a confident conclusion. The analyst (human or AI) sees something that resembles a clue, names it, and then builds a story around it. That is not verification. That is narrative construction. The follow-up: are there inconsistencies? After the false geolocation, I asked another important question: “Are there any inconsistencies in this image when it comes to shade, reflections, or objects?” This was the opportunity for the model to catch itself. It did not. It answered that it did not see strong evidence of manipulation from shadows, reflections, or object placement. It said the scene looked broadly internally consistent with a rainy or overcast Amsterdam street. It described the diffuse lighting as plausible. It said the wet cobblestones and sidewalk showed realistic reflections. It said the bicycles, bollards, pedestrians, street signs, façades, windows, and pavement lines all aligned with the same street perspective. Its assessment: “No major inconsistencies detected.” It rated the image as visually plausible and internally consistent. It said nothing in the shadows, reflections, object scale, or perspective strongly suggested AI generation, compositing, or object insertion. Again, this is not surprising. Modern AI-generated images can be internally coherent. They can have plausible lighting. Plausible reflections. Plausible object placement. Plausible architecture. Plausible perspective. That is why visual plausibility is not enough. A fictional image can be visually coherent. A real image can be visually strange. Therefore, “I see no obvious inconsistencies” does not mean “this is real.” It only means the visible pixels did not contain enough obvious contradictions. The final visual-forensics prompt: find AI tells Then I pushed harder: “Use all your knowledge and analyse the image to see if there are any AI tells in this image. Make it thorough.” This should have been the strongest test. The answer was even more revealing. ChatGPT concluded: “I do not see strong AI-generation tells in this image.” It assessed the image as: “Likely authentic or at least photograph-based.” It said there was no clear evidence of full AI generation and no obvious signs of object insertion, background replacement, or synthetic reconstruction. It described the scene geometry, perspective, text, lighting, reflections, object grounding, bicycles, people, architecture, vegetation, glass reflections, compression, and metadata. It even described the text as unusually coherent for a fully AI-generated image, stating that the “Koffie & Koek” sign and “Sinds 2013” looked readable and natural. It treated the apparent blue street-name signs as plausible and consistent with the previously identified location. The final conclusion was: “Likely real / photograph-based. No strong AI-generation tells detected. No obvious manipulation artifacts visible.” That is the central problem of this entire experiment. The image was AI-generated. But another AI analysis judged it likely real. Why this matters for OSINT This experiment shows three separate but connected failures. First, AI can generate a realistic image of a place that does not exist. Second, AI can later fail to recognize that image as synthetic. Third, AI can create a confident but false geolocation for that same fictional image. For OSINT practitioners, the third failure may be the most dangerous. A model saying “I don’t know” is manageable. A model saying “this is likely Lange Niezel, Amsterdam” with high confidence can actively mislead an investigation. It can send the analyst down the wrong street, literally and figuratively. It can create false leads. It can waste time. It can contaminate reporting. It can influence other analysts. It can become the first link in a chain of repeated errors. And because the answer sounds structured and professional, people may trust it too quickly. Why ChatGPT cannot simply recognize its own image The last part of your document addressed the obvious question: If ChatGPT generated the image, why can’t ChatGPT recognise it later? The answer is important. In a new chat, the model usually sees only the uploaded image. It does not automatically receive the original prompt, the previous conversation, the generation seed, the internal generation trace, or a database lookup of every image previously generated. There are two very different questions: Does this image look AI-generated? And: Was this exact image generated by ChatGPT? The first is visual analysis. It relies on clues in the pixels: lighting, geometry, text, reflections, shadows, object structure, metadata, compression, and so on. The second is provenance. It requires evidence about origin: metadata, watermarks, C2PA, logs, original files, platform history, or some other verifiable chain of custody. Those are not the same thing. A model can inspect an image and say it looks plausible. That does not prove it is real. A model can fail to find AI tells. That does not prove it was not generated. A model can say it cannot determine origin from pixels alone. That may be the most honest answer. The key lesson from the document is this: ChatGPT does not recognise a generated image as fake simply because ChatGPT generated it earlier. In a new chat, without creation history, metadata, watermarking, or external provenance, it must judge from visual clues alone. Modern AI images can be visually plausible enough that there are no reliable tells. That is not just a technical limitation. It is an evidentiary limitation. AI tells are indicators, not proof Many people still talk about AI image detection as if it is a checklist. Bad hands. Broken text. Strange shadows. Warped windows. Impossible reflections. Malformed cars. Melted bicycles. Repeating patterns. Weird faces in the background. Those clues can help. But they are not proof. There are two problems. First, modern image generators are improving. The obvious artifacts are becoming less obvious. Second, real photographs can also look strange. Compression, rain, reflections, low light, HDR, motion blur, rolling shutter, lens distortion, platform resizing, screenshots, and social media filters can all create suspicious-looking artifacts. That means both of these statements can be true: A real image may look fake. A fake image may look real. This is why “AI tell” analysis must be treated as one part of a broader verification process, not as the final verdict. The real question is no longer “Where is this?” Traditional geolocation usually begins with: Where is this? But in the age of generative AI, that question may come too late. The first question should be: Can this image be grounded in the real world at all? Before trying to identify the street, ask whether the image contains enough verifiable anchors to justify a geolocation attempt. Can you read a street sign? Can you match the house numbers? Can you verify the business? Can you match the façade sequence? Can you find the same bollard layout? Can you match the road surface and curb design? Can you verify the traffic signs? Can you find the same scene in street-level imagery? Can you corroborate it from independent images? If not, the right conclusion may be: “Visually plausible, but not geolocated.” That is much safer than inventing a street name. A fictional street can still be internally consistent One of the reasons this case is so powerful is that the image is not absurd. The lighting works. The reflections are plausible. The wet road makes sense. The perspective is coherent. The buildings look Dutch. The bikes look mostly believable. The street feels physically possible. But “physically possible” is not the same as “geographically real.” A fictional street can have coherent lighting. A fictional café can have readable text. A fictional building can have plausible windows. A fictional road can have reflections. A fictional image can pass a visual inspection and still fail reality. That is the new problem. AI no longer needs to create fantasy worlds. It can create ordinary worlds that never happened. The new OSINT workflow The final answer in your document gave the right teaching point: Do not ask ChatGPT to decide whether an image is real. Ask it to help generate testable hypotheses. That should become a standard practice. A better workflow looks like this. Preserve the original file. Do not overwrite it. Do not annotate directly on it. Do not rely on screenshots unless that is all you have. Check provenance first. Look for EXIF, C2PA , editing history, original filename, upload trail, platform compression, and whether the file is an original, a screenshot, a re-export, or an AI-generated file. Separate soft cues from hard anchors. “Looks like Amsterdam” is not evidence. “This exact façade sequence matches this exact street” is evidence. Create an anchor table. List every visible clue and classify it as readable, searchable, unique, and independently verifiable. Reverse-search the full image and cropped details. Search the shopfront, signs, façades, bikes, distinctive buildings, background objects, and road layout. Use street-level data. Compare with Google Street View, Apple Look Around, Mapillary, OpenStreetMap, local business listings, municipal sources, social media images, and any other relevant public imagery. Test urban logic. Do the bollards make sense? Do the traffic signs make sense? Does the road layout fit the country? Are the house numbers where they should be? Do the municipal details match the city? Use AI carefully. Ask it to list possible clues, contradictions, and verification steps. Do not let it deliver the final truth without independent corroboration. Use confidence language. Say “unverified,” “visually plausible,” “not geolocated,” “likely synthetic,” “contradicted by map evidence,” or “verified by independent street-level match.” Most importantly: document what failed. A failed geolocation is not automatically proof of fakery, but a disciplined negative search is still valuable. What this experiment really proves This experiment does not prove that every AI-generated image is impossible to detect. It does not prove that geolocation is dead. It does not prove that ChatGPT is useless for OSINT. It proves something more subtle and more important: Visual plausibility can no longer be treated as evidence of reality. The original image looked like Amsterdam. The first analysis knew it should be treated with caution. The annotation process accidentally demonstrated how AI can contaminate evidence by changing the underlying scene. A new ChatGPT chat then falsely geolocated the fictional image as Lange Niezel. A follow-up analysis found no major visual inconsistencies. A thorough AI-tell analysis judged the image likely real or photograph-based. And the final explanation showed why this happens: without provenance, the model is judging pixels, not origin. That is the whole problem in one case study. AI generated a fictional street. AI then believed the fictional street. The end of seeing is believing For decades, images carried an implied claim: This was somewhere. This happened. This existed in front of a camera. That assumption is now broken. An image may show a street that never existed. A protest that never happened. A building that was never built. A person who was never there. A military vehicle in a location it never visited. A disaster scene fabricated from statistical memory. A realistic image is no longer enough. In this new environment, seeing is not believing. Seeing is the beginning of verification. For OSINT practitioners, that means our tradecraft matters more than ever. Not tools. Not vibes. Not confidence. Tradecraft. Provenance. Source tracing. Geolocation. Corroboration. Falsification. Documentation. Confidence language. Chain of custody. Methodological humility. That is how we survive the age of synthetic evidence. Final lesson The most dangerous AI images will not always look spectacular. They will look boring. A rainy street. A café sign. A cargo bike. A few bollards. Some wet paving. A grey sky. A city you think you know. And then an AI will tell you where it is. With confidence. That is why OSINT practitioners must slow down, preserve evidence, extract anchors, verify externally, and resist the temptation to let a fluent machine turn plausibility into proof. The street in the image never existed. But the risk it represents is very real. Tags: AI tradecraft methodolgy Data Analysis geoint Intelligence Analysis Digital Evidence AI Risks in OSINT geoint geolocation Critical Thinking Risks AI Risks in Analysis AI Bias in OSINT Critical Thinking in AI AI Dependence AI in Investigations Critical Thinking in OSINT Verification in OSINT Synthetic Identity Detection Evidence Poisoning AI-Driven Deception OSINT analysis AI Recent Posts See All Evidence Poisoning: The OSINT Crisis Nobody Is Ready For AI May Not Replace Analysts. It May Break Them First. Critical Thinking Collapse 2.0: AI’s Impact on OSINT","image_urls":["https://static.wixstatic.com/media/038b0b_42ec7fcf8e4745e5b211b3de0ed6f22b~mv2.png/v1/fill/w_49,h_37,al_c,q_85,usm_0.66_1.00_0.01,blur_2,enc_avif,quality_auto/038b0b_42ec7fcf8e4745e5b211b3de0ed6f22b~mv2.png","https://static.wixstatic.com/media/038b0b_462d6bbb56694fe39eb64ed9d5e7daa6~mv2.png/v1/fill/w_49,h_37,al_c,q_85,usm_0.66_1.00_0.01,blur_2,enc_avif,quality_auto/038b0b_462d6bbb56694fe39eb64ed9d5e7daa6~mv2.png","https://static.wixstatic.com/media/038b0b_cc0087b846d046fea2f18789da2252ce~mv2.png/v1/fill/w_49,h_37,al_c,q_85,usm_0.66_1.00_0.01,blur_2,enc_avif,quality_auto/038b0b_cc0087b846d046fea2f18789da2252ce~mv2.png"],"local_images":["blog_data/images/blog_4a59b13cd215_0.bin","blog_data/images/blog_4a59b13cd215_1.bin","blog_data/images/blog_4a59b13cd215_2.bin"]}
diff --git a/blog_data/by_source/nixintel.jsonl b/blog_data/by_source/nixintel.jsonl
new file mode 100644
index 0000000000000000000000000000000000000000..f6d5bcbfd3616e114d0b05a261a39cc5bd88bf07
--- /dev/null
+++ b/blog_data/by_source/nixintel.jsonl
@@ -0,0 +1,20 @@
+{"source":"nixintel","url":"https://nixintel.info/","title":"","status":"ok","retrieved_at":"2026-08-29T16:29:57.551832+08:00","text":"Calculating Website Age & Tracking Changes With URL Dater Leave a Comment / OSINT Tools / Nixintel How can you determine the age of a webpage in a reliable way? URL Dater uses a range of different sources to present an accurate picture. Calculating Website Age & Tracking Changes With URL Dater Read More » Using SSL Certificates To Find Threat Actor Infrastructure 1 Comment / OSINT / Nixintel At last month’s SANS OSINT Summit I gave a talk the usefulness of SSL certificates for open source intelligence researchers. The talk looks at three recent examples of how information from certificate transparency logs can be used to discover, attribute, and unmask threat actor infrastructure. The video of the talk has now been published and you can Using SSL Certificates To Find Threat Actor Infrastructure Read More » Telegram For Cyber Investigators 2 Comments / OSINT / Nixintel Telegram is one of the most important platforms for OSINT investigators. I joined the Needlestack podcast to discuss how Telegram works and shared some practical OSINT advice along the way. Telegram For Cyber Investigators Read More » Digging Into Russian Disinfo Infrastructure 6 Comments / OSINT / Nixintel Disinformation and propaganda has been one of the key features of the war between Russia and Ukraine. One of the many groups that have sprung up to push pro-Russian propaganda narratives is a small hacktivist organisation called Beregini. This article by Givi Gigitashvili provides a useful introductory insight into the methods of Beregini by analysing Digging Into Russian Disinfo Infrastructure Read More » Verify Your Online Identities With Keybase 1 Comment / Security / Nixintel Twitter’s recent decision to remove blue check marks from accounts it has previously verified causes a number of issues for the platform and its users. One of the most obvious ones is around authentic identity. Without verification, how do I know that a particular account really does belong to the person or organisation who claims Verify Your Online Identities With Keybase Read More »","image_urls":["https://nixintel.info/wp-content/uploads/2023/04/twitter_profile.png","https://nixintel.info/wp-content/uploads/2023/07/Screenshot-2023-07-31-at-22.50.56.png","https://nixintel.info/wp-content/uploads/2026/01/Screenshot-2026-01-11-161045.png"],"local_images":["blog_data/images/blog_1e330956d596_0.bin","blog_data/images/blog_1e330956d596_1.bin","blog_data/images/blog_1e330956d596_2.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/about/","title":"About Me","status":"ok","retrieved_at":"2026-08-29T16:30:11.706439+08:00","text":"Home About About I am a highly experienced investigator and cybersecurity specialist. I specialise in Open Source Intelligence (OSINT) and have more than 15 years’ experience of conducting internet investigations into everything from cybercrime and fraud to nation state threat actors. In my law enforcement career I was a detective focusing on cyber crime, digital forensics, and internet research. Having built up my skills in traditional investigations of serious and complex crime I began to develop techniques and tactics to identify and prosecute criminals who used the internet, including some of the UK’s most prolific child sex offenders, fraudsters, and dark web criminals. I’m also an Instructor Candidate for the SANS Institute , the world’s largest information security research, training, and certification provider. I teach SEC497 Practical Open Source Intelligence and SEC587 Advanced Open Source Intelligence to students from Fortune 500 companies, government, military and law enforcement so that they will have the skills they need to have successful careers in cyber security and all aspects of internet investigation. I’m a confident and experienced public speaker, and I love to share my learning and research with others. I was also previously an executive board member of The OSINT Curious Project . This blog is purely for my own writing and research and my views are entirely my own. Twitter LinkedIn Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email","image_urls":[],"local_images":[]}
+{"source":"nixintel","url":"https://nixintel.info/author/nixintel/","title":"Nixintel","status":"ok","retrieved_at":"2026-08-29T16:31:02.622604+08:00","text":"Calculating Website Age & Tracking Changes With URL Dater Leave a Comment / OSINT Tools / Nixintel How can you determine the age of a webpage in a reliable way? URL Dater uses a range of different sources to present an accurate picture. Calculating Website Age & Tracking Changes With URL Dater Read More » Using SSL Certificates To Find Threat Actor Infrastructure 1 Comment / OSINT / Nixintel At last month’s SANS OSINT Summit I gave a talk the usefulness of SSL certificates for open source intelligence researchers. The talk looks at three recent examples of how information from certificate transparency logs can be used to discover, attribute, and unmask threat actor infrastructure. The video of the talk has now been published and you can Using SSL Certificates To Find Threat Actor Infrastructure Read More » Telegram For Cyber Investigators 2 Comments / OSINT / Nixintel Telegram is one of the most important platforms for OSINT investigators. I joined the Needlestack podcast to discuss how Telegram works and shared some practical OSINT advice along the way. Telegram For Cyber Investigators Read More » Digging Into Russian Disinfo Infrastructure 6 Comments / OSINT / Nixintel Disinformation and propaganda has been one of the key features of the war between Russia and Ukraine. One of the many groups that have sprung up to push pro-Russian propaganda narratives is a small hacktivist organisation called Beregini. This article by Givi Gigitashvili provides a useful introductory insight into the methods of Beregini by analysing Digging Into Russian Disinfo Infrastructure Read More » Verify Your Online Identities With Keybase 1 Comment / Security / Nixintel Twitter’s recent decision to remove blue check marks from accounts it has previously verified causes a number of issues for the platform and its users. One of the most obvious ones is around authentic identity. Without verification, how do I know that a particular account really does belong to the person or organisation who claims Verify Your Online Identities With Keybase Read More »","image_urls":["https://nixintel.info/wp-content/uploads/2023/04/twitter_profile.png","https://nixintel.info/wp-content/uploads/2023/07/Screenshot-2023-07-31-at-22.50.56.png","https://nixintel.info/wp-content/uploads/2026/01/Screenshot-2026-01-11-161045.png"],"local_images":["blog_data/images/blog_411c2c255975_0.bin","blog_data/images/blog_411c2c255975_1.bin","blog_data/images/blog_411c2c255975_2.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/contact/","title":"Contact","status":"ok","retrieved_at":"2026-08-29T16:30:15.301288+08:00","text":"Home Contact Contact To get in touch, please contact me via the form below. Alternately you can get in touch via LinkedIn . Please enable JavaScript in your browser to complete this form. Please enable JavaScript in your browser to complete this form. Name * First Last Email * Comment or Message Submit Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email","image_urls":["https://nixintel.info/wp-content/plugins/wpforms-lite/assets/images/submit-spin.svg"],"local_images":[]}
+{"source":"nixintel","url":"https://nixintel.info/copyright/","title":"Copyright","status":"ok","retrieved_at":"2026-08-29T16:35:04.916113+08:00","text":"Home Copyright Copyright © Steven Harris and nixintel.info, 2019-2023. Unauthorized use and/or duplication of this material without express and written permission from this site’s author/owner is strictly prohibited. Small excerpts and links may be used, provided that full and clear credit is given to Steven Harris and nixintel.info with appropriate and specific direction to the original content. You may NOT reuse or duplicate any content from this website as part of any training programme (whether private or public) or publish it elsewhere (whether for profit or not) without the express written authorisation of the site owner. Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email","image_urls":[],"local_images":[]}
+{"source":"nixintel","url":"https://nixintel.info/linux/build-your-own-custom-osint-machine-part-4/","title":"Build Your Own Custom OSINT Machine – part 4","status":"ok","retrieved_at":"2026-08-29T16:34:45.447812+08:00","text":"Home Linux Build Your Own Custom OSINT Machine – part 4 Build Your Own Custom OSINT Machine – part 4 9 Comments / Linux / By Nixintel The last post in this guide looked at how to install some useful OSINT programs for Linux directly from the internet. In this post I’ll show how to install some of the many popular Python-based OSINT tools that are available. It’s easy to feel intimidated by using the command line, but by the end of this guide it’ll be clear what pip, git, and Python are all about. Python is brilliant for carrying out a large number of repetitive tasks and sorting through data quickly. These tools can’t make your investigative decisions for you, but they can crawl the web and pull back data very quickly, certainly much faster than most browser-based tools will. In this guide I’ll go through the installation of reconaissance tool theHarvester step-by-step from the absolute basics all the way through to launching it with a custom alias. Then I’ll explain how to install recon tools like Photon , Sublist3r , and Gasmask , username search tool Sherlock , scraping tools for Twitter ( Twint ) and Instagram ( Instalooter ), phone number searcher PhoneInfoga , and password breach checker h8mail . It might seem like a lot now, but once you understand how these programs work, you’ll be cloning them from Github and using them for your research like there’s no tomorrow. Getting Started With Installation – Basics These programs don’t usually come with a nice shiny user interface like some of the programs you install from the Ubuntu Software Centre. This can make them seem complicated and installing them can cause a lot of frustration, but by the end of this guide you’ll know your Pip from your Git and be able to install a wide range of powerful OSINT tools. The guide is intended for people who are fairly new to Linux, so I’ll try and cover everything from the very beginning. In the DIY-Buscador Ubuntu machine, open up the terminal by pressing Ctrl+Alt+T . You’ll see something like this:   You live here now.   If you’ve never used a terminal before, don’t worry! The computer doesn’t care whether the instructions came from a shiny GUI that you clicked on or whether you typed the command into the terminal directly. For example in this previous post I showed how to install Stegosuite by finding it in the Ubuntu Store, clicking on “install” and entering my admin password to give it permission to run. In the terminal the exact same thing can be done by typing the following command: sudo apt install stegosuite sudo prompts me to enter my admin password and confirm that the program is authorised to run. Apt is simply the program that Ubuntu uses to manage software packages, so adding ‘install’ tells apt what I want it to do, and stegosuite tells apt which one of the thousands of available Ubuntu packages I want to install on my system. So it’s pretty obvious what this command would do: sudo apt remove stegosuite And stegosuite would be uninstalled, just like that. Notice that if you try to use apt without sudo, Linux won’t let you. If you’re not authorised, you aren’t allowed to modify the software or any part of the operating system. (On some older tutorials you might see “apt-get” instead of “apt”, but they do the same thing.) Getting Git Using sudo apt install programname works well for programs that are listed in the Ubuntu repository – but none of the OSINT Python tools we want to install are listed there. They’re all available on GitHub , so to get them installed on the OSINT machine it’s necessary to use a program called git . A few of the tools can also be installed using another program called Pip, but I’ll get to that shortly. Git is a complex tool used by developers for version control of their software, but for the purposes of this guide it’s only necessary to know that Git allows you to clone software directly from GitHub onto your computer. In the console, check to see what version of git is installed in Ubuntu by entering the following command: git --version You’ll be told that git is not installed! It isn’t part of Ubuntu by default, so quickly add it into your OSINT build with: sudo apt install git Press Y when prompted and git will install in a few moments. Pip and Python As of Ubuntu version 20.04, Python 2.7 is no longer installed in Ubuntu by default. The new default version is Python 3. To check this in the console type: python3 --version   The screenshot above is from Ubuntu 19.04, which did include Python 2. The latest and all future versions of Ubuntu will not include Python 2. Install With Pip Pip is a package manager for Python. It ensures that when you’re installing a Python program, all the necessary libraries and modules will be installed too. Usually these requirements are listed in a text file called requirements.txt, so installing all the necessary addons is usually as simple as: sudo pip3 install -r requirements.txt The other great thing about pip3 is that it allows you to install some Python programs with one simple command. This is much cleaner and easier than building software from GitHub. I’ll show how to install Twint this way later on. So for best practice, use the following guidelines: 1. If you have the choice to use pip to install directly (e.g. as with h8mail or Twint), use pip. 2. If not, use git. 3. If the program uses Python 3 (i.e. most of them) use python3 and pip3 in the console 4. Most tutorials often assume you’re running as root, i.e. with sudo and don’t explicitly mention it. In this build, it will always be necessary to put sudo in front of any pip or pip3 commands. Installing theHarvester It’s always easier to learn by doing rather than just reading so I’m going to demonstrate how to install theHarvester. theHarvester is an established tool that is used to find out about a particular domain. It will pull back e-mail addresses, PGP keys, IP addresses and other information about the domain you’re investigating. theHarvester Github page can be found here: h ttps://github.com/laramies/theHarvester . This URL is important, so copy it from your browser’s navigation bar and keep it in the clipboard. Open the terminal with Ctrl + Alt + T and enter the following, you can just paste the URL you copied into the terminal with Ctrl+Shift+V (not just Ctrl+V like on the regular Desktop): git clone https://github.com/laramies/theHarvester Now git is cloning all those files posted on GitHub directly to a folder in your home directory called theHarvester. Once git has finished cloning, move to that directory by typing cd theHarvester (note the terminal is case-sensitive) cd simply means “change directory”. To list the contents of the directory, simply enter: ls You’ll see something like this: There’s a file in there called requirements.txt. Before we can run theHarvester, we need to install those Python library requirements with pip3. Enter the following in the console: sudo pip3 install -r requirements.txt Pip will then install the extra software that is needed: Now it’s all done! To run theHarvester, stay in theHarvester directory and enter: python3 theHarvester.py -h Notice if you’ve typed python and not python3 the program won’t run because it needs the newer version of Python. All this command is doing is telling python3 to run a script called theHarvester.py. The -h flag on the end tells the script to open the help guide for the program. If it’s working correctly you’ll see something like this: Ta-da. It’s beyond the scope of this article to explain how to use theHarvester, but there’s a simple introduction here and in many other places on the web. This completes the installation of theHarvester – but there’s an customisation we can make to our OSINT build setup that will make using theHarvester just a little smoother. theHarvester Alias Shortcut Typing “python3 ~/theHarvester/theHarvester.py” before you start every single query gets a bit tiresome. Fortunately in Linux it is easy to customise everyting and so it’s possible to create a shortcut, known as an alias. This can be done by editing the .bashrc file that controls all your terminal settings. Open the terminal with Ctrl+Alt+T again and enter nano ~/.bashrc Nano is just the terminal’s built-in text editor. This opens up the .bashrc file that needs to be edited. When it opens, scroll to the bottom and add the following lines: #alias for theHarvester alias theharvester='python3 ~/theHarvester/theHarvester.py' Use Ctrl + X to exit, and Y when prompted to ask if you want to save the changes. Notice I made theharvester all lower case – it just makes typos less likely. Now close the terminal, and then open a new one so the changes take effect. Now just type: theharvester -h and theHarvester runs straight away. You can also run the command to launch queries directly e.g. theharvester -d somerandomsite.org -b google -l 500 That’s the basic formula for installing Python programs from GitHub. In the remainder of this article I’ll explain how to install a program with pip.   Installing Twint with Pip Pip makes installing packages a lot easier, so for this example I’m going to show it can be used to install Twint. Twint is a really flexible Twitter scraper. It grabs all kinds of data from Twitter and exports it to a wide range of formats like csv or SQL. There’s a good introduction to Twint here . The link to the Twint GitHub page is here. Notice that unlike theHarvester, Twint can be installed with either Git or Pip, (or even by using a Python virtual environment, which is not within the scope of this guide). As per the rules of thumb I mentioned above, if given a choice between Git or Pip, always go with Pip. It’ll soon be clear just how much less complex this is. In the terminal copy and paste the following: sudo pip3 install --upgrade -e git+https://github.com/twintproject/twint.git@origin/master#egg=twint Remember to preface the command with sudo or you’ll have trouble running it. Once it’s completed, simply type twint -h And you’ll see the program has installed correctly! It isn’t even necessary to create an alias, because Pip did this automatically during the installation. Example usage would be: twint -u nixintel -o nixinteltweets.csv --csv This would scrape all the Tweets from my Twitter account and save them to a csv file for further analysis. Installing Other Python OSINT Programs I’ve shown how to set up your custom OSINT machine for installing programs either with Git or directly with Pip. The rest of the guide will look at some other useful OSINT tools, what they do, the necessary commands to install them, and the entry needed in a .bashrc file to create an alias. For the purposes of this article, I’ve installed all of these programs in my DIY-Buscador VM, so I’ll vouch for the fact that all of these methods currently work!   Instalooter   GitHub Page : https://github.com/althonos/InstaLooter Scrapes content from a designated Instagram account. Requires IG login but no API key. Git or Pip ? Pip Console command: sudo pip3 install instaLooter (note upper-case L) Usage: instalooter -h (note lower case L) Alias : Automatically instalooter by default   H8mail 2.0   GitHub Page : https://github.com/khast3x/h8mail PyPi Page : https://pypi.org/project/h8mail/ H8mail checks e-mail addresses to see if their credentials have ever bene found in a breach. The real power of h8mail comes with its ability to query a 45GB breach compilation. This is available separately. You’ll need a lot of extra space in your VM if you want to fit this in. Git or Pip : Pip Console command : sudo pip3 install h8mail Usage: h8mail -h Alias : h8mail by default   Photon     GitHub page : https://github.com/s0md3v/Photon Photon is a fast OSINT crawler. Point it at a domain to recover associated e-mail addresses, DNS info, subdomains, social media accounts, and other information. Git or Pip: Git Console commands : git clone https://github.com/s0md3v/Photon cd Photon sudo pip install -r requirements.txt python3 photon.py -h Alias: alias photon='python3 ~/Photon/photon.py' Usage (with alias): photon -h   Sherlock   GitHub Page : https://github.com/sherlock-project/sherlock Sherlock is a fast username searcher. I previously wrote a usage guide and review here . Git or Pip? Git Console command: git clone https://github.com/sherlock-project/sherlock   cd sherlock sudo pip3 install -r requirements.txt python3 sherlock.py -h Alias: alias sherlock='python3 ~/sherlock/sherlock.py'   Usage (with alias) : sherlock nixintel     Gasmask   GitHub Page : https://github.com/twelvesec/gasmask An auto reconnaissance tool similar to Photon or the Harvester. Note this program now runs with Python 3. Git or Pip? Git Console command: git clone https://github.com/twelvesec/gasmask cd gasmask sudo pip3 install -r requirement.txt python gasmask.py -h Alias : alias gasmask='python3 ~/gasmask/gasmask.py' Usage (with alias) : gasmask -h   Sublist3r   GitHub page: https://github.com/aboul3la/Sublist3r A tool for identifying subdomains by querying the data held by search engines. Can bruteforce if necessary. Git or Pip? Git Console command: git clone https://github.com/aboul3la/Sublist3r cd Sublist3r sudo pip3 install -r requirements.txt python3 sublist3r.py -h Alias: alias sublister='python3 ~/Sublist3r/sublist3r.py' (note I dropped the 3, I made too many typos) Usage (with alias) : sublister -h     PhoneInfoga   GitHub page : https://github.com/sundowndev/PhoneInfoga/ Crawls dozens of resources to conduct OSINT on a target phone number. Be sure to read the Wiki article on bypassing the Google Captcha before using it. Git or Pip? Git Console command: git clone https://github.com/sundowndev/PhoneInfoga cd PhoneInfoga sudo pip3 install -r requirements.txt python3 phoneinfoga.py -h Alias: alias='python3 ~/PhoneInfoga/phoneinfoga.py' Usage (with alias): phoneinfoga -h     That concludes this part of the guide to building your own custom OSINT Linux machine. If you had little Linux experience before and managed to get these programs installed and working then kudos to you because the command line can be an unforgiving place but as you can see it can be used to do some really powerful things. The same method can be used to install other GitHub based tools like Skiptracer , Knock , Cloudflair, and many others. A few of these tools benefit from the addition of API keys, but that’s really for a separate post. This guide and the ones before it should make it clear just how simple it can be to create your own custom OSINT VM. In the next post I’ll explain how to clone and backup your OSINT VM in case it breaks, how to transfer it to another computer, and how you can hash it if needed. After that I’ll also suggest some useful OSINT addons for Firefox and Chrome. Part 5 of this series can be found here .                 Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 9 thoughts on “Build Your Own Custom OSINT Machine – part 4” mr loop 1st November 2019 at 11:36 am Hello, The harvester is not loading, I have triple checked the Alias I get the following message Errno 2 no such file or directory Loading... Reply Nixintel 1st November 2019 at 6:23 pm Does this error only occur when you try to run Harvester with an alias? I.e. does it run if you run it directly from the Harvester directory itself e.g /home/user ~ $ python theHarvester.py -h ? If it runs from the directory but not with the alias then the error is most likely because there is an issue with the file path or name. The command line is case sensitive so double check that the path in the alias is correct, including case sensitivity. Loading... Reply Mr pop 2nd November 2019 at 10:37 am Hello, Thanks will have a look. Just trying to sort out the geckodriver at the moment. Thanks for the reply and the amazing website 🙂 I really want to improve and get in to OSINT. This is a create resource. Loading... Reply Mr loop and pop 2nd November 2019 at 10:57 am Also it says that permission is denied from access ‘docker’ docker pull sundowndev/phoneinfoga:latest IN short I have managed to run PhoneInfoga, however after about 4 attempts of it working it is now showing the catcha (blocked). I have installed geckodriver which seems to let me run recon scans but it believe docker pull sundowndev/phoneinfoga:latest will solve the issue fully. Loading... Reply Mr poopy butthole 7th November 2019 at 2:29 pm So I managed to get back to it, and it is all working, I just started again and double checked everything. Thanks for the help and the site. PS glad to see your a Type O Negative fan \\m/ Loading... Reply Mr Mingster 20th February 2020 at 9:07 pm I have version 18 of ubuntu I have version 3.6.9 of python. Everything else is working but everytime i try and use the code for Git or for pip3 it says command not found. I cant access any of the programmes i need the most. Thank you for your tutorial anyway, it is great, hopefully you can help me with this.. Loading... Reply Nixintel 20th February 2020 at 10:10 pm It sounds like you might still need to install git and pip. To do so try: sudo apt install git sudo apt install python-pip (for Python 2.x) sudo apt install python3-pip (for Python 3.x) Try again once you’ve installed these and you should have a bit more luck. Loading... Reply Pingback: 如何制作自己的互联网存档 - iYouPort Pingback: POWERFUL OSINT investigative Techniques and Tactics (2024) Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_001-1.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_004-1.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_005-1.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_007-1.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_007.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_008-1.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_008.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_009-1.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_009.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_010-1.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_010.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_011.png","https://nixintel.info/wp-content/uploads/2019/06/Buscador-DIY-Running-Oracle-VM-VirtualBox_012-1.png","https://secure.gravatar.com/avatar/6474e292fccee2439c9f52a365d6c91badf863bb6b39a2291ebfcb2434ee84f0?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/85770c43be059ed877c3b5fa99e8b62e6a9b2406c217807dddcdd6a375c726b4?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/a8dbec59c215a7304ee0e9f72018ce377e1a7869da6ef4dc675dc1de3278de1e?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/b2c7aae6a5e70d8f81889d9b94e259653a95278a6af60e284bf4f8b8cfeb90f0?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/c65f0a237f8f1e9db129a777410a38151fe50b11f21f9951adc5863c9e163201?s=50&d=mm&r=g"],"local_images":["blog_data/images/blog_083acfa87d18_0.bin","blog_data/images/blog_083acfa87d18_1.bin","blog_data/images/blog_083acfa87d18_2.bin","blog_data/images/blog_083acfa87d18_3.bin","blog_data/images/blog_083acfa87d18_4.bin","blog_data/images/blog_083acfa87d18_5.bin","blog_data/images/blog_083acfa87d18_6.bin","blog_data/images/blog_083acfa87d18_7.bin","blog_data/images/blog_083acfa87d18_8.bin","blog_data/images/blog_083acfa87d18_9.bin","blog_data/images/blog_083acfa87d18_10.bin","blog_data/images/blog_083acfa87d18_11.bin","blog_data/images/blog_083acfa87d18_12.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/osint-tools/calculating-website-age-tracking-changes-with-url-dater/","title":"Calculating Website Age & Tracking Changes With URL Dater","status":"ok","retrieved_at":"2026-08-29T16:33:23.083499+08:00","text":"Home OSINT Tools Calculating Website Age & Tracking Changes With URL Dater Calculating Website Age & Tracking Changes With URL Dater Leave a Comment / OSINT Tools / By Nixintel How do you know how old a webpage really is? A core part of website investigation is determining precisely when site was created or when an article was published. For most sites this is rarely an issue of concern, but for websites that are intentionally misleading it can be more challenging. Websites created for fraud, phishing, disinformation or other deceptive purposes frequently misrepresent the age of the site in order to appear more established and authoritative than they really are. It’s also helpful to be able to find out exactly when an article was published and detect subsequent modifications. There are several ways to do this. Article publication dates might be obvious, but it is also trivial to edit publication timestamps and they cannot be relied upon. The Internet Archive can also be a useful indicator, but it has gaps in coverage and is slow to query. In any case a first crawl of a website will by definition always lag the actual creation of the site so it’s better to go upstream to find more reliable signals. To make this process quicker and easier I’ve put together URL Dater from a collection of old Python scripts that I’ve used for a few years but with a web interface to make the tooling and results a little easier to work with. URL Dater timeline output showing Last-Modified header timestamps and registration update information for Bellingcat.com URL Dater collects three sources of information to validate the age of a web page. First it uses RDAP (the replacement for WHOIS) to find out when the original domain was first registered and also when the registration was last updated. Secondly it uses certificate transparency logs to determine when the very first SSL certificate for that website was issued. Finally it connects to the target URL and reads the Last-Modified header timestamp from any images that are embedded on the page. These data points are combined together to produce a timeline showing when the site and its content were created or modified. RDAP RDAP (Registration Data Access Protocol) is a new standard for querying domain registration records. It replaces WHOIS, which was deprecated in January 2025 . It’s far easier to work with programmatically because the data is returned in a standard JSON format that can be easily parsed. The only limitation with this method is that a few TLDs still don’t currently support RDAP queries , and some that do choose not to share registration date information (why DENIC , why?). The RDAP information shows when a domain was first registered and when the registration records were last updated. If URL Dater doesn’t return RDAP registration information for the website domain then you can view WHOIS records via Big Domain Data or Whoxy as an alternative. First SSL Certificate Since almost all websites now support HTTPS it’s safe to assume that pretty much any website you want to research will have an SSL certificate. Any website without an SSL certificate is likely to be deranked in search results and users will also receive warnings in their browser that the site is insecure . It is extremely rare to find a modern website that doesn’t have an SSL certificate – even if it was created for malicious or deceptive purposes. This is helpful for researchers because since 2013 SSL certificate providers have made every certificate they issue publicly auditable via certificate transparency logs . URL Dater checks these logs via crt.sh to find the “Valid From” timestamp for the first security certificate issued for a domain. This fraudulent company imitated an existing organisation that was older and more established. Using URL Dater to retrieve the timestamp from the first SSL certificate showed that it was This provides a high confidence, third-party verified timestamp for when a website likely first went live. Just be aware that SSL certificates have a “Valid From” field and not an “Issued At” field, so the while the first certificate time is reliable and precise, it isn’t accurate to the exact minute. You can read more about this in the FAQ . Last Modified Headers The final indicator collected by URL Dater are the Last-Modified timestamps from images embedded on a webpage . This indicates the time when an image was last modified on the web server and is a reliable indicator for when the content was added to the webpage. Note this is separate from any timestamp metadata embedded in the image itself. The Last-Modified header timestamp value is derived from the web server itself and is significantly more difficult to alter or modify. Example of Last-Modified headers for images retrieved from the URL https://www.bellingcat.com/news/2025/12/17/how-russias-invasion-is-impacting-ukraines-youth/ on the Bellingcat website. The results distinguish between favicons and other images when presenting the findings. The main reason for doing this was that in practice site owners modify favicons far less regularly compared to other images on webpages so I found it helpful to make the distinction when trying to date the content accurately. Plotting the Last-Modified header timestamps I love Python and have used it my investigations for years but I never really took to learning front end web development. I’ve really benefited from the use of tools like Cursor to convert my Python scripts into Flask apps with a JS frontend. It also allowed me to add in some useful extra features like the ability to create timelines to visualise results. Results can also be exported in PDF, PNG or CSV format. Timeline visualisation for the URL https://www.bbc.co.uk/news/articles/ckgj1m1ze8go , as of 11 Jan 2026. It shows when the main domain was registered and updated, when the first SSL certificate was issued, and when specific images were last modified on the webpage. Users can zoom in on the timeline to plot exactly when specific images were Last-Modified. Installation and Known Issues The code is in the URL Dater GitHub repository . It’s a single container Docker app so as long as you have Docker installed on your host system you just need to clone the repo and build the container. git clone https://github.com/nixintel/urldater cd urldater docker compose up --build The main issues you’re likely to encounter are limitations of the underlying tools. For example, some TLDs don’t yet support RDAP , crt.sh (used for SSL history) is often offline, and some websites simply don’t use Last-Modified headers. For further details about the data is collected and what its limitations are, please read the FAQ . The demo server at Urldater.app is also running on a very lightweight server that occasionally struggles to process data from larger websites, which may result in performance issues. I strongly recommend self-hosting this on your own hardware for better performance. Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2026/01/Screenshot-2026-01-11-161045.png","https://nixintel.info/wp-content/uploads/2026/01/image-1.png","https://nixintel.info/wp-content/uploads/2026/01/image-2.png","https://nixintel.info/wp-content/uploads/2026/01/image-3.png","https://nixintel.info/wp-content/uploads/2026/01/image-4.png","https://nixintel.info/wp-content/uploads/2026/01/image-5.png","https://nixintel.info/wp-content/uploads/2026/01/image-6.png"],"local_images":["blog_data/images/blog_7b882fcc2ee7_0.bin","blog_data/images/blog_7b882fcc2ee7_1.bin","blog_data/images/blog_7b882fcc2ee7_2.bin","blog_data/images/blog_7b882fcc2ee7_3.bin","blog_data/images/blog_7b882fcc2ee7_4.bin","blog_data/images/blog_7b882fcc2ee7_5.bin","blog_data/images/blog_7b882fcc2ee7_6.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/osint-tools/six-tools-to-help-with-geolocation/","title":"","status":"ok","retrieved_at":"2026-08-29T16:32:35.676688+08:00","text":"Home OSINT Tools Six Tools To Help With Geolocation Six Tools To Help With Geolocation 3 Comments / OSINT Tools / By Nixintel If you’ve been interested in geolocation for any length of time, you’ll already be familiar with some of the most common tools that researchers make use of: Google Maps & Street View , Google Earth , reverse image search tools , Suncalc , and so on. There are many lesser-known tools that are also useful and can help to fill gaps in your investigations. Let’s have a look at a few of them. What Is Where What Is Where is a more user friendly way of querying the Open Street Map database. It helps you to build queries in a similar way to Overpass Turbo , but without the complex query language and syntax. So if you want to find parks in London, or schools within 200m of a main road in Berlin, you can build the queries using a series of drop down menus that match OSM’s pre-defined categories. For example you can pick a category from the menu like “Aerodrome” and then use an appropriate keyword from the OSM Tag database to refine your search. This makes your results more accurate but will also help to keep the server response time low. The aerodrome category is refined by adding the “military” keyword. If you get stuck there are several example queries in the site documentation that you can customise and adapt for your own needs. It’s still worth learning the Overpass Turbo query language if you intend to use the tool regularly, but What Is Where is a great place to get started. Kartaview Kartaview works in a similar way to Google Street View in that it offers street-level imagery that is accessed from an interactive map but it differs from Street View in two important ways. Firstly the images are uploaded directly by users from their mobile devices. There is no Kartaview Car. Secondly Kartaview offers coverage in areas where Google lacks it, such as in Germany. It’s also very similar to Mapillary , even if it is not as well known. It’s possible to see the content uploaded by each individual user. Kartaview contributors are incentivised to upload content via a leaderboard ranking system which rewards the amount of content uploaded. Users also have their own profile pages where it is possible to see the images uploaded by each user. For example this is the user profile of current all-time leader JB Brown who has uploaded more than 30 million images at the time of writing. Unlike other platforms, Kartaview also displays some metadata associated with the uploaded images such as timestamps, device, and operating system information. Open Traffic Cam Open Traffic Cam is a collection of publicly accessible traffic camera feeds from the USA. Simply zoom to the section of the map that you’re interested in, and click on one of the pins to view the camera footage. Getting results with this tool can be a little hit and miss. Some cameras are offline or no longer updated so there are a few dead links but the majority still seem to work. Google Earth: Sunlight & Shadows Google Earth Pro (the desktop version) needs little introduction as a geolocation tool, but you might not be aware of the Sunlight tracker that allows you to plot the sun position and shadow lengths that help with verifying the time of day. It lacks the fine detail of Suncalc, but it presents the information in a way that is much clearer. Here’s Frankfurt in Google Earth (3D buildings are enabled). Frankfurt in Google Earth. By clicking on the sun icon in the menu bar, a slider appears that can be used to adjust the time and date. The shadow and sun position will adjust automatically. Adjusting the slider changes the time and shadows adjust accordingly. The sun position moves too. Here’s the sun as seen from Frankfurt at around sunrise time on 24th July 2022: Sunrise view. Now here’s the same position, but in the middle of the night. Note the star constellations. The stars reflect the Earth’s rotation. If you want to be more precise with your timings, click on the spanner icon next to the slider and enter your time/date parameters manually: The Date and Time options allow you to enter specific times more easily. F4 Map F4Map uses Open Street Map data to plot individual buildings on a 3D map. It’s an extremely useful tool when there is no 3D building coverage in Google Earth and when your verification requires a high level of detail. Here’s Hamburg as rendered by F4Map: F4Map renders individual buildings with a high level of detail. F4 Map also supports the display of shadows, weather conditions and the sun position at different times of day, although this is limited to just morning, noon, evening, and night. To turn features on and off, just click on the settings menu and choose Graphic Options. F4Map allows time/date/weather customisations. The 3D buildings are based on Open Street Map data, so global coverage is much wider than 3D building locations in Google or Bing Maps, which rely on complex layers of aerial imagery for the 3D effect. Even more useful is the incorporation of 3D terrain data to render landscapes as they appear in real life. It isn’t enabled by default, so to activate it use Settings > Graphic Options > Ground Elevations. Here’s Innsbruck before and after Ground Elevations are enabled: Before: no 3D terrain enabled. After: the same location with 3D mode and ground elevation enabled. 3D Sun Path 3D Sun Path is made by Andrew Marsh and lets you visualise the sun’s position, azimuth and shadow length when you’re trying to chronolocate an image. It’s similar to Suncalc and in my opinion it displays the necessary information in a much clearer way. 3D Sun Path shows the sun’s bearing, azimuth (height in the sky) and shadow length for any given date/time/location. It is also integrated with a wide range of open source mapping and satellite image tools for more refined results. Satellite images and a variety of sun-path tools are incorporated into the tool. Simply choose your location and enter time/date parameters to track the sun’s position and shadow lengths for that location. These are just a few of the many useful but less well-known geolocation tools. If you found this interesting I’ve written many other posts about geolocation techniques , and there are other useful tools in my OSINT bookmark collection . I’ve also made a couple of Ten Minute Tips videos on geolocation that you can find here . Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 3 thoughts on “Six Tools To Help With Geolocation” katinukas 25th July 2022 at 8:35 am F4 Map: “Oops! Unauthorized F4map API usage. If you are this website administrator, please contact the support at [email protected] .” Loading... Reply Juan Smith Perera 28th September 2022 at 6:40 pm Great post. Great tools. Thanks for sharing Loading... Reply Jesús 28th December 2022 at 7:52 pm Thanks a lot. Loud and clear. Very well explained. Loading... Reply Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2022/07/image-1.png","https://nixintel.info/wp-content/uploads/2022/07/image-10.png","https://nixintel.info/wp-content/uploads/2022/07/image-11.png","https://nixintel.info/wp-content/uploads/2022/07/image-12.png","https://nixintel.info/wp-content/uploads/2022/07/image-13.png","https://nixintel.info/wp-content/uploads/2022/07/image-14.png","https://nixintel.info/wp-content/uploads/2022/07/image-15.png","https://nixintel.info/wp-content/uploads/2022/07/image-16.png","https://nixintel.info/wp-content/uploads/2022/07/image-17.png","https://nixintel.info/wp-content/uploads/2022/07/image-4-2048x963.png","https://nixintel.info/wp-content/uploads/2022/07/image-5.png","https://nixintel.info/wp-content/uploads/2022/07/image-6.png","https://nixintel.info/wp-content/uploads/2022/07/image-7.png","https://nixintel.info/wp-content/uploads/2022/07/image-8.png","https://nixintel.info/wp-content/uploads/2022/07/image-9.png","https://nixintel.info/wp-content/uploads/2022/07/image.png","https://secure.gravatar.com/avatar/7dcda0872150b5af240ee89c9a4b48b315799f2e9e28cbac9bfa20f1dec9d10d?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/9be338a10be4ebfb9ff429763c776af53b6c0bae891d96381504453bad27bd91?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/cf49af0034a3311009fc23b4918ea8e470990ce3415018e0e7854f00b053ff82?s=50&d=mm&r=g"],"local_images":["blog_data/images/blog_ef012822ce5f_0.bin","blog_data/images/blog_ef012822ce5f_1.bin","blog_data/images/blog_ef012822ce5f_2.bin","blog_data/images/blog_ef012822ce5f_3.bin","blog_data/images/blog_ef012822ce5f_4.bin","blog_data/images/blog_ef012822ce5f_5.bin","blog_data/images/blog_ef012822ce5f_6.bin","blog_data/images/blog_ef012822ce5f_7.bin","blog_data/images/blog_ef012822ce5f_8.bin","blog_data/images/blog_ef012822ce5f_9.bin","blog_data/images/blog_ef012822ce5f_10.bin","blog_data/images/blog_ef012822ce5f_11.bin","blog_data/images/blog_ef012822ce5f_12.bin","blog_data/images/blog_ef012822ce5f_13.bin","blog_data/images/blog_ef012822ce5f_14.bin","blog_data/images/blog_ef012822ce5f_15.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/osint/counting-crowds-in-public-spaces/","title":"","status":"ok","retrieved_at":"2026-08-29T16:31:13.867606+08:00","text":"Home OSINT Counting Crowds In Public Spaces Counting Crowds In Public Spaces 5 Comments / OSINT / By Nixintel This week’s huge protests in Israel drew huge crowds to the streets – but how many people took part? Crowd sizes are often used as evidence to show how widely supported a particular cause is, so being able to determine how many people took part in a demonstration is an important skill for those working in verification. Fortunately counting crowds in public spaces has been made easier than ever before by the creators of MapChecking . It is powered by Google Maps and allows researchers to plot a geographic area and then calculate the number of people that could fit in that space. There are three simple steps to follow: 1. Find the location. 2. Define the count area. 3. Calculate the crowd density. Let’s work our way through them to work out roughly how many people are shown in the image above. Find The Location First we need to identify the precise location. Fortunately with public protests this isn’t usually too difficult due to widespread media coverage and documentation. The image above was taken in Tel Aviv, looking along Giv’at HaTahmoshet St. A panoramic photo was taken during the protest and uploaded to Google Street View. The tall cylindrical building on the left is a government complex. Someone who was at the protest has already uploaded a panoramic photo from this location so verifying that this is the correct place is quite straightforward. Define The Count Area Now we’ve identified the location, the next thing we need to do is to use MapChecking to draw in the area where we can see the crowd in the original photo. We need to try and replicate this area: For the sake of accuracy it’s important to remember that there will be people in the crowd that we cannot see in this map due to the obstruction of buildings. For greater accuracy combining several photos from different angles would be better, but for the sake of this tutorial we’ll keep it simple. We’ve already identified the location on the map so now we need to replicate this in MapChecking. This is as simple as navigating to the location in the map interface and using the mouse to draw the area where we see the crowd in the photo. The final shape looks something like this: MapCheck will use the highlighted shape to calculate how many people were present. Calculate The Crowd Density There’s one last step before we can work out roughly how many people are present in the image. We need to know the density of people per square metre so we can know how many are in the search area. MapChecking allows us to adjust the density with a slider: The slider is used to adjust the crowd density. The biggest challenge is how to actually work out the density in the first place. The crowd isn’t evenly spaced so we need to accept that our answer will not be ultra-precise down to a single figure, but usually an approximate value is enough. To help with this the site provides several sample images that show what different crowd densities look like, as documented in this research by Keith Still . Since we have additional close up footage of the crowd thanks to the Google Photo spheres we can compare them with the baseline images from Keith Still’s research to form a rough idea of the density. Here’s the crowd density in the middle of the protest: Crowd density as captured at the scene and uploaded to Street View. Let’s compare them to the baseline images. The crowd looks quite packed, but people are still able to hold their phones out in front of them and hold flags so they are not so squeezed that they can’t move. It doesn’t look dense enough for 6 people per square metre. It’s certainly higher than 2 people per square metre though. There isn’t this much space between people in the crowd in the picture: Somewhere between 3-4 people per square metre looks like a better approximation: To calculate the final number, I’m going to use the figure of 3.5 people per square metre. The crowd is denser in the centre, but more dispersed at the edges. Using the slider to enter the density value tells us how many people are in the area that we drew to match the photo: At a density of 3.5 people per sqm, there are approx 112,000 people in the image. To reflect the slight uncertainty caused by the varied crowd density, it’s helpful to be able to adjust the slider to get an upper and lower range of possible crowd size. At 2.5 people per square metre the crowd size drops to just under 80,000, rising to 140,000 for a density of 4.5 people per square metre. The correct figure will be part way between these two. If you enjoyed this post, check out my other ones on geolocation here . Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 5 thoughts on “Counting Crowds In Public Spaces” Arnaud G 29th March 2023 at 1:50 pm Thanks this is super interesting. In the case of the recent demonstrations in France, taking the example of Paris, how would you go about counting the # of participants in a day? My concern is that crowds move along a certain path and numbers may vary at different times. Unions numbers and police numbers vary greatly. Loading... Reply Nixintel 29th March 2023 at 2:04 pm Two approaches that would help: 1) As many photos of possible of the areas where you are trying to measure. 2) Identify the approximate time of the photos. In your conclusions you should then be able to show a range of possible crowd sizes but also how they peaked and troughed at different times. e.g. at 1200 we observed between X and Y number of people in locations A,B and C. By 1900 this had increased to between XX and YY etc. A more advanced technique for counting moving crowds would be to run video footage fo the crowd and count them with Amazon’s Rekognition People Path tool, but this is more complex to achieve. https://docs.aws.amazon.com/rekognition/latest/dg/persons.html Loading... Reply Pingback: Counting Crowds In Public Spaces – NixIntel – Library Project XIII: Seven Heavenly Rabbits Edition Pingback: Counting Crowds In Public Spaces - Whalers Blog Pingback: Counting Crowds In Public Spaces - Whalers Blog Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2023/03/2-sqm.png","https://nixintel.info/wp-content/uploads/2023/03/3-4sqm.png","https://nixintel.info/wp-content/uploads/2023/03/6-sqm.png","https://nixintel.info/wp-content/uploads/2023/03/cover.png","https://nixintel.info/wp-content/uploads/2023/03/crowd_area.png","https://nixintel.info/wp-content/uploads/2023/03/crowd_mapped.png","https://nixintel.info/wp-content/uploads/2023/03/density1.png","https://nixintel.info/wp-content/uploads/2023/03/photo_bubble.png","https://nixintel.info/wp-content/uploads/2023/03/slider.png","https://nixintel.info/wp-content/uploads/2023/03/slider2.png","https://nixintel.info/wp-content/uploads/2023/03/street_overview.png","https://secure.gravatar.com/avatar/a8dbec59c215a7304ee0e9f72018ce377e1a7869da6ef4dc675dc1de3278de1e?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/ad642ab4353b7901b76df43cf9ab015a7ee05ae84eeb8a982e72e064d22604fa?s=50&d=mm&r=g"],"local_images":["blog_data/images/blog_ecb6460988fe_0.bin","blog_data/images/blog_ecb6460988fe_1.bin","blog_data/images/blog_ecb6460988fe_2.bin","blog_data/images/blog_ecb6460988fe_3.bin","blog_data/images/blog_ecb6460988fe_4.bin","blog_data/images/blog_ecb6460988fe_5.bin","blog_data/images/blog_ecb6460988fe_6.bin","blog_data/images/blog_ecb6460988fe_7.bin","blog_data/images/blog_ecb6460988fe_8.bin","blog_data/images/blog_ecb6460988fe_9.bin","blog_data/images/blog_ecb6460988fe_10.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/osint/digging-into-russian-disinfo-infrastructure/","title":"Digging Into Russian Disinfo Infrastructure","status":"ok","retrieved_at":"2026-08-29T16:33:50.871413+08:00","text":"Home OSINT Digging Into Russian Disinfo Infrastructure Digging Into Russian Disinfo Infrastructure 6 Comments / OSINT / By Nixintel Disinformation and propaganda has been one of the key features of the war between Russia and Ukraine. One of the many groups that have sprung up to push pro-Russian propaganda narratives is a small hacktivist organisation called Beregini . This article by Givi Gigitashvili provides a useful introductory insight into the methods of Beregini by analysing the content of some of their recent leaks. For this post I thought it would be interesting to see what insights might be gained from digging into the web infrastructure of the Beregini group website. It’ll also be a good opportunity to run through a few command line techniques to practice website investigation. The Goal and The Tools We’re going to start with a few passive recon techniques to help to identify where the main Beregini website is hosted, and what (if anything) this can tell us about the group. Although Beregini are highly active on Telegram, they also have a website at bg14.ru . We can start by gathering a few data points about the website to see what we can find out. The Beregini website at bg14.ru . As far as possible I’m going to use command line tools to find the information that I need. I’m a strong believer that OSINT practitioners who can use simple commands to gather and process raw data have a big advantage when it comes to intelligence collection. The main reason is that this makes it much easier to begin to scale and automate research in a way that is much more difficult to do with browser based methods. Let’s have a look at a few basic commands to get started. Whois Detailed Whois records with real personal data in them are largely a thing of the past, but that doesn’t mean that they aren’t useful. Here’s the Whois record for bg14.ru: domain: BG14.RU nserver: harleigh.ns.cloudflare.com. nserver: pablo.ns.cloudflare.com. state: REGISTERED, DELEGATED, UNVERIFIED person: Private Person registrar: PIN-RU admin-contact: https://whois.pinspb.ru created: 2022-03-09T12:40:12Z paid-till: 2024-03-09T12:40:12Z free-date: 2024-04-09 source: TCI Performing a Whois lookup with a web-based tool is quite straightfoward, but most versions of Linux and Mac OS have a command line whois tool built in. It has a lot more options than a regular web-based Whois lookup, but a basic enquiry looks like this: whois bg14.ru This returns the same data as in the web tool. Instead of taking a screenshot I can save the output to a text file for documentation purposes. whois bg14.ru > whois_lookup.txt Regardless of the method used, the Whois data doesn’t tell us who owns the site (of course) but it does reveal three useful snippets of information: The site is using Cloudflare nameservers. This probably means that finding the true IP address of the website (and thus the real hosting company and server location) is going to require a little extra effort. The admin contact for the site is associated to another domain – pinspb.ru . We’ll need to look at who this domain belongs to and what it is for. The domain was created on 9th March 2022, which ties in with the site first being recorded by the internet archive on 16th March 2022. However Beregini have been active since at least 2016. This most likely means they have another web presence somewhere else that we’ll need to try and locate in due course, although we won’t cover that in this post. The Internet Archive first documented the site in March 2022, a week after the domain was registered. DNS Records Time to start using the command line again. To find where the domain is hosted we need to know the IP address. We can use the built in Unix tool dig to find this. Here’s the basic command: dig bg14.ru Which returns: ; <<>> DiG 9.16.1-Ubuntu <<>> bg14.ru ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51636 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;bg14.ru. IN A ;; ANSWER SECTION: bg14.ru. 300 IN A 172.67.163.61 bg14.ru. 300 IN A 104.21.50.131 This is far too noisy to read effectively. We can trim the results by using the +noall and +answer options like this: dig bg14.ru +noall +answer The results are now much easier to read. We have two DNS A records that show the IP addresses where the website is located: bg14.ru. 300 IN A 104.21.50.131 bg14.ru. 300 IN A 172.67.163.61 We still need to think about documentating our research as we go along. To do this we can tidy up the output of the command a little bit more and save the output to a CSV file: dig bg14.ru +noall +answer | awk '{sub(/\\.$/, \"\", $1);print $1 \",\" $5}' > ipaddresses.csv To save the data to a nice tidy CSV we can pass the result of the dig command using the pipe ( | ) symbol to the awk command. Awk is very powerful and lets us modify text output on the fly. In this case the first part of the awk command sub(/.$/, \"\", $1) removes the trailing dot from the domain name in the first field ( $1) and replaces it with an empty value ( \"\") . The next step of the awk command print $1 \",\" $5 will print fields 1 and 5 from the dig results, and place a comma between them. The output of this command is saved to a file ipaddresses.csv , which looks like this: bg14.ru,172.67.163.61 bg14.ru,104.21.50.131 You might be thinking at this point that this all looks quite nerdy and so far you haven’t got any extra data that you couldn’t have grabbed from a tool like DNSDumpster . If you’re only looking at one single domain that is possibly true (depending on your typing speed and willingness to rely on cached results instead of live data…), but what if you want to grab the same information for 5, 10, 500, or 10000 domains at once? Collecting data this way is much faster and easily repeatable than manually copying and pasting domain names into Central Ops or View DNS to get the same data. Who Owns The IP Address? So far we have two IP addresses for the Beregini website, but who do they belong to? Since Whois records are published for IP addresses as well as for domains we can stay in the command line and find that out who these IP addresses belong to with another Whois lookup. A word of caution at this point: IP address whois records only show the ISP or hosting company that a particular IP address was allocated to. It does not tell you which of that organisation’s clients or customers was using that IP address at any particular time. This means that we can’t use IP whois records to identify individuals, but we can at least know which ISP or hosting organisation they use. Here’s the command to find who owns one of the bg14.ru IP addresses: whois 172.67.163.61 This query returns a lot of information, including details about who owns this IP address: NetRange: 172.64.0.0 - 172.71.255.255 CIDR: 172.64.0.0/13 NetName: CLOUDFLARENET NetHandle: NET-172-64-0-0-1 Parent: NET172 (NET-172-0-0-0-0) NetType: Direct Allocation OriginAS: AS13335 Organization: Cloudflare, Inc. (CLOUD14) RegDate: 2015-02-25 Updated: 2021-05-26 As we suspected from the original Whois lookup, the organization field reveals that Beregini are using an IP address belonging to Cloudflare. This means finding their true IP address will be a little bit difficult, but it is still possible. Finding The IP Address Behind Cloudflare There’s a common misconception among internet investigators that Cloudflare are a hosting company. They are not. Cloudflare is a Content Delivery Network (CDN). Cloudflare relays content that is hosted elsewhere all across the world through its vast global network of servers. This speeds up the delivery of content to users and also means that Cloudflare can use its huge resources to protect sites from DDOS and malicious traffic. It’s a great resource but the unfortunate side affect for investigators is that when you query the IP address of a domain that uses Cloudflare you only get the IP address of a Cloudflare CDN server that is near(ish) to your location. This effect also explains why if you used the same dig command that I used earlier, you probably got different IP addresses to the ones shown above. Cloudflare protects websites and speeds up content delivery, but the content is hosted elsewhere. So we need to find a way to find the real IP address for bg14.ru. This is a complex topic and there isn’t one single method that works every time. I gave a talk on this subject called “ Finding Fraudsters Behind Cloudflare ” at the 2022 SANS OSINT Summit that goes into this in a lot more detail. For now we’ll focus on one quick and easy(ish) method that actually works to find the Beregini website’s real IP address by using Censys . Censys Query Censys is a a huge collection of thousands of different data points collected from all across the web. It constantly gathers information about the services, open ports and other data that it finds at each IP address it visits. As well as host data, Censys also logs the details of security certificates and parses them into a searchable format. The result is a vast collection of useful datapoints that we can query to find information about sites and services that we are looking for. It’s beyond the scope of this article to discuss Censys in more depth, but you can read more about their collection methods here . The Censys search portal at https://search.censys.io Censys isn’t Google. You’re unlikely to be able to throw keywords into the search bar and hope you can find what you’re looking for (although sometimes you might). Censys has it’s own query language that we can use to search for specific types of data, so we’ll need to think carefully about exactly which datapoints we want to look for. There’s a few places we could start, but I’m going to see if any IP addresses can be linked to any certificates that mention bg14.ru. The certificate transparency log for bg14.ru at https://crt.sh My rationale for starting here is that the certificate transparency log for bg14.ru shows that many certificates have been issued for the site by Let’s Encrypt and that Beregini have opted not to use Cloudflare’s own certificate service. There’s nothing unusual about this, but it might mean that we can use Censys to search for hosts where there is a Let’s Encrypt certificate with a common name that matches bg14.ru. If Censys has previously found this certificate and associated it to a non-Cloudflare host we might be able to find a little gap that leads to the real IP address. The Censys query will looks something like the one below. It tells Censys to show any hosts where there is a security certificate containing the common name “bg14.ru”: services.tls.certificates.leaf_data.subject.common_name:bg14.ru Entering the search query using the Censys syntax language. Sure enough, our hunch was correct. Censys has logged at least one certificate for bg14.ru and they’ve associated it to an IP address…and this one doesn’t belong to Cloudflare. The IP address linked to the bg14.ru domain by Censys. Could 91[.]243[.]50[.]197 be the real IP address for the Beregini website? It’s possible. We’ll look at a method for verifying this shortly, but let’s see what other information Censys found first. Whois information for the IP address. There’s some Whois information included in the Censys entry. It tells us that the IP address where bg14.ru is hosted belongs to an ISP based not in Ukraine, but in St Petersburg, Russia. Remember that Beregini purport to be dissatisfied Ukranians – but the infrastructure they are using certainly isn’t based in Ukraine, it’s in Russia. This is an important point although it isn’t completely conclusive. There doesn’t have to be a firm geographic link between an organisation and the hosting arrangements for its website. Yet of all the countries in all of the world where Beregini could have chosen to host their server, they chose a hosting company based in St Petersburg. Screenshot of the website at pindc.ru, translated with Google Translate. The hosting company website at pindc.ru refers visitors to their main website at pinspb.ru . If this second domain sounds familiar that’s because we came across it the in the admin contact email for the bg14.ru Whois entry. It looks like Beregini are using the St Petersburg company for both their hosting and domain registration arrangements. Thanks to a user-uploaded photo, we can even see what the inside of the data centre looks like courtesy of Google Street View . A photo of the inside of the data centre where bg14.ru is hosted. Source: https://goo.gl /maps/UyMvgbXYHkTbDq2A6 On the balance of probabilities this tends to support the hypothesis that the Beregini group are Russian based and backed, rather than the dissident Ukranians of their public persona. This finding is not conclusive by itself, but it is certainly an interesting place to begin further enquiries. Final Verification So far we’ve used completely passive techniques to find information about the Beregini website and we’ve got a fairly decent hunch about the true IP address for their website and its hosting arrangements. We can still do better than “decent hunch” and actually verify whether or not the website really is located there. These techniques are active and involve connecting to the website directly, so consider OPSEC measures like a VPN when undertaking research like this. We’re going to use the command line one last time. It seems likely that the true IP address for the Beregini website is 91[.]243[.]50[.]197 , so we’re going to use the curl command to see if we can grab the bg14.ru website content directly from that IP and either confirm or rule out our theory. First let’s grab the website content directly with a URL. curl will default to the IP address returned by a DNS request, so this will be directly from Cloudflare. curl -k https://bg14.ru -vv The -vv option provides more verbose output so we can see what curl is doing when it retrieves the webpage. The -k option tells curl to skip any issues caused when connecting via https. As expected, we get all the raw CSS and HTML from the webpage as served via Cloudflare: * Trying 172.67.163.61:443... * TCP_NODELAY set * Connected to bg14.ru (172.67.163.61) port 443 (#0) *snip* < server: cloudflare < cf-ray: 7ef83309897874b1-LHR < alt-svc: h3=\":443\"; ma=86400 ... <link rel=\"pingback\" href=\"https://bg14.ru/xmlrpc.php\"> <title>BEREGINI</title> etc... What if we try and grab the site content directly from the IP address? This won’t always work, especially when a webserver has been configured to ignore direct connections to the IP address or if multiple sites share the same IP, but we can see if it’s still possible. Here’s the command: curl -k https://91.243.50.197 -vv And the result: * Trying 91.243.50.197:443... * TCP_NODELAY set * Connected to 91.243.50.197 (91.243.50.197) port 443 (#0) ... SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 * ALPN, server accepted to use h2 * Server certificate: * subject: CN=bg14.ru * start date: Jun 17 02:19:31 2023 GMT * expire date: Sep 15 02:19:30 2023 GMT * issuer: C=US; O=Let's Encrypt; CN=R3 * SSL certificate verify ok. We don’t get the full web page content this way, but we do pull back the security certificate for bg14.ru . It looks like our hunch is proving to be correct. There’s one more technique to try. We can tell curl to ignore the Cloudflare IP address returned by DNS records and instead force it to try and resolve the website at our target IP. If it can, the site content should appear in the terminal. If it can’t, we’ll get nothing back. curl -k https://bg14.ru --resolve bg14.ru:443:91.243.50.197 -vv The addition of the --resolve option tells curl to use our target IP address to connect to the site on port 443 (HTTPS). Here’s the result: Added bg14.ru:443:91.243.50.197 to DNS cache * Hostname bg14.ru was found in DNS cache * Trying 91.243.50.197:443... * TCP_NODELAY set * Connected to bg14.ru (91.243.50.197) port 443 (#0) ... * Server certificate: * subject: CN=bg14.ru * start date: Jun 17 02:19:31 2023 GMT * expire date: Sep 15 02:19:30 2023 GMT * issuer: C=US; O=Let's Encrypt; CN=R3 * SSL certificate verify ok. ... <link rel=\"pingback\" href=\"https://bg14.ru/xmlrpc.php\"> <title>BEREGINI</title> etc... Success! We’ve managed to retrieve the bg14.ru site content directly from the original hosting server and verified what we found with Censys. This means we can be confident about the site’s true IP address, ISP, and server location. It also reveals useful additional information about Beregini’s infrastructure and vendor choices that we can use in further research/ I’m an experienced investigator and OSINT practitioner and I’m currently looking for new work. If you think my skills could help you or your organisation, then please get in touch . Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 6 thoughts on “Digging Into Russian Disinfo Infrastructure” Kenshiro Watanabe 4th August 2023 at 7:19 pm Great article on disinformation and verification! Thank you so much! Loading... Reply Luris Sucak 7th August 2023 at 10:33 pm Interesting stuff! Learning new stuff every day. I’m surprised I didn’t know that about Cloudflare Loading... Reply thearmchairdetective 25th August 2023 at 9:35 am Nice One, so glad the blogs still alive. Miss your tweets. Loading... Reply Docal 27th June 2024 at 3:08 pm Well done Loading... Reply Teter 27th June 2024 at 4:44 pm Very nice Loading... Reply Pingback: Digging Into Russian Disinfo Infrastructure - Whalers Blog Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2023/07/Screenshot-2023-07-31-at-22.43.21.png","https://nixintel.info/wp-content/uploads/2023/07/Screenshot-2023-07-31-at-22.50.56.png","https://nixintel.info/wp-content/uploads/2023/07/image-1.png","https://nixintel.info/wp-content/uploads/2023/07/image-2.png","https://nixintel.info/wp-content/uploads/2023/07/image-3.png","https://nixintel.info/wp-content/uploads/2023/07/image-4.png","https://nixintel.info/wp-content/uploads/2023/07/image-5.png","https://nixintel.info/wp-content/uploads/2023/07/image-6.png","https://nixintel.info/wp-content/uploads/2023/07/image-7.png","https://nixintel.info/wp-content/uploads/2023/07/image-8.png","https://nixintel.info/wp-content/uploads/2023/07/image.png","https://secure.gravatar.com/avatar/0133cb1352133a63fd006c5f6a7a4770558e65d737bfb197e798faa0255d7f52?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/193fd8c154214c0e9ddc9c0cd3ce9ca5094f5855c9b103e954865a4138343f66?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/4786774c85f22a5c9b0050d0e512f453512db3515fba17adadfddce8a6b09036?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/69e81abba6af60daff3d0e6640b598b18a1d39c0ac344d0e46a42108835a845f?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/fff61f74f260c1aa431b806b98deffcd0dbc242fe6316e39f60909cc89c25225?s=50&d=mm&r=g"],"local_images":["blog_data/images/blog_7828d506708f_0.bin","blog_data/images/blog_7828d506708f_1.bin","blog_data/images/blog_7828d506708f_2.bin","blog_data/images/blog_7828d506708f_3.bin","blog_data/images/blog_7828d506708f_4.bin","blog_data/images/blog_7828d506708f_5.bin","blog_data/images/blog_7828d506708f_6.bin","blog_data/images/blog_7828d506708f_7.bin","blog_data/images/blog_7828d506708f_8.bin","blog_data/images/blog_7828d506708f_9.bin","blog_data/images/blog_7828d506708f_10.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/osint/geolocation-at-the-retail-park/","title":"","status":"ok","retrieved_at":"2026-08-29T16:30:21.797994+08:00","text":"Home OSINT Geolocation: At The Retail Park Geolocation: At The Retail Park 3 Comments / OSINT / By Nixintel Some images are easier to geolocate than others. If an image is easy to geolocate it is generally because at least one of the following three conditions apply: The image context makes it clear. For example there are GPS coordinates embedded in the image, or there is information about the location posted to the internet alongside the image. A reverse image search tool like Google Lens or Yandex is able to automatically recognise details in the image that identify the location. There are researchable map markers in the image, for example sign posts, business names, prominent landmarks etc. Sometimes none of these conditions apply. When this is the case geolocation becomes much harder and a more methodological structure is needed. Here’s a walkthrough of such an approach to find where the photo below was taken. The challenge photo. The photo was originally posted by Conor Nolan at 15:28 UTC on Jan 15th 2023. Conor tells us that the image was taken “just now” so at least we know when the image was taken. The problem is we don’t know much else. There’s no helpful GPS data, no luck with a reverse image search, and not much in the way of geographic information that we can easily search for straight away. We need a more structured methodology to find where Conor took this photo. I have written about gap analysis many times before and will use the same simple investigative structure here. There are four questions to follow to find the answer: What do I know? What does this mean? So what do I need to know? How do I find out? So let’s start at the beginning… What Do We Know? There’s little information in Conor’s Twitter profile and his bio says he’s located in London (note: as of 14th April it says Ireland, but it said London at the time this image was posted). There’s certainly not much in the way of immediate accessible information that we can research. It’s often tempting to give up at this point because there doesn’t appear to be any obvious way forward. This is often the case with more challenging images but there are other techniques we can apply to get as much data out of the image as possible. There is always more than you think. The original image was taken at about 15:28 UTC on 15th Jan 2023, but there isn’t much other information. By playing a short game of 20 Questions with the image, we force ourselves to extract as much information as we can about the image and its context. Armed with 20 different data points, we will have lots of new lines of research to follow up until we find the location, and if we still can’t find it we at least know that we have tried everything. We already have a couple of starting points, so let’s find our 20 data points by studying the photo as thoroughly as possible: The image was taken at 15:28 UTC on Jan 15th 2023. Conor (the photographer) has London in his Twitter location bio. It was daylight when the image was taken. The black car in the foreground is right hand drive. Conor is in a car park. The buildings resemble a retail park. Shop #1 has a red hoarding. Shop #1 sells furniture, bedding, appliances and audio. The name of shop #2 is not visible, but it has a red, orange, green and blue hoarding. Shop #3 is hard to see, but we can see a yellow hoarding. Shop #4 is called “Maxi” something and has a red and white sign. Some Christmas decorations are still visible. Shop #5 appears to have a red and white sign. The retail buildings are made of long rectangular blocks (metal or concrete?) The roof is not flat, it has a two-tier structure (this might help when it comes to aerial imagery later…) The roof is supported by external posts. Shadows from the support posts are cast onto the front of the building. This will help with orientation. The weather conditions are bright with some cloud. No evidence of rain. There’s a blue advert/sign with white text on the far left of the image. Some of these details are more important than others, but we won’t necessarily know exactly which ones until the end. Some details like the shop names are more likely to lead the location than the other details, but the small details will help with the fine tuning and verification at the end. What Does This Mean? Time to move to the next phase of gap analysis. We’ve established what we know (and it’s probably a lot more than we first thought) so next we have to figure out what all these data points tell us. It might not look like it yet, but we’ve already got enough data to get us to the objective quite quickly. Here’s what our findings tell us: Very few countries drive on the left side of the road. ( Source ) The right hand drive car means this is a left-hand drive country. Given that it was daylight at the location at 15:28 UTC on Jan 15th 2023 this means that the UK or Ireland is the correct place (the time and daylight means it can’t be Australia etc). Conor’s bio said London – but that doesn’t mean he took the picture there. The correct location will be a retail park with a car park in front of it. There will be a shop whose name ends in u, x or y. If English is the language then y is more likely at the end of the name than u or x. The shop sells furniture, bedding and electrical and audio equipment. There’s a second shop that might be easier to identify. It’s called “Maxi” – something and has a red and white sign style. The store fronts are facing roughly west. Conor is facing east. We can tell this because the shadows indicate the late afternoon sun is coming from over Conor’s shoulder, so west is behind him. This also means the long row of shops will be orientated roughly along a north-south line. When we find the approximate location, we should be able to verify that all the other details (roof style, posts, shop signs etc) are present. All our research so far means that if we can find a retail park in the UK or Ireland that has a “Maxi-?” store (Shop #4) alongside a furniture/bedding/electrical store that matches shop #1 and faces roughly west, we will find the correct location. If there is more than one matching location we can use the smaller details (posts, roof design, building materials etc) to eliminate the incorrect possibilities. What Do We Need To Know? To find the answer we need to choose our strongest line of enquiry. In this case we could either search for stores in the UK and Ireland that sell furniture/electrical goods and end in y, or we could choose to research stores called “Maxi”. You could really choose either as they are both likely to lead to a specific store. I decided to start with the “Maxi” store since it’s clearer what the name is than the large furniture store. This means that we need to know what the Maxi stores are (with matching name and logo) and where all their retail park stores are in the UK and Ireland. Then when we have found all these, we can eliminate all the retail parks where the shop layout, building, and orientation details do not match. How Do We Find Out? Let’s begin by searching for stores that are called “Maxi” in the UK. A Google search with a wildcard for the store name will help (since we don’t yet know if Maxi is a full or partial store name). A Google search to find stores with “Maxi” in their name. There are a few unhelpful results but the first result that mentions a Maxi- retailer is this one which relates to the Maxi Zoo chain of pet stores. The website tells us that Maxi Zoo has 29 stores in Ireland. A Google Image search for Maxi Zoo stores leads to this Shutterstock collection of Maxi Zoo storefronts . By comparing the images to the photo it looks like we’re on the right track. The original “Maxi” logo in the source image. Sample Maxi Zoo storefront images from Shutterstock. It seems like a good potential match. We’ve already established that the image is most likely in the UK or Ireland on the basis of the right-hand drive vehicle. A little extra research into Maxi Zoo shows that it has stores in Ireland, but none in the UK. This will prove to be helpful since it will mean we only have to focus on Ireland rather than the UK to find the correct location. Finding The Right Store Based on what we’ve found so far, we need to focus on trying to identify which one of the 29 Maxi Zoo stores in Ireland Conor was next to when he took the picture. As we look at each location we can quickly check if any of the other shops or architectural features we pulled from the original image are present. If they aren’t the location can be discounted. Google Maps makes this process quite straightforward. By focusing the map on Ireland and ticking the “Update results when map moves” option the stores are highlighted as the map moves around. All the Maxi Zoo store locations. Clicking on the link on the left hand side of the map brings up a picture of the store so each one can be quickly ruled in or out. 29 stores sounds like a lot to get through but with this method it only takes a few minutes. We can quickly see that this store does not match. In this case we can see straight away that the Maxi Zoo in Blanchardstown is not the one in the original picture. The storefront architecture doesn’t match. After a few more false starts, the Maxi Zoo in Waterford looks a little more promising. Notice the store sign hangs vertically down like in the original photograph. The shop next door (shop #3) has a yellow sign and on first glance the architecture seems to match. It might not be right, but it definitely can’t be ruled out. We need to take a closer look. The best way to do this is with Google Street View. There’s no direct coverage of the car park itself but the coverage from the road outside is good enough to make an assessment: This is where the time spent focusing on tiny details at the start pays off. If we’re right about the location, we should be able to see all of them present in the image above. Let’s check: Harvey Norman – the signs, logo and font match the original image. This is the bedding, appliances and audio store (shop #1). Next door is a shop with the rainbow coloured hoarding. It’s in the same place as in the original image. We can see that shop #2 is a Home Focus At Hickeys. Compare this image to Conor’s original: 3. Next door to Home Focus we can see that the shop with the yellow sign is a Halfords (Shop #3) . 4. The two tier roof between Harvey Norman and Home Focus is in the same place as in the original image. The metal block panels and external roof support architecture all match as well. 5. The only piece of information we are given at the start is that the image was taken at 15:28 UTC on 15th Jan 2023. The shadows in the original image suggested that the building should be aligned roughly North-South, with Conor looking east. The orientation looks good: To verify this is correct, we can use Suncalc to see if the shadows at the location match up with what Conor’s photo shows. Suncalc says that the shadows should be orientated like this: This matches perfectly with the shadows in the original image – perfect! So we can see that our structured methodology has served us well and made geolocating this image possible even with somewhat limited initial information. There is always more information in an image than first appears and we can use every last piece of it to find what we are looking for. If you enjoyed this post check out my other geolocation posts here . Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 3 thoughts on “Geolocation: At The Retail Park” Kenny Johnson 18th April 2023 at 1:03 pm Excellent walk-thru! Thank you. Loading... Reply Bal Krishna 24th April 2023 at 9:49 am Wonderful walkthrough. Very well explained. Loading... Reply Pingback: Geolocation: At The Retail Park - Whalers Blog Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2023/02/Fmhfr7YWIAALw9W-2048x1536.jpg","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-15.34.19.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-15.51.51.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-15.53.37-2048x631.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-16.51.29-2048x1411.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-17.03.27.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-17.08.29.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-17.50.08-2048x827.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-17.56.34.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-18.05.49.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-18.12.56.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-18.15.08.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-18.25.05.png","https://nixintel.info/wp-content/uploads/2023/04/Screenshot-2023-04-14-at-18.31.10.png","https://secure.gravatar.com/avatar/26c1c40d2c7caa6d5f2d87a2b34a2b71f6386891aa88a49e0976436fc85e6cdd?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/f75cfac195779401a22d854a1f4f8edf927204aa6000f5fa69acb2af86a9a7c4?s=50&d=mm&r=g"],"local_images":["blog_data/images/blog_2d7647e66e95_0.jpg","blog_data/images/blog_2d7647e66e95_1.bin","blog_data/images/blog_2d7647e66e95_2.bin","blog_data/images/blog_2d7647e66e95_3.bin","blog_data/images/blog_2d7647e66e95_4.bin","blog_data/images/blog_2d7647e66e95_5.bin","blog_data/images/blog_2d7647e66e95_6.bin","blog_data/images/blog_2d7647e66e95_7.bin","blog_data/images/blog_2d7647e66e95_8.bin","blog_data/images/blog_2d7647e66e95_9.bin","blog_data/images/blog_2d7647e66e95_10.bin","blog_data/images/blog_2d7647e66e95_11.bin","blog_data/images/blog_2d7647e66e95_12.bin","blog_data/images/blog_2d7647e66e95_13.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/osint/geolocation-tips-techniques/","title":"Geolocation Tips & Techniques","status":"ok","retrieved_at":"2026-08-29T16:33:20.467468+08:00","text":"Home OSINT Geolocation Tips & Techniques Geolocation Tips & Techniques 1 Comment / OSINT / By Nixintel In this video Technisette and I joined David Bombal to demonstrate some different geolocation techniques. We covered quite a few topics including: EXIF Data Using terrain features to find locations with Google Earth Removing unwanted parts of an image to do better reverse image searches Cropping and reverse searching images with Bing and Google Lens Extracting data from an image to research and pivot Plus a couple of speed runs to see how quickly we can identify a few locations. Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 1 thought on “Geolocation Tips & Techniques” IT Infrastructure Management 28th December 2022 at 7:30 am I am so glad you shared this information. It is very helpful for me. Loading... Reply Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://secure.gravatar.com/avatar/ff17f4496e7b61c8a2fbd928d94200f8c1fb6a02ee4a3074047cbb07f0b626c6?s=50&d=mm&r=g"],"local_images":[]}
+{"source":"nixintel","url":"https://nixintel.info/osint/obtaining-useful-information-from-a-kik-profile/","title":"Obtaining Useful Information From A Kik Profile","status":"ok","retrieved_at":"2026-08-29T16:34:31.98765+08:00","text":"Home OSINT Obtaining Useful Information From A Kik Profile Obtaining Useful Information From A Kik Profile 5 Comments / OSINT / By Nixintel 2026 update – this technique is no longer valid. It was written in 2019 and doesn’t reflect how Kik currently works. Last week I posted about how it was possible to obtain hi-res images and other information from Instagram and Twitter accounts by amending some of the URLs that the applications present by default. In a similar way it’s possible to obtain extra information about a Kik user profile by conducting queries with the correct URL. Kik is a popular mobile chat app that does not ask users to provide much personal information for verification, which is partly why it attracts so many unpleasant individuals . Nevertheless it does provide a little useful information about the user, including a hi-res profile pic. The URL we need to adjust is as follows: https://ws2.kik.com/user/<username_goes_here> If the user has a valid account, the URL will direct you to a small JSON file containing the user’s provided first name, last name, the time they last modified their profile image (in Unix time), and a link to a hi-res version of their profile picture. For a quick example, we can apply this to a Kik account which claims to be an “official” account for Zendaya (whether this is really the official account or not is beside the point). Her Kik username is “zendayakik”, so the URL to query is: https://ws2.kik.com/user/zendayakik We can now see the JSON file that gives the following information: First name Last name (which of course is left blank, maybe Zendaya was a bad example to choose!) Time the profile picture was last modified. This is in unix time, which you can convert to regular human-readable time with a tool like Unix Converter . If this is the original profile picture, it can give an indication when the account was created. URL to a hi-res version of the user’s profile picture. This is a much clearer image than the one available in the app by default. As always, there’s no substitute for verifying that the information Kik provides is actually true, but this technique can help to give you a head start for any Kik-based enquiries you need to make.   Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 5 thoughts on “Obtaining Useful Information From A Kik Profile” Rin 5th September 2023 at 11:18 pm It said that the page requested was not found… Anything u can do to help?? Loading... Reply Nixintel 16th October 2023 at 5:00 pm It is most likely the case that this technique no longer works. I haven’t tried it for a long time but this article is several years old now. Loading... Reply Yer 15th December 2023 at 7:36 pm It’s still works. Just make sure you don’t put the on either side of the username. And when you enter the help for the image it gives you remove all backslashes that they put next for the forward slashes. Also remove the “ and } at the end. Loading... Reply IamTheOneWhoFlops 17th June 2025 at 11:37 pm Nope, looks like they finally got wise to that url trick. normally it would have fed the users profile page, so things like join date and last seen i believe. But it just returns page not found now. I wonder if they just moved the endpoint and its still accessable or if they actually changed how the app works when requesting data from the server… Might have to decompile a fresh apk and see if anything interesting pops out… Loading... Reply Roger 30th June 2026 at 12:40 am Nope, it doesn’t work Loading... Reply Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2019/05/zendaya.jpg","https://secure.gravatar.com/avatar/507d27af4644a28ccf723c2e24448154ecb694507e42b53ff570650506a79180?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/58b400369457cf6a513e2363bb5698cebc89a2b6aa685f2c291570a446d23e9b?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/a8dbec59c215a7304ee0e9f72018ce377e1a7869da6ef4dc675dc1de3278de1e?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/c8ca64c08939b1ca71560ecfca2a43d33c20f0da616def26af1cf2418bb20e0c?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/e1978a38f6258a8fca4b5f38a6c4164fcbb62474f059815b7310f1ff42a679d9?s=50&d=mm&r=g"],"local_images":["blog_data/images/blog_13c0476833a5_0.jpg"]}
+{"source":"nixintel","url":"https://nixintel.info/osint/quiztime-how-to-clean-pictures-for-better-search-results/","title":"","status":"ok","retrieved_at":"2026-08-29T16:31:47.56668+08:00","text":"Home OSINT Quiztime: How To Clean Pictures For Better Search Results Quiztime: How To Clean Pictures For Better Search Results 5 Comments / OSINT / By Nixintel In last week’s Wednesday Quiz Tilman Wagner posted this photo and asked us several questions about it: 1) Who posted it and where? 2) What was the occasion? 3) Did Tilman participate, and if so, how? So where to start? We need to know the location before we can answer any of Tilman’s questions. There are a few clues in the image that might make a good starting point: the language on the screen is is in British English (organisation spelled with an ‘s’) and it suggests a networking event or meeting of some kind. There’s a WiFi sign but unfortunately the network name is too small to read, or else we could have had some fun with Wigle . No quick wins so far. An important rule in geolocation (and investigation generally) is that the more unique or distinctive a feature is, the more useful it is for finding the origin of a photo. By far the most distinctive feature is the unusual pyramid shaped building that it visible from the window. If we can locate this, we can work out where the photo was taken from. This is the most distinguishing feature in the photo and will be the key to geolocating it. Cropping the image and conducting a reverse image search seems to be the most obvious way to find the building, but there’s a big problem with that approach in this instance. When we look through a window with human eyes, we subconsciously ignore details like window frames and curtains to focus on what is outside. Unfortunately reverse image search engines aren’t smart enough to do this yet and they don’t distinguish between the foreground noise and the background detail that we are interested in. If you tried to solve this puzzle with this method you probably got a lot of matches that looked like this: Yandex search results find a lot of matches…but only for window frames. Reverse image search engines show their limitations here. They focus on the window frame and curtains but don’t focus on the building outside that we’re interested in. So what can we do? Removing Noise From The Image What we need is an easy way to remove the foreground clutter from the image so we can conduct a better reverse image search. Cleanup.pictures is very easy to use and makes it easy to remove unwanted features (like window frames) from images. Instead of leaving gaps, the software guesses what should appear in the image based on the rest of the image content and fills in the details. It will be perfect for what we need. First we upload our cropped image to the website. Cropped image ready to upload to Cleanup.pictures. Next we use the eraser tool to highlight the details we want to remove. Highlight the areas for removal. Here’s the final result – not too bad! The result with all the foreground noise removed. By using the smart eraser Cleanup.pictures removes the unwanted details and fills in the gaps based on the unaltered parts of the image. The result you can see above gives a clutter-free image that will give us a much better chance of success with a reverse image search. Here are the reverse image search results with the foreground clutter removed: Search results without the foreground noise. Much better! With the window frame removed, we get much better matches for the building in the background. We learn that it is the National Library of Latvia in Riga . By examining the area in Google Maps , we can see that there is only one building that Tilman’s photo could have been taken from: the Wellton Riverside Spa Hotel . The other buildings opposite the National Library do not have glass fronted balconies like the location in the original picture. The Wellton Riverside Spa Hotel in Riga. By way of confirmation, a quick look at the conference facilities on the hotel website brings up a room that matches the one in Tilman’s picture. The National Library is even visible out of the windows. The conference room at the Wellton Riverside Spa. So we know the location – how do we find out about the conference? Finding The Event Tilman posted this challenge on Wednesday 26th October and the photo was posted on the same day, so it’s reasonable to assume that the event happened in the few days leading up to the 26th. This means a good starting point is to found out what events were held at the Wellton Riverside Spa that week. It’s a simple piece of information but it’s surprisingly tricky to find out. The hotel website doesn’t list upcoming private events and search engines aren’t really too helpful. Eventbrite has a great search feature that allows you to search for events by location, but unfortunately it only works for current and future events, not past ones. It’s much easier to start with an event and find the location, but it seems more difficult the other way around. So what techniques might help us make the link between an event and a location? Geotagged social media posts are often helpful to tackle this problem. Both Facebook and Instagram have geographic search filters, so they are a good place to start. Instagram is my preferred resource for this because even though its search features are quite limited, it is still really good for searching photos by location. Simply entering “Wellton Riverside Spa” into the search bar brings up a few locations and hashtags of interest. All the matching hashtags and location tags for the Wellton Riverside Spa. One of the geotagged images leads to this image that was posted on 25th October. It refers to the hashtag #MILSummit2022 – so we will need to find out exactly what this summit was. The image is geotagged at the hotel location. A second image reveals some of the themes of the event. The same user posted another photo seemingly taken at the same event. Whatever the MIL summit is, the themes of media literacy, disinformation and verification are very common. We know Tilman works in this field, so this is probably a good indicator we are on the right track. We also learn from the second image that the full name of the conference is the “Baltic MIL summit”. This post links the MIL event at the hotel to the Ziniu Economic Forum, By researching the “Baltic MIL Summit” we quickly find that on Monday 24th October the Žinių Ekonomikos Forumas was hosting the MIL Summit at the hotel. The Facebook page for the event contains hundreds of photos of the participants taking part in the conference. Not only do these photos help to confirm the location matches the one in the original photo, but eventually we even find the exact same photo that Tilman used for the quiz. Bingo! A familiar photo on the ZEF Facebook page. So we now know that the image was posted by the Ziniu Economic Forum on their own Facebook page, and that the event at the hotel was the Baltic MIL media literacy summit held at the Wellton Riverside in Riga. To finish the quiz we just need to find out whether Tilman took part (if indeed he did). Linking Tilman To The Conference Clicking through all 230+ of the event photos was useful because not only did it help to identify the source of the original image, but despite all the attendees being very heavily photographed there was not a single photo with Tilman in it. (If you didn’t know what Tilman looked like already, a little Googling will bring up this bio with a picture.) Tilman’s picture and bio details. So there are two possibilities: either Tilman was there and he is very, very camera shy, or he was not there in person at all. On the balance of probabilties, it seems more likely that he did not physically attend the event, but we need to try and verify this first. Are there any other sources of information that might help? Looking through the images, it’s clear that there are strong links between the Deutsche Welle Akademie (where Tilman works) and the MIL event in Riga. We need to try and explore this connection a little bit more. A good place to start might be with the conference organisers, Ziniu Economic Forum. Most conferences have at least some publicity and a schedule of events. If we can find these, we might be able to learn a little bit more about the links between Deutsche Welle and the MIL Summit. The first article on the ZEF website refers to the summit and also includes a schedule for the event ( PDF download ). There are a lot of speakers – including several from DW Akademie – but Tilman is not one of them. Day Two of the summit, but no Tilman… So we know some of Tilman’s colleagues were speaking at the event, and even though we have not found any evidence that he attended in person, the schedule indicates that some of the sessions were streamed over the internet – so perhaps he took part by watching online? Perhaps he did, but it is hard to verify this directly. Can we do any better than just saying Tilman is linked to the conference because his colleagues were speaking there? We have already made a one-way link from the ZEF to the DW Akademie via the conference photos and speaker schedule, but what if we approach from the other direction and see what DW Akademie have to say in their own event publicity? By starting at the DW Akademie website we can see that they have two social media news feeds, one for Twitter and one for Facebook . By focusing on the dates of 24-25th October we can see that a live feed of the conference was available (so perhaps this was how Tilman took part?), but the other main publicity feature from DW is a talk by Lena Ritsche on their new game “Go Verify”. Here it is on Facebook: Facebook mention of Go Verify. And here on Twitter… Twitter reference to Go Verify. The Twitter post contains a direct link to the Go Verify game that is the main focus of Deutsche Welle’s publicity around the Baltic MIL Summit. By following the link and reading about Go Verify we find a familiar name at the bottom of the article: And there we have the closest link between Tilman and the conference so far. It seems unlikely that he was present, and we can’t say for sure whether he watched online or not – but we can say that the Go Verify game that he helped to develop was the subject of one of the talks. If you want to learn more about how to use Cleanup.pictures you can wach Technisette and I demonstrate it on David Bombal’s webcast here . Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 5 thoughts on “Quiztime: How To Clean Pictures For Better Search Results” Pingback: Quiztime: How To Clean Pictures For Better Search Results – We are OSINTCurio.us Robert Jan Bolk 15th January 2023 at 10:42 pm LS Het hotel waar hierover gesproken wordt, wat tegenover de bibliotheek zou moeten staan, staat er niet. Gelukkig is het maar een spelletje, groet.. Loading... Nixintel 16th January 2023 at 11:39 am The hotel is directly opposite the library on the other side of the Daugava River? Loading... Sarmad Nadeem 7th February 2023 at 9:54 pm I use Imgcleaner.com to remove unwanted objects from the image. Its good. Loading... PicPicAi 29th June 2025 at 2:08 pm Great OSINT quiz on cleaning pictures! Using PicPicAi image editing tools can enhance photo clarity, making search results more accurate. A fun, practical guide for better visual investigations! Loading... Comments are closed.","image_urls":["https://nixintel.info/wp-content/uploads/2022/11/Screenshot-2022-11-01-205952.png","https://nixintel.info/wp-content/uploads/2022/11/image-1.png","https://nixintel.info/wp-content/uploads/2022/11/image-10.png","https://nixintel.info/wp-content/uploads/2022/11/image-11-2048x1196.png","https://nixintel.info/wp-content/uploads/2022/11/image-12.png","https://nixintel.info/wp-content/uploads/2022/11/image-13-2048x1249.png","https://nixintel.info/wp-content/uploads/2022/11/image-14.png","https://nixintel.info/wp-content/uploads/2022/11/image-15.png","https://nixintel.info/wp-content/uploads/2022/11/image-17.png","https://nixintel.info/wp-content/uploads/2022/11/image-18.png","https://nixintel.info/wp-content/uploads/2022/11/image-2.png","https://nixintel.info/wp-content/uploads/2022/11/image-3.png","https://nixintel.info/wp-content/uploads/2022/11/image-4.png","https://nixintel.info/wp-content/uploads/2022/11/image-5.png","https://nixintel.info/wp-content/uploads/2022/11/image-6.png","https://nixintel.info/wp-content/uploads/2022/11/image-7.png","https://nixintel.info/wp-content/uploads/2022/11/image-8.png","https://nixintel.info/wp-content/uploads/2022/11/image-9.png","https://nixintel.info/wp-content/uploads/2022/11/image.png","https://secure.gravatar.com/avatar/1ab89dbac7ea73f1de9b6bfd4b8cecc178b09b036185ef5e664b357508e477b6?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/1f375d63a86b79935db749923d68c3f9ac3173321ac835939223d04e1edb0afe?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/277607c0d8e8d0c09232c77c96a154501cfe6465404a1e87eb60b2e885a68eb7?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/a8dbec59c215a7304ee0e9f72018ce377e1a7869da6ef4dc675dc1de3278de1e?s=50&d=mm&r=g"],"local_images":["blog_data/images/blog_ffdea357f0f4_0.bin","blog_data/images/blog_ffdea357f0f4_1.bin","blog_data/images/blog_ffdea357f0f4_2.bin","blog_data/images/blog_ffdea357f0f4_3.bin","blog_data/images/blog_ffdea357f0f4_4.bin","blog_data/images/blog_ffdea357f0f4_5.bin","blog_data/images/blog_ffdea357f0f4_6.bin","blog_data/images/blog_ffdea357f0f4_7.bin","blog_data/images/blog_ffdea357f0f4_8.bin","blog_data/images/blog_ffdea357f0f4_9.bin","blog_data/images/blog_ffdea357f0f4_10.bin","blog_data/images/blog_ffdea357f0f4_11.bin","blog_data/images/blog_ffdea357f0f4_12.bin","blog_data/images/blog_ffdea357f0f4_13.bin","blog_data/images/blog_ffdea357f0f4_14.bin","blog_data/images/blog_ffdea357f0f4_15.bin","blog_data/images/blog_ffdea357f0f4_16.bin","blog_data/images/blog_ffdea357f0f4_17.bin","blog_data/images/blog_ffdea357f0f4_18.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/osint/telegram-for-cyber-investigators/","title":"Telegram For Cyber Investigators","status":"ok","retrieved_at":"2026-08-29T16:33:47.871816+08:00","text":"Home OSINT Telegram For Cyber Investigators Telegram For Cyber Investigators 2 Comments / OSINT / By Nixintel Telegram is one of the most important platforms for OSINT investigators. I joined the Needlestack podcast to discuss how Telegram works and shared some practical OSINT advice along the way. Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 2 thoughts on “Telegram For Cyber Investigators” Pingback: Telegram For Cyber Investigators - Whalers Blog Pingback: Telegram For Cyber Investigators - Whalers Blog Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":[],"local_images":[]}
+{"source":"nixintel","url":"https://nixintel.info/osint/using-gap-analysis-to-keep-osint-investigations-on-track/","title":"Using Gap Analysis To Keep OSINT Investigations On Track","status":"ok","retrieved_at":"2026-08-29T16:34:54.432749+08:00","text":"Home OSINT Using Gap Analysis To Keep OSINT Investigations On Track Using Gap Analysis To Keep OSINT Investigations On Track 6 Comments / OSINT / By Nixintel With any kind of OSINT investigation it’s easy to gather huge amounts of data in a very short amount of time, but what do you do with it all? There are thousands of tools you can use to scrape information from all kinds of sources, but how do you decide to prioritise it? What information is relevant, and what is not? How do you keep your research on track and avoid wasting time on pointless searches that take you nowhere? This guy used gap analysis, I guarantee it. Consider the Mueller Investigation into President Trump – it executed over 500 search warrants, issued over 2,800 subpoenas, made 230 requests for telecoms data, and interviewed about 500 witnesses, all to produce a 448 page report. The Skripal Poisoning investigation took over 900 witness statements, seized 2300 pieces of evidence, and reviewed 4000 hours of CCTV footage. All of these investigations were very different in purpose but they all had to gather and evaluate vast quantities of information in order to achieve their aims, but how did they avoid becoming overwhelmed? Of course it helps that these enquiries are well resourced, but the important investigative decisions about where to go next are still made by just a tiny number of senior investigators. How do they keep things on track and avoid drowning in data? How do they decide what is important and what is irrelevant? What determines where they will go next? Gap analysis helps pull important information out of 4000 hours of CCTV footage… If you’re just starting out with OSINT investigation, or even if you have lots of experience, you’ll notice how easy it is to build up a lot of data and go off on a lot of tangents very easily. Most OSINT investigations are not on the same scale as the Mueller Report or the Skripal Poisonings of course, but the same investigative decision-making method used by experienced investigators in major cases can also be applied to smaller scale investigations to help sort through the data, focus on what’s important, and then decide what to do next. The method is known as gap analysis. Gap Analysis Gap Analysis is a simple but very effective way to keep an investigation focused on what is important and avoid unnecessary and confusing tangents. The name comes from the fact that it is used to evaluate all the known information and then identify gaps where further enquiries are needed. It is not specific to OSINT, but it can be easily applied to online investigations. It uses four simple questions to look at the gathered information, evaluate it, and then decided what to focus on next. The four questions are: 1) What do I know? 2) What does this mean? 3) So what do I need to know? 4) How do I find out? Instead of rushing ahead and leaping from one tool to the next in hope of a quick win, gap analysis ensures that the approach is more methodical and accurate. With OSINT it is possible to be fast or accurate, but it is not often possible to do both! Even if you are completely stuck at the start of an OSINT task, or maybe just overwhelmed with information, applying these questions to the data in front of you will help determine where to start. Also notice that thinking about what tools or resources to use are only addressed at question four – “How Do I Find Out?” While a knowledge of the available OSINT tools is essential, they will never get you very far if they are not used in conjunction with a good investigative method. The method will determine what tools to use. A Quiztime Case Study – Using Gap Analysis To Find Tilman Wagner On 22nd May the Quiztime challenge was quite a hard one to begin with – but it was possible to solve by using gap analysis to identify what information was available, and what had to be done next in order to solve the challenge.   Gap analysis helps us to move quickly from this…   . ..to this. Tilman posted the image below and asked two questions: 1) Was there another flight between his and the Easyjet one? and 2 ) Where was the Easyjet plane flying to? Where is the Easyjet flight headed to? He also told us that the image was taken on 12th May 2019, and that this was his outbound flight. Tilman often posts from Tirana where he is based but he was clear this was an outbound flight and he was not heading to Tirana. The first thing to do was to identify Tilman’s location and work from there.   There was no way to solve this instantly, but being systematic and using gap analysis it was possible to identify some ways to find the location and start heading in the right direction. Here are the four key questions I used to get started: 1) What do I know? i) This is on the 12 th May 2019. ii) There is an Easyjet plane on the runway ahead of Tilman’s plane. iii) There is a sign in the picture that says “BB 25” 2) What does this mean? i) Tilman’s plane was also at an airport that Easyjet fly from. ii) The sign may tell us something about the location. 3) So what do I need to know? i) Which aiports do Easyjet fly from. ii) What does the BB25 sign next to the runway mean, if anything? 4) How do I find out? i) Get a list of locations that Easyjet fly from. ii) Find a guide that explains airport runway signage. So already gap analysis gave me something to work with. Finding out where Easyjet fly from is straightforward – their website and this Wiki page give all the destinations, but they fly from 136 different airports. I could have looked at every single aiport on Google Earth and compared it to the photo, but that would take a long time and I would quickly drown in information. He’s on this map somewhere. We have him cornered… The runway sign was more promising. A quick Google tells us that “BB 25” means that this sign denotes taxiway BB for runway 25 – this is a vital piece of information that will help solve the puzzle much more quickly. Runway Names and Numbers Every single runway has a number, or two specific numbers to be exact. A runway takes its number from a the compass heading it is directed towards. For example a runway that points due west (bearing 270 degrees) would be called runway 27. However planes sometimes use different ends of the runway to take off from depending on wind direction, so the runway is given a second number for when aircraft use the opposite end. Because runways are straight lines, the opposite end of a runway will have a compass heading that is 180 degrees opposite to the other end. So if one end of a runway points towards 270 degrees, the other must point 90 degrees. This means the runway name will be 090/270, or 09/27 for short. If you’re confused there’s a really simple guide here . All you need to known about airport taxiway signs. So now I knew the runway in the photo is runway 25. This means the Easyjet plane is heading 250 degrees for takeoff. With a little bit of geometry it was possible to find out a little more that will quickly help to locate Tilman. If one end of the runway is facing 250 degrees, the other end must be facing 70 degrees (because 250- 180 = 70), so the runway name we are looking for will be 07/25. 07/25 – Bingo! So perhaps now would be a good time to hit Google Earth and just check out all the Easyjet aiport locations that have a runway named 07/25? It would have been an option to do this, but it was possible to narrow the parameters even further with just a little more geometry. If the Easyjet plane is facing 250 degrees (roughly WSW), then Tilman must have been looking roughly northwest when he took the photo. No airport buildings of any kind are visible on the image, so the main airport infrastructure must be on the south side of the runway, not the north side. Now the parameters for finding the correct airport were really small: i) It is used by Easyjet ii) It has a runway 07/25 iii) The main terminal buildings are likely on the south side of the runway. A very quick trawl through the list of 136 Easyjet destinations reveals that only a tiny number (I think it was less than 15 but can’t quite recall) had a runway 07/25. I checked these out on Google Maps, and even fewer had the main airport buildings on the south side of the runway. One of the very few that met all three search criteria was Rome Leonardo Da Vinci Airport . I then moved to Google Earth to try and verify if this could be correct: A view down Runway 25 from Google Earth. Note the red/white tower and other buildings on the right that match those in Tilman’s photo.   Just to the left is the BB25 sign. It isn’t clear in this image, but it can be clarified with the airport plan published by Jeppesen. By comparing the original photo to the Google Earth image it was clear the red and white towers in the background were the same on both photos. Tilman had been waiting to take off from runway 25 at Rome Leonardo Da Vinci Aiport. Two planes waiting in the queue at the end of Runway 25. This last Google Earth image showed two planes waiting to take off at the end of the runway. This suggested that it was at least possible there was another plane between Tilman’s aircraft and the Easyjet one we were trying to find. So having established Tilman was in Rome, it was time to decide what to do next by applying some more gap analysis. 1) What do I know? i) The image was taken on 12th May. ii) The image was taken on runway 25 at Rome Leonardo da Vinci Aiport (FCO). 2) What does this mean? i) Tilman’s plane and the Easyjet flight will have departed close together on 12th May. To identify Tilman’s flight we will also need to identify the Easyjet flight. 3) What do I need to know? i) What time planes took off from FCO on 12th May. ii) Where do Easyjet fly to from Rome? 4) How do I find out? i) Get a list of departure times for FCO on 12th May 2019. ii) Find out where Easyjet fly to from FCO. Now you might assume that it would be possible just to head over to Flightradar and view historic departure information and solve the puzzle just like that, but it wasn’t. Tilman posted the challenge ten days after the flight, but Flightradar only holds records for the last seven days unless you have a premium account. There are other aircraft datasets available but most are intended for commercial use and cost a lot of money to access. So where to get the data I needed? To get the data I used Airportia and found the page with departure records for FCO here . Now there seemed to be a problem again because Airportia only allows you to see the last seven days worth of information, but with a little URL manipulation it was possible to access the data I needed. The standard URL format Aiportia uses is: https://www.airportia.com/italy/leonardo-da-vinci/departures/YYYYMMDD/0000/2359/ So by amending the URL to my target date as follows, it was possible to get the data for the date in question, even though there is no direct option to do this from the website: https://www.airportia.com/italy/leonardo-da-vinci/departures/20190512/0000/2359/   There was a lot of data to go through, especially as there is a big difference between planned departure times and actual departure times. Airportia doesn’t allow sorting of flights by actual departure time, so a little patience was required. I got slightly disheartened at this point because I counted a total of 21 different Easyjet departures to thirteen different destinations: Geneva, Nice, Paris, Gatwick, Lyon, Berlin TXL, Paris Orly, Amsterdam, Nantes, Basel, Toulouse, Bristol and Luton.It would be hard to find the exact flight without guessing. I guessed that perhaps Tilman would have flown to Dusseldorf, based purely on the fact that he goes to Germany a lot, so I looked for Easyjet flights near to Dusseldorf flights but I’m happy to say I was wrong. Logic beats guessing every time. So how to narrow down my the list of 21 possible flights to one? Time for more gap analysis: 1) What do I know? i) There were 21 Easyjet flights from Rome on the 12th May. ii) The flights go to 13 different locations. iii) The flight in the picture is one of those. iv) The flight pictured is in daylight. 2) What does this mean? i) The flight must have been before sunset, as it is still light and there are no runway lights visible. ii) Any flights that took place after sunset can be eliminated. 3) What do I need to know? i) What time was sunset on 12th May? 4) How do I find out? i) Use Suncalc! Suncalc told me that sunset had been at 20:20 on the 12th May. This meant that any flight after this time could not have been in daylight and so could be eliminated. It was possible to eliminate 7 Easyjet flights this way, leaving me with just 14 possibilities. More Information Needed I was running out of ways to identify the specific Easyjet flight. It was not possible to accurately read the tail number of the aircraft (that would have been too easy) and I needed more information. Tilman helpfully provided some :   Tilman said this image was taken shortly after takeoff after his aircraft turned left approximately 90 degrees. The runway geometry meant that he had taken off on a heading of 250 degrees so a left turn of approximately 90 degrees meant he was heading roughly south. A quick Google Maps search helped confirm the location in the photo:   Even if you hadn’t figured it out from the runway angle, Tilman’s second picture shows the town of Fiumicino. This also means he is heading south. With some new information, it was time to apply some more gap analysis. 1) What do I know? i) Tilman’s plane took off from Runway 25, turned left, and headed south. ii) An Easyjet flight took off ahead of him, destination unknown. 2) What does this mean? i) That the departure timetable will show a flight heading south near to the same time an Easyjet flight took off. ii) That where a flight to the south and an Easyjet flight occur together, this is probably the right answer. iii) That if there is a flight in between an Easyjet flight and a southbound flight, it will likely contain the answer to Tilman’s second question. 3) What do I need to know? i) Which flights on 12th May were going to a destination south of FCO? 4) How do I find out? i) Revisit the flight departure data. ii) Check the destinations on a map – which are to the south? So on reviewing the flight data, the only flights heading (roughly) due south out of FCO on 12th May were to Tunis, Palermo, and Catania: He’s down there somewhere. The only time when a flight to one of these destinations took off shortly after an Easyjet flight was at 17:36 when a plane went to Palermo, just after Easyjet flew to Nice at 17:32. The relevant part of the timetable. Note the big difference between planned departures and actual departures. It is the actual departure time that we need to know to solve this puzzle. This also means that there was another flight inbetween, to Pisa at 17:33. There is no other combination of Easyjet flight followed closely by a southern flight towards Palermo, so this had to be the correct answer. Fortunately Tilman confirmed that it was! Without a sound logical method like gap analysis it would not have been possible to solve this challenge, but it allowed me to make sense of the data available and also identify the next pieces of information needed to find the answer. The average terrorism or murder investigation is a lot more complicated of course, but the only real difference is in the amount of data that has to be analysed and evaluated, not the decision making process itself.   Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 6 thoughts on “Using Gap Analysis To Keep OSINT Investigations On Track” Mira 16th October 2019 at 6:32 pm Hi, First of all, let me thank you for your blog posts which are such an amazing tool to learn OSINT. I have a question about this one: Why did you discard the flights to Catania? There was one that departured at 13:28 and was preceded by an Easyjet flight to London Gatwick at 13:26. Another one departured at 15:12 and was preceded by an Easyjet flight to Paris-Orly at 15:10. Do you think the time between the two flights was too short? According to this website, 2 minutes is a minimum to avoid a wake turbulence hazard https://www.skybrary.aero/index.php/Mitigation_of_Wake_Turbulence_Hazard Loading... Reply Nixintel 16th October 2019 at 7:39 pm Hi Mira, thanks for taking the time to comment. The main reason I discounted the Catania flights at those times is because in the original picture it looked like it was getting too dark. Although it was still daytime when the picture was taken, the sky on the left of the image looks like the sun is already quite low, so I assumed it was getting close to evening time. I think that the sun is too low in the sky for 13:28 or 15:10 at that time of year. Re-reading the article I realise I was not explicit about this when I wrote so it is not very clear what my rationale was, but that was pretty much it! Loading... Reply Mira 18th October 2019 at 11:21 am Thank you for the explanation. I was also thinking at the beginning that the photo was probably taken in the evening (or early in the morning), but I forgot about it along the way. Loading... Reply Pingback: Dressed NOT for Success – We are OSINTCurio.us Pingback: Cyber Intelligence – jagadee.online Pingback: Geolocation: At The Retail Park - Whalers Blog Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2019/05/103301966_cctv_1_petrov_boshirov_met-.jpg","https://nixintel.info/wp-content/uploads/2019/05/AirportSigns.jpg","https://nixintel.info/wp-content/uploads/2019/05/Screenshot-2019-05-29-at-21.44.39-1024x926.png","https://nixintel.info/wp-content/uploads/2019/05/Screenshot-2019-05-29-at-21.53.34-985x1024.png","https://nixintel.info/wp-content/uploads/2019/05/Screenshot-2019-05-29-at-22.46.05-897x1024.png","https://nixintel.info/wp-content/uploads/2019/05/Screenshot-2019-05-29-at-22.58.52.png","https://nixintel.info/wp-content/uploads/2019/05/Screenshot-2019-05-29-at-23.04.44-1024x729.png","https://nixintel.info/wp-content/uploads/2019/05/Screenshot-2019-05-30-at-16.56.03.png","https://nixintel.info/wp-content/uploads/2019/05/Screenshot-2019-05-30-at-17.06.14-300x287.png","https://nixintel.info/wp-content/uploads/2019/05/Screenshot-2019-05-30-at-17.12.15-300x106.png","https://nixintel.info/wp-content/uploads/2019/05/alitalia.jpg","https://nixintel.info/wp-content/uploads/2019/05/easyject_image.jpg-large-1024x768.jpeg","https://nixintel.info/wp-content/uploads/2019/05/image2.jpg-large-1024x768.jpeg","https://nixintel.info/wp-content/uploads/2019/05/mueller.jpg","https://nixintel.info/wp-content/uploads/2019/05/panoramio-42434834-1024x768.jpg","https://secure.gravatar.com/avatar/65e9fe80f2064d59c07e759bd6ad06a81d72406abfe8550d37627452e2ca2516?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/a8dbec59c215a7304ee0e9f72018ce377e1a7869da6ef4dc675dc1de3278de1e?s=50&d=mm&r=g"],"local_images":["blog_data/images/blog_1a292eea0d47_0.jpg","blog_data/images/blog_1a292eea0d47_1.jpg","blog_data/images/blog_1a292eea0d47_2.bin","blog_data/images/blog_1a292eea0d47_3.bin","blog_data/images/blog_1a292eea0d47_4.bin","blog_data/images/blog_1a292eea0d47_5.bin","blog_data/images/blog_1a292eea0d47_6.bin","blog_data/images/blog_1a292eea0d47_7.bin","blog_data/images/blog_1a292eea0d47_8.bin","blog_data/images/blog_1a292eea0d47_9.bin","blog_data/images/blog_1a292eea0d47_10.jpg","blog_data/images/blog_1a292eea0d47_11.jpg","blog_data/images/blog_1a292eea0d47_12.jpg","blog_data/images/blog_1a292eea0d47_13.jpg","blog_data/images/blog_1a292eea0d47_14.jpg"]}
+{"source":"nixintel","url":"https://nixintel.info/osint/using-ssl-certificates-to-find-threat-actor-infrastructure/","title":"Using SSL Certificates To Find Threat Actor Infrastructure","status":"ok","retrieved_at":"2026-08-29T16:33:44.943794+08:00","text":"Home OSINT Using SSL Certificates To Find Threat Actor Infrastructure Using SSL Certificates To Find Threat Actor Infrastructure 1 Comment / OSINT / By Nixintel At last month’s SANS OSINT Summit I gave a talk the usefulness of SSL certificates for open source intelligence researchers. The talk looks at three recent examples of how information from certificate transparency logs can be used to discover, attribute, and unmask threat actor infrastructure. The video of the talk has now been published and you can watch it here. The tools and resources I refer to in the talk can all be found here . Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 1 thought on “Using SSL Certificates To Find Threat Actor Infrastructure” Pingback: Using SSL Certificates To Find Threat Actor Infrastructure - Whalers Blog Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":[],"local_images":[]}
+{"source":"nixintel","url":"https://nixintel.info/osint/website-osint-whats-the-link-between-antifa-com-and-russia/","title":"Website OSINT: What’s The Link Between Antifa.com and Russia?","status":"ok","retrieved_at":"2026-08-29T16:34:34.490881+08:00","text":"Home OSINT Website OSINT: What’s The Link Between Antifa.com and Russia? Website OSINT: What’s The Link Between Antifa.com and Russia? 7 Comments / OSINT / By Nixintel The term “OSINT” sometimes gets thrown around a little too loosely. The “open source” part of OSINT is straightfoward enough: there’s a world of information out there and with enough digging and practice you can find almost anything you could ever think of – but by itself this is not OSINT. The “intelligence” part of OSINT is often neglected, sometimes with quite serious consequences . Getting your hands on the data you want is usually easy enough, but this raw information has to be analysed and turned into a coherent narrative, a process that is often fraught with difficulty and uncertainty. A lot of uncertainty can be removed if there is a clear plan in place at the start. We have to remember that OSINT is never done simply for its own benefit. It is always part of a wider objective like a journalistic investigation, or a missing person case, or a military operation, and so on. The nature of the objective that you’re doing OSINT for will ultimately determine the scope and shape of the research that you undertake, and the findings that you provide to your client or boss. Collecting raw information from the internet is easy enough, but turning it into an organised, verified, and useful report takes a little more work. The Intelligence Cycle The Reddit crowdsourced investigation version of this model only features ‘Collect’ and ‘Disseminate’… To ensure consistency and thoroughness in OSINT work most organisations adopt a version of the Intelligence Cycle like the one pictured above. There are several variations of this model, but they are all very similar. They all assume an initial plan or goal, followed by a collection phase, some processing and analysis, and finally dissemination of the information to the intended recipient. The processing and analysis phase is the most important one because this is where the raw collected data is critically evaluated, theories are tested, and correct information is separated from the false or ambiguous (with varying degrees of success). This means that “here’s a bunch of stuff I found on the internet” is not OSINT. It might be open source, but it isn’t useful intelligence until it’s been tested, verified, and analysed. Does the information you found provide useful answers to the question you set at the start? Have you verified it? How have you dealt with the conflicting information you collected? How much weight have you given to sources of information that are of uncertain reliability? Have you provided you client with OSINT or BULLSHINT? And so on. Is Antifa.com Controlled By Russians? So what has all this got to do with Antifa? I actively try to avoid politics on Twitter, but sometimes it’s inescapable despite my best efforts. Recently my interest was piqued by a claim that the domain antifa.com was redirecting visitors to Joe Biden’s presidential campaign site, and that furthermore, the Antifa website was registered by shady Russians. Was this the spectre of electoral interference about to make a reappearance? Yeah…but no. The central claim about a Russian link seemed to revolve around the WHOIS history of the Antifa.com domain – I’m always initially sceptical about claims made solely on the basis of WHOIS since it’s such an ambiguous source of information, but I decided to dig into the domain history a little more to see what it was possible to find out. What follows is a brief step-by-step guide to using the Intelligence Cycle to plan a little OSINT research and analysis to see what we can find out. Planning – What Do I Actually Want To Find Out? This is quite a simple query. I could ask “ Was the redirect from Antifa.com to Joe Biden’s website a Russian plot? ” It’s a sensationalist question, but it’s also a closed question (you could only answer “yes” or “no”). It’s almost a leading question too, in that your political stance might cause you to come to a conclusion based simply on how the the question is asked, and not necessarily based on any of the research. Closed and leading questions are not good investigative questions. Open questions are much better and less likely to feed our biases. A better question to ask might be “ What is the nature of the relationship between Antifa.com and it’s Russian registrar, if any? ” Collection – Find The Materal That I Need The collection part of the intelligence cycle is where we can gather all the information that we need to try and answer the question we set at the start. In this case I want to know about the history of the antifa.com domain, who owned it, what content it has displayed over time, and what we can find out about any redirects that are in place. To do this I’m going to collect information about the server (so I can catch any redirect information that might be present), the WHOIS history, the certificate history, and any preserved content from the Wayback Machine that might show me what content the site has displayed over time. 1. Server Information Curl is still my favourite tool for quickly grabbing information about a server. To grab information about the Antifa.com server, I entered the following command: $ curl -I http://antifa.com The -I flag ensures that I get server header information back. In this case I get the following result: HTTP/1.1 302 Found Server: nginx Date: xxx Connection: keep-alive Location: https://itsgoingdown.org/ X-Served-By: Namecheap URL Forward This is interesting because there’s still a 302 redirect in place, but now it points to a different URL. We can also see that Namecheap’s URL Forwarding service is in place, so I’ll grab some information about how that works to add to my analysis later: 2. WHOIS History I also want to know as much as I can about the WHOIS history. After all, this is the source of the suspicion that there might be some Russian links to the site. There are several tools to do this. RiskIQ and Whoisology both have WHOIS data going back to 2012/2013. However we know that the domain was registered at least as far back as 2002 (and as it turns out, even before that) so we need to go further back if possible. It’s possible to pay for a service like this with Domain Tools , but a full historic WHOIS report is a bit too pricey for a single blog post. Fortunately there is a little hack that takes advantage of the fact that WHOIS records are themselves often archived by the Wayback Machine, so we can use this technique to find WHOIS records that go back as far as 2009 : It’s not ideal but that’s as far back as we can go without splashing the cash on a paid-for WHOIS record. The information held by RiskIQ helpfully lists more recent registration renewal or change dates: 3. Certificate History A domain’s certificate history can offer several insights into its structure and setup, including ownership and hosting changes. Crt.sh offers a nice clear overview of a site’s certificate history, and there’s always Censys if you need to go into more depth. Here’s the very short certificate history for Antifa.com: 4. Wayback Machine Fortunately the subject domain has been archived many times over the years. The oldest capture is as far back as January 1999 and the most recent was 17th August 2020. It’s no coincidence that so many snapshots have been made since the domain begain to be heavily publicised in the last week: With this information we’ll be able to look at the historical content of the website to see what it was displaying at different time periods. Processing & Analysis Because this is just a short example for a blog post, I’m not going to spend much time doing any processing of the information I’ve collected. Ordinarily it’s usually helpful to turn raw data into spreadsheets, graphs, and relational diagrams to make analysis easier, especially with more complex tasks. Instead I’m going to move straight on to analysing the raw information that I collected. My aim is going to be to try and construct a timeline from the WHOIS, Certificate, and Wayback Machine history to try and see how the domain has changed over time and what that might mean for the original question about the domain and the relationship with its Russian registrar. Before doing that I want to look at the server header I grabbed at the start: HTTP/1.1 302 Found Server: nginx Date: xxx Connection: keep-alive Location: https://itsgoingdown.org/ X-Served-By: Namecheap URL Forward The HTTP 302 code tells us that all requests to visit antifa.com are all now directed to another site, itsgoingdown.org. This site does in fact appear to be a left wing political website, which is what we might expect. This redirect is enabled through Namecheap’s URL forwarding service, so by looking up Namecheap’s documentation about how this process works , we can infer that the person(s) managing the Antifa.com domain does so via Namecheap’s control panel and that the domain is therefore managed through Namecheap. This shouldn’t be surprising because this is exactly what the current WHOIS records tell us: Domain name: antifa.com Registry Domain ID: 85915752_DOMAIN_COM-VRSN Registrar WHOIS Server: whois.namecheap.com Registrar URL: http://www.namecheap.com Updated Date: 2019-10-23T14:38:04.00Z Creation Date: 2002-04-24T12:35:11.00Z Registrar Registration Expiration Date: 2021-04-24T12:35:10.00Z Registrar: NAMECHEAP INC Registrar IANA ID: 1068 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.6613102107 Reseller: NAMECHEAP INC Ever since 23rd October 2019, the subject domain has been registered with Namecheap. So where’s the Russian registrar link that we were interested in? If we go back through the historic WHOIS data we can see that between 2009 (the oldest WHOIS data we can access) and the switch to Namecheap on 23rd October 2019, the domain was registered to an address in St Petersburg, Russia: Registrar Abuse Contact Phone: +7.8129140281 Domain Status: clientUpdateProhibited Domain Status: clientTransferProhibited Domain Status: clientDeleteProhibited Registry Registrant ID: Registrant Name: Whois privacy services provided by DomainProtect LLC Registrant Organization: Whois privacy services, provided by DomainProtect LLC Registrant Street: c/o Office-Mail processing center Sadovaya, 53 Registrant City: Saint Petersburg Registrant State/Province: Saint Petersburg Registrant Postal Code: 190068 Registrant Country: RU Registrant Phone: +1.8662452838 Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant Email: [email protected] I think this was the point at which Yahoo! News and several others decided to end their research and go straight to publishing. This was a little premature though: Hmm. That’s a very broad definition of the word “linked”. This is what happens when rushing from Collection to Dissemination and skipping over the Analysis part of the Intelligence Cycle. Russia is a country – what’s the link to the registrant? When did they control the domain? Can we know what they did with it? Do they still own it? All these questions need to be resolved before we draw a conclusion. Better to be slow and right than fast and wrong. So what exactly is the link to Russia in the WHOIS data? The registrant name and e-mail are hidden in the WHOIS records, but the street address is not. By searching for the address “ c/o Office-Mail processing center Sadovaya, 53 ” we can see that it’s linked to hundreds and hundreds of other WHOIS records for other domains. Why might this be? Fortunately the Wayback Machine records we saved during the collection phase will help. We can see what Antifa.com looked like during the time it was registered by a mysterious Russian organisation. Brace yourselves for the big reveal… For the entire time that the domain was owned by the shadowy Russian group, all they did was offer it up for sale . Although we don’t have WHOIS records older than 2009, we can see that even in 2008 the domain was parked and up for sale. In fact it was for sale for many years up until it switched to a new owner on 23rd October 2019. Even after the change of ownership, no significant content changes were made until 14th April 2020. We can see this in the certificate history from crt.sh . The antifa.com domain never had an SSL certificate before 14th April 2020. This date is significant because it’s also the same date that the Antifa Website Twitter account was created : (Of note the URL in the Antifa Website Twitter bio also redirects to itsgoingdown.org. ) The Antifa.com YouTube channel was also created at around this time, on 18th April 2020: Sure enough, the first Wayback Machine capture after 14th April 2020 reflects this change. The “For Sale” sign is gone and has been replaced with new content: The #JusticeForGeorgeFloyd hashtag links directly to the Antifa Website Twitter. Remember that at this point the previous Russian registrar has not been linked to the site for over eight months. This was still the case on 12th August when the domain was set up to redirect to Joe Biden’s website: Can we be confident of a link between Russia, Antifa, and Biden based on what we’ve found in our limited research? I’m not sure we can. Product Dissemination Because this is just a short blog exercise, there’s no one to disseminate the information to beyond you, the reader (well done if you’re still reading this far on). It’s a good point at which to review our original question and see if the collection and analysis we’ve done actually answers the original question – what is the nature of the relationship between Antifa.com and its Russian registrar, if any ? This has been quite a brief exercise and there are certainly an awful lot of other avenues of research we could have gone down. So what can we conclude? The world of OSINT is rarely black and white and there will always be some areas of uncertainty. There’s nothing wrong with a little uncertainty, provided that this is reflected in your findings: your conclusions always have to be supported by your research and not embellished. Nah. Based on this research we can say that the domain was previously registered by a Russian-based organisation and has been since at least 2009, possibly even before that. We can also say that during the Russian registrant’s period of ownership the evidence suggests that the domain was only parked and offered for resale. There is no evidence to suggest any content was hosted on the domain during their ownership period, or that any redirects were in place. The registration of the domain changed in October 2019 and there is no clear connection to the Russian registrant after that point. The current owner of the domain uses Namecheap as a registrar but from the information collected it is not possible to say who they are. The current owner has used the domain for a distinctly different purpose than the previous Russia-linked owner. At the time the domain was configured to redirect traffic to Joe Biden’s website almost 11 months had passed since the last clear association to any Russian entities. The evidence collected tends not to support the suggestion that the diversion of traffic from Antifa.com to Joe Biden’s website was linked to the previous Russian registrant. So if you’d cut the corner in the intelligence cycle and gone straight from Collection to Dissemination you could easily have missed the important details and made the sensational – but unsupported – assumption that the diversion of traffic from Antifa.com to Joe Biden’s campaign site was a Russian scheme. It’s certainly tempting to take shortcuts and draw exciting conclusions, but this rarely makes for accurate reporting. Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 7 thoughts on “Website OSINT: What’s The Link Between Antifa.com and Russia?” Ray Dulac 20th August 2020 at 4:16 pm While this post feels like BullshINT, going from collection to dissemination, I wanted to help fill a couple of the collection gaps, since I have access to a paid Domain tools account. I reviewed the historical companies through a paid account. The goal of posting was to share more collection information. I don’t think it will change the analysis, just trying to help. When looking at the whois history section from 2002 to 2008, the whois record had the Organization listed as Eruobox in St. Petersburg. The record changed to the c/o Office-mail information on 2008-08-15. When reviewing the screenshot history, it shows that in 2009 the site was used for pharma sales on a web page called “Indian Drugs.” The screenshots are tagged 2009-07-31 and 2009-10-04. On 2009-12-14 it is back to the for sale style pages. The whois records from that time still show the c\\o Office-Mail. Loading... Reply Nixintel 23rd August 2020 at 1:06 pm Thanks for the extra info Ray. There’s really no subsitute for Domain Tools when it comes to historic WHOIS records! Loading... Reply Zhouhan 21st August 2020 at 2:21 am Thanks for sharing your insights! Loading... Reply Kadidia Doumbia 24th October 2020 at 10:53 pm A wealth of information. It will time to digest all. Thank you. Loading... Reply princeofsaiyanz 23rd June 2022 at 9:09 pm This was a very good read, I followed the process and it opened my eyes Loading... Reply Dan Dows 8th January 2024 at 1:44 pm You were correct in the calling post bs. They fabricated the Russia link. It doesn’t connect to Russia anywhere in any of domain research sites. So they not only responded to a fact with misinformation /lies. They did what all media now feels way to comfortable doing. They lied. The site is linked to Kalkofnsvegur 2, Reykjavik, Capital Region, 101, IS Loading... Reply Pingback: Evaluating contradictory foreign interference allegations in the 2020 U.S. election - DFRLab Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-17-at-20.33.37.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-17-at-20.38.38-2048x1840.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-17-at-21.20.10.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-17-at-22.17.18.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-13.43.22.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-14.13.52-2048x447.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-14.24.28.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-18.43.03-2048x250.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-18.59.24-2048x923.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-19.05.32-2048x575.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-19.52.02.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-19.55.57-2048x543.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-19.58.21.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-20.17.48.png","https://nixintel.info/wp-content/uploads/2020/08/Screenshot-2020-08-18-at-23.07.35.png","https://secure.gravatar.com/avatar/0302222195676697c7c4053e24a16d62e9880f24790ef61b1f1563d1eda37d5f?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/8e2022a012f6263d3a43b47ab52db129c03e7292d0bcb43fc57e19d84b6edd1f?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/a119af20a90be6372a467f0b49536b06a4c322d97c4cd6b2089f96e5935ccee7?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/a8dbec59c215a7304ee0e9f72018ce377e1a7869da6ef4dc675dc1de3278de1e?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/c20812e8c98a36cdf6d83498da81115a2fecba7bebbd71cf9a25b3f0996c4b4e?s=50&d=mm&r=g","https://secure.gravatar.com/avatar/e379292b260973aa638e47e9d7150d2112dc65b62ade97b354143aaf9040607b?s=50&d=mm&r=g"],"local_images":["blog_data/images/blog_96509521c651_0.bin","blog_data/images/blog_96509521c651_1.bin","blog_data/images/blog_96509521c651_2.bin","blog_data/images/blog_96509521c651_3.bin","blog_data/images/blog_96509521c651_4.bin","blog_data/images/blog_96509521c651_5.bin","blog_data/images/blog_96509521c651_6.bin","blog_data/images/blog_96509521c651_7.bin","blog_data/images/blog_96509521c651_8.bin","blog_data/images/blog_96509521c651_9.bin","blog_data/images/blog_96509521c651_10.bin","blog_data/images/blog_96509521c651_11.bin","blog_data/images/blog_96509521c651_12.bin","blog_data/images/blog_96509521c651_13.bin","blog_data/images/blog_96509521c651_14.bin"]}
+{"source":"nixintel","url":"https://nixintel.info/schedule/","title":"Schedule","status":"ok","retrieved_at":"2026-08-29T16:30:19.34645+08:00","text":"Home Schedule Schedule I teach SANS SEC497 Practical Open Source Intelligence and SANS SEC587 Advance Open Source Intelligence . Date Location Event Link 28 Sep – 3 Oct 2026 Bethesda, MD SANS DC Metro – SEC497 More Info 16-21 Nov 2026 Paris SANS Paris – SEC587 More Info 1-6 March 2027 London SANS London – SEC497 More Info Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email","image_urls":[],"local_images":[]}
+{"source":"nixintel","url":"https://nixintel.info/security/verify-your-online-identities-with-keybase/","title":"Verify Your Online Identities With Keybase","status":"ok","retrieved_at":"2026-08-29T16:34:22.534033+08:00","text":"Home Security Verify Your Online Identities With Keybase Verify Your Online Identities With Keybase 1 Comment / Security / By Nixintel Twitter’s recent decision to remove blue check marks from accounts it has previously verified causes a number of issues for the platform and its users. One of the most obvious ones is around authentic identity. Without verification, how do I know that a particular account really does belong to the person or organisation who claims to own it? Blue ticks made this a little clearer but without them it is much easier for fake and impersonation accounts to flourish. So how can Twitter account users verify their identities and proved that their accounts are authentically theirs? The inability to prove identity and authenticity without a blue tick makes it hard to deal with fakes. Fortunately help is at hand. The need to prove the authenticity of one’s identity is not a new problem in the world of information security and solutions exist to help prove that the users and services really are who they claim to be. By using cryptography it is possible to verify our identities beyond all doubt, and so if we can link cryptographic proofs to the websites and social media accounts that we own then we can prove irrefutably that they are ours. Introducing Keybase Cryptography is complicated but you don’t need advanced technical skills to take advantage of its benefits. Keybase is a web-based service that makes it easy to incorporate cryptographic keys into online identities with proofs . Keybase uses public key cryptography to provide services like end-to-end encrypted chat and file sharing but it also offers the ability for users to cryptographically verify that they own a particular social media account or website. After creating a Keybase account and then setting up and installing Keybase on your device (ideally on more than one device) Keybase allows you to claim and prove ownership of social media accounts and websites that you own. Keybase does this by providing cryptographic proofs that users can add to the Twitter accounts and websites that they own, thereby proving that the same person who owns a Twitter account also owns a particular website. Use Case: Twitter Account Verification Supposing your a Twitter user who has just lost your blue tick and you’re worried about people making fake profiles to impersonate you and your company. You could negate this problem by using Keybase to cryptographically prove that your Twitter account is also definitively linked to your website and/or other social media accounts, thereby removing any doubt that you are who you say you are. Here’s what this looks like in practice. After installing Keybase and setting up my account, my public profile shows that I have verified ownership of both my Twitter account and this website. Here’s the cryptographic proof for my Twitter account. This is Tweet is automatically generated by Keybase for me to paste into Twitter. Keybase then scans my profile to check for an exact match for the long random string of letters and numbers. If it finds the matching string, it will be able to verify that the account is linked to my Keybase profile. If it can’t, it won’t. Verification tweet that is used by Keybase to prove identity. By clicking on the link in my verification Tweet you can go to my Keybase profile where Keybase will confirm that my Twitter account does genuinely belong to me. Clicking on the verification link directs back to my Keybase profile, which confirms the authenticity of my account ownership. Notice that in my Keybase profile I have also verified that I control the domain nixintel.info. I did this by adding a cryptographically signed file generated by Keybase and uploading it to my server where it can be publicly viewed and verified. So you can see how you can use this technique to prove that your Twitter account is also associated to your website. If you have multiple Keybase users that belong to the same organisation, such as a particular news website, it is also possible to add multiple signatures to the website verification file . So if you are a news organisation whose journalists have just lost their blue checks and are worried about impersonators, one solution would be for each journalist to create Keybase profiles that verify their Twitter accounts and then also add their signatures to the Keybase verification file on the organisation’s website. That way they will be able to prove irrefutably that they own their Twitter account and that they really do work for the organisation where their signature file is stored. You can see how Keybase have implented this on their own site here . Adding the Keybase signature to a website proves ownership. But what’s to stop any random impersonator copying my verification Tweet or website file and trying to clone my profile? It might seem like an obvious way to work around the verification but it’s doomed to failure. Why so? Since Keybase derives the Twitter profile and website file proofs from cryptographic keys that are stored only on my devices, anyone who just copied the public proofs and pasted them into a fake site or profile would fail the Keybase verification process because they don’t have the necessary matching private keys. They would never be able to display the proof of ownership in their Keybase profile in a way that a genuine account holder would. Visibility Keybase verification is not a direct replacement for all of the features and visibility of a Twitter blue check, but it does prove with cryptographic certainty that users own the accounts and websites that they claim to. It’s also an extremely powerful way to expose fakes and discredit impersonators since they cannot produce the cryptographic proof that genuine accounts can. The only other thing to consider is how do you let your followers know how to verify you with Keybase? Twitter profile with a link to the verifying Keybase profile in the bio. Once you’ve added your proof tweet, you can make it your pinned Tweet. It isn’t essential that you pin it, but the tweet needs to stay in your feed so it can be verified by others. Another technique is simply to add a link to your Keybase profile in your Twitter bio or a link directly to your verification tweet. It’s not as visible as a blue check mark, but it is certainly a reliable way of proving your account ownership and authenticity. You also don’t need to pay $8 a month for basic cryptography. For a previous article on the OSINT opportunities that Keybase presents. Click here . Share this: Tweet Share on Telegram (Opens in new window) Telegram Share on WhatsApp (Opens in new window) WhatsApp Share on Mastodon (Opens in new window) Mastodon Email a link to a friend (Opens in new window) Email Related ← Previous Post Next Post → 1 thought on “Verify Your Online Identities With Keybase” Pingback: از آناتومی اتومیشن تا قدرت AI در امنیت سایبری | SecWithMoh Leave a Reply Cancel reply This site uses Akismet to reduce spam. Learn how your comment data is processed.","image_urls":["https://nixintel.info/wp-content/uploads/2023/04/kb_profile_proof.png","https://nixintel.info/wp-content/uploads/2023/04/kb_proof1.png","https://nixintel.info/wp-content/uploads/2023/04/nyc.png","https://nixintel.info/wp-content/uploads/2023/04/twitter_profile.png","https://nixintel.info/wp-content/uploads/2023/04/website_key.png"],"local_images":["blog_data/images/blog_2b8c7172515b_0.bin","blog_data/images/blog_2b8c7172515b_1.bin","blog_data/images/blog_2b8c7172515b_2.bin","blog_data/images/blog_2b8c7172515b_3.bin","blog_data/images/blog_2b8c7172515b_4.bin"]}
diff --git a/blog_data/by_source/sector035.jsonl b/blog_data/by_source/sector035.jsonl
new file mode 100644
index 0000000000000000000000000000000000000000..d2deb4cc8b7e4ed6bd1e6ab235319e9972fb6000
--- /dev/null
+++ b/blog_data/by_source/sector035.jsonl
@@ -0,0 +1,37 @@
+{"source":"sector035","url":"https://sector035.nl/articles/2021-46","title":"","status":"ok","retrieved_at":"2026-08-29T16:28:57.652882+08:00","text":"Week in OSINT #2021-46 | Sector035 Week in OSINT #2021-46 Home Week in OSINT Articles Search Week in OSINT #2021-46 22nd Nov 2021 instagram geolocation google search engine deep fake quiztime facebook conference It was an awesome and productive week for me, followed by a weekend with GOSINTcon, a German conference. What will this week bring? So much good stuff being shared over the last week, followed by conINT, that I sadly had to miss, and on Sunday a German OSINT Conference. What else could one wish! Awesome couple of days, and now back to work. This week, I've got some nice tips and tools for you. Do you have any suggestions? Feel free to hit my DM's on Twitter , or email me at sector035 at pm.me. Off to this week's overview: Quiztime Solution Overload Search Instagram Video Verification Which Face Is Real? Facebook Marketplace Intelligence Conference conINT Article: Quiztime Solution Steven \"Nixintel\" Harris has been at it again, with a wonderful write-up of a Quiztime challenge. From identifying the specific aeroplane, to finding information about it's farewell tour, and eventually ending up with the exact location the photo was taken. Another great technique was introduced here by Steven: Using the Virtual Tours in Google Earth to quickly visit dozens of sites, to find a matching location. Thanks for this awesome write-up! The result of Nixintel's overpass query of cell masts Link: https://nixintel.info/osint/planes-and-cell-masts-a-quiztime-epic Tool: Overload Search Twitter account cyb_detective posts a constant stream of tools and tips on OSINT. Last week she tweeted about a very cool Extension called 'Overload Search' by Partial Overload , and is a nifty little tool to help people build a Google search query. Fill in all the necessary fields, and your own custom search is fired off at Google. If you search a lot by hand, this won't be so useful for you, but for people starting in the field of investigating, this is a very welcome tool to have. One little note: For me, the pull-down menu with languages and countries didn't work, so use the international ISO format for the country codes, and try the official English names of countries. Constructing a query bit by bit Link: Chrome extension Tip: Instagram Video Verification An awesome tip from Twitter user ohshint_ : If you're having issues with Instagram, and they demand a video of your face, you can trick the system easily by creating a little video. Open the Sketchfab, fire up the camera of your mobile phone, and capture away! #OSINT Protip 13: Is #Instagram banning your sockpuppets? Use this simple trick to bypass their new \"video verification\" data collection scheme. Step 1: Go to https://t.co/LCpxZZKOvO Step 2: Use your phones camera and follow Instagram's instructions. #OSINTProtip #Metaverse — OH SHINT! (@ohshint_) November 20, 2021 Link: https://sketchfab.com/tqyw/collections/human-face Site: Which Face Is Real? A cool tip from @digint31 , to practice your skills on recognizing computer generated faces. It's not that difficult if you know what to look for, but if you're struggling a bit I certainly recommend you to play here. If you're still new to the game, I can recommend a blog post by Nixintel , in which he describes all the tell-tale signs of such photos. Spotting the fakes Link: https://www.whichfaceisreal.com Tip: Facebook Marketplace Craig Silverman dove into Facebook Marketplaces, and found a nice way to find every listing on a marketplace account, and find out what year a Facebook account was created as a bonus at the same time. I've tested it with a Dutch Facebook account, and it does show up indeed. I've had a quick look at the source code, and the traffic sent to the browser, but it seems this is a text that is sent from the server, and I haven't been able to find a full date or timestamp somewhere. So it seems this is all you get, but this can be a very helpful tip! Thanks for sharing that with us Craig! For more tips like this, make sure to follow his newsletter over here . Information as seen by a Dutch Facebook user Link: https://www.getrevue.co/profile/craigsilverman/... Media: Intelligence Conference conINT On November 20 there was conINT , an intelligence conference, with some awesome speakers like Nicole Beckwith , Rae Baker , IntelCorgi and more! For now, it seems the video can only be watched back as a whole on Twitch. Link: https://www.twitch.tv/videos/1210896210 Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/c/c/5/8/2/cc582f7a3cb901df727b5981e30d012c70366d5e-2146-nixintel.jpg","https://sector035.nl/user/pages/articles/2021-46/2146-facebook.jpg","https://sector035.nl/user/pages/articles/2021-46/2146-overload-search.jpg","https://sector035.nl/user/pages/articles/2021-46/2146-whichfaceisreal.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_581c59c84ebb_0.jpg","blog_data/images/blog_581c59c84ebb_1.jpg","blog_data/images/blog_581c59c84ebb_2.jpg","blog_data/images/blog_581c59c84ebb_3.jpg","blog_data/images/blog_581c59c84ebb_4.bin","blog_data/images/blog_581c59c84ebb_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2021-47","title":"","status":"ok","retrieved_at":"2026-08-29T16:26:22.13562+08:00","text":"Week in OSINT #2021-47 | Sector035 Week in OSINT #2021-47 Home Week in OSINT Articles Search Week in OSINT #2021-47 29th Nov 2021 api tutorial geolocation tool facebook A small episode this time, with some tools, API's and explanations on how to geolocate! Not really a massive newsletter this week, but after working extra hard to get the first version of my tutorial on chronolocation ready for publication, I took some time off. Small update or not, still some interesting topics that I saved in my notes from last week: DumpItBlue+ Geolocation Write-up Protractor for Chrome API's for OSINT Geolocating a Tree Tool: DumpItBlue+ This tool has some interesting features, and even though Facebook has changed its layout, there are still things that work. The tool has several options that you can use, but make sure to first visit the correct page. Want to dump all friends? First open the all friends tab. Want to remove comments? Make sure to be in the timeline, and so forth. A nifty Facebook tool, with auto-scroll, comments expander, removing of items and a lot more. Thanks Ritu and Irina for sharing this tool last week! Dumping friends to a nice HTML table Link: Chrome extension GitHub: https://github.com/arioux/DumpItBluePlus Article: Geolocation Write-up Twitter user hpiedcoq shared a great article on Twitter, written by DrStache . From a seemingly impossible photo, taken somewhere in the Middle-East, he found the exact location. Using some handy tools, like the online protractor and OnTopReplica , among some maths to calculate the distance of buildings. Using the online protractor Link: https://link.medium.com/KCny0UG4slb Protractor: https://www.ginifab.com/feeds/angle_measurement/ OnTopReplica: https://github.com/LorenzCK/OnTopReplica Tool: Protractor for Chrome Talking about protractors, do you know it's also possible to have one in your browser? One that I found som time ago is the protractor for Google Chrome. It sits in your toolbar and when activated, it will project a simple protractor on the screen, making it easy to measure all kinds of angles. Measuring angles made easy Link: Chrome extension Tip: API's for OSINT This is an awesome list with API's that can be used to retrieve all kinds of information. This seems to include some paid options, but a lot of these sources are absolutely free. Thanks for collecting all these resources, and sharing it with us ' Cyber Detective '! An abundance of API's for us! Link: https://github.com/cipher387/API-s-for-OSINT Media: Geolocating a Tree Brecht Castel is a journalist and fact checker at Knack, and is well known on Twitter for his investigations. Since recent he also has a YouTube channel, where he'll be sharing some of his techniques. His second video, posted last week, shows you how he geolocated a baobab tree. Thanks Brecht! More tutorials like this are always welcome! Link: https://youtu.be/g-MvXuCCkEA Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/1/5/2/0/d/1520d0530dfb88b34cf5a1de89bf2143dbf083cf-2147-protractor.jpg","https://sector035.nl/user/pages/articles/2021-47/2147-apis.jpg","https://sector035.nl/user/pages/articles/2021-47/2147-dumpitblue.jpg","https://sector035.nl/user/pages/articles/2021-47/2147-protractor2.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_56efee5333b5_0.jpg","blog_data/images/blog_56efee5333b5_1.jpg","blog_data/images/blog_56efee5333b5_2.jpg","blog_data/images/blog_56efee5333b5_3.jpg","blog_data/images/blog_56efee5333b5_4.bin","blog_data/images/blog_56efee5333b5_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-06","title":"","status":"ok","retrieved_at":"2026-08-29T16:25:59.674998+08:00","text":"Week in OSINT #2022-06 | Sector035 Week in OSINT #2022-06 Home Week in OSINT Articles Search Week in OSINT #2022-06 14th Feb 2022 maps instagram geolocation iot processes reverse image search military geopolitical A small update from the world of OSINT news, with some maps, some geopolitical affairs and some tools. This week there's only a small update, since I ran into some issues with another tool I wanted to include. Once in a while there's a tool that looks really great, but when it's giving me trouble, it's eating away a lot of time needed to write all this. Things happen, and maybe I have the time to bugfix it and include it some other day. But despite being a small update, it's not less interesting in my opinion: Geowifi Ukraine Monitor Sterra Cleanup Pictures Cognitive Biases Tool; Geowifi The great Gonzo created an awesome tool: Geowifi. I had some issues with the virtual machine I use to test tools, so sadly enough I wasn't able to give this one a go. I love how he didn't stick to Wigle only, but also used other sources to find as much information as possible! Thanks for sharing Gonzo! Intoducing GeoWiFi | 📡💘🌎 I developed the tool because my twitter thread on the subject ( https://t.co/6tuUzhAzQa ) was well received and I thought it might be interesting to take it a step further. pic.twitter.com/EXJYsFftQm — GOΠZO (@GONZOs_int) February 9, 2022 Link: https://github.com/GONZOsint/geowifi Site: Ukraine Monitor The Centre for Information Resilience has created a map with open source information on the Russian military movements along the Ukraine border. The map is hosted on MapHub and every entry is timestamped, and has information about its source. If you are following this event, this is a map you will absolutely appreciate. Exploring the map with military movements Link: https://maphub.net/Cen4infoRes/russian-ukraine-monitor Tool: Sterra Last week hpiedcoq tipped me off on a new Python script called Sterra by meakaaet , a new Instagram analysis tool. It downloads a set of followers or accounts that are being followed, and their information, and enables you to run some analysis on the results afterwards. You can simply 'compare' two sets of results, and output the accounts they have in common to a new XLSX. What I like is that all results are saves in an Excel sheet, so you can download multiple sets of information, and take your time analysing the results at a later point in time. I didn't run multiple jobs yet, and knowing how fast the social media landscape changes, it might be that this tool will trigger some rate limits in the future. Analysis of followers I did run into a few issues when I tried to install it with Python3.8, so a little heads-up. You need to: Run at least Python3.9 Have Python3.9-dev installed Link: https://github.com/novitae/sterraxcyl Site: Cleanup Pictures Last week I sent out a Quiztime challenge, and when going over one of the solutions I found a lovely link. The website 'Cleanup Pictures' is a website that uses AI to remove unwanted objects from photos. Twitter user MCantow used it to remove a car from a photo, after which a reverse image search gave him good results. As an example, you can see here what the results look like. After Before ↔ The slider might not work on mobile phones Link: https://cleanup.pictures/ Article: Cognitive Biases 'Dutch OSINT Guy' Nico wrote an article on cognitive biases and why it doesn't deserve a place during investigations. It's not a lengthy article, but I do suggest reading it. The topic is not only important, but it can make the difference between a solid investigation, and a story based on your own personal feelings and ideas. Thanks for sharing Nico! NEW BLOG: Why #OSINT doesn't need your feelings Read it here: https://t.co/fSRs85Ap01 pic.twitter.com/1OYO4RmOkP — Dutch Osint Guy Nico (@dutch_osintguy) February 7, 2022 Link: https://dutchosintguy.com/... FUNINT: Fun With Google When it comes to Google Streetview, there are several sites out there that share funny scenes captured by the cameras. Need a break from work? Want to relax by looking at some weird and funny things out there? Then these sites might just be what you need. Link: https://www.streetviewfun.com/ Link: https://www.weirdgoogleearth.com/ Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/6/8/a/c/7/68ac76998ddc074d31322a947b26241fabdf6269-2206-challenge.jpg","https://sector035.nl/images/6/c/e/3/6/6ce36fcaff9ad0b71ca74771f8739f403ef2254e-2206-cen4infores.jpg","https://sector035.nl/images/d/3/2/b/f/d32bf21a9deeb77392a87f9e7161871f63f5269f-2206-challenge-clean.jpg","https://sector035.nl/user/pages/articles/2022-06/2206-sterra.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_cbf38e6d19b6_0.jpg","blog_data/images/blog_cbf38e6d19b6_1.jpg","blog_data/images/blog_cbf38e6d19b6_2.jpg","blog_data/images/blog_cbf38e6d19b6_3.jpg","blog_data/images/blog_cbf38e6d19b6_4.bin","blog_data/images/blog_cbf38e6d19b6_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-07","title":"","status":"ok","retrieved_at":"2026-08-29T16:25:32.569787+08:00","text":"Week in OSINT #2022-07 | Sector035 Week in OSINT #2022-07 Home Week in OSINT Articles Search Week in OSINT #2022-07 21st Feb 2022 maps instagram geolocation google companies corporate intelligence hacking cybercrime Another week with some tips, tricks and tools in the world of OSINT. Most have been shared a lot already, maybe I should try and find some more niche links... I get sent tips, tools and articles once in a while, but it can happen that they don't make it in my newsletter. Please don't feel bad, it's nothing personal, but usually I didn't have enough time to test it, or somehow I ran into an issue and needed to check things out, after which it's left untouched for some time. I felt it might be good to clarify this, because it has happened a few times in the last weeks, and now you know. But... For this week, I have the following items left to share: Mountains and Geolocating Company Search Hacking Snakes OSINT Start.me Page Investigating Digital Ads Google Maps Tip Instahunt Media: Mountains and Geolocating Benjamin Strick talks about how to use mountains for geolocation purposes. He talks about Google Earth 3D, how to use it and gives some examples on how he used it in previous investigations. After that he also shows the website PeakVisor, and talks about the main differences between the two tools. Link: https://www.youtube.com/watch?v=vNu2X7aCMkU Tip: Company Search Twitter user OSINTcanada shared a nice little trick last week on how to find information on companies via a Google search. Fun little company hack: site:( https://t.co/tAhZeUa6Aj | https://t.co/LLqyq4R4X9 | https://t.co/Hvzust06bd ) \"company name\" After your search, click the News tab. Have fun! — OSINTcanada 🌍 (@OSINTcda) February 16, 2022 I saw what was happening there, and very nice info-cards on people showed up. But there were lots of news articles in between too. So I tweaked the Google search a little, and added two other sites. It now shows even more hits, and mainly people: site:(linkedin.com/in | zoominfo.com/p | rocketreach.co | xing.com/people | contactout.com) \"company\" Article: Hacking Snakes Journalists of BR and WDR have been working together for months on end to trace down leads that were left behind by hackers over the years. By using open source, like archived pages, they were able to identify some people that are suspected to be part of a group of hacker with ties to the FSB. A visually stunning story by Hakan Tanriverdi , Florian Flade and Lea Frey, showing how investigative journalism can also work within the world of cyber-related issues. Link: https://interaktiv.br.de/elite-hacker-fsb/en Link: OSINT Start.me Page The Twitter account @start.me shared a link page last week, on the topic of OSINT. This collection of links is by the Faros Foundation and contains loads of links. Many of them are probably known already, but as usually there are also some niche and lesser known websites. There's an abundance of start.me pages already, and loads of links to sources, but there's always something new to discover. Links by the Faros Foundation Link: https://start.me/p/1kvvxN/ Article: Investigating Digital Ads Craig Silverman has his own newsletter, and the last issue talks about different sources you can use when you're trying to track down digital advertisements. He shares tools I've already covered , like TheMarkup's Blacklight, but also new sources like PageXray and Well-Known.dev. Nice collection of links, thanks for sharing! Detecting all trackers at 'purina.com' GetRevue newsletter: https://www.getrevue.co/profile/craigsilverman/ Tip: Google Maps Tip A nifty little trick by The SEINT on Google Maps and Google Streetview. When looking for a specific crossing, simply search for those streets with an ampersand. I tested it, and Google's AI understands anything you throw at it. Bot streets with a space, comma, ampersand, the word 'and', everything seems to work. Still a nice trick that I didn't know until now. Thanks for sharing! Looking for a specific crossing Site: Instahunt A cool little site that helps you find interesting locations within Instagram. Simply search for a location, click the button, grab all the JSON outout from Instagram, and the tool maps everything out for you. It returns and shows the Instagram and Facebook links to all sites returned by the search. Great tool by Louis Tomos Evans ! Quickly mapping locations Link: http://instahunt.co/ Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/0/1/5/e/d/015ed5203d4aebd5fdc213094f4b085d1d14989d-2207-instahunt.jpg","https://sector035.nl/user/pages/articles/2021-22/2122-blacklight.jpg","https://sector035.nl/user/pages/articles/2022-07/2207-googlemaps.jpg","https://sector035.nl/user/pages/articles/2022-07/2207-snake.jpg?classes-caption=1","https://sector035.nl/user/pages/articles/2022-07/2207-startme.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_da4d946e6ccf_0.jpg","blog_data/images/blog_da4d946e6ccf_1.jpg","blog_data/images/blog_da4d946e6ccf_2.jpg","blog_data/images/blog_da4d946e6ccf_3.jpg","blog_data/images/blog_da4d946e6ccf_4.jpg","blog_data/images/blog_da4d946e6ccf_5.bin","blog_data/images/blog_da4d946e6ccf_6.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-11","title":"","status":"ok","retrieved_at":"2026-08-29T16:25:02.064841+08:00","text":"Week in OSINT #2022-11 | Sector035 Week in OSINT #2022-11 Home Week in OSINT Articles Search Week in OSINT #2022-11 21st Mar 2022 geolocation ip address quiztime chronolocation obsidian accessibility Another short episode this week, with some cool links, IP Geolocation, workflow and reports, and chronolocation. This week it features something I discovered myself last week, a new and easy tool to use with chronolocation during the night. If ancient sailors were able to navigate the stars, it must be possible to use this same thing for chronolocation, right? And yes, up to a certain degree it's absolutely possible. But that's not all I have for you this week, there's more: Malfrat's OSINT Map IP Geolocation Obsidian in Your OSINT Work Accessibility and Reporting Chronolocation With Stars Links: Malfrat's OSINT Map The OSINTFramework didn't get an update for years, so Twitter user @MalfratsInd forked the original repo on GitHub and recreated it, filling it with links that are currently active and useful for investigations. There's still a lot of sites to cover, so if you have more ideas, head over to the GitHub repo and help it grow! Interactive OSINT mindmap Link: https://map.malfrats.industries/ Media: IP Geolocation Last month The OSINTCurious Project posted one of my articles on locating an IP address , and the lack of accuracy. I usually focus mainly on servers, but the techniques I wrote there are generic. Then I stumbled upon a video by Half as Interesting , describing an event from 6 years ago. It's about the dangers of blindly following locations provided by IP2Geo datasets. And it's shocking to read that even law enforcement didn't verify any of such information either. So I repeat it again, please don't make this mistake... Verification is key! With everything! Article: https://arstechnica.com/tech-policy/... Media: Obsidian in Your OSINT Work Micah Hoffman has his own company for years already, and he has some awesome course material over at MyOSINT.Training . One of the things he's been working on in the past few weeks is Obsidian, that has featured in my newsletter before too. And a few weeks ago he showed the possibilities in a live stream for OSINT investigations. Micah going over Obsidian for OSINT YouTube: https://youtu.be/sKF37Ng4gaI Courses: https://www.myosint.training/ Article: Accessibility and Reporting And another section that mentions Micah, because last week he played around with some highlighted boxes in an image. After converting the image to greyscale, not a lot was left to be seen. It might not be the best simulation (look at Coblis for a better option ), but the problem still exists. The most common problems are with red or green, and can range from seeing it weak to not seeing the colour at all. And let red and green be very common colours used in all these images we all share with the world. Simulating what people with colour blindness sees Link: https://webbreacher.com/2022/03/16/report-accessibility/ Tip: Chronolocation With Stars When Julia Bayer posted her Quiztime challenge last week, I went off to search for a tool to line up stars and other celestial elements. There are several 'sky maps' out there, but this tool is simple, clean and easy to use. After finding the rough location of the moon, you can match the date and time until there's a match. You can also select celestial bodies, and see their exact position and their rise and set times. Another new thing I discovered, by looking at Quiztime challenges ! Matching stars to find a time Link: https://www.timeanddate.com/astronomy/night/ Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/0/f/b/a/0/0fba00030f927bbf6ee5cec83ba4ae847d84a0da-2211-osintmap.jpg","https://sector035.nl/user/pages/articles/2022-11/2211-colourblindness.gif","https://sector035.nl/user/pages/articles/2022-11/2211-obsidian.jpg","https://sector035.nl/user/pages/articles/2022-11/2211-stars.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_767ba539d2f1_0.jpg","blog_data/images/blog_767ba539d2f1_1.bin","blog_data/images/blog_767ba539d2f1_2.jpg","blog_data/images/blog_767ba539d2f1_3.jpg","blog_data/images/blog_767ba539d2f1_4.bin","blog_data/images/blog_767ba539d2f1_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-16","title":"","status":"ok","retrieved_at":"2026-08-29T16:24:36.970504+08:00","text":"Week in OSINT #2022-16 | Sector035 Week in OSINT #2022-16 Home Week in OSINT Articles Search Week in OSINT #2022-16 25th Apr 2022 geolocation imagery google satellite imagery quiztime osintcurious linkedin legal verification analytics Another filled episode, with some videos and articles, but I also added some tips and insights on the new Google Analytics platform. This week there's quite some content, and there's been some really nice information out there that I needed to share here too. But I also decided to share some personal insights on Google Analytics 4. Because these analytics tags are being seen in the wild more and more, and since there aren't a lot of sights indexing them, we may have to do some manual searching for this: WeVerify Quiztime Walk Through Spectator Earth US Legality and Scraping Google Analytics ISearchFrom Bombal and TOCP Article: WeVerify In this article Jochen Spangenberg from DW looks back at many years of development of the WeVerify tool. Initially starting as the InVID project, this tool is now one of the most important tools used by factcheckers all over the world. It contains a range of image, text and video verification tools in the browser. Even though the project has officially ended last year, it may continue via a new project that is in the last stage of proposals. Let's hope it keeps being developed! The WeVerify toolbox Article: https://innovation.dw.com/... Link: Chrome extension Media: Quiztime Walk Through Twitter user Nattic has been solving Quiztime challenges for a while now, and some time ago he started creating YouTube videos of his work process. This video shows how important it is to pay attention to small details, and also how spacial awareness can result in solving a seemingly difficult quiz with ease. A great look into the art of geolocation that's worth to check out. Geolocating with Nattic Link: YouTube Video Site: Spectator Earth Some time ago Twitter user OSINT_Research shared a link to the website of Spectator , that features a range of tools for satellite imagery. It has easy access to freely available imagery by Sentinel and Landsat, and they even provide API access in case you want to automatically monitor an area. And don't think that it only features imagery in natural colour, because if you need an NVDI filter, or specific bands, that too is available. Searching and filtering free satellite imagery Link: https://spectator.earth/ API: https://api.spectator.earth/ Article: US Legality and Scraping Zack Whittaker has covered the latest news on legal issues concerning web scraping in the US. It may not seem to be important for some people, and others may not understand the difficulty here, but I do think it's a good idea to read the article. It clearly shows how the rules within the terms of service can be overruled by the law. This of course doesn't mean this outcome will be the same in other states or countries, but it does send a positive signal to journalists and researchers. Photo by Greg Bulla - Unsplash Link: https://techcrunch.com/2022/04/18/web-scraping-legal-court/ Tip: Google Analytics Google Universal Analytics (the famous UA codes) will be replaced by a new analytics platform, called Google Analytics 4 or GA4 for short. This already started somewhere in 2020, but here's a recent quote from Google's support page: On July 1, 2023, standard Universal Analytics properties will no longer process data. You'll be able to see your Universal Analytics reports for a period of time after July 1, 2023. However, new data will only flow into Google Analytics 4 properties. This means that it's important to extend the searching for analytics codes with a different code, that has a different prefix. It's of course possible to search for these tags by using websites like PublicWWW , NerdyData or even Shodan . Sadly enough I've seen that analytics specific platforms like DNSlytics still haven't been updated to use GA4. So be prepared to run manual searches for the time being, until they finally catch up! How to find the codes? To find the code, dive into the source code of a page, and look for: googletagmanager.com In case a global site tag has been used, this will point to a JavaScript that is called via the following piece of HTML code, where GA_MEASUREMENT_ID is the unique analytics code for this site or page: <script async src=\"https://www.googletagmanager.com/gtag/js?id=GA_MEASUREMENT_ID\"></script> When you dive into the source code, you can probably spot the analytics code, when you look at the last line of this code snippet: <script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push( {'gtm.start': new Date().getTime(),event:'gtm.js'} );var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src= '//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-AB1C2D'); In this case, it's the Google Tag Manager code that is clearly visible, starting with the prefix GTM- . Isn't there an easier way? As usual, there is indeed an easier way! Because you can install a nifty little extension made by Google, that will show you exactly what Google Analytics codes are on a website or page, and even are able to record all your visits, if you have a need for that. Easy overview of analytics codes GA4 Article: https://support.google.com/analytics/answer/10089681 Link: Chrome extension Tip: ISearchFrom Just a golden oldie that I think needs to be shared again. The website 'I Search From' can be used to target your Google searches by matching a specific location and language. Google will use this information to show 'localized' content within the search results, by which I was able to find a Chinese fish processing plant some years ago. Haven't heard from it yet? I do recommend you to have a look, play around with it, and compare the difference and quality of search results. Searching with local results Link: http://isearchfrom.com/ Media: Bombal and TOCP Last week some members of The OSINT Curious Project were guests at David Bombal's YouTube channel for an interview, where they talked about OSINT, how it's used within different areas of expertise, and share some stories from the battlefield. Well over an hour of tips, resources and information on how to get started with OSINT. The TOCP crew meet David Bombal Link: https://youtu.be/ImWJgDQ-_ek Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/5/4/8/0/a/5480aeeafd3c0b615b1b259b594f45c3b222a389-2216-isearchfrom.jpg","https://sector035.nl/user/pages/articles/2022-16/2216-linkedin.jpg","https://sector035.nl/user/pages/articles/2022-16/2216-spectator.jpg","https://sector035.nl/user/pages/articles/2022-16/2216-tagassistant.jpg","https://sector035.nl/user/pages/articles/2022-16/2216-weverify.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_a74f16b0bbbe_0.jpg","blog_data/images/blog_a74f16b0bbbe_1.jpg","blog_data/images/blog_a74f16b0bbbe_2.jpg","blog_data/images/blog_a74f16b0bbbe_3.jpg","blog_data/images/blog_a74f16b0bbbe_4.jpg","blog_data/images/blog_a74f16b0bbbe_5.bin","blog_data/images/blog_a74f16b0bbbe_6.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-22","title":"","status":"ok","retrieved_at":"2026-08-29T16:24:12.069276+08:00","text":"Week in OSINT #2022-22 | Sector035 Week in OSINT #2022-22 Home Week in OSINT Articles Search Week in OSINT #2022-22 6th Jun 2022 maps twitter geolocation youtube programming This Monday I've got another small collection of tips, articles and an upcoming interesting live stream in the field of OSINT. While diving into some Twitter related stuff, I discovered that in early April 2018 I only had about 250 followers when I started my Week in OSINT. Now, a bit over 4 years later, I have about 24k followers! And even though I'm a lot busier now than back then, I still love creating these little articles. Thanks for connecting, and sharing all those lovely resources with me! Twitter Search Subscriptions Spoonbill OSINT on Oil Rigs OSINT Automation YouTube Shorts TWITTER: @evowizz @wondersmith_rae @SANSDefense @jms_dot_py @dutch_osintguy @matt0177 @thegumshoo @cyb_detective @DemoDawid Tip: Twitter Search Subscriptions Dylan Roussel shared an upcoming feature on Twitter last week . It seems that they're testing a new option where you're able to turn on notifications on new tweets within a search query. It's unknown yet when it'll be live, and so far it's only visible to Alpha testers of the Twitter app. Let's just hope the testing goes fast, and that soon we're all able to use this feature! Image by Dylan Roussel Tip: Spoonbill I know this is a golden oldie, but since I've never covered it in my newsletter, and was reminded about it, I think it's time to share this one. Spoonbill gives you the ability to track the changes made by a Twitter account. Not all usernames are being tracked, but you can start tracking by connecting a Twitter account and subscribing to changes. To check whether an account is already in their database, simply go to: https://spoonbill.io/twitter/data/{USERNAME} Tracking changes over time Link: https://spoonbill.io/ Article: OSINT on Oil Rigs Rae Baker loves investigating maritime object, and this time she looked at oil rigs and other related items. In her new blog she covers a bunch of really useful resources that can help investigate anything that might have a connection to the world of oil. From geolocation, to tracking the transport of products like crude oil. Well done, and thanks for sharing this! Exploring the world of oil online Link: https://link.medium.com/h8G2G3Emzqb Media: OSINT Automation On June 23 there will be another live stream by SANS . In this stream Justin Seitz is their guest, and Nico Dekens , Matt Edmondson and John Terbush from SANS will interview him on the automation of OSINT. Can't wait to join this talk, and you should too if you're interested in learning some more technical OSINT! Join the crew, and start automating Link: https://youtu.be/S5-PKoEBbP8 Tip: YouTube Shorts This weekend Cyber Detective shared a nifty trick for YouTube shorts . You probably know them by now, the short clips that popup everywhere. They are slightly different from normal videos since they don't start with the standard interface. No way to skip to a specific time frame, no settings, no subtitles. But by changing the URL slightly, it's possible to enable them all. Twitter user Demian even gave an even easier trick. Simply take the URL, and change the word 'shorts' to the letter 'v'. So this: https://www.youtube.com/shorts/yFuK68u2-hw becomes: https://www.youtube.com/v/yFuK68u2-hw YouTube will rewrite the URL automatically and load the desired video in a regular player. Thanks for sharing this tip! Loading YouTube shorts in a regular player Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/6/e/0/e/9/6e0e94a67596d64b093fc8771d4c020249b2640d-2222-oilmap.jpg","https://sector035.nl/user/pages/articles/2022-22/2222-automating-osint.jpg","https://sector035.nl/user/pages/articles/2022-22/2222-spoonbill.jpg","https://sector035.nl/user/pages/articles/2022-22/2222-twittersearch.jpg","https://sector035.nl/user/pages/articles/2022-22/2222-youtube.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_3857113ce3ae_0.jpg","blog_data/images/blog_3857113ce3ae_1.jpg","blog_data/images/blog_3857113ce3ae_2.jpg","blog_data/images/blog_3857113ce3ae_3.jpg","blog_data/images/blog_3857113ce3ae_4.jpg","blog_data/images/blog_3857113ce3ae_5.bin","blog_data/images/blog_3857113ce3ae_6.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-28","title":"","status":"ok","retrieved_at":"2026-08-29T16:23:45.528119+08:00","text":"Week in OSINT #2022-28 | Sector035 Week in OSINT #2022-28 Home Week in OSINT Articles Search Week in OSINT #2022-28 18th Jul 2022 maps geolocation extension add-on tool social media programming documentary It's time for another break again, so this Monday I've rounded up some interesting links and have some extra bonus content! Every year around this time I take a break for a few weeks, and this year it was very much needed, since I've been busy on all levels. So in the meantime, I've collected some things that you can look at for the coming weeks. Maybe you could help out with adding platforms to WhatsMyName, or learn how to code Python. Enough ideas to help you through the upcoming weeks WhatsMyName Learn to Code Geolocation with Mountains Selection Search FreeMapTools Documentaries Tool: WhatsMyName Micah Hoffman is going to change the layout of the WhatsMyName script he has kept up for years already. It is one of the best tools out there, with a minimum of false positives, and he sure needs your help. Not only can you help by adding more platforms, but you can also help out thinking about a new JSON layout! Upcoming changes to WhatsMyName Link: https://github.com/WebBreacher/WhatsMyName Tutorial: Learn to Code You have loads of time on your hand, and finally want to spend some time learning how to code Python? Then I can tell you that FreeCodeCamp has got you covered! Learn all the basics with the course \"Python for Everybody\", that can be found under \"Scientific Programming with Python\". The good thing of it, is that you don't even need to create an account! Just jump right in, go over the videos, code along, and answer some questions if you want to! And did you know that on the bottom of the page there are the most popular tutorials? And that the news section has loads of extra content too, that's worth looking at? Scraping tweety things with Freecodecamp Link: https://www.freecodecamp.org Tutorial: Geolocation with Mountains A few weeks ago Eyran Millis shared a tutorial on LinkedIn about using mountain ridges in geolocation tasks. He goes over several use cases, and shows how one can use different sites to look for mountains and hills. Sites like PeakVisor , Peakery and Peakfinder are all included, and he gives some valuable tips on each of these. Thank you Eyran, for putting this guide together! Using PeakVisor to verify a location Link: https://www.linkedin.com/posts/... Tool: Selection Search The tool 'Selection Search' is a small tool for Chrome and Firefox that enables you to quickly search for selected text. The default selection has Google, YouTube and Stackoverflow, but it's extremely easy to add your own websites. It has a lot of customizable options too, to open links in a new window, incognito mode, a tab and it's even possible to assign hotkeys. A small, but very useful tool that was sent to me by Twitter user TRADECRAFT14 . It's possible to add your own sites Link: Chrome extension Link: Firefox add-on Site: FreeMapTools The website FreeMapTools has a large collection of handy tools when it comes to maps in general. Sadly enough some very useful tools aren't available any more due to costs. Some tools that are still working are mentioned on the front page, like a distance calculation tool. Thank you NothicEye , for sharing this site over on Discord! From the fire department, to a conference Link: https://www.freemaptools.com Bonus: Documentaries As a little bonus, I'll include some interesting documentaries for you to watch, and they all contain some level of online investigations. Netflix: D.B. Cooper: Where Are You?! A bran- new miniseries about the infamous skyjacker that goes by the name of D.B. Cooper. In 1971, he hijacked a plane and after receiving $200.000, he jumped out of a Boeing 727 after it took off to Mexico. And it wouldn't be in this episode if it wouldn't contain some armchair sleuthing. Link: https://www.netflix.com/title/81349547 Netflix: Why did you kill me? This is another documentary on Netflix, this time it is a story about a mother whose daughter was killed. A chilling story, about how a family used social media to go after the notorious gang involved in her death. Link: https://www.netflix.com/title/80991050 YouTube: Innocent Victims of Reddit Armchair sleuths are well known for solving a lot of unsolved cases, and the ease of which one can do an online investigation is part of the reason. But it doesn't always turn out so good! Have a look at this video by Wavywebsurf and make sure you don't make the same mistakes! Link: https://youtu.be/hi14dP5Rdm0 Have a good couple of weeks and enjoy your searches! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/8/9/6/4/7/896478ae907c81f63625348a8d64cbeb9e558955-2228-geolocation.jpg","https://sector035.nl/user/pages/articles/2022-28/2228-freecodecamp.jpg","https://sector035.nl/user/pages/articles/2022-28/2228-freemaptools.jpg","https://sector035.nl/user/pages/articles/2022-28/2228-selectionsearch.jpg","https://sector035.nl/user/pages/articles/2022-28/2228-whatsmyname.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_6d550f856eff_0.jpg","blog_data/images/blog_6d550f856eff_1.jpg","blog_data/images/blog_6d550f856eff_2.jpg","blog_data/images/blog_6d550f856eff_3.jpg","blog_data/images/blog_6d550f856eff_4.jpg","blog_data/images/blog_6d550f856eff_5.bin","blog_data/images/blog_6d550f856eff_6.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-35","title":"","status":"ok","retrieved_at":"2026-08-29T16:23:24.555974+08:00","text":"Week in OSINT #2022-35 | Sector035 Week in OSINT #2022-35 Home Week in OSINT Articles Search Week in OSINT #2022-35 5th Sep 2022 maps tutorial geolocation bookmarks opsec google This week only a short episode, but with some interesting topics! Like Gmail's GAIA, geolocation tips and loads of links and tips! This weekend I've been rather busy, and chose to spend some more time for myself than on this episode. But I still managed to gather some interesting topics, and I'm especially excited about the first article! Despite the fact it comes with some dangers, it's interesting to see that the holy grail of GAIA based investigations is found: From GAIA to Gmail Landmark Identification Collection of Collections OpSec and OSINT Tutorial: From GAIA to Gmail Some time ago I received a message from Bob Engelen , with a tip on how to resolve an email address connected to a Google account, when you only have the GAIA ID. I've written two guides over the years ( here and here ) on how you can leverage the information within Google accounts to find more information. Since late 2020 Google has started removing a lot of information regarding this, so it isn't as useful as it used to be. But one thing was left to be discovered: How can you find the email address when you only have a GAIA iD? Well... Go over to LinkedIn, and read Bob's article on how to do just that! Be careful, because you will have to send an actual message to the other party involved. And since you can't copy-paste from the article on LinkedIn, the actual URL you need to use is as follows: https://hangouts.google.com/?action=chat&pi={GAIA ID} Resolving an email address from a GAIA ID Link: https://www.linkedin.com/posts/... Sites: Landmark Identification OH SHINT! sent out a tweet with some very useful websites, that can help you with a geolocation task. Geohints offers a visual database of lots of landmarks and their respective geographic locations. The landmark recognition tool over at Toolpie uses image recognition to find where a landmark might be located. And the German site Brueckenweb has a database of bridges from all over the world, and offers a search function on parts of the name, construction type, year of construction and lots more. Looking at traffic lights in Europe on Geohints Link: https://geohints.com Link: https://landmark.toolpie.com Link: https://www.brueckenweb.de/... Links: Collection of Collections Twitter user OSINT Tactical expanded a list of Start.me pages that were collected by OSINT_Research . And besides expanding it, he also created a new Start.me page that is a collection of OSINT link collections. Besides that, he also created a backup over on GitHub, where you can find more than 130 link collections, filled with thousands of links to any subject imaginable. Thank you for collecting all these links and sharing it with the community! A new @startme OSINT project created by @OSINT_Research has now been added to OSINT inception which is a start-me of the best #OSINT start-me projects, you can also search through all projects with a Google CSE on the right side of the page: https://t.co/9K4xitjb2u #Inception — 𝚃𝚊𝚌𝚝𝚒𝚌𝚊𝚕 𝙾𝚂𝙸𝙽𝚃 𝙰𝚗𝚊𝚕𝚢𝚜𝚝 (@OSINT_Tactical) August 29, 2022 GitHUb: https://github.com/C3n7ral051nt4g3ncy/... Start.me: https://start.me/p/Pwy0X4/osint-inception Article: OpSec and OSINT Matt Makowski has written an article on operational security. But he did it in an interesting way, because he does not only show you what is important to keep hidden yourself, but he also shows what information could be gathered if someone you are investigating wasn't privacy minded. Via a collection of diagrams and examples he gives you pointers on what to look for when you are investigating someone, and at the same time he gives tips on how to stay secure yourself. Another great article from Matt! Pivot points and possible privacy concerns Link: https://www.osintme.com/... Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/user/pages/articles/2022-35/2235-gaia-to-email.jpg","https://sector035.nl/user/pages/articles/2022-35/2235-geohints.jpg","https://sector035.nl/user/pages/articles/2022-35/2235-osintme.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_c9657c1fd793_0.jpg","blog_data/images/blog_c9657c1fd793_1.jpg","blog_data/images/blog_c9657c1fd793_2.jpg","blog_data/images/blog_c9657c1fd793_3.bin","blog_data/images/blog_c9657c1fd793_4.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-42","title":"","status":"ok","retrieved_at":"2026-08-29T16:22:57.154195+08:00","text":"Week in OSINT #2022-42 | Sector035 Week in OSINT #2022-42 Home Week in OSINT Articles Search Week in OSINT #2022-42 24th Oct 2022 geolocation opsec google youtube tool search engine fake news cheat sheet disinformation Today I have a large edition, with topics like: Operational security, google searches, a cheat sheet and some handy tips! I spent some extra time last week collecting all kinds of links and tips, and I had lots of fun creating this edition. There were so many awesome tweets, articles and tips shared last week, and so many topics to cover! I enjoy writing such episodes the most, since it usually has something for everyone. Overview: Naval Opsec Let's Geolocate Bookmarklet Chinese Propaganda Geotargeted Google Search YouTube Handles Geolocation Cheat Sheet News: Naval OpSec Steven 'nixintel' Harris shared the story that was sent out by Marsattaqueblog , about how during an exercise a French frigate was sunk while they were literally 'off the radar'. From November 21 to December 3, 2021, a total of 23 ships, one submarine and 65 aircraft embarked on a maritime exercise . Despite any radio contact, since all radio and satellite communication was jammed ( source ), the red team sunk one of the blue frigates, simply because of a location found via Snapchat. The blue frigate was close enough to the shore, that it was within reach of a 4G mast, and was able to connect to Snapchat. After the discovery of the active account, a simulated strike with 14 missiles was ordered, since a precision hit wasn't possible. Another example of how bad OpSec can have a devastating effect. Polaris 21 Tweet: https://twitter.com/APB_Laudrain/status/1582316787894714368 Media: Let's Geolocate Benjamin Strick has been busy making some more light-hearted content, according to his own words. And I can say it's a great thing, especially with all the conflicts in the world that are dominating the daily news. And I encourage you to do the same. You can for instance join him in this video where he will be geolocating large pieces of art from all over the world. Another awesome video from Ben, and despite the fact some locations were very easy to find, it does give insight into his thought process. Pay attention and take note how Ben uses all the information available to solve each and every question. Link: https://youtu.be/6_77F1EZ30s Tool: Bookmarklet Twitter user OSINT_Tactical created a bookmarklet that enables you quickly search for a username within a range of social media. I'm not really a fan of this, since it actually opens up a bunch of tabs with results and this might cause some issues. Firefox and Brave only opens a single tab by default, and within Chrome you can't seem to run it from a blank page, and you need to explicitly give the okay to open multiple tabs in your browser before it works. I did decide to share it here, because it's another easy and fast tip to quickly find possible leads. A bunch of tabs, and someone 'stole' my username? Link: https://github.com/C3n7ral051nt4g3ncy/... News: Chinese Propaganda Fergus Ryan and his colleagues had a look at some Chinese propaganda, that feature two girls from Uyghur and that shop up in several videos. This Twitter thread goes over the information they found, connecting these videos to the so called 'Information Office'. This is an interesting thread, showing how information campaigns are being used to spread a certain narrative, and how, sometimes, they can easily be pulled apart. Thanks for the tip Lou . A written confirmation in one of the videos? Twitter thread: https://twitter.com/fryan/status/1582960014053949440 Site: Geotargeted Google Search Henk van Ess sent me a tip about a new way of 'geotargeting' Google searches. For several years I've been using iSearchFrom , and this handy site is able to target a specific location when searching. When searching for news, Google sometimes shows news items from your local area, and with the ability to target a very specific area, this might come in very handy. This tip was immediately followed up by a tip from someone called ' Einat FB ', that pointed out there is another site, called ' U Search From ', which is a modified and better tool than I've been using. Thanks for these tips! Searching while targeting specific areas Link: https://valentin.app Link: https://usearchfrom.com Tip: YouTube Handles Over the last few days I have received multiple emails about a new YouTube feature, called YouTube Handles. Creators are able to claim a handle, that will enable someone to generate a link that looks like this: https://www.youtube.com/@redbull Currently, this page will send back an HTTP code '303' , that redirects the browser to a different URL. In this particular instance, it will redirect you to the URL: https://www.youtube.com/user/redbull . According to the blog about it on YouTube, everyone that already had a custom channel URL set up, will have that same name reserved as a handle, and they stopped the option of creating new custom channel URL's for now. It is unsure what the future holds, but if a lot of YouTube users will claim their own handle, following this news, it might be even easier to find them! Link: https://blog.youtube/news-and-events/... Tutorial: Geolocation Cheat Sheet If you are new to geolocation, and you are still struggling with finding clues, then this might be an awesome cheat sheet for you! The SEINT created a large mindmap with lots of things that might be visible in a photo, that can help you on your way. This is a work in progress, and will be updated when he finds more items, but it's already impressive! Don't forget to use this as a cheat sheet only, and make sure to always come up with your own ideas too, when analysing an image or video. You can find a PNG and PDF version of this mindmap over at the SEINT's GitHub. Small portion of the very large geolocation mindmap GitHub: https://github.com/seintpl/osint FUNINT: Spooky Logic An awesome geeky joke, created by @38mo1 , that comes up around Halloween, and involves some classic 'logic gates'. Some of these will be known by the OSINT community, since the basis of it all is Boolean algebra, the same thing we use when creating our innovative search queries. But for the electrical engineers, this is known territory! Thank you for sharing this, OSINT Amy ! Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/f/0/9/2/e/f092e3f263a5f547cee49992da43f777a76079c0-2242-geolocation.jpg","https://sector035.nl/user/pages/articles/2022-42/2242-bookmarklet.jpg","https://sector035.nl/user/pages/articles/2022-42/2242-funint.jpg","https://sector035.nl/user/pages/articles/2022-42/2242-polaris21.jpg","https://sector035.nl/user/pages/articles/2022-42/2242-propaganda.jpg","https://sector035.nl/user/pages/articles/2022-42/2242-valentinapp.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_48a4834913f4_0.jpg","blog_data/images/blog_48a4834913f4_1.jpg","blog_data/images/blog_48a4834913f4_2.jpg","blog_data/images/blog_48a4834913f4_3.jpg","blog_data/images/blog_48a4834913f4_4.jpg","blog_data/images/blog_48a4834913f4_5.jpg","blog_data/images/blog_48a4834913f4_6.bin","blog_data/images/blog_48a4834913f4_7.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-44","title":"","status":"ok","retrieved_at":"2026-08-29T16:22:21.072845+08:00","text":"Week in OSINT #2022-44 | Sector035 Week in OSINT #2022-44 Home Week in OSINT Articles Search Week in OSINT #2022-44 7th Nov 2022 geolocation social media threat intelligence snapchat reverse image search mastodon This week I've got a lengthy episode for you, with a lot of topics, and I dive into Mastodon! Within the realm of social media, there's a lot going on. Twitter is dominating the news, not really in a positive way, but also Mastodon is getting more and more popular. These shifts happen once in a while, so it's important to stay up to date and check what kind of information can be derived from new, or upcoming platforms. In this weekly episode I make a little start, by giving you some basic pointers, that might help you understand Mastodon a little better. But of course there's more: Backmoji Threat Intel Clean Images Geolocation Cheat Sheet Genealogy Mastodon Intro Mastodon for OSINT Site: Backmoji Griffin wrote an article on how to retrieve previous versions of a Snapchat Bitmoji. He found out that by simply changing the URL where the Bitmoji is stored, he can retrieve previous versions. And right after that Micah Hoffman fired up his notepad, VSCodium, PyCharm or whatever he uses, and created 'Backmoji', a page where you can quickly retrieve an overview of all previous versions. Finding previous versions of Bitmoji's Article: https://hatless1der.com/... Backmoji: https://backmoji.osint.ninja Links: Threat Intel Last week Start.me shared a large list of links, this time targeting the realm of cyber threat intelligence. This page contains sites, reports and news items from a lot of different threat intel companies, and contains a wealth of information. A lot of information within this line of work contains open source information, and I love to learn from other disciplines to enhance my own game. Thank you Rahmat Nurfauzi for collecting these resources! Sites and news on threat intelligence Link: https://start.me/p/wMrA5z/cyber-threat-intelligence Tutorial: Clean Images Steven 'nixintel' Harris has written another great blog post on a geolocation challenge. This time he shows us that with the use of online tools, it is possible to clean up pictures and enhance search results by reverse images searches. He then continues to explain how he answered the other questions, and you get a good look at all the processes involved when dealing with open source investigations in general. Cleaned up Original ↔ Comparison before and after using https://cleanup.pictures Link: https://nixintel.info/osint/... Tutorial: Geolocation Cheat Sheet The SEINT has been busy again! Last time, back in issue 2022-42 , I shared a geolocation cheat sheet. And this time, he releases the second one, aimed at pivot points you might be able to find inside a location. It contains lots of different things to think about, from cellphones and clothes, to toys and TV's. An amazing job, creating another great cheat sheet. Thank you for sharing these with the community! Another geolocaton cheatsheet with useful tips Link: https://github.com/seintpl/osint Media: Genealogy Last week I listened to an episode of Science Vs, a podcast that is all about science, fact checking, and scientifically interesting stories. The episode that aired on October 20 is called \"The Mystery of the Man Who Died Twice\". It dives into the story of how genealogy, together with the DNA databases over at GEDmatch, solved a mysterious case that baffled the police. This story shows the power of genealogy, and I highly recommend listening to this episode. Listen to the episode on Spotify Link: https://pod.link/1051557000 Episode: https://pod.link/1051557000/episode/... Tip: Mastodon Intro With the current dumpster fire that is going on over at Twitter, a lot of people have exclaimed they would transfer to Mastodon. This social media platform has been around for some years, and is slightly different from Twitter, in the way that it uses decentralized platforms. It is possible to run your own server, called an 'instance', or find one that suits your needs, and create a profile. Messages, called 'toots', can be shared locally or public, by having them shared with other servers. The platform communicates via the ActivityPub standard , and can be used to communicate with other platforms using the same standard, like PeerTube , PixelFed or WriteFreely . With this social media platform, there's quite a bit of new terminology, so here is a small list of terms to remember: Term Meaning ActivityPub The open and decentralized protocol designed for social networks. It has options to create, edit or delete content and has server-to-server communications for so called 'federation'. Boost Mastodon's term for re-sharing a message. It is comparable to Twitter's retweet function. Federation Federated servers within Mastodon are servers that communicate with each other. Content from one server can be seen, shared or interacted with from other servers that are 'federated'. It can be seen as a network of trusted third party instances. Fediverse The term for the network of connected instances, that communicate with each other. Instance Server that is running a Mastodon server. There are thousands of different servers out there, each with their own community, agenda, ideology et cetera. Toot A message posted on Mastodon, usually up to 500 characters long. Username It is possible to have multiple accounts on different servers. The way a username is shown is like this: @[Username]@[MastodonInstance.Domain] . This does make it somewhat challenging when looking for someone if they have a generic username. And with that, let's dive into som tips when you are searching on Mastodon for content of people! Tip: Mastodon for OSINT On (probably) most public servers, that are part of the large 'fediverse', for instance Mastodon.social , it is easy to search for content. This can be content on that particular server, or on the federated ones, thus giving you the option to quickly find accounts. And you don't even need to be logged in for this, but when you do have an account, it will give you some more options. Do search via other instances too, like Mastodon.online , since it may give you some extra results. Searching for topics or tags If you are looking for specific groups, people with certain ideas or ideology, then it may be a good idea to check out whether there are any instances of interest. Some servers that provide lists, or even a search option: https://search.noc.social https://fediverse.space https://mastodon.fediverse.observer/list https://the-federation.info/mastodon There are far more instances though, and searching them is a painstaking job, but with some creative searching it will be possible to find interesting servers. If you still can't find something, then I do also want to point you out to the list with servers that are not federated over at Mastodon.social. This list contains servers that share content they do not want to show up in the public timeline, and can be found here , under 'Moderated servers'. Looking at the names of some instances, where some parts even have been redacted, I think this list is a great place to check out. Thanks Sinwindie for pointing this out to me! Another list of banned or blocked instances, where some have sensitive of extreme content, can be found over here on GitHub . Some of these are offline now, but is possible to check what other instances they communicate with, using a specific API endpoint. It is called a list of 'peers'. And if the server still runs Mastodon, the peers can be retrieved by simply going over to the server and query the following API endpoint: {mastodon instance}/api/v1/instance/peers In case you are looking for another curated list of instances, that mostly overlap with the public list of peers of Mastodon.social, check out this list with close to 9000 fediverse instances . This also contains other ActivityPub platforms, like PeerTube, Misskey, Owncast and more. There is a lot of information freely available, and searching within federated instances is quite easy. Diving into platforms that are more private, might give some extra challenges, where finding the correct platform might be the most difficult part. But with the current situation over on Twitter, I do think it is important to start looking at these decentralized social media a lot more, start learning how they work, and look at new innovative ways to investigate them. Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/7/7/5/d/2/775d27ae69039981118dd3176af9c4938d54f268-2244-cleanup2.jpg","https://sector035.nl/images/c/f/8/b/b/cf8bbec0bf0e9becdbf074d449ca6a8936b26805-2244-mastodon-search.jpg","https://sector035.nl/user/pages/articles/2022-44/2244-backmoji.jpg","https://sector035.nl/user/pages/articles/2022-44/2244-cleanup1.jpg?chache=1","https://sector035.nl/user/pages/articles/2022-44/2244-geolocation.jpg","https://sector035.nl/user/pages/articles/2022-44/2244-mastodon-blocked.jpg","https://sector035.nl/user/pages/articles/2022-44/2244-threatintel.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_a967ed7a8565_0.jpg","blog_data/images/blog_a967ed7a8565_1.jpg","blog_data/images/blog_a967ed7a8565_2.jpg","blog_data/images/blog_a967ed7a8565_3.jpg","blog_data/images/blog_a967ed7a8565_4.jpg","blog_data/images/blog_a967ed7a8565_5.jpg","blog_data/images/blog_a967ed7a8565_6.jpg","blog_data/images/blog_a967ed7a8565_7.bin","blog_data/images/blog_a967ed7a8565_8.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-47","title":"","status":"ok","retrieved_at":"2026-08-29T16:22:03.535316+08:00","text":"Week in OSINT #2022-47 | Sector035 Week in OSINT #2022-47 Home Week in OSINT Articles Search Week in OSINT #2022-47 28th Nov 2022 instagram tutorial geolocation tool social media steam podcast This week I dive into tips and TryHackMe, Steam and scripting, and some other things from the world of OSINT! Over the last few months all sorts of threat intel accounts on Twitter have been using the hashtag #OSINT. This, combined with all sorts of worldly turmoil and wars, it has been really tricky to find some interesting new content on there. But there are still tips and tricks out there, and this week, I gathered the following topics for you: TryGeolocateMe Steam OSINT Bash Scripting Practical OSINT Instagram Metadata Tutorial: TryGeolocateMe Early 2020 TryHackMe user Bee created a room called 'geolocatingimages'. I didn't see it before, but stumbled upon it recently. In this room you work your way through multiple levels of geolocation tasks, ranging from simple reverse image searches to finding IP cameras on Shodan. This is the same user that created the Shodan room , but this time it's about practising your geolocation skills. A step-by-step tutorial on geolocation Link: https://tryhackme.com/room/geolocatingimages Tool: Steam OSINT Over on the TOCP Discord, it was Forthe again who shared a new tool. This Python script enables you to get a better insight into a Steam user. It dumps the public friends list, but also gives a peek into interactions between users. By investigating these interactions, it can give you a better understanding of who might be a 'closer' online friend. User info on Steam Listing of commenters Link: https://github.com/matiash26/Steam-OSINT-TOOL Media: Bash Scripting OSINT Dojo made a short video on bash scripting, standard scripting language in Linux and MacOS. With this little tutorial you learn how to create a script that will run multiple user enumeration tools, and save all the information in a text file. These small scripts can not only speed up the information gathering process, but also makes sure you don't forget to run certain tools. The basics of bash scripting Link: https://youtu.be/hrXZv0hST0M Media: Practical OSINT Join Matt Ashburn and his guest Brian Fuller from Mercyhurst University, where he is director of operations for the Ridge College of Intelligence Studies and Applied Sciences. In this podcast Brian discusses hands-on tips from the field of OSINT. I wished this episode was a lot longer, but it still has some good tips on things like operational security. Learn some very basic things, like keeping an eye on different time zones, or making sure to visit other sites before and after visiting a specific target. Another great episode from NeedleStack by Authentic8! The Authentic8 podcast, also on YouTube! Podcast: https://pod.link/1600516532/... YouTube: https://youtu.be/RMzz_yB7DUs Tip: Instagram Metadata Until a few months ago, it was possible to retrieve the JSON data of an Instagram post by adding something in the URL. Then it stopped working, and there were some workarounds. But lately I've seen people post a new and slightly edited version of it, and this one works as a charm! {IG URL}/ ?__a=1&__d=1 I suspect the addition of __d=1 is a parameter to tell Instagram that we are working with a 'desktop' version of Instagram. I don't have an older example at hand, but the amount of information that is sent back also seems to contain more than before. Retrieving JSON data from IG once more Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/2/b/4/3/0/2b430b2de45fa49fa4a0b6274f47ff4fea2f2e80-2247-steam2.jpg","https://sector035.nl/user/pages/articles/2022-47/2247-instagram.jpg","https://sector035.nl/user/pages/articles/2022-47/2247-steam1.jpg","https://sector035.nl/user/pages/articles/2022-47/2247-tryhackme.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_4806e024679a_0.jpg","blog_data/images/blog_4806e024679a_1.jpg","blog_data/images/blog_4806e024679a_2.jpg","blog_data/images/blog_4806e024679a_3.jpg","blog_data/images/blog_4806e024679a_4.bin","blog_data/images/blog_4806e024679a_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2022-49","title":"","status":"ok","retrieved_at":"2026-08-29T16:21:42.941671+08:00","text":"Week in OSINT #2022-49 | Sector035 Week in OSINT #2022-49 Home Week in OSINT Articles Search Week in OSINT #2022-49 12th Dec 2022 twitter domains geolocation zotero The last episode of 2022, with a few nice tips and tools, and a little rant over the shift within the Twitter atmosphere. Last week the Twitter account of Sarah Womer (UnleashedOSINT) went offline. The reason? She was pointing out right-winged accounts and companies active on Twitter, promoting their business. It seems that a mass report followed, and her account was permanently suspended. Then there's also the story of why three members of the Twitter Trust and Safety Council quit . Does free speech on Twitter means that more hateful accounts are being reinstated ? Is this the end of Twitter as we knew it? I personally think so. But on the other hand, this will become the largest platform to keep track of, when looking at extremists. And the good thing is, we have had years of practice when it comes to OSINT. So it will be more than easy to find whatever we need on there! Anyway, that is enough ranting in this last episode of 2022. Earlier this year I tried to come up with another end-of-the-year OSINT quiz, but I simply haven't had the time to finish one. So for the next few weeks, I will be checking out some interesting content on Mastodon (you can find me here by the way), or I will be very busy relaxing and enjoying the holidays! Zotero Azure's AADInternals Geolocating With the Stars Locked Twitter Accounts Tool: Zotero Over on Mastodon Bashinho shared a tip about Zotero. This program is for saving and annotating information, and has a browser plugin for Firefox and Chrome. With a simple click of a button you can save pages, make notes, and save them offline. This way you can build a collection of locally stored web pages and quickly search through them. In his German video he also shows the export function, where he shows how to save a list of found resources to a CSV file. Thanks for this tip! Saving pages with Zotero Link: https://www.zotero.org Tutorial: Azure's AADInternals Steven 'Nixintel' Harris wrote a blog post about the 'AADInternals' tool, that was created by Dr. Nestori Syynimaa . The tool is used to administering Azure AD and Office 365, but for there is also an online tool to get a first glance at domains that are administered by a company. By simply searching on a domain name of interest, you can check whether they use Azure AD for their domains, which domains are managed or federated and what STS (Security Token Service) they use. From there, you can pivot for more information. Only the first 20 results are shown, but if you want to know more, then do install the AADInternals and run it directly within Powershell. Checking out some random bird site Blog: https://nixintel.info/osint-tools/... Link: https://aadinternals.com/osint Tutorial: Geolocating With the Stars John McElhone spent some time looking at a photo of a new B-21 Raider, and came up with a nice idea. He wanted to try and find the location where the photo was taken, by looking at the constellations that are visible in the photo. By using Astrometry.net and Stellarium , and armed with some EXIF information, he managed to find and confirm the location where the photo was taken. The end result of John's geolocation job, and the original photo Link: Twitter thread Media: Locked Twitter Accounts Sinwindie shared a nice tip on how you can still get some more insight into a locked Twitter account. By looking who is interacting with the account, or checking out archived or cached pages of a previously opened account, it is still possible to find more info. One extra tip: Within Google it is also possible to check the actual cache. It's a bit more hidden nowadays, but can be found by opening the little 'kebab menu' (the three vertical dots) and look for the option 'Cached'. Link: https://youtu.be/-YPuJqvae0c FUNINT: Google Review Zewen shared this tweet over on Discord. It's a 'golden oldie', but... This is just another great example of using open sources to solve a crime Have a great holiday season and see you in 2023! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/5/7/1/2/2/57122a49960d536821dea3d4bb3027af45279d9f-2249-geolocation.jpg","https://sector035.nl/user/pages/articles/2022-49/2249-aadinternals.jpg","https://sector035.nl/user/pages/articles/2022-49/2249-funint.jpg","https://sector035.nl/user/pages/articles/2022-49/2249-zotero.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_51d0100fef63_0.jpg","blog_data/images/blog_51d0100fef63_1.jpg","blog_data/images/blog_51d0100fef63_2.jpg","blog_data/images/blog_51d0100fef63_3.jpg","blog_data/images/blog_51d0100fef63_4.bin","blog_data/images/blog_51d0100fef63_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2023-12","title":"","status":"ok","retrieved_at":"2026-08-29T16:21:17.494327+08:00","text":"Week in OSINT #2023-12 | Sector035 Week in OSINT #2023-12 Home Week in OSINT Articles Search Week in OSINT #2023-12 27th Mar 2023 geolocation tool overpass turbo ai chatgpt This episode turned into a geolocation and OverPass special, with a little extra topping of OpenAI's GPT! Geolocation is a very important part of the OSINT landscape, and besides manual investigations, there are also tools that can help you. One of the most helpful tools, is OverPass Turbo. By querying the OpenStreetMaps API, it is possible to find locations in any location of the world. But the query language isn't really easy to master for me, but luckily there are some things that will help, as can be read in this episode of Week in OSINT! Finding Sherlock OverPass and GPT More OverPass and GPT Learning OverPass Poastal Media: Finding Sherlock Gary Ruddell is a cybersecurity professional from Schotland, and has posted a few OSINT based videos on YouTube. His latest video is about Sherlock, and I don't mean the video where he talks about the username tool . I mean the American series Elementary, the modern take on Sherlock Holmes. He shares his thought process while geolocating the rooftop of a video production company that is used a few times in this series. Great video if you want to learn a bit more about this subject, and also a good training idea to use tv-series or movies to practice your skills. Link: https://youtu.be/VzUDFM3K4Sk Tip: OverPass and GPT The latest version of Chat GPT-4 has been dominating the news lately, and I also have been playing with GPT-4, as well as the Bing Chat. But John Wiseman found something really neat, and that is the use of GPT-4 to create useful OverPass Turbo queries. Just like him, I'm also not great at writing queries, so every bit of help is useful in this case. So if you have access to GPT-4, do give this a try! I did find out that with more complex queries, it had some issues filtering the correct 'amenities' though, but since the AI is constantly improving, and it is possible to edit the query, this isn't a huge issue. Using ChatGPT to find locations in OSM Link: Twitter thread Tool: More OverPass and GPT Yes, there is even more to come. Because how would you like to connect GPT-3 to a custom web-app, that focusses on OverPass Turbo queries only? Well, Ben Strong did just that! He wrote a small Python script that queries the GPT-3 model, adds a fact or joke, and displays the result of the query on a small map. Sadly enough, my paid API trial finished end of last year, and I haven't connected any payment options, so I haven't tested it myself yet. But if you do have a paid account, and you are willing to dive into this, have a good understanding of how to install and configure it, then this is a great opportunity to play a bit more with OverPass! Asking GPT-3 for Indian restaurants near Hereford Link: https://github.com/earth-genome/ChatGeoPT Blog: https://link.medium.com/rm0nVEvAtyb Tutorial: Learning OverPass This project is 8 years old, and they could really use some help with the creation of new lessons. Would you like to help out? Then make sure to check out their GitHub repo ! Do you want to know more about OverPass Turbo? Well, there is an older interactive tutorial, where you can learn how to write some basic queries. I have followed it, and I found it does require careful reading, and some basic knowledge about the query language will absolutely help. But it is absolutely something I suggest you check out if you want to learn some basics of the OverPass query language. Besides an interactive tutorial, they also have useful documentation with lots of examples. Link: Tutorial Link: Documentation Tool: Poastal Jake Creps has been busy going over all kinds of platforms, to check API responses. He started writing a little tool that will be able to tell you whether an email address is already registered for a certain platform or not. I was lucky enough to have a sneak peak over the weekend, so I could try it out, and it works as intended. The code is very rough, there are false negatives, and can absolutely be improved, but I really like the idea! Checking registered emails on sites and platforms Link (when it goes public later on): https://github.com/jakecreps/poastal FUNINT: OpSec and Cake Jordan Wildon , the maker of Telepathy, shared his moment of embarrassment when it comes to OpSec. Well played Nick, well played... Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/user/pages/articles/2023-12/2312-learnoverpass.jpg?classes-caption=1","https://sector035.nl/user/pages/articles/2023-12/2312-opsec.jpg","https://sector035.nl/user/pages/articles/2023-12/2312-overpass-ai.jpg","https://sector035.nl/user/pages/articles/2023-12/2312-overpass.jpg","https://sector035.nl/user/pages/articles/2023-12/2312-poastal.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_54bf39ddea87_0.jpg","blog_data/images/blog_54bf39ddea87_1.jpg","blog_data/images/blog_54bf39ddea87_2.jpg","blog_data/images/blog_54bf39ddea87_3.jpg","blog_data/images/blog_54bf39ddea87_4.jpg","blog_data/images/blog_54bf39ddea87_5.bin","blog_data/images/blog_54bf39ddea87_6.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2023-17","title":"","status":"ok","retrieved_at":"2026-08-29T16:20:55.794656+08:00","text":"Week in OSINT #2023-17 | Sector035 Week in OSINT #2023-17 Home Week in OSINT Articles Search Week in OSINT #2023-17 1st May 2023 twitter geolocation privacy opsec social media virtual machine security After a week off, I'm back with several topics ranging from geolocation, Tweetdeck, a streaming platform and some OpSec tips. Two weeks ago I knew my week was fully planned, so there wouldn't be time to publish an episode, so I chose to take some time off. For this week, I have some cool topics to talk about, but one thing I do urge you to read, is the first section about Atlas OS. Because no matter what reason someone has to create and run a virtual machine, there are things one should avoid at all cost, like a complete lack of security! Atlas OS Geolocation Tweetdeck Kick Identity Protection Tip: Atlas OS Last week I was going over some tweets by Daniel Card, aka mRr3b00t , about a new, stripped down Windows environment called 'Atlas OS'. Even Linus Tech Tips posted a video about this on their YouTube channel. I know for a fact that within the OSINT community there are people that use a slimmed down version of an OS for virtual machines, but I wanted to post a strong warning here. Don't simply download an OS, configuration script, or even a pre-built image if it is not downloaded from the website of the original maker of the OS. Yes, there are some pre-built environments that have been shared by me before, like Tsurugi , which can be called an exception. But in this case, Atlas OS removes all security features that makes Windows safe to use, like Windows Defender and security updates! Don't... Please, just don't! Do you want to investigate adversaries and visit all kinds of shady websites, without any form of protection? With the only plus side of sparing some seconds while clicking through some sites? The AtlasOS team has responded on Twitter that they will show a warning about disabling these featured in an upcoming release. Let me end this section with a general tip from me, and probably the rest of the InfoSec community: If you don't know what you're doing, better not do it at all! Article: Geolocation Steven 'Nixintel' Harris posted another geolocation tutorial earlier this month. He talks about a challenge that was posted by Conor Nolan on January this year. In the article he explains how he used small details in an image to generate enough clues to find the correct location. Again this shows the importance of going over the fine details of an image when being tasked to geolocate it, and Steven again takes us along his thought process when dealing with these tasks. Thanks again for the great explanation! Searching for Maxi Zoo stores in the UK Link: https://nixintel.info/osint/... Tutorial: Tweetdeck Sofia Santos wrote an article on Tweetdeck, and has updated it to reflect the most recent changes. This post goes over how Tweetdeck is used to create columns with searches, profiles and lists to keep tabs on a specific topic. This is a wonderful tutorial for everyone that hasn't used Tweetdeck yet. And with Twitter slowly becoming an uncensored, unregulated, right-winged platform, the importance of monitoring this platform might be more important than ever. And while tweeting her updated blog post, she also shared a cheat sheet by Zilvinas Kucinskas , that lists all search operators for Twitter. Step-by-step tutorial on how to fill Tweetdeck Tutorial: https://gralhix.com/2022/... Cheat sheet: https://www.exportdata.io/blog/... Tip: Kick Kick is an alternative streaming platform, and I heard about it last week after it was mentioned by the OSINT community over at Kase Discord . And while checking the resources using the 'developer toolbar', I found some interesting URLs that can be queried without being logged in. Sadly enough, I haven't managed to get it working with cURL, since they seem to check whether JavaScript is running. https://kick.com/api/v1/users/{username} This API endpoint on a user, gives basic information on the username, which is also visible on the page itself. One extra thing that is mentioned is the numerical user ID, and a link to the profile image. https://kick.com/api/v1/channels/{username} The v1 of the channel endpoint, gives the most information. Most noteworthy are the following fields, that aren't visible by simply browsing there: Entity Information name_updated_at Date and time when the channel name was changed banner_image URL of the banner that is used user It contains the field email_verified_at , with a date and time of email verification chatroom Information on when the chatroom was created and updated previous_livestreams Overview of the last live streams, including a dates and times of the stream, publication and the last update verified The channel ID, creation date and the last update of the verification status There is also a v2 of the API, that can be found at: https://kick.com/api/v2/channels/{username} It has mostly the same information as the v1 endpoint, but is a lot more slimmed down and lacks information on a few things, like the overview of previous streams. There are more API endpoints, but most of the information can be seen in the browser itself. But if you do find more interesting information, do share them with the community! Tutorial: Identity Protection Earlier this month the 'Special Operations Command' of the US Army released their updated 'digital identity protection toolkit'. This extensive guide is full of tips and hints on how to protect your identity online. On their website you can download the full 160-page PDF-file, or you can download the general sections separately. They also have so-called 'smart cards', with information on the most common social media platforms, fitness apps, and other websites. This resource is an absolute must if you are looking to protect your online identity, or need to tighten your OpSec! OpSec tips per category or platform Link: https://www.soc.mil/IdM/publications/IdMpubs.html Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/4/6/7/e/c/467ec55372793e00d4d4f65e1e74a75f82a5c00d-2317-nixintel.jpg","https://sector035.nl/user/pages/articles/2023-17/2317-atlasos.jpg","https://sector035.nl/user/pages/articles/2023-17/2317-opsec.jpg","https://sector035.nl/user/pages/articles/2023-17/2317-tweetdeck.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_da87fa33c3e4_0.jpg","blog_data/images/blog_da87fa33c3e4_1.jpg","blog_data/images/blog_da87fa33c3e4_2.jpg","blog_data/images/blog_da87fa33c3e4_3.jpg","blog_data/images/blog_da87fa33c3e4_4.bin","blog_data/images/blog_da87fa33c3e4_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2023-19","title":"","status":"ok","retrieved_at":"2026-08-29T16:20:22.586715+08:00","text":"Week in OSINT #2023-19 | Sector035 Week in OSINT #2023-19 Home Week in OSINT Articles Search Week in OSINT #2023-19 15th May 2023 twitter geolocation google search engine telegram factchecking ai fake news Another packed episode, with topics ranging from fake news, to Telegram, and an old Chrome extension! So much to talk about, and not everything made it into this week's episode, because I was a bit busy over the weekend. But I did manage to read a lot, and play with the Google Unlocked extension, and I am still happy that I'm able to write this Week in OSINT for close to five years, and keep on top of the OSINT news while doing it! Let's crack on, with the following topics: Inactive Twitter Accounts AI and Geolocation Telegram VM Fake Protesters New TLD Google Unlocked Tip: Inactive Twitter Accounts Let's start with a warning about the new inactive account policy that was published on April 24 this year. The previous policy was published on September 13, 2019 and mentioned an inactive period of 6 months . I know from personal experience that Twitter didn't really act on this policy, since I still have a dormant account for a quiz out there. But if they are changing this policy, and are going to act on it, this might become a problem. Just think about investigators that actually hold dozens of accounts, and want to plan a long holiday... Twitter's new policy on inactive accounts Tip: AI and Geolocation Henk van Ess shared some tips on how AI can be useful during investigative work. In this article he talks about generating lists of addresses, or coordinates. But what I found most interesting myself, is the last part of the post where Henk uses AI to find an address. By giving only partially available information, such platforms can easily return possible hits. At last, this is a use of ChatGPT for OSINT, that I think is absolutely great. Filling in the blanks, with AI! especially when one need to fill in the 'blanks'! Link: https://www.digitaldigging.org/... Tutorial: Telegram VM Ginger T has posted a first part of a tutorial, where he describes how he built his Telegram VM. He takes the time to explain his language and VPN setup, why he uses containers in Firefox, and talks about his OpSec. He also talks in length about different settings in his browser, and the add-ons he uses in his VM. This is a wonderful tutorial for people that are new to setting up a VM, and I can't wait to read the second part! The containers within Ginger T's VM Link: https://www.cqcore.uk/... Article: Fake Protesters Over the last few weeks journalists have uncovered a form of \"fake news\" I didn't see before. By sending people to genuine protests, but having them hold up signs that show pro-Russia and other messages, people were trying to be tricked into believing a different narrative. The photos that were taken of these 'protesters', had to make people believe there was more support than really was the case. An interesting investigation, and Twitter thread , by Kevin Shakir and his colleagues from the Danish DR Nyheder , Le Monde , Süddeutsche Zeitung , Westdeutscher Rundfunk , Norddeutscher Rundfunk , Expressen , NRK and SVT . Fake protesters uncovered Article (DK): https://www.dr.dk/nyheder/... Link: Twitter thread Tip: New TLD Back in 2014 ICANN delegated a new TLD to their root servers, the top level domain .zip . Recently it became possible to register a domain name ending with this TLD, and many people did. This created quite an uproar in the InfoSec community, and I can understand why! When I looked into some of the most recent domain registrations, I found domains that could pose as legitimate programs of files. On May 12, the amount of registrations took a small leap, followed by an explosion of registrations on the May 14! Registrations of ZIP domain names To give an example of the cesspool of domain names that were registered, I had a look at some very misleading domain names. All of these can easily be mistaken for a genuine file name: Date Domain 6 April tumblr.zip, audible.zip 19 April facebook.zip, whatsapp.zip 20 April waze.zip, chromium.zip 12 May attachments.zip, document.zip 13 May vacationphotos.zip, windowsdrivers.zip 14 May office-update.zip, windowsupdate.zip 15 may attachement.zip, bankstatements.zip You want to keep an eye out for newly registered domains yourself? Or want to search for domains that might impersonate specific brands? Then do check out one of the best free sources our there, called DN Pedia. There you can see that on May 14, almost 2300 domain names were registered with this top level domain. Link: https://dnpedia.com/ Tool: Google Unlocked I received a tip about a new browser extension, called Google Unlocked. With this extension installed in Chrome or Firefox, it will be possible to see hidden, or removed, results directly in your browser. It works by looking for a response that contains a link to the Lumen Database on the bottom of the search page. The extension opens that page, and extracts all URL listed there, and places them on the bottom of the search results. Thanks for the share Exalt Before After ↔ Link: https://github.com/Ibit-to/google-unlocked Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/7/1/e/9/9/71e991451f55723bf2131062c7ba6ac88e795a74-2319-google-unlocked-before.jpg","https://sector035.nl/images/9/3/6/9/5/9369559b760edcc1022110de236e4a70e18e6fc6-2319-google-unlocked-after.jpg","https://sector035.nl/user/pages/articles/2023-19/2319-chatgpt.jpg","https://sector035.nl/user/pages/articles/2023-19/2319-fake-protesters.jpg","https://sector035.nl/user/pages/articles/2023-19/2319-telegram-vm.jpg","https://sector035.nl/user/pages/articles/2023-19/2319-twitter.jpg","https://sector035.nl/user/pages/articles/2023-19/2319-zip-tld.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_7d949ff5d26d_0.jpg","blog_data/images/blog_7d949ff5d26d_1.jpg","blog_data/images/blog_7d949ff5d26d_2.jpg","blog_data/images/blog_7d949ff5d26d_3.jpg","blog_data/images/blog_7d949ff5d26d_4.jpg","blog_data/images/blog_7d949ff5d26d_5.jpg","blog_data/images/blog_7d949ff5d26d_6.jpg","blog_data/images/blog_7d949ff5d26d_7.bin","blog_data/images/blog_7d949ff5d26d_8.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2023-25","title":"","status":"ok","retrieved_at":"2026-08-29T16:16:42.177146+08:00","text":"Week in OSINT #2023-25 | Sector035 Week in OSINT #2023-25 Home Week in OSINT Articles Search Week in OSINT #2023-25 26th Jun 2023 maps twitter geolocation telegram armed conflicts This episode turned out completely different from expected, but I have no doubt that I gathered some interesting tips. Initially I planned to write my episode on Friday evening and Saturday morning, but due to the developments in Russia I had other priorities. Despite the fact I am not always following politics, conflict areas, or global affairs, I simply had to keep an eye out for the latest news. That also meant I only had a Sunday to find some extra items, read articles, test tools and whatever is needed to fill a Week in OSINT. And then It struck me: I can simply write about the easy to use, and free tools, that I used to try and stay on top of everything. But since I usually only do OSINT investigations, and monitoring is not my daily work, I had to come up with something that was easy, and quick to set up. So here we are, half of the usual Week in OSINT, and a collection of tips and tricks, to get free monitoring up and running in no-time: Geolocating MwOsint German Street View LiveUAMap Telegram to RSS Feed Informer Twitter Monitoring Article: Geolocating MwOsint Twitter user Daan2k21 has caught the bug of geolocating, and created two write-ups on Medium at this point. One of those I really wanted to share in here, and he describes in detail how hw located MwOsint , and how he found the exact time the photo was posted. A well written, clear step-by-step guide with some good tips and sources. Thank you for sharing this! Geolocating in the Alps Link: https://link.medium.com/Kd6n4K6cRAb News: German Street View On June 8 it was announced in ' The Keynote Germany ', that from June 22 on the Google Street View cars would be roaming the street of Germany once more. When Google started capturing 360° images in Germany, the citizens were outraged about a breach of their privacy, and demanded to have their houses blurred. The amount of blurring would take so much effort, that Google decided it would not update their images from that moment on. Now, about 13 years later, there are several 'street view' providers, and Google decided it is worth another shot. Soon Google will join Apple in providing 360° images once again Link: https://9to5google.com/2023/06/09/google-street-view-germany/ Because of the situation in Russia with the Wagner group marching towards Moscow, I was monitoring the situation as it unfolded. That also meant there was less time to fill this episode. But that also gave me the idea to share the free tools I used to get some very basic monitoring up and running, mostly to feed my personal curiosity. So let's dive into what I used to keep tabs on the news. Site: LiveUAMap One of the sites out there, that are constantly monitoring situations in the world is of course the Live UA Map. This service is constantly scraping and pulling in data, processing it, and will plot specific events that have a specific location, on the map. This has been an important tool for a lot of people already since 2014, and this was one of the first things I opened. Important events, mapped out for your convenience Link: https://russia.liveuamap.com Tip: Telegram to RSS But since I was not completely happy running LiveUAMap alone, because not all messages I want to check have a location, and thus not always show up there. I could have manually checked a bunch of Telegram channels, but why do that if you can automate it using an RSS feed? The first thing I needed to do, was to create several feeds for the Telegram channels I was interested in. For that, I used a service of 'RSSHub' and I didn't even need an account. Any Telegram channel, that has the 'web preview' function available can be added. That means, it is possible to view the channel with a URL that starts with: https://t.me/s/ After this, you take the channel name, and add it to the RSSHub url that will convert it to an RSS feed for further processing. For instance with the Moscowmap channel: https://rsshub.app/telegram/channel/moscowmap Site: Feed Informer After I collected a bunch of Telegram channels, I could have added them all to an RSS feed, and leave it at that. But I wanted to be able to read it in English, since I don't read Cyrillic, so I wanted to have the messages translated using the bilt-in Chrome translator. So I jumped over to Feed Informer, and added the Telegram feeds with the tip mentioned above, to one single feed. Building one stream of RSS items I then exported this feed to HTML code, so I was able to host it somewhere out there, but you can also directly open the HTML page that Feed Informer creates. I wanted to automate things even more, so I added a 1-minute refresh to the page, and near-live updates of the latest 50 messages would be shown in my browser. Hosted RSS feed with the latest news Link: http://feed.informer.com Tip: Twitter Monitoring Of course the monitoring wouldn't be complete just using the LiveUAMap and Telegram channels alone. Lots of information was published on Twitter, including geolocations and verifications, so I also wanted to monitor that. And there are two main ways to do this, and I used both for this. First, there is the 'Twitter List' function, where you are able to add accounts to a 'list'. You can then open just that one list with messages from only those accounts. Second, there is of course the wonderful TweetDeck. You can add the Twitter list to that, but you are also able to create custom search queries, so that you are able to group different topics in different columns. Using TweetDeck for monitoring Twitter Tip: Final Thoughts Since I was the only one checking these sources, there was a limit to the amount of messages I was able to read and process. So by picking Telegram channels that were at the time most important to the situation, and Twitter accounts that had a solid reputation and provided information that was published later in reputable news sources, I collected about 20 to 25 accounts in total to monitor. This provided me with a steady stream of messages that was possible for me to digest, and not overwhelm me. Did I maybe miss some smaller events that happened? Probably. But with several Twitter accounts, and different official and non-official Telegram channels, I had a wide spread of news messages coming in. With events like this, it is very easy to quickly set up some type of monitoring. When you have your sources picked, you can have a steady stream of news coming in within mere minutes. You can check all these sources by hand, spending time switching back and forth. You may even be reading the same messages twice if you are not paying attention. But in this way, you are able to keep things coming in nice and clean, with only a browser opened on TweetDeck and a custom RSS feed. FUNINT: This Week's Meme I usually refrain from any political news, or touch on recent events, because I want to focus on sharing tools, tips and tricks. But after spending a Friday night and a full Saturday watching the news unfold, I simply couldn't resist... Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/1/3/b/d/5/13bd576a96231bb307e561a85f419cf0467f9598-2325-apple-maps.jpg","https://sector035.nl/user/pages/articles/2023-25/2325-daan2k.jpg","https://sector035.nl/user/pages/articles/2023-25/2325-feedinformer.jpg","https://sector035.nl/user/pages/articles/2023-25/2325-feedinformer2.jpg","https://sector035.nl/user/pages/articles/2023-25/2325-liveuamap.jpg","https://sector035.nl/user/pages/articles/2023-25/2325-meme.jpg","https://sector035.nl/user/pages/articles/2023-25/2325-tweetdeck.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_e01844337911_0.jpg","blog_data/images/blog_e01844337911_1.jpg","blog_data/images/blog_e01844337911_2.jpg","blog_data/images/blog_e01844337911_3.jpg","blog_data/images/blog_e01844337911_4.jpg","blog_data/images/blog_e01844337911_5.jpg","blog_data/images/blog_e01844337911_6.jpg","blog_data/images/blog_e01844337911_7.bin","blog_data/images/blog_e01844337911_8.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2023-28","title":"","status":"ok","retrieved_at":"2026-08-29T16:16:11.700841+08:00","text":"Week in OSINT #2023-28 | Sector035 Week in OSINT #2023-28 Home Week in OSINT Articles Search Week in OSINT #2023-28 17th Jul 2023 twitter google search engine geolocation tool analytics overpass turbo Welcome to another Week in OSINT, with some insights into Twitter, a nifty Google trick, an OverPass Turbo tool, and other news. This Monday I have another small update from my side, due to lots of work. I wish I had the time to write longer updates, but maybe it isn't so bad to keep these short. Else all my readers would only be playing with new tools and tricks the whole week, and never be able to have any work done! Anyway, I did manage to dig up a few interesting things I read last week: More on Twitter Google Site Operator GeoPincer Google Analytics 4 Uniform Timezone News: More on Twitter Another blow for researchers that are monitoring Twitter users. Since some time ago there have been some serious issues with the platform. It has been extremely unstable for some period last week. New tweets weren't loading, and I received error messages when I wanted to view a specific tweet. Last week it was even impossible for some time to search on specific tweets with a basic search like: to:sector035 . This has been going on since Musk fired loads of engineers, and it might even get worse in the future. Besides the issues that are the direct result of a lack of engineers, there are also changes that make the platform unusable for researchers. First, there is the issue of rate limiting that stops you from seeing anything more than a few hundred tweets a day. Another issue that I noticed on Sunday, July 9, was that it seemed to be impossible to retrieve a full list of followers or followed accounts. The list only loaded the first few dozen accounts, and then stopped. Was this limited too? Or was this another 'temporary' issue? We actually might never know. Issues in the Twittersphere A third issue that was mentioned early July, was the rumour that Twitter stopped Google indexing its content. This is actually not true, and it is believed that it might be due to the rate limiting that Google temporarily showed less information. Luckily, Twitter made some changes and things are looking better at the moment, since the most recent tweets are available again in Google ! That also opens up the door for some very basic monitoring, without being logged in. Only a handful of tweets are shown, but it is possible to view the latest content of an account, by setting the User-Agent to a Google bot. Viewing Twitter content anonymously Other positive news is that both Archive.today and the Internet Archive , are able to archive single tweets or profiles. For some time, that was also unavailable , but that is also back! Twitter is still an important resource when it comes to alt-right movements, fake news spreaders, and troll farms. And since the big lay-off over at Twitter, things have been increasingly unstable. Some things seem to have been resolved, other issues require some workaround, but it seems that it will never return to what it was. Make the best of it, and keep on digging! (until you are rate limited, of course...) Tip: Google Site Operator I was having some issues last week with the site: operator in Google, but only when I was logged. No clue what was wrong, but it has actually been solved, and everything works again. But during my searches, I saw a message over on Mastodon by Alex Ștefănescu ( / ), a developer over at OCCRP . Searching specific Facebook profiles This simple Google search can be used to find specific content in a Facebook about section of a profile. Really nice tip from Henk van Ess here, thank you for sharing this! Link: https://gijn.org/2023/06/26/... Tool: GeoPincer One of the handy tools one can use during geolocation, is OverPass Turbo. The query language is not the easiest to learn, but once you get the hang of it, it is really powerful! The Reddit user tholo2k has created a nifty Python script that will query a location, and give a list of specific named 'amenities' that are within a given distance from each other. An awesome little tool, easy to use, and might help a lot of people looking for a specific location. Overpass Turbo just got easy! I did receive an error message when I ran it the first time though. So if you are hitting a wall, maybe try and upgrade the urllib3 and requests . This worked for me: python -m pip install -U urllib3 requests Link: https://github.com/tloja/GeoPincer Article: Google Analytics 4 Google Analytics as we know it, is no longer... Of course, there are still a lot of websites that haven't transitioned to the new 'GA4', and you can still find connections using the already known tools. And a legacy UA-ID is still possible, according to Google. But the new analytics, or 'Google Tags', are quite confusing. In this article by Craig Silverman ( / ), everything you need to know, including some tips for future investigations. One thing that doesn't change, is de-anonymising dedicated servers by searching for specific analytics codes Searching for the GTM-tag over at BuiltWith Link: https://digitalinvestigations.substack.com/... Tool: Uniform Timezone Bellingcat created a new browser extension for Chrome, called 'Uniform Timezone'. After installing, and reloading a Twitter of TikTok page, you can hover over any time mentioned on that page. It will then tell you the time in different formats in a small floating information box. A simple click on any of the values will copy that value to the clipboard, and you can also set a custom time zone if you have a need for that. Wonderful, and simple, tool for Chrome that surely will come in handy! Thanks swedishmike for sharing that! Chrome extension in action Link: https://github.com/bellingcat/uniform-timezone Link: Chrome extension FUNINT: This Week's Meme This week, I focus again on Twitter, the ongoing changes and stability of the platform. This platform just keeps on giving! PS: I think that it's about time that Chad Warner adds \"FUNINT\" to his list of disciplines too: Funny intelligence. Involves gathering enough data on the current landscape of OSINT, its process, or the tools used, to make fun of it. Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/a/3/1/6/9/a316935ccdfb4610948db4c2c8758dcd0603b226-2328-geopincer.jpg","https://sector035.nl/user/pages/articles/2023-28/2328-funint.jpg","https://sector035.nl/user/pages/articles/2023-28/2328-google-site.jpg","https://sector035.nl/user/pages/articles/2023-28/2328-nyt-ga4.jpg","https://sector035.nl/user/pages/articles/2023-28/2328-twitter-anon.jpg","https://sector035.nl/user/pages/articles/2023-28/2328-twitter-followers.jpg","https://sector035.nl/user/pages/articles/2023-28/2328-uniform-time.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_92e0fda8fc06_0.jpg","blog_data/images/blog_92e0fda8fc06_1.jpg","blog_data/images/blog_92e0fda8fc06_2.jpg","blog_data/images/blog_92e0fda8fc06_3.jpg","blog_data/images/blog_92e0fda8fc06_4.jpg","blog_data/images/blog_92e0fda8fc06_5.jpg","blog_data/images/blog_92e0fda8fc06_6.jpg","blog_data/images/blog_92e0fda8fc06_7.bin","blog_data/images/blog_92e0fda8fc06_8.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2023-49","title":"","status":"ok","retrieved_at":"2026-08-29T16:15:48.283203+08:00","text":"Week in OSINT #2023-49 | Sector035 Week in OSINT #2023-49 Home Week in OSINT Articles Search Week in OSINT #2023-49 11th Dec 2023 maps geolocation podcast tutorial ctf tool training Another week, another episode with podcasts, people, tutorials and training! This weekend was a bit more busy than I anticipated, so I didn't have enough time to finish this week's episode in time. But I still wanted to publish it, since I found some interesting things last week I really wanted to share. So today it didn't appear on 8AM Central European Time, as usual, but slightly later. Without further ado, I present to you this week's topics: Goodbye Podcast Sourcing Games Craig Silverman PeakVisor Sitemaps News: Goodbye Podcast In the paragraph below, I wrote that the podcast came to an end. Someone did point out, rightly so, that it needs some extra nuance. I quote: \" I would never say the podcast will not return, as I get bored easily. I will say that it is on an indefinite \"hiatus”. Maybe it will become something completely different. Stay tuned and stay subscribed. \" It has been a few months ago already, but I do want to start this week with a personal thank you to Michael Bazzell [ ]. Over the years, he has created hundreds of episodes of his 'Privacy, Security, and OSINT Show', but it has come to an end last month. Thank you so much for sharing all your knowledge and insight with the community. For the hours of listening pleasure, the tips and privacy tools you use. And even though you don't see the point of having an eternal archive, I secretly hope that one day you will find a good solution to host all the episodes again. Farewell to an amazing podcast Link: https://inteltechniques.com/blog/... Training: Sourcing Games If you have some time off during the upcoming holiday season, for whatever reason, this is the thing for you! Several weeks ago, Jan Tegze [ ] shared three (!) new levels over on 'Sourcing games'. I love such games, because the techniques needed to answer the questions, have real-world applications. Thank you, Jan, for the constant updates! Diving into #39 Link: https://sourcing.games/game-39 Link: https://sourcing.games/game-40 Link: https://sourcing.games/game-41 Media: Craig Silverman Craig Silverman [ ] was invited by the NeedleStack [ ] crew to talk about investigative journalism, disinformation on social media, open source intelligence and more! And if you haven't subscribed to this podcast yet, I do suggest you do so right away Craig Silverman on NeedleStack Podcast: https://pod.link/1600516532/episode/... YouTube: https://www.youtube.com/watch?v=Oa_Uea810-0 Tutorial: PeakVisor Sophie Tedling [ ], tech fellow at Bellingcat [ ], created a two-part series on PeakVisor, one of the best mountaineering tools out there. The online tool enables you to view what hills and mountains look like, from any point on earth. In this series, she explains exactly how it works, how to use it, and how it compares to Google Earth's 3D view. First part of PeakVisor for OSINV YouTube: Part 1 YouTube: Part 2 Tutorial: Sitemaps Cyb_detective [ ] has been busy lately, downloading my site content. The reason for that is, to write a tutorial about how to create sitemaps, and download every single link from a website. In the tutorial a small Python script is shown that will generate a list of links. Besides that, other tools are mentioned too, to scrape websites for further analysis. Scraping links with Python Link: https://publication.osintambition.org/... FUNINT: This Week's Meme Thank you for all the years you have created your podcast! The community truly respects all the work you've put in, and we wish you all the best with your future plans. Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/e/3/8/4/c/e384ccfba00f8652a271f9b8ac552b91df8c637c-2349-sitemaps.jpg","https://sector035.nl/user/pages/articles/2023-49/2349-bazzell-podcast.jpg","https://sector035.nl/user/pages/articles/2023-49/2349-meme-bazzell.jpg","https://sector035.nl/user/pages/articles/2023-49/2349-sourcing-games.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_a9433beb4445_0.jpg","blog_data/images/blog_a9433beb4445_1.jpg","blog_data/images/blog_a9433beb4445_2.jpg","blog_data/images/blog_a9433beb4445_3.jpg","blog_data/images/blog_a9433beb4445_4.bin","blog_data/images/blog_a9433beb4445_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2024-22","title":"","status":"ok","retrieved_at":"2026-08-29T16:15:29.655721+08:00","text":"Week in OSINT #2024-22 | Sector035 Week in OSINT #2024-22 Home Week in OSINT Articles Search Week in OSINT #2024-22 3rd Jun 2024 google geolocation extension training interview Besides the usual interview, exercise and geolocation article, I need to address an important situation regarding the future of Chrome extensions This week a major part of this episode has to do with an important change that is coming up, the phase-out of older extensions, due to major changes within the Chromium based browsers. I have taken it upon myself to start creating a list of extensions that might stop working once this change is pushed, and a link to that list can be found here . Overview Sofia Santos' #27 Hunted's Hickman Geolocating a Gang Leader Phase-out of Manifest V2 Training: Sofia Santos' #27 Sofia Santos [ ] created yet another OSINT exercise, and it is number 27 already! This one is for the beginners within the field of open source investigations, and can be solved rather easily with the right searches. What I love about these exercises, is that she mentions how difficult the questions are for beginners, and for seasoned investigators. And to check your findings, she also posts a 'walkthrough' on YouTube right away, explaining how it can be solved. This way you learn how the thought process within open source investigations work, and can learn how to pivot from one finding to another. From easy to hard, something for everyone Link: https://gralhix.com/osint-exercise-027/ Media: Hunted's Hickman The show Hunted has been running for several years in the UK and other countries. Even though a lot of the techniques used are sped up for the show, all required legal paperwork is removed, and based on the Dutch episodes I saw some years ago, legal warrants are given fairly easily. But still, a lot of the techniques portrayed in the show are real. In that way, it does give a good insight in how law enforcement, or investigative bureaus work. In this interview, Daisy Hickman [ ] is being interviewed on Baker's Chatcast about her career, and her experiences in Hunted. Talking Hunted, and touching on OSINT within the show Link: https://www.youtube.com/watch?v=nups_uNcx6Y Article: Geolocating a Gang Leader Benjamin Strick [ ] has been scrutinizing a CCN interview with a Haitian gang leader, and has been able to find the exact location where the interview took place. Even though the location might have been known by law enforcement already, the article shows how he worked, step-by-step, to find the actual house. And since Haiti doesn't have street view, nor does it have a lot of third party captured imagery, most will have to be done via satellite imagery. Another great example how geolocation of video or images can be done, with some basic tools, and enough perseverance. Drawing by Ben, after scrutinizing the video Link: https://link.medium.com/OQvjy7na4Jb News: Phase-out of Manifest V2 An important change within Chromium based browsers is about to start very soon, the phase-out of the so-called \"Manifest V2\" extensions. A manifest is a framework for extensions, and has been in use for many years already, despite some security issues that could occur due to its nature. The V3 is already active, and is in use by a lot of extensions already, but this might change very soon. One of the biggest changes could be that ad-blockers won't be as effective, due to the fact that updates in the list of domains will go through the Chrome web store, and have to be approved first, while it now is done by the extension itself in the background, sometimes several times a day. But there are also other Examples of Chromium based extensions that still use Manifest 2, and that I have installed myself, are: GHunt Companion JSON Viewer Map Switcher OldTweetdeck Tampermonkey uBlock Origin User-Agent Switcher and Manager As you can see, there are some well known extensions on that list, and it is very well possible that certain extensions will stop working all together in the near future. This means that new extensions will have to be developed, workarounds need to be found, or maybe even switch to a different browser. One possibility is to test out Thorium . There has been requests to keep the support for Manifest V2 for several years within the Thorium community, and the developer has mentioned more than once he will do his best to delay the phase-out as long as possible, until the code is fully removed from Chromium. Brave Browser isn't a solution either, since they will also start implementing the change very soon. The only advantage with the Brave Browser is, that they have their built-in Ad Blocker. But if blocking advertisements is your only concern, you might as well look at completely different options , in my opinion! So what will this mean for open source investigators, that rely heavily on extensions within their browser? Well, you can always switch to Firefox, because after some quick searching, I have found no mention of Firefox dropping the support of Manifest V2. The only problem is, that Hunchly will not work in Firefox , so if you really need Hunchly, you are out of luck and might need to use two separate browsers, and only capture half the pages you visit. While writing this section, I did some checking, but life of course take unexpected turns, so I spent half a day cleaning up the kitchen after a blocked drain. But when I went over some notes, I did find some positive news after all. Because it seems that the beta version of Tampermonkey runs okay with some user scripts that I have installed. And within the release notes of Chrome 124 Enterprise and Education, I read that another beta version, of a User-Agent Switcher , is also update to Manifest V3. It is still possible that certain extensions will break, or stop working, but For now, I will be actively looking for solutions, or replacement extensions, to fill certain gaps. Do feel free to share good alternatives for browsers, or extensions, with the community so we can help each other out! Link: List with extensions . Link: https://blog.chromium.org/2024/05/... FUNINT: This Week's Meme I already added the meme for this week, well before I remembered I needed to add a section about the disappearance of Manifest V2 from Chrome... Not sure whether the outcome will be as catastrophic as this meme depicts, but I guess we'll find out! Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/d/c/0/7/7/dc077c3163c8782d3db1c0fd5da1b67929345ee9-2422-sofia.jpg","https://sector035.nl/user/pages/articles/2024-22/2422-canva-drawing.jpg","https://sector035.nl/user/pages/articles/2024-22/2422-meme.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_039dd670b506_0.jpg","blog_data/images/blog_039dd670b506_1.jpg","blog_data/images/blog_039dd670b506_2.jpg","blog_data/images/blog_039dd670b506_3.bin","blog_data/images/blog_039dd670b506_4.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2024-23","title":"","status":"ok","retrieved_at":"2026-08-29T16:15:19.02577+08:00","text":"Week in OSINT #2024-23 | Sector035 Week in OSINT #2024-23 Home Week in OSINT Articles Search Week in OSINT #2024-23 10th Jun 2024 google geolocation Your weekly dose of OSINT news brings you some more UDM options, Sofia and Shadows, and we'll look at some creepypasta! This week I looked at some more Google parameters, and the rest is filled with the topic of geolocation. So if you love playing the Quiztime challenges, and want to get better at it, then this episode of Week in #OSINT is for you! Here is this week's overview: Google UDM Sofia's Stage Talk Backrooms ShadowFinder Finding Sofia Tip: Google UDM Two weeks ago, I wrote about the discovery of the udm=14 parameter value within the Google searches, and how it can be used to strip the AI generated content, and Google adds. Some time after, Irina Shamaeva [ ] took it upon her to play around with other possible values, and it seems there are more options available for this parameter. And looking at the discovery that the URL parameter udm=7 is for videos, and is actually redirecting to tbm=vid , I had a look at that new parameter myself. After I did some testing, I found an old thread over at Stackexchange, listing a lot of options. of which the following ones are still working today: Parameter Result tbm=bks Books tbm=isch Google images (redirect to udm=2) tbm=nws Google news tbm=pts Google Patents tbm=shop Shopping tbm=vid Videos tbm=fin Financial tbm=map Downloads Google Maps JSON These parameters can be used to search Google directly, for instance: https://www.google.com/search?tbm=fin&q=facebook This link will direct you to the current price of Meta Platforms Inc over at Nasdaq, powered by Google Finance. Of course the question is: What else is there to discover? What other parameters are out there? And are there any that can help create more targeted searches, and therefore maybe create better search results? I know these options have been around for quite some time, but it is always great to explore. Link: https://booleanstrings.com/2024/06/05/... Media: Sofia's Stage Talk This week, Bellingcat [ ] is featured twice, but Sofia Santos [ ] also makes two appearances in this week's Week in #OSINT! This time with an interview over at Bellingcat's Stage talk. She talks about how she got into OSINT, how she found a job at CIR [ ] and of course about the importance of mental health. A great interview with Sofia, who is mostly known for her challenges, but also does an awesome job combatting crimes against humanity. Sofia's interview over at Soundcloud Link: https://soundcloud.com/bellingcat/... Media: Backrooms On the internet people are known to leave images or messages, that start to lead their own life, of which some turn into a creepypasta . Once in a while something is posted that has an impact, and have people stunned for years on end, not knowing what to do with it. It becomes a meme within its own right, until someone steps up and solves the riddle. This is such a story, the story of the so called backrooms . And while the original image was found in 2019 already , by Twitter user rkfg_me , it stayed unnoticed until Farrell McGuire [ ] posted a video on YouTube about it. An interesting search, that solves on of the many mysteries that exist on the internet. Thank you, Ben Heubl [ ] for the tip! The background story, and resolution, of the original 'backroom' Link: https://www.youtube.com/watch?v=-1EKIIM3ShI Tool: ShadowFinder Galen Reich [ ] and Gabòr Friesen [ ] created a tool over at the Bellingcat GitHub, that can help find a possible location, by using date and time information, together with a measured shadow. Rummaging through my personal photos, I found one and made an educated estimate of the length of the shadow, to give it a test drive myself too. After filling in all the details in the Google Colab project, like the exact date and time, and the object height and shadow length, it will give you all locations where the information provided could exist. This tool has a very specific 'niche', but there are absolutely circumstances where it can come in very handy. And to show how the tool works, they chatted with Georainbolt [ ], to hear what he thinks. Georainbolt talking with the developers of the tool Link: https://github.com/bellingcat/ShadowFinder Video: https://www.youtube.com/watch?v=pQIjDPFgdJA Media: Finding Sofia And what a treat I have for you this week! Because both Georainbolt [ ] and Sofia Santos [ ] are featured again! And this time Trevor is solving exercise number 19 , that only consists of text! Great to see his thought process, and how he takes notes, while going over the different clues. If you want to have a crack at it yourself, then I would suggest you do that. I can absolutely be solved, even after being online for about a year. Solving Sofia's exercise #19 Link: https://www.youtube.com/watch?v=Eg3Ztsw5FS4 FUNINT: This Week's Meme Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/user/pages/articles/2024-23/2423-meme.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_b8c6227065bf_0.jpg","blog_data/images/blog_b8c6227065bf_1.bin","blog_data/images/blog_b8c6227065bf_2.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2024-25","title":"","status":"ok","retrieved_at":"2026-08-29T16:14:56.820002+08:00","text":"Week in OSINT #2024-25 | Sector035 Week in OSINT #2024-25 Home Week in OSINT Articles Search Week in OSINT #2024-25 24th Jun 2024 twitter search engine book geolocation extremism podcast From search tools to Skip, and from X to extreme, another episode with some interesting topics from the world of OSINT I do strive to push an episode out whenever I am able to, but that doesn't always work, but I am back! So after skipping week 24, I found some interesting content that I wanted to share with you all. And one of the most interesting things, is an enormous read in the shape of a book that was published some time ago. Because open source intelligence, or investigations, do not rely on tools, but on deep understanding of the topic and platforms you are researching. But as usual, I have several items in this week's episode, covering a wide range of topics: NeedleStack with Skip Gaming and Extremism Search Tools Twitter/X Nonsense Josemonkey Media: NeedleStack with Skip Skip Schiphorst [ ] was a guest at the NeedleStack [ ] podcast, where he talks about investigating content in other languages, like Chinese and Arabic. Skip talks about his past and how he was asked to develop a course at one day. But he also talks about translating texts with basic tools with Google Lens and Google Translate, but also how certain nuances might be missed if someone isn't a native speaker. Another great NeedleStack episode, that will give you a great listen during your commute. NeedleStack's Spotify, with Skip Schiphorst Link: https://pod.link/1600516532/episode/... Media: Gaming and Extremism Gaming platforms have been used to share propaganda or certain insights for several years now, and Linda Schlegel [ ] and Rachel Kowert [ ] have collected information that give more insight into the world of extremists, and how gaming platforms are used to spread hate, harass people, or push a specific ideology. This book is not something that is a quick read, with over 200 pages filled with how platforms are used to spread these messages, to how companies try to detect, deter or counter extremism within their platforms or games. With hundreds of footnotes and references, it contains a lot of study material, and if you work with investigating gaming platforms within your field of work, then I highly recommend this read. And the best thing of all is, that it is published under a Creative Commons license. Thank you Ismael Alvarez [ ] for sharing this interesting book! Image taken from the cover of this book Link: https://www.taylorfrancis.com/books/... Link to Related publications over at Academia.edu Links: Search Tools This set of links by intel0logist [ ] has been online for several years already, but only recently I found it in Ritu Gill's [ ] OSINT roundup newsletter. It contains over 250 URLs to search engines, extensions and add-ons, databases and other related sites. This is a lovely treasure trove for people that are looking for a niche search engine for their investigation. Huge list of search tools Link: https://start.me/p/nRADzL/advanced-search-tools Tip: Twitter/X Nonsense Another tip by Ritu Gill's [ ] newsletter, about how to clean up your Twitter/X timeline. It seems that within the topics and interests that you 'follow', are not inline with what you are truly interested in, and in my case especially the 'interests' are totally unrelated to my content, what I like, the people I follow, and so on. It seems to me that Twitter/X is pushing these interests to generate some more revenue by showing as many ads as possible. The platform itself has been getting worse the last few months, is being swarmed with bots, scams and spam, and this is just another nail on their unescapable coffin, in my opinion. Loads of crappy interests forced upon you by Twitter Find all the interests within your Privacy and Safety settings, under Content you see . The so-called \"interests\", are just a long list of keywords and types, but the most interesting one is the \"Topics\", that might contain terms you have seen showing up in your timeline, that you have no interest in whatsoever. Media: Josemonkey While browsing the internet for some interesting content, I found the YouTube channel of josemonkey [ ], where he is finding people that want to be found. People can tag him in a post where they share a video, asking him to geolocate them. In his YouTube videos he responds with an explanation on how he was able to use the visual clues to find the exact location people were when they created their quest. Another really nice channel that give more insight into how geolocation works, and what techniques can be used to find a specific location. Josemonkey tackling Texan Texaco's Link: https://www.youtube.com/@josemonkey FUNINT: This Week's Meme Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/b/d/5/b/e/bd5bec386fa15d06dd2ec0cafca271919b60ee05-2425-gaming-extremism.jpg","https://sector035.nl/user/pages/articles/2024-25/2425-meme.jpg","https://sector035.nl/user/pages/articles/2024-25/2425-searchtools.jpg","https://sector035.nl/user/pages/articles/2024-25/2425-twitter-interests.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_d8484dc1535d_0.jpg","blog_data/images/blog_d8484dc1535d_1.jpg","blog_data/images/blog_d8484dc1535d_2.jpg","blog_data/images/blog_d8484dc1535d_3.jpg","blog_data/images/blog_d8484dc1535d_4.bin","blog_data/images/blog_d8484dc1535d_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/2024-27","title":"","status":"ok","retrieved_at":"2026-08-29T16:14:33.552938+08:00","text":"Week in OSINT #2024-27 | Sector035 Week in OSINT #2024-27 Home Week in OSINT Articles Search Week in OSINT #2024-27 8th Jul 2024 book geolocation opsec overpass turbo osint osm ai This week another small update from the world of open source investigations, with some free reading material to start with! This week I start off with a free book, put together by researchers, that show the importance of open source information and investigation techniques. I haven't been able to read it in full yet, but I do encourage you to check it out and bookmark it for future reference. Further more I touch on the subject of AI, large language models, and how they are slowly shaping the world of investigations: OSINT book AI & OSINT Earthkit OpSec Tip Tip: OSINT book The book \"Open Source Investigations in the Age of Google\" isn't just any book about open source investigations that teaches you the ropes, but is a collection of chapters written by different authors. They contain case studies, go into detail about the role of open source investigations within the intelligence community or journalism, and show how it can be used to track human rights violations or nuclear weapons development. The publication is free to read online, and contains a wealth of information, also within the abundance of footnotes that are available. Thank you Dr. Olamide Samuel [ ] for sharing this on X! Another must-read Link: https://www.worldscientific.com/worldscibooks/... Article: AI & OSINT This article touches on the subject of where AI and LLM's can be beneficial within the world of open source investigations. Several years ago the techniques weren't really ready yet, but the rapid development of large language models, training sets and new algorithms, make it that the world of open source intelligence is shifting. Matt Edmondson [ ] described in what areas computers can help us out nowadays, and if we are able to solve crimes faster due to this, while still being able to independently verify the outcome, I am all for it! You now how hard it is to find a suitable image? Link: https://thehackernews.com/2024/07/... Tool: Earthkit Several weeks ago I was sent a link to the GitHub repo of \"earthkit\", after which I tried to get it up and running locally. I didn't have enough time to solve some bugs I encountered, and I left it for what it was. But when Cyb_detective [ ] mentioned it again last week, accompanied by a web-based version, I had to play with it again! This is a one-stop solution for geolocation tasks, and while it isn't perfect yet, it will be more than able to help you in some of the more tougher investigations out there, or get you somewhat close to a possible area. A really awesome tool that can only improve. Thank you Jett Chen [ ] for all your work! Using GeoCLIP to guestimate an easy Quiztime challenge GitHub: https://github.com/JettChenT/earthkit Link: https://earthkit.app Tip: OpSec Tip A quick tip from Sinwindie [ ], about active investigation techniques that use pass resets to find information. It may seem harmless on your end, but have you tried these techniques on your own accounts recently? Have you checked that the target isn't being notified about it? Online platforms may change their policies about this overnight, and all of a sudden your seemingly harmless investigative technique can spook a high-value target. Be careful out there, stay passive, stay hidden... Stay passive! Link: https://www.youtube.com/watch?v=bQQxTbsrUKM FUNINT: This Week's Meme Have a good week and have a good search! Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/6/2/c/8/4/62c8479ee2a1b5c272ffe1b3158edc6a30bf9dac-2427-investigate.jpg","https://sector035.nl/user/pages/articles/2024-27/2427-earthkit.jpg","https://sector035.nl/user/pages/articles/2024-27/2427-meme.jpg","https://sector035.nl/user/pages/articles/2024-27/2427-osintbook.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_3313f8663bc5_0.jpg","blog_data/images/blog_3313f8663bc5_1.jpg","blog_data/images/blog_3313f8663bc5_2.jpg","blog_data/images/blog_3313f8663bc5_3.jpg","blog_data/images/blog_3313f8663bc5_4.bin","blog_data/images/blog_3313f8663bc5_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:apr_2024","title":"April 2024","status":"ok","retrieved_at":"2026-08-29T16:18:43.196053+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 29th Apr 2024 Week in OSINT #2024-17 This week's episode of WiO covers topics from cruise ships to custom search, and from sins to secrets! Now that I've got the very cheesy alliteration covered, it's time to write the intro for this week's episode. As usual, this is done in the early morning, when everything around me is still quite... maps google podcast custom search engine osint maritime 22nd Apr 2024 Week in OSINT #2024-16 Another Monday with some interesting tips from the world of open source intelligence and investigations This week I have some more interesting tools, links and media for you, part of it from some of my own research I have been doing while building a new virtual machine. And while I was thinking ab... youtube podcast extension tutorial tool 15th Apr 2024 Week in OSINT #2024-15 From videos to visualisations, companies to communities, and from tips to tools! Maybe all of it is in this week's episode, but I mainly love alliterations... Time flies when you're having fun, or when you are busy studying, like I was... But this week I am back with another 'normal' episode of We... cryptocurrency bookmarks social media factchecking corporate intelligence business intel osint training 8th Apr 2024 Week in OSINT #2024-14 A short update from the world of OSINT, with some nifty mapping tools and tips by me, some profile photos and another source of news! I am still rather busy, and didn't have time to write a full-on update from the last few weeks. But I did want to share a few interesting things I read or used myse... maps google social media osint Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/1/4/c/d/8/14cd89b826ff0b52e1ff0593cfab6989b1e68fd2-2415-deckblue.jpg","https://sector035.nl/images/1/f/8/2/9/1f829fbc69822b5b3d854fc8fd0f04495bff36b0-2417-cruisemapper.jpg","https://sector035.nl/images/3/2/f/f/2/32ff261b8063c396a2d0c593327179bc32edd030-2416-truckparkings.jpg","https://sector035.nl/images/f/3/0/d/1/f30d1a897adf80224612b84e3ed5514ed3d49d31-2414-grid.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_313c589aab9d_0.jpg","blog_data/images/blog_313c589aab9d_1.jpg","blog_data/images/blog_313c589aab9d_2.jpg","blog_data/images/blog_313c589aab9d_3.jpg","blog_data/images/blog_313c589aab9d_4.bin","blog_data/images/blog_313c589aab9d_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:aug_2024","title":"August 2024","status":"ok","retrieved_at":"2026-08-29T16:17:35.114915+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 5th Aug 2024 Week in OSINT #2024-31 This week I have a small update from the world of OSINT for you, and am taking a small break for a few weeks! It is time for me to take a little break again, like I usually do every year around July or August, and it comes at a great time. The last few weeks I have sometimes struggled to find suit... privacy bookmarklet podcast extension phone numbers Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/4/0/1/1/8/40118aef4fa9e9fec4019f0f9d9e2588c70cc5df-2431-osintlytics.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_e56bd5a4a7e5_0.jpg","blog_data/images/blog_e56bd5a4a7e5_1.bin","blog_data/images/blog_e56bd5a4a7e5_2.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:dec_2023","title":"December 2023","status":"ok","retrieved_at":"2026-08-29T16:19:51.319698+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 18th Dec 2023 Week in OSINT #2023-50 Christmas is getting close, and this will be the last episode of this year! But I've got some interesting content for you! Every year around the December holidays I take some time off. And even though I have taken several breaks this year, due to an extremely busy schedule, I am going to take anot... domains whois podcast extension phone numbers training 11th Dec 2023 Week in OSINT #2023-49 Another week, another episode with podcasts, people, tutorials and training! This weekend was a bit more busy than I anticipated, so I didn't have enough time to finish this week's episode in time. But I still wanted to publish it, since I found some interesting things last week I really wanted to... maps geolocation podcast tutorial ctf tool training 4th Dec 2023 Week in OSINT #2023-48 In this episode of Week in OSINT, I have some nice tutorials, an advent calendar, links and the weekly meme! Another Monday, another episode of Week in OSINT is here! Some really nice topics to cover, and of course I will try to keep the new tradition of featuring a weekly meme in my episodes! ... google bookmarks social media ctf reverse image search users Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/7/d/e/8/9/7de8980acf75e8b4ec4e232b69b1b73cf445dd82-2349-sitemaps.jpg","https://sector035.nl/images/8/7/4/3/0/874301e75646683cb31f8cfe1f225242693f8e54-2350-theseint.jpg","https://sector035.nl/images/8/8/f/1/4/88f1422f2d20ace56de3a4df80335bde1d73abd6-2348-advent.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_203206e5f992_0.jpg","blog_data/images/blog_203206e5f992_1.jpg","blog_data/images/blog_203206e5f992_2.jpg","blog_data/images/blog_203206e5f992_3.bin","blog_data/images/blog_203206e5f992_4.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:dec_2024","title":"December 2024","status":"ok","retrieved_at":"2026-08-29T16:17:13.871434+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 2nd Dec 2024 Lake Constance - Geolocation It has taken well over 7 years before this geolocation challenge was resolved, and I have spent countless hours on trying to find this years ago. Sadly enough, work and other priorities had taken over my life, so the last three years I didn't have time to look at it at all. Until recently, when I ma... maps geolocation quiztime aerial imagery Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/8/8/6/7/d/8867d4106d890f7d5545af85c3dc7b027e46e557-tweet-countrytec-2017-07-24.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_54129e987971_0.jpg","blog_data/images/blog_54129e987971_1.bin","blog_data/images/blog_54129e987971_2.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:feb_2024","title":"February 2024","status":"ok","retrieved_at":"2026-08-29T16:19:19.893034+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 19th Feb 2024 Week in OSINT #2024-07 This week I have a very short update again, but I am very pleased with the little tips that I found for you! As stated in episode 2024-04 , I am very busy lately, so I don't always have time to write a full length episode. But I did find a little bit of time to share some interesting things that... domains privacy tutorial 12th Feb 2024 Week in OSINT #2024-06 Another Monday, another small recap from the world of OSINT! This week I have some tools, tricks, tips and other topics! Another busy week, with a lot of things happening in the world of OSINT. Due to my busy schedule, I am unable to mention everything, but I did spot some interesting things over... google podcast tool training 5th Feb 2024 Week in OSINT #2024-05 Another short update from the OSINT community, with some news about recent changes, privacy and another challenge by Sophia! The social media landscape is constantly changing, as are the tools we have to our disposal. That is why I always recommend people not to rely solely on tools, but understan... twitter google privacy opsec training Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/0/c/c/2/0/0cc201598e2e4ef1fc66d0a63184734f15c9ac79-2405-sotwe.jpg","https://sector035.nl/images/2/d/6/9/7/2d69751fe8501102a59d4b07534ee2ee50cdda0a-2406-regex.jpg","https://sector035.nl/images/a/6/1/1/6/a61169fbcb100b1edb3ea5754d9ab639b0e6f9af-2407-browser-privacy.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_48dd986907b2_0.jpg","blog_data/images/blog_48dd986907b2_1.jpg","blog_data/images/blog_48dd986907b2_2.jpg","blog_data/images/blog_48dd986907b2_3.bin","blog_data/images/blog_48dd986907b2_4.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:jan_2024","title":"January 2024","status":"ok","retrieved_at":"2026-08-29T16:19:35.606176+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 29th Jan 2024 Week in OSINT #2024-04 Here is another overview of week 4 from the world of OSINT, covering everything from CTFs to DNS and anything in between! Lately I have been extremely busy with an education, and for a couple of weeks things won't really improve. So it is possible that a few of the upcoming episodes are slightly s... google investigation bookmarks social media ctf archive 22nd Jan 2024 Week in OSINT #2024-03 Welcome to the first episode of Week in OSINT of 2024! Here are some interesting articles, tutorials and tips for you! It has been a while since the last episode of Week in OSINT, but after being ill during the holidays, I chose to spend some time on things that are way more important than this we... google podcast bookmarks tutorial methodology maritime Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/0/1/d/f/e/01dfef30c715ad20610f4c091d7c382326a3d979-2403-globalfishingwatch.jpg","https://sector035.nl/images/d/e/7/d/f/de7df8ea62d63d5170173af1f46a73c360fb69f6-2404-hacktoria.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_f0a7c817b8e1_0.jpg","blog_data/images/blog_f0a7c817b8e1_1.jpg","blog_data/images/blog_f0a7c817b8e1_2.bin","blog_data/images/blog_f0a7c817b8e1_3.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:jul_2024","title":"July 2024","status":"ok","retrieved_at":"2026-08-29T16:17:44.215663+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 29th Jul 2024 Week in OSINT #2024-30 Welcome to your OSINT fix of Monday July 29, with some articles, crypto currency, a podcast and a nifty tool! I like to do things 'quick and dirty' if I need something fast, but then I always forget to actually create something for the next time I really need it. And that also gets me to the last... maps privacy cryptocurrency podcast tool osint health 22nd Jul 2024 Week in OSINT #2024-29 Welcome to a short update of week 29 of 2024, where I dive into some interesting posts I found on social media. Last week I had an extremely busy weekend, where I hardly had any spare time for myself, so I really had to skip that one! But slowly we're getting things bak on track, so this week I re... domains whois bookmarks 8th Jul 2024 Week in OSINT #2024-27 This week another small update from the world of open source investigations, with some free reading material to start with! This week I start off with a free book, put together by researchers, that show the importance of open source information and investigation techniques. I haven't been able to... book geolocation opsec overpass turbo osint osm ai 1st Jul 2024 Week in OSINT #2024-26 This week a filled episode, with books and bookmarks, names and Needlestack, training and tweets! This week I spend some extra time to go over social media tracking down all the good stuff out there, and it was quite a lot! I learned a lot again, due to all the tips that people shared online with... twitter book podcast bookmarks archive training methodology Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/0/c/7/d/e/0c7de3c6d5c12a3a4e32844237238016d25bf556-2429-urldna.jpg","https://sector035.nl/images/1/8/5/3/e/1853e5c754fece24b8f73dfbc2d1a558c9c17173-2426-osint-books.jpg","https://sector035.nl/images/2/1/d/6/5/21d657f6593a1ddbaf722d3aa4f4c20fd45362bb-2430-searchgrid.jpg","https://sector035.nl/images/3/3/f/2/5/33f258226d4eda51a3405a7b489c348d9a8f6135-2427-investigate.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_36758270acc3_0.jpg","blog_data/images/blog_36758270acc3_1.jpg","blog_data/images/blog_36758270acc3_2.jpg","blog_data/images/blog_36758270acc3_3.jpg","blog_data/images/blog_36758270acc3_4.bin","blog_data/images/blog_36758270acc3_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:jun_2024","title":"June 2024","status":"ok","retrieved_at":"2026-08-29T16:18:01.170397+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 24th Jun 2024 Week in OSINT #2024-25 From search tools to Skip, and from X to extreme, another episode with some interesting topics from the world of OSINT I do strive to push an episode out whenever I am able to, but that doesn't always work, but I am back! So after skipping week 24, I found some interesting content that I wanted to... twitter search engine book geolocation extremism podcast 10th Jun 2024 Week in OSINT #2024-23 Your weekly dose of OSINT news brings you some more UDM options, Sofia and Shadows, and we'll look at some creepypasta! This week I looked at some more Google parameters, and the rest is filled with the topic of geolocation. So if you love playing the Quiztime challenges, and want to get better... google geolocation 3rd Jun 2024 Manifest V3 This page contains a list of extensions, and their respective Manifest versions. In Week in #OSINT 2024-22 , I wrote about the upcoming changes within the Chromium based browser extensions. This page contains a list of extensions that use the newer Manifest V3, and should be (somewhat) future proof. extension chrome 3rd Jun 2024 Week in OSINT #2024-22 Besides the usual interview, exercise and geolocation article, I need to address an important situation regarding the future of Chrome extensions This week a major part of this episode has to do with an important change that is coming up, the phase-out of older extensions, due to major changes wit... google geolocation extension training interview Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/4/f/f/7/2/4ff726d5841b23418295771deed27b241d118369-2423-georainbolt.jpg","https://sector035.nl/images/a/a/5/1/f/aa51f347d350a700a79c3ee51c781b499983da4a-2422-sofia.jpg","https://sector035.nl/images/e/4/7/e/a/e47eac015520a74a3053321839ac7faf59d7cde8-2425-gaming-extremism.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_cc52eac8321f_0.jpg","blog_data/images/blog_cc52eac8321f_1.jpg","blog_data/images/blog_cc52eac8321f_2.jpg","blog_data/images/blog_cc52eac8321f_3.bin","blog_data/images/blog_cc52eac8321f_4.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:mar_2024","title":"March 2024","status":"ok","retrieved_at":"2026-08-29T16:19:05.164832+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 18th Mar 2024 Week in OSINT #2024-11 Another short update from the world of OSINT, that starts off with a review of a documentary I watched last week. Social media has quite an impact on modern society, and not always in a positive way, as can be seen in the documentary \"Idaho Murders: Trial by TikTok\" that was launched last week. De... google investigation tiktok podcast osint 11th Mar 2024 Week in OSINT #2024-10 Welcome to another very lengthy update from the world of OSINT, with some Google searches, strategy and a hint of Insta and Snaps... One of the things I like about open source intelligence (OSINT) and social media intelligence (SOCMINT), is the fact that there never seems to be a dull moment. Ever... google instagram snapchat methodology network analysis 4th Mar 2024 Week in OSINT #2024-09 [Search Engine Special] This week I've got a special lined up, since it is all focussed on search engines after following the news about a Google bug! The last week or so had one specific theme, namely: Google Search! This episode of Week in OSINT is therefore a special on search engines. Once in a while something breaks... google search engine yandex bing Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/1/1/c/3/8/11c38f6f7fd03b3ac48b7adaf67e2724e24587a1-2409-seosly-bing.jpg","https://sector035.nl/images/6/1/8/4/d/6184dff09a8fcb6042c8fa5807fcb88ac60e3dd4-2411-tiktok-trial.jpg","https://sector035.nl/images/9/c/f/4/f/9cf4f1d432b0b829c8bbb0b8ff69c9a86461c0ac-2410-snapmap.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_0e5f583623cd_0.jpg","blog_data/images/blog_0e5f583623cd_1.jpg","blog_data/images/blog_0e5f583623cd_2.jpg","blog_data/images/blog_0e5f583623cd_3.bin","blog_data/images/blog_0e5f583623cd_4.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:may_2024","title":"May 2024","status":"ok","retrieved_at":"2026-08-29T16:18:19.14432+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 27th May 2024 Week in OSINT #2024-21 This week we'll be looking at the way Google used to look, and how to retrieve that, an old chat app, and more interesting topics. This week's episode of Week in #OSINT almost turned into a special that revolves around 'history'. Whether it is returning to the good old Google, a tool that is alrea... google podcast snapchat osint 20th May 2024 Week in OSINT #2024-20 This week another small collection of news, articles and tips, curated by me, and shared for your Monday morning pleasure. This week was a bit difficult to get the episode out, since I had a rather busy, and somewhat weird schedule last week. After working some odd shifts, and some extra hours, I... maps twitter dark web osint 13th May 2024 Week in OSINT #2024-19 This week a small update due to a very busy weekend. Some content I found online, but this week I also share one of my personal tips! At the end of last week, large parts of the world had the chance to admire a rare event. In large parts of the world the Aurora Borealis and Australis were visible... extension add-on tool telegram phone numbers 6th May 2024 Week in OSINT #2024-18 Another episode with some interesting articles, tools, search engines and of course the ever-present Monday Morning Meme! It has been quite some time that I actually tested a tool in a custom VM, but this week I simply had to give the new Telegram a go. I love this tool a lot, especially since it... google custom search engine telegram sock osint methodology Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/2/4/6/a/1/246a1ca3a990a79835292fe2d598f99966a7c3e5-2421-google2.jpg","https://sector035.nl/images/5/8/a/4/9/58a4900c2b284cecf2deccbbef1c8045f42f90e2-2420-oldtweetdeck.jpg","https://sector035.nl/images/9/7/0/5/4/97054937f1cad56a397415b4704f7131f3ce8f8a-2419-uaswitcher.jpg","https://sector035.nl/images/b/c/7/e/1/bc7e1cadfe70a5122cbbbaa204e5742fb71479bd-2418-cses.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_59788d6128c7_0.jpg","blog_data/images/blog_59788d6128c7_1.jpg","blog_data/images/blog_59788d6128c7_2.jpg","blog_data/images/blog_59788d6128c7_3.jpg","blog_data/images/blog_59788d6128c7_4.bin","blog_data/images/blog_59788d6128c7_5.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:nov_2023","title":"November 2023","status":"ok","retrieved_at":"2026-08-29T16:20:09.631739+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 27th Nov 2023 Week in OSINT #2023-47 It is another Monday, so I have gathered some interesting content from the world of OSINT for you! Hello Monday, here is another short update with some interesting things I found last week. Another last minute edit here or there, that is why this episode is published slightly later. This is not a... tutorial tool ai 20th Nov 2023 Week in OSINT #2023-46 A very short update, after being away for some weeks! This week, with some 'highlights'... Okay, excuse the pun, those highlights can be found in the first section of this week's episode. A really handy little tool that will absolutely help you on your adventures out there. Talking about adventure... google extension add-on tool Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/1/f/5/3/c/1f53c2128960a94a7071e19512709b313b8979ea-2347-urlhunter.jpg","https://sector035.nl/images/3/b/4/a/9/3b4a9e8368caa4d062756cbe6b71fe66910f253f-2346-forensic-osint1.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_d195042a054a_0.jpg","blog_data/images/blog_d195042a054a_1.jpg","blog_data/images/blog_d195042a054a_2.bin","blog_data/images/blog_d195042a054a_3.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/archives_month:oct_2024","title":"October 2024","status":"ok","retrieved_at":"2026-08-29T16:17:24.09373+08:00","text":"Articles | Sector035 Articles Home Week in OSINT Articles Search Here you can find all the published articles (still migrating some from Medium . Including your weekly dose of OSINT news published every Monday at 8:00 AM CEST! 19th Oct 2024 About Black Box (CL)OSINT Tools Within the last decade or so I have the feeling that 'OSINT' simply has become a buzzword, and loads of companies and startups want to jump on the bandwagon to try and earn some extra money with it. But with that, I also noticed a very dangerous development within the field of open source intelligen... tool osint methodology Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/6/7/2/0/a/6720a60f8f2d2bc9029558c1433459ee70361229-black-box.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_a76c4cce6c87_0.bin","blog_data/images/blog_a76c4cce6c87_1.bin","blog_data/images/blog_a76c4cce6c87_2.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/chronolocation-of-media","title":"tutorial on chronolocation","status":"ok","retrieved_at":"2026-08-29T16:26:43.360456+08:00","text":"Chronolocation of Media | Sector035 Chronolocation of Media Home Week in OSINT Articles Search Chronolocation of Media 26th Nov 2021 social media metadata investigation chronolocation A comprehensive guide to determining dates and times in (online) media In this article I'll be diving into the world of chronolocation, metadata and shadows. Since this is the largest article I've written so far, I've decided to create a table of contents for your convenience. At the end of every chapter and after long paragraphs, there's a link to bring you back there if you need it. Since I know there will be updates in the future, I also added a document version control, for an easy overview of the changes. Table of Contents Introduction 1.1 Geolocation vs Chronolocation 1.2 Intended Use 1.3 History of the Word Chronolocation Workflow for Chronolocation Metadata in Digital Media 3.1 Interpretation of Metadata Basics of Chronolocation 4.1 Earliest Possible Moment 4.2 Latest Possible Moment 4.3 Possible Time Frame 4.4 Specific Time Looking for Clues 5.1. Construction, Scenery and Landscaping 5.2. Events, Acts and Festivities 5.3. Seasons and Nature 5.4. Other Indicators 5.5. Google Earth Pro Sun Based Chronolocation 6.1. Basic Time Calculation 6.2. Date and Time Calculations Tips and Tricks 7.1. Hard to See Shadows 7.2. Shadows in Different Angles 7.3. ShadowCalculator 7.4. Warnings and Pitfalls Conclusion and Glossary 8.1. Glossary Version control Date Changes 26/11/21 Initial publication articles chronolocation / metadata 1. Introduction I have always been intrigued by the way forensic examiners were able to determine a timestamp for photos or events, without having direct knowledge of it in the first place. Since I became a regular member of the Quiztime community, having done quite a bit of 'geolocation' during those quizzes and some more serious investigations, and more than once there wasn't just the question of where a certain photo or video is shot, but also when it happened. In this guide, I am going to dive a little deeper into the techniques of what is called ‘chronolocation', the act of determining or estimating a time or time frame of an event or situation that was captured by visual media. This article has been in the making for a very long time! It basically started during February 2018 when I was able to determine the possible date and time of a photograph that was posted as one of the daily verification quizzes by the Twitter account Quiztime. Later that same year I spent some evenings on determining the possible date of an extrajudicial execution in Cameroon. After this people started contacting me with questions about the techniques I used, or requests to help in investigations. And so, we end up in early 2019, when I started to write this lengthy tutorial. But due to all kinds of other commitments I've never been able to finish this, until now. The writing of it has been quite a journey I must say! It took me weeks to even get an overview of subjects I wanted to touch. Then multiple weeks of writing things on my personal blog on Medium, followed by transferring it all to a separate document, since it was getting way too big. I planned to release it as a PDF on GitHub, but after I decided to host my own blog things finally took off again. And I finally took the time to transfer everything to here and finally was able to finish it. And when I saw that others, like Nick Waters, were posting little write-ups as well about it, it was time to get to work again. After more endless nights and weeks of working on it in my spare time, I somehow actually was able to finish something I felt comfortable sharing with the world. So here it is… A guide that is probably nowhere near being complete! But as far as I was able to find it is one of the first and maybe the only one of its kind at the moment. 1.1. Geolocation vs Chronolocation When it comes to establishing a time frame, it turns out that both the art of geolocation and chronolocation have similarities. The main difference is that a global indication of the location is needed for chronolocation if we want to be precise. But both techniques demand a thorough investigation of every part of a photo or video, an understanding of the surrounding area, some local knowledge and maybe even the weather. Where for geolocation the knowledge is used to find a possible location, in chronolocation we use that information to narrow down the possible time frame. Besides that, both geolocation and chronolocation can complement each other. Where the knowledge of a precise location can help determine an accurate time frame, a shadow can aid an investigator in geolocation by giving a clue in which direction a photo or video was shot. But it can also be important to determine a time or date to find specific events that happened around that moment in time, to zoom in on possible locations. 1.2. Intended Use The goal of this guide is to give a basic understanding of chronolocation and to share it with everybody who needs to apply the techniques in one form or another. This guide will probably not cover every possible aspect of chronolocation, but I tried to make it as complete as possible. The tips and techniques range from going through source code or extracting metadata, to investigating sceneries depicted in a photo to determine a possible date or time. Everything described in this guide contains common sense, basic physics and other verifiable techniques, but they must be used correctly before they can be admitted as evidence. It is also important to note that when using specific techniques for legal cases, it is advised to have them verified independently before admitting them to a court of law. Furthermore, I intend to make this a living document that will receive a new revision over time when there is enough new information to add. It would be nice if the community of OSINT, GEOINT and other INT's reach out if they feel there are any areas of expertise that should be included. 1.3. History of the Word Chronolocation The word ‘chronolocation' comes from the Greek word 'chronos' (time) and the Latin word ‘locus' or the verb 'locare' for locate. In general, it describes the act of determining the moment something happened. It isn't a well-known word, but it seems it has been used for years already to describe the action of finding a date or time frame. Here is an abstract of ‘Gender and Song in Early Modern England' from 2014 using the same term when it talks about finding the time frame of a scene in the 1992 film ‘Orlando'. Extract from ‘Gender and Song in Early Modern England' by Leslie C. Dunn and Katherine R. Larson. The earliest mention of the word itself I could find takes us back to 1983, to the article 'Australian Sea Levels in the Last 15,000 Years' by David Hopley of the Department of Geography of the James Cook University of North Queensland. So, the word has been in use for quite some time already and due to the upcoming 'citizen journalism' the term is slowly gaining more popularity. To make things a little complicated, the term is used in fiction novels as a term for 'time travelling'. But I won't be touching that subject in this guide, since that is in no way my area of expertise. ↑ Table of Contents 2. Workflow for Chronolocation Geolocation and chronolocation have similarities when it comes to the investigative part of it, as mentioned earlier. Both require certain steps that need to be followed, or at least considered, and, as with any type of investigation, the credibility of the source is important. Since I was unable to find a good workflow for either, I propose the following for chronolocation, which of course can be adopted for geolocation with some adjustments: Proposed workflow for chronolocation of media Since the verification of findings in any kind of investigation is the most important, it is listed multiple times throughout this workflow. In this article, several techniques will be discussed that can be used to determine dates or times. Starting with metadata in digital media, and ending with calculating shadows. Where possible, Quiztime quizzes are used as examples. This Twitter account is a great way to practice your verification skills, and in the past multiple quizzes needed chronolocation techniques to solve a question. ↑ Table of Contents 3. Metadata in Digital Files When media is acquired in a digital form, and a date or time needs to be determined, there are multiple ways of doing so, depending on the file type and the source it came from. First and foremost, it is important to check whether there is extra information inside the original obtained file, the so-called metadata . Within digital media there is usually extra information, which can be acquired by investigators. As an example, we can use a tool that can read the Exif data of a digital photo. Exif stands for 'Exchangeable image file format' and specifies the format of information inside digital images and audio. Some images have an abundance of information, but it is also possible that it is stripped of all the information due to being uploaded to a social media platform. Example of Exif information inside a JPG file, opened in JPEGsnoop Sometimes it is enough to look at the details of digital files from your file explorer to read the metadata, but there are several tools out there that give you some more options. 3.1. Interpretation of Metadata Retrieving timestamps directly from digital files is a good start, but since a few years a lot of social media platforms are stripping the uploaded media from the metadata. Besides that, it is also possible to strip this information manually prior to distribution. And since the metadata inside the Exif tags consists of mostly plaintext data that can be easily changed or erased with easy to use tools, it can be one of the less trusted ways of determining a date or time. There are exceptions, for instance when the file is acquired directly from a trusted source, like a forensic photographer, or a member of a news agency, but in general my personal advice would be to treat Exif data as corroborating information and verify any date and time that is mentioned in a file, by investigating its content. Photos on sites like Flickr, that preserves the Exif information, might look handy since the people uploading it wouldn't have a reason to change the data. But there's another problem on such sites, since there are quite a lot of photos that have incorrect timestamps for the location they show. One of the most common reasons is that people on holidays don't always adjust their camera settings to reflect the local time zone. So be prepared to verify all Exif data within photos from social media sites like Flickr if they need to be used for chronolocation. To prevent such information ending up in your evidence, here's a tip by Christiaan Triebert : Try and contact the source, and verify the clock settings of the device that was used to capture the image or footage. Make a photo of the camera with a clock next to it that shows the current, local, time. This way you have the possibility to adjust timestamps if needed. Besides Flickr and 500px that preserve full Exif information, there are some social media platforms that retain other valuable pieces of information, like the time of uploading. Even though the exact moment of uploading might not seem useful straight away, it can at least give some insight into the latest possible creation date of digital media. There have been instances where people made claims about a certain event, where the footage shown was uploaded months or years earlier, thereby refuting the story. Finding metadata in websites or digital media is a subject that is very important for chronolocation, it’s too wide for the scope of this article. Therefore, I've created a separate guide on this that explains the basics. It shows the usage of simple tools, and how to retrieve information on some popular websites and social media. Click here to go to the chapter ' Metadata in Digital Media ' ↑ Table of Contents 4. Basics of Chronolocation When you have an image or video the chances are that these come from an online source. If so, it always pays off to investigate the metadata that comes with it. If that doesn't contain information that is useful, the next step is to dive into the minute details of the scene to look for clues that can indicate a specific date, time or time frame. Before going into that, let's first have a look at something else, the initial research question. Within chronolocation there are several 'moments' that might be determined, depending on the need of that research question. Finding an exact time is not always possible, and sometimes not even needed. So it's important to determine whether finding the exact date is the goal. Answering that question can save a lot of time. 4.1. Earliest Possible Moment There are times that the research question is along the lines of: \"Is the situation depicted possible, at the moment it was claimed?\". Or maybe the situation calls for debunking a specific claim, where an 'earliest moment in time' is key. In such cases all one needs to do is to determine the earliest possible moment in time for the media that is being researched, because it's not always needed to determine the exact creation date of the media, since verification can be done by determining one parameter. When looking for indications of the earliest possible moment one can look at objects or circumstances that were not present or have changed before the specific date itself. Examples are manufacturing dates of cars, or licence plates that are issued in chronological order. Another example can be the presence of a public transport vehicle that, that matches a specific time or day mentioned in that particular case. Other things to look for are the specific seasons, the local weather or construction work that was done in the area. 4.2. Latest Possible Moment Just as it is possible to have the earliest possible moment, there is also the latest moment that an event has occurred, or the media was created. The research question or purpose is slightly different, but the approach is the same. For this you need to look at things that have changed after the moment in time that is claimed. For instance one can look for new objects after the time of the event, like new road signs or construction work that was finished. Besides new objects, one can also look for things that have been removed after the claimed moment. This can be anything from mowed lawns to a building that was demolished. Anything that can bring down this date can be used to find the latest moment where the situation that is researched could have happened. 4.3. Possible Time Frame When the research question demands that a possible time frame must be established, one can combine the earliest and latest possible moments in time. This can also be used as the basis when trying to determine an exact date and time, since by first limiting the amount of possible dates, it will help to focus on the small details and eventually find the exact day. This is not always an easy task but by going over small details in a photo or video, it's sometimes possible to find enough little clues to narrow down the possible time frame that a specific scene could exist. An example of narrowing down such dates can be read in this write-up of the Quiztime challenge of February 28, 2018 . ↑ Table of Contents 4.4. Specific Time When the exact location is known or determined, it's sometimes possible to calculate a more specific moment in time by using the angle and direction of the sun, if any shadows are visible. We'll have a more in-depth look at these techniques in chapter 6 . Be aware though that there are a few important things to consider when using this technique: The main thing is the exact location on earth. Due to the fact that the angle of the sun near the equator is completely different compared to a location that is further towards the north or south, it can be harder to determine a correct time. Since the earth doesn't move nicely and calm in a circle around the sun, but has an oval shaped path, and even 'wobbles' while it rotates along its own axis, the exact location is important. Around the equator the sun sits high in the sky, moving faster in a horizontal way, but when moving further north or south, the sun is in a more shallow angle towards the horizon, appearing to move more slowly throughout the day. And the movement of the sun isn't only different throughout the day, but also during longer periods. Since locations further away from the equator have a more shallow angle throughout the year, and due to movement of the earth, it can result in less difference in angles at any given time. To illustrate these points, here are two locations, where two moments in time are shown where the direction of the sun is nearly identical: Location: Helsinki, Finland Date Time Azimuth June 22 14:59 215.03 December 31 14:59 215.07 Location: Hurghada, Egypt Date Time Azimuth June 22 12:15 239.98 December 31 16:26 240.03 In Helsinki it's possible to have the same time and azimuth, or 'direction of the sun', on two dates that are months apart. While these parameters change rapidly in Egypt when you jump even one or two weeks back or forth. 4.5. Basic Steps When the research question demands a specific date, it's best to start with a rough time frame and narrow that down with more information. For instance, one can use satellite imagery to look for large objects, like buildings, that have changed or demolished over the years. To narrow down the time frame even more, go over other sources that have information on the area. This can be news media, or even social media, as long as it has information with a date that makes it possible to look for differences. With this newly found information, the time frame can be narrowed down. When the time frame has been narrowed down to less than about a year, it might be possible to determine the exact moment of time. For that, one has to look at the position of the sun, by going over shadows if they are visible. Overcast skies can make this step difficult or even impossible, since light scatters in different directions. And when shadows aren't clear enough to use, look for a general direction where the light comes from to determine the possible direction where the sun is sitting. This might give enough information to narrow down the possible time, but for that a possible date has to be determined first. To sum it up, the steps we need to take are: Determine the location Determine the year Determine the season Determine the date and time If only the location is known, and there are no indications to narrow down the year itself, it might be possible to find a possible date and time without the actual year. Since the earth rotates around the sun in a very predictable pattern every year, it is sometimes possible to use tools to find the possible date, if the angle and direction of the sun can be measured precisely. How that works, will be explained in chapter 6 . ↑ Table of Contents 5. Looking for Clues When you are new to chronolocation, the best way to start, besides having a correct and trusted EXIF data of a photo, is to simply look at a scene. Go over it, try to describe the objects that are visible and find indications of a certain moment in time that these objects should have existed. Use the same techniques as you use for geolocation, and perform a ' gap analysis ' to structure the information and research questions. You might end up with a period as large as a decade, or as small as a year. But depending on what you are investigating, it could even be a specific day of the week or a specific local time. Sadly enough it isn't always possible to zoom in on a specific time or day, but there are also times that there is a lot to work with. I admit that I am sometimes blinded by lots of details in such a way that I miss some obvious clues. But going over all the information that is visible in a photo or video, as well as zooming in on those details, is extremely important. It's possible that while revisiting certain details after some time, one is able to pivot on other information that was gathered. Here are some examples of easy to spot things that can help you in the first steps: Seasonal indications like flowers, trees or general weather conditions Production years of cars, issue dates of licence plates New buildings, construction work or demolitions Clock towers, watches and clock from public transport Signs with time-based parking restrictions to determine a weekday Markets, roadworks, festivities or other temporary events Posters or placards with dates, like movies releases Advertisements, sales or specials at shops To illustrate some techniques described above, I'll look at one of my all-time favourite challenges from Quiztime. Philipp Dudek asked two questions in this challenge : Where was the photo taken and what date? The location was reasonably easy to find for most people, it was the Danish embassy in Riga, Latvia. Knowing the location, we can have a first look at the photo to try and find clues that can be used for chronolocation. Give it a try before scrolling below the photo, to see whether you can already find some clues yourself. As explained earlier, the first step in such a task is to narrow down the time frame. Since the photo was clearly taken in the digital era of photography, and the question was published early 2018, we have a period spanning well over a decade. And the most obvious indicators to narrow down the earliest possible moment, as discussed in chapter 4 , are the earliest production dates of cars. To find the latest possible time, some time was spent to find out when security cameras were placed on the building across the street. The third indicator was a change in parking restrictions at a later date, due to the fact that the sign itself wasn't visible on the photo. By using these three pieces of information, it was possible to bring back the time frame down to about 3,5 years. After that, it was time to look at the season, pruning of a specific tree and by calculating the angle of the shadow, all of which will be explained in later chapters. If you want to read the full write-up of this geolocation and chronolocation challenge, you can do so here . 5.1. Construction, Scenery and Landscaping Large changes within the scenery might be spotted with something as simple as Google Earth Pro . There is also a web version, but I would recommend using the application for speed, multiple extra options and the ease of which one can save, import or export locations in the form of KML files. April 2021 April 2020 ↔ Comparison slider might not work on mobile 5.2. Events, Acts and Festivities One thing that can be of help when trying to determine a possible time frame, are events or festivities shown on posters, placards or such. These are usually placed several weeks before a big event, and even though they could still be around several months after the event, they can provide some indication of the earliest possible moment in time. When going over photos or videos that are taken in a city or even indoors, make sure to check things like: Film and theatre posters Events and expositions Advertising placards Such posters and placards can also help with geolocation, since some countries have a very specific way of writing down dates. There are ISO standards when it comes to date notation , but there are some countries that have their own official standards. For instance, there are several countries, like Germany, Switzerland, Armenia and Romania, that write the dates using periods in between the numbers. These dates are always in the form of dd.mm.yyyy , with or without the leading zeroes for the days and months. So one can be fairly confident that the days are mentioned first when there are dots used in a written date. ↑ Table of Contents 5.3. Seasons and Nature Plants and trees can give a very good indication of the season during the time a photo or video was created. If there are plants or trees visible that seem to be flowering, you could try and determine what plant it might be and when they are supposed to bear flowers or blossom. I do have to send out a small caution and remind you that certain crops or plants can flower in different months, depending on the location. To give an example, it is common to see big fields of yellow rapeseed in the northern part of Europe and even in China from around April to June. But in Canada, where most of the yellow fields are Canola, a very similar scene will show up in June or July. And if we're talking about Australia, don't be surprised to learn this season falls in the months of August till October. To make it slightly more complicated, there are summer and winter versions of rapeseed, but usually the winter type has a higher yield, so it is more common to see them in the seasons I mentioned. Horse chestnut during spring — Pixabay An example that was handed to me by MCantow , is the chestnut. In Northern Europe we can see the chestnuts hanging from the trees from around October until early winter, but there is more to that tree during the rest of the year. Besides having the seeds at the end of the year, it grows flowers in late spring or early summer, as can be seen in the photo above, and during the fall the leaves turn a lovely shade of red-brown. In the following example , MCantow points out a European horse chestnut and a common lilac, that could be used to pinpoint the season. Using vegetation to determine a month Since the common lilac flowers in April and May in Europe, this narrows it down to two months. If the tree in this image is indeed the European horse chestnut, it would flower around the month of May. Since the distinct white flowers aren't visible in the image, this could mean that the episode may have been shot in the month of April, when the lilac would be bearing its flowers. MCantow was also the person who spotted something very useful in the previously mentioned example of the Riga embassy quiz. In the photo a lime tree visible in the garden of the embassy, that was trimmed or pruned once every so often. After doing some research on this, we found out it is indeed common to prune a lime tree every two years, because this is the best way to keep it in a healthy shape. By comparing images from this particular tree over longer periods of time on Flickr, we were actually able to estimate in which specific months over the years that tree was pruned, and therefore helping us in finding the actual date. But there are enough plants and trees that might be of help to determine a season, or even a possible month. Here are a few examples that I wanted to share since they blossom or flower in specific areas at very specific times. Do be careful and use this only as a rough guide, and always make sure to check local flora to make sure that you have the correct species when looking at specific plants or trees. Species Period Comment Lavender June Cape Verde and the Canary Islands, and from Europe across to northern and eastern Africa, the Mediterranean, southwest Asia to southeast India Cherry Blossom March to April Mostly Asia, but there are a few locations in Europe and North America where cherry blossoms can be found in parks Poppies April to June April to May in Southern Europe, May to June for more northern countries Witch-Hazel September to March USDA zones 3 to 8 (North America), it's special since this tree actually flowers during the winter months More information about the 'USDA zones', or hardiness zones, can be found at the Wikipedia page . This can be used as a reference, or to verify specific plants or trees within a geographic area. ↑ Table of Contents 5.4. Other Indicators There are many more factors you can use to bring down the date or time when it comes to chronolocation. If you are observant enough, and use every bit of information that is available, it'll open up a world of possibilities. In the next example people found out the time the photo was taken, by paying attention to the helicopter that was mentioned. After geolocating the photo, they looked at the flight data that was available of that area, and came up with the exact time. Using air traffic to determine a possible time To track air traffic, a website like Flightradar24 can be very useful. There are other websites that offer the same functionality, and with paid accounts it's possible to get more historical information on air traffic. 5.5. Google Earth Pro The free tool Google Earth Pro can be extremely helpful since it has historical imagery from nearly every location on the planet. This dataset can be found in the menu bar, by clicking on the small clock icon. Historical imagery within Google Earth Pro After clicking on the menu button, a small slider appears showing the date of the imagery that is currently showing. The slider shows light blue marks on dates where it features a dataset. Sliding throughout the dates will reveal these images on the screen. Going over the historical imagery can be useful to find changes in the landscape, as discussed in paragraph 5.1, but can also be useful to see what shadows look like in a specific location. August 2021 June 2011 ↔ ↑ Table of Contents 6. Sun Based Chronolocation If there is no clock visible in a photo or video, another way to determine a date or time is to use shadows. For multiple investigations I had to use this to try and determine a solid time frame, even though it can be a very challenging task at times. Some media are just downright poor in quality, or shadows are in very unfortunate angles to make it more difficult to work with it. But first let me explain something about the process involved. First, the earth revolves around the sun, what we call the earth’s revolution and the trajectory that the earth makes is shaped like an ellipse. While we spin around the sun once a year, the earth also rotates around a vertical axle that is slightly off centre. The tilted axis, together with the rotation around the sun gives the earth it’s four seasons. Image by Dennis Nilsson, Wikipedia Because the rotation of the earth and the trajectory around the sun is extremely predictable, we know that at any given day and time the sun is in a specific position. During a summer in the Northern Hemisphere the sun is high up in the sky, while the winters have the sun much lower towards the horizon. On the internet there are several tools available that can calculate the exact position of the sun at any given day or time. To use this for a calculation, the only thing needed are the angle in comparison to the horizon (the zenith or altitude) and direction of the sun (the azimuth). With these two pieces of information, anyone can calculate the possible date and time of any given shadow. Due to the trajectory of the earth and its rotation, there are two dates a year when the sun is in the same position, called the equinox. These dates are around March 20 and September 22. Looking at the moment of the equinoxes, we see the following pattern emerge: Latitude March equinox September equinox 90 N 0 degrees 0 degrees 60 N 30 degrees 30 degrees 50 N 40 degrees 40 degrees 25 N 65 degrees 65 degrees 0 N 90 degrees 90 degrees 25 S 65 degrees 65 degrees 50 S 40 degrees 40 degrees 60 S 30 degrees 30 degrees 90 S 0 degrees 0 degrees Before we can start calculating a time or a date, a few things are important to know, namely: The more towards the equator, the more difficult it can get due to the fact the sun has a more flat trajectory than anywhere else The easiest calculation is when the image is taken where the shadow is showing horizontally in the image, or there is an easy way of measuring the length. If there is an indication the scene might be slanted, it is no problem to rotate it slightly to make it easier for yourself Shadows that are in an angle or coming towards you, aren’t easy to measure, unless it falls on a surface that enables measuring the length in an accurate manner It is the best if shadows are fully visible and clear enough to be measured When a shadow is not fully visible, it is still possible to use it to calculate a possible time, since only a direction is needed, but finding dates can pose problems since the length of the shadow is needed Try not to work with shadows where the surface is warped or uneven, unless you are equipped to work with that by, for instance, using 3D modelling to recreate the scene Both the object and shadow it casts, should be measured within a single frame, so that the relation between object height and shadow length can be determined When using different frames from a film clip, distances can vary and therefore might make measurements less accurate Some reference point is needed to determine the exact direction the shadow is falling towards If all these conditions are met, then it is not only possible, but even fairly easy to determine the date and time when that photo or video was taken. ↑ Table of Contents 6.1. Basic Time Calculation As a first example, we'll go over an old Quiztime question, with a photo that was taken on Thursday, June 7, 2018. The date was given, and the time had to be determined. Example of a chronolocation quiz at @Quiztime For this, we first need to find the exact location of this image. This isn't so difficult, and after some reverse image searching, it gives us the answer: It's a large artwork at the foot of the Atomium in Brussels. We only need to establish where it is located exactly, and from which angle the photo was taken. Welcome sign at the base of the Atomium Measuring the angle of the artwork, gives us a deviation of 5 degrees, in comparison to true north. We can measure this fairly easily by using the ruler in Google Earth Pro. Measuring the azimuth in Google Earth Pro Looking at the image itself, we can see a shadow that was cast by the woman standing in front of it. This gives us the indication that the sun was standing south, with an azimuth of 185 degrees. When we line up the base of the artwork (green) with the direction of the shadow (red), we see that they run nearly parallel. Estimating the direction of the shadow If we want to be even more precise, we can zoom in on the image itself to check whether the shadow is indeed in line with the artwork itself, or slightly off. When we look at the shadows, it seems that there is a slight difference, but the difference is so small, that this would be maybe half a degree deviation. Looking at all the details To find out what time this was possible, we open the website SunCalc . We first need to find the exact location, and for that we can simply search for 'Atomium' ( A ), and it'll give us a list of possible locations. Selecting the location in Brussels, we then set the date to June 7, 2018 ( B ) by clicking on the date field. We can then move the slider on the top bar ( C ) until we get close to the desired azimuth. To get as close as possible, we can adjust the minutes manually, by clicking on the time field, and adjusting it accordingly. The time given on the website is in local time, and is adjusted for daylight saving time automatically. Finding the correct azimuth After matching the altitude and azimuth of the sun, we find that the time that this photo was taken was around 13.53 local time. The actual time was around 14:00, which is only a few minutes off, which is a good result. ↑ Table of Contents 6.2. Date and Time Calculations A more difficult task is to try and find a time and date. For this, we also need to look at the altitude of the sun, besides the azimuth. Since the height of the sun is changing throughout the seasons (remember the 'low sun' during winters in the Northern Hemisphere), we need to take that into consideration. To calculate a possible date and time, in general the following steps are necessary: Bring down the rough time range to one year Determine the exact location Determine the azimuth (direction) of the sun Determine the altitude (angle) of the sun Find all corresponding moments in time Eliminate seasons After that, there should only be one specific moment in time left. If this moment is very close to a solstice, it is possible that two moments in time match. This will need further elimination, if at all possible. To see how this process works, I'll use the following Quiztime challenge by Julia Bayer : Another quiz from @Quiztime The first step is to find the location. This turns out to be the Haus der Kulturen der Welt , on the river Spree in Berlin. We'll need coordinates of the possible location in a bit, so we write them down: 52.5195441,13.3649990 . The second step is to determine the height of the object and the shadow length, so we can determine the angle of the sun. Do make sure you select the correct point when visualizing the path of the sun rays. Imagine how the rays hit a specific part of the glass, and where on the surface they cast a shadow. Visualizing the sun rays One option to calculate the altitude of the sun is by measuring the amount of pixels, both for the object height and the shadow length. For this you can use Photoshop, The Gimp, or any other program that enables you to load an image, and to draw a line to measure the amount of pixels. Because it's irrelevant what units of measurement we use, we don't need to use millimetres or metres. What we are interested in, is the angle between the vertical and horizontal plane of the right-angled triangle we created. By entering the height as the amount of pixels of the object in Suncalc, we can then slide the sun left and right until we have the desired length. Another option is to calculate the angle manually with the following formula: α = arctan(height / shadow length) If it's been too long ago that you've used a calculator, or rather like to use online tools, then there are multiple websites that can help you. One of them is the website calculator.net , that have a module for right triangles. Fill in the height of your object under a , and the length of the shadow under b . After pressing the button, the altitude of the sun will be calculated and shown as α . Whichever method is used, this will give us a value of about 25,6 to 25,7 degrees altitude. If we want to find out at what moments in time this altitude and azimuth occurred, we'll be using the website SunEarthTools.com . On the website, we pick the menu option 'Sun Position'. This page has several tools that revolve around the location of the sun. The option that is most interesting is the 'Annual sun path' section. You can scroll down, or jump to it straight away by clicking the option directly under the map section. Generating an Excel sheet I've noticed that the adjustments for daylight saving time isn't working as it should. I've turned that option off, and calculate everything in time zone GMT+0. I adjust the times later on. This option will generate an Excel sheet with altitudes and azimuth of the sun throughout a whole year, based on a given location. For this we fill in the details, like the location and the year, and then choose and the steps, or increments. The sheet can be generated in increments of 5, 10, 15, 20, 30 or 60 minutes. In general, I would say: The closer to the equator, the smaller the increment. For this an increment of 15 minutes is enough, and will generate a sheet of about 1MB in size. In this case, I chose the previously mentioned coordinates: 52.5195441,13.3649990. It technically isn't really an Excel sheet, but an HTML table. Excel will give a warning when opening it, and will convert it accordingly if you continue. After opening the sheet it'll show all the dates of the year in the first row, and in the columns it'll have the different times in 15 minute increments. Per timestamp, it has one column starting with E for elevation, and one starting with A for azimuth. To visualize what I'm looking for, I personally like to highlight cells that fall in between certain ranges by using the 'Conditional formatting' option. This option is also available in the open source app Calc in LibreOffice. In this case, the altitudes and azimuths are far apart, so it's enough to create two rules for the whole sheet, where cells will be highlighted in different colours when they fall in between different values. If the azimuth and altitude are very close together, consider using the same colour for highlighting, or create a rule for the different columns. To do this, pick the menu item 'Conditional Formatting' and use the option: Highlight Cells Rules - Between . Conditional formatting in Excel This option gives us the ability to highlight cells that have a value within a specific range. To find the possible values for that range, play a bit with SunCalc and move the sun back and forth, to get a rough idea what the direction of the sun could be. Find the minimum and maximum values for the azimuth, by comparing the direction of the shadow to the image or video you're investigating. After determining these values, the altitude was determined to be between 26 and 27 degrees, since that is the angle of the shadow. The azimuth has to be somewhere in between 262 and 264 degrees. After assigning different colours to these values, a pattern will emerge within the sheet, as can be seen below. Creating formatting rules Depending on the language settings on your system and in Excel, it's possible that the numbers will be seen as text and the cells won't be highlighted. To correct that, select all the cells by clicking in the left top corner, or pressing Ctrl-A or Cmd-A, and replace all periods with a comma. After that, it'll be easy to find the possible times by looking at the moments where both the altitude and azimuth fall between the ranges we provided. The only period where this is possible is between August 3 and August 7, 2021 around 16:45 in the afternoon. Given the fact that Julia mentioned the photo was taken on a Thursday, there's only one option left. Finding matching values If you're not using Excel, or any open source options like LibreOffice, another option is to go over SunCalc.org manually and pick two or three dates per month, until the altitude and azimuth gets closer to your desired values. After a rough period has been established, it's possible to move towards the desired dates. But by using the export provided by SunEarthTools , it's possible to determine a possible time frame easily, quickly, and accurately. ↑ Table of Contents 7. Tips and Tricks Accurate chronolocation is only possible if there's enough information to go on. But there are times when the media being investigated is hard to interpret. Shadows might be coming from different directions, or hard to make out. Or the photo doesn't lend itself for accurate measuring of the shadows. But usually there are always some things that can be tried, to enhance a photo, or work with the information that is visible. 7.1. Hard to See Shadows There are moments when a shadow isn't very visible, but there are ways to enhance the image to make measuring more easy. There are different options you can use, to make the shadow more visible. Within Photoshop for instance, tools that could help are: Inverting the image Adjust the brightness and contrast Change the exposure or exposure offset Enhance the shadows An example of an old Quiztime quiz , where such adjustments have been made can be seen here: After Before ↔ Comparison slider might not work on mobile Using that same photo of the fire department pickup, there's another thing that's just about visible. When zooming in on the windows, the brightest part of the sky is on the right side of the visible windows. Since the shadows seem to indicate that the sun is nearly in a direct line of our viewing direction, it makes sense that there is a possibility that the sun is visible in the reflection, here marked in yellow. Finding the sun in reflective surfaces Make sure to investigate a photo or video, and look for any clue that might help you in any way to determine the location of the sun. 7.2. Shadows in Different Angles If the shadows on the photo of video are not aligned horizontally, it will make measuring the exact angle more difficult. Since we live in a three-dimensional world, the length of a shadow is sometimes difficult to measure when it's falling towards you. Here are two examples, both taken in the same area. GOOD! Shadows are horizontal - © Volker Meyer, Pexels BAD! Shadows are falling towards you - © Lina Kivaka, Pexels Luckily there are possibilities to measure the distance of a shadow fairly accurate, by using elements of the environment as guidance. Try and find items of which the exact size can be determined, of find something that can be used to measure the shadow as accurate as possible. Street tiles can be extremely helpful, by using them as a grid, for instance. Let's have a look at an example, again at the Louvre, where the shadow is not plotted horizontally on the image. It is still possible to use the tiles as a grid, and calculate where the shadow would be when positioned horizontally in the photo, therefore making a calculation possible. First we need to establish where we would like to have our shadow in the image, and draw a horizontal line that we'll use for guidance later on, so we can determine were the shadow would fall if it would be rotated anticlockwise. Visualize where the shadow should be for our measurement Next we recreate the grid with the correct proportions, and we will recreate the position and length of the shadow. This can be a simple line, from the object, or in this case a person, to the furthest point of the shadow. Recreate the grid and shadows Then we draw a circle in our grid, where the centre of the subject itself is also the centre of the circle itself. To find the centre, visualize how the highest point that is able to create that shadow, extends directly downwards to the ground. This will be the centre that we need to use to draw a circle. The radius of this circle extends towards the end of the original shadow, show here in yellow. Plotting a rotated shadow that can be measured After lining up the horizontal line in the photo, and the radius of the circle, we find a new point where the shadow would fall, if it would be rotated anticlockwise. When measuring the original image in Photoshop, I found a length of 830 pixels. When comparing this to the length of the original shadow in the image, we find that it's only 625 pixels long, and therefore roughly 30% too short to be used for an accurate calculation. 7.3. ShadowCalculator If it's unclear what a shadow, for instance cast by a building, could look like in a specific area, then it's possible to recreate it using freely available tools. One of the simplest ones I've found so far, is ShadowCalculator . It has the option to create a virtual building on top of Google Maps, placing points on the map to create a shape. Quick example of the Dam Palace in Amsterdam Every point in the shape can have its height adjusted, making somewhat more complex shapes possible. By adjusting the date and the time on the right side of the screen, the shadow and its shape will be adjusted on the map. 7.4. Warnings and Pitfalls When going over images and videos, looking for shadows, there are a few things to be careful about. If you're new to the game, there are some situations that could lead you to different dates or times. One thing to be careful about, are clouds in the sky. Sunlight that travels through a cloud can scatter the sunlight, whereby the clouds are acting as a diffuser . This will make the edges of the shadow harder to distinguish, information we actually need to determine a correct altitude. Besides that, it can also make it very hard to distinguish the shadow from darker surfaces like asphalt. Clouds acting like a diffuser Another thing to be wary about are reflective surfaces. Especially in modern cities, with large glass facades, with reflective windows. Looking at the example, we can clearly see the sun being reflected in the large building, thus sitting in a location somewhere left of the photographer. But due to the reflective surface of the building, all the shadows fall towards us. Photo © Matheus Bertelli, Pexels To determine the exact direction of the sun, one would have to zoom in onto the right bottom of the photo. The woman walking there is not lighted by the reflection of the sun. By using this bit of information, it's possible to determine the correct location of the sun after all. Pay attention to details ↑ Table of Contents 8. Conclusion This concludes this comprehensive guide on chronolocation, and I hope it gives some tips, tools and hints for people that are just starting out with this. The most important thing in chronolocation is always: Pay attention to details, verify what you're seeing, and use knowledge or information about a specific area to get a better understanding of the situation. Whether it's asking an expert to determine whether crops are harvested already, searching the internet for information on dry and wet seasons, what plants are flowering at any given time and so on. By combining all that information, and looking at multiple sources to narrow a time window down to a year or a few months, it's time to dive into the details. Hopefully you have shadows that can guide you, or maybe there's a sale at a shop that is visible in an image you're working on. It doesn't matter how small the clue, sometimes a simple no-parking sign can break a case open and enable you to determine the exact date within reach. So go out, take some photos in different situations, or go over your old archives, and practice. Make sure your EXIF information is correct, and see whether you're able to find out when you took a specific photo. I'm closing off by saying that this guide is not finished yet, and will probably receive some updates in the upcoming months or so. There are also some topics I want to include over time, expand on certain paragraphs, or write down some tips even more clearly. But due to time constraints (I know! It only took me over 3 years), I had to finish this guide to be released early November 2021. 8.1. Glossary Altitude The term altitude is used to describe the angle in degrees of the sun in relation to the earth's surface. An altitude of 0° means at ground level, and 90° means directly overhead. Arctan The arctan is the inverse trigonometric function of the tangent function, which is the ratio of the side opposite an angle divided by the side adjacent to the angle. It is used in the following formula, that calculates the angle, or altitude, of the sun: α = arctan(height / shadow length) Azimuth This term is used to describe the direction where the sun is standing, in relation to true North. This means that at an azimuth of 180°, the sun will be in the south. Diffused light Diffused or soft light is the situation where the sunlight is scattered. This can be due to clouds, or because the sun is set very low, and bounces off the atmosphere. Equinox An equinox is the moment the plane of Earth's equator is at a 90-degree angle with the sun, so the centre of the visible Sun is directly above the equator. This occurs twice each year, around March 21 and September 23. Solstice The solstice is the moment where the sun is the furthest away from the equator, and happens around June 20 or 21, and December 20 or 21. They are called respectively the Summer Solstice, and Winter Solstice. In June this results in the longest day of the year, and the shortest day in December, when you're in the Northern Hemisphere, and vice versa in the Southern Hemisphere. SunCalc SunCalc is a tool that enables you to recreate the location of the sun during any moment in time, at any location on earth. The link to the website is: https://www.suncalc.org/ SunEarthTools The website SunEarthtools provides multiple tools that can be used to create an overview of sunrise and sunsets, or export Excel sheets with altitude and azimuth information. The link to the website is: https://www.sunearthtools.com/ Acknowledgement First, I want to thank everybody of the Quiztime crew for sending out daily verification quizzes. I've learned a lot from these, and have been able to broaden my knowledge over the last few years. I also want to thank Christiaan Triebert and Aliaume Leroy for taking the time to review the information and giving tips. And most of all I need to thank someone very special to me, who had to miss me for hours on end, while I was writing paragraph after paragraph, and doing research during holidays. ↑ Table of Contents Previous Post Next Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/2/8/3/7/3/283738aec7fb54aa80a90926a98252c8717238bb-chrono-enhance1b.jpg","https://sector035.nl/images/3/7/5/b/f/375bffcdb336d230ad7ad19758b4489c2b7d1650-chrono-google-earth-pro2.jpg","https://sector035.nl/images/6/0/3/e/c/603ec54776f4afd3ab7b0d45d338348420ab994a-chrono-birmingham-2020.jpg","https://sector035.nl/images/a/b/1/a/f/ab1af4920befc0dcf4693f562b53dc5c7965506f-chrono-birmingham-2021.jpg","https://sector035.nl/images/e/0/6/4/6/e06468ea027c89542056c00b68115ee96030ef64-chrono-google-earth-pro1.jpg","https://sector035.nl/images/e/e/8/0/9/ee80933ac825fb0e4b7650d1164d7afea746a3e8-chrono-enhance1a.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-angles1.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-angles2.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-atomium.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-atomium3.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-atomium4.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-atomium5.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-chestnut.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-earths-motions.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-excel1.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-excel2.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-excel3.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-exif.png","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-google-earth-pro.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-orlando.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-shadow-measure1.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-shadow-measure2.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-shadow-measure3.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-shadowcalculator.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-suncalc.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-sunearthtools1.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-tip1.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-tip2.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-tip3a.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-tip3b.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-tweet-berlin2.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-tweet-brussels.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-tweet-fiete.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-tweet-julia.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-tweet-mcantow.jpg","https://sector035.nl/user/pages/articles/chronolocation-of-media/chrono-workflow-new.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_ee6bd9beb826_0.jpg","blog_data/images/blog_ee6bd9beb826_1.jpg","blog_data/images/blog_ee6bd9beb826_2.jpg","blog_data/images/blog_ee6bd9beb826_3.jpg","blog_data/images/blog_ee6bd9beb826_4.jpg","blog_data/images/blog_ee6bd9beb826_5.jpg","blog_data/images/blog_ee6bd9beb826_6.jpg","blog_data/images/blog_ee6bd9beb826_7.jpg","blog_data/images/blog_ee6bd9beb826_8.jpg","blog_data/images/blog_ee6bd9beb826_9.jpg","blog_data/images/blog_ee6bd9beb826_10.jpg","blog_data/images/blog_ee6bd9beb826_11.jpg","blog_data/images/blog_ee6bd9beb826_12.jpg","blog_data/images/blog_ee6bd9beb826_13.jpg","blog_data/images/blog_ee6bd9beb826_14.jpg","blog_data/images/blog_ee6bd9beb826_15.jpg","blog_data/images/blog_ee6bd9beb826_16.jpg","blog_data/images/blog_ee6bd9beb826_17.bin","blog_data/images/blog_ee6bd9beb826_18.jpg","blog_data/images/blog_ee6bd9beb826_19.jpg","blog_data/images/blog_ee6bd9beb826_20.jpg","blog_data/images/blog_ee6bd9beb826_21.jpg","blog_data/images/blog_ee6bd9beb826_22.jpg","blog_data/images/blog_ee6bd9beb826_23.jpg","blog_data/images/blog_ee6bd9beb826_24.jpg","blog_data/images/blog_ee6bd9beb826_25.jpg","blog_data/images/blog_ee6bd9beb826_26.jpg","blog_data/images/blog_ee6bd9beb826_27.jpg","blog_data/images/blog_ee6bd9beb826_28.jpg","blog_data/images/blog_ee6bd9beb826_29.jpg","blog_data/images/blog_ee6bd9beb826_30.jpg","blog_data/images/blog_ee6bd9beb826_31.jpg","blog_data/images/blog_ee6bd9beb826_32.jpg","blog_data/images/blog_ee6bd9beb826_33.jpg","blog_data/images/blog_ee6bd9beb826_34.jpg","blog_data/images/blog_ee6bd9beb826_35.jpg","blog_data/images/blog_ee6bd9beb826_36.bin","blog_data/images/blog_ee6bd9beb826_37.bin"]}
+{"source":"sector035","url":"https://sector035.nl/articles/lake-constance","title":"","status":"ok","retrieved_at":"2026-08-29T16:13:47.450464+08:00","text":"Lake Constance - Geolocation | Sector035 Lake Constance - Geolocation Home Week in OSINT Articles Search Lake Constance - Geolocation 2nd Dec 2024 maps geolocation quiztime aerial imagery It has taken well over 7 years before this geolocation challenge was resolved, and I have spent countless hours on trying to find this years ago. Sadly enough, work and other priorities had taken over my life, so the last three years I didn't have time to look at it at all. Until recently, when I managed to find the location of this exact spot, but it wasn't in the usual way. The original Tweet Bask in 2017 the Twitter user @CountryTec sent out a tweet, asking for help on locating a specific image from the 50's. This is the original tweet: CountryTec, reaching out to the public for help The tweet translates to: I have this photo with my parents taken around the 50's. Does anybody know where this is? Please #RT One of the first questions that was asked, was what could be written on the monument, and @CountryTec already had a look at that, and with the help of some other people, the deduced it said something along the lines of: \"... SCHWEIZ IN DANKBARER ERINNERUNG AN DIE EISERNE ZEIT ...\" Or, translated: \"... Switzerland in remembrance of the iron age ...\" The German term \"Eiserne Zeit\" is usually for the thirty years' war , that lasted from 1618 to 1648, but it was uncertain whether this monument was that old. People also hinted that in the middle of the monument, on both sides of the inlay, there were the numbers 14 and 18, which may hint towards the first world war. In July 2018, @CountryTec shared it again, where it received some attention once more. This time, the Twitter account @Quiztime was tagged, after which the Quiztime crew received this challenge. This was the time I saw it, and some great work had been done so far already! The information that was known by then was: Taken somewhere around the mid-50's Most part of the text was known Most probably around Lake Constance Might be around Arbon, Seepark Rorschach or Lindau Looking back at it now, this may have been enough to actually solve it. But it turned out, there was a problem. Spoiler alert, the monument was removed! How it Started Looking at most of the information that was available, I tried to have a stab at it with the @Quiztime crew, working closely together with mainly Fiete Stegers [ ]. It seemed a somewhat straightforward quest, and there are certain ideas on what might help geolocate this, like: General reverse image search Use AI to colour the image, for aid in searching Search, in German, for monuments Go over public records and local websites After spending some time doing that, I found that nothing came up. Google, Bing and Yandex showed some monuments that looked similar, but there were no matches to be found. Me and a few people went over some websites, databases, social media, but without any results. Looking at Shadows At a certain point, I wanted to know what direction we might be looking, since it might help in finding, or excluding, certain locations. For that, I made some assumptions and tried to measure the shadow that was visible in the image. The first assumption was a rough estimate of the height of the man, and the second was a rough estimate of how long the shadow might be. The third assumption was the idea that this photo was taken in the summer. I based that on the fact that the shadows looked sharp, due to a bright sun, and the way the people were dressed. All combined, I had the following pieces of information in mind: Somewhere in Switzerland, near Lake Constance Looking at the background, we are facing a lake Somewhere in summer time The height of the person around 1.75m Length of the shadow was estimated around 80cm Drawing in the shadows Going over to one of my favourite tools for shadow calculations, I opened up SunCalc . I went over several dates, and found that August and September were throwing shadows that were too long, making it impossible to find a match. Going back to July, I was able to have the sun high enough in the sky that a shadow of about 80cm or so was possible. And it turned out that the sun would have been roughly south. This could be southwest, or southeast, but with all the assumptions made, it was impossible to narrow it down any further. Finding a general direction of the sun Since there had been an idea the photo might have been taken around the area of Arbon, Lindau or Seepark Rorschach, which are all south of Lake Constance, this meant people were on the right track. The Breakthrough More than six years after I started this quest, where I was not constantly searching, but once every couple of months I would revisit this and look for a new information, it was still unsolved. That was until on November 28, 2024, I went back to the challenge and looked at all the comments to see whether there was any new information. And there certainly was! A new lead, out of the blue Someone who had been looking at the request managed to find some old postcards on a Swiss website, giving an extra hint towards the exact municipality we were looking for: Horn. And there wasn't just a single postcard from Horn that showed this location, but I managed to find 4 in total. The location, with the name 'Horn' According to the Wikipedia page , Horn lies in the district of Arbon, which was mentioned earlier too. Looking back now, and knowing all the information that was available back then, I am certain we could have solved this well over six years earlier. But having other priorities in life, these things sometimes move to the bottom of the stack, and when you see new information, like Phaedrus' [ ] his tweet with the postcard, it relights your interest once more. And this time, we needed to finish it all the way. Old Maps and Photos To find out where the monument could have been, I had a look at older maps from the area. Using the historical maps from the Federal Office of Topography Swisstopo, I compared the map of 1960 to the one of a later date, like 1975 . And there was an interesting change, because somewhere around the area where I expected the photo to have been taken, the whole area changed. Instead if a small bulge, a large part of land has been added. You can see the comparison below, but sadly enough it doesn't seem to work on a mobile phone. 1975 1960 ↔ Changes in the landscape between 1960 and 1975 On the website of the Swisstopo office, there is also the option to dive into historical aerial photos. And after going over about 10 or so different images, I chose to show the location as it was in 1935, and in 1972. This clearly shows not just the scale of what has been done to the area, but the image in 1935 also shows the water feature near some trees. 1972 1935 ↔ Aerial photos of 1935 and 1972 Here is another detailed aerial shot, taken in June 1945, also taken from the website of Swisstopo. Zoomed in, it clearly shows a half circle, a line of trees, and something that resembles a water feature in the center. The water feature, as it was in 1945 On the website of Wikimedia , Fiete Stegers [ ] found an aerial shot of Horn, made by Werner Friedli in May 1949. After downloading the original image, and zooming in onto the location where the water feature must have been, we can clearly spot the rough outline of the center part of it. Aerial photo, taken in 1949 Verification Stage Since we now had a very strong lead this might be the correct location, and it seemed to match with old maps and aerial photos, it was time to go back and look at the postcards more closely. It was time to go over to Google Earth Pro, GoogleMaps, PhotoShop, and try to line everything up nicely. Measuring the ratio of the distance between the churches or towers that are visible, wasn't a perfect match with the old photographs. But the shape of the churches A ( Kirche St. Martin ) and C ( Pfarrkirche St. Jakobus ) do match the general shape that can be seen in the postcard. The only one that is slightly more difficult to see, is church B ( Evangelische Kirche Arbon ), but given the fact that we are working with digital versions of very old postcards from decades ago, it was the best I could do. Trying to line up the view with the postcard Time to find out more about what happened in this area back then. Diving into History Now that we were fairly certain the location is correct, and we even find a part of the landscape changed, we need to find out what happened to the monument. And for that I dove into the state archive of Thurgau, searching for the term I learned while looking into this topic: \"Quaianlage\", or lakefront. In the archive I was able to find another postcard, with some more information about this monument ( in German ). The text explains that it was a water feature created by Louis Wethli (1867-1940) and was donated by a German merchant called Alfred Heinrich Klinkmann (1871-1943). Alfred worked in Milan until the first world war, and chose to move to Horn during this time. Out of gratitude for the hospitality, he commissioned a new water feature, that has been described as a \"bench protection\". He turned to the Zurich sculptor Louis Wethli, who built it between 1927 and 1928. When in 1969 the lakefront was redesigned, it was removed completely, and only returned on the so called \"Festplatz am See\" in 1997. Going over Google Maps and StreetView, we don't see anything that looks like the monument as we have been seeing on the postcards though. But one thing stood out, right on the edge of the \"Festplatz am See\", a stone feature ( Google Maps ) What is left of the monument It is very hard to make out, so it is time to have a better look at photos taken in the nearby area. And it doesn't take long before we find an image by Antoine Meyer. In that image, we can see details of the carvings, and comparing them side by side shows elements that absolutely match with the original from one of the postcards. The female figure is mostly hidden in the shadows, and no PhotoShop magic will be abel to enhance that. But the rough shape of her arms are still visible, and looking at the posture of the child on the right, it all matches nicely. Comparing the carvings And when we load the image in PhotoShop, and look at the text on the plaque, we are able to recover most of the text, that was characteristic of the original monument: \"DER GASTFREUNDLICHEN SCHWEIZ IN DANKBARER ERINNERUNG AN DIE EISERNE ZEIT DES WELTKRIEGES\" Underneath there seems to be some more text, but I wasn't able to fully reconstruct the full sentence. But after a tip from Louise [ ], who contacted me by email, the most probably option is the following line: \"1914 - 18 VON EINEM GÖNNER DER GEMEINDE HORN\" Loosely translated, it reads: \"The hospitable Switzerland in grateful remembrance of the iron age of the world war. 1914-1918 by a patron of the community of Horn\" Trying to make the text slightly easier to read Conclusion After well over 7 years after the original question was posted online, and thanks to the help I received from Fiete Stegers [ ] and the unsung hero over on X, called Phaedrus [ ], we were able to finish this chapter. By a complete overhaul of the landscape, it turned out it was rather difficult to find the location, yet not impossible. Due to this challenge, I found much more useful resources, found out there are way more historical aerial photos than I knew, and combined all sorts of techniques to verify everything. And after I posted my last message about it on X at 10:30 PM, it took some random account less than two hours to claim he or she found it, via a post on Reddit. Jumping in on the bandwagon, replying to a different thread about this photo, trying to take all the credits. If there is one person that deserves credits, it is Phaedrus [ ], who gave everyone a nudge in the right direction after several years, by finding the postcards. Don't do this... Previous Post Archives December 2024 October 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 Syndicate Atom 1.0 RSS Home Week in OSINT Articles Search","image_urls":["https://sector035.nl/images/0/4/9/4/a/0494a0984b06e27ea65204be73ea260a60832770-horn-1935.jpg","https://sector035.nl/images/1/3/c/f/3/13cf34c35a0a1ca9beb03e5d4dbfcac947f297f7-horn-map-1960.jpg","https://sector035.nl/images/2/4/c/d/a/24cdac4d513189b7ab78a776ba365482294bcd4a-horn-1972.jpg","https://sector035.nl/images/3/9/3/4/4/39344e26805320ac5cfa5f9ab1e2212a13917476-horn-map-1975.jpg","https://sector035.nl/images/e/8/1/a/9/e81a91dfeb9ae10fc986c6263e8613fc90dafc9c-tweet-countrytec-2017-07-24.jpg","https://sector035.nl/user/pages/articles/lake-constance/aerial-1949.jpg","https://sector035.nl/user/pages/articles/lake-constance/carving.jpg","https://sector035.nl/user/pages/articles/lake-constance/google-maps-photo.jpg","https://sector035.nl/user/pages/articles/lake-constance/horn-1945.jpg","https://sector035.nl/user/pages/articles/lake-constance/map-view.jpg","https://sector035.nl/user/pages/articles/lake-constance/marvin-tweet.jpg","https://sector035.nl/user/pages/articles/lake-constance/postcards.jpg","https://sector035.nl/user/pages/articles/lake-constance/shadowcalc-1.jpg","https://sector035.nl/user/pages/articles/lake-constance/shadowcalc-2.jpg","https://sector035.nl/user/pages/articles/lake-constance/text.jpg","https://sector035.nl/user/pages/articles/lake-constance/tweet-phaedrus.jpg","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-250px.png","https://sector035.nl/user/themes/quark-open-publishing/images/logo/sector035-logo-400px.png"],"local_images":["blog_data/images/blog_f02c247450c2_0.jpg","blog_data/images/blog_f02c247450c2_1.jpg","blog_data/images/blog_f02c247450c2_2.jpg","blog_data/images/blog_f02c247450c2_3.jpg","blog_data/images/blog_f02c247450c2_4.jpg","blog_data/images/blog_f02c247450c2_5.jpg","blog_data/images/blog_f02c247450c2_6.jpg","blog_data/images/blog_f02c247450c2_7.jpg","blog_data/images/blog_f02c247450c2_8.jpg","blog_data/images/blog_f02c247450c2_9.jpg","blog_data/images/blog_f02c247450c2_10.jpg","blog_data/images/blog_f02c247450c2_11.jpg","blog_data/images/blog_f02c247450c2_12.jpg","blog_data/images/blog_f02c247450c2_13.jpg","blog_data/images/blog_f02c247450c2_14.jpg","blog_data/images/blog_f02c247450c2_15.jpg","blog_data/images/blog_f02c247450c2_16.bin","blog_data/images/blog_f02c247450c2_17.bin"]}
diff --git a/blog_data/by_source/wanderingjackdaw.jsonl b/blog_data/by_source/wanderingjackdaw.jsonl
new file mode 100644
index 0000000000000000000000000000000000000000..a1ad84056bc6b379b760431ba2fe3934d9b04371
--- /dev/null
+++ b/blog_data/by_source/wanderingjackdaw.jsonl
@@ -0,0 +1,33 @@
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/challenges/","title":"Challenges","status":"ok","retrieved_at":"2026-08-29T16:07:25.876844+08:00","text":"Challenges Here you'll find a collection of challenge exercises I've made for you to practice OSINT research skills with. Challenge 01: Pet the Dog Challenge 02: Out on a Walk  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/02_outonawalk.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/pet_the_dog.webp"],"local_images":["blog_data/images/blog_e4721ca9ef8f_0.bin","blog_data/images/blog_e4721ca9ef8f_1.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-a-very-cold-case-challenge/","title":"82. A Very Cold Case","status":"ok","retrieved_at":"2026-08-29T16:12:29.320431+08:00","text":"Walkthrough for Bellingcat's 'A Very Cold Case' challenge 09 Jul, 2026 Hi, welcome to this write-up for the A Very Cold Case challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. The challenge We've received an audio file with a radio programme covering the results of a Winter Olympics event. In the audio three different anthems can be heard partially. We have to find the date on which this medal ceremony took place. The first assumption When I listened to the anthems, I didn't recognize any of them. To be honest, I'm not that good recognizing sounds of any type. I feel awkward asking others for advice, because I sometimes get the (unwarranted) feeling that I have to do everything 100% myself or it doesn't 'count' (whatever that may mean). However, I'm starting to learn that finding and asking others for information they have on hand is a useful path to take. So, I played the audio for someone I know to see if they could give me a first clue. They said they recognized two anthems. They claimed the first part was Russia's national anthem and the third part was Germany's. Now I had a place to start. Assuming this information was correct, then I'd have to find a Winter Olympics event where the final medalists were from Russia, Germany and a third not yet known country. If I could find that event, then I could find the date when those medals were awarded. My plan was to check the Winter Olympics year by year, event by event, until I spotted an event in which Russia, Germany and another country had placed top three. Then I'd look up the anthem of that country and compare the audio. Straightforward, no? Russia hasn't been competing in the Olympics for a while, or at least not officially with their own anthem and such. I tried to look up what years Russia joined the Winter Olympics under their own banner and ended up at this link . Since the 2018 Winter Olympics athletes from Russia competed as ROC. So, I decided to work my way backwards starting with the 2014 Winter Olympics. Instead of checking each and every event at the Winter Olympics, I only had to check events with a Russian or German medalist. Knowing that Wikipedia has specific pages per country per Olympic year, I decided to stick with Russia and check year per year from there. Checking 1994-2014 I started in 2014 and worked my way backwards through the years. I used the Wiki page for Russia's acitivity at the Winter Olympics . Then I scrolled to the Medalists section. For every medal won, I went through the following process: Open the linked Wiki page for the relevant medal's sport event in the subsection Event (for example pair skating or ladies' singles etc) in a new tab. Check if the three medalists in the clicked event are a combination of Russia + Germany + a third country. If not, leave and go to the next event. If yes, look up the national anthem of the third country on Youtube, listen and compare it to Bellingcat's audio file. If the audio didn't match, note down the country as not it . They could be ignored in following events. Repeat from top. For 2014 I checked Latvia's anthem because of this event , Italy's anthem because of this event and France's anthem because of this event . All three weren't a match, so on to the next year. For 2010 I checked for Sweden and Norway , but no luck either. For 2006 I had to check Switzerland and Canada . No match. In 2002 the only new country that popped up was Bulgaria , but it didn't match the original audio either. In the 1998 Winter Olympics I found no new country combination. For 1994 I could check out Austria , but no. What was up with that? Huh? Oh!! I was temporarily confused. I thought I was dealing with Germany and Russia's national anthem, but I had checked every Winter Olympics year and hadn't found a match yet. The only countries to ever share the stage in 1994-2014 with both Germany and Russia were Austria, Bulgaria, Canada, Switzerland, Norway, Sweden, France, Italy and Latvia, and all of their anthems didn't match the original audio. Now the only Winter Olympics left were in earlier years, when Germany and Russia didn't even exist in their current form yet. How could that be? Then the penny dropped. I checked the audio for the USSR and it was a match with Bellingcat's audio. Then I checked for West Germany, and it matched too. I wasn't dealing with German and Russian medalists, but with West German and Soviet ones! I still had to find that third country, but now I knew how to look through earlier years. I repeated the same process as before, but now checked events for wins by USSR + West Germany + new third country. Checking before the 1990s From the Russia at the Winter Olympics Wikipedia pages I switched to Soviet Union at the Winter Olympics pages. I began at 1988 to once again worked my way backwards in time. The first new option I found was Czechoslovakia . They didn't win a medal in this event, just placed third in group B. Still, since two of the anthems were from countries that no longer existed in their past form, I wondered if the third would be as well. I looked up the national anthem of Czechoslovakia et voila! I had found the third anthem that is audible in Bellingcat's audio file. Now I just had to find an event where the Soviet Union, West Germany and Czechoslovakia shared the stage. Since I expected Czechoslovakia to have won fewer medal than the Soviet Union in the Winter Olympics, I switched to the Czechoslovakia at the Olympics Wiki pages so I'd have to check fewer possible events. I checked 1984 , 1980 , and when I reached 1976 I found an event with the three right medalists. Ice hockey at the 1976 Winter Olympics resulted in gold for the Soviet Union, silver for Czechoslovakia and bronze for West Germany. The event took place from 2 to 14 February 1976. Since usually sport medals are awarded right after the last match of the last day of the event, I assumed that these medals too would be awarded on the last day: 14/02/1976 . This turned out to be the correct answer.  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/001_russian_medals.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/002_wiki1976.webp"],"local_images":["blog_data/images/blog_66aca278d799_0.bin","blog_data/images/blog_66aca278d799_1.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-among-the-roots-challenge/","title":"48. Among the Roots","status":"ok","retrieved_at":"2026-08-29T16:09:43.331048+08:00","text":"Walkthrough for Bellingcat's 'Among the Roots' challenge 10 Aug, 2025 Hi, welcome to this write-up for the Among the Roots challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a picture of an item, partially buried in sand, dirt, stones, leaves and roots. It's quite hard to see. We know from Bellingcat's description that it's ordnance, but we have to find out what model and ordnance type. At a glance, the first things I noticed were: It's an arid environment, but some plants can still grow Because the object is partially underground it might be a mine of some sort It looks round and flat at the top The scale is hard to gauge, but with the size of the leaves, maybe it's the size of a big foot? I felt kind of at a loss of where exactly to start, so I decided to look even longer at the picture. What was I really looking at? With these new details, I felt more certain that it was a mine. I went over to CAT-UXO's page on landmines , but saw that there were 475 types to browse through. Oof. Maybe I could narrow that down somehow? Browsing around I decided to reverse image search Bellingcat's picture. I learned a lot about archeological finds of ancient pots, haha! But there were also quite some results relating to ordnance, especially on Yandex and Google. I didn't find the source of the picture, nor anything quite looking like the object in it. However, it did lead to a lot of articles about landmines and groups that clear landmines. They were interesting to browse. Some countries came up a lot in these articles: Yemen, Libya, Syria, Iraq, Iran and more. I noted some of these with arid environments down. Out of curiosity I once again visited CAT-UXO's website, went to their landmine page, and sorted by 'used in Yemen' . There were 30 results, and one looked like the shape of the object of the picture, hmm... Could it be the PMN landmine? Then I sorted by 'used in Libya' and only the PMN came close again. The flat top, the rounded edge, the distinct line dividing the item in two parts looked the same... But the colors looked very different. I felt like I was getting close to the model of ordnance, but felt unsatisfied with not really knowing the why and where behind the placement of this particular mine. Going a little meta Reading CAT-UXO's PMN landmine page , it stated that the mine is Russian. I began to think: the previous Bellingcat challenge in the Hidden Hazards category was about Russian ordnance as well. I looked up the name of the creator of the Hidden Hazards challenges: Andro Mathewson & Kate Millar. Clicking the names linked to Andro Mathewson's Linkedin page . Under experience it read: Project & Research Manager (Eyes On Russia) . Hmm, were we getting challenges based on ordnance used by Russia in their invasion of Ukraine? Ukraine does have some arid regions too... Back to CAT-UXO I went, and I now sorted the landmines by 'country of origin: Russia' and 'country used in: Ukraine' . There were 35 results. The PMN model showed up again and seemed to be the only one resembling the shapes in the picture. I still felt a little uncertain when I gave in the answer, because of the color differences. Could a mine weather in such a way, or be camouflaged in such a way, that it appeared fully sand color instead of its original brown/green/black-ish colors? Fortunately for me, the Bellingcat screen turned green. The correct answer was: PMN landmine .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-9.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-8.webp"],"local_images":["blog_data/images/blog_d6f6b79d8ea8_0.bin","blog_data/images/blog_d6f6b79d8ea8_1.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-charge-size-challenge/","title":"92. Charge Size","status":"ok","retrieved_at":"2026-08-29T16:12:41.956509+08:00","text":"Walkthrough for Bellingcat's 'Charge Size' challenge 02 Jun, 2026 Hi, welcome to this write-up for the Charge Size challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. The challenge This challenge contains one question: What is the minimum amount of TNT needed to shatter windows 30 meters away? In the first challenge in this series it became clear that an overpressure of 1 psi can shatter windows. So, in this scenario, the overpressure must be 1 psi at a distance of 30 meters away from the location of the TNT. How much TNT creates that level of psi at 30 meters? I tried to look for some type of calculator that would be able to estimate blast overpressure or damage. My first try at a search query into Google was: estimate blast damage I first arrived at this blast calculator , but I was unable to use it because I had no data about the angle of incidence. Then I was led to this blast damage estimation page from the UN. I found it a bit difficult to use, since it gives the blast damage in damage to windows, organs and houses. What counts as 'windows shattered' in this calculator? When one type of three has a chance of shattering? When they all do? I preferred a calculator that would show me the psi or kPa at a certain distance, so I kept looking around. On the same website of the UN, after browsing their menus, I saw this Kingery-Bulmash blast parameter calculator which seemed to include the parameters I was looking for. Since windows shatter at 1 psi, and since 1 psi equals 6.89476 kPa, I adjusted the amount of TNT until the incident pressure hit 6.89 kPa. This happened at 4.58 kg TNT. Surprisingly, this answer was incorrect. I scratched my head, but then remembered that the first challenge in this series required the user to round the kPa up to an integer, which meant that they worked with 7 kPa as the overpressure at which windows would shatter. I went back to the calculator and adjusted the TNT amount until an incident pressure of 7.00 kPa was hit, which happened at 4.75 kg. This number did make the screen turn green. So, the final answer is: 4.75 .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/img001.webp"],"local_images":["blog_data/images/blog_a2eb4c3881e5_0.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-denial-of-provenance-challenge/","title":"38. Denial of Provenance","status":"ok","retrieved_at":"2026-08-29T16:08:40.422007+08:00","text":"Walkthrough for Bellingcat's 'Denial of Provenance' challenge 16 Jul, 2025 Hi, welcome to this walkthrough of the Denial of Provenance challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but most likely there are many different ways of reaching the same results. Looking for the painting We've received a picture of a painting, a little backstory about there being a mistake in the accession record and the following question: \"What is the name of the venue where this possessor met a client on 14 May 1942?\" The first step I took was to do a reverse image search on the painting, so I'd know what work we would be looking into. In the results of TinEye the title of the painting and its painter are visible in many file names. My next step was to try to look for a record of who has possessed it by googling for: The Denial of Saint Peter Caravaggio accession record This brought me to the painting's page on the website of The Met Museum. Scrolling down a little, there was a tab called provenance in the artwork details with information about all of its previous owners. When I combined part of the list of owners mentioned in the gallery page and Bellingcat's data into one timeline, it looked like this: Guido Reni owned it from 1613 to 1624 In the Savelli family from 1624 to until ca. 1952 Mysterious owner meets a mysterious client on 14 May 1942 for it Vincenzo Imparato Caracciolo bought it on art market between 1945 and 1952 Hmm, that does not add up at all. So, supposedly it remained in the hands of a certain Italian family until after the war, but also, there was a meeting about this painting in 1942, where it switched hands from unknown to unknown. The painting was in fascist Italy under Mussolini at 1942. WW2 was happening. People were fleeing, removed from homes and killed. Nazi Germany's soldiers were collecting (aka plundering) valuable property, art, money. Thinking about it, I thought one of the following could have occurred: (Someone from) the Savelli family/the owner had to sell/trade/give the painting away for desperate reasons (like needing money, buying favors) and no official record was made of it. The family/owner gifted the painting in suspicious cooperations with certain individuals or parties and no official record was made of it. The family/owner had to flee their home and the painting was looted. The family/owner had been arrested, deported or killed and their possessions were confiscated by ruling powers or stolen by others opportunists. Nothing war or Nazi related! Turbulent 1942 Europe is a coincidence! Going down the wrong roads I've probably grown too used to just googling the obvious pieces of information first to see if more new information would easily pop op. In my summarized timeline above, it already looked quite obvious what might have happened with the painting. I even made a list of things I imagined had happened. But I didn't immediately follow that trail. I first decided to browse Wikipedia and do some general google searches into the painting, the painter and the year 1942. When that didn't lead to anything specific, I tried to do google searches into the painting and the previous and future owners, like for example the Savelli family. This didn't lead to much either. Then I decided to look up the painting in Italian ( La Negazione di Pietro ) combined with the year, the date, some related owner names, hoping to find some local news that maybe wouldn't pop up in English search results. No luck. After all that, I couldn't find any information that seemed to be leading to the answer of where this painting went. I was convinced I was overlooking something obvious and going down the wrong paths with these searches. So, I took a little break to reset. The obvious path reveals itself When I returned to this task, I looked at my notes. I wrote down what I thought might have happened to the painting and the family who owned it, so why hadn't I looked closer into that yet? Especially when I had such a specific date to work with too? I returned to google and searched: 14 May 1942 nazi art theft Savelli No, too specific. Why would anyone record the name of the family if the painting was obtained illegally or in a shady trade? So next I went for: 14 May 1942 nazi art theft Most results were speaking about nazi plunders, so I thought that might have been a more correct term for it, so I tried: 14 May 1942 nazi plunder Still no obvious result, but I wanted to give it one more go, just in case I wasn't wording it right yet: 14 May 1942 nazi stolen art There it was, something promising. One of the top results was a PDF on a website called looted art about the activity of the Einsatzstab Rosenberg in France. According to Wikipedia , this was \"a Nazi Party organization dedicated to appropriating cultural property during the Second World War\" . There are three places where the date appeared in the document. Firstly, there was an overview of all the dates Goering (aka Göring, a well-known Nazi minister) visited Musee du Jeu de Paume, where exhibitions would be prepared for him to personally view confiscated art, probably to pick some for his own collection. 14 May 1942 is on the list. In the second and third appearance of the date, the file mentioned that on that day he met with Dr. Alexander von Frey and Jan Dik Jr. to exchange art in Jeu de Paume. Reading the descriptions of the meetings and the paintings exchanged, Dik maybe seemed like a better candidate than Von Frey for having exchanged this painting. But, either way, the venue name is here: Jeu de Paume  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-4.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-3.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-3.webp"],"local_images":["blog_data/images/blog_9af62f7b4383_0.bin","blog_data/images/blog_9af62f7b4383_1.bin","blog_data/images/blog_9af62f7b4383_2.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-edward-scizzorhands-art-thief-challenge/","title":"37. Edward Scizzorhands Art Thief","status":"ok","retrieved_at":"2026-08-29T16:08:22.000208+08:00","text":"Walkthrough for Bellingcat's 'Edward Scizzorhands: Art Thief' challenge 03 Jul, 2025 Hi, welcome to this walkthrough of the Edward Scizzorhands: Art Thief challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but most likely there are many different ways of reaching the same results. Finding the painting We're shown a small piece of a painting and are told that a part of this painting has been cut out and stolen in 1982, from a cathedral. The cut-out canvas circulated for 35+ years until it was found during an auction. We have to find out the name of the auction house where this happened. The first question that arises is: what painting is this? We're only getting to see a small part of it. I can't search for information about it if we don't know anything about it. I did a reverse image search with the RevEye browser add-on. Google, Bing and Yandex all couldn't find the exact right full painting. However, TinEye gave me a promising lead. I clicked on the image and saw that it was a match for the given fragment on Bellingcat. From that link name we can now guess the name for the painting and painter. So I googled for martyrdom saint sebastian federico barocci . From this search I easily found some websites like Wikimedia and A&Aeportal that confirmed that this is the correct painting. These links also confirm that the painting hangs in a cathedral, just like the challenge prompt stated. Now that the painting is no longer a mystery, it was time to look into the crime and its resolution. Finding the story behind the crime Whenever I googled martyrdom saint sebastian federico barocci stolen or anything related to that, there was one article from Finestre sull'Arte that kept popping up. From the first sentences that are readable, it seems like an instant solution to all our questions. One problem, it's behind a paywall. Visiting an archive link doesn't remove it, nor does visiting the link through a new incognito browser window. Too bad. I continued on to a different link for art news , where there's a short piece about the theft, lacking any real useful information. However, it does link to its news source, which is an Italian news article. I tried reading the Italian news article with google translate. In it, I saw a new piece of information: the name of the father of the person who was depicted on the square of canvas that was cut out and stolen. Curious about this new information, I googled martyrdom saint sebastian federico barocci benedetto bonaventura . Of course the top result was that paywalled article again, grrr... But right under there was a link to a thread about the theft on X from Rembrandt's R👀m 🖌 (maaikedirkx) . This three post thread tells the story of the theft and tells about the item's reappearance on an auction. And luckily for us, a screenshot of the auction's webpage is included. I clicked on it and saw the name of the auction house in question in the top left corner: Wannenes . And voila, there's our answer.  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot01.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot02.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot03.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot04.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot05.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot06.webp"],"local_images":["blog_data/images/blog_4e845964b896_0.bin","blog_data/images/blog_4e845964b896_1.bin","blog_data/images/blog_4e845964b896_2.bin","blog_data/images/blog_4e845964b896_3.bin","blog_data/images/blog_4e845964b896_4.bin","blog_data/images/blog_4e845964b896_5.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-failed-to-detonate-challenge/","title":"46. Failed to Detonate","status":"ok","retrieved_at":"2026-08-29T16:09:10.916057+08:00","text":"Walkthrough for Bellingcat's 'Failed to Detonate' challenge 04 Aug, 2025 Hi, welcome to this write-up of the Failed to Detonate challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received an image of a corroded item, some type of weapon or military item can be assumed from the description of the challenge. Our task is to find its model and category. Looking closely at the item, the first thing I noticed was that there was text on it. It's not very readable, but three distinct kanji can be seen before the rest of the text wraps around the side. So, most likely we're dealing with a Chinese or Japanese item. I tried to get the kanji into text by drawing them in this kanji recognition website . To the best of my abilities, I came to: 无榴一. I tried to google 无榴一 and 无榴, but didn't get any results that would help me along. So I decided to put a pin in that path for now. Looking for resemblance My next step was to do a reverse image search on the picture posted by Bellingcat. I browsed through the search results until I found an image that resembled the item most closely. My attention was also drawn because the preview mentioned it was Chinese. Clicking the image, I landed on this forum thread where someone asked for a fuze to be identified. Scrolling and reading along, I saw many interesting old drawings and schematics of fuzes that looked very much like the picture we received, at least in external design. This was the first time I saw such items labeled as fuze , so I noted that down. A part of the thread's conversation goes: \"Soviet prototype of the “卡-3”\" \"do you mean that an analogue of KTM-1?\" \"The original Soviet version was the KTM-3\" This drew my attention because they're new terminology to look into. Also, I know that the third kanji on the item ( 一 ) means 1, so KTM-1 sounded like the most relevant thing to look more into first. I decided to google: Chinese KTM-1 fuze I went to the tab of image results, to see if I could find pictures that would resemble the original picture more than before. Immediately in the first row I saw a fuze with kanji that I recognized! The image led to this page from CAT-UXO. There's lots of additional information here, but most importantly, it looked very much like the one from the original picture. The one from Bellingcat looks a little more weathered, corroded, maybe partially broken. But in comparison: the item's text, general shape and design, and hole location all seemed to be a match. And it turned out to be correct. The final answer is: Type 1 fuze .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-7.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-6.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-6.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_04-3.webp"],"local_images":["blog_data/images/blog_7cf32d7305ba_0.bin","blog_data/images/blog_7cf32d7305ba_1.bin","blog_data/images/blog_7cf32d7305ba_2.bin","blog_data/images/blog_7cf32d7305ba_3.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-far-right-fashion-challenge/","title":"74. Far-right Fashion","status":"ok","retrieved_at":"2026-08-29T16:11:29.105552+08:00","text":"Walkthrough for Bellingcat's 'Far-right Fashion' challenge 11 Feb, 2026 Hi, welcome to this write-up for the Far-right Fashion challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. The challenge We've been given the logo of a far-right fashion brand. The logo contains a symbol used by far-right groups. This challenge is surprisingly quick to solve if you know of Bellingcat's Monitoring Glossary . Looking at the symbols in the Visual Symbols category, I reached the fasces symbol and saw a familiar symbol. The log-version is a bit hard to recognize in the fashion logo, but if you look at the picture of the graffiti, it's easier to see the comparison between the logo and a stylised version of the fasces. I also looked up the fasces symbol on Wikipedia . The symbol knows many uses and versions, but scrolling down, there is one rendition that looks very similar to the logo too. It's the version that was used by the Italian air force during the Fascist period. It also has a circle around it. So the answer for the challenge is: fasces  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/comparison-4.webp"],"local_images":["blog_data/images/blog_8bf494ab83aa_0.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-fascist-echoes-challenge/","title":"72. Fascist Echoes","status":"ok","retrieved_at":"2026-08-29T16:11:11.472472+08:00","text":"Walkthrough for Bellingcat's 'Fascist Echoes' challenge 08 Feb, 2026 Hi, welcome to this write-up for the Fascist Echoes challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a picture of a hate symbol painted on a weapon. This weapon was used in an attack that led to quick legislation change. We have to find both the date of this legislation change and the name of the historic political movement that used the hate symbol we can see on the weapon. To me, finding the political movement seemed like the easier task of the two. If I could find the name of the symbol, I could research its origin and historic movements related to that symbol. For the legislation change, I expected to have to start with identifying the weapon. If the weapon would lead to the attack, I'd be able to look into the political consequences of the attack. Hopefully that would lead to concrete law changes with dates attached. The symbol The symbol on the weapon is a grid that consists of three vertical and three horizontal lines crossing each other. I found it in Bellingcat's Monitoring Glossary under Cross of the Archangel Michael , where its relationship with the Iron Guard is explained. It's also in Wikipedia's list of symbols designated by the ADL as hate symbols as St. Michael's Cross. Clicking it leads to the page about the Iron Guard , an interesting page with a lot of background information. The second half of the answer is thus: Iron Guard . The legislation change Coincidentally, reading the Iron Guard article on Wikipedia, eventually I reached a part called Iron Guard in other countries . It reads: \"The Archangel Michael's Cross was among the symbols emblazoned on the firearms used by Brenton Tarrant during the 2019 Christchurch mosque shootings and by Payton S. Gendron during the 2022 Buffalo shooting.\" This already gave me two options to look into regarding the attacks for which a weapon with that symbol was used. Would pictures of the weapon be placed online? If so, I could compare them to the picture we've received by Bellingcat. I went to Google Images and looked up: christchurch shooting weapon There are a lot of pictures of the weapon the attacker used to be found online. This image in particular caught my eye, which led to this article that contains a plethora of photos. The weapon is a match with the one of the Bellingcat picture. Now that I knew for sure that the picture was related to the Christchurch mosque shootings, I could start my search for the legislation that was changed because of it. I queried Google for: christchurch shooting legislation change One of the top results leads to this page that gives an overview of all amendments to the Arms Act in 2019. It confirms that this has happened due to the attack, stating: \"Following the 15 March 2019 terrorist attack on Christchurch masjidain, then Prime Minister Jacinda Ardern announced that New Zealand’s firearms laws would change.\" Investigating the list from the top, the first item is an order . It states it comes into force on 21 March 2019, but doesn't use any official terms for it becoming law, which made me question whether this order was what I was looking for. The Bellingcat challenge asks what date did the new legislation come into force? -but does an order count as legislation? I looked up what types of legislation exist in New Zealand and read on this page that an order counts as secondary legislation. However, at the top of the order it says that it has been revoked on 12 April 2019 (by section 75 of a newer Act labeled 2019 No 12), making it seem as if it had been replaced by something else. I was unsure of this order, so I kept looking just in case something more obvious would appear. The second item in the list is simply an introduction to Parliament, so I skipped looking into that item. The third item in the list looked promising, because it read: On 11 April 2019, following a truncated Select Committee process, in which over 13,000 public submissions were received and considered, the Arms (Prohibited Firearms, Magazines, and Parts) Amendment Act 2019 received Royal Assent and became law on 12 April 2019. This was an Act, and it had a date of assent: 11 April 2019. It made sense that this most likely replaced the temporary order that was revoked on 12 April 2019, because it said it was revoked by a section of the Amendment Act 2019 (2019 No 12). To me it seemed more likely that the Bellingcat challenge was referring to this new, full Act, although I still did find the wording of the questions a bit confusing. Because the main list states that the royal assent for this Act was received on 11 April 2019 and thus it became law on 12 April 2019, I went with the latter date, which turned out to be correct. So the definite full answer is: 12/04/2019 Iron Guard  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/001_ironguard.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/002_comparison.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/003_law.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/004_revoked.webp"],"local_images":["blog_data/images/blog_6ecc81dfd176_0.bin","blog_data/images/blog_6ecc81dfd176_1.bin","blog_data/images/blog_6ecc81dfd176_2.bin","blog_data/images/blog_6ecc81dfd176_3.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-fixed-narrative-challenge/","title":"75. Fixed Narrative","status":"ok","retrieved_at":"2026-08-29T16:11:35.99156+08:00","text":"Walkthrough for Bellingcat's 'Fixed Narrative' challenge 11 Feb, 2026 Hi, welcome to this write-up for the Fixed Narrative challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. The challenge We've received a picture of a post with a sticker promoting a far-right active club. In the background two buildings are partially visible. We have to identify the symbol used on the sticker and the city it has been placed in. The symbol Browsing through Bellingcat's Monitoring Glossary , the symbol can be found in the category of visual symbols , under Celtic Cross . A little more background on the use of the Celtic Cross by far-right movements can also be found on Wikipedia . This is already the second half of the challenge solved: celtic cross . The city In the background of the picture are two buildings. The one on the right appears to have decorations and may be on the older side. The one on the left looks like a (maybe Eastern European) 20th century apartment block to me. I expected the left building to be more easily identifiable, because a larger portion of it is visible, the shape with the curve is quite distinct, and the antennas (?) on the top are very noticeable. I started with a reverse image search on the picture through Google, but limited the search field to just the left part of the picture with the building. There were many matching pictures to be found in the results, like for example this stock picture that calls the building Albania Palace Building in Belgrade. So, next up I googled: albania palace building belgrade Again I was met with many results with pictures of buildings that looked identical to the part of the building that's visible in Bellingcat's picture. This page gives some really good close-up pictures from several angles. There is a curve in the building's shape, there are two similar antennas on the top, the identical amount of windows are present per floor and these windows have shutters, on the top floor there's an AC unit in the same location, and on the top of the building there is the same edge with two wider and three smaller parts sticking out more than the rest of the roof's edge. My earlier search query also led to Palace Albanija's Wikipedia page where it's location in Belgrade is confirmed. And with that we have the full answer for the Bellingcat challenge: Belgrade, celtic cross . The post This is beyond the scope of the original challenge, but I got curious to see if it was possible to spot the specific post the sticker was placed on. I looked up the building on Google Maps and switched to satellite view with 3D on. This made it easier to see from what direction the picture might have been taken. Comparing the curve at the front of the building helped with this. I entered Google Streetview to look at streets that were west of the building. In Sremska street, looking toward Palace Albanija, there is a building on the right-hand side that looks similar to the picture on the right side of the Bellingcat picture. Above is a comparison between the building from Google Streetview in Sremska next to the building in Bellingcat's picture. The picture from Bellingcat seems to be taken from quite a low angle, which makes sense if the sticker was placed at eye-height or maybe slightly lower. Was it that post? The two buildings look identical. A lamp post further west into the street doesn't allow for a view of the right-side building. There are no black wires visible on Google Streetview, but the most recent footage is from 2013. On more modern pictures many black wires are visible in the air. Was the picture taken somewhere from here, angled up? Was the sticker on that specific post? I'm not completely sure, a lot in the area could have changed too since 2013. But for now it's my best guess. :)  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/001_building.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/002_angle.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/003_view.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/004_screenshot.webp"],"local_images":["blog_data/images/blog_d65fbd60198b_0.bin","blog_data/images/blog_d65fbd60198b_1.bin","blog_data/images/blog_d65fbd60198b_2.bin","blog_data/images/blog_d65fbd60198b_3.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-fresh-faced-challenge/","title":"31. Fresh Faced","status":"ok","retrieved_at":"2026-08-29T16:07:57.158637+08:00","text":"Walkthrough for Bellingcat's 'Fresh Faced' challenge 20 Aug, 2025 Hi, welcome to this write-up for the Fresh Faced challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. Finding the article We've received a screenshot from a newspaper article and with that we have to find footage of the interview visible in the screenshot. In the picture, Eliot Higgins is pointing at a laptop, accompanied by a text below it that reads \"Bloger Eliot Higgins svaki dan pregledava nove snimke\" . I put the text into Google Translate with the 'detect language' setting on, and found out that it's Croatian. It read: \"Blogger Eliot Higgins reviews new footage every day\" . I reverse image searched the screenshot and found a link to the news article on Google. It's an article written in Croatian, with a Croatian TLD (.hr), which aligned with the screenshot language. Finding the footage Scanning the article, I saw that the picture credits were 'Tomislav Krasnec/VLM' . The author of the article was also Tomislav Krasnec. Assuming I'd have the best luck finding any footage on Youtube, I went over there and typed in Tomislav Krasnec Eliot Higgins (the author of the article + the subject of the article) in the search bar. Fortunately, the thumbnail of the top result looked very familiar, and the uploader name too! Watching the video , it's clear that this is the interview related to the screenshot. Higgins can be seen in the same outfit, pointing at the same laptop with a cute green creature on top. The furniture in the background looked the same too. I took the relevant part of the link that was requested by the challenge, which turned out to be the correct answer: k7qd4Y6QAfY .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-13.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-12.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-11.webp"],"local_images":["blog_data/images/blog_a0c578ced20d_0.bin","blog_data/images/blog_a0c578ced20d_1.bin","blog_data/images/blog_a0c578ced20d_2.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-funny-money-challenge/","title":"36. Funny Money","status":"ok","retrieved_at":"2026-08-29T16:08:07.93481+08:00","text":"Walkthrough for Bellingcat's 'Funny Money' challenge 13 Jul, 2025 Hi, welcome to this walkthrough of the Funny Money challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but most likely there are many different ways of reaching the same results. Looking for the case Not knowing anything about (rare) coins, I decided to go for a broad google search first. I looked up: 1933 rare coins Immediately multiple results pop up for the 1933 double eagle . Besides the relevant Wikipedia page and some general informational website, there's also one link about double eagle coins being melted down, recovered, stolen, and it talks about their scarcity and monetary value. This all sounds quite eventful. In my next google search tried to be a bit more concrete, since we're looking for a court case and the double eagle coin seems a like a likely candidate. So I looked up: 1933 double eagle court case Lots of results! They all seem to go about the Langbord family going up against the U.S. Dept. of Treasury for the right to keep their 1933 double pennies, which have been confiscated. For example, there's this article about the case, this article about the appeal and, very handy, this post that gives an overview of the whole saga. Looking for the attorney Reading deeper into all of the articles, the Langbord family seemed to have used the same family attorney every time: Barry Berke. However, the Bellingcat challenge page won't accept that answer! What's up with that? Well, the easy way to solve this is to do a google search for Barry Berke and you'll find out he has a middle name. But I went to long way and looked up a PDF version of the official court document so I could check the names of all the participants. There I saw the full name. So, in conclusion, the solution for this challenge is Barry H. Berke .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-3.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-2.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-2.webp"],"local_images":["blog_data/images/blog_507c41233492_0.bin","blog_data/images/blog_507c41233492_1.bin","blog_data/images/blog_507c41233492_2.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-ice-ice-baby-challenge/","title":"54. Ice Ice Baby","status":"ok","retrieved_at":"2026-08-29T16:10:53.274032+08:00","text":"Walkthrough for Bellingcat's 'Ice Ice Baby' challenge 13 Sep, 2025 Hi, welcome to this write-up for the Ice Ice Baby challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a picture of a hand holding up a dessert in front of a blurred background with buildings, cars, people, a street sign, maybe some decorations and tiny lights. We have to find the shop where this dessert was bought. My first thoughts were: The background looks a little touristy, maybe reverse image can pick up on it. The colors and shapes of the street sign could be looked up. The dessert looks like ice cream, or it looks like something that could melt, but it's in pristine condition. I doubt anyone would buy a dessert and walk around with it for several streets before taking a picture like this. I assume it has just been bought, very close to the location of where the picture has been taken. The dessert is in a transparent cup with a transparent spoon. It looks quite small, like it's a luxurious delicacy. It looks quite unique. Finding the place I started with a reverse image search through Google, but only selected the top part of the picture, above the dessert. Immediately many results came up for Covent Garden in London. I clicked on the images that seemed to show the same building as in the picture, and the results described this as the Covent Garden market building . For example, this result on Wikimedia seemed to show the building from the same angle. In the description it stated captured from Russell Street . I looked up Covent Garden on Google Maps and put myself on Russell Street in Streetview . Hm, that does look the same! The tree trunk (marked in green), the location of the parked cars (blue), the sign (orange) and the building in the background (yellow). It looks like the picture was taken standing on the sidewalk on the right side from this angle. Finding the dessert I started looking around on Russell Street in Streetview, close to the Covent Garden market building, at all of the shops that could be selling ice cream to go. However, many buildings that were quickly visible, looked like restaurants for dining in. When I clicked Santa Nata , the pop-up said Portuguese custards tarts, to go . That didn't really sound like ice cream, but the place did look like it might serve unique, small delicacies. I clicked the pictures in Google of the items and the menu, and it didn't seem to have any ice cream. I saw this sign on one of the pictures, but the cup wasn't see-through. I looked at a few other shops in the area, but nothing really came close, so I returned to Santa Nata. This time, I checked their Instagram account. Ah! Multiple reels of soft serves! Served in a transparent cup, with a transparent spoon, quite small, with a cute swirl. The only thing that might be missing is the little cookie. Maybe they aren't served with every flavor of soft serve, but I can also easily imagine the person who took the picture not being able to resist eating that already before snapping a picture. I wouldn't be able to wait. I put in the answer and the screen turned green. The answer is indeed Santa Nata .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-15.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-14.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-13.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_04-8.webp"],"local_images":["blog_data/images/blog_fb9e2436f002_0.bin","blog_data/images/blog_fb9e2436f002_1.bin","blog_data/images/blog_fb9e2436f002_2.bin","blog_data/images/blog_fb9e2436f002_3.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-iconography-of-hate-challenge/","title":"71. Iconography of Hate","status":"ok","retrieved_at":"2026-08-29T16:11:07.958591+08:00","text":"Walkthrough for Bellingcat's 'Iconography of Hate' challenge 07 Feb, 2026 Hi, welcome to this write-up for the Iconography of Hate challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. The challenge We've received a graphic containing six symbols. We have to find out which of these are commonly used by hate groups. I recognized some of these symbols, unfortunately due to local far-right activity. Usually these groups use a variety of runes in their logos, or their banners and posters. The runes The easiest way to look up any of the symbols would be to go to Bellingcat's Monitoring Glossary . Looking through the category visual symbols , one can encounter symbol 6 , symbol 2 and symbol 3 . Alternatively, one can look up these symbols in a search engine by describing the symbols or reverse image searching for them. Combining these searches with terms such as hate group , hate symbol , far right or dog whistle will quickly lead to several helpful pages. Doing this for symbol 2 , 3 and 6 brought me to the Wikipedia pages for these three runes and their connections to modern day hate groups. I also found three other helpful tools that I now use in addition to Bellingcat's Monitoring Glossary: Wikipedia's List of symbols designated by the ADL as hate symbols Hate On Display's database of hate symbols A publication by the Bundesamt für Justiz about right-wing extremist symbols, signs and banned organizations They're all convenient tools to save. They have much overlap, but all contain some unique information as well. The other symbols I tried to look into the other three symbols to see if there was any connection to hate groups. They can't be found in any of the hate symbol guides posted above, but they might be very obscure. For symbol 1 I didn't see the need to do a reverse image search, because it was simply an arrow pointing downward. It doesn't look like a rune because of its thin form. I did a variety of search engine queries like: down arrow hate symbol down arrow far right arrow pointing down hate group arrow pointing down dog whistle I couldn't find anything related to extremism. For symbol 4 and 5 I did a reverse image search in Google and added a mix of words related to hate groups. Awkwardly I hoped nothing would pop up, because symbol 4 looks like something I've used in every PowerPoint presentation in my life. But once again I couldn't find anything related to hate groups, past or present. With that, the correct answer to make the screen turn green is: 2, 3, 6  ","image_urls":[],"local_images":[]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-larger-than-you-think-challenge/","title":"50. Larger than you Think","status":"ok","retrieved_at":"2026-08-29T16:10:11.360395+08:00","text":"Walkthrough for Bellingcat's 'Larger than you Think' challenge 18 Aug, 2025 Hi, welcome to this write-up for the Larger than you Think challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a picture with a piece of ordnance. It isn't very clear, but there are a few things that I noticed: The description says this is a fragment of something, so it must be quite big if this piece is only a part of it. The description mentions it is a missile type . It seems to have a blue/grey color, although it could be due to weathering or other damage. There is a curve in its shape. On top there is a piece sticking out, maybe it was a kind of wing, maybe it was something else. I expected this to be a long search, but it was relatively quick thanks to resources I had already found and saved in the previous challenges from the Hidden Hazards series. Missile search I tried to do a reverse image search on Bellingcat's picture. No exact matches showed up, but there were a lot of results about Russian missiles used in Ukraine. I went to CAT-UXO, an informational website about explosive ordnance that I stumbled upon during the Failed to Detonate challenge . I sorted all missiles to only show those with country of origin Russia and country used in Ukraine, and got 71 results . I browsed through them, but found it very difficult to recognize or identify any specific parts. Because there was a large chance that this challenge was about a weapon used in Ukraine, I went to the GICHD explosive ordnance guide for Ukraine, third edition , that I found and saved during the Target Not Acquired challenge . Missiles start at page 219. There were about 12 of them, and only one looked remarkably close to the original picture. Especially in the two pictures of the individuals clearing fragments, the curve of the object and the parts that stick out seemed to resemble the object in the Bellingcat picture. It looked like the same blue-grey-hue too. I was pretty sure at this point, but wanted to find a little more information just in case. When I googled kh-101 missile I arrived at an article from Bellingcat about the identification of a missile used in an attack on a children's hospital as a Kh-101. I recognized the picture, because it was also used in the Bellingcat newsletter to announce these latest challenges. Hmm... In the article the authors link to this identification manual for a previous Kh-101 strike. On page 41 there is a part visible that looks almost identical to the part visible in the challenge picture. Googling the marking that is mentioned next to it (9-Е-2648) led to many more articles about Kh-101 attacks and similar parts found. So, by now I was quite certain and put in the answer, which turned out to be correct. It is: Kh-101 .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-12.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-11.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-10.webp"],"local_images":["blog_data/images/blog_ee235d705ea6_0.bin","blog_data/images/blog_ee235d705ea6_1.bin","blog_data/images/blog_ee235d705ea6_2.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-mummys-little-helper-challenge/","title":"39. Mummy's Little Helper","status":"ok","retrieved_at":"2026-08-29T16:08:51.529881+08:00","text":"Walkthrough for Bellingcat's 'Mummy's Little Helper' challenge 30 Jun, 2025 Hi, welcome to this walkthrough of the Mummy's Little Helper challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but most likely there are many different ways of reaching the same results. The search for the ushabti We're shown a picture of a collection of ushabtis with some background information on these ancient figurines. One of them has been purchased in London in 2013 for £937.50 and we must find out which one, at which auction house, and who the ushabti was meant to serve. My first google search was for ushabti £937.50 london , expecting this might show an overview or log for the sale. One of the top results is indeed an auction page for one of the ushabtis from the picture, namely the turquoise one. Checking the lot information, I saw that the year of the sale date corresponded with what we're looking for (2013) as well as the price (£937.50 inc. premium) and the location (London). The auction house where this took place is Bonhams in Knightsbridge. In the prompt we were told that ushabtis have an inscription on them with information about who they're serving. Conveniently this inscription is placed on the item page of the auction website too. In it I could read that the figurine is serving Semataui , son of Sheri. So, the final answer will be: Bonhams Semataui  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01.webp"],"local_images":["blog_data/images/blog_28ce841a2a0b_0.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-on-the-right-track-challenge/","title":"77. On the Right Track","status":"ok","retrieved_at":"2026-08-29T16:12:02.01821+08:00","text":"Walkthrough for Bellingcat's 'On the Right Track' challenge 28 Aug, 2026 Hi, welcome to this write-up for the 77. On the Right Track challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a picture of GeoPeter . It's a selfie made while travelling. We need to geolocate him and find the name of the neighborhood he's posing in for his picture. I first inspected the picture to gain as much knowledge as possible before starting my search. This could help me get some context for what I'm looking for. I made a list for myself and noted: It's a man wearing a scarf and hat: is it a cold environment? The environment looks quite European, maybe Eastern Europe. The man is wearing a pin with the flag of Sweden and Latvia: is that where he is? It looks like he's at a train station. In the distance there is a tower of some sort. There's a building in background. It's vague, but with a big logo and a bright color, it might be a supermarket. It looks like there's maybe also a bus station in the background. The country There are quite a few points to get started with, but I first wanted to limit my search area as much as possible. Because of the pin GeoPeter is wearing, and because of the hint in the Bellingcat challenge text ( \"Hidden throughout are a few details that give away my location.\" ) I thought the country was most likely Sweden or Latvia. This might be a bold presumption to make, but because I had to start somewhere, I decided to go for it for now. If I stumbled upon dead ends, I could always remind myself that the country choice was potentially flawed, and reevaluate. My initial expectation of the picture was that it was located somewhere in Europe, maybe in the east of Europe. If I had to limit my choice between Sweden and Latvia, I found Latvia the more likely option. Maybe it's hours of playing GeoGuessr, maybe it's my limited knowledge of Scandinavian environments, but the location in the photograph didn't seem very Swedish to me. So Latvia was left over as first choice. Because I thought this picture was taken at a train station, I went to Google Maps and dropped myself into the Streetview of a variety of random train stations in Latvia. I simply wanted to see if the general look came close to the picture or if I was completely off. No random train station looked exactly like the picture, but based on how they looked I thought it was certainly possible that the Bellingcat picture was taken in Latvia. How I didn't get there: the tower So, my starting point was Latvia, and I was looking for a train station. I could try to look at every train station in Latvia, but that would be many hours of inefficient work. So I tried to look for identifiers in the picture that would be more rare. Looking at the selfie and rereading my observation list, I thought the odd tower in the background would be a good building to focus on. Surely there can't be that many towers like that? But what kind of tower was it? It felt impossible to look up the location of towers if I didn't even know what type of tower it was. I did a reverse image search on only the part of the picture that showed the tower. It didn't really help that the tower is partially hidden in the picture. I had no results that were an exact match, but I did have a lot of types of tower pop up. I noted communication, observation, railway, radar, radio and water towers. So which type was it? I wasn't sure. I decided to look up every type of tower in Google Images and compare the results to the tower in Bellingcat's picture. For every type of tower I did a separate query, and one query with \"Latvia\" added to it. So, eventually I searched all the following queries in Google Images: communication tower communication tower latvia observation tower observation tower latvia railway tower railway tower latvia radar tower radar tower latvia radio tower radio tower latvia water tower water tower latvia It felt a little silly to do, but I have no knowledge of towers whatsoever, so I was trying to spot any sort of comparison. The tower in the selfie has a notable upside down triangle shape at the top. The only image results that showed anything remotely similar were the 'water tower latvia' queries. These towers were not very high, just like in the picture. They were usually made up of two parts: the straight tower, and the top part that looked like a little round house, a triangle, or a different shape. One I saw even had an upside down triangle shape. I was not really convinced, but for now it was the best lead I had so far. I thought that the tower in the background of the picture might be a water tower. So, could I find that specific water tower from the selfie? I tried to redo the reverse image search on the tower, but added a variety of search terms along with it, such as water tower , latvia , and water tower latvia . I found a lot of water towers that looked a little bit like the one I was searching for, like this one , this one and this one . Because all of those results were on the Virtual Globetrotting website, I tried to use their search too. I limited their search for Latvia as the country and water storage towers as the category. I looked through all the results, but unfortunately no luck. Was there some resource elsewhere that listed all water towers in Latvia that I could check? I decided to look on Google for the following search terms: map water towers latvia I found this Wikimedia page but once again I couldn't find an exact match. I was starting to doubt that the tower in the picture was actually a water tower. I decided to try one more method with the water tower theory. I wanted to try out Bellingcat's search tool for OpenStreetMap. The guide for it can be found here . I was curious to see if I could find a match for a train station and a water tower being within a certain distance of each other in Latvia. I looked up the correct tag for a water tower and for a railway station . I tried to look for those two within 500 meters of each other I had about 20 results. Excitedly I looked them all up on the map and then checked Google Streetview footage or uploaded pictures by users on Google Maps. I didn't find the location from the Bellingcat pictures. How come? I thought of a few reasons: The water tower might not be a water tower. The water tower might not be tagged as such in OpenStreetMap. The water tower might be more than 500 meters away from the station. There was a variety of ways to test these theories and to keep search for the water tower, but I had too much doubt and wanted to let the water tower go for now. I needed a fresh approach. How I did get there: the supermarket I looked at my initial observation list and noticed that I had speculated that the building in the background might be a supermarket. I decided to try Bellingcat's search tool for OpenStreetMap again, this time looking for a train station and a supermarket within 500 meters of each other. A supermarket seemed to me more likely to be tagged on the map than a maybe-water tower. I had 15 results within Latvia. Once again I looked up all of the results on the map (from left to right) and then checked Google Streetview footage or uploaded pictures by users on Google Maps. Pretty quickly I stumbled upon a view that was very familiar ! It appears that GeoPeter was at Sloka Station in Latvia. The metal poles over the railway look the same. In the background the tower is visible . Walking around with Streetview the tower, the supermarket and the bus station are all visible next to the train station. This was definitely the location from the picture! So the answer was Sloka . Why didn't the tower search work? I went back to Bellingcat's search tool and once again tried to search for a railway station and a water tower within 500 meters of each other, but got zero results in the Sloka area. I checked OpenStreetMap and both the railway station and the water tower are labeled as such (so it was a water tower after all). I checked the distance and they are within 500 meters of each other. Why didn't the tool give this location as a result for the search for the water tower? I still have no idea. If you do know, please tell me ! I'd love to know if I did something wrong in that search, so I can improve (and correct myself here if I made a mistake). Either way, I got there at the end with the supermarket search. The definite answer was indeed Sloka .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/001_pin.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/002_tower.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/003_search-1.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/004_maptermstower.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/005_maptermssupermarket.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/006_map.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/007_supermarket.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/008_openmap.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/009_zeroresults.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/010_330meters.webp"],"local_images":["blog_data/images/blog_edc6298762bb_0.bin","blog_data/images/blog_edc6298762bb_1.bin","blog_data/images/blog_edc6298762bb_2.bin","blog_data/images/blog_edc6298762bb_3.bin","blog_data/images/blog_edc6298762bb_4.bin","blog_data/images/blog_edc6298762bb_5.bin","blog_data/images/blog_edc6298762bb_6.bin","blog_data/images/blog_edc6298762bb_7.bin","blog_data/images/blog_edc6298762bb_8.bin","blog_data/images/blog_edc6298762bb_9.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-proceeds-of-war-challenge/","title":"40. Proceeds of War","status":"ok","retrieved_at":"2026-08-29T16:08:56.248345+08:00","text":"Walkthrough for Bellingcat's 'Proceeds of War' challenge 01 Aug, 2025 Hi, welcome to this walkthrough of the Proceeds of War challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First things first For this challenge we've received an image of three ritual daggers and a little bit of backstory on them. We have to find the presumed nationality of a dark web seller. My first thought was that I'd need to know what these daggers are called. Or I'd need to know in what kind of collection they belong, since from the picture it looked like they were in a display case in a museum of sorts. Knowing these things would enable me to look up more information about them more easily. Finding the daggers The first thing I did was to do a reverse image search on the provided photo of the three fancy daggers. I got a lot of results for daggers that looked differently and stock pictures of the exact same daggers without any useful information. But two results grabbed my attention. The first one was a picture on Flickr, which showed more of the case the daggers were displayed in. It also showed the floor, a part of the wall, a reflection of some paintings on the wall, and a label with a QR code. Unfortunately, the QR code didn't work and the information on the label didn't help much in terms of names or terminology. The second notable link was to a blog post in Russian on a rating website. The post was made for a specific location: Potocki Palace, in Lviv. Scrolling through the post, it has a lot of pictures of the inside and the collections displayed. The daggers made an appearance! The post mentioned that in the Potocki Palace , the writer visited the Lviv Art Gallery . Looking that up, it does indeed seem that the Borys Voznytsky Lviv National Art Gallery is located in the Potocki Palace, in Lviv. All this information seemed related and relevant, since we read on Bellingcat that the daggers were originally displayed somewhere in Ukraine before being moved. I put a pin it for later. I now knew that these pieces were probably displayed in the Potocki Palace in Lviv, but the reverse image search didn't lead me to concrete titles, collection names or articles about those specific items. So I wanted to do a more general google search to see what else I could find. Finding the collection The Bellingcat prompt referred to the daggers as Asian pieces detained by the SBU in 2023 . So I searched google for: Asian collection sbu 2023 Because of the ongoing Russian invasion of Ukraine, I got a lot of very recent war results that didn't lead to the topic I was searching for. So I narrowed it down to results from before 2024: Asian collection sbu 2023 before:2024 I spotted a very promising link! But in the preview I saw a reference to Chinese collection so I wanted to try one little adaptation before reading more and looked up: Chinese collection sbu 2023 before:2024 Now the before mentioned promising link showed up again, along with a second one. Time to investigate. The first news article I saw , from June 20th 2023, spoke about detaining the Chinese parts of the \"Platar\" collection, that included items like ritual daggers, at the border of Lviv. The second news article is from a day later, where a statement from the Platar museum claimed that the collection was being moved from Ukraine to Prague. Examination required for this was done by Borys Voznytsky Lviv National Art Gallery, they claimed. Ah, I recognized that Arty Gallery name, because in my reverse image search I suspected that that was the location of the daggers. The location added up (Lviv), the museum added up, the items being Chinese daggers seemed to be a hit too. So, I was now relatively sure these daggers belonged in the Platar collection, but not 100% certain yet. The first news article linked to the official website of the Platar collection . Using google translate, I looked around on the website and looked at all of the pictures of the art pieces, but very few were actually shown. The daggers, or any other Chinese-appearing art pieces, were not displayed. I navigated to the subsection called gallery . There I saw an article about an exhibition of part of the Platar collection at the Lviv National Gallery of Art . The interior in two images looked very familiar Comparing these two pictures, they resembled the pictures of the inside of the palace made on the Russian review site. The green walls, the display cases, the floor tiling, the art on the wall -all a match. I went back to the flooring in the Flickr image of the daggers, and compared it to the background of one of the pictures of the green art gallery rooms, and saw that the floor and the yellow wall seemed to be a match, although it was hard to spot! Based on all this, I thought it was now relatively certain that the Chinese daggers belonged to the Platar collection, that the Platar collection was being displayed in the Lviv Art Gallery, which was located in the Potocki Palace in Lviv. Then, for some reason, they were moved out of Lviv and detained by SBU. It was claimed that they were being moved legally to Prague, Czechia. But were they really heading there, in a fair way? Finding out where the daggers truly went The daggers were part of the Platar collection, and the news article stated that the Platar collection at that point belonged to Serhiy Taruta. So I decided to google: Serhiy Taruta platar One of the first interesting results was an article in PDF format . It doesn't give me any direct answers or leads, but it did provide me with a lot of general information about private artifact collections in Ukraine and I learned about black archeology. Always good to know some extra background info on what you're researching. Then I got to the most relevant search result: this art crime blog with a post from 2023 about the movement of art collections from Ukraine, that discusses the Platar case too. It also linked to this news article about law enforcement seizing artifacts in Spain. Bellingcat asked us what the presumed seller's nationality was, and it's starting to look like it might be Spanish. But I wanted to dig a little more. My next google search was: Spain Ukraine \"platar\" This led me to an article about pieces from Ukraine being seized in Spain . It goes more into Ukrainians and Spanish people being arrested, and how a criminal network was involved. The art crime blog wrote a post about it as well, where in it is stated that the antiquities were sold through a web of sales, one of which was identified in Madrid. Now I felt a little more secure in my 'presuming'. The presumed identity of the seller is Spanish .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_000.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-5.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-4.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-4.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_04-2.webp"],"local_images":["blog_data/images/blog_75a0f8f743ee_0.bin","blog_data/images/blog_75a0f8f743ee_1.bin","blog_data/images/blog_75a0f8f743ee_2.bin","blog_data/images/blog_75a0f8f743ee_3.bin","blog_data/images/blog_75a0f8f743ee_4.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-seems-fishy-challenge/","title":"51. Seems Fishy","status":"ok","retrieved_at":"2026-08-29T16:10:22.578472+08:00","text":"Walkthrough for Bellingcat's 'Seems Fishy' challenge 21 Sep, 2025 Hi, welcome to this write-up for the Seems Fishy challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a picture of a lobster on a rock and we have to find what animal used to live on that rock before the lobster took its place. Studying the picture closely, the first things I noticed were: Generally, it looks Mediterranean. There are boats on the left, so it's most likely a coastal town, with something like a harbor. There are white buildings to the right, with a restaurant/patio. The car has a white license plate with black text and a tiny bit of blue on the left side, so probably it's a EU country. It looks like it’s on a roundabout or traffic intersection of some sort. The lobster has no claws (might be a certain species?). Thinking about how to tackle this challenge, I saw two possible ways: Finding the specific lobster statue online, which could lead to more information about what it has replaced. Finding the specific location of the statue, and looking up that spot on Streetview to see what used to be there before. Looking for the lobster I first tried to see if I could find the lobster statue. Doing a reverse image search in Google, Bing, Yandex and Tineye didn't lead to any clues. It did, however, caused me to see hundreds of lobsters statues. Big and small. Public and private. Who knew there is such interest in lobsters. And please, Google, don't ever talk to me about Betsy the Lobster again. When reverse image searching didn't work, I tried several search engines with a variety of search queries about lobsters, statues, monuments, replacements, coastal towns with sea creatures, harbors, crustaceans, picturesque towns with sea animal decorations -you name it. I tried to look up the species of lobster, which I thought to be a spiny lobster, and tried to implement that in my searches to no avail. I tried looking into Mediterranean towns well-known for catching, exporting or serving lobsters. Nothing. I was starting to think that nobody on the internet had ever spoken about this particular lobster before. It was time to try a different approach. Looking for the spot Because I couldn't find the lobster, I decided to try to look for the area in the picture. Because of clues in the picture, I thought I'd have to limit myself to a EU country, most likely one with a Mediterranean coastline. I did a reverse image search on the Bellingcat picture, but limited the search area on the picture to the areas around the lobster. I mainly tried to focus on the white houses on the right side. I never got any specific results that seemed right, but there were some countries that kept popping up in the search results: Greece Albufeira in Portugal Andalusia region of Spain Ibiza Greece and a whole region in Spain seemed a lot to tackle, but I could check out the other two. I saw pretty quickly that the Portugal option didn't really fit. Ibiza looked more promising. I entered Google Maps and went around the coast of Ibiza. I searched closely for: a road very close to the sea (because of the boat being close to the road/buildings in the picture), a harbor of unknown size (maybe small if the picture only shows a few boats), with some buildings, maybe with a marked restaurant, maybe with an intersection or roundabout. Whenever something looked like a maybe, I entered Streetview to have a look. But, ultimately I couldn't find the lobster spot. Still being in doubt between Spain and Greece didn't help, so I tried to find out which one it was for sure. I knew that GeoGuessr players can recognize a lot of small things, so I tried to narrow the countries down again by other signs in the picture, such as traffic signs, sidewalk, bollards, etc. I checked with GeoHints , Plonk It and GeoTips . Yet I remained unsure. Not knowing what way to turn next, I tried to find a meta route. I looked at the metadata of the Bellingcat picture, but unfortunately there were no coordinates of where the picture was taken. Then I looked at the creator of the challenge, Charlotte Maher. I couldn't find any social media pictures of places she'd visited, except for her visit to the International Journalism Festival in Perugia, Italy. I did a real quick, hopeless search for lobsters over there, just in case. No... Stuck with the knowledge that probably somewhere along the coast of Spain or Greece this lobster is minding its own business, yet no new ideas on how to narrow that down to an actionable search that wouldn't take days. What now? Looking for a hint After getting stuck and taking a little break, I saw that Bellingcat had organized a livestream in which someone tried to solve this month's challenges. I watched the recording, hoping to reach a point where I could see a hint or a little push for how to continue on my own. The stream was helpful and I got a clue that made it possible for me to continue. However, I must admit I was a little bit disappointed about how rushed the livestream felt. I understand that solving mutliple challenges in a short amount of time is difficult and limits the amount of time that can be spent per search and the amount of details that can be discussed. But I learn a lot from watching people think out loud. I also learn a lot from seeing people going down the wrong path -why they initially thought it was good idea to pursue that path, and especially, seeing how and when they realize it might be better to switch tactics after all. I think with two commentators in the stream, and an active chat, all guiding and hinting along, it was a little overwhelming and hurried for my personal liking. Still, it was helpful. Anyway. When the stream reached a point where the Balearic islands were mentioned as the right area, I thought, oh! Wait! I checked out Ibiza, then left the region. Maybe I hadn't been thorough enough! I went to Google Maps and decided to start on Mallorca next. Once again, I tried to look for: First of all, a harbor Then a road close to the water (lots of places had lots of beach in between roads/houses and the water, which could be skipped), preferably two roads very close together Buildings, preferably on the second road from the water Maybe a marked restaurant Maybe an intersection or roundabout or other noticeable transition or coming together of roads with a spot for statues in between or next to it I started at Palma and went around the island from there, sometimes dropping into Streetview if something looked promising. Nothing really looked quite like it, until I encountered this area: I dropped in at the roundabout, because I saw two roads close to the water close by, along with a little rectangle shape that could be interpreted as a harbor. And I saw the lobster rock! I've drawn a few lines of things that I noticed the most when comparing the picture to the Streetview area, but there's lots more to match, especially when walking around a little. Here's the link for the specific spot. But, the rock was empty! No lobster, no other animal! But when I kept walking around a little, I entered a shot from September 2022. Finally, I got to see what the lobster replaced. It's indeed a seahorse .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/collage-1.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-17.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-16.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_04-10.webp"],"local_images":["blog_data/images/blog_8db87c26f875_0.bin","blog_data/images/blog_8db87c26f875_1.bin","blog_data/images/blog_8db87c26f875_2.bin","blog_data/images/blog_8db87c26f875_3.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-shattered-glass-challenge/","title":"91. Shattered Glass","status":"ok","retrieved_at":"2026-08-29T16:12:37.106338+08:00","text":"Walkthrough for Bellingcat's 'Shattered Glass' challenge 02 Jun, 2026 Hi, welcome to this write-up for the Shattered Glass challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. The challenge We've been asked to give the minimum peak overpressure required to shatter glass (in kPa). All of these terms were new to me, so I decided to first learn a little about what we were dealing with. I googled for: minimum peak overpressure kpa This led me to this link from a blasting mats manufacturer that explains a lot of the terminology. I saved some relevant parts into my notes: “ Blast pressure is the instantaneous rise in air pressure above the normal atmospheric pressure caused by the rapid expansion of gases from an explosion. […] Typical atmospheric pressure is around 14.7 pounds per square inch (psi) at sea level, so any pressure created by an explosion above that baseline is classified as overpressure .” “ The peak overpressure of a blast wave is the maximum pressure increase from the explosion.” \" Psi is a unit of pressure that measures the amount of force exerted on an area of 1 square inch.\" \"Kilopascals ( kPa ) are the metric unit of pressure. One psi is equal to 6.895 kPa .\" With this information I had a better idea of what was actually asked. I scrolled down a little more on the same webpage and found a graphic that stated that an overpressure of 1 psi can shatter glass. Since 1 psi equals 6.895 kPa, it meant that 6.895 kPa was the minimum amount of overpressure needed to shatter glass. Just to make sure that that information was correct, I tried to look up a second source. I googled: overpressure shatter glass kpa This brought me to this link that also explained that an overpressure level of 1.0 psi can shatter glass. So, that's another confirmation. To my confusion, the answer 6.895 was wrong. I wondered if Bellingcat wanted an integer as an answer, so I rounded up to 7 kPa, which did turn the challenge page green. So the correct answer is: 7 .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/image001.webp"],"local_images":["blog_data/images/blog_bf4696c52814_0.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-shifting-focus-challenge/","title":"52. Shifting Focus","status":"ok","retrieved_at":"2026-08-29T16:10:37.131059+08:00","text":"Walkthrough for Bellingcat's 'Shifting Focus' challenge 20 Sep, 2025 Hi, welcome to this write-up for the Shifting Focus challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a blurry picture and have to identify the address. Looking closely, these things were the first that I noticed: This looks like a gas station (the challenge text confirms this). There is a sign with a logo, probably of the gas station with its prices. There appear to be two types of prices, one is labeled blue, one is labeled red or green. The prices are 4-6 numbers long, one starts as 449 and the other as 566, maybe 588? There's a car, it looks like it has a yellow license plate. There are snowy mountains in the background. Surrounding lights are all on, it’s probably morning or evening. The building on the right has bright posters or ads in several colors. On the total right: maybe more gas pumps, like on the left side of the main building. I first went on some paths that didn't lead to the answer for this challenge, as you'll see (but eventually I did reach the answer). The Bellingcat newsletter stated \"Bellingcat staff brought home some souvenirs from their summer vacations\" . I kept this in the back of my mind, which wasn't the best thing to do here. I took that newsletter way too literally, haha! The misleading way Before showing the easy path to the right answer, let me first show you how I found out some information and got lost on some unfruitful paths. My first thought was that the scene in the picture looks like it is in the US. To get a feel of what American gas stations look like, I googled: US gas station I browsed the image results and then, to get a few options of what price signs might look like, I googled: US gas station prices I noticed an image result that was promising. It led to a stock image of a Chevron price sign. The logo looked like what was on the original picture. Next, I looked for: chevron gas station locations This led me to this map with all of the Chevron gas stations in the US. That's a lot! But at least a large part of the US can be crossed off. So far so good, right? Well, this is where I lost my way for a little while. Because I wondered: how could I narrow this down? I thought of two main ways: There are prices on the sign, so I could look in which region these were the right prices. Especially in summer 2025, these are remarkable numbers, hm? There are snowy mountains. I could look into mountainous regions. Especially such snowy mountains in the summertime, that can't be just anywhere? Here's a short recap of my next activities: The prices on the Chevron sign looked to be for a blue label and a green label, so I tried to look up if certain types of gas are related to certain types of colors. Green looked to be diesel most of the time. Blue was usually 'regular'. I tried looking up when prices of diesel would be higher than 5, but it was way too high of a price. The US average only got there in 2022 in this 5 year chart . I tried looking around more anyway, looking into forum threads where people complained over high 'regular' gas prices of over 4 in 2025, and only people in California were talking about it. I was in doubt. Just to be sure, I looked if Chevron was also active in Canada or other countries, and checked price numbers there as well, but that didn't really convince me either. In the US I remained. Next I tried to look up mountain ranges, especially ones that would get that snowy. Lots of areas, it seemed. But what mountains remained that snowy in summer? I didn't find any decent information about that, especially not with California's prices in the back of my mind. The mountains, the prices, the road and the gas station never really lined up . What I was doing was starting to feel silly. Was I overlooking something obvious? Was I interpreting data the wrong way? Or was I making assumptions that I shouldn't have? So, I got stuck, and then decided to start over in a different way. The easy way I didn't want to use reverse image search immediately at the start, because I wanted to challenge myself to look up data visible in the picture. But I had gotten stuck, so the time to apply reverse image search had arrived. In the Google search results, I saw multiple gas stations with mountains in the background, but one in particular caught my eye, because of the shape of the roof of the building (in addition to the mountains). When I clicked the matching link I was led to a list of gas stations in Sandy, UT. I started at the top of the list, looking at the pictures that came along with the address, and already it seemed to resemble what I'd been looking for quite a bit. I copied the correlating address (8655 Highland Dr., Sandy, UT 84093, United States) and looked it up on Google Maps and entered Streeview. Oh! The location of the pump, the mountains in the background, the prices sign, the positioning of the lights and road -every last detail looked like a match. And it turned out the be the correct address: 8655 Highland makes the screen turn green! However. As you might remember, as I copied earlier, the Bellingcat newsletter with the announcement for this month's challenges said \"Bellingcat staff brought home some souvenirs from their summer vacations\" . As you can see from the Streetview screenshot above, the prices from the gas station are way lower than the one's on Bellingcat's picture. Also, the mountains aren't as snowy as in the picture we've received. I walked through other moments captured in Google Streetview. The car almost always passed by in the months of June-August, and never can the mountains be seen with that amount of snow. It makes me think that maybe the picture was actually been taken in a colder season than summer... Looking at the prices in past Google Streetviews, never do they even come remotely close, except for 2022... Am I seeing things, or is this a picture from late fall, winter, or maybe early spring? From 2022, instead of a recent summer vacation shot? I hope Bellingcat will tell us in the next newsletter.  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/collage.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-16.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-15.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-14.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_04-9.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_05-3.webp"],"local_images":["blog_data/images/blog_908de5a2c0d0_0.bin","blog_data/images/blog_908de5a2c0d0_1.bin","blog_data/images/blog_908de5a2c0d0_2.bin","blog_data/images/blog_908de5a2c0d0_3.bin","blog_data/images/blog_908de5a2c0d0_4.bin","blog_data/images/blog_908de5a2c0d0_5.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-ship-happens-challenge/","title":"76. Ship Happens","status":"ok","retrieved_at":"2026-08-29T16:11:49.863908+08:00","text":"Walkthrough for Bellingcat's 'Ship Happens' challenge 15 Jul, 2026 Hi, welcome to this write-up for the Ship Happens challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. The challenge We've received someone's travel picture and have to find out the name of the ship that brought the person visible in the picture to the location where the picture is taken. The picture seems to have been taken in some sort of terminal or other place travelers pass through. There are multiple people sitting and walking around with luggage. In the middle is a man, standing next to a life-size camel statue. In the background is a wall of windows, offering no clear view of the outside but rather of something bigger than the windows, with a blue/white pattern and small round windows. A ship? Because I have no knowledge of ships whatsoever, my plan was to first find the picture's location. I hoped that finding the location would lead to a way to research what ships would be arriving or leaving at said location or in the area. Then I could match those ships' looks to the one probably visible through the windows in Bellingcat's picture. The location I started with a reverse image search on the picture, hoping to find the building the picture was taken at. I assumed that the massive camel statue on a red carpet would be notable enough to get a quick match. I used a browser add-on called RevEye to reverse search the image on Google, Bing, Yandex and TinEye. A few of the results on Google looked like a large camel statue on red carpet. One was this IG post with the description \"Dubai, UAE\" . Another was this thread on a cruise forum . Scrolling down, the post made on January 13, 2005 not only has the camel shown, but also an overview of the cruise terminal it's located in. It's labeled as Abu Dhabi Cruise Terminal . Putting the overview picture from the forum next to Bellingcat's picture, the two locations appear to be the same. Especially the blue wavy couches, the floor tiling, the textured upper windows, and the slanted window roof look identical. Just to double check, I looked up Abu Dhabi Cruise Terminal in Google Images to see if the posts I had seen hadn't mislabeled the location. In the results were plenty of examples that indeed the location was right. The ship Now that I knew that the picture was taken at Abu Dhabi Cruise Terminal, and that the ship likely had a blue/white pattern that was partially visible through the window of the original picture, I wanted to find an overview of ships that pass through that cruise terminal. With that, I could compare their looks to the picture. Before going for more specific queries, I first tried to do a really general search and looked up the following on Google: Abu Dhabi Cruise Terminal For me, the second search result was this port page on Cruisemapper. Conveniently, a list of cruise ships is shown in the Schedule section, but depending on when you're looking at it, there are not many ships going and leaving due to the 2026 Iran war . Also, the schedule only showed the current month and future months. It didn't show ships from previous months. I checked the port's News tab hoping to see some more information of travels going through the area in the past, and one article's picture caught my eye. The ship in the preview picture seemed to have a blue/white pattern. I clicked the article , but unfortunately there was no bigger picture available. The news article does give some other information. It states that the MSC Euribia ship departure from \"homeports Dubai, Doha, and Abu Dhabi\" is disrupted, thus resulting in the cancellation of its remaining Middle East winter 2026-2027 schedule. Since I was looking for a ship related to the Abu Dhabi Cruise Terminal, this was promising. Clicking on the ship name in the news article led to this ship page that showed the boat slightly better, but still not close enough to really see those small pattern details well enough. I went back to Google Images to look for: MSC Euribia Looking through the results, the MSC Euribia's decoration pattern appears to resemble the pattern visible through the window in the Bellingcat picture. Comparing several pictures, the exact pattern can even be found on the ship, like in the picture on this page . With this I was quite certain that the ship pictured in Bellingcat's photograph was the MSC Euribia, so I assumed that the person in the shot had traveled with that ship too. Fortunately that answer made the screen turn green. So the definite answer is MSC Euribia .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/001_cruiseterminal.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/002_news.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/003_ship.webp"],"local_images":["blog_data/images/blog_73f0ec430ce9_0.bin","blog_data/images/blog_73f0ec430ce9_1.bin","blog_data/images/blog_73f0ec430ce9_2.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-small-but-deadly-challenge/","title":"47. Small but Deadly","status":"ok","retrieved_at":"2026-08-29T16:09:29.164408+08:00","text":"Walkthrough for Bellingcat's 'Small but Deadly' challenge 10 Aug, 2025 Hi, welcome to this write-up of the Small but Deadly challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a picture of three damaged items, ordnance of some sort. Our task is to find the most likely model number for these objects. Looking closely at the image, some things that drew my attention: The bottom black parts can appear like a tube, or fanned out There appears to be something red at the top There's Cyrillic on the main middle parts, along with numbers The credit for the image is dsns.gov.ua -Ukraine I think the path to the answer can be fairly short and quick, but let's say I took the scenic route for a little more context, haha! Where were these objects found? I did a reverse image search on Bellingcat's picture in Google, Yandex and TinEye, but I viewed the results on TinEye first because they appeared to be an exact match. The first image research was called 'bomb disposal in Mykolaiv 9 March 2022'. The second result led to this page where it's explained that these cluster bombs were found in Nikolaev on 9 March 2022. A quick detour to the Wikipedia page of Mykolaiv taught me that Mykolaiv is also called Nikolaev. It's a city in the south of Ukraine, with crucial access to the Black Sea. So, this little detour in the origin of the picture didn't give me the model number of the items, but I did learn that these are maybe a cluster type of weapon/bomb/munition. I put a pin in the other information, in case I'd get stuck later and wished to read more about the area. The search for the model number Next in my reverse image results, I decided to check Yandex, because it looked like we were dealing with Russian weapons used in Ukraine. There were a lot of results that resembled the object we were looking for! Two pictures drew my attention the most, because the reading on them was the clearest. I tried to put the writing together from combining the text of the two pictures and two of the three lines were pretty clear: 9H235.00.000 30-26? 30?-53-91 (seemed to differ between pictures) K-991-12 But what of this information was the model number? Conveniently, the second picture had a label at the top, called 9N235 . The object said 9H235 in Cyrillic, and a text referred to it as 9N235 . I checked the Russian Cyrillic alphabet on Wikipedia and saw that the Cyrillic letter H commonly gets translated to N, so it checked out. I made my way to CAT-UXO , a convenient website where you can check many types of explosive ordnance. I stumbled upon this website during a different challenge and saved it for later use. In the search bar I looked up 9N235 and found this page for the 9N235 Submunition. That looked identical to me! And it turned out to be correct. The final answer is: 9N235 .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-8.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-7.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-7.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_04-4.webp"],"local_images":["blog_data/images/blog_fed4248375dd_0.bin","blog_data/images/blog_fed4248375dd_1.bin","blog_data/images/blog_fed4248375dd_2.bin","blog_data/images/blog_fed4248375dd_3.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-spot-the-location-challenge/","title":"26. Spot the Location","status":"ok","retrieved_at":"2026-08-29T16:07:51.010729+08:00","text":"Walkthrough for Bellingcat's 'Spot the Location' challenge 01 Nov, 2025 Hi, welcome to this write-up for the Spot the Location challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a picture of two giraffes, edited to be in front of the Eiffel Tower and the Seine. We have to find out in which country these giraffes were most likely photographed. I guess they weren't touring around in France after all... Looking closely at the picture, I noted down some things that caught my attention: The giraffes have small brown birds all over their back and neck. The spots are very dark brown and kind of jagged around the edges, with some having sort of coves in them. They appear to have long faces with a droopy mouth and a dark spot on their foreheads. Finding the (sub)species The first thing I thought was important to know, was the species of the giraffe. If I knew for sure what species I was dealing with, then I could look up their habitat and see what countries would pop up. I googled giraffe species hoping to get some kind of chart for comparison. I ended up on this webpage on how to tell giraffes apart. Scrolling down a little, there is an overview of nine giraffe types with pictures of their spots. Because our giraffes have jagged lines in their spots, I could already eliminate any giraffe with very smooth or square spots. This left four types for me to consider: Rothschild Thornicroft Southern Masai I decided to google each of the four species, so I could study their full bodies and compare them to the Bellingcat picture. Pretty quickly, the Masai giraffe was eliminated too. The spots are very wiggly, way more than what I'm looking for. The Southern Giraffe was eliminated too. They have droopy faces, but the lines between the spots are very thin and clear, unlike the ones the giraffes have in the Bellingcat picture. Two species remained, and I found it hard to compare them, so I made collage to look at them more closely, right next to each other: When I looked closely at the Rothschild giraffe, I noticed that the spots might be a little different. The horns also look bigger. And where's the droopy face? Looking at the Thornicroft giraffe, there seemed to be the most resemblances. Same horns. Droopy face. Spots almost identical. And there's a dark spot right on the face, in between the eyes. I felt relatively sure at this point that I was looking at two Thornicroft giraffes in front of the Eiffel tower. Finding the country I went back to the giraffe species link I visited earlier to read about the Thornicroft giraffe. There it stated that they live in eastern Zambia. To double check, I also visited Wikipedia . Here it's written that \"Thornicroft's giraffe is endemic to Zambia\" . This safari page said the same thing. Apparently there are only 550 left in the wild, all in Zambia, so there's barely any chance that they've gotten their picture taken in any other country. PS: The little birds sitting on the giraffes are apparently called oxpeckers. Here you can find a very interesting study about their bond with multiple benefits! Anyway, I put Zambia in the Bellingcat answer box and the screen green turned green. Voila!  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/giraffe_comparison.webp"],"local_images":["blog_data/images/blog_01a894be5a0e_0.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-symbolic-literacy-challenge/","title":"73. Symbolic Literacy","status":"ok","retrieved_at":"2026-08-29T16:11:21.849791+08:00","text":"Walkthrough for Bellingcat's 'Symbolic Literacy' challenge 10 Feb, 2026 Hi, welcome to this write-up for the Symbolic Literacy challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a picture in which a graffitied symbol is visible. We have to find the name of the building that's partially visible. Looking at the picture, here were some first thoughts I had and some things I noticed: The graffiti is in red, no other markings are visible. The building looks like a tunnel or bunker of some sorts, but it's hard to say because by now it looks like ruins. There is a doorway with stairs leading up. A part of the building is higher up. Are these the ruins of an upper floor? Or is it built on the slope of a hill? Based on the foliage and the general 'vibe' (for lack of a better word), it looks like this was taken somewhere in Europe. Finding the symbol The symbol is a little hard to see, it being graffiti and partially hidden behind foliage. Was I looking at a cross or a plus sign? Was the lower part an upside down omega or something else? I tried to look up all sorts of descriptions for this symbol in a variety of search engines, but couldn't find anything related to it. I drew the symbol in Paint for a reverse image search, but had no luck with that either. Getting kind of stuck in a circle of my own thoughts on how to describe this symbol, I decided to approach the challenge in a different way. By the way, after completing this challenge I found out that the symbol is actually in the Bellingcat Monitoring Glossary . That would have been an interesting point to start this search with, but alas. I used a different road to get there. Knowing what the symbol is called now, I tried to google it again. If you use the terms cross and u together in some ways in your query, it's quite easy to find more information. So finding the right variation of words can be really important. Good thing to have learned for a future search. Finding the building I checked to see if the picture had any metadata that would be helpful. For this I used the EXIF Viewer Pro browser add-on. There was no GPS data, but three other things were notable to me: Artist: Peter Hohenhaus Copyright: dark-tourism.com Date time original: 2018:04:09 I looked up Peter Hohenhaus and saw that he was the author of Dark Tourism , which makes sense. By now I expected that this picture was published in an article on Dark Tourism about those ruins, buildings or the general area. Finding that article would most likely give me more information to use. I was considering using Dark Tourism's search option to look for bunker (224 results), ruins (258 results), or urban exploration (35 results), but felt a little unsure. I wasn't familiar with Dark Tourism's articles yet, and didn't know how diligently they were labeled. Also, what was I looking at? Did I know for sure that it was a bunker or ruins? The picture only shows a very small part of maybe a bigger whole. Instead I decided to focus on the date of the original picture: 2018-04-09. Evidently, the article with this picture could not have been published before that date, only after. How quickly after visiting the locations did the author publish an article about it? I first tried to do a specific Google search for Dark Tourism articles published in in the +/- two months after the picture was taken: site:dark-tourism.com after:2018-04-08 before:2018-05-01 This only gave one page of results, but unfortunately none of the articles that appeared, contained this picture. Next up I broadened the search to all articles from the date of the picture to almost the end of the same year: site:dark-tourism.com after:2018-04-01 before:2018-12-01 This gave four pages of results, but I didn't mind going through them. By now I was fascinated by all of the articles and got slowed down by reading them, which was well worth my time, haha. Hohenhaus went to many interesting places and I enjoyed encountering history that I didn't know about yet. Still, I tried to limit the amount of articles I decided to click from the search results list. Looking at the Bellingcat picture, I expected this place to be in Europe, so I primarily checked out articles for European locations. Eventually I reached the article about Villa Rebar . In the gallery, picture 09 is the same as the one posted by Bellingcat. Apparently it's a ruined hunting lodge with tunnels leading to bunkers, the residence of Ante Pavelić . Looking up Villa Rebar online, there are plenty of other articles that show that far right graffiti is quite common there. And if you look up Villa Rebar on Google and check the photos people have added to the Google location for this building, there's even a video of someone walking by the symbol painted on the wall. It looks like the same wall next to the doorway as is visible in the picture by Dark Tourism. That confirms the name of the building we were looking for, which was indeed: Villa Rebar  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/001_metadata.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/002_articlepics.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/003_video.webp"],"local_images":["blog_data/images/blog_64783fa2bccb_0.bin","blog_data/images/blog_64783fa2bccb_1.bin","blog_data/images/blog_64783fa2bccb_2.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-take-you-to-the-beach-challenge/","title":"21. Take You to the Beach","status":"ok","retrieved_at":"2026-08-29T16:07:46.579871+08:00","text":"Walkthrough for Bellingcat's 'Take You to the Beach' challenge 02 Nov, 2025 Hi, welcome to this write-up for the Take You to the Beach challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've received a satellite image, captured by Landsat-8. It's our task to find the name of the archipelago that's visible on the image. A very quick search This was definitely the quickest Bellingcat challenge I've ever completed. I reverse image searched the satellite image through Google. Immediately at the top of the results I saw three credible results: This Wikipedia page shows an archipelago that looks completely similar. It's called Mayotte and the picture is taken by Sentinel-2. This page from Nasa shows the same archipelago, called Mayotte's Lagoon, with Landsat-8 as the source. This case study write-up from POGO about Mayotte shows a familiar image from Sentinel-2. It seemed like the answer was already in front of me. Just to be absolutely sure, I looked up Mayotte on Google Maps and checked to see if it was once again looking identical to the satellite image we'd been given. After that I decided to give in my definite answer, Mayotte , to the challenge page, which turned out to be correct.  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/comparison-3.webp"],"local_images":["blog_data/images/blog_854680472d0b_0.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-target-not-acquired-challenge/","title":"49. Target Not Acquired","status":"ok","retrieved_at":"2026-08-29T16:09:53.747702+08:00","text":"Walkthrough for Bellingcat's 'Target Not Acquired' challenge 17 Aug, 2025 Hi, welcome to this write-up for the Target Not Acquired challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We received a picture of an object, partially buried, kind of looking like a thermos bottle, but it's ordnance so don't touch it! The size is hard to gauge, but comparing it to the surrounding plants, it looks rather small. The Bellingcat text also calls this item compact . I had no idea what type of ordnance I was dealing with. In the Bellingcat newsletter there was a link to A Beginner’s Guide to Identifying Explosive Ordnance in Social Media Imagery , so I tried to give the illustrated chart a go. Imagining I was looking at the back of the item, I imagined it being oblong, without fins, with a flat base and with driving bands. The chart led to projectile . I looked up what full projectiles looked like on CAT-UXO but wasn't convinced that was right. I put a pin in that for now. What if, in the picture, I was actually looking at the front of the item instead of the back? Nothing in the illustrated chart really looked like that either. It was time to try a different method, because I wasn't really getting anywhere. Looking around I reverse image searched the picture on Google and Yandex. Nothing quite matched the object I was looking at, but even if I could simply find the type of ordnance, I'd have a new path to explore. Looking around at items that looked kind of similar, they were often labeled either as tank shells or grenades . With tank shells, we'd be back in the projectile category, the one I put a pin in earlier. So, I decided to look into grenades first. I was confused that grenades were coming up so often in the image results, because in the illustrated ordnance chart these looked very round and were described as 'lemon' or 'egg'-shaped. I checked out the grenade page on CAT-UXO and my eye immediately fell on the subcategory that appeared at the top of the results. That shape did look a little like the picture's object! Filtering to show only the projected grenades , I got 82 results. That wasn't too bad, so I browsed through them. The RLV grenades kind of looked like it, but not quite. But the VOG grenades looked very, very closely like the picture. Inspecting them all more closely, only one truly looked like the Bellingcat picture: the VOG-25M grenade. The shapes were identical, except that the ridges looked slightly differently spaced. But how important was that detail? I felt confident enough about my finding, so I put it into the answer box. And then the screen turned red. Oops! It was wrong! So, to answer my own question, apparently that detail was very important. Lesson learned. When I recovered from the surprise, relieved that I didn't actually just give wrong advice to an ordnance disposal squad, I looked at the VOG type grenades again. The VOG-25 looked completely different. The VOG-25P's bottom part, before the ridges start, were too long to be the same object as the picture. The VOG-25M still looked mostly the same. CAT-UXO only showed three VOG-type projected grenades, but maybe there were more? I decided to google for: vog projected grenade types I found some specific ordnance guides, like this one from GICHD about explosive ordnance in Ukraine , but could not see anything with a closer resemblance than the VOG-25M. I then tried to google for: vog-25 projected grenade types This didn't result in any useful information either. I only ever found the same three types of VOG grenade. I was starting to think that maybe I was following the wrong trail. Should I bite down harder or reassess and restart? Looking deeper I decided to join the Bellingcat discord to see if there were any tips or hints that I could use. I didn't want to get spoiled, so I navigated the relevant topic as carefully as possible, but I did see that others had gotten stuck on the VOG-25M as well. The general gist I got was: keep following that idea, keep reading around, and you'll get there. So, I tried some more search terms and kept reading around. Eventually, the following google search term got me there: vog-25m grenade ukraine This lead to an article about surgeons removing a VOG-25 grenade from a soldier's body. A new type was mentioned that I'd never read about before: the VOG-25PM. I tried looking up more information about it, which required quotation marks in the google terminology, or else I'd be led back to the 25M and 25P. But with quotation marks, I ended up on this overview page . The ridges did appear to match more closely. I also found this updated GICHD guide for ordnance used/found in Ukraine that mentioned that the VOG-25PM very closely resembles the VOG-25M. And with that extra information, I put in this new type of grenade in Bellingcat and fortunately this time the screen turned green. So, the definite answer is: VOG-25PM .  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-11.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_02-10.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_03-9.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_04-6.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_05-2.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_06-2.webp"],"local_images":["blog_data/images/blog_60eff701c749_0.bin","blog_data/images/blog_60eff701c749_1.bin","blog_data/images/blog_60eff701c749_2.bin","blog_data/images/blog_60eff701c749_3.bin","blog_data/images/blog_60eff701c749_4.bin","blog_data/images/blog_60eff701c749_5.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-up-the-creek-challenge/","title":"16. Up The Creek","status":"ok","retrieved_at":"2026-08-29T16:07:33.456509+08:00","text":"Walkthrough for Bellingcat's 'Up The Creek' challenge 05 Oct, 2025 Hi, welcome to this write-up for the Up The Creek challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. First look We've been given a picture, taken from an airplane window, that shows a long river. We need to find the name of this specific river. Things that are noticeable in the picture: The river is very long and meanders through the landscape with a distinct pattern. Around the river are fields, some houses, roads, but beyond that is a lot of forest. There is a blue, curved bridge in the middle of the picture. It's a hilly environment, with even some mountains in the distance. Looking up the river Because the river's path looks so distinct, I started with a reverse image search. If search engines couldn't recognize the river immediately, then at least they might tell me the general area based on the environment. Reverse image searching the picture on Google gave a plethora of results: Rogue River, Chehalis River, Reshio River, and more. I took my time to scroll through the pictures, to see if I could spot any that looked very closely like the river's path. There was one result that caught my eyes, because the river was very curvy, and because I spotted a little, curved bridge going over it. I followed the associated link to a blog post called Advocacy Update: Fish, Farm, Flood 2.0 from 2018. It talks about task forces and states: \"By December 2019 they will be using their research to develop a decision-making tool that combines science, policy, and local knowledge to identify the relative impact of a buffer planting in any given stretch of the Snoqualmie River.\" No other rivers were mentioned in the post, and the update is regarding fishing, farming and flooding is a specific area. So, I assumed that the picture that went along with the post was of the Snoqualmie River . I decided to look up the Snoqualmie River and view its Wikipedia page for some general information. It's a 72 km long river in the US, in the State of Washington. I then tried to look up Snoqualmie River on Google Maps, to see if I could find the specific spot that is shown in the picture to verify that it was the right river name. Zooming in and going along the path of the river, the area right next to Novelty seemed the most promising. You can even see a bridge going over the river called Novelty Bridge. Here are a few comparisons of the original Bellingcat picture and the view from Google Maps. It looked pretty convincing, but I wanted to check one last thing. I dropped down to Google Streetview, right next to the bridge, to see what it looked like. At this point I thought there were enough pointers to confirm that the picture showed the Snoqualmie River. I put in Snoqualmie and it was indeed the correct answer.  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/collage_01.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/collage_02.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/collage_03.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/screenshot_01-18.webp"],"local_images":["blog_data/images/blog_946daf7cbbed_0.bin","blog_data/images/blog_946daf7cbbed_1.bin","blog_data/images/blog_946daf7cbbed_2.bin","blog_data/images/blog_946daf7cbbed_3.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-bellingcats-urban-symphony-challenge/","title":"81. Urban Symphony","status":"ok","retrieved_at":"2026-08-29T16:12:26.976062+08:00","text":"Walkthrough for Bellingcat's 'Urban Symphony' challenge 07 Jul, 2026 Hi, welcome to this write-up for the Urban Symphony challenge from Bellingcat . Here you can see my thought processes and what steps I took to get to the answer, but of course there are many different ways of reaching the same results. The challenge We've been given an audio file and need to find the name of the tower we can hear chiming. The location Listening to the audio, there were a lot of sounds that I didn't recognize. However, I could identify spoken text, so I decided to note that down first: \"Be aware of pickpockets at this station.\" \"Caution, you're reaching the end of the travelator.\" I first looked up the first sentence I heard on Google, but it gave a large variety of results. It appears that many stations all over the world use this particular sentence. Next I googled: caution you're reaching the end of the travelator This led to quite a few results about Amsterdam, like this Reddit post and this one . There were also a few results from other cities, but the spoken sentence always different by at least one word. So, I was fairly certain that we'd have to search within Amsterdam next. The tower Because I had to recognize a clock chime that would probably be played in Amsterdam, I googled: amsterdam clock chime This led me to a page of results with videos of Amsterdam towers chiming their song. I listened to one of the Zuiderkerk clock tower , the Westertoren and the Munttoren . I thought the Munttoren might resemble the original audio most closely, so I looked up more fragments with the following google query: munttoren amsterdam clock chime I listened to a few more videos and kept thinking that the chiming in the audio could be a match for the chime of the Munttoren in Amsterdam. I did find it incredibly hard to hear and doubted myself a lot. Sorry to all the chiming sound lovers, but the bells and melodies all sound very same-y to me. Fortunately the answer made the Bellingcat challenge screen turn green. So the definite answer is: Munttoren .  ","image_urls":[],"local_images":[]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-challenge-01-pet-the-dog/","title":"Challenge 01: Pet the Dog","status":"ok","retrieved_at":"2026-08-29T16:13:17.286252+08:00","text":"Walkthrough for Challenge 01: Pet the Dog 19 Feb, 2026 Hi, welcome to this write-up of Challenge 01: Pet the Dog by me. Here you can see what steps I took (and the thought processes behind them) to get to the answers, or what kind of search path I designed for them. However, keep in mind that of course there are many different ways of reaching the same results. The challenge I've posted a cropped picture of a part of a dog statue. With this information, you need to find the location of the statue, the individuals it's based on and their names. My aim with this challenge was to give practice for: Reverse image searching Searching for general information with a search engine, mostly through articles I recommend looking at images closely before starting an in-depth search, just to have a little more context or to notice things you might want to look out for. Some noticeable details of this picture for me are: There's a foot visible next to the dog, so the dog might not be the complete statue. There's a sign on the wall behind the dog. It's hard to read, but the top part seems to say Rio . There's a really blue body of water in the background. It might be the sea. Combined with the bright sunlight in the picture, maybe it's a warm location. The floor has a really distinct cobblestone pattern. The search I started with a reverse image search on the picture. For this I typically use the RevEye browser add-on, which lets you search for a picture on Google, Bing, Yandex and TinEye simultaneously. In Google's results, I get a variety of dog statues, but also the right statue in a variety of angles. However, in TinEye's results I see the exact picture the crop was made from. One of the links lead to a blog website, not the specific picture. The other link is dead. One of the files is called Clarice Lispector and the other is called Estatua Clarice . So I decided to query Google: clarice lispector statue The results make it pretty obvious that this is the statue we're looking for. This page confirms that the human of the duo is Clarice Lispector . That already solves the second question of the challenge. Her Wikipedia page contains the statue picture, stating that it's in Rio de Janeiro. The Google search results also show the statue as a marker on Google Maps, including an address. Entering Google Maps the statue is marked next to a small road. But is it really there? Switching over to Google Streetview gives several options throughout multiple years in which the statue is visible. Right-clicking the location on Google Maps gives the coordinates: -22.962976390226064, -43.16451904351414 . This is the answer to the first question of the challenge. The only quest left is to find the dog's name. For this I started with a search query in Google for: clarice lispector dog In this LitHub article it reads: \"In A Breath of Life, Clarice Lispector’s fragmentary final work, she devotes a few short passages to her dog, Ulysses, with a focus on this same strange intimacy of difference.\" In this portrait article the dog is called Ulisses (with an i instead of an y ). In this article too, and there's a picture of a dog breed that looks like the statue with a caption that confirms it's Ulisses we're looking at. Just to be absolutely sure, I do one more search for: ulysses clarice lispector Lots of convincing pictures in the results, but also two different links, one an interview , another a review , that give a little insight into the origin of her dog's name. Somewhat unexpected, quite funny, maybe a little bit concerning, haha! tl;dr Answers In conclusion: -22.962976390226064, -43.16451904351414 Clarice Lispector Ulysses or Ulisses  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/001_tineye.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/002_googleresult.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/003_maps.webp"],"local_images":["blog_data/images/blog_8751fb5a6290_0.bin","blog_data/images/blog_8751fb5a6290_1.bin","blog_data/images/blog_8751fb5a6290_2.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-challenge-02-out-on-a-walk/","title":"Challenge 02: Out on a Walk","status":"ok","retrieved_at":"2026-08-29T16:13:29.496903+08:00","text":"Walkthrough for Challenge 02: Out on a Walk 28 Feb, 2026 Hi, welcome to this write-up of Challenge 02: Out on a Walk by me. Here you can see what steps I took (and the thought processes behind them) to get to the answers, or what kind of search path I designed for them. However, keep in mind that of course there are many different ways of reaching the same results. The challenge I've posted two pictures of somewhere outside. With this information, you need to find the location where the pictures were taken and some information about the area. My aim with this challenge was to give practice for: Geolocating. Doing search engine queries in a foreign language (if you don't speak Dutch). Navigating a railway website of a foreign country (if you're not familiar with the Dutch railway). I recommend looking at images closely before starting an in-depth search, just to have a little more context or to notice things you might want to look out for. Some noticeable details of these pictures for me are: The little wooden sign has several textual clues. Next to the wooden sign is a row of planted trees that might be particular. On the nature picture is a red bench, with next to it a building with an awning. There's water visible in the picture, which narrows down the location to parks with something like a pond, brook or lake. The park To find the park the pictures were taken in, one of the two pictures holds a major clue. There's a small plate on a wooden sign post, which shows that the one who took the pictures was on an established walking route. The text is in Dutch, so they're probably in a part of the world where Dutch is a native language. Looking closer at the specific texts, it's made up of four parts: Klompenpaden: this is the name for a collection of walking routes. Words ending in -en in Dutch are often verbs or, as is the case here, a plural of a noun. rondwandeling: this simply reads 'a walk' and can be safely ignored. It holds no major information. Stoetwegenpad: this is the name for a specific walk in the klompenpaden collection. The -pad addendum can mean path, way, route or walk. 11 km: this is the length of the Stoetwegenpad , which happens to be 11 kilometers. Literally translating these terms is useful for the context (finding out that we're dealing with walking routes here), but for looking this up online, sometimes it's better to use the original terms. So, with these terms I went to a search engine, Google this time, and looked for: klompenpaden stoetwegenpad In the results I saw this page for the walk. The names, logo and length of the walk match. Conviently, the website also offers a map for the full walk, which opens in a new tab . On the map I could see a few named green areas the route passed through: Wulperhorst , Blikkenburg , De Breul , Rijnwijck . Also, multiple city names are visible on the map: Zeist , Odijk , Bunnik . With this information I went to Google Maps and looked up the area . Now it's clear that the pictures were taken in The Netherlands. In the original pictures I saw water, maybe a pond of some sort, and a notable red bench. Were these located in one of these green areas the Stoetwegenpad passed through? With the route map and Google Maps next to each other, I could cross reference what areas I needed to inspect further. When I dragged the little yellow person around on Google Maps to see what parks I could walk around in through Google Streetview, not much lighted up. Most of the Streetview footage was from around the parks, not inside of them. There were a few blue circles marking snapshots of one specific place. Checking those out, they still gave a little bit of a clue of where these pictures were most likely taken. More useful was to click the markers that appeared on Google Maps for named parks, buildings, and other locations that have been marked by Google. Clicking one of those gives a pop-up for the location with access to reviews and pictures posted by people who have visited that place. If you hover over the picture that shows up, a see photos button appears. This way, I clicked a variety of markers for and around areas such as Wulperhorst , Blikkenburg , Landgoed De Breul . I focused on areas where I saw water on the map, since there was also water in the picture. Then I went through the pictures, trying to see if there were any red benches, ponds, matching foliage, buildings, etc. Doing this, there is only one area that was very similar to the pictures, namely Landgoed De Breul. And there's even one 360° picture posted by someone that is an exact match to one of the two pictures of the challenge. The red bench, the buildings visible through the foliage, the sandy path -it all ligned up. The first answer of the challenge has already appeared: the pictures were taken in a park called (Landgoed) De Breul . The train station The second and third question require some information about a train station. The second question is solvable in seconds once the park has been found. Both on the Stoetwegenpad map and the area on Google Maps , a train track is visible, along with the marker for a train station. Clicking it on Google Maps, its name appears: Station Driebergen-Zeist . No fancy search acrobatics required. Next up is the question about food availability on the train station. The Netherlands has a main railway operator called NS. With a tiny bit of online searching and/or Wikipedia reading this is quite clear. The NS has its own website with an option to search for any station to receive information about that specific station. Information about the Dutch train stations is more easily found on their Dutch website than their international variant . Looking up Driebergen-Zeist on the NS website brought me to this page . It contains all the information about the facilities on the station, including a section for Eten & Drinken (food and drink). The page states that there's two places on the station that offer food and drink. The first one, Cafetaria to Go , has to go in its name, which sounds like what I'm looking for if I want to bring a snack to the park. So I googled: driebergen zeist cafetaria to go This brought me to the cafetaria's own website . Browsing that and the pictures and reviews posted on Google, it looks like I could bring my friend some takeaway food. Their website says they're open every day of the week between 11am and 10pm, so as long as I arrive during the day, I can easily bring some food to the park with me. I hope my friend is in the mood for some fries and spring rolls (called loempia in Dutch)! tl;dr Answers In conclusion: (Landgoed) De Breul Station Driebergen-Zeist The train station has a cafetaria with takeaway food that's opened between 11am and 10pm.  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/01_terms.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/02_pad.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/03_seephotos.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/04_comparison.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/05_trainstation.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/06_ns.webp"],"local_images":["blog_data/images/blog_35d9b409a2e0_0.bin","blog_data/images/blog_35d9b409a2e0_1.bin","blog_data/images/blog_35d9b409a2e0_2.bin","blog_data/images/blog_35d9b409a2e0_3.bin","blog_data/images/blog_35d9b409a2e0_4.bin","blog_data/images/blog_35d9b409a2e0_5.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-challenge-1-by-mrs-osint/","title":"Challenge 1: Mystery","status":"ok","retrieved_at":"2026-08-29T16:12:46.74073+08:00","text":"Walkthrough for Challenge 1 by Mrs. OSINT 28 Jan, 2026 Hi, welcome to this write-up of Challenge 1: Mystery by Mrs. OSINT . Here you can see what steps I took (and the thought processes behind them) to get to the answers, but of course there are many different ways of reaching the same results. The challenge We've received a single picture of a place outdoors. Based on this we need to find the answers to the following questions: What is this place called by the locals? Where is it located? What is this place famous for (what do they sell)? First look I prefer to take a closer look at an image before starting my search, so I have some context for what to look out for. Here are a few things that caught my eye when I inspected the image: There are fumes that don't look like clouds, maybe the location is related to hot springs, volcanic activity or a different natural phenomenon. The hills and ground are dark, the greenery is bare. There's a steps/stairs-like shape in how the hill in the foreground slopes down. There's a building visible with multiple cars parked around it. Maybe it's a place that has visitors? There appears to be a bridge. Is it for people to walk on? There's a little shed-like building visible in front of the bridge. The search I decided to start with a reverse image search on the given picture in Google, Bing and Yandex. Browsing through the Google results, I saw a lot of pictures of areas that looked very similar. One result sprung out to me, because I recognized a lot of identical landmarks. This picture looked like it had been made in almost the same angle, just a little farther away: The picture is from Wikimedia and is called Owakudani Valley and Mount Kammurigatake near Owakudani Station . I wanted to see a few more pictures, so I put the following query into Google: owakudani valley Browsing the image results, it seems like I'm at the right address. The picture we've received is from the Owakudani Valley . Now looking at the general results, I saw and read a Wikipedia article about the place. It's a volanic valley with hot springs and previously a hiking trail, very cool. The article also goes into its popular specialty: kurotamago , black hard-boiled eggs. I still had not encountered what locals would call this particular place, so up next I decided to google: owakudani local name In the results were lots of travel websites and pages about the local history. Browsing a few of them on the first two pages of results, I found two different local names. This article says that during the Edo period, the place got called Ojigoku (Great Hell Hole). I did a quick google search for that Japanese term, and indeed got a lot of results leading to the same place. In a different article it is said that its second name is Jigokudani (Hell Valley). Looking up that term led to more pages like this one that both names were in use once. The answers In conclusion, the search led to the following answers to the challenge's questions: The place was called Jigokudani (Hell Valley) & Ojigoku (Great Hell Hole) by locals. They might just use 大涌谷 (Owakudani) in this day and age. It's located in Owakudani, Hakone, Kanagawa Prefecture, Japan. It's famous for its black eggs (黒卵, or kurotamago), hard-boiled eggs that are prepared in the local hot springs.  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/001_picturecomparison.webp"],"local_images":["blog_data/images/blog_e19a8648ed76_0.bin"]}
+{"source":"wanderingjackdaw","url":"https://wanderingjackdaw.bearblog.dev/walkthrough-for-challenge-2-by-mrs-osint/","title":"Challenge 2: Cotton Candy","status":"ok","retrieved_at":"2026-08-29T16:12:50.639364+08:00","text":"Walkthrough for Challenge 2 by Mrs. OSINT 23 Apr, 2026 Hi, welcome to this write-up of Challenge 2 by Mrs. OSINT . Here you can see what steps I took (and the thought processes behind them) to get to the answers, but of course there are many different ways of reaching the same results. The challenge We've received a picture of a busy street. Based on this single photograph we're being asked to answer the following questions: What are the coordinates for where this picture was taken? What popular district is this? It's Friday night, I could go for some cotton candy. Where am I going? What time do they close? Arch The photograph has a large amount of clues of the arch's whereabouts, an overwhelming amount even. I decided to start with the simplest thing that was visible for me: the name of street that is printed on the arch, Takeshita Street . In Google I put the following search query: takeshita street Lots of results. Takeshita Street appears to be a popular tourist attraction in Tokyo. My next step was to look up the specific street on Google Maps . It looks to be a long street with two main entrances connecting to bigger roads on the east and west side. My first thought was the expectation that an arch would be placed at the entrance of a street. With two bigger main entrances and a collection of smaller ones, I decided to drop down into Streetview on the map at the two main entrances first. The east side has an arch, but it looks very different from the one in the picture we've received. However, the arch on the west side of the street looks familiar, including the landmarks around it. Going back in time in Google Streetview to 2017 , the western arch even has the same decorations on top as in the original picture. Because I felt certain that the picture was taken at the western arch of Takeshita Street, I went back to Google Maps (in 3D mode) and right-clicked the area in front of the arch, where I'd estimate the picture was taken. The coordinates appear in a pop-up box. So, the coordinates are: 35.67157252013977, 139.70312250404845 . District The second question is what district this is. Simply looking up the street in Google, gives an information overview with several area names. My assumption would be that Shibuya was a district, but I could be mistaken. To make sure, I googled: tokyo districts This brought me to this Wikipedia page with this image of the Special Wards of Tokyo. Special Ward is a different term than District , but scrolling down on the Wikipedia page, there is a section called Notable districts . Shibuya is on that list, so I thought it might count as a district for this question. I zoomed out on Google Maps to see what names would pop up in the area where I was, and I compared that to the Special Wards map. It looked to be Shibuya. However, looking a little further, on Shibuya's Wiki page Takeshita Street is mentioned as being located in Harajuku. And on Harajuku's Wiki page Harajuku is called a district in Shibuya. Although the terminology isn't entirely clear to me, I'd answer here that the popular district in the picture is Harajuku , which is located in special ward Shibuya, which is located in the city of Tokyo. Cotton candy For the third question, I started with the assumption that the person who's requesting cotton candy was standing on the spot where the picture was taken. What would be the closest location for getting cotton candy on a Friday night? In Google Maps, I searched for cotton candy in the area of Takeshita Street . A list of locations popped up, so I started checking, starting with the ones closest to the spot in the photograph and working my way outwards, deeper into the street. The first possibly relevant location that was shown on the map for me was Momi & Toy's Crêperie. I looked up their website, navigated to the menu and saw that they didn't sell any cotton candy. Nevermind! The second closest result was Totti Candy Factory. I went through the same process and checked their menu . There's cotton candy on there! I looked up their social media accounts to be sure, and yes, on their IG page one can definitely see that they're a cotton candy shop. But are they open on a Friday night? I couldn't find any opening hours on Totti's website, and (based on my own negative experiences) I didn't really trust the opening hours given to me by Google for the place, since they can be outdated. Instead I checked the pinned posts on their Instagram page and found a post with general information about the store , including opening hours. On a weekday, Totti is open until 8 PM. So, that gives the answer to the final question: the photographer is going to Totti Candy Factory , which will be open until 8 PM . The answers In short, the answers are: 35.67157252013977, 139.70312250404845 Harajuku Totti Candy Factory, 8 PM  ","image_urls":["https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/01_streetmap.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/02_archcomparison.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/03_coordinates.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/04_shibuya.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/05_district.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/06_cottoncandymap.webp","https://bear-images.sfo2.cdn.digitaloceanspaces.com/wanderingjackdaw/07_8pm.webp"],"local_images":["blog_data/images/blog_f530d8ecac33_0.bin","blog_data/images/blog_f530d8ecac33_1.bin","blog_data/images/blog_f530d8ecac33_2.bin","blog_data/images/blog_f530d8ecac33_3.bin","blog_data/images/blog_f530d8ecac33_4.bin","blog_data/images/blog_f530d8ecac33_5.bin","blog_data/images/blog_f530d8ecac33_6.bin"]}
diff --git a/blog_data/images/blog_01a894be5a0e_0.bin b/blog_data/images/blog_01a894be5a0e_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..8ec41aa618f99650440547db3ebd26a243958b0b
--- /dev/null
+++ b/blog_data/images/blog_01a894be5a0e_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:95274a35b110375ea239120e52c2915147ce5397a13ace69ab6332ba5f45f073
+size 155176
diff --git a/blog_data/images/blog_039dd670b506_0.jpg b/blog_data/images/blog_039dd670b506_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9325dcfca5e15bd4be4d05147ff0c762e775ab52
--- /dev/null
+++ b/blog_data/images/blog_039dd670b506_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:71ee7a806620da45d81ea9806745e90aa287e6562389ed9112980e977d9930d0
+size 83385
diff --git a/blog_data/images/blog_039dd670b506_1.jpg b/blog_data/images/blog_039dd670b506_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a3e04cf036a4ad4995aab8b11db6ee2f570c038a
--- /dev/null
+++ b/blog_data/images/blog_039dd670b506_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c819c0585aca05a61ec50785d8a6c5787d5b8b65f38f4db3bdfdaec08ca5539e
+size 78613
diff --git a/blog_data/images/blog_039dd670b506_2.jpg b/blog_data/images/blog_039dd670b506_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7130323e609c2c8237937721affc7ccb56d318b5
--- /dev/null
+++ b/blog_data/images/blog_039dd670b506_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5c9e7bf694a470da840d6bf1adf98473147bbcef0845cd1e5eace27da4a31027
+size 113623
diff --git a/blog_data/images/blog_039dd670b506_3.bin b/blog_data/images/blog_039dd670b506_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_039dd670b506_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_039dd670b506_4.bin b/blog_data/images/blog_039dd670b506_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_039dd670b506_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_083acfa87d18_0.bin b/blog_data/images/blog_083acfa87d18_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..3a0ed9e8989ceb073beaf9e6d2b1fffae02a0f54
--- /dev/null
+++ b/blog_data/images/blog_083acfa87d18_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a10645720b42bb086a9416797edec539f024db62edab63ae2a36604c89997fc8
+size 213524
diff --git a/blog_data/images/blog_083acfa87d18_1.bin b/blog_data/images/blog_083acfa87d18_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..851d75b992f7ec34b1ee91dedd46e04c40f7b3e6
--- /dev/null
+++ b/blog_data/images/blog_083acfa87d18_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:46279676980012dc59c44f02e7e3ee9f6cb28aaf4828d781ac088b698902e1b6
+size 432334
diff --git a/blog_data/images/blog_083acfa87d18_10.bin b/blog_data/images/blog_083acfa87d18_10.bin
new file mode 100644
index 0000000000000000000000000000000000000000..ff319a33f72e04a600e78cbcfb1aa4e3fb6bf762
--- /dev/null
+++ b/blog_data/images/blog_083acfa87d18_10.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:726f29855fc72daa176b6b09f8156897b6e068d90aa5807e9cbb65f20a3d4c51
+size 219150
diff --git a/blog_data/images/blog_083acfa87d18_11.bin b/blog_data/images/blog_083acfa87d18_11.bin
new file mode 100644
index 0000000000000000000000000000000000000000..ba4ce2b9f87ba2d5d1d0ba96e3d1d146f50ac845
--- /dev/null
+++ b/blog_data/images/blog_083acfa87d18_11.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:295636be5c1930fefc7ef2092c368899f3a49fbb3b1d883ce0c8b2bdf8e2543a
+size 425191
diff --git a/blog_data/images/blog_083acfa87d18_12.bin b/blog_data/images/blog_083acfa87d18_12.bin
new file mode 100644
index 0000000000000000000000000000000000000000..27f01c98c5f280c30570e24d6725d60710aabb2b
--- /dev/null
+++ b/blog_data/images/blog_083acfa87d18_12.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cf732b0faab6e4b02c7bbde8535ba018ad1400e7b2463ea45168f2334d32916a
+size 348870
diff --git a/blog_data/images/blog_083acfa87d18_2.bin b/blog_data/images/blog_083acfa87d18_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..26c8839293a0a8ec7fb4216d17c270df0aa3bbb6
--- /dev/null
+++ b/blog_data/images/blog_083acfa87d18_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:66489a6ccc7ff84576d2f1430e9f21f935adeb392fa82419c0a01e4033e6217f
+size 430589
diff --git a/blog_data/images/blog_083acfa87d18_3.bin b/blog_data/images/blog_083acfa87d18_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..be211ce20fa6ed571903699d14769641b930e1b4
--- /dev/null
+++ b/blog_data/images/blog_083acfa87d18_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:105493b2a12d734adda0d3a92f66cd1c2e8796a1b71c3837a960ff61be23ac4f
+size 418744
diff --git a/blog_data/images/blog_083acfa87d18_4.bin b/blog_data/images/blog_083acfa87d18_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..1955da89598942a243d908ac89577f2745466694
--- /dev/null
+++ b/blog_data/images/blog_083acfa87d18_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:991d434b55a7440e7032667264e7efbb02603add0063ecabc8128081b3b6d724
+size 392346
diff --git a/blog_data/images/blog_083acfa87d18_5.bin b/blog_data/images/blog_083acfa87d18_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..478b6577e25fda74a4953a34d7a96eedae69a4a4
--- /dev/null
+++ b/blog_data/images/blog_083acfa87d18_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6bdab7c6b0d78f2269eaaf95fc84523d8db141faa5c96f151e0a7d3842b3d8eb
+size 410271
diff --git a/blog_data/images/blog_083acfa87d18_6.bin b/blog_data/images/blog_083acfa87d18_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..ce2c90b62e1e6bcabd3c610e210d3fe3d291c6ee
--- /dev/null
+++ b/blog_data/images/blog_083acfa87d18_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d0559e498336c36cd230e8c8840794f41eda46fb93967c41afdba621cf3a2a52
+size 422254
diff --git a/blog_data/images/blog_083acfa87d18_7.bin b/blog_data/images/blog_083acfa87d18_7.bin
new file mode 100644
index 0000000000000000000000000000000000000000..b98d969bb05c86ace5b8824f3196f45b1ddce28b
--- /dev/null
+++ b/blog_data/images/blog_083acfa87d18_7.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1405d76e759f41f9954795421e017c958feaba24fd584305b154d6df68ef261a
+size 427424
diff --git a/blog_data/images/blog_083acfa87d18_8.bin b/blog_data/images/blog_083acfa87d18_8.bin
new file mode 100644
index 0000000000000000000000000000000000000000..38b482e3692279cd9775352737e18e446c254f86
--- /dev/null
+++ b/blog_data/images/blog_083acfa87d18_8.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ede20c10e502e97ac9f69bcfd441bbc6eebe6a7f93e3e2a73376a24a21e7d1c
+size 472320
diff --git a/blog_data/images/blog_083acfa87d18_9.bin b/blog_data/images/blog_083acfa87d18_9.bin
new file mode 100644
index 0000000000000000000000000000000000000000..31f866d6c2a4617f9de9c72b8ca28e6ec53ddebe
--- /dev/null
+++ b/blog_data/images/blog_083acfa87d18_9.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d27290d10a1348553fd3e117a4f9bee1bff6baf89aaafa6415b72a8e0efb6ec
+size 422652
diff --git a/blog_data/images/blog_0e5f583623cd_0.jpg b/blog_data/images/blog_0e5f583623cd_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1465b04acdbaa106ae48feef06b81f2a74b37b79
--- /dev/null
+++ b/blog_data/images/blog_0e5f583623cd_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8960ef76378077a9e5e3be0fb7ba6f20dbe9eb45daf1f12e471c447fe78b53e6
+size 53459
diff --git a/blog_data/images/blog_0e5f583623cd_1.jpg b/blog_data/images/blog_0e5f583623cd_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3c12c22484e3acee66ec5e98af1d3d99cb608889
--- /dev/null
+++ b/blog_data/images/blog_0e5f583623cd_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7c6701fec107cb770c265354dc3d81a38fbc447ba05385873e5e74fb195b5ad6
+size 56693
diff --git a/blog_data/images/blog_0e5f583623cd_2.jpg b/blog_data/images/blog_0e5f583623cd_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d1b04dfc67a1e8800829b91e2f956b11d67b2f2e
--- /dev/null
+++ b/blog_data/images/blog_0e5f583623cd_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:94520cd716afb2f53bfcc720b514b50e82a3e1c2793eacec8f6a012830a4d0ce
+size 67090
diff --git a/blog_data/images/blog_0e5f583623cd_3.bin b/blog_data/images/blog_0e5f583623cd_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_0e5f583623cd_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_0e5f583623cd_4.bin b/blog_data/images/blog_0e5f583623cd_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_0e5f583623cd_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_13c0476833a5_0.jpg b/blog_data/images/blog_13c0476833a5_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9f40f5b008225c6d19b2b303ef1a679c88cf4574
--- /dev/null
+++ b/blog_data/images/blog_13c0476833a5_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:035715618302a3164f98653328b9b20bc7c2fe12a69661d60e8f17de061d15d6
+size 77956
diff --git a/blog_data/images/blog_1a292eea0d47_0.jpg b/blog_data/images/blog_1a292eea0d47_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e3cbb1b794b6f9d2e340531f1ae6e7da7fa600b5
--- /dev/null
+++ b/blog_data/images/blog_1a292eea0d47_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5d4647bd548daf5474742c6ea0f2a4b214d37b25ce8059ed271f164bc62b7c1f
+size 23948
diff --git a/blog_data/images/blog_1a292eea0d47_1.jpg b/blog_data/images/blog_1a292eea0d47_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e078880cfd6de7af8ebb03b493e805e575681202
--- /dev/null
+++ b/blog_data/images/blog_1a292eea0d47_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a143f0a1f1685b8d78a39cbcd0960d93d73338ac0cf17a668f3628e9bf7d3542
+size 182842
diff --git a/blog_data/images/blog_1a292eea0d47_10.jpg b/blog_data/images/blog_1a292eea0d47_10.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f808d933999c9960e019a9e7a6c214f5df0a035a
--- /dev/null
+++ b/blog_data/images/blog_1a292eea0d47_10.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3ac1c599c0d0ebc734fed3c5c1ef9148a24e1107e02c19e6f914f6ee56b60086
+size 20462
diff --git a/blog_data/images/blog_1a292eea0d47_11.jpg b/blog_data/images/blog_1a292eea0d47_11.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d8a2aa1299a3b8f0151419ce73e05271cb77524c
--- /dev/null
+++ b/blog_data/images/blog_1a292eea0d47_11.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c3c655ef2e7ff49f6a8dc85dae2dcf30a4480a897e281721be369ea6cf6d1a2b
+size 75248
diff --git a/blog_data/images/blog_1a292eea0d47_12.jpg b/blog_data/images/blog_1a292eea0d47_12.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1de5288cd2b3b5206752dc4db745e1bdb0f5f308
--- /dev/null
+++ b/blog_data/images/blog_1a292eea0d47_12.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fbf179fcfaf9560ca6b3996530dcf153ff2c5733a0f7bba7d3056dcda024e887
+size 64553
diff --git a/blog_data/images/blog_1a292eea0d47_13.jpg b/blog_data/images/blog_1a292eea0d47_13.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b8570b0e65ccfe7277e04a55c7e567d14eceffe9
--- /dev/null
+++ b/blog_data/images/blog_1a292eea0d47_13.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2ace0d0eb5fe03c0964a410a3cb2a1375e79a8afb093324a39b22c41f997b23a
+size 34859
diff --git a/blog_data/images/blog_1a292eea0d47_14.jpg b/blog_data/images/blog_1a292eea0d47_14.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1a728a6335c913a8688c981f50bf5071f400362a
--- /dev/null
+++ b/blog_data/images/blog_1a292eea0d47_14.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f5f2e86f84843c5946488fd58dbe520032cf02c4000a674365213c82bf98ceb6
+size 92551
diff --git a/blog_data/images/blog_1a292eea0d47_2.bin b/blog_data/images/blog_1a292eea0d47_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..94ef8f08c00c00a0c76da7891bfc79791a30526b
--- /dev/null
+++ b/blog_data/images/blog_1a292eea0d47_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:63e34b05c4879c4c5753279885d3d1ef8bd8ba6e3eecdca35385bacee6de9805
+size 1206351
diff --git a/blog_data/images/blog_1a292eea0d47_3.bin b/blog_data/images/blog_1a292eea0d47_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..3678fb6c8d160609f30c15241274e8ccd7cadb0c
--- /dev/null
+++ b/blog_data/images/blog_1a292eea0d47_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1b899a169bde4a81ecec40271655128553c8f05ca631578b36f75ca0204073b6
+size 1558078
diff --git a/blog_data/images/blog_1a292eea0d47_4.bin b/blog_data/images/blog_1a292eea0d47_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..1dbe605986299f16bc45e09738a43d259c1a4a3c
--- /dev/null
+++ b/blog_data/images/blog_1a292eea0d47_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:08befd5a583f3023d7788fa5f0bde79c713dd19916f0efd5305475ab274c18b2
+size 1110831
diff --git a/blog_data/images/blog_1a292eea0d47_5.bin b/blog_data/images/blog_1a292eea0d47_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..1ec4f07970200bd8c9176ca11241e841aa2afd8f
--- /dev/null
+++ b/blog_data/images/blog_1a292eea0d47_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e6e9e89358012b3ec30c22ddcf277c50cbc7d649a3d71928c158a62546828216
+size 1388483
diff --git a/blog_data/images/blog_1a292eea0d47_6.bin b/blog_data/images/blog_1a292eea0d47_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..cde021f0fbae0de20e1fa34d5ab864d09d12f416
--- /dev/null
+++ b/blog_data/images/blog_1a292eea0d47_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b8e2cdeab26fcae1fed1221215db7957af36e72db02797139dbc8206e879ebee
+size 345887
diff --git a/blog_data/images/blog_1a292eea0d47_7.bin b/blog_data/images/blog_1a292eea0d47_7.bin
new file mode 100644
index 0000000000000000000000000000000000000000..d0bc6ed1b5b7dd4a076c4c169c617574256719a4
--- /dev/null
+++ b/blog_data/images/blog_1a292eea0d47_7.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4df81eb61fb49c7d6ec3303197ef3cca274f2b141563a7f99f521b0ff83f4f19
+size 914726
diff --git a/blog_data/images/blog_1a292eea0d47_8.bin b/blog_data/images/blog_1a292eea0d47_8.bin
new file mode 100644
index 0000000000000000000000000000000000000000..1da23dbcf78564782e6abc6cc97b0158189b0e07
--- /dev/null
+++ b/blog_data/images/blog_1a292eea0d47_8.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:40ca1785ea1d4a5c187fd27e70efcdba1e6d0d1fd4ea1aa0ac44e3c45999daeb
+size 144733
diff --git a/blog_data/images/blog_1a292eea0d47_9.bin b/blog_data/images/blog_1a292eea0d47_9.bin
new file mode 100644
index 0000000000000000000000000000000000000000..f22df5d8c549d4957606ff0512c8f5134aa06ccc
--- /dev/null
+++ b/blog_data/images/blog_1a292eea0d47_9.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b52dd34d4b361b0eedf5c965f2b2c299e77773613dd5fe2c02fb2a9a59a3c037
+size 27810
diff --git a/blog_data/images/blog_1e330956d596_0.bin b/blog_data/images/blog_1e330956d596_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..a98fb12b4b95968fd8541da0d22fe234787bd219
--- /dev/null
+++ b/blog_data/images/blog_1e330956d596_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c05bff45c78330821af7390269694de6a2f9241f97953e164c99e137181d5abe
+size 278089
diff --git a/blog_data/images/blog_1e330956d596_1.bin b/blog_data/images/blog_1e330956d596_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..c0fc45a77142372acbcd45f96a9c5bb508da92cd
--- /dev/null
+++ b/blog_data/images/blog_1e330956d596_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f8a0e86cd4cee95e9b0795a8ef4f31b06522fd029616507d80d385725d647778
+size 2025613
diff --git a/blog_data/images/blog_1e330956d596_2.bin b/blog_data/images/blog_1e330956d596_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..952c963183781f1dede1752c3f4f2c02f962dae4
--- /dev/null
+++ b/blog_data/images/blog_1e330956d596_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9775405189f069454f66f9d30560617ec53feff2145b39f6d439e026c057f573
+size 46683
diff --git a/blog_data/images/blog_203206e5f992_0.jpg b/blog_data/images/blog_203206e5f992_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9a9029021d8f191966a9622151ecd6912e51fb36
--- /dev/null
+++ b/blog_data/images/blog_203206e5f992_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4ae31cb7a7942483c4f64171bcf5b9814db073969bf5c7ded1eda4700819af19
+size 125673
diff --git a/blog_data/images/blog_203206e5f992_1.jpg b/blog_data/images/blog_203206e5f992_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d03aec28a0cce652d028067fffe015c85b3cd876
--- /dev/null
+++ b/blog_data/images/blog_203206e5f992_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:958d4d38da8902f887ef0482b59e41f381bcc8cb9fc7ae058fed7756126b3265
+size 58545
diff --git a/blog_data/images/blog_203206e5f992_2.jpg b/blog_data/images/blog_203206e5f992_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..15ca2a9e45ed982d5d27c25cbafb7deeb875d73a
--- /dev/null
+++ b/blog_data/images/blog_203206e5f992_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6199a8795a28d1e61263a6c7048680192f6fc89a9beffc5a2d02845861ac0280
+size 64153
diff --git a/blog_data/images/blog_203206e5f992_3.bin b/blog_data/images/blog_203206e5f992_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_203206e5f992_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_203206e5f992_4.bin b/blog_data/images/blog_203206e5f992_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_203206e5f992_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_28ce841a2a0b_0.bin b/blog_data/images/blog_28ce841a2a0b_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..85df7f103b4da83cc96fa061a3bdf2dfa32aeac9
--- /dev/null
+++ b/blog_data/images/blog_28ce841a2a0b_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9372eb47df6fec5597071531a2084cc506e1a20ef833478f618aee4b629149b7
+size 58496
diff --git a/blog_data/images/blog_2b8c7172515b_0.bin b/blog_data/images/blog_2b8c7172515b_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..5fd1f887c6400dab81895e1a285269c7e3de3bde
--- /dev/null
+++ b/blog_data/images/blog_2b8c7172515b_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:041d8a72aef7ff5e11250cf2322c2603e78a5fce1ab061fe532ad8f958302d55
+size 76880
diff --git a/blog_data/images/blog_2b8c7172515b_1.bin b/blog_data/images/blog_2b8c7172515b_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..7f879aef193216dfd5ef8dd12a181a4c8467b1a1
--- /dev/null
+++ b/blog_data/images/blog_2b8c7172515b_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8e6065c2b706b01117084e4b46cd7cceb4cb80f6f8b57c3178e3157981235f7e
+size 32992
diff --git a/blog_data/images/blog_2b8c7172515b_2.bin b/blog_data/images/blog_2b8c7172515b_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..1d2bd30fed358f9da324265842908482286bca10
--- /dev/null
+++ b/blog_data/images/blog_2b8c7172515b_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dd8da31ee64b9f47183823ea807f1d6457edd1bccdbe86d6de06746365550727
+size 515249
diff --git a/blog_data/images/blog_2b8c7172515b_3.bin b/blog_data/images/blog_2b8c7172515b_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..a98fb12b4b95968fd8541da0d22fe234787bd219
--- /dev/null
+++ b/blog_data/images/blog_2b8c7172515b_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c05bff45c78330821af7390269694de6a2f9241f97953e164c99e137181d5abe
+size 278089
diff --git a/blog_data/images/blog_2b8c7172515b_4.bin b/blog_data/images/blog_2b8c7172515b_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..5436991dd31d5989f229f0b06526423ac496147d
--- /dev/null
+++ b/blog_data/images/blog_2b8c7172515b_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:204a7da1395711e03a80c85063283ca672f3081fa24b037dabb4088e27ebabda
+size 82718
diff --git a/blog_data/images/blog_2d7647e66e95_0.jpg b/blog_data/images/blog_2d7647e66e95_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6a5b2e945563026efac15346f70bc0364086e16b
--- /dev/null
+++ b/blog_data/images/blog_2d7647e66e95_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5234c74b8d3ad10dadd30df9ecdb35ca6f0e0e664a28079e1e8bc137facd02a3
+size 313477
diff --git a/blog_data/images/blog_2d7647e66e95_1.bin b/blog_data/images/blog_2d7647e66e95_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..f31c8cecb4bf81c60aa5990051df5630270710d8
--- /dev/null
+++ b/blog_data/images/blog_2d7647e66e95_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:877fc3453963291d4c2016175b61768d609541a338bc336164ddedb3bd0e801d
+size 46276
diff --git a/blog_data/images/blog_2d7647e66e95_10.bin b/blog_data/images/blog_2d7647e66e95_10.bin
new file mode 100644
index 0000000000000000000000000000000000000000..c8f53988451bc06b15af6c50d23bdaafbb655695
--- /dev/null
+++ b/blog_data/images/blog_2d7647e66e95_10.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:84147d0df35eb32aaae394026fd8524abbcbd30f19a5962dd2e4fdb06373988f
+size 1463871
diff --git a/blog_data/images/blog_2d7647e66e95_11.bin b/blog_data/images/blog_2d7647e66e95_11.bin
new file mode 100644
index 0000000000000000000000000000000000000000..b4860af4a38a6c8c3dfd98a438ecfe3fff1f429c
--- /dev/null
+++ b/blog_data/images/blog_2d7647e66e95_11.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:79c9a87bdf2cb5c098111e4161135caa722f775d69000652a5256706e7ed0d17
+size 675808
diff --git a/blog_data/images/blog_2d7647e66e95_12.bin b/blog_data/images/blog_2d7647e66e95_12.bin
new file mode 100644
index 0000000000000000000000000000000000000000..3afec2eb71918b1463a0154c16a99fb38e2b666b
--- /dev/null
+++ b/blog_data/images/blog_2d7647e66e95_12.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7995f0a50a00f163574f1e24586aa5baf6035b2a308e0d2c0cad88b88e34ee81
+size 417832
diff --git a/blog_data/images/blog_2d7647e66e95_13.bin b/blog_data/images/blog_2d7647e66e95_13.bin
new file mode 100644
index 0000000000000000000000000000000000000000..c761a9743982270d72d6313b5b24d3186f29f9bc
--- /dev/null
+++ b/blog_data/images/blog_2d7647e66e95_13.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0ace7cdc8f4ac1d2524323604e9b2f6499ad630d9248d1f523ad406f6752f606
+size 120084
diff --git a/blog_data/images/blog_2d7647e66e95_2.bin b/blog_data/images/blog_2d7647e66e95_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..ced5e892ab17749a0a0f6d6481a7a14eeb4fb89e
--- /dev/null
+++ b/blog_data/images/blog_2d7647e66e95_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:90d777264cabc3f812a425a49c20c625d039bfd999963a7c325e06e5d12016e2
+size 66213
diff --git a/blog_data/images/blog_2d7647e66e95_3.bin b/blog_data/images/blog_2d7647e66e95_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..d89e8413f2f011384cacda15399a56371e732e75
--- /dev/null
+++ b/blog_data/images/blog_2d7647e66e95_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a620fe186c7f921d0bc7cd0909c64430acc0d3eaa1c6272c70eb6777b5217db7
+size 1428008
diff --git a/blog_data/images/blog_2d7647e66e95_4.bin b/blog_data/images/blog_2d7647e66e95_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..f3e7228928033fc44e2615f70a22b281c745848b
--- /dev/null
+++ b/blog_data/images/blog_2d7647e66e95_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:96ebcc4d248f74885c64e1f25a426ed4f538c5766ac762eeb5aa799df46e13a1
+size 1011470
diff --git a/blog_data/images/blog_2d7647e66e95_5.bin b/blog_data/images/blog_2d7647e66e95_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..8c472df1ee0d14c148fb4413b59bfe4596ee0aa0
--- /dev/null
+++ b/blog_data/images/blog_2d7647e66e95_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2413800cca620239b59b461e22806d8fe8cea8255f65f91a11d785b221ca81ce
+size 1415775
diff --git a/blog_data/images/blog_2d7647e66e95_6.bin b/blog_data/images/blog_2d7647e66e95_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..8ff5b3fa160fa45b612193c195b339797b232371
--- /dev/null
+++ b/blog_data/images/blog_2d7647e66e95_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:75baae8798524ca62f03cc3b3e01343e199b967507358cd08c5bd26fb427affa
+size 790694
diff --git a/blog_data/images/blog_2d7647e66e95_7.bin b/blog_data/images/blog_2d7647e66e95_7.bin
new file mode 100644
index 0000000000000000000000000000000000000000..5fc219ea2c30871b732fdd4e240d9313103bd3fe
--- /dev/null
+++ b/blog_data/images/blog_2d7647e66e95_7.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88daff486c712d6f06e89d8698b7c15bdc49460279c0c56e0a92df22880bf314
+size 1968733
diff --git a/blog_data/images/blog_2d7647e66e95_8.bin b/blog_data/images/blog_2d7647e66e95_8.bin
new file mode 100644
index 0000000000000000000000000000000000000000..7f7d05a7dbd189b1f1bf5d1df504d4a44baa5383
--- /dev/null
+++ b/blog_data/images/blog_2d7647e66e95_8.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d6e94dbc4dc482af3018b12bd75ad878fa51dd0ef7d7996a522e89b5d2bfbf65
+size 1722259
diff --git a/blog_data/images/blog_2d7647e66e95_9.bin b/blog_data/images/blog_2d7647e66e95_9.bin
new file mode 100644
index 0000000000000000000000000000000000000000..5f926bb902d5776767f1edfcdfc717eaabf30fe1
--- /dev/null
+++ b/blog_data/images/blog_2d7647e66e95_9.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3c09b38445420e99751d2b2c59169edd39dc2a6554be407a50d63b55bdf47ad7
+size 4896271
diff --git a/blog_data/images/blog_313c589aab9d_0.jpg b/blog_data/images/blog_313c589aab9d_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6640adae44101b603c186a9bff426124b53a2e13
--- /dev/null
+++ b/blog_data/images/blog_313c589aab9d_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:373a1b993384c92468ff779aafbe289883de776da40d431da95b63e476243719
+size 120397
diff --git a/blog_data/images/blog_313c589aab9d_1.jpg b/blog_data/images/blog_313c589aab9d_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5ce414ebedf4fc3a9a3d288aeb23ae8b581fb2db
--- /dev/null
+++ b/blog_data/images/blog_313c589aab9d_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f472a60260d4d6add4d8436691a8dfaa3bc6a9cb64593b2e5009735bab08b1b8
+size 69221
diff --git a/blog_data/images/blog_313c589aab9d_2.jpg b/blog_data/images/blog_313c589aab9d_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..34c5e9f9966009981365501901244056b4439360
--- /dev/null
+++ b/blog_data/images/blog_313c589aab9d_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5f5d9b57ac6fdeb863798d8c1db7668bc194d5fdbe13cc930e4299d4ba7f49b4
+size 101974
diff --git a/blog_data/images/blog_313c589aab9d_3.jpg b/blog_data/images/blog_313c589aab9d_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7305c2bb725f98524be7b06d58ebaf04f134d61b
--- /dev/null
+++ b/blog_data/images/blog_313c589aab9d_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:785f907e14388d8a505639e846793b4a21c2683641b54c98d7da2072187fdc56
+size 206757
diff --git a/blog_data/images/blog_313c589aab9d_4.bin b/blog_data/images/blog_313c589aab9d_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_313c589aab9d_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_313c589aab9d_5.bin b/blog_data/images/blog_313c589aab9d_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_313c589aab9d_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_32639a1b455a_0.jpg b/blog_data/images/blog_32639a1b455a_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9194d6800d19b620288d71fe86aa737c206fd527
--- /dev/null
+++ b/blog_data/images/blog_32639a1b455a_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88905ff3550ada779e59ae4524b18d1c0d35fc79ba3dcdcff3fd5a6e93c945a8
+size 145513
diff --git a/blog_data/images/blog_32639a1b455a_1.jpg b/blog_data/images/blog_32639a1b455a_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1367942a18f4ad310b4370f78f4e3a8babd18a05
--- /dev/null
+++ b/blog_data/images/blog_32639a1b455a_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:abc79155824f0f3b47c39eb165bd9a9cfd11a299a6e0b3827a3b4fdf582b8bf5
+size 228012
diff --git a/blog_data/images/blog_32639a1b455a_10.bin b/blog_data/images/blog_32639a1b455a_10.bin
new file mode 100644
index 0000000000000000000000000000000000000000..b73d97f97ce0d7137023ba073f46d95ef086c73a
--- /dev/null
+++ b/blog_data/images/blog_32639a1b455a_10.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:91edac3936073fa3ae6191cd6d4dc363d4b667299fa14dd933cdcd9fd91e88ce
+size 220753
diff --git a/blog_data/images/blog_32639a1b455a_11.bin b/blog_data/images/blog_32639a1b455a_11.bin
new file mode 100644
index 0000000000000000000000000000000000000000..7e92f471e351955a220cde15db2561950aea84f1
--- /dev/null
+++ b/blog_data/images/blog_32639a1b455a_11.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:26273ff035635a1266a24ee981da66c0dab81af9a5d4c0aeb5910849f3bc679c
+size 68235
diff --git a/blog_data/images/blog_32639a1b455a_12.bin b/blog_data/images/blog_32639a1b455a_12.bin
new file mode 100644
index 0000000000000000000000000000000000000000..cc9d2097d6c4ad7bc67e07899c4b1b668411fa01
--- /dev/null
+++ b/blog_data/images/blog_32639a1b455a_12.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae3be77214461f7aeb128dee270fe82e5cfc0572032bc5602fc31239f51d4a37
+size 527256
diff --git a/blog_data/images/blog_32639a1b455a_13.bin b/blog_data/images/blog_32639a1b455a_13.bin
new file mode 100644
index 0000000000000000000000000000000000000000..5ab11749237d678988d8713622ab9a84a8ca000d
--- /dev/null
+++ b/blog_data/images/blog_32639a1b455a_13.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8494161df87f55c1a5f9f6d373edca9af26b66d8a3d5ab98a7739452e8db4afc
+size 657723
diff --git a/blog_data/images/blog_32639a1b455a_14.bin b/blog_data/images/blog_32639a1b455a_14.bin
new file mode 100644
index 0000000000000000000000000000000000000000..73e66f3f799f3e94fb2f5178f5348c48c65b141c
--- /dev/null
+++ b/blog_data/images/blog_32639a1b455a_14.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:37e556b42e9ba29977cd7469b31b12fee5443c6857ceb4b83c480f2a1a26faba
+size 310221
diff --git a/blog_data/images/blog_32639a1b455a_15.bin b/blog_data/images/blog_32639a1b455a_15.bin
new file mode 100644
index 0000000000000000000000000000000000000000..429d00c2230ffaa8f5b83075cc08bd9ec09026bd
--- /dev/null
+++ b/blog_data/images/blog_32639a1b455a_15.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cb3ce4eab8ae64a7ebc1ecb6d143e9e2772a603067c887d14b912d97243cffd3
+size 185246
diff --git a/blog_data/images/blog_32639a1b455a_16.bin b/blog_data/images/blog_32639a1b455a_16.bin
new file mode 100644
index 0000000000000000000000000000000000000000..b49b0b9c5f7298a85e8a995eecbac23a0d73a5d8
--- /dev/null
+++ b/blog_data/images/blog_32639a1b455a_16.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ee98aba61726d742cf86b17f68581ed5726198d64d1f0f0ee18986d9d7524c09
+size 200119
diff --git a/blog_data/images/blog_32639a1b455a_17.bin b/blog_data/images/blog_32639a1b455a_17.bin
new file mode 100644
index 0000000000000000000000000000000000000000..235e92a517b24cd97cea49c1bb798cfc989e12dd
--- /dev/null
+++ b/blog_data/images/blog_32639a1b455a_17.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:045b6733c55f70e17480679e752c5bce6c0e220c86691966e8057f250106ac79
+size 705279
diff --git a/blog_data/images/blog_32639a1b455a_2.jpg b/blog_data/images/blog_32639a1b455a_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0a9d2189728394c6b6f20f9e13ce02548dba094f
--- /dev/null
+++ b/blog_data/images/blog_32639a1b455a_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:330eadc1d39d3ca90ee58ea394c955a508a33d2864984f06ae8f40cc0f3e45f5
+size 345532
diff --git a/blog_data/images/blog_32639a1b455a_3.jpg b/blog_data/images/blog_32639a1b455a_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..482a1f1683ae3f6599875dbc6ee56a3affc6b4a3
--- /dev/null
+++ b/blog_data/images/blog_32639a1b455a_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8e1adb55cbf40b77eded47584fb23ffd9707fedc320df9e844e5c80164174168
+size 234122
diff --git a/blog_data/images/blog_32639a1b455a_4.jpg b/blog_data/images/blog_32639a1b455a_4.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5d2cfaa509046e86cfaaea597c025bed42ed06dc
--- /dev/null
+++ b/blog_data/images/blog_32639a1b455a_4.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a3b9ccb57415f6f0e5a16d676a003d3f4e6baf85275681153e84e76f2b241e5d
+size 699411
diff --git a/blog_data/images/blog_32639a1b455a_5.jpg b/blog_data/images/blog_32639a1b455a_5.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bcf5552eba3e8c9305307fb6cb4493f32de784be
--- /dev/null
+++ b/blog_data/images/blog_32639a1b455a_5.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:35c4261177b87e76d6c3216e8f0f0ac128d43f92ae572a10fd0b6cf504696c2d
+size 183597
diff --git a/blog_data/images/blog_32639a1b455a_6.jpg b/blog_data/images/blog_32639a1b455a_6.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4f02fc7bb9f4ecc803ee690d8b14f0111c5c7f8e
--- /dev/null
+++ b/blog_data/images/blog_32639a1b455a_6.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c2f2c2b08d4f32606422bcce615be170766c90280f76e5155975d4462897621
+size 676652
diff --git a/blog_data/images/blog_32639a1b455a_7.jpg b/blog_data/images/blog_32639a1b455a_7.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..534261c48e794c67e2b5eb47c74b696c47deca66
--- /dev/null
+++ b/blog_data/images/blog_32639a1b455a_7.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6003f059abb920af1367c6e60908c3506e09165813ecfed83a65853cf36078ff
+size 46629
diff --git a/blog_data/images/blog_32639a1b455a_8.jpg b/blog_data/images/blog_32639a1b455a_8.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4094980ac8b2cd9dee6cdd9485be5e8afc76d4f6
--- /dev/null
+++ b/blog_data/images/blog_32639a1b455a_8.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:374c634676c419fe61b10813d1b75cb1be3324e832e18bd99e4c4b9c2c3e04c3
+size 175225
diff --git a/blog_data/images/blog_32639a1b455a_9.jpg b/blog_data/images/blog_32639a1b455a_9.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fc5f57ecf0de9dc6403e49be35caebe02132d76e
--- /dev/null
+++ b/blog_data/images/blog_32639a1b455a_9.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:193c9e384629eebdefc9aaaec947b3a37cb7b403db4cd200fecd75d8273432b4
+size 460194
diff --git a/blog_data/images/blog_3313f8663bc5_0.jpg b/blog_data/images/blog_3313f8663bc5_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bcf73211567a28e983ab08cd85d71126b7b2233b
--- /dev/null
+++ b/blog_data/images/blog_3313f8663bc5_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bdf25c059b0bf45b298ca1debe581f0fe0bd352636f6e2c3f92ef37b6e97b90a
+size 120786
diff --git a/blog_data/images/blog_3313f8663bc5_1.jpg b/blog_data/images/blog_3313f8663bc5_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c24609420f6be79f912e82da5d8dbe19c4cf3058
--- /dev/null
+++ b/blog_data/images/blog_3313f8663bc5_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a15ae7cb5b24430e427308931b109212cc57de4d37b51453f0a44e05489ab220
+size 133289
diff --git a/blog_data/images/blog_3313f8663bc5_2.jpg b/blog_data/images/blog_3313f8663bc5_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..41799a70990d67cf8ef24d777e49ab2d8f8681d6
--- /dev/null
+++ b/blog_data/images/blog_3313f8663bc5_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc5c6fdae19383d48c45d450fd49c62f2f54c55f829887611b6e5e4efe6f4304
+size 141631
diff --git a/blog_data/images/blog_3313f8663bc5_3.jpg b/blog_data/images/blog_3313f8663bc5_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..306e38897ac1ca3950a5f38cfae35e23bf8106b1
--- /dev/null
+++ b/blog_data/images/blog_3313f8663bc5_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9c1d5fcb1f13130ac3603f3f95503203edf9a0cb37ecd22c90f1afbd5df0d405
+size 116805
diff --git a/blog_data/images/blog_3313f8663bc5_4.bin b/blog_data/images/blog_3313f8663bc5_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_3313f8663bc5_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_3313f8663bc5_5.bin b/blog_data/images/blog_3313f8663bc5_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_3313f8663bc5_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_35d9b409a2e0_0.bin b/blog_data/images/blog_35d9b409a2e0_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..7b2fc8f6aa1241d9b31e5bc05542e8d89e1031e9
--- /dev/null
+++ b/blog_data/images/blog_35d9b409a2e0_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3a1808ea2b009dd3cee92f1d4c4fe0237e2648bf9c242f5c1fc861015fa61ca7
+size 108288
diff --git a/blog_data/images/blog_35d9b409a2e0_1.bin b/blog_data/images/blog_35d9b409a2e0_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..bca7df5f51b640bf5e5324265d6f991218946a64
--- /dev/null
+++ b/blog_data/images/blog_35d9b409a2e0_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2bc4d3e1192ec561a40b48fbe7ffca2fa7a9adcc59179de90b5b7a29abd7001b
+size 85776
diff --git a/blog_data/images/blog_35d9b409a2e0_2.bin b/blog_data/images/blog_35d9b409a2e0_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..1b653f0ed773e8221837c3a909199363d82e0350
--- /dev/null
+++ b/blog_data/images/blog_35d9b409a2e0_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f9b7362cec11ce42c2f96c4c74b10032ad7ba87e3c09abe9e6ac939abbd4b8c9
+size 52492
diff --git a/blog_data/images/blog_35d9b409a2e0_3.bin b/blog_data/images/blog_35d9b409a2e0_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..2f0cb524888ee8701fcc63df6849ff638bdf686e
--- /dev/null
+++ b/blog_data/images/blog_35d9b409a2e0_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:63dd190cbc9d552900964acfc47049777104d5b9a75778f6845b0626e1924eae
+size 155714
diff --git a/blog_data/images/blog_35d9b409a2e0_4.bin b/blog_data/images/blog_35d9b409a2e0_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..34a8c2febf9cd117a6f988cb9592d371ee4c62af
--- /dev/null
+++ b/blog_data/images/blog_35d9b409a2e0_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:405384e290677465d24447e1f154e97178be6f23e14794aa820fa6a63887f698
+size 49840
diff --git a/blog_data/images/blog_35d9b409a2e0_5.bin b/blog_data/images/blog_35d9b409a2e0_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..ae6dbb793be27ce633b6703899b63728bdbeb895
--- /dev/null
+++ b/blog_data/images/blog_35d9b409a2e0_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b4949e6b7a71c6e696c052c5395ac424ba478048a43724ed704762f734d6181e
+size 24026
diff --git a/blog_data/images/blog_36758270acc3_0.jpg b/blog_data/images/blog_36758270acc3_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..00d63a3201bf7b39d4e6ca6f9054189dbcd8526c
--- /dev/null
+++ b/blog_data/images/blog_36758270acc3_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c02fcc7a9760f72522e367500de4c0e3ed0535fd8d3b192f6f42a8ba6d8907d
+size 42871
diff --git a/blog_data/images/blog_36758270acc3_1.jpg b/blog_data/images/blog_36758270acc3_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6537bac3e0129d41c5712bb2324489ae7e3e8f7a
--- /dev/null
+++ b/blog_data/images/blog_36758270acc3_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:304e2180b575b0312c3d02b04dbde1952d517b2005afadfd05e8ac9659395f1b
+size 63625
diff --git a/blog_data/images/blog_36758270acc3_2.jpg b/blog_data/images/blog_36758270acc3_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..93948bebf6d4753c8c87813fdb6d009f9a178741
--- /dev/null
+++ b/blog_data/images/blog_36758270acc3_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5d999da2676683002a679822420881cb93a99cbf8c439b2c19e1eecc6c279fb8
+size 129600
diff --git a/blog_data/images/blog_36758270acc3_3.jpg b/blog_data/images/blog_36758270acc3_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..97f264c9b54b7eb916214657cee8f00e7e3b58bf
--- /dev/null
+++ b/blog_data/images/blog_36758270acc3_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c6040ee6f08e5f7bd5d902d04c55d517ae2a1d01b8f69d92c1d661e883108581
+size 110716
diff --git a/blog_data/images/blog_36758270acc3_4.bin b/blog_data/images/blog_36758270acc3_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_36758270acc3_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_36758270acc3_5.bin b/blog_data/images/blog_36758270acc3_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_36758270acc3_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_3857113ce3ae_0.jpg b/blog_data/images/blog_3857113ce3ae_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1bb6fd4c3adb2e922cb8cb9212e1dc96a5e0b999
--- /dev/null
+++ b/blog_data/images/blog_3857113ce3ae_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:58fc4b8624a37bd57dc6b78ad0cb4543ad14ace980f41872dafd51ac6eca9d7c
+size 60096
diff --git a/blog_data/images/blog_3857113ce3ae_1.jpg b/blog_data/images/blog_3857113ce3ae_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ebb6cde4c22457fcff8f3d175252b3ac341e8a13
--- /dev/null
+++ b/blog_data/images/blog_3857113ce3ae_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ec7cd11dc79ef75f42a7d5074c84de3820bc46f41d326dc13beed7fcce6d08d6
+size 118706
diff --git a/blog_data/images/blog_3857113ce3ae_2.jpg b/blog_data/images/blog_3857113ce3ae_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..07c56463e633284a39546fcce9c1dcba609d12c2
--- /dev/null
+++ b/blog_data/images/blog_3857113ce3ae_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f0b176f3e83adbcc9cd84406d08537882839257a8a18ce7fad16dff18ae47e51
+size 56514
diff --git a/blog_data/images/blog_3857113ce3ae_3.jpg b/blog_data/images/blog_3857113ce3ae_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..26bf4264db78b8f0276204f6759833e961f6c2a5
--- /dev/null
+++ b/blog_data/images/blog_3857113ce3ae_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:37ac84f995f7d08aa4dbcb1e63af3745ef35a659ac8596050c0b6171c326ea52
+size 79945
diff --git a/blog_data/images/blog_3857113ce3ae_4.jpg b/blog_data/images/blog_3857113ce3ae_4.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5361c29746078d8fa02afaff9b7e697ca5664d4d
--- /dev/null
+++ b/blog_data/images/blog_3857113ce3ae_4.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:71b56bdf5edccad286c3a217bfa88d674af98f78da5153981256b16fb0431dbf
+size 90615
diff --git a/blog_data/images/blog_3857113ce3ae_5.bin b/blog_data/images/blog_3857113ce3ae_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_3857113ce3ae_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_3857113ce3ae_6.bin b/blog_data/images/blog_3857113ce3ae_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_3857113ce3ae_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_411c2c255975_0.bin b/blog_data/images/blog_411c2c255975_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..a98fb12b4b95968fd8541da0d22fe234787bd219
--- /dev/null
+++ b/blog_data/images/blog_411c2c255975_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c05bff45c78330821af7390269694de6a2f9241f97953e164c99e137181d5abe
+size 278089
diff --git a/blog_data/images/blog_411c2c255975_1.bin b/blog_data/images/blog_411c2c255975_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..c0fc45a77142372acbcd45f96a9c5bb508da92cd
--- /dev/null
+++ b/blog_data/images/blog_411c2c255975_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f8a0e86cd4cee95e9b0795a8ef4f31b06522fd029616507d80d385725d647778
+size 2025613
diff --git a/blog_data/images/blog_411c2c255975_2.bin b/blog_data/images/blog_411c2c255975_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..952c963183781f1dede1752c3f4f2c02f962dae4
--- /dev/null
+++ b/blog_data/images/blog_411c2c255975_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9775405189f069454f66f9d30560617ec53feff2145b39f6d439e026c057f573
+size 46683
diff --git a/blog_data/images/blog_4806e024679a_0.jpg b/blog_data/images/blog_4806e024679a_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8d8299d99be72f3b6611572be0d5cf4734124a9b
--- /dev/null
+++ b/blog_data/images/blog_4806e024679a_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:78519d13a125bc33fee6b6a33dc4241fbce141c3593abcd01b76e680e9eedef1
+size 45102
diff --git a/blog_data/images/blog_4806e024679a_1.jpg b/blog_data/images/blog_4806e024679a_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..03d3773c0e8cf93659dca6e3a299f2f2886059d7
--- /dev/null
+++ b/blog_data/images/blog_4806e024679a_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4eb458cfbae9a29d26e822323116c1d576036852dc667706b90d7c0e5b95bb05
+size 61122
diff --git a/blog_data/images/blog_4806e024679a_2.jpg b/blog_data/images/blog_4806e024679a_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f609a8d8ce4f3ca51d768f2b4d70b51b10694f1c
--- /dev/null
+++ b/blog_data/images/blog_4806e024679a_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:29399c8168dfd36cd5baf8c0611db0cc12f35756f39d7131f2b1cbd48b3d2a79
+size 94642
diff --git a/blog_data/images/blog_4806e024679a_3.jpg b/blog_data/images/blog_4806e024679a_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..008f0eded69c31866b026210dd49a268e82571f0
--- /dev/null
+++ b/blog_data/images/blog_4806e024679a_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:76816061b432f96706e32e98a4628ab5ce9f18f9da61b1a090419141494a1da8
+size 43454
diff --git a/blog_data/images/blog_4806e024679a_4.bin b/blog_data/images/blog_4806e024679a_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_4806e024679a_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_4806e024679a_5.bin b/blog_data/images/blog_4806e024679a_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_4806e024679a_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_48a4834913f4_0.jpg b/blog_data/images/blog_48a4834913f4_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..049a920316c48df6c248f2bf69b4bece0619f4c4
--- /dev/null
+++ b/blog_data/images/blog_48a4834913f4_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e73ca70d7cbcebcc688c2555a45cd89217d531fb519d7ef50dc6c75c8e911801
+size 40341
diff --git a/blog_data/images/blog_48a4834913f4_1.jpg b/blog_data/images/blog_48a4834913f4_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c1958bc9a561eafd01e811a14e447b98f36a5625
--- /dev/null
+++ b/blog_data/images/blog_48a4834913f4_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:00575a2b928d67b2721fdccdd1a0098100fb5b8866f38b184e6a0b07812a3a56
+size 40023
diff --git a/blog_data/images/blog_48a4834913f4_2.jpg b/blog_data/images/blog_48a4834913f4_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..39d0e818fea29f4869d4b8cfd074e99de0ed7ea5
--- /dev/null
+++ b/blog_data/images/blog_48a4834913f4_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:914e128f02bc4103f9427fa8267db55546f3bd609ad098b436feed8802cd7406
+size 121893
diff --git a/blog_data/images/blog_48a4834913f4_3.jpg b/blog_data/images/blog_48a4834913f4_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bec070af8533cd64e5b6e357ac7395bdafde82cc
--- /dev/null
+++ b/blog_data/images/blog_48a4834913f4_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:627d73e3fa49772312927f5e2b78d3f020c4bb7cfb7db1a99fbddd3e6fb90bc0
+size 69122
diff --git a/blog_data/images/blog_48a4834913f4_4.jpg b/blog_data/images/blog_48a4834913f4_4.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..91a4ea94eaac12846250f28a3b15a6408e291c60
--- /dev/null
+++ b/blog_data/images/blog_48a4834913f4_4.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:45007530de9fa472412ccb70879349976cb6fe0c80afc9c2f08ead54b336782c
+size 48031
diff --git a/blog_data/images/blog_48a4834913f4_5.jpg b/blog_data/images/blog_48a4834913f4_5.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ba052116821c9d32afac9ec0e1ee5e10d531c10a
--- /dev/null
+++ b/blog_data/images/blog_48a4834913f4_5.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:86db676aa984b1850777dbc33b994c8caa9fb781bd0f1428372d6fdbe1537ea9
+size 62789
diff --git a/blog_data/images/blog_48a4834913f4_6.bin b/blog_data/images/blog_48a4834913f4_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_48a4834913f4_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_48a4834913f4_7.bin b/blog_data/images/blog_48a4834913f4_7.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_48a4834913f4_7.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_48dd986907b2_0.jpg b/blog_data/images/blog_48dd986907b2_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..decc5085fc63d0fedafe522d9b7ac346dde47370
--- /dev/null
+++ b/blog_data/images/blog_48dd986907b2_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:26bb4efbca5be0e08d496225e7adeea60739a48225b981318843be303b350565
+size 85000
diff --git a/blog_data/images/blog_48dd986907b2_1.jpg b/blog_data/images/blog_48dd986907b2_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1e89c83da0f14e4fc47cfea73304135fef0d8366
--- /dev/null
+++ b/blog_data/images/blog_48dd986907b2_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b379f4682dbb87acb166c3f8f20cc2c770afd188c6cf91994df6623b5f9fcf0a
+size 79515
diff --git a/blog_data/images/blog_48dd986907b2_2.jpg b/blog_data/images/blog_48dd986907b2_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5c1e4284daf03091ef7f63b2e26d007bd4e555d1
--- /dev/null
+++ b/blog_data/images/blog_48dd986907b2_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cd2089e571deefcd53c25951e5e0f061b5a3b7f9e89862f9c3ce400cf0fb90d0
+size 39676
diff --git a/blog_data/images/blog_48dd986907b2_3.bin b/blog_data/images/blog_48dd986907b2_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_48dd986907b2_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_48dd986907b2_4.bin b/blog_data/images/blog_48dd986907b2_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_48dd986907b2_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_4a59b13cd215_0.bin b/blog_data/images/blog_4a59b13cd215_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..3d4439adf7f1baf5bc0dd7cdde8f2480a70364b4
--- /dev/null
+++ b/blog_data/images/blog_4a59b13cd215_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:350586f60a851072433e412acc600e5b50bcf027c29096041212ac7c80149927
+size 4978
diff --git a/blog_data/images/blog_4a59b13cd215_1.bin b/blog_data/images/blog_4a59b13cd215_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..b51bc27a0bd07289c0867293a70f88ebd7bae48c
--- /dev/null
+++ b/blog_data/images/blog_4a59b13cd215_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1e75ae70a9cc87447fb52f7db08112ee861bac96802651e29aadf5444db8b3b
+size 5162
diff --git a/blog_data/images/blog_4a59b13cd215_2.bin b/blog_data/images/blog_4a59b13cd215_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..3d5a51fb0d9ff9a42843e2504b0704ee3b467d67
--- /dev/null
+++ b/blog_data/images/blog_4a59b13cd215_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:679f46392dde1e4c3003fcaf43dfde15a418204ce2c0d4b0a2f737670417ab5e
+size 4984
diff --git a/blog_data/images/blog_4e845964b896_0.bin b/blog_data/images/blog_4e845964b896_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..7faa70d4109d9373c363eed6c0580e9ccce60c79
--- /dev/null
+++ b/blog_data/images/blog_4e845964b896_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e01d22e939786d7f49a3568a236489359452e4d2d8354639b9d880a97429375f
+size 10986
diff --git a/blog_data/images/blog_4e845964b896_1.bin b/blog_data/images/blog_4e845964b896_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..660b11a67470fbbe8d715cc6c7e22d9f01f1ae6c
--- /dev/null
+++ b/blog_data/images/blog_4e845964b896_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3c0e4bf7600a4286884e21cd75443f906978aea0af38c8665107c21c031b2b9e
+size 15436
diff --git a/blog_data/images/blog_4e845964b896_2.bin b/blog_data/images/blog_4e845964b896_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..0cad29c071e1bb40ad07aa8f6a947298d0e7c7d2
--- /dev/null
+++ b/blog_data/images/blog_4e845964b896_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:522669370f3b6977d8ee4a72659a38df4fe232e371dbd62a9494a9b1c6182d0f
+size 12516
diff --git a/blog_data/images/blog_4e845964b896_3.bin b/blog_data/images/blog_4e845964b896_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..eaf4ba5b12d73f350b2e66c8de3d015e60a71fb2
--- /dev/null
+++ b/blog_data/images/blog_4e845964b896_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5c1c5b7f1c837a32d99bf308b29bffecfcbe623a9771e2f42bb1155da8717f04
+size 21138
diff --git a/blog_data/images/blog_4e845964b896_4.bin b/blog_data/images/blog_4e845964b896_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..78ffe6d3639001541f06e68eff2a491c44125f17
--- /dev/null
+++ b/blog_data/images/blog_4e845964b896_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5b207012dc80faf5f606f59641fcbf60b8f90e913d18c7e72e65636869b300af
+size 22518
diff --git a/blog_data/images/blog_4e845964b896_5.bin b/blog_data/images/blog_4e845964b896_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..1f1c195118db73e6e9283c3488ec6a05ea0337ea
--- /dev/null
+++ b/blog_data/images/blog_4e845964b896_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae97f5992e8f73bfedd7a1165cf2705568ec7d61afb66b65d657c0d3e090d097
+size 27920
diff --git a/blog_data/images/blog_507c41233492_0.bin b/blog_data/images/blog_507c41233492_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..62c32f47baa80b7532e81876c8748ca0c68de021
--- /dev/null
+++ b/blog_data/images/blog_507c41233492_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2aac2742b7bb253857d0080ae6d23f3bd521e85272b141769684077e8cf2722a
+size 6044
diff --git a/blog_data/images/blog_507c41233492_1.bin b/blog_data/images/blog_507c41233492_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..969f4b30fa72d8349a5a7c3cbcd7a889f0b0d9b6
--- /dev/null
+++ b/blog_data/images/blog_507c41233492_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fdce5e1d51c89cbff4d74ba295a2f9770980e2a0d062351278a5d06d283e71c7
+size 23300
diff --git a/blog_data/images/blog_507c41233492_2.bin b/blog_data/images/blog_507c41233492_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..a9bd0a9404a9dae630aeddd5fe0790017163c555
--- /dev/null
+++ b/blog_data/images/blog_507c41233492_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e3c4aa47e8ce4c1ceb581a9daf094519d40c5eea2cf6146a9d91e0084dcf4c8c
+size 21878
diff --git a/blog_data/images/blog_517f0e7f0bb1_0.bin b/blog_data/images/blog_517f0e7f0bb1_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..2dfe9750ed0d199b89eadcbc671da824bdc5ab85
--- /dev/null
+++ b/blog_data/images/blog_517f0e7f0bb1_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7e053d509fdf621ed36afcef232b6d2067df512d6b53d5ffd3bfd9141701adbf
+size 705475
diff --git a/blog_data/images/blog_517f0e7f0bb1_1.bin b/blog_data/images/blog_517f0e7f0bb1_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..39ba1199346674fb2a43928eb1983306493a9094
--- /dev/null
+++ b/blog_data/images/blog_517f0e7f0bb1_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4fb518e37316311185b5020e7f3513a4e28de134e5199efadec4b6d4a2bf61e7
+size 411826
diff --git a/blog_data/images/blog_517f0e7f0bb1_10.bin b/blog_data/images/blog_517f0e7f0bb1_10.bin
new file mode 100644
index 0000000000000000000000000000000000000000..b26900961959163f46d3414eed843dec2d8cb1d7
--- /dev/null
+++ b/blog_data/images/blog_517f0e7f0bb1_10.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fce4cf21087a30c7f756d60e7c7e6bcc4aabe17e84177a6a83e531a738bfeeb2
+size 513653
diff --git a/blog_data/images/blog_517f0e7f0bb1_2.bin b/blog_data/images/blog_517f0e7f0bb1_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..08b3e5a8a8e8da44cd35d063f72efa84295b4276
--- /dev/null
+++ b/blog_data/images/blog_517f0e7f0bb1_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d8e6f8029ecce8570bdf5b3818b2f59176c7c6580fac5320a8901e8f7f14e5f3
+size 386425
diff --git a/blog_data/images/blog_517f0e7f0bb1_3.bin b/blog_data/images/blog_517f0e7f0bb1_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..e35ce8e2f88e49dd25722dbeac920419bcac4e3d
--- /dev/null
+++ b/blog_data/images/blog_517f0e7f0bb1_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0e637bd244e53620c3793441fb7c83c0acac5fa5d9100659b82f4596f7bf8f25
+size 436721
diff --git a/blog_data/images/blog_517f0e7f0bb1_4.bin b/blog_data/images/blog_517f0e7f0bb1_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..a342a47a4f634d5fb962d31c7c909bae5183a145
--- /dev/null
+++ b/blog_data/images/blog_517f0e7f0bb1_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:edd9c43818086b2fbf11472154c59542e8191cfe3acf4eb7aacec9b1c7df0362
+size 359575
diff --git a/blog_data/images/blog_517f0e7f0bb1_5.bin b/blog_data/images/blog_517f0e7f0bb1_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..8bed684868bc5d9ee9c64604d1fdc7941f667313
--- /dev/null
+++ b/blog_data/images/blog_517f0e7f0bb1_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a2a7db4ac7f585aff57444ff7c84f8b3af0137cbbed90c1a3e4acfc0043e96a9
+size 477822
diff --git a/blog_data/images/blog_517f0e7f0bb1_6.bin b/blog_data/images/blog_517f0e7f0bb1_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..8f3d249665323f8de33aace864868b2d36d5baf1
--- /dev/null
+++ b/blog_data/images/blog_517f0e7f0bb1_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:af0719ec60a3b540107a238c77b14a63919b04b42b99ac9c4d069c90d3bfbd9a
+size 441624
diff --git a/blog_data/images/blog_517f0e7f0bb1_7.bin b/blog_data/images/blog_517f0e7f0bb1_7.bin
new file mode 100644
index 0000000000000000000000000000000000000000..11fdfef20837e8f3ff2e7487d0b0bb640c7d794d
--- /dev/null
+++ b/blog_data/images/blog_517f0e7f0bb1_7.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7e89ea39ebe651928388a1cddae90683a8539807a86bf41caf780343285effdb
+size 410973
diff --git a/blog_data/images/blog_517f0e7f0bb1_8.bin b/blog_data/images/blog_517f0e7f0bb1_8.bin
new file mode 100644
index 0000000000000000000000000000000000000000..a3c02fbec4600e0bd783211b2ad47ebfbd6dfdba
--- /dev/null
+++ b/blog_data/images/blog_517f0e7f0bb1_8.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:51448880baa2b12924b5436289d41130f9854558a9bcd8aa610c0ab8885d0e90
+size 436717
diff --git a/blog_data/images/blog_517f0e7f0bb1_9.bin b/blog_data/images/blog_517f0e7f0bb1_9.bin
new file mode 100644
index 0000000000000000000000000000000000000000..165ae3626fc3db214f50de930d3db78cf0ea2296
--- /dev/null
+++ b/blog_data/images/blog_517f0e7f0bb1_9.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:86ffacb1860c3b25acaf877570c33ad4fb071dc6100e443de1771f2e0331eb57
+size 397736
diff --git a/blog_data/images/blog_51d0100fef63_0.jpg b/blog_data/images/blog_51d0100fef63_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4c358449c2bcf9d5f8309b6f8f5a7d23ff7fec07
--- /dev/null
+++ b/blog_data/images/blog_51d0100fef63_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c4322a66974e641d62602ec8f1c067ac3837873ae73efab720ddee0346724164
+size 53314
diff --git a/blog_data/images/blog_51d0100fef63_1.jpg b/blog_data/images/blog_51d0100fef63_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..80d00103efb1fc7b39c06f850b500c55066d3b80
--- /dev/null
+++ b/blog_data/images/blog_51d0100fef63_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e1291fcb7e0f89e0a005c0167e23531377c352f495ea2da49173dde2640caaa4
+size 71488
diff --git a/blog_data/images/blog_51d0100fef63_2.jpg b/blog_data/images/blog_51d0100fef63_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..02c0d9be956ddbbf049c19d75c37a99715bb5371
--- /dev/null
+++ b/blog_data/images/blog_51d0100fef63_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c927211913be0181d66ac4d903b0e5e3994e57c3767a49bda5b89c4e3e80f34f
+size 121462
diff --git a/blog_data/images/blog_51d0100fef63_3.jpg b/blog_data/images/blog_51d0100fef63_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4e3297f1b358dfae4ed508db3e1de17f4dd4852c
--- /dev/null
+++ b/blog_data/images/blog_51d0100fef63_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7d20849299c6c3178f97e0023402ceac0bd523662fde3c7f4d25a11837c20f02
+size 61506
diff --git a/blog_data/images/blog_51d0100fef63_4.bin b/blog_data/images/blog_51d0100fef63_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_51d0100fef63_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_51d0100fef63_5.bin b/blog_data/images/blog_51d0100fef63_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_51d0100fef63_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_54129e987971_0.jpg b/blog_data/images/blog_54129e987971_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8b9aaa24b4515a2fe57a47dd80df2f554a69cdd2
--- /dev/null
+++ b/blog_data/images/blog_54129e987971_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5f6001dff1b0168d853ad22a4b2129077893dba5b8d7081e1b974ea85f6a5753
+size 120197
diff --git a/blog_data/images/blog_54129e987971_1.bin b/blog_data/images/blog_54129e987971_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_54129e987971_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_54129e987971_2.bin b/blog_data/images/blog_54129e987971_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_54129e987971_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_54bf39ddea87_0.jpg b/blog_data/images/blog_54bf39ddea87_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..adf365f8acf1944dddc773f909eab2487fd84819
--- /dev/null
+++ b/blog_data/images/blog_54bf39ddea87_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7f0588922c1a0b78367765c8c78f39919f1e6466177302acb2eaafb48ca95059
+size 90753
diff --git a/blog_data/images/blog_54bf39ddea87_1.jpg b/blog_data/images/blog_54bf39ddea87_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d95bf9c88a1887dd290262f5d5502eb31e534204
--- /dev/null
+++ b/blog_data/images/blog_54bf39ddea87_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:48fdebd15cee63a38e3aea4fa8809e4b8e278dfe2cdabb2466c88181373ae4bc
+size 121549
diff --git a/blog_data/images/blog_54bf39ddea87_2.jpg b/blog_data/images/blog_54bf39ddea87_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f4eab34508d9373d1c2a8f5c1d17a7e328bc012c
--- /dev/null
+++ b/blog_data/images/blog_54bf39ddea87_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:553149e85059414f0c0e7a9586b9a6ba32de6774bb0cd0b8808831904d5ef0e1
+size 230982
diff --git a/blog_data/images/blog_54bf39ddea87_3.jpg b/blog_data/images/blog_54bf39ddea87_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d7dbc6bbf1b6c3cc62a2e67b30e4c363774092ab
--- /dev/null
+++ b/blog_data/images/blog_54bf39ddea87_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0af7df71734d65b269ae42b1020add9150753dd0776498554a8eb5dc5505580b
+size 130726
diff --git a/blog_data/images/blog_54bf39ddea87_4.jpg b/blog_data/images/blog_54bf39ddea87_4.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..155ea452b4bffa7db78fc92dcfabf6d25969c2db
--- /dev/null
+++ b/blog_data/images/blog_54bf39ddea87_4.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b4c3129a232b84f5d13218a191405bf421079d3142c1c7516e6271c7bfab871c
+size 38216
diff --git a/blog_data/images/blog_54bf39ddea87_5.bin b/blog_data/images/blog_54bf39ddea87_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_54bf39ddea87_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_54bf39ddea87_6.bin b/blog_data/images/blog_54bf39ddea87_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_54bf39ddea87_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_56efee5333b5_0.jpg b/blog_data/images/blog_56efee5333b5_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8df7664fb4b33e5f232abb7a0fbaf3bc32eef0d9
--- /dev/null
+++ b/blog_data/images/blog_56efee5333b5_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f373c237c2b7e06aca8c8418e3fd0bab98169e9227f7ba643ed3ba64ed86f13a
+size 58832
diff --git a/blog_data/images/blog_56efee5333b5_1.jpg b/blog_data/images/blog_56efee5333b5_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aac2107347ed3e50a472b69d1fb41bb1d7eec326
--- /dev/null
+++ b/blog_data/images/blog_56efee5333b5_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ff3235b9cb343ace66cb8cdf8013c9ebc7154a32ec06ce5e64798326800e038
+size 111542
diff --git a/blog_data/images/blog_56efee5333b5_2.jpg b/blog_data/images/blog_56efee5333b5_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6b80433fb21ffb3f9bbcb3167aee656c17b5e65a
--- /dev/null
+++ b/blog_data/images/blog_56efee5333b5_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:719c49349a1e854b787a727a436a9f78f6029bc11eafb283004a75c512bb31ad
+size 102399
diff --git a/blog_data/images/blog_56efee5333b5_3.jpg b/blog_data/images/blog_56efee5333b5_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ca12c4aa830a5943d06cba73918b53834c7e68a7
--- /dev/null
+++ b/blog_data/images/blog_56efee5333b5_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a1042ac95f0bd2c77f2eb5159afddb49922d5ce7f3f47863b24067c1a36311ac
+size 97521
diff --git a/blog_data/images/blog_56efee5333b5_4.bin b/blog_data/images/blog_56efee5333b5_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_56efee5333b5_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_56efee5333b5_5.bin b/blog_data/images/blog_56efee5333b5_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_56efee5333b5_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_581c59c84ebb_0.jpg b/blog_data/images/blog_581c59c84ebb_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5533a77c50f34377cb4756129df07cecd7de33e4
--- /dev/null
+++ b/blog_data/images/blog_581c59c84ebb_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fffb778141f795272ac91b27462b802662ff15d656690349cb2ba02edab8fbb7
+size 243371
diff --git a/blog_data/images/blog_581c59c84ebb_1.jpg b/blog_data/images/blog_581c59c84ebb_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..73b9e8aa5ba00589e6ee028afb6c586827f606c6
--- /dev/null
+++ b/blog_data/images/blog_581c59c84ebb_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5e14b00d7f6a3690f7239ffb4c7d210b426e672a5efdc183659402f9d53c53c3
+size 26957
diff --git a/blog_data/images/blog_581c59c84ebb_2.jpg b/blog_data/images/blog_581c59c84ebb_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..07e414c0301d112b93677b81cdf5fbf36569f3a7
--- /dev/null
+++ b/blog_data/images/blog_581c59c84ebb_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:21458574d4745358aeff1951bb5f2a18c123e8a807d2bbe82e4cbaf7fef57509
+size 95121
diff --git a/blog_data/images/blog_581c59c84ebb_3.jpg b/blog_data/images/blog_581c59c84ebb_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2d74b3dd3da6c6925ca8db9f0c05256d684aecf6
--- /dev/null
+++ b/blog_data/images/blog_581c59c84ebb_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:31605c9d917c22820514af24cdd0060365f2c7dc406bfe3b1ee9807a19a47d17
+size 80577
diff --git a/blog_data/images/blog_581c59c84ebb_4.bin b/blog_data/images/blog_581c59c84ebb_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_581c59c84ebb_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_581c59c84ebb_5.bin b/blog_data/images/blog_581c59c84ebb_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_581c59c84ebb_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_59788d6128c7_0.jpg b/blog_data/images/blog_59788d6128c7_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1c3b708252138568bc58c9ecbeea6cc3127ce11b
--- /dev/null
+++ b/blog_data/images/blog_59788d6128c7_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:982a79827a0076c4174d10f333ab99f46384ef81b8ef7cbe893e101619010bec
+size 47831
diff --git a/blog_data/images/blog_59788d6128c7_1.jpg b/blog_data/images/blog_59788d6128c7_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..34b619e8822556967bf2bdd4c20246217102257d
--- /dev/null
+++ b/blog_data/images/blog_59788d6128c7_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fe342552aac8105776eac51ab4a26c8a7d71a505d2618557daa86f4105418b5e
+size 90484
diff --git a/blog_data/images/blog_59788d6128c7_2.jpg b/blog_data/images/blog_59788d6128c7_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7df3c4991bff75dedfd74bd2d659d6481342d5da
--- /dev/null
+++ b/blog_data/images/blog_59788d6128c7_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1d119a37b6e25f43963d87ce9e1042525929fb6dcd28c7f8ff12d43299607b28
+size 73429
diff --git a/blog_data/images/blog_59788d6128c7_3.jpg b/blog_data/images/blog_59788d6128c7_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6fcbdb4331c6938e991d3909548e9dc3086c40b2
--- /dev/null
+++ b/blog_data/images/blog_59788d6128c7_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d31530ed642e2999f7bfe622fd91b369b14beaa48b8606cfaa95fedf9e15d9f7
+size 124295
diff --git a/blog_data/images/blog_59788d6128c7_4.bin b/blog_data/images/blog_59788d6128c7_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_59788d6128c7_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_59788d6128c7_5.bin b/blog_data/images/blog_59788d6128c7_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_59788d6128c7_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_60eff701c749_0.bin b/blog_data/images/blog_60eff701c749_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..2dd16d53017a26aff7b85a3c5da86f1f35395f24
--- /dev/null
+++ b/blog_data/images/blog_60eff701c749_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eaea879df76e49c816b0298a63f4440b1cab6bf8f41e0dca3de06f874cd2aa31
+size 22126
diff --git a/blog_data/images/blog_60eff701c749_1.bin b/blog_data/images/blog_60eff701c749_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..e9c68c872db90156af8e431bc5d0205a6b24ec65
--- /dev/null
+++ b/blog_data/images/blog_60eff701c749_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5d5a0d67a664b08d77c63151b90fac9bd2daa86ce150208eec2e1fee52b29133
+size 48288
diff --git a/blog_data/images/blog_60eff701c749_2.bin b/blog_data/images/blog_60eff701c749_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..1a81ccaeb352794f2663cb9da947267114ee30e6
--- /dev/null
+++ b/blog_data/images/blog_60eff701c749_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b5e3517a8c99de81103f02f072f5a60a3e800ed0dfdba25e1e08eccb72121349
+size 89614
diff --git a/blog_data/images/blog_60eff701c749_3.bin b/blog_data/images/blog_60eff701c749_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..942a413b3468a0e6e17ac3819b87672db52b6d17
--- /dev/null
+++ b/blog_data/images/blog_60eff701c749_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2fac519c7275eae754f88748c76070dc438baf860d950eb63b4dbd89b9210128
+size 8132
diff --git a/blog_data/images/blog_60eff701c749_4.bin b/blog_data/images/blog_60eff701c749_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..615eed27843538e5f252ddf42a7569857d08699b
--- /dev/null
+++ b/blog_data/images/blog_60eff701c749_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:29de0f0ef62e4b2a1e55869e4d15833c933dd79598924916310bef52f86ee5d7
+size 39060
diff --git a/blog_data/images/blog_60eff701c749_5.bin b/blog_data/images/blog_60eff701c749_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..5d78be668f83ea58e775093f72997cc926986a76
--- /dev/null
+++ b/blog_data/images/blog_60eff701c749_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:05360fc663d764b042ca71372791d6646da45c4daafc955e82720dd531cf5974
+size 11222
diff --git a/blog_data/images/blog_64783fa2bccb_0.bin b/blog_data/images/blog_64783fa2bccb_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..c5518ec1f101edf0ccdd0a298bd96b82bfd1efd7
--- /dev/null
+++ b/blog_data/images/blog_64783fa2bccb_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:419aa3b4eab3e5590761785cc99ed1623e6d02e3577edf30d9b5a2ecc6229afb
+size 42426
diff --git a/blog_data/images/blog_64783fa2bccb_1.bin b/blog_data/images/blog_64783fa2bccb_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4d61b9456ea509f86104517ff1d6a76b50e54163
--- /dev/null
+++ b/blog_data/images/blog_64783fa2bccb_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8476609cb555399c1626898e4ec219cee54ae89d65bafb8300d66b5258d4f7d2
+size 69230
diff --git a/blog_data/images/blog_64783fa2bccb_2.bin b/blog_data/images/blog_64783fa2bccb_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..bd29f1c2261d8b93b5a61127637389c7a0579882
--- /dev/null
+++ b/blog_data/images/blog_64783fa2bccb_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b918008739d66a69f2fd685c62ae9f825d528fff60d1582f35a1098d7935275b
+size 85284
diff --git a/blog_data/images/blog_66aca278d799_0.bin b/blog_data/images/blog_66aca278d799_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..67bcdd9e1d4c6c7a71d644a0fa78a5cb6826776b
--- /dev/null
+++ b/blog_data/images/blog_66aca278d799_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:391bfaf476547ee321b4cb1f14aa78e202802524d721b4114e7301a72339ced3
+size 45834
diff --git a/blog_data/images/blog_66aca278d799_1.bin b/blog_data/images/blog_66aca278d799_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..585582bdc3f1ca5f689bf858c1d6d1e0b355cba6
--- /dev/null
+++ b/blog_data/images/blog_66aca278d799_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:99a8f4e2a0f56c738f8c22d620a248d5612528f0c43bb812dd5cb94a9109afbe
+size 13166
diff --git a/blog_data/images/blog_6d550f856eff_0.jpg b/blog_data/images/blog_6d550f856eff_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5ebf5f7aac30c31ccf65c503049752759ecd8372
--- /dev/null
+++ b/blog_data/images/blog_6d550f856eff_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:076630ed2890f8bdb75dd05c1023e49e09cb733ecff5aa1a871716b3bc0abaeb
+size 91569
diff --git a/blog_data/images/blog_6d550f856eff_1.jpg b/blog_data/images/blog_6d550f856eff_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..982149eaf87f5df94346955e4c45446d7e8ca2cf
--- /dev/null
+++ b/blog_data/images/blog_6d550f856eff_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:be99f4fc8b4a40a48c6e1acaaf973065520140cf568e8a1dc9791df71bae26f2
+size 84984
diff --git a/blog_data/images/blog_6d550f856eff_2.jpg b/blog_data/images/blog_6d550f856eff_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5989ef27395aea209912c1ce582f6c58f2a0a199
--- /dev/null
+++ b/blog_data/images/blog_6d550f856eff_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ac5d3b92a7b744bc5b77e80822a18d440cd271e03bfbb140a119f22e33d5d84
+size 113103
diff --git a/blog_data/images/blog_6d550f856eff_3.jpg b/blog_data/images/blog_6d550f856eff_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d8fc5af258593150d4bf8460612ce46f1b9140c1
--- /dev/null
+++ b/blog_data/images/blog_6d550f856eff_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a237e77a9405c58515737af5335eb25aa7d00343b5dd7c1c50af639ee8f1b851
+size 174304
diff --git a/blog_data/images/blog_6d550f856eff_4.jpg b/blog_data/images/blog_6d550f856eff_4.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a45ed8d605264edbfcc5be6f26dcc4161dcb0f49
--- /dev/null
+++ b/blog_data/images/blog_6d550f856eff_4.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2436f018842fd7fe8a6aa20b3a3d70dc9ed5db4847f33c812f3b425a373decd3
+size 93184
diff --git a/blog_data/images/blog_6d550f856eff_5.bin b/blog_data/images/blog_6d550f856eff_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_6d550f856eff_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_6d550f856eff_6.bin b/blog_data/images/blog_6d550f856eff_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_6d550f856eff_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_6ecc81dfd176_0.bin b/blog_data/images/blog_6ecc81dfd176_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..ed8ebe4080434bdd3a446540ea41897d00892e83
--- /dev/null
+++ b/blog_data/images/blog_6ecc81dfd176_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:96d48cc063e250fc11705fec82802d73c6f31c76521d593740287324827dc203
+size 39390
diff --git a/blog_data/images/blog_6ecc81dfd176_1.bin b/blog_data/images/blog_6ecc81dfd176_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4287884f82e9fb5e711b4045dc13d065b36a93d6
--- /dev/null
+++ b/blog_data/images/blog_6ecc81dfd176_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e79e05a2aff77c215dca8646c7e1c47a225e068f9ae42238fad5fc765c2b2a3f
+size 69508
diff --git a/blog_data/images/blog_6ecc81dfd176_2.bin b/blog_data/images/blog_6ecc81dfd176_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..f84d9706635644e2a2fea6c2aa449741b9995ad8
--- /dev/null
+++ b/blog_data/images/blog_6ecc81dfd176_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:93e12a2af8268b35eb0e776dae7bbded87fe2ea1708ddaaef58b62e3ff00e6b7
+size 18440
diff --git a/blog_data/images/blog_6ecc81dfd176_3.bin b/blog_data/images/blog_6ecc81dfd176_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..7d00f7b66147807d4020c84008c7999c665d4e30
--- /dev/null
+++ b/blog_data/images/blog_6ecc81dfd176_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:43fb6bbca1956ef7baf7c349ea7d02440398ee1fbb5718f6299e94b00ad54bb4
+size 23100
diff --git a/blog_data/images/blog_73f0ec430ce9_0.bin b/blog_data/images/blog_73f0ec430ce9_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..430273861a4eca8ac9b6411cbe846ea96e1a0421
--- /dev/null
+++ b/blog_data/images/blog_73f0ec430ce9_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d41c2e60b8963ab86a57b51465f72725382a3a891e6850b7e72b76108e8f3581
+size 89692
diff --git a/blog_data/images/blog_73f0ec430ce9_1.bin b/blog_data/images/blog_73f0ec430ce9_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..399d83738dafa3392525c1a8e7ea4f08e5671955
--- /dev/null
+++ b/blog_data/images/blog_73f0ec430ce9_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3954f5aceb76fcbe2f7eea6397b11cf7c93d620a7ed130f84856ab9624051147
+size 16652
diff --git a/blog_data/images/blog_73f0ec430ce9_2.bin b/blog_data/images/blog_73f0ec430ce9_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..6563d3d3113e7c5add0b019b7cae644711c9679b
--- /dev/null
+++ b/blog_data/images/blog_73f0ec430ce9_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:39282571e56337b53eef8a2010686872ea7cb5e6e8a12ef8e577c7e3b2abb76d
+size 94428
diff --git a/blog_data/images/blog_75a0f8f743ee_0.bin b/blog_data/images/blog_75a0f8f743ee_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..83c9b0aae0f89ed0f521571c914d9ba65a5507a5
--- /dev/null
+++ b/blog_data/images/blog_75a0f8f743ee_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1d0117c71cfddf44a2cfe18832109992c0623f6067827e4191c68151a45aba20
+size 45874
diff --git a/blog_data/images/blog_75a0f8f743ee_1.bin b/blog_data/images/blog_75a0f8f743ee_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..61a478b4434df970d98020008829a2bb575e037a
--- /dev/null
+++ b/blog_data/images/blog_75a0f8f743ee_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dd6948cef67e755dd743320b3cc3b83eaef60cddbb99716e4b4a516706da5ee3
+size 14836
diff --git a/blog_data/images/blog_75a0f8f743ee_2.bin b/blog_data/images/blog_75a0f8f743ee_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..305433d64f94eb106212d87a58a3c1b5da8d7fa9
--- /dev/null
+++ b/blog_data/images/blog_75a0f8f743ee_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:14aeabfd466db17970a1b45793d58ed318e8cf4573451fb9a56b84f61e0facca
+size 22356
diff --git a/blog_data/images/blog_75a0f8f743ee_3.bin b/blog_data/images/blog_75a0f8f743ee_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..49a8df39e4873ddebf97ba526b935977fd5e39ee
--- /dev/null
+++ b/blog_data/images/blog_75a0f8f743ee_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:be1d4d8f3a9f869cddcd658f49fbd01b44be35bd25df8d1a9d504abab84d2ecb
+size 101910
diff --git a/blog_data/images/blog_75a0f8f743ee_4.bin b/blog_data/images/blog_75a0f8f743ee_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..d0f9f222c0624fe60f9a4f00e5c8b8ff31d4b6a6
--- /dev/null
+++ b/blog_data/images/blog_75a0f8f743ee_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:52dff853c4a870aa58fc58cf6ef7c9fad52cac3b92e7cec74b7530320c5fed5a
+size 67066
diff --git a/blog_data/images/blog_767ba539d2f1_0.jpg b/blog_data/images/blog_767ba539d2f1_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..54dfb0a34b5cfd8551d479e5fcfc8e756b58cf44
--- /dev/null
+++ b/blog_data/images/blog_767ba539d2f1_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eff9e896c6d88088d70d9fe65c983780f6c59dfe120a32cc079d09c99c34a106
+size 43533
diff --git a/blog_data/images/blog_767ba539d2f1_1.bin b/blog_data/images/blog_767ba539d2f1_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..9d86d417410b841a6fe195eda0aa8833832146eb
--- /dev/null
+++ b/blog_data/images/blog_767ba539d2f1_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4809c111c561291470f94a3d0856512eff6a69ec9149182cbcb23c8cdcf075a5
+size 1464370
diff --git a/blog_data/images/blog_767ba539d2f1_2.jpg b/blog_data/images/blog_767ba539d2f1_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e9b67f5cfbea0753bb14dfef9ef231bed5c059a6
--- /dev/null
+++ b/blog_data/images/blog_767ba539d2f1_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7656d6ef34e81eca2ad34fd4d88e7bfb15003021674be7350d681d90e4533899
+size 157951
diff --git a/blog_data/images/blog_767ba539d2f1_3.jpg b/blog_data/images/blog_767ba539d2f1_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ef3e71ebede4ab54a361ee3f28fdc4d0355c6375
--- /dev/null
+++ b/blog_data/images/blog_767ba539d2f1_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7631041f245793b20f2d698b886357ca1d9326f57f69953df7cf4a377e4d2a39
+size 46613
diff --git a/blog_data/images/blog_767ba539d2f1_4.bin b/blog_data/images/blog_767ba539d2f1_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_767ba539d2f1_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_767ba539d2f1_5.bin b/blog_data/images/blog_767ba539d2f1_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_767ba539d2f1_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_7828d506708f_0.bin b/blog_data/images/blog_7828d506708f_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..0a331604210438bc8124d13a67523761896b8b40
--- /dev/null
+++ b/blog_data/images/blog_7828d506708f_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a23e084be237857985e40927320c59cbc632b15ae8763cf6372c805069959012
+size 3253497
diff --git a/blog_data/images/blog_7828d506708f_1.bin b/blog_data/images/blog_7828d506708f_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..c0fc45a77142372acbcd45f96a9c5bb508da92cd
--- /dev/null
+++ b/blog_data/images/blog_7828d506708f_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f8a0e86cd4cee95e9b0795a8ef4f31b06522fd029616507d80d385725d647778
+size 2025613
diff --git a/blog_data/images/blog_7828d506708f_10.bin b/blog_data/images/blog_7828d506708f_10.bin
new file mode 100644
index 0000000000000000000000000000000000000000..8e050a6e3d90f104bf0ce150093087424867a3c5
--- /dev/null
+++ b/blog_data/images/blog_7828d506708f_10.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f8658e50312be2591d0cbb26069ca93746d54285d5984dc1d80f15965fc657dc
+size 110603
diff --git a/blog_data/images/blog_7828d506708f_2.bin b/blog_data/images/blog_7828d506708f_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..5f6412bc5744da476790bbbeb83627c6df2c8716
--- /dev/null
+++ b/blog_data/images/blog_7828d506708f_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2ab44a7ff6a8735f6057f3b9478a65f241f2c9a981c454d66e8103eb4894f751
+size 7566
diff --git a/blog_data/images/blog_7828d506708f_3.bin b/blog_data/images/blog_7828d506708f_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..b0fe3f9a93f80e7240154e7acc1b8f893e516d85
--- /dev/null
+++ b/blog_data/images/blog_7828d506708f_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9eb81ec7fb967a2df649ef4fe148f73987fbe297711afa594b7ce818a178937b
+size 12778
diff --git a/blog_data/images/blog_7828d506708f_4.bin b/blog_data/images/blog_7828d506708f_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..20e865f7684583bac5039eec0d665c328b51639b
--- /dev/null
+++ b/blog_data/images/blog_7828d506708f_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ff70e9054684fb98954fed6215659c9dc838c981200f470757ecfec515f00f51
+size 202530
diff --git a/blog_data/images/blog_7828d506708f_5.bin b/blog_data/images/blog_7828d506708f_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..8bd7b2d5ac975db75b35c53f693191a7b2e1dfbf
--- /dev/null
+++ b/blog_data/images/blog_7828d506708f_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:61194648ef82a23560abf2016464e56b1788dadc3cd4bd025c0a13797be0f189
+size 91761
diff --git a/blog_data/images/blog_7828d506708f_6.bin b/blog_data/images/blog_7828d506708f_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..90764ae094a7a1231d8cccbf9586cc12a6b1de0e
--- /dev/null
+++ b/blog_data/images/blog_7828d506708f_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:10b10d12dae14db7087741b9892ca4c6501b3885148cdce55774195b76cef70f
+size 69962
diff --git a/blog_data/images/blog_7828d506708f_7.bin b/blog_data/images/blog_7828d506708f_7.bin
new file mode 100644
index 0000000000000000000000000000000000000000..b5b997e329a48542b27e99e6dd9a54bfc5b9e351
--- /dev/null
+++ b/blog_data/images/blog_7828d506708f_7.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4468b0e3fbfffbb0e3285cd17ebbacf7437776e5398caf72d75f742e2610525c
+size 80980
diff --git a/blog_data/images/blog_7828d506708f_8.bin b/blog_data/images/blog_7828d506708f_8.bin
new file mode 100644
index 0000000000000000000000000000000000000000..88e879d9d4033922f71618be5162d72f2e2fe3b2
--- /dev/null
+++ b/blog_data/images/blog_7828d506708f_8.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:de87c01af42b6b17612c100730709915c91cd87f2ba53e1f852fd12afd308d15
+size 156127
diff --git a/blog_data/images/blog_7828d506708f_9.bin b/blog_data/images/blog_7828d506708f_9.bin
new file mode 100644
index 0000000000000000000000000000000000000000..338df3c7202b7d21640868016f8d5b47bce6f50b
--- /dev/null
+++ b/blog_data/images/blog_7828d506708f_9.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1b62c9b045bddaeb0704598658611457c75ae0581635eb6370e875e480a0c420
+size 50862
diff --git a/blog_data/images/blog_7b882fcc2ee7_0.bin b/blog_data/images/blog_7b882fcc2ee7_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..952c963183781f1dede1752c3f4f2c02f962dae4
--- /dev/null
+++ b/blog_data/images/blog_7b882fcc2ee7_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9775405189f069454f66f9d30560617ec53feff2145b39f6d439e026c057f573
+size 46683
diff --git a/blog_data/images/blog_7b882fcc2ee7_1.bin b/blog_data/images/blog_7b882fcc2ee7_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..c2d25f52214ab17b152939a06e3013b34c9a603a
--- /dev/null
+++ b/blog_data/images/blog_7b882fcc2ee7_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3688d53c90b1a25f0a7961e3bcbfc2c4a3ecbad20af7c2602d6af4de5840b229
+size 18917
diff --git a/blog_data/images/blog_7b882fcc2ee7_2.bin b/blog_data/images/blog_7b882fcc2ee7_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4380121051cd62e0c141b0235502e1c87ba5738a
--- /dev/null
+++ b/blog_data/images/blog_7b882fcc2ee7_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6b8aec591ff5a2fb593b2c2e2cd2a15e80cabc43b87831aa77708c365b65b892
+size 54500
diff --git a/blog_data/images/blog_7b882fcc2ee7_3.bin b/blog_data/images/blog_7b882fcc2ee7_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..f8ae9b1d9d3cfe9e3843fa58dcafa5bc48868b2f
--- /dev/null
+++ b/blog_data/images/blog_7b882fcc2ee7_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:90f4555b3040eb687a43eeb8a8f69115ed10bbf72573850b506e60069e0a1c2d
+size 68385
diff --git a/blog_data/images/blog_7b882fcc2ee7_4.bin b/blog_data/images/blog_7b882fcc2ee7_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..8445cee4bad09f04036bcdb1be297faa41bf0574
--- /dev/null
+++ b/blog_data/images/blog_7b882fcc2ee7_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9981e8f34c783e2287b04f45b4fe3802f3a94596a9f67b487368d148483dd224
+size 36551
diff --git a/blog_data/images/blog_7b882fcc2ee7_5.bin b/blog_data/images/blog_7b882fcc2ee7_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..1285de390635b02004e1ebc9ed08102bc89673ee
--- /dev/null
+++ b/blog_data/images/blog_7b882fcc2ee7_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:85eb1720af6bca5945a80314d7d16dfb3fa974d9e6faee8a8fa0eb1dcedc508f
+size 174858
diff --git a/blog_data/images/blog_7b882fcc2ee7_6.bin b/blog_data/images/blog_7b882fcc2ee7_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..1671c85739d1ed540371b6465139a9745119dd45
--- /dev/null
+++ b/blog_data/images/blog_7b882fcc2ee7_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d0cdc4b0d8aa062e06106a8420334ad3290c03d22e9d0f1a747bb98ddf616e5f
+size 53006
diff --git a/blog_data/images/blog_7cf32d7305ba_0.bin b/blog_data/images/blog_7cf32d7305ba_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..072d61075dc4eee049051622674ebf985dcc7055
--- /dev/null
+++ b/blog_data/images/blog_7cf32d7305ba_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d06d137cca9a2d4cf721fda416d2ac85320ebd67ee3cfa71efe18c9a4df7434
+size 15718
diff --git a/blog_data/images/blog_7cf32d7305ba_1.bin b/blog_data/images/blog_7cf32d7305ba_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..44cf463df4f508920c292c09a77085cd92ca0fdf
--- /dev/null
+++ b/blog_data/images/blog_7cf32d7305ba_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5cbd6a895b6b590cf1777e80757b6e330833a0ab3ca413ad7d700a9aeef94d5e
+size 14120
diff --git a/blog_data/images/blog_7cf32d7305ba_2.bin b/blog_data/images/blog_7cf32d7305ba_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..704ccf63daff66ae99e2216a825c17357b7d198e
--- /dev/null
+++ b/blog_data/images/blog_7cf32d7305ba_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88340b81b3bac14674853a6fa9e1f020161dd0ab4c1a84ff6345eede24f30881
+size 27224
diff --git a/blog_data/images/blog_7cf32d7305ba_3.bin b/blog_data/images/blog_7cf32d7305ba_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..3ea09eaee447db7803a670960cea5b627e41bcfb
--- /dev/null
+++ b/blog_data/images/blog_7cf32d7305ba_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d67d5028b84154c83578204068fb9ab2cb9e0d58a638b3a0c5269bce88599b17
+size 52808
diff --git a/blog_data/images/blog_7d949ff5d26d_0.jpg b/blog_data/images/blog_7d949ff5d26d_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5643ca315f2264b803ae6dc69036d7eb6bc75bc5
--- /dev/null
+++ b/blog_data/images/blog_7d949ff5d26d_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d5ec28440c74133747796692fe7f6f867d49768eea45e7fe98312fd3c94b5edf
+size 52197
diff --git a/blog_data/images/blog_7d949ff5d26d_1.jpg b/blog_data/images/blog_7d949ff5d26d_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64cc4ffbc079024dc2383a188c76b3922a48dfcd
--- /dev/null
+++ b/blog_data/images/blog_7d949ff5d26d_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0eb450c70a0fee81fa7a58a982d4555bcef797a65ea4db069d5a2f1e003cdfd1
+size 37658
diff --git a/blog_data/images/blog_7d949ff5d26d_2.jpg b/blog_data/images/blog_7d949ff5d26d_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0cdfc2e63bf9909b51841051d3455311c4c6161c
--- /dev/null
+++ b/blog_data/images/blog_7d949ff5d26d_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:246705cbd86a067da02db2e8256c400d853386121ea656a5ddd3bd051b04006d
+size 49633
diff --git a/blog_data/images/blog_7d949ff5d26d_3.jpg b/blog_data/images/blog_7d949ff5d26d_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bf8d2ccda5b99ad5dbff7e6099f7ac7216bac077
--- /dev/null
+++ b/blog_data/images/blog_7d949ff5d26d_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:728f259fc5e0c091b36bd9d561ff69541d09632af8d0c3d48fa3b8a96388cca5
+size 118326
diff --git a/blog_data/images/blog_7d949ff5d26d_4.jpg b/blog_data/images/blog_7d949ff5d26d_4.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..176f3738e91ae31f67c96f868f578b8cdd1bcee2
--- /dev/null
+++ b/blog_data/images/blog_7d949ff5d26d_4.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:79ee3a87002d2427d2b01c4357ba1dea603e772e295e9cac7a0718f4d748d2bc
+size 28261
diff --git a/blog_data/images/blog_7d949ff5d26d_5.jpg b/blog_data/images/blog_7d949ff5d26d_5.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f1edfca85d7eef04db2d1cfe4a4fc213156744e7
--- /dev/null
+++ b/blog_data/images/blog_7d949ff5d26d_5.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:44e14527c8a2a00a9e70e82f66f13b3234a5cc5c6e221177df69f928642fffdb
+size 65370
diff --git a/blog_data/images/blog_7d949ff5d26d_6.jpg b/blog_data/images/blog_7d949ff5d26d_6.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b81664df287673cb26ad7f9720d07cfd70aecbe8
--- /dev/null
+++ b/blog_data/images/blog_7d949ff5d26d_6.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fcfc343bd2dacd746d012083adba5cd0a39c900e880d5495ba5a3b6272b725ff
+size 23069
diff --git a/blog_data/images/blog_7d949ff5d26d_7.bin b/blog_data/images/blog_7d949ff5d26d_7.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_7d949ff5d26d_7.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_7d949ff5d26d_8.bin b/blog_data/images/blog_7d949ff5d26d_8.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_7d949ff5d26d_8.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_854680472d0b_0.bin b/blog_data/images/blog_854680472d0b_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..2c0942dd5efad9186772092d56ff16fab5a3aca4
--- /dev/null
+++ b/blog_data/images/blog_854680472d0b_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:669ec9f4f4aecf4acba9d2e5a30ffe50d8db0292b0fe7e692572c7109ea75cb5
+size 48922
diff --git a/blog_data/images/blog_8751fb5a6290_0.bin b/blog_data/images/blog_8751fb5a6290_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..def7d293a209e5a3c8cdbd820f572cae62662fd5
--- /dev/null
+++ b/blog_data/images/blog_8751fb5a6290_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:156b0faa0c1e7b644431a8a6fffbba46d5d27705ffcaefcb6c56c1141372c8da
+size 16484
diff --git a/blog_data/images/blog_8751fb5a6290_1.bin b/blog_data/images/blog_8751fb5a6290_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..dd791013e26a552b7a4932ca6e79b8caf713c5f6
--- /dev/null
+++ b/blog_data/images/blog_8751fb5a6290_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:df8127cd6a98cb696e5e0a040bfb7f49818edc719c2b736397b016579a2b52ee
+size 25114
diff --git a/blog_data/images/blog_8751fb5a6290_2.bin b/blog_data/images/blog_8751fb5a6290_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..96f9ebd2f23d82bb3224103cd6f2fef99340c8a6
--- /dev/null
+++ b/blog_data/images/blog_8751fb5a6290_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e8c142c2dfbe25147dbbb60f4af0a00a086656869d7100c326ffc0f11eef9287
+size 59292
diff --git a/blog_data/images/blog_89c2d63d87c4_0.bin b/blog_data/images/blog_89c2d63d87c4_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..37a02d723d60622661e9512a8f00ff1dde3b7d9a
--- /dev/null
+++ b/blog_data/images/blog_89c2d63d87c4_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:04f23064f6f8aebabe9a1c289afdaa88daefad11d400e06c1072c6c15ea46f4f
+size 237665
diff --git a/blog_data/images/blog_89c2d63d87c4_1.jpg b/blog_data/images/blog_89c2d63d87c4_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..09e349c22ddee9cb20820d4ba983dc9c95adcc73
--- /dev/null
+++ b/blog_data/images/blog_89c2d63d87c4_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4f949a87ce84cc62310e59d293471a743c6ea4d36135e4547eee70c271dd06fb
+size 122151
diff --git a/blog_data/images/blog_89c2d63d87c4_10.bin b/blog_data/images/blog_89c2d63d87c4_10.bin
new file mode 100644
index 0000000000000000000000000000000000000000..2d912cc9f6f92756811dd3221289d3d121cd7664
--- /dev/null
+++ b/blog_data/images/blog_89c2d63d87c4_10.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8e00f16d905130bcf65b9cac25ca5b1b2aa32ecc33f87b936c3620b921388573
+size 87454
diff --git a/blog_data/images/blog_89c2d63d87c4_2.bin b/blog_data/images/blog_89c2d63d87c4_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..f9066100908b9088bfdaacf7889098fbae34205a
--- /dev/null
+++ b/blog_data/images/blog_89c2d63d87c4_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0ce7ecfff7640787f2bcd3c15b37f76e2ad7be7c097ac01ff065acf0c4183f92
+size 201399
diff --git a/blog_data/images/blog_89c2d63d87c4_3.bin b/blog_data/images/blog_89c2d63d87c4_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..f9066100908b9088bfdaacf7889098fbae34205a
--- /dev/null
+++ b/blog_data/images/blog_89c2d63d87c4_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0ce7ecfff7640787f2bcd3c15b37f76e2ad7be7c097ac01ff065acf0c4183f92
+size 201399
diff --git a/blog_data/images/blog_89c2d63d87c4_4.jpg b/blog_data/images/blog_89c2d63d87c4_4.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..28d7fba09e28ec01ff07bed0f066e5725d563747
--- /dev/null
+++ b/blog_data/images/blog_89c2d63d87c4_4.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b8c195cf48208d81ce4308f3334ef913b1b4067fa95fc973329d167cf73887f7
+size 129969
diff --git a/blog_data/images/blog_89c2d63d87c4_5.bin b/blog_data/images/blog_89c2d63d87c4_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..90836990a1124b6e7ae5fea0f1412b58782d5637
--- /dev/null
+++ b/blog_data/images/blog_89c2d63d87c4_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:afb922fd9b972c3377eb7206cc162daa6c623df5b27d5d4bba05e0d155d86726
+size 510831
diff --git a/blog_data/images/blog_89c2d63d87c4_6.bin b/blog_data/images/blog_89c2d63d87c4_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..d2c4437071a764ab13b75cc4dd2ca45b47939788
--- /dev/null
+++ b/blog_data/images/blog_89c2d63d87c4_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b30ec22768dd64415ab898f9d740e19fc745e26889018b6fdc45a6091e587186
+size 261835
diff --git a/blog_data/images/blog_89c2d63d87c4_7.bin b/blog_data/images/blog_89c2d63d87c4_7.bin
new file mode 100644
index 0000000000000000000000000000000000000000..0a76577925c08ace255f62a63fb4b8a7bd8c7095
--- /dev/null
+++ b/blog_data/images/blog_89c2d63d87c4_7.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0ef462b7645f0ca2d1b6925ffd96e5fd5f4851afdcb5f80d67767bfbd12496d0
+size 272534
diff --git a/blog_data/images/blog_89c2d63d87c4_8.bin b/blog_data/images/blog_89c2d63d87c4_8.bin
new file mode 100644
index 0000000000000000000000000000000000000000..a4f6459b99e4c87a3f377efebde64f5758aa3b07
--- /dev/null
+++ b/blog_data/images/blog_89c2d63d87c4_8.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7349824bcfa73a29436196d7f3c09097987509a1b2e2f3fc1c71341fd3e76205
+size 127061
diff --git a/blog_data/images/blog_89c2d63d87c4_9.bin b/blog_data/images/blog_89c2d63d87c4_9.bin
new file mode 100644
index 0000000000000000000000000000000000000000..0b811a378f67950e2b91b9c326079dc444abf308
--- /dev/null
+++ b/blog_data/images/blog_89c2d63d87c4_9.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:746123c073601024651fbc62f44f621511adb47f093a30ddad3101ec8c3434a6
+size 191355
diff --git a/blog_data/images/blog_8bf494ab83aa_0.bin b/blog_data/images/blog_8bf494ab83aa_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..1646a61dbcdbd4fd58e6faf1eb957259d3757c28
--- /dev/null
+++ b/blog_data/images/blog_8bf494ab83aa_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4df5ef31d2df4773c5950255a5dc677f628c6a2b88a4fbad94dc87cf1e24fdf2
+size 35458
diff --git a/blog_data/images/blog_8db87c26f875_0.bin b/blog_data/images/blog_8db87c26f875_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..06a567b457325825aa726e64794d6d3d98e575f4
--- /dev/null
+++ b/blog_data/images/blog_8db87c26f875_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:944131f00da7573d742b9019a3f94789f51a1482beef41c5e1a6e34486bf219d
+size 70712
diff --git a/blog_data/images/blog_8db87c26f875_1.bin b/blog_data/images/blog_8db87c26f875_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..70e671ae0f29f2d3869e5d1805ffa057ba8134e3
--- /dev/null
+++ b/blog_data/images/blog_8db87c26f875_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2b0f16a5ef0394f06a30ef55ecdd8665cbea81395a5f4101bb0c74bcfae5ffc5
+size 13928
diff --git a/blog_data/images/blog_8db87c26f875_2.bin b/blog_data/images/blog_8db87c26f875_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..b79fa1a13f0ff2142d0da5ee9886b66b19582570
--- /dev/null
+++ b/blog_data/images/blog_8db87c26f875_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f8b0e9c044b540b341e09753ec54a357ae15191c01551b8843634896fd7a7d92
+size 41554
diff --git a/blog_data/images/blog_8db87c26f875_3.bin b/blog_data/images/blog_8db87c26f875_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..3bcf62035d5519ae78fb2daf95e80d9d512daa27
--- /dev/null
+++ b/blog_data/images/blog_8db87c26f875_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9f5b35a1266110f8a41d241f8df727404cc4a6e553fd9396be3b994f3d316baf
+size 57452
diff --git a/blog_data/images/blog_908de5a2c0d0_0.bin b/blog_data/images/blog_908de5a2c0d0_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..05e83b9d1c6dc3058e82e090a4595fc799d8ee36
--- /dev/null
+++ b/blog_data/images/blog_908de5a2c0d0_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:176936406477a3b2c6464a602ffa6f42045c1db67030da3d7943fe5ae9d96f16
+size 63976
diff --git a/blog_data/images/blog_908de5a2c0d0_1.bin b/blog_data/images/blog_908de5a2c0d0_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..1970306bffded953689b8d0bb099c1bc5efa9a05
--- /dev/null
+++ b/blog_data/images/blog_908de5a2c0d0_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fffc78bce790491c73692d6a05ffdeb93d5c532897420102987ad3a631b5dc9d
+size 28214
diff --git a/blog_data/images/blog_908de5a2c0d0_2.bin b/blog_data/images/blog_908de5a2c0d0_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..e2e642f4e7d2c81047ecb0afa2bb2b3d96a33400
--- /dev/null
+++ b/blog_data/images/blog_908de5a2c0d0_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a1067bfe1588ebd93be9a94c91217fb7196e018ef563fa8bc4b3147fbaf15693
+size 32148
diff --git a/blog_data/images/blog_908de5a2c0d0_3.bin b/blog_data/images/blog_908de5a2c0d0_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..41ac8a957ca964384ad877a89a394aa6842cb3ad
--- /dev/null
+++ b/blog_data/images/blog_908de5a2c0d0_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:acbaa9109365e50d9a91cf58d3cea0e823903dca0577c54bfaab7faaea18b80c
+size 91758
diff --git a/blog_data/images/blog_908de5a2c0d0_4.bin b/blog_data/images/blog_908de5a2c0d0_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..116859707477de4a291f27039e8d3b0bbb2d9419
--- /dev/null
+++ b/blog_data/images/blog_908de5a2c0d0_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d8f89acd73c5a44b1ec0077177e8903618729a9d22de1abea5eb2bd59408ee1
+size 74588
diff --git a/blog_data/images/blog_908de5a2c0d0_5.bin b/blog_data/images/blog_908de5a2c0d0_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..06830cd0a65fdb8631d6ba99ca9e7506784b5acf
--- /dev/null
+++ b/blog_data/images/blog_908de5a2c0d0_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0a45214eb7f0e7204f0579aa35ffa3825decf22c4c755c023936c23181beea49
+size 67928
diff --git a/blog_data/images/blog_92e0fda8fc06_0.jpg b/blog_data/images/blog_92e0fda8fc06_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a0ad89149ce6109a8d76fd6239eee286a079aa61
--- /dev/null
+++ b/blog_data/images/blog_92e0fda8fc06_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:132569bac5b6126475f5e873edf7e3481ba6b2e70b1039044280abf3e7c09fba
+size 68893
diff --git a/blog_data/images/blog_92e0fda8fc06_1.jpg b/blog_data/images/blog_92e0fda8fc06_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36cf2910a39b7dc2228c1fc87c5b46f09ad0b97b
--- /dev/null
+++ b/blog_data/images/blog_92e0fda8fc06_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a55c7063b89b99312c7bdf41825994f0fc1fc1ed837393c2f16b6b1bc9882d1e
+size 73046
diff --git a/blog_data/images/blog_92e0fda8fc06_2.jpg b/blog_data/images/blog_92e0fda8fc06_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4415019f3ddba9764c6e9650e00d4d8958daa366
--- /dev/null
+++ b/blog_data/images/blog_92e0fda8fc06_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0f223f5bcfec6d177ebb0b2c3a4b833aef325cc5f5646dfcf45152b70d2976fb
+size 55530
diff --git a/blog_data/images/blog_92e0fda8fc06_3.jpg b/blog_data/images/blog_92e0fda8fc06_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e62daba4ea41c6eea63e5aaaabdaebb86a596f2f
--- /dev/null
+++ b/blog_data/images/blog_92e0fda8fc06_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:15ff97ba325e3480b4150b493e02e19b3c26c14a151206b586b59f2e77fc836c
+size 70708
diff --git a/blog_data/images/blog_92e0fda8fc06_4.jpg b/blog_data/images/blog_92e0fda8fc06_4.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2a77debe64eb7f792644676be2b4f0bb4f68461f
--- /dev/null
+++ b/blog_data/images/blog_92e0fda8fc06_4.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:22b0bf95d9cf689df1b344b85afdea044f19a74483c1af42688cd78d165d5315
+size 57500
diff --git a/blog_data/images/blog_92e0fda8fc06_5.jpg b/blog_data/images/blog_92e0fda8fc06_5.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7fd29ccdf15acd17f5ae0cd1eb0655601caa49c2
--- /dev/null
+++ b/blog_data/images/blog_92e0fda8fc06_5.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2e203671d6817752953a14c0de5344770437466976898469e72e53f9fe78dcc5
+size 75295
diff --git a/blog_data/images/blog_92e0fda8fc06_6.jpg b/blog_data/images/blog_92e0fda8fc06_6.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2a1296de3f597465336a8abcaec3cf806073c3e5
--- /dev/null
+++ b/blog_data/images/blog_92e0fda8fc06_6.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8078327799127a3bd11f89ef27d5d4eea49b1e5603fdcb09f7b67fc34b412057
+size 107386
diff --git a/blog_data/images/blog_92e0fda8fc06_7.bin b/blog_data/images/blog_92e0fda8fc06_7.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_92e0fda8fc06_7.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_92e0fda8fc06_8.bin b/blog_data/images/blog_92e0fda8fc06_8.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_92e0fda8fc06_8.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_946daf7cbbed_0.bin b/blog_data/images/blog_946daf7cbbed_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..3c5a976c03fbe4dbbd274d3ac7d635592b91bc91
--- /dev/null
+++ b/blog_data/images/blog_946daf7cbbed_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:327de571d1e5d7e71280f9fa5cce0bb4401f86a6e9d61c5ea5a332b0389a8aaa
+size 44282
diff --git a/blog_data/images/blog_946daf7cbbed_1.bin b/blog_data/images/blog_946daf7cbbed_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..73dd5b42a380b4e80c00022ee44985a71dce2b6a
--- /dev/null
+++ b/blog_data/images/blog_946daf7cbbed_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3a16142859426232486d6e347be5adf4a13d101f7d29ae94310fc2e3d1de0049
+size 79222
diff --git a/blog_data/images/blog_946daf7cbbed_2.bin b/blog_data/images/blog_946daf7cbbed_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..603a2edd302d1006b7ee75ebc5baa633c3e069c0
--- /dev/null
+++ b/blog_data/images/blog_946daf7cbbed_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:598617ab28ae75dba70ef9dac1f4049d7b818a192709b55a1d6be66a4feb2e93
+size 86706
diff --git a/blog_data/images/blog_946daf7cbbed_3.bin b/blog_data/images/blog_946daf7cbbed_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..50ace1ffa5d04f1614f4710cf59a1416bb32fefa
--- /dev/null
+++ b/blog_data/images/blog_946daf7cbbed_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7bcfa9634c6296d2f637430b4d3ff87275813a9b26f609d4a16f0cdb25f87047
+size 47182
diff --git a/blog_data/images/blog_96509521c651_0.bin b/blog_data/images/blog_96509521c651_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..e37c8d98ab8890864039b7b059ad78437963894e
--- /dev/null
+++ b/blog_data/images/blog_96509521c651_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:60d7433430aa9b8054cdae5bc89cce96e74ddb922f726ee9a258b6e7cd6d4f2a
+size 67651
diff --git a/blog_data/images/blog_96509521c651_1.bin b/blog_data/images/blog_96509521c651_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..0f4517d770e8a3762cd9ab08088f5a1570cd3b36
--- /dev/null
+++ b/blog_data/images/blog_96509521c651_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:39bd7a14062fab8cfb47a1b7d1ec4814a473e6d1c379bfc00f9076764a228a25
+size 644224
diff --git a/blog_data/images/blog_96509521c651_10.bin b/blog_data/images/blog_96509521c651_10.bin
new file mode 100644
index 0000000000000000000000000000000000000000..0a325adae1ea874123d30744676e5d43dd07bd5c
--- /dev/null
+++ b/blog_data/images/blog_96509521c651_10.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:28091ae6f97879b216f1408e373ebcaed14182f693183ae3160172e62b1d11d6
+size 94375
diff --git a/blog_data/images/blog_96509521c651_11.bin b/blog_data/images/blog_96509521c651_11.bin
new file mode 100644
index 0000000000000000000000000000000000000000..6a9386564675540b61121d2f2009d2c06463add3
--- /dev/null
+++ b/blog_data/images/blog_96509521c651_11.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:165665a005571d05421c15ee21758e085b0de52a4de0e108f72d069776f2a54a
+size 412047
diff --git a/blog_data/images/blog_96509521c651_12.bin b/blog_data/images/blog_96509521c651_12.bin
new file mode 100644
index 0000000000000000000000000000000000000000..de3f21defc508afbd22d3c027fb322605a6b4439
--- /dev/null
+++ b/blog_data/images/blog_96509521c651_12.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ce7a72cc692e984a9c29c16d1bbfba9992cb2585c8b1b1579a0ed16362e86a5b
+size 123371
diff --git a/blog_data/images/blog_96509521c651_13.bin b/blog_data/images/blog_96509521c651_13.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4f39bf4f505c6e65aa4666d02b5a0ff9f3c4c515
--- /dev/null
+++ b/blog_data/images/blog_96509521c651_13.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:32c996b1ca3acec1c0f30ac7384775066cda6361b77895194bbea88325049bac
+size 91096
diff --git a/blog_data/images/blog_96509521c651_14.bin b/blog_data/images/blog_96509521c651_14.bin
new file mode 100644
index 0000000000000000000000000000000000000000..8a44eecf1a1fcd42e8e9de8b224f93dade735e48
--- /dev/null
+++ b/blog_data/images/blog_96509521c651_14.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d3c75ff617095665f0d82b0e3e53f93ecf7571ff380afab0a4396bc244bbbf80
+size 1189715
diff --git a/blog_data/images/blog_96509521c651_2.bin b/blog_data/images/blog_96509521c651_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..7b099e23dfb951423c97be0385123fd928c4248c
--- /dev/null
+++ b/blog_data/images/blog_96509521c651_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e6648455a78d1e8d5d4dd922197f27af906f9ab664d624b3f649d2b07fe01d25
+size 1195180
diff --git a/blog_data/images/blog_96509521c651_3.bin b/blog_data/images/blog_96509521c651_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..3c32bf3b5ae51d4b1f31b8381acc5c162822a270
--- /dev/null
+++ b/blog_data/images/blog_96509521c651_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:78e86b616b531033846eb0fac24615c04dd2a757a3539ed6f2d79a4a959292de
+size 263778
diff --git a/blog_data/images/blog_96509521c651_4.bin b/blog_data/images/blog_96509521c651_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..9c9eb600f5d8ab629549085c06cef6386f6fa631
--- /dev/null
+++ b/blog_data/images/blog_96509521c651_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ba3f57f370a2c6591f3ecc8773d96e45a8baf95ff34229d611f8768b2eced745
+size 250838
diff --git a/blog_data/images/blog_96509521c651_5.bin b/blog_data/images/blog_96509521c651_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..133fa1c0492a4e5a41b6221997808e0cd9dcfc5a
--- /dev/null
+++ b/blog_data/images/blog_96509521c651_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:425bf134d7ec533c062c52db7a8692ed86a053e425112062de964b8ede46cd56
+size 519628
diff --git a/blog_data/images/blog_96509521c651_6.bin b/blog_data/images/blog_96509521c651_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..c12c803683fdc6dbd0ad1bfed4208c6e245fb594
--- /dev/null
+++ b/blog_data/images/blog_96509521c651_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dc8268399acd5f3f594fc273fa6d6a755b78b6d51a0434772e78f82e09c4e1d1
+size 64144
diff --git a/blog_data/images/blog_96509521c651_7.bin b/blog_data/images/blog_96509521c651_7.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4e92557308bed234eabf747b41500df695caef5a
--- /dev/null
+++ b/blog_data/images/blog_96509521c651_7.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9b49878cc8dc7cdfc3afcfdf8a6329cdc3e329acf4242753dff88c6ef838932b
+size 134412
diff --git a/blog_data/images/blog_96509521c651_8.bin b/blog_data/images/blog_96509521c651_8.bin
new file mode 100644
index 0000000000000000000000000000000000000000..6527b80b87a308394a018a1f99922eef4a330665
--- /dev/null
+++ b/blog_data/images/blog_96509521c651_8.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7488f61163d5ebe8c698b7438c8d52ee1dbc513007472e43dd32c78303ebb770
+size 511998
diff --git a/blog_data/images/blog_96509521c651_9.bin b/blog_data/images/blog_96509521c651_9.bin
new file mode 100644
index 0000000000000000000000000000000000000000..3f6a02693551388e29531a87649c97bf291f2019
--- /dev/null
+++ b/blog_data/images/blog_96509521c651_9.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1adf178eb7469cce7d9f5b860cc7053ba7f5ae4e0bc4a83a3118c42c774d32f2
+size 813811
diff --git a/blog_data/images/blog_9af62f7b4383_0.bin b/blog_data/images/blog_9af62f7b4383_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..85c865643eced34fe09ab2011e7a794875890ec4
--- /dev/null
+++ b/blog_data/images/blog_9af62f7b4383_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:08c8d651e0f0e3ca86bf3e92a951210b5193b141c5fe07175863490c7a6ec171
+size 11870
diff --git a/blog_data/images/blog_9af62f7b4383_1.bin b/blog_data/images/blog_9af62f7b4383_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..35153abdc38d2601d4b1b5b5a035c35cac5ae04f
--- /dev/null
+++ b/blog_data/images/blog_9af62f7b4383_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c38c9708b760e83389d2854bc0c7ba898f7907f67fc30185cddcf5383ccc58c9
+size 68410
diff --git a/blog_data/images/blog_9af62f7b4383_2.bin b/blog_data/images/blog_9af62f7b4383_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..f4d26ac6928188854f3ec51e1844dbf7e15e2aad
--- /dev/null
+++ b/blog_data/images/blog_9af62f7b4383_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9b1feba37a88fd88d5a25c2655ef4ef5c621dde6db8f7c241fa9bf8bd4174478
+size 39920
diff --git a/blog_data/images/blog_a0c578ced20d_0.bin b/blog_data/images/blog_a0c578ced20d_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..b50b6656f9131d4b46da3ba33ae67f554f3d187e
--- /dev/null
+++ b/blog_data/images/blog_a0c578ced20d_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:db13e4c8238cdb24cc721c47bf425e07cc78f939a56fea6d57bcfa6e05eb7b47
+size 7416
diff --git a/blog_data/images/blog_a0c578ced20d_1.bin b/blog_data/images/blog_a0c578ced20d_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..813fa93fefde45c8caea928e01e299f4fe7b5d0a
--- /dev/null
+++ b/blog_data/images/blog_a0c578ced20d_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:293dddbc9720c7ee35bf1963c609b67e521a11790d88ef2e480c288d40d5c249
+size 26660
diff --git a/blog_data/images/blog_a0c578ced20d_2.bin b/blog_data/images/blog_a0c578ced20d_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..ac1a246530fbc1c1bf92f775e41ca10dbfa4c3aa
--- /dev/null
+++ b/blog_data/images/blog_a0c578ced20d_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7fa54c807f404a60c6fd275aa1d63f46b02878f6c9365aacf2c5e78db6e0fccd
+size 22694
diff --git a/blog_data/images/blog_a2eb4c3881e5_0.bin b/blog_data/images/blog_a2eb4c3881e5_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..d5514968351e2984ec9aadcd66b276b0aecf54f2
--- /dev/null
+++ b/blog_data/images/blog_a2eb4c3881e5_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7973028fca20c38e67dff92ecd5551e6dcb5b682592bd6b6cb642a1cb118c1a5
+size 15764
diff --git a/blog_data/images/blog_a74f16b0bbbe_0.jpg b/blog_data/images/blog_a74f16b0bbbe_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8f966335d1597e27f6197e254ee6c559e2ba9fb0
--- /dev/null
+++ b/blog_data/images/blog_a74f16b0bbbe_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:888aee560e8fe2e64f46c91990b64eb0bf544e6530e84c1d6f996bc5a5812d57
+size 69308
diff --git a/blog_data/images/blog_a74f16b0bbbe_1.jpg b/blog_data/images/blog_a74f16b0bbbe_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a5f88c31b57bf05948d7fc99e8865c7e1c72721b
--- /dev/null
+++ b/blog_data/images/blog_a74f16b0bbbe_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da7fac8ca97a40130f8fcaf51dac065eb87455c7004c272e850e897ec79a385b
+size 43378
diff --git a/blog_data/images/blog_a74f16b0bbbe_2.jpg b/blog_data/images/blog_a74f16b0bbbe_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..251bf4286e69ef11294e6f55573e4efb5f551846
--- /dev/null
+++ b/blog_data/images/blog_a74f16b0bbbe_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:75376cb484cff60831c33cbc71d87a829aa599498ec275b74c954324f7120170
+size 229659
diff --git a/blog_data/images/blog_a74f16b0bbbe_3.jpg b/blog_data/images/blog_a74f16b0bbbe_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..99bab4658fbd6bb23805a69dfa1d8e36c04875eb
--- /dev/null
+++ b/blog_data/images/blog_a74f16b0bbbe_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eadff67465e9e993e48c6fb1eb351716110f01351e987052dba1ba63ff9722b0
+size 69429
diff --git a/blog_data/images/blog_a74f16b0bbbe_4.jpg b/blog_data/images/blog_a74f16b0bbbe_4.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..eff8cdbe42684d73140551bc008756846c75fa68
--- /dev/null
+++ b/blog_data/images/blog_a74f16b0bbbe_4.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3295ed2d44d113c0afd5b214b9848d843cb35bc6acf27b4d69bab255a3d06b64
+size 55609
diff --git a/blog_data/images/blog_a74f16b0bbbe_5.bin b/blog_data/images/blog_a74f16b0bbbe_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_a74f16b0bbbe_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_a74f16b0bbbe_6.bin b/blog_data/images/blog_a74f16b0bbbe_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_a74f16b0bbbe_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_a76c4cce6c87_0.bin b/blog_data/images/blog_a76c4cce6c87_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..fc78d94ceddcc12dd32cc7354d05b57b611b6117
--- /dev/null
+++ b/blog_data/images/blog_a76c4cce6c87_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c8782881775667b693861412fd86defa4c453fd3825dc64ce7d3bacd5c48599a
+size 1043633
diff --git a/blog_data/images/blog_a76c4cce6c87_1.bin b/blog_data/images/blog_a76c4cce6c87_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_a76c4cce6c87_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_a76c4cce6c87_2.bin b/blog_data/images/blog_a76c4cce6c87_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_a76c4cce6c87_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_a9433beb4445_0.jpg b/blog_data/images/blog_a9433beb4445_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..160a0fd239e7efb2407f62aac107c43369c4a942
--- /dev/null
+++ b/blog_data/images/blog_a9433beb4445_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8d3ae497eb2c12fcf1fafe29ee5928ceb982759129e9ab7ebc93bd70627e3636
+size 74475
diff --git a/blog_data/images/blog_a9433beb4445_1.jpg b/blog_data/images/blog_a9433beb4445_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..839097ca4c4421872be313445a70b19deb616f69
--- /dev/null
+++ b/blog_data/images/blog_a9433beb4445_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6a058cdaf7245d8893848d2b4239edcb3bed1dc91f2ee328a7a3a34f46db175b
+size 132837
diff --git a/blog_data/images/blog_a9433beb4445_2.jpg b/blog_data/images/blog_a9433beb4445_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2b1d4b966d4df6d8fa806e5bd692c902f362ea3d
--- /dev/null
+++ b/blog_data/images/blog_a9433beb4445_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3ba912b7e258696743a37ddacf9881fe8b01c1aef82aae40c53b5cc63a722b3e
+size 109426
diff --git a/blog_data/images/blog_a9433beb4445_3.jpg b/blog_data/images/blog_a9433beb4445_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e6731f9039b92372ac01f49b24c8ec6512ea0e3f
--- /dev/null
+++ b/blog_data/images/blog_a9433beb4445_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b46993850ffb8af61a65ef88b5868b3b51f60074ff13d19b7ccb86a23093937c
+size 32571
diff --git a/blog_data/images/blog_a9433beb4445_4.bin b/blog_data/images/blog_a9433beb4445_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_a9433beb4445_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_a9433beb4445_5.bin b/blog_data/images/blog_a9433beb4445_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_a9433beb4445_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_a967ed7a8565_0.jpg b/blog_data/images/blog_a967ed7a8565_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f919923efdec9f34190a44ba2ded3a811376c9bf
--- /dev/null
+++ b/blog_data/images/blog_a967ed7a8565_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a3aabc5dbbe023f3fa30190e8020cd46a5d3b9187253abbccaad99e6da1c092e
+size 104044
diff --git a/blog_data/images/blog_a967ed7a8565_1.jpg b/blog_data/images/blog_a967ed7a8565_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..70110261b9301843b4080eae19b36468c658c6df
--- /dev/null
+++ b/blog_data/images/blog_a967ed7a8565_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a36e6456fd8f520c3e5b6391cb67d62fd6f5e4c4824af31ddb14d0838bd2f6a6
+size 54289
diff --git a/blog_data/images/blog_a967ed7a8565_2.jpg b/blog_data/images/blog_a967ed7a8565_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cce743833d4fd671aa9aee3bbc501bcccac8e5bd
--- /dev/null
+++ b/blog_data/images/blog_a967ed7a8565_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a1892b735be8b1f4b4b8adc8431d387060e3b9899cc57b293fd113a9e51a6f76
+size 47101
diff --git a/blog_data/images/blog_a967ed7a8565_3.jpg b/blog_data/images/blog_a967ed7a8565_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..241874d6afd073dff01e93efbd7be6a13e71e6b0
--- /dev/null
+++ b/blog_data/images/blog_a967ed7a8565_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:06cb0ecc98840152d1e041f9153487b5f4272b1064d8713e47ed4c785ece3be5
+size 178942
diff --git a/blog_data/images/blog_a967ed7a8565_4.jpg b/blog_data/images/blog_a967ed7a8565_4.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cc8a6c18db88216698e8f1d5d5d6b7e6d285bc99
--- /dev/null
+++ b/blog_data/images/blog_a967ed7a8565_4.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:32ee3e832f2d74f6c18da5655270e6a6f79dee6db9554a0ad234dbfd6265338f
+size 44505
diff --git a/blog_data/images/blog_a967ed7a8565_5.jpg b/blog_data/images/blog_a967ed7a8565_5.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..225d090687ceb9e087ad6573f62e718783f80e7b
--- /dev/null
+++ b/blog_data/images/blog_a967ed7a8565_5.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:afec954851dff60a2dffdf0fe87bffda795415c3e394dd547f3898bbe770b1d6
+size 52833
diff --git a/blog_data/images/blog_a967ed7a8565_6.jpg b/blog_data/images/blog_a967ed7a8565_6.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c8deb8a6d1835f2d3ecbff4b071849589ade04ae
--- /dev/null
+++ b/blog_data/images/blog_a967ed7a8565_6.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1aa5ee180cb19ce14c2f2b3a2c2bad130db49e2418f9573f1d6b67fe84dfc74
+size 96555
diff --git a/blog_data/images/blog_a967ed7a8565_7.bin b/blog_data/images/blog_a967ed7a8565_7.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_a967ed7a8565_7.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_a967ed7a8565_8.bin b/blog_data/images/blog_a967ed7a8565_8.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_a967ed7a8565_8.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_b8c6227065bf_0.jpg b/blog_data/images/blog_b8c6227065bf_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..17552d914ed6e457b9c9b62cb531d4d9959ad09c
--- /dev/null
+++ b/blog_data/images/blog_b8c6227065bf_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:05dcadeceef54c1f5e39d1d5b15a40676ec31089c5cd8e1aab4e8b43529ea96b
+size 134380
diff --git a/blog_data/images/blog_b8c6227065bf_1.bin b/blog_data/images/blog_b8c6227065bf_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_b8c6227065bf_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_b8c6227065bf_2.bin b/blog_data/images/blog_b8c6227065bf_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_b8c6227065bf_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_bf4696c52814_0.bin b/blog_data/images/blog_bf4696c52814_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..5c3a04559a3db789a68efd8032a17ba12807e3c9
--- /dev/null
+++ b/blog_data/images/blog_bf4696c52814_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:414cb01a36ebb91b08d6db085bbe68aed8109b7281a87ebfd1f23d24217abec2
+size 22828
diff --git a/blog_data/images/blog_c9657c1fd793_0.jpg b/blog_data/images/blog_c9657c1fd793_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4a838db6f383bb4d6326acdde108cab41cae5b9e
--- /dev/null
+++ b/blog_data/images/blog_c9657c1fd793_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8941b2d18c969090714c6958711330791d0cb3a399649b5131bd919fb4b93045
+size 43836
diff --git a/blog_data/images/blog_c9657c1fd793_1.jpg b/blog_data/images/blog_c9657c1fd793_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7fe21653557097205883db96e477c5e89898fae3
--- /dev/null
+++ b/blog_data/images/blog_c9657c1fd793_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5f1a1f6a159bce02c5974cf1a64b7b975b4e2ab21239a39be85369db89dd079d
+size 117716
diff --git a/blog_data/images/blog_c9657c1fd793_2.jpg b/blog_data/images/blog_c9657c1fd793_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dcab1c0aa8fc60b1888a96b7097a3fe0c984f174
--- /dev/null
+++ b/blog_data/images/blog_c9657c1fd793_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1da293ef01681dd23f2d3ef229c3cf85abe51ae35cf838f9f2a65237b814d598
+size 52035
diff --git a/blog_data/images/blog_c9657c1fd793_3.bin b/blog_data/images/blog_c9657c1fd793_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_c9657c1fd793_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_c9657c1fd793_4.bin b/blog_data/images/blog_c9657c1fd793_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_c9657c1fd793_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_cbf38e6d19b6_0.jpg b/blog_data/images/blog_cbf38e6d19b6_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..df89c2a354ebd57dcf3cc0f7b9a5ec88a38fb941
--- /dev/null
+++ b/blog_data/images/blog_cbf38e6d19b6_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:833f195f56532855146ecc338d72f7cbd773ef7d0d445dbfa5fda712d1cfd4eb
+size 86924
diff --git a/blog_data/images/blog_cbf38e6d19b6_1.jpg b/blog_data/images/blog_cbf38e6d19b6_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..660929223a424a9af8e76dd94d3c1ae2a173f72d
--- /dev/null
+++ b/blog_data/images/blog_cbf38e6d19b6_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:380aac14377bc0db3f86e8bec42145a9088f346b1f857ff659975241c796c3cb
+size 85740
diff --git a/blog_data/images/blog_cbf38e6d19b6_2.jpg b/blog_data/images/blog_cbf38e6d19b6_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..69dc6d597cefc52745a4cd526a1e7172ade96520
--- /dev/null
+++ b/blog_data/images/blog_cbf38e6d19b6_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e646b4fef23fe0470674d2b5530351c81c1fe204acf65d3507cbc024e23eedb8
+size 80407
diff --git a/blog_data/images/blog_cbf38e6d19b6_3.jpg b/blog_data/images/blog_cbf38e6d19b6_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..98e1f2a29fbe520cd3bbd202e8f304fb4fe81e67
--- /dev/null
+++ b/blog_data/images/blog_cbf38e6d19b6_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf5e4373093ede7b1bd37490fe741d2a8fb1ba29493f6deb6beb46c5fb37a26c
+size 57476
diff --git a/blog_data/images/blog_cbf38e6d19b6_4.bin b/blog_data/images/blog_cbf38e6d19b6_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_cbf38e6d19b6_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_cbf38e6d19b6_5.bin b/blog_data/images/blog_cbf38e6d19b6_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_cbf38e6d19b6_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_cc52eac8321f_0.jpg b/blog_data/images/blog_cc52eac8321f_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9ed24e05707fc2746a6be94051173f90168e3ef0
--- /dev/null
+++ b/blog_data/images/blog_cc52eac8321f_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c9625435bd3f17c3e4e4d3160ff6c3fdb89f6ad711099b2bfe1f4f67b3477485
+size 53073
diff --git a/blog_data/images/blog_cc52eac8321f_1.jpg b/blog_data/images/blog_cc52eac8321f_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2825b6f5e73e4d7798dfb35d8fba495bb1aeb093
--- /dev/null
+++ b/blog_data/images/blog_cc52eac8321f_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d599713f2ee86efdd94d3ae9aa52ac198989163e5acfd9a50ef515f6061a94ce
+size 73721
diff --git a/blog_data/images/blog_cc52eac8321f_2.jpg b/blog_data/images/blog_cc52eac8321f_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..23a383d60a15d08f6c6b8d02b4c1cdc9a33be970
--- /dev/null
+++ b/blog_data/images/blog_cc52eac8321f_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1d34f0655a66e05757f90017354be4991569ab321cd7f93faa8351972996b77f
+size 82648
diff --git a/blog_data/images/blog_cc52eac8321f_3.bin b/blog_data/images/blog_cc52eac8321f_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_cc52eac8321f_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_cc52eac8321f_4.bin b/blog_data/images/blog_cc52eac8321f_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_cc52eac8321f_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_d195042a054a_0.jpg b/blog_data/images/blog_d195042a054a_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1688773e5b142dadcc7d694425fdb98aaea0e7cd
--- /dev/null
+++ b/blog_data/images/blog_d195042a054a_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1c56b5f6e99101e4c184b5a57a0553509280f65e2cbef236853a05d66da60078
+size 66265
diff --git a/blog_data/images/blog_d195042a054a_1.jpg b/blog_data/images/blog_d195042a054a_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ddcdad1323b02dc12f1e4157dd53225b972ed29c
--- /dev/null
+++ b/blog_data/images/blog_d195042a054a_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:993c1c74cb18c4b955858068415a3323c40d7d4b6a863f887ba21c4ce91aec66
+size 89296
diff --git a/blog_data/images/blog_d195042a054a_2.bin b/blog_data/images/blog_d195042a054a_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_d195042a054a_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_d195042a054a_3.bin b/blog_data/images/blog_d195042a054a_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_d195042a054a_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_d65fbd60198b_0.bin b/blog_data/images/blog_d65fbd60198b_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..496b37d061b3c7577635a600ad93f1882deaaf94
--- /dev/null
+++ b/blog_data/images/blog_d65fbd60198b_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7449f7f448fba44c565b9a95ebef65f920cce913904462e29c768cc564eeef24
+size 55172
diff --git a/blog_data/images/blog_d65fbd60198b_1.bin b/blog_data/images/blog_d65fbd60198b_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..ef355bcd49e8f3a4e2dced0d05b37618875e6436
--- /dev/null
+++ b/blog_data/images/blog_d65fbd60198b_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a08227304b1b4677e07dffaffc34b2df80eb7c4331ae73d14488820dd02cea49
+size 167660
diff --git a/blog_data/images/blog_d65fbd60198b_2.bin b/blog_data/images/blog_d65fbd60198b_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..ca11bd639b7f86021489ec11711b110239c4655b
--- /dev/null
+++ b/blog_data/images/blog_d65fbd60198b_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3894b4efd2d94d076ffbb9c2d96c30feac6328449eeb540aa413838d49491c64
+size 50030
diff --git a/blog_data/images/blog_d65fbd60198b_3.bin b/blog_data/images/blog_d65fbd60198b_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..bce66542a77649801b139f0c1e7faaaeaaa9ea07
--- /dev/null
+++ b/blog_data/images/blog_d65fbd60198b_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8aeea0c1ad7ff76f4a6c19ed3f5efe6d87ec792c7188a74d3eb05e6cf1b5df6f
+size 111486
diff --git a/blog_data/images/blog_d6f6b79d8ea8_0.bin b/blog_data/images/blog_d6f6b79d8ea8_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..c3d2bfb20d77b6f168fe8a7cb3912e477a01bd85
--- /dev/null
+++ b/blog_data/images/blog_d6f6b79d8ea8_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:33d8d942ad41cfd3b15c30ffd694e2c177622dfbe46ec38a5cd962b1cb257ea6
+size 157858
diff --git a/blog_data/images/blog_d6f6b79d8ea8_1.bin b/blog_data/images/blog_d6f6b79d8ea8_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..39d67b43cdd0f06a48fcb50388257d1784f6c96e
--- /dev/null
+++ b/blog_data/images/blog_d6f6b79d8ea8_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:acf193815709f42852e92ea940331221a831e7df9d3f406c3d9bfd05d1b4c43a
+size 49278
diff --git a/blog_data/images/blog_d8484dc1535d_0.jpg b/blog_data/images/blog_d8484dc1535d_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ed8a2fd7537eda464f41735d7fb502d257a37507
--- /dev/null
+++ b/blog_data/images/blog_d8484dc1535d_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d061471043336be3a1b1fac6b4ae32e41bdb5595a8bbe5215ee3cc095deb18ad
+size 92356
diff --git a/blog_data/images/blog_d8484dc1535d_1.jpg b/blog_data/images/blog_d8484dc1535d_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9753918d7fdfe11ca2aa81bedca07d7dde15778c
--- /dev/null
+++ b/blog_data/images/blog_d8484dc1535d_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c5fa724907edc75a2263c0ab21eb6a44311932edd2871347b13d1b3e1f7b41c1
+size 86723
diff --git a/blog_data/images/blog_d8484dc1535d_2.jpg b/blog_data/images/blog_d8484dc1535d_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..57afaa917ab402273e8f2f8d65911a21979c038e
--- /dev/null
+++ b/blog_data/images/blog_d8484dc1535d_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:edaa28b481229b6c03044cb8bbe682423259cea5618c1bc6e92fb93a366f0b23
+size 149855
diff --git a/blog_data/images/blog_d8484dc1535d_3.jpg b/blog_data/images/blog_d8484dc1535d_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..79e1375fb4152b29ade27321d63cb52a8f40e573
--- /dev/null
+++ b/blog_data/images/blog_d8484dc1535d_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:349ba270e1184481c903363db58e2ac1725c9e404425d4044fc25724a01eb894
+size 51611
diff --git a/blog_data/images/blog_d8484dc1535d_4.bin b/blog_data/images/blog_d8484dc1535d_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_d8484dc1535d_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_d8484dc1535d_5.bin b/blog_data/images/blog_d8484dc1535d_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_d8484dc1535d_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_da4d946e6ccf_0.jpg b/blog_data/images/blog_da4d946e6ccf_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..601a97fd401ae986edca9d81c750121ef5b8d846
--- /dev/null
+++ b/blog_data/images/blog_da4d946e6ccf_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2ce20c910db7a8ea26079ad723ef38d71f700d7f13933c6dbb84848fa8652a6e
+size 149932
diff --git a/blog_data/images/blog_da4d946e6ccf_1.jpg b/blog_data/images/blog_da4d946e6ccf_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..648934cbac7715bc8425135d1910eaf20cde6d0d
--- /dev/null
+++ b/blog_data/images/blog_da4d946e6ccf_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0bb9f47cee1117f70659ec08cde6e1e8a7907180d9702194d816a8fb19e6cbae
+size 143438
diff --git a/blog_data/images/blog_da4d946e6ccf_2.jpg b/blog_data/images/blog_da4d946e6ccf_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3800b1c8c38f664863f04f37834e74921fc7e220
--- /dev/null
+++ b/blog_data/images/blog_da4d946e6ccf_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:595a13cd35deb3e7c1e8eef91e9342ec542293af5be3db270423c2c3686189bc
+size 110414
diff --git a/blog_data/images/blog_da4d946e6ccf_3.jpg b/blog_data/images/blog_da4d946e6ccf_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..57e9f3f99ebde3a92d1944595b25f762c5677f8c
--- /dev/null
+++ b/blog_data/images/blog_da4d946e6ccf_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9a58f76f0aa48b2af859c953f5590cf0c0fbd99a832ceaa1711b5796d92a9fad
+size 118078
diff --git a/blog_data/images/blog_da4d946e6ccf_4.jpg b/blog_data/images/blog_da4d946e6ccf_4.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..91d8e266541c7b0702ada4b9e50de31ef59468b1
--- /dev/null
+++ b/blog_data/images/blog_da4d946e6ccf_4.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2307e7e342f8598cc8ab689a90dd28964c27a6ea08873195946885176b94e557
+size 88956
diff --git a/blog_data/images/blog_da4d946e6ccf_5.bin b/blog_data/images/blog_da4d946e6ccf_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_da4d946e6ccf_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_da4d946e6ccf_6.bin b/blog_data/images/blog_da4d946e6ccf_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_da4d946e6ccf_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_da87fa33c3e4_0.jpg b/blog_data/images/blog_da87fa33c3e4_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6a7b824194ddd56854be9b3c5bef527c8b10fec7
--- /dev/null
+++ b/blog_data/images/blog_da87fa33c3e4_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fb47b6f3fa914e197e6aaa145c75b2a5c3eb79a213df0055cce5f4c1c4afc49a
+size 36751
diff --git a/blog_data/images/blog_da87fa33c3e4_1.jpg b/blog_data/images/blog_da87fa33c3e4_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a03c51ee7e1897b20a20568de642692e9596bf4e
--- /dev/null
+++ b/blog_data/images/blog_da87fa33c3e4_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a06751216d1aae663607ecb0ecca042cb9d5b33be23a77f8eb7f91870dcafd35
+size 60784
diff --git a/blog_data/images/blog_da87fa33c3e4_2.jpg b/blog_data/images/blog_da87fa33c3e4_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b7f380bf982c80a2339d2e4f20060e52a1cf95c6
--- /dev/null
+++ b/blog_data/images/blog_da87fa33c3e4_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a0cf20108b91c565e9a637e2049eb33080f77dedfecd55c9d3a7f241b232567d
+size 109545
diff --git a/blog_data/images/blog_da87fa33c3e4_3.jpg b/blog_data/images/blog_da87fa33c3e4_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3306fe7053289d2d5f71baf02da3baed4789f848
--- /dev/null
+++ b/blog_data/images/blog_da87fa33c3e4_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d3ace3f024aa412724840454dbf95ed7b03560c8cf8fd9e4995f09fc551f4af9
+size 39679
diff --git a/blog_data/images/blog_da87fa33c3e4_4.bin b/blog_data/images/blog_da87fa33c3e4_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_da87fa33c3e4_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_da87fa33c3e4_5.bin b/blog_data/images/blog_da87fa33c3e4_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_da87fa33c3e4_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_e01844337911_0.jpg b/blog_data/images/blog_e01844337911_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..583680325912bbb7563c030d264446394c3d4309
--- /dev/null
+++ b/blog_data/images/blog_e01844337911_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:869a4e008d3714c95136b05bcbcf1ddd53c4381d6274fe809f25ec9f232d1f76
+size 98710
diff --git a/blog_data/images/blog_e01844337911_1.jpg b/blog_data/images/blog_e01844337911_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fc92552974a2eb5b0071832fcca43138d3cdc234
--- /dev/null
+++ b/blog_data/images/blog_e01844337911_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a2f150fd712c2a2e57aa2dc8d6e01a3c179fdddcfa038926c2702912cfef76c2
+size 87643
diff --git a/blog_data/images/blog_e01844337911_2.jpg b/blog_data/images/blog_e01844337911_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e72b5d3018b7f574ac52d89d68134a552cc420ca
--- /dev/null
+++ b/blog_data/images/blog_e01844337911_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e18358262132d1d3738778aa0a1c255b2f032eeec2e35819ffe6f9208c984c6d
+size 68005
diff --git a/blog_data/images/blog_e01844337911_3.jpg b/blog_data/images/blog_e01844337911_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c1b6fff5c0200988246a2e60f3bf72948a871d76
--- /dev/null
+++ b/blog_data/images/blog_e01844337911_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7fbe6ff1886c72ef5ce83c62ad617936e59a2c4a8702383e668eccb38d41cf1b
+size 103309
diff --git a/blog_data/images/blog_e01844337911_4.jpg b/blog_data/images/blog_e01844337911_4.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fdea2193f1816b29dcb538db07406574c53bda2d
--- /dev/null
+++ b/blog_data/images/blog_e01844337911_4.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0886203878a6aafbd22b3916aae55733c8ccc3533a9dc76fbe1aaaf660c0b581
+size 102868
diff --git a/blog_data/images/blog_e01844337911_5.jpg b/blog_data/images/blog_e01844337911_5.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f27bbc7a4ec5cd3a4e1058c493a920ce86f8ccba
--- /dev/null
+++ b/blog_data/images/blog_e01844337911_5.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a13b3d9769b1e794feb837e560a124bd71bcde9d4eae2df3fc3b7e137a16972
+size 199841
diff --git a/blog_data/images/blog_e01844337911_6.jpg b/blog_data/images/blog_e01844337911_6.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..56d2f7349e9736e509c9a48e5db2f1aca079fb8d
--- /dev/null
+++ b/blog_data/images/blog_e01844337911_6.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:06064b5db236cfc0ad00891e0924ed90a909bc90a0b1ad6d974c5a6aedd281cc
+size 101819
diff --git a/blog_data/images/blog_e01844337911_7.bin b/blog_data/images/blog_e01844337911_7.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_e01844337911_7.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_e01844337911_8.bin b/blog_data/images/blog_e01844337911_8.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_e01844337911_8.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_e19a8648ed76_0.bin b/blog_data/images/blog_e19a8648ed76_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..0625f32478ef76b9f23627e0c5911be420b3782c
--- /dev/null
+++ b/blog_data/images/blog_e19a8648ed76_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:062777e61d4495a199e31c1236e4f9abc3f235d85e8ddaa32105a9adc099cc88
+size 130858
diff --git a/blog_data/images/blog_e32049c84994_0.bin b/blog_data/images/blog_e32049c84994_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4627de894172537bac7ab7deaa1de79cdce132ce
--- /dev/null
+++ b/blog_data/images/blog_e32049c84994_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fada59750a7ebb13132139cac08a0f410798300fc7935e19d515702d469e0756
+size 466521
diff --git a/blog_data/images/blog_e32049c84994_1.bin b/blog_data/images/blog_e32049c84994_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..2369f645b01b41eee85e8f402780957a97e498f3
--- /dev/null
+++ b/blog_data/images/blog_e32049c84994_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:75d253ed5fc7dc1d9923fa08b427c53e5aaddc39307ca234f832331448ed3e3c
+size 461286
diff --git a/blog_data/images/blog_e32049c84994_10.bin b/blog_data/images/blog_e32049c84994_10.bin
new file mode 100644
index 0000000000000000000000000000000000000000..d6ba46a9934069d039caba06bb1db2d335bcb257
--- /dev/null
+++ b/blog_data/images/blog_e32049c84994_10.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88816629bea640686e9e9dd4c77266e9442a0427aec6de54a73015b1bfb9e6a0
+size 1506793
diff --git a/blog_data/images/blog_e32049c84994_11.bin b/blog_data/images/blog_e32049c84994_11.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4a161dfcbde7cb683032251f9e171539bd21d8f5
--- /dev/null
+++ b/blog_data/images/blog_e32049c84994_11.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fdf24c2c42cc92fbfd3dfc244ebe90ffeb326ea7e3248fb275735494ff06a68f
+size 5230580
diff --git a/blog_data/images/blog_e32049c84994_12.bin b/blog_data/images/blog_e32049c84994_12.bin
new file mode 100644
index 0000000000000000000000000000000000000000..e078edf25edbee2fa48862087331a193e7cf58ef
--- /dev/null
+++ b/blog_data/images/blog_e32049c84994_12.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:15082d3cb43fd08f3718b2d8bb83ab0ccbec8ea72f3d496ccfbc090b000e6918
+size 1423155
diff --git a/blog_data/images/blog_e32049c84994_13.bin b/blog_data/images/blog_e32049c84994_13.bin
new file mode 100644
index 0000000000000000000000000000000000000000..2d51d2b6780430e8a7b8454bf5060919dbc45cd7
--- /dev/null
+++ b/blog_data/images/blog_e32049c84994_13.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:80b102ff18adfbf2dc4d07033eeae5f06a38acc0c3d7a6c517391134a7961f0f
+size 1562413
diff --git a/blog_data/images/blog_e32049c84994_2.bin b/blog_data/images/blog_e32049c84994_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..2c1961d589a2cf6031afef9be90281a877ec8cde
--- /dev/null
+++ b/blog_data/images/blog_e32049c84994_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:32941dc4def5b1233b81ace914e67ac8601f048d7cd9b0b84ca66d5b7b04195e
+size 482556
diff --git a/blog_data/images/blog_e32049c84994_3.bin b/blog_data/images/blog_e32049c84994_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..1196cf23b4fdba2ea911d2205eba19248405861f
--- /dev/null
+++ b/blog_data/images/blog_e32049c84994_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:11ccadab39bc363a3181e9151fc32de5d8b05c0125dfaebe6b7eb5efdef21bd8
+size 487079
diff --git a/blog_data/images/blog_e32049c84994_4.bin b/blog_data/images/blog_e32049c84994_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..c63b5d64e36e4aa05bb1ab39a3fdadb859a6d87e
--- /dev/null
+++ b/blog_data/images/blog_e32049c84994_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:563bd63b83fd32263853011d997950bc4134801483c37ea62db0f61cf7599d50
+size 534749
diff --git a/blog_data/images/blog_e32049c84994_5.bin b/blog_data/images/blog_e32049c84994_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..e2f53398bbee00489c94091f4c378fdf58bf3591
--- /dev/null
+++ b/blog_data/images/blog_e32049c84994_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1c5bd9dc002713cd5086b703d9b24ff9358f73b1d411153fc58a732d59c187f
+size 1384847
diff --git a/blog_data/images/blog_e32049c84994_6.bin b/blog_data/images/blog_e32049c84994_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..e0a1049ad2c1e5a605f13292f9ce8f053bf4408c
--- /dev/null
+++ b/blog_data/images/blog_e32049c84994_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ffc424971e7cbf7bcac4ef317ee6a6dea6bd3084dce1782701c8f482d78a6cf0
+size 498531
diff --git a/blog_data/images/blog_e32049c84994_7.bin b/blog_data/images/blog_e32049c84994_7.bin
new file mode 100644
index 0000000000000000000000000000000000000000..f9d829571f36e738bfd7ce75b7f1b6ab9d2bc77d
--- /dev/null
+++ b/blog_data/images/blog_e32049c84994_7.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:95f967a91e0ea9445ed75e82d17322028f7d226714bf9fb0511475451cf0150a
+size 557006
diff --git a/blog_data/images/blog_e32049c84994_8.bin b/blog_data/images/blog_e32049c84994_8.bin
new file mode 100644
index 0000000000000000000000000000000000000000..2e71214adf451e5d60afc91c99a9e6d687f8ace8
--- /dev/null
+++ b/blog_data/images/blog_e32049c84994_8.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:60189f21024a4ac55e5e75513156229b77c0b7e6d96252b7d044122aa6e9016b
+size 1255902
diff --git a/blog_data/images/blog_e32049c84994_9.bin b/blog_data/images/blog_e32049c84994_9.bin
new file mode 100644
index 0000000000000000000000000000000000000000..85d0d7977df7d941d1b9fee9deff2218351f1b6f
--- /dev/null
+++ b/blog_data/images/blog_e32049c84994_9.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:965157cd91c132e1610675a8aecdaf492704c92307ebbd8b97011532be8d20c6
+size 1343044
diff --git a/blog_data/images/blog_e4721ca9ef8f_0.bin b/blog_data/images/blog_e4721ca9ef8f_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..bb47af1b927e8b30279a6a738ce820c38abff820
--- /dev/null
+++ b/blog_data/images/blog_e4721ca9ef8f_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5fa4f3c78cbd9c8d98ef3f359d138cc2a4f5e3fe44da36f5c7d73036aeba13ba
+size 16918
diff --git a/blog_data/images/blog_e4721ca9ef8f_1.bin b/blog_data/images/blog_e4721ca9ef8f_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..58061cf170fe7194e479f64488b6496762255300
--- /dev/null
+++ b/blog_data/images/blog_e4721ca9ef8f_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:238a0eec00b72a578ed95395dee791708b1880496886243ddbc338fa2ac442d0
+size 17112
diff --git a/blog_data/images/blog_e56bd5a4a7e5_0.jpg b/blog_data/images/blog_e56bd5a4a7e5_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e0fefe0e173cf695d0cd062b1ce62efc66a33f04
--- /dev/null
+++ b/blog_data/images/blog_e56bd5a4a7e5_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bebe140ea9535843561eb8b20dcae1946506987068fd2e8f275c1b4492a94138
+size 53996
diff --git a/blog_data/images/blog_e56bd5a4a7e5_1.bin b/blog_data/images/blog_e56bd5a4a7e5_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_e56bd5a4a7e5_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_e56bd5a4a7e5_2.bin b/blog_data/images/blog_e56bd5a4a7e5_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_e56bd5a4a7e5_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_ecb6460988fe_0.bin b/blog_data/images/blog_ecb6460988fe_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..d80730721cc78969812adc72c160ba3f882fd1b2
--- /dev/null
+++ b/blog_data/images/blog_ecb6460988fe_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e18b0930f0b23574c64fa80411d5c201f2824d3fb9737ffaeb1b00bee81ba9b4
+size 295541
diff --git a/blog_data/images/blog_ecb6460988fe_1.bin b/blog_data/images/blog_ecb6460988fe_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..fdb5ecd0a1b33de4688e6107c36c956fc50b7131
--- /dev/null
+++ b/blog_data/images/blog_ecb6460988fe_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e1da0460da3112375d483a8d33c8ab4b39180bf4094f64a75588b7bfb2b6f759
+size 606504
diff --git a/blog_data/images/blog_ecb6460988fe_10.bin b/blog_data/images/blog_ecb6460988fe_10.bin
new file mode 100644
index 0000000000000000000000000000000000000000..fe51bf6a5704e51bd6390f60b73b4cea0e0bb36e
--- /dev/null
+++ b/blog_data/images/blog_ecb6460988fe_10.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:950e8d1f24440931083945dd1d79119479b8e936b564b3d14795a27cdc256f0f
+size 1239434
diff --git a/blog_data/images/blog_ecb6460988fe_2.bin b/blog_data/images/blog_ecb6460988fe_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4f3fb6941eed9a1874ce0debd629c055d5156121
--- /dev/null
+++ b/blog_data/images/blog_ecb6460988fe_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:15915be039c8f59949f1f7340ecca9c4a8ca1e51a45c827aebfd8193150ac647
+size 309502
diff --git a/blog_data/images/blog_ecb6460988fe_3.bin b/blog_data/images/blog_ecb6460988fe_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..952ad42bc03bee9424a46782258cb928689c7554
--- /dev/null
+++ b/blog_data/images/blog_ecb6460988fe_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02b4299ba410d0e2134785a3a1e2fd863cfb997ff05552ca36de5ceec9c04e1d
+size 1164141
diff --git a/blog_data/images/blog_ecb6460988fe_4.bin b/blog_data/images/blog_ecb6460988fe_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..899062569f77ba19627e2b4f29a6231c88c5a4b0
--- /dev/null
+++ b/blog_data/images/blog_ecb6460988fe_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:32e3a1a8ae84fc3f7aefbd3ae50c19f0673fa4dbbe57d3fd45427bfa9569f74d
+size 1218415
diff --git a/blog_data/images/blog_ecb6460988fe_5.bin b/blog_data/images/blog_ecb6460988fe_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..caffdd1cd1d92d4f156d4e03b46986f9dc1d6ce3
--- /dev/null
+++ b/blog_data/images/blog_ecb6460988fe_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:07bdbc3fb580f9d4a2d07b7db279ce13245440dd470375c6b466e861b1a7d9a2
+size 607597
diff --git a/blog_data/images/blog_ecb6460988fe_6.bin b/blog_data/images/blog_ecb6460988fe_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..c98c5281d03ff6a6b3db70db466d4b1f6ed5f2d9
--- /dev/null
+++ b/blog_data/images/blog_ecb6460988fe_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:221c973a539c88e0f2babdcb292dae7f3b7214800df55781c4321aa98063a798
+size 845231
diff --git a/blog_data/images/blog_ecb6460988fe_7.bin b/blog_data/images/blog_ecb6460988fe_7.bin
new file mode 100644
index 0000000000000000000000000000000000000000..0dadb02842c12f425a455f33daacd0c5f41bb9a3
--- /dev/null
+++ b/blog_data/images/blog_ecb6460988fe_7.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d683ed0656900a159f3416e2df76c729447cbb99a0e96815114f967191812aec
+size 1270654
diff --git a/blog_data/images/blog_ecb6460988fe_8.bin b/blog_data/images/blog_ecb6460988fe_8.bin
new file mode 100644
index 0000000000000000000000000000000000000000..2c2604afe018e9fa17a18f50a7237c36ba542138
--- /dev/null
+++ b/blog_data/images/blog_ecb6460988fe_8.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aafb6c9191eccbfbd5c44f5f497950de70dda544c00a7f405b2e2c860b4baf75
+size 24675
diff --git a/blog_data/images/blog_ecb6460988fe_9.bin b/blog_data/images/blog_ecb6460988fe_9.bin
new file mode 100644
index 0000000000000000000000000000000000000000..dd0aad8d6b6a5d601a154a10463741a8212171f2
--- /dev/null
+++ b/blog_data/images/blog_ecb6460988fe_9.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:680259ba8df149fa3d8d2e63f0647d26d6e7868e2082d15182d447e60d929e6f
+size 24462
diff --git a/blog_data/images/blog_edc6298762bb_0.bin b/blog_data/images/blog_edc6298762bb_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..9c67f84cf771e2e1a0dea457e7736f1ead7cafc4
--- /dev/null
+++ b/blog_data/images/blog_edc6298762bb_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d877ac86feb1b58253d9ddbcaf4e7924a8b10c58c2695d75e8f6d2ca8952e71d
+size 12364
diff --git a/blog_data/images/blog_edc6298762bb_1.bin b/blog_data/images/blog_edc6298762bb_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..5ad347bb9a889596e39dea741c118c787db4ffd0
--- /dev/null
+++ b/blog_data/images/blog_edc6298762bb_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9920bc271a645ca17f3867894a8dc8712763f27342cbe6fe7833da74454ca550
+size 8072
diff --git a/blog_data/images/blog_edc6298762bb_2.bin b/blog_data/images/blog_edc6298762bb_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..25ad159886f252ef9d8fb46b9fff0994fe705a14
--- /dev/null
+++ b/blog_data/images/blog_edc6298762bb_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:24f28c585b5622baca53a261df9e113c0b63777a662a5f0f2b77f3eac9712a00
+size 3882
diff --git a/blog_data/images/blog_edc6298762bb_3.bin b/blog_data/images/blog_edc6298762bb_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..eea9bdd618bfee90ec710d38376e24848ca7ff4f
--- /dev/null
+++ b/blog_data/images/blog_edc6298762bb_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e9ec32631da2e2f88ac97b9571dd0de14969cef9c5a3ffdb3ede2904cc23762a
+size 9006
diff --git a/blog_data/images/blog_edc6298762bb_4.bin b/blog_data/images/blog_edc6298762bb_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..7f11d6821e69a52c311d56b75eb5fbf62bd6c115
--- /dev/null
+++ b/blog_data/images/blog_edc6298762bb_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:530745556b7dd449dd636c19a5a39ee363e5113f6d0f0e559093b8da2d69d878
+size 9096
diff --git a/blog_data/images/blog_edc6298762bb_5.bin b/blog_data/images/blog_edc6298762bb_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..54d57b965c2e054d371d54214a323e1f77948de6
--- /dev/null
+++ b/blog_data/images/blog_edc6298762bb_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da584fc2e3a2cf1d0909c89e19c632426e2db50b66cbf3612c3de8953ac8529f
+size 64264
diff --git a/blog_data/images/blog_edc6298762bb_6.bin b/blog_data/images/blog_edc6298762bb_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..c1e2c1d935ef50ebe6d8c89af7331969e0cbfca5
--- /dev/null
+++ b/blog_data/images/blog_edc6298762bb_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d85bc57bbbd2f9bb5e7ffe6501d534aaa836ecf3afce389d5d91539689ce82ea
+size 62216
diff --git a/blog_data/images/blog_edc6298762bb_7.bin b/blog_data/images/blog_edc6298762bb_7.bin
new file mode 100644
index 0000000000000000000000000000000000000000..f043505e2d0e0fbac3cb6d34e52d1d92fb4d9901
--- /dev/null
+++ b/blog_data/images/blog_edc6298762bb_7.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d9fd7e8566d8bd9c9ea2e069fe010098b768d24e7d15512d40d0d84ff3d7269
+size 69944
diff --git a/blog_data/images/blog_edc6298762bb_8.bin b/blog_data/images/blog_edc6298762bb_8.bin
new file mode 100644
index 0000000000000000000000000000000000000000..2d133646ff88c7d7621256622b6291ae9988753d
--- /dev/null
+++ b/blog_data/images/blog_edc6298762bb_8.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:17be303cc4505d6a3829c42f77ad915466181a0194e2dd8199e981a66ecea0da
+size 119358
diff --git a/blog_data/images/blog_edc6298762bb_9.bin b/blog_data/images/blog_edc6298762bb_9.bin
new file mode 100644
index 0000000000000000000000000000000000000000..5d85b709098f2e50f9b7def192bec9160cd2bc3f
--- /dev/null
+++ b/blog_data/images/blog_edc6298762bb_9.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa1f41a86ca7c7e68b4b26cd7d40a8edef2adf8934332e64fe340f4e033a74d4
+size 28770
diff --git a/blog_data/images/blog_ee235d705ea6_0.bin b/blog_data/images/blog_ee235d705ea6_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..7ca9ae6ac7ed0337786ee0ddb79564baa3e36134
--- /dev/null
+++ b/blog_data/images/blog_ee235d705ea6_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:911b6454ee5a20b0fd98043ecafed118381ba0e685b7a1b47895559a698bff21
+size 37416
diff --git a/blog_data/images/blog_ee235d705ea6_1.bin b/blog_data/images/blog_ee235d705ea6_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..3abc254a8a5e47f41be4059c741c2bbfad4b65cd
--- /dev/null
+++ b/blog_data/images/blog_ee235d705ea6_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:62969490879bb3e7fe398f4b08b3bcd95a1377d62b41dcb467a1d3a217e8f036
+size 39660
diff --git a/blog_data/images/blog_ee235d705ea6_2.bin b/blog_data/images/blog_ee235d705ea6_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..1264036528654d403fe8f6720251ffa9006c0dbd
--- /dev/null
+++ b/blog_data/images/blog_ee235d705ea6_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:71b5129d730ba1de16f1b3706a0e9eec7914145074528143ff9d840bb25c1f97
+size 22554
diff --git a/blog_data/images/blog_ee6bd9beb826_0.jpg b/blog_data/images/blog_ee6bd9beb826_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c98f66daf55774659b2d503730cc34e9b51367dc
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ed89d57578e474fba2481b790ee2735bf254d0e8dac405d13cd2d86d3cae880f
+size 155326
diff --git a/blog_data/images/blog_ee6bd9beb826_1.jpg b/blog_data/images/blog_ee6bd9beb826_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c771613c5b0346a639b6d4d151c465f7f6c28bfd
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c4f1db70ce4c39ca1b4bee84474bef5597f3807043082af34adbc5d107f60857
+size 103677
diff --git a/blog_data/images/blog_ee6bd9beb826_10.jpg b/blog_data/images/blog_ee6bd9beb826_10.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1232835de91da308caaf23d56e5ed0b2fa467e1e
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_10.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b8653400b09f5e778164bf8dafde04e7e6901b131233157fc26ce10c6b3807bd
+size 300668
diff --git a/blog_data/images/blog_ee6bd9beb826_11.jpg b/blog_data/images/blog_ee6bd9beb826_11.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..65ed31deb11a88e2cd29c0822c514b61d1b9b0e8
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_11.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:21369437f3cc4a5350f5ab4158a33174c66aa9b6c03f845d5a631a57235e2610
+size 64989
diff --git a/blog_data/images/blog_ee6bd9beb826_12.jpg b/blog_data/images/blog_ee6bd9beb826_12.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6f7fc4a475708e7988e99b5feb94a14479a166c7
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_12.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:efa3d5b647fc7f74544b5eb1ff2cf930a38bd82aef46069236861f69a9301f31
+size 180084
diff --git a/blog_data/images/blog_ee6bd9beb826_13.jpg b/blog_data/images/blog_ee6bd9beb826_13.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2dc583c405e9fbe571f49c65d697ecb4019dfa34
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_13.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:42d0771ea5692b66eab0b0e52465518a3ffd067ea35743913d099a59f8150b7c
+size 63306
diff --git a/blog_data/images/blog_ee6bd9beb826_14.jpg b/blog_data/images/blog_ee6bd9beb826_14.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..88900a5e0dfa3928611edc552ad28c547bf51bb5
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_14.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2c1d812f8447ff653e821566eba7845c4f1166e95d0769f07fd27a0372145604
+size 92837
diff --git a/blog_data/images/blog_ee6bd9beb826_15.jpg b/blog_data/images/blog_ee6bd9beb826_15.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..48b14651823d25b3d80bf5e143c26319305c8b24
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_15.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7602b7ec1a5734dbdee52690fe3b5def9419e335187e3d52190dae588371aa25
+size 127427
diff --git a/blog_data/images/blog_ee6bd9beb826_16.jpg b/blog_data/images/blog_ee6bd9beb826_16.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..12b6214ad73f6859942b1437dbcee7b83c103a3b
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_16.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a72187baaad5bfea250ebd83ac707456f0e54fe4d440cbdf7b8bda1793afa4cc
+size 123600
diff --git a/blog_data/images/blog_ee6bd9beb826_17.bin b/blog_data/images/blog_ee6bd9beb826_17.bin
new file mode 100644
index 0000000000000000000000000000000000000000..8604efaec6a66a162a63965fe9760a0aa00a3741
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_17.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:571582c114dbd7eeb171772cf17f95a678318d4fb501d634abdc094b51b8b8e5
+size 15617
diff --git a/blog_data/images/blog_ee6bd9beb826_18.jpg b/blog_data/images/blog_ee6bd9beb826_18.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..28a681c12d76db0e1493891c96f4672ef358b50e
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_18.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:966afea9d76ba88e68b159ca8c5ac2b6b063a51c500cc4cf312ace52bbad4322
+size 83037
diff --git a/blog_data/images/blog_ee6bd9beb826_19.jpg b/blog_data/images/blog_ee6bd9beb826_19.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b6df9559f1008dd3e5c7cf65c6110cfca2a69f1d
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_19.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0687aa269a4785d9fb2eb5f58abd8d05dfc05d0065e3e98837a7f6018a3dad90
+size 62714
diff --git a/blog_data/images/blog_ee6bd9beb826_2.jpg b/blog_data/images/blog_ee6bd9beb826_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d1e808290cfa8a3266ed637cd35f7ce5bb26fdf5
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7e0c5fb29c89bdb890a8e0c9bbb39e6225a70629a0ebb41d1f541d563656820f
+size 133112
diff --git a/blog_data/images/blog_ee6bd9beb826_20.jpg b/blog_data/images/blog_ee6bd9beb826_20.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6b35fd315bf5eb9de382d953f2cd6379801ae5cc
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_20.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8f6f8454312d964ea77ca032ac9e232f385f1d55ceee3c97c688afbb350bac4b
+size 81425
diff --git a/blog_data/images/blog_ee6bd9beb826_21.jpg b/blog_data/images/blog_ee6bd9beb826_21.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a98c09594b8af4174352067e227b9c16b655ab80
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_21.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fbc6c53007251468763bbfddc88e11cd25d39c2a600a544dfb887c1b517f96b8
+size 48838
diff --git a/blog_data/images/blog_ee6bd9beb826_22.jpg b/blog_data/images/blog_ee6bd9beb826_22.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8ad748939dae936d38cfb3bf9d149800b74da8c5
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_22.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0dc3a91700df09e000bdec4631db52b8fff231a8fbcade95e3ccaf9f11f7b6d7
+size 133258
diff --git a/blog_data/images/blog_ee6bd9beb826_23.jpg b/blog_data/images/blog_ee6bd9beb826_23.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3b1c420e9cc8585c7379080f301548cbb2a935ba
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_23.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:045158e99c6a7dd2a0da34da9e72cd7cc2c94c920e023ba0160bffd5a5c6c143
+size 117178
diff --git a/blog_data/images/blog_ee6bd9beb826_24.jpg b/blog_data/images/blog_ee6bd9beb826_24.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c8bb8371f3b1422bc2c8a9521a13fdb52f4b2062
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_24.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bdbb4d07208e5f51b5bb2dfce4b32a37e6349e5a89d623e18ec88ebea7432702
+size 125464
diff --git a/blog_data/images/blog_ee6bd9beb826_25.jpg b/blog_data/images/blog_ee6bd9beb826_25.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..930d9a997a5f34bada3f50bea7de7ac6230824b8
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_25.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5c08ab62d502a353f5f4a220b2a0f28fe464176a4533f38516a1281dca56c592
+size 64276
diff --git a/blog_data/images/blog_ee6bd9beb826_26.jpg b/blog_data/images/blog_ee6bd9beb826_26.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4b894eeea5b0f2a4deca6ad677af82ac988b4461
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_26.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d099d456dc2180e8afbf4ebcc49829c1c96f88dbd1bcc3fa664ff0870dcd99cf
+size 118121
diff --git a/blog_data/images/blog_ee6bd9beb826_27.jpg b/blog_data/images/blog_ee6bd9beb826_27.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aa5f523fb3b34bbae2ce42c7b44dabc9168f9e04
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_27.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9daa22a86dd27ecbc767918759a19e523bed9cd5bef9e68517b70d20d7cb4f24
+size 44855
diff --git a/blog_data/images/blog_ee6bd9beb826_28.jpg b/blog_data/images/blog_ee6bd9beb826_28.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fd1f455cd20b3a0ca3465c243bd02df184bf7625
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_28.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:121d8fd127377ade12a8a59a20712450350d10a1bee76cd9a7ad5cd06018dbe0
+size 201455
diff --git a/blog_data/images/blog_ee6bd9beb826_29.jpg b/blog_data/images/blog_ee6bd9beb826_29.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..73b1df17d2f3d96864b0b7c40f1b652c1b1cb882
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_29.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f607e5ec1b65241da651d99421f50c8909507b6064b62b38cfb5544324fe997c
+size 144746
diff --git a/blog_data/images/blog_ee6bd9beb826_3.jpg b/blog_data/images/blog_ee6bd9beb826_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..84f0d4f0f5913365526476735c6e092289c7f0e4
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c42de536e48a93f05ad99110b48e4745f928441b3f38731565e44c1eca1eee3
+size 123886
diff --git a/blog_data/images/blog_ee6bd9beb826_30.jpg b/blog_data/images/blog_ee6bd9beb826_30.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6d3138afe5027a219ab64123a08bc29e2b8a0b7a
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_30.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf848af870f6d5aa5e4d948ee088f7c6cd462671be9579a44d78df9476def511
+size 333787
diff --git a/blog_data/images/blog_ee6bd9beb826_31.jpg b/blog_data/images/blog_ee6bd9beb826_31.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..59eb46030547c60cf32bc44bba563a6415dfb213
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_31.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:307d1a9feadcb6b31cb52f50dff3004484e9839a675695c49add297ba0852e62
+size 148112
diff --git a/blog_data/images/blog_ee6bd9beb826_32.jpg b/blog_data/images/blog_ee6bd9beb826_32.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ed7916fd683823b7a163e0a2802a4b0df4abe90a
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_32.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:51b9303f85f04154cd1f193cb991c86b2516e8b91fd38efebba7e9d889fe2c5d
+size 113565
diff --git a/blog_data/images/blog_ee6bd9beb826_33.jpg b/blog_data/images/blog_ee6bd9beb826_33.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6fa991aaa278e06524ed3fa941b33244487afc36
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_33.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ce515a6e6a8cf74c933f801113a3882e18d817f1d8b297d9cdd8e7acd24f81ad
+size 166164
diff --git a/blog_data/images/blog_ee6bd9beb826_34.jpg b/blog_data/images/blog_ee6bd9beb826_34.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..52d1d21f40025fd137bfc73a0f068712c1bea4ae
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_34.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ac0dbf57e40fba0462407124672a52d854fb318c4e1ef0e6e39e4c6e7867c156
+size 122709
diff --git a/blog_data/images/blog_ee6bd9beb826_35.jpg b/blog_data/images/blog_ee6bd9beb826_35.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9f02d5c4919ec267e4ecc3c183951701f526cf13
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_35.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f79519349aac7c41d7127549e651c48b774e7bbf126048b34cbfa5cae904d3a2
+size 81081
diff --git a/blog_data/images/blog_ee6bd9beb826_36.bin b/blog_data/images/blog_ee6bd9beb826_36.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_36.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_ee6bd9beb826_37.bin b/blog_data/images/blog_ee6bd9beb826_37.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_37.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_ee6bd9beb826_4.jpg b/blog_data/images/blog_ee6bd9beb826_4.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2356ab574ab0035191afeb91cff9c2b87c25be8e
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_4.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c8d7fd6524d4fc34162ff77df3358507b737f70191817ea43a72fa56e8a47124
+size 81585
diff --git a/blog_data/images/blog_ee6bd9beb826_5.jpg b/blog_data/images/blog_ee6bd9beb826_5.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8169e6f9b679d54f11fd0833f9786786de29f41e
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_5.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:25efb25a90a6115496f3204ec9f90b0853468efa20a140f8f5b7e9a44994364d
+size 128766
diff --git a/blog_data/images/blog_ee6bd9beb826_6.jpg b/blog_data/images/blog_ee6bd9beb826_6.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..75a7d5dde6edc2c485c166d6665758b20c73df7e
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_6.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d85b737dc21c0a099a1ac38a71a745199fe2d49fe99b3f4a31e28069da7c798c
+size 239247
diff --git a/blog_data/images/blog_ee6bd9beb826_7.jpg b/blog_data/images/blog_ee6bd9beb826_7.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2f1ab8ad1129c28c80a831209d533262330740b3
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_7.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b7eb1b5e61ed8e796a9cc4599f0432b53131d0d266002e4e3b4b56b4030360fd
+size 211968
diff --git a/blog_data/images/blog_ee6bd9beb826_8.jpg b/blog_data/images/blog_ee6bd9beb826_8.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c64db8a93247239c36e6f6d0927d95bb8e8727bd
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_8.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:20bfb083ad51b5b3b8e8bb2399396eea7cf7742707e4dfae3be4f0041627c93d
+size 265795
diff --git a/blog_data/images/blog_ee6bd9beb826_9.jpg b/blog_data/images/blog_ee6bd9beb826_9.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..31c264834951bd4b1bcd1dca27a5293a4e31cbc2
--- /dev/null
+++ b/blog_data/images/blog_ee6bd9beb826_9.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f00f9e8f93f15ec4568c3873c7d9d27c9c31f18dc55c62d3a1d6783e8e863147
+size 72983
diff --git a/blog_data/images/blog_ef012822ce5f_0.bin b/blog_data/images/blog_ef012822ce5f_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..2c1620c356cd6fd5529415152d4e820c2d73374a
--- /dev/null
+++ b/blog_data/images/blog_ef012822ce5f_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:55617c675e69184a9a4b1fd48d4269540f9910f82b205a71398a61c4d3af0207
+size 33159
diff --git a/blog_data/images/blog_ef012822ce5f_1.bin b/blog_data/images/blog_ef012822ce5f_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..3a2b51a12004e09113b92ae351c1eff55d7bcfcc
--- /dev/null
+++ b/blog_data/images/blog_ef012822ce5f_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4f90bbe16d272b1aabd6d05b5f54694e60ba465ffd6e70a84d91812337ddaf91
+size 1126430
diff --git a/blog_data/images/blog_ef012822ce5f_10.bin b/blog_data/images/blog_ef012822ce5f_10.bin
new file mode 100644
index 0000000000000000000000000000000000000000..91ee02cb8aa3b0ba8a3b0b6307088bfc85b4f71a
--- /dev/null
+++ b/blog_data/images/blog_ef012822ce5f_10.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e094857cd51d4d1c509e357e4f02801b7a2d3353f2d962dabb3b9f45e1ce14e
+size 818209
diff --git a/blog_data/images/blog_ef012822ce5f_11.bin b/blog_data/images/blog_ef012822ce5f_11.bin
new file mode 100644
index 0000000000000000000000000000000000000000..2763b5882e3b6328c1e0b772b13349b6baa4048b
--- /dev/null
+++ b/blog_data/images/blog_ef012822ce5f_11.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a06de586e3d7dc69cc473e6bf01cfe637edcd5285486f285d5eb8e4143471c3a
+size 733655
diff --git a/blog_data/images/blog_ef012822ce5f_12.bin b/blog_data/images/blog_ef012822ce5f_12.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4b44c9051a6ddfcbc03ed6c51320cf0b4b213abb
--- /dev/null
+++ b/blog_data/images/blog_ef012822ce5f_12.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa68559e0d46f2437dab56e5c6dd14b3caf0c04563545a39ce275d00db8f8bf1
+size 2435599
diff --git a/blog_data/images/blog_ef012822ce5f_13.bin b/blog_data/images/blog_ef012822ce5f_13.bin
new file mode 100644
index 0000000000000000000000000000000000000000..14003cd63c95c5673de132c8ef30867abf0bed40
--- /dev/null
+++ b/blog_data/images/blog_ef012822ce5f_13.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8101ef37bbf0f6a1976e022f8f91a3f5b3a3dd633b837e243ff3f4ffbf78b275
+size 2937330
diff --git a/blog_data/images/blog_ef012822ce5f_14.bin b/blog_data/images/blog_ef012822ce5f_14.bin
new file mode 100644
index 0000000000000000000000000000000000000000..0755855a358fb054bc776fb3d1d2364a17c0d664
--- /dev/null
+++ b/blog_data/images/blog_ef012822ce5f_14.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f413f3a00aed02fb0a6258bbef5750acb463cb27886bd3baaabc0c0a145284e1
+size 2294760
diff --git a/blog_data/images/blog_ef012822ce5f_15.bin b/blog_data/images/blog_ef012822ce5f_15.bin
new file mode 100644
index 0000000000000000000000000000000000000000..f94fadb72423a14c0614a1985f31251e5a86f619
--- /dev/null
+++ b/blog_data/images/blog_ef012822ce5f_15.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9617123f555fa0e394c9a49aa3df5d6ddd05aaca542117ebfe56d28181ba4f06
+size 1827874
diff --git a/blog_data/images/blog_ef012822ce5f_2.bin b/blog_data/images/blog_ef012822ce5f_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..da135bd5bb48c8a0c0a24c109fea11282d93b11b
--- /dev/null
+++ b/blog_data/images/blog_ef012822ce5f_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:094e114a92c69d9f636f1c9b4d5b61e3254f5c41c1c364ef67304ca0d80ff5d6
+size 69894
diff --git a/blog_data/images/blog_ef012822ce5f_3.bin b/blog_data/images/blog_ef012822ce5f_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..f9d98c68cec0b9c5a690b28864fad0f9f4ca9622
--- /dev/null
+++ b/blog_data/images/blog_ef012822ce5f_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e4b476035bf22c381adc1e9a1d0cfc7aad1915f14401b57bd84ae6a5f1de3ab
+size 1720045
diff --git a/blog_data/images/blog_ef012822ce5f_4.bin b/blog_data/images/blog_ef012822ce5f_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..259b126ec658cf7dc81a053d7509b66be7326cfd
--- /dev/null
+++ b/blog_data/images/blog_ef012822ce5f_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:20a9fbb39a42d93f0d8889d971c8aa0c3c7a0c823cb012da7847b1d267026846
+size 66247
diff --git a/blog_data/images/blog_ef012822ce5f_5.bin b/blog_data/images/blog_ef012822ce5f_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..fed9fcf7dd2545c28053cb5b39d3d6da38f90c74
--- /dev/null
+++ b/blog_data/images/blog_ef012822ce5f_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d175616362a37316f1ca49bc5a607523e20793ed99926535af8c0e23aa1fd043
+size 1435027
diff --git a/blog_data/images/blog_ef012822ce5f_6.bin b/blog_data/images/blog_ef012822ce5f_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..8e9f60cafeb0075b002ca9ef6a445b43ec3520b8
--- /dev/null
+++ b/blog_data/images/blog_ef012822ce5f_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4ab20d2e525d83da11ecca56df948682bed98296a96138dd612aac284d5bdd54
+size 2672765
diff --git a/blog_data/images/blog_ef012822ce5f_7.bin b/blog_data/images/blog_ef012822ce5f_7.bin
new file mode 100644
index 0000000000000000000000000000000000000000..9c1402d0a8bd04c711d030c43c4f66d774ce4df7
--- /dev/null
+++ b/blog_data/images/blog_ef012822ce5f_7.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c362a1fbe2141697077b933ae5c52b972fa6d7275a8f44d6a151819ace09dad5
+size 1200972
diff --git a/blog_data/images/blog_ef012822ce5f_8.bin b/blog_data/images/blog_ef012822ce5f_8.bin
new file mode 100644
index 0000000000000000000000000000000000000000..b1b7172ca2aae1c7a503f677561bb662f2cd0e00
--- /dev/null
+++ b/blog_data/images/blog_ef012822ce5f_8.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d3b0e6d6332c70491004c077e81672fedfece6929c37f7820e362a609bc35b54
+size 719880
diff --git a/blog_data/images/blog_ef012822ce5f_9.bin b/blog_data/images/blog_ef012822ce5f_9.bin
new file mode 100644
index 0000000000000000000000000000000000000000..ddee06ea0066c374c8777497a3f54d1e9240a491
--- /dev/null
+++ b/blog_data/images/blog_ef012822ce5f_9.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:23e20c041072395b91c83edcc4cc8a2b35286d2ae915a2a83ba1b7eecfbc9874
+size 2176185
diff --git a/blog_data/images/blog_f02c247450c2_0.jpg b/blog_data/images/blog_f02c247450c2_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..240294cff1af43b33a7eed931d4055e8d2ace457
--- /dev/null
+++ b/blog_data/images/blog_f02c247450c2_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bb78794af7950ad3664cec81ff717081415896b18da379c1daf321d90ad8de13
+size 121584
diff --git a/blog_data/images/blog_f02c247450c2_1.jpg b/blog_data/images/blog_f02c247450c2_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..01af703399511f3db76140cfd7bfc19515acdfd3
--- /dev/null
+++ b/blog_data/images/blog_f02c247450c2_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3f07ba5610cffc7ee0c9a3543e7195c7dfb3a1bdc6a776dc614668df76140367
+size 128854
diff --git a/blog_data/images/blog_f02c247450c2_10.jpg b/blog_data/images/blog_f02c247450c2_10.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5589f1de679f1f4aec0295afa37afd613ff8752e
--- /dev/null
+++ b/blog_data/images/blog_f02c247450c2_10.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7c262fa40b8db10fada27f3dbff46d1bc4b3fda8e77af45780f9a02c00cef9ca
+size 179831
diff --git a/blog_data/images/blog_f02c247450c2_11.jpg b/blog_data/images/blog_f02c247450c2_11.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2b26bcb744e4a9f55fde965aeeb01b535ff969bd
--- /dev/null
+++ b/blog_data/images/blog_f02c247450c2_11.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:16cbcd8005263265a58f501459e90d4b6297a2511d41e62dc766decf5312e6ca
+size 252152
diff --git a/blog_data/images/blog_f02c247450c2_12.jpg b/blog_data/images/blog_f02c247450c2_12.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8b202c3949126ea588f434190942acf176f0ce9b
--- /dev/null
+++ b/blog_data/images/blog_f02c247450c2_12.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c64999a1a31a608c60d8513de72a9a8bb41908b5e71fdaa552c57fff4841d536
+size 25444
diff --git a/blog_data/images/blog_f02c247450c2_13.jpg b/blog_data/images/blog_f02c247450c2_13.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2c5f766bb9683111b1269b9d33dfece276571c4a
--- /dev/null
+++ b/blog_data/images/blog_f02c247450c2_13.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cbb724d27555571238795c4289fed5e9cd7a7e068e454692a47d516988835bce
+size 293411
diff --git a/blog_data/images/blog_f02c247450c2_14.jpg b/blog_data/images/blog_f02c247450c2_14.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bd495e69b4f49095db562ebf08bef368ffbea245
--- /dev/null
+++ b/blog_data/images/blog_f02c247450c2_14.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ab3d8e84e4f3be81c9edc8292f931b3d716ee80e497711fe77a61eaffceb1d2c
+size 24711
diff --git a/blog_data/images/blog_f02c247450c2_15.jpg b/blog_data/images/blog_f02c247450c2_15.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4a6cde61940b5546bdea151c3f52c1b4d22a2520
--- /dev/null
+++ b/blog_data/images/blog_f02c247450c2_15.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:43895c6df9fb6453636fd7f051677a8019551d022abc1fa2645a68ff6b78a70a
+size 22615
diff --git a/blog_data/images/blog_f02c247450c2_16.bin b/blog_data/images/blog_f02c247450c2_16.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_f02c247450c2_16.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_f02c247450c2_17.bin b/blog_data/images/blog_f02c247450c2_17.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_f02c247450c2_17.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_f02c247450c2_2.jpg b/blog_data/images/blog_f02c247450c2_2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..82e69967517b5c3224393bcc7b7a4c5778313411
--- /dev/null
+++ b/blog_data/images/blog_f02c247450c2_2.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0e379c779772d362a9f53924294f10f5f95ad27c8c6150fc7352062a561fdd98
+size 137118
diff --git a/blog_data/images/blog_f02c247450c2_3.jpg b/blog_data/images/blog_f02c247450c2_3.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9e10d91c02d879dccab283d717e3021ac2d8fb19
--- /dev/null
+++ b/blog_data/images/blog_f02c247450c2_3.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:18997c27b23b14c53677b9418189f8a9181c960537583c3aea4495a3867cce0d
+size 348840
diff --git a/blog_data/images/blog_f02c247450c2_4.jpg b/blog_data/images/blog_f02c247450c2_4.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..70ae86218dad1b2c3c8abb166586af5df44b65c0
--- /dev/null
+++ b/blog_data/images/blog_f02c247450c2_4.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:71ff49e8a1414a8960bf219d02cc67e58a63ab07831669ca1ec23ef5521c11f3
+size 78258
diff --git a/blog_data/images/blog_f02c247450c2_5.jpg b/blog_data/images/blog_f02c247450c2_5.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fdbe227028e86e7cee8b0c8f57b0c83b7c40fa0c
--- /dev/null
+++ b/blog_data/images/blog_f02c247450c2_5.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:97a5d91ac7a63f0fe6ecec281c68847b1e9b0fbff529e12734b2b56499b679b2
+size 50950
diff --git a/blog_data/images/blog_f02c247450c2_6.jpg b/blog_data/images/blog_f02c247450c2_6.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..048381c0b98ed133cec75e8ff57a64ea929d61bd
--- /dev/null
+++ b/blog_data/images/blog_f02c247450c2_6.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0556a14a5aff6e722d3e723ca64342f0743c38befe6588396d45b1df3cfe0c5d
+size 37970
diff --git a/blog_data/images/blog_f02c247450c2_7.jpg b/blog_data/images/blog_f02c247450c2_7.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ad97a176473f4078436181b86d45d03bca09fab6
--- /dev/null
+++ b/blog_data/images/blog_f02c247450c2_7.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d04030901971f35010ef254844db6ccf7aea21facec56bff79fa2ac9b26309d4
+size 519591
diff --git a/blog_data/images/blog_f02c247450c2_8.jpg b/blog_data/images/blog_f02c247450c2_8.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..518b9695ce9716747a8faa80857d1aa789d087bf
--- /dev/null
+++ b/blog_data/images/blog_f02c247450c2_8.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:04f262e81e87d5d2370813327620d0f069d86d5ae5d089bea32675d263636db7
+size 71814
diff --git a/blog_data/images/blog_f02c247450c2_9.jpg b/blog_data/images/blog_f02c247450c2_9.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8ff5016f3ae21716964e7c6c40af16af7144b28e
--- /dev/null
+++ b/blog_data/images/blog_f02c247450c2_9.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:18026e3ae6d2a7bed7739e225d922c37a91ed211e68bf295ce3e04140943269d
+size 71175
diff --git a/blog_data/images/blog_f0a7c817b8e1_0.jpg b/blog_data/images/blog_f0a7c817b8e1_0.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..701ed1f6f6abcc648cee05860b420998cd0978ff
--- /dev/null
+++ b/blog_data/images/blog_f0a7c817b8e1_0.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4bc1833b8b926c9566d8e19b8b67ef2483664bed50838c03b59ad5f5eb79a52b
+size 85263
diff --git a/blog_data/images/blog_f0a7c817b8e1_1.jpg b/blog_data/images/blog_f0a7c817b8e1_1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c7639711947d52b237c84ac79a1a864022502db0
--- /dev/null
+++ b/blog_data/images/blog_f0a7c817b8e1_1.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0afe4f0a0cc141bd255d26c65003546651f6f6a836ed453eb6d51406ff0875dc
+size 116757
diff --git a/blog_data/images/blog_f0a7c817b8e1_2.bin b/blog_data/images/blog_f0a7c817b8e1_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..4242f241518fd5478f401955e802c4c25ab83d4c
--- /dev/null
+++ b/blog_data/images/blog_f0a7c817b8e1_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592d3ea4c039e0883a21dca342781e15981f74a0021fec312c635a53c044cbe5
+size 1920
diff --git a/blog_data/images/blog_f0a7c817b8e1_3.bin b/blog_data/images/blog_f0a7c817b8e1_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..066dde16c2755a0007308e44799d946c0310ffec
--- /dev/null
+++ b/blog_data/images/blog_f0a7c817b8e1_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:422bbd9922a2af4cc9e8f8e425a6304075d84e5431e9eeb6eae559793f2b308b
+size 2842
diff --git a/blog_data/images/blog_f530d8ecac33_0.bin b/blog_data/images/blog_f530d8ecac33_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..afda9a697f3d6b6d5f030949f6a4f7d429c4df53
--- /dev/null
+++ b/blog_data/images/blog_f530d8ecac33_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5acf337baaf41617975c4f5ee5afb73d7a32991ba504fda27d08be3f63fea693
+size 93186
diff --git a/blog_data/images/blog_f530d8ecac33_1.bin b/blog_data/images/blog_f530d8ecac33_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..f2995b024caa0b5b23b60ba4f6dd5cfa68e5c708
--- /dev/null
+++ b/blog_data/images/blog_f530d8ecac33_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eb2dbd760554056bea26aedaa5a92b12514a9afbf4c383b8a1607be9a551b5cf
+size 140886
diff --git a/blog_data/images/blog_f530d8ecac33_2.bin b/blog_data/images/blog_f530d8ecac33_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..0b95fef9132d5b128eed93927d97872fd91316c2
--- /dev/null
+++ b/blog_data/images/blog_f530d8ecac33_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9acce35754d064e0e3435f6375e3b05d4fd75fbbea54d0522f9f7a8f8a4b2843
+size 92526
diff --git a/blog_data/images/blog_f530d8ecac33_3.bin b/blog_data/images/blog_f530d8ecac33_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..0308f8e57b42968baaa2a480c7a6f12e8ebb0ee9
--- /dev/null
+++ b/blog_data/images/blog_f530d8ecac33_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:64a3a965da52da339cedecab72c66c7491866ba2ead9b3a9a9de8b3f74fe682d
+size 42606
diff --git a/blog_data/images/blog_f530d8ecac33_4.bin b/blog_data/images/blog_f530d8ecac33_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..e8a2b5a5ad1c2fdf8f425394124d10b23b1f24ac
--- /dev/null
+++ b/blog_data/images/blog_f530d8ecac33_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b1b4bec64c52fa7b21a4900d57d4cd84de6efa454abd7e5640b5ad8113201038
+size 69742
diff --git a/blog_data/images/blog_f530d8ecac33_5.bin b/blog_data/images/blog_f530d8ecac33_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..90357570067b49118ad22aa72125aed1ed408c26
--- /dev/null
+++ b/blog_data/images/blog_f530d8ecac33_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:db2dc608243aa3bed5d4bce33bb8b2689937957ab5184375e09b3db6c45c325c
+size 91952
diff --git a/blog_data/images/blog_f530d8ecac33_6.bin b/blog_data/images/blog_f530d8ecac33_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..eaa1a3a010bfc944416ea275ee1219eae8dbde14
--- /dev/null
+++ b/blog_data/images/blog_f530d8ecac33_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7e9246ef665b9401a19c628b46e26a37d04a74a5122cd3d8871cbaa0af6d0052
+size 3396
diff --git a/blog_data/images/blog_fb9e2436f002_0.bin b/blog_data/images/blog_fb9e2436f002_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..9f7e3cf2b73ca41530c122be140608e8b85aa831
--- /dev/null
+++ b/blog_data/images/blog_fb9e2436f002_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3b4658d1a89e269c00cc931a0af21bae693cbd2c59f326fbfd54949bdb62fbc1
+size 15922
diff --git a/blog_data/images/blog_fb9e2436f002_1.bin b/blog_data/images/blog_fb9e2436f002_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..77571c0e6defdfe6547f85a4cf1b518733d1fa82
--- /dev/null
+++ b/blog_data/images/blog_fb9e2436f002_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:961ae043a684e6bb7a8fdc872f7209467c12e7bde1dff9944456e084b95df4b1
+size 127040
diff --git a/blog_data/images/blog_fb9e2436f002_2.bin b/blog_data/images/blog_fb9e2436f002_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..f3cf6c8319166970471ed52484cdec22d84b15e1
--- /dev/null
+++ b/blog_data/images/blog_fb9e2436f002_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c5f00a4978bef5652e69fafec77052e3419368d73836fc0bffa77cd1e6720e0a
+size 54566
diff --git a/blog_data/images/blog_fb9e2436f002_3.bin b/blog_data/images/blog_fb9e2436f002_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..ba63de9a5527d5439fef2e7a5bc1b881e43b8203
--- /dev/null
+++ b/blog_data/images/blog_fb9e2436f002_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ce6f1ddb80e983b9b4886931740b7422211c8a1b32c5176e22efdab9eee7e390
+size 58910
diff --git a/blog_data/images/blog_fed4248375dd_0.bin b/blog_data/images/blog_fed4248375dd_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..85576f2b926c9b78e9ef286818a59be483e311d1
--- /dev/null
+++ b/blog_data/images/blog_fed4248375dd_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:58c3ccd673371afcc953fd5c8eb976161d6e5f9d23c9e67b83da45cc12b759d6
+size 17128
diff --git a/blog_data/images/blog_fed4248375dd_1.bin b/blog_data/images/blog_fed4248375dd_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..7b2c73c4d2887b4ff23f8701ad29537591dfafea
--- /dev/null
+++ b/blog_data/images/blog_fed4248375dd_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a35702e3898bcfd0e088a04c0f19c4efefd5a27087bca10a848dd6fbf34531ae
+size 43552
diff --git a/blog_data/images/blog_fed4248375dd_2.bin b/blog_data/images/blog_fed4248375dd_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..232afc233f707dce454518ad156e804f3bf6900d
--- /dev/null
+++ b/blog_data/images/blog_fed4248375dd_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ec6704478c0f219c6b43dfc95d89fa7841d95168559c57afe714e558fb630040
+size 64454
diff --git a/blog_data/images/blog_fed4248375dd_3.bin b/blog_data/images/blog_fed4248375dd_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..3e5a73ee67ba9bdaba8a1e11185802f2b2e612b5
--- /dev/null
+++ b/blog_data/images/blog_fed4248375dd_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bc6922b094849e0c8d091c8ff0d95791ff39bd3a07909fd18f70d79ea4f56b7a
+size 56340
diff --git a/blog_data/images/blog_ffdea357f0f4_0.bin b/blog_data/images/blog_ffdea357f0f4_0.bin
new file mode 100644
index 0000000000000000000000000000000000000000..c987c84fc54dc622909c5d2d869684abf15ab3f9
--- /dev/null
+++ b/blog_data/images/blog_ffdea357f0f4_0.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7fdb0c49060a61c44e869b2e0212cdedb0c025f13da86bb0bb4faba37357239e
+size 270630
diff --git a/blog_data/images/blog_ffdea357f0f4_1.bin b/blog_data/images/blog_ffdea357f0f4_1.bin
new file mode 100644
index 0000000000000000000000000000000000000000..6777ffc8079663463a41484dfde88273381a9456
--- /dev/null
+++ b/blog_data/images/blog_ffdea357f0f4_1.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1d204af1dc1465c88b67c2515b4e65420972d7e66b5ba69bf0de7ce32f72623
+size 934565
diff --git a/blog_data/images/blog_ffdea357f0f4_10.bin b/blog_data/images/blog_ffdea357f0f4_10.bin
new file mode 100644
index 0000000000000000000000000000000000000000..c9f5d2196963adfe659cd947a0af0ab1da26b3cf
--- /dev/null
+++ b/blog_data/images/blog_ffdea357f0f4_10.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:740a7aa7af82db58c9ae52954d1f989af8fec0beb666feac498a3ea451ba5833
+size 521862
diff --git a/blog_data/images/blog_ffdea357f0f4_11.bin b/blog_data/images/blog_ffdea357f0f4_11.bin
new file mode 100644
index 0000000000000000000000000000000000000000..99274e4922d7ebfa467972da60e5f6a0705d9536
--- /dev/null
+++ b/blog_data/images/blog_ffdea357f0f4_11.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:57e2296cf32c5dd9fa5770bb51ff2c42115f698599639f891fd15efaa55697ab
+size 388148
diff --git a/blog_data/images/blog_ffdea357f0f4_12.bin b/blog_data/images/blog_ffdea357f0f4_12.bin
new file mode 100644
index 0000000000000000000000000000000000000000..e675383db2ebee7e3ec8d0259916b4aed20dd7e4
--- /dev/null
+++ b/blog_data/images/blog_ffdea357f0f4_12.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:632d6b039a8c74f452f3a06b79bc259e14be8c3e72656552d27296a60d79656a
+size 820522
diff --git a/blog_data/images/blog_ffdea357f0f4_13.bin b/blog_data/images/blog_ffdea357f0f4_13.bin
new file mode 100644
index 0000000000000000000000000000000000000000..784c591347b1b4391d9c853449d8f36304154510
--- /dev/null
+++ b/blog_data/images/blog_ffdea357f0f4_13.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e796f12464d177cdf300b41812fa338a376c0e815474502dd26c61c2da1a3ef6
+size 1552695
diff --git a/blog_data/images/blog_ffdea357f0f4_14.bin b/blog_data/images/blog_ffdea357f0f4_14.bin
new file mode 100644
index 0000000000000000000000000000000000000000..f22f154a4ce9e3a18f2cc6477572e1cf213e9a1a
--- /dev/null
+++ b/blog_data/images/blog_ffdea357f0f4_14.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7640b403bda53c5d5bd91cbbf078a166f93bf232b5eb20fc561efd947a142672
+size 1341085
diff --git a/blog_data/images/blog_ffdea357f0f4_15.bin b/blog_data/images/blog_ffdea357f0f4_15.bin
new file mode 100644
index 0000000000000000000000000000000000000000..c9927740d6fa97438c5942538711d8640a217fe9
--- /dev/null
+++ b/blog_data/images/blog_ffdea357f0f4_15.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e4ea1bd7d6cbdd5df40e88dc85dea99e7cea74c47a723e79abb1cbfbc5c97324
+size 530579
diff --git a/blog_data/images/blog_ffdea357f0f4_16.bin b/blog_data/images/blog_ffdea357f0f4_16.bin
new file mode 100644
index 0000000000000000000000000000000000000000..03d5f0d105bdab5aad882310752adca72efd8e32
--- /dev/null
+++ b/blog_data/images/blog_ffdea357f0f4_16.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b7f20e191f72287130acb86c1afc316f9a2181022becfd8d5e46c17c64025bd4
+size 926735
diff --git a/blog_data/images/blog_ffdea357f0f4_17.bin b/blog_data/images/blog_ffdea357f0f4_17.bin
new file mode 100644
index 0000000000000000000000000000000000000000..35c95517799fe6d8b23f00683f399d7c8beb0ab3
--- /dev/null
+++ b/blog_data/images/blog_ffdea357f0f4_17.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:64c3f7bd721d7e6d5cadeff399a206931bf23b58f6b9aee6f376f6a09862562c
+size 412152
diff --git a/blog_data/images/blog_ffdea357f0f4_18.bin b/blog_data/images/blog_ffdea357f0f4_18.bin
new file mode 100644
index 0000000000000000000000000000000000000000..7db69c5c519030fc7f72b8d7f7f9ce0f41eaebbf
--- /dev/null
+++ b/blog_data/images/blog_ffdea357f0f4_18.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e1b520bffebcd3164fbf1dd9157685f6e2fda3e47995a92d3643d867db3e8e7
+size 423115
diff --git a/blog_data/images/blog_ffdea357f0f4_2.bin b/blog_data/images/blog_ffdea357f0f4_2.bin
new file mode 100644
index 0000000000000000000000000000000000000000..20813b0daca559a471965a61c8567218f4ff08b7
--- /dev/null
+++ b/blog_data/images/blog_ffdea357f0f4_2.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5339a7700d94ec496c6ed9bd1f8f02742e3141c04dfa754b91fc33a20e805850
+size 136988
diff --git a/blog_data/images/blog_ffdea357f0f4_3.bin b/blog_data/images/blog_ffdea357f0f4_3.bin
new file mode 100644
index 0000000000000000000000000000000000000000..7087318ce11f161626b19a88360fa464123dfaef
--- /dev/null
+++ b/blog_data/images/blog_ffdea357f0f4_3.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7e3acc9fe5d549a1b12842003ca81c8e048a647b572e1be878ef272834696c6f
+size 679174
diff --git a/blog_data/images/blog_ffdea357f0f4_4.bin b/blog_data/images/blog_ffdea357f0f4_4.bin
new file mode 100644
index 0000000000000000000000000000000000000000..9b6f0dc620d76e4419f96fba8de61329675b1c15
--- /dev/null
+++ b/blog_data/images/blog_ffdea357f0f4_4.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8e81f24fbea8ee6b0f90e6ce45cb168f31c2eb743577ae83d16432c0ff7879fd
+size 4240136
diff --git a/blog_data/images/blog_ffdea357f0f4_5.bin b/blog_data/images/blog_ffdea357f0f4_5.bin
new file mode 100644
index 0000000000000000000000000000000000000000..a4a33f11574bbf965b9f61c110e15b9bf3126948
--- /dev/null
+++ b/blog_data/images/blog_ffdea357f0f4_5.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0d4db3486fa2cc305c5ad2668aa254e4493a24b09f171cd6130474c551b27c85
+size 4519129
diff --git a/blog_data/images/blog_ffdea357f0f4_6.bin b/blog_data/images/blog_ffdea357f0f4_6.bin
new file mode 100644
index 0000000000000000000000000000000000000000..3c84e29b9421e2243db547e8bebc448927bf4870
--- /dev/null
+++ b/blog_data/images/blog_ffdea357f0f4_6.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:75e76fdb598887264c4253f63562f9e458ee67b2a9473c6cbc9a9179aea8088a
+size 2939937
diff --git a/blog_data/images/blog_ffdea357f0f4_7.bin b/blog_data/images/blog_ffdea357f0f4_7.bin
new file mode 100644
index 0000000000000000000000000000000000000000..707cc4c4a9e7d85114a8de376451043c6bed19c1
--- /dev/null
+++ b/blog_data/images/blog_ffdea357f0f4_7.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:85a949bbf8a6cbcc52912fd6b4492578169493b0c11c3da0cd8c90f2e8a7eb05
+size 197215
diff --git a/blog_data/images/blog_ffdea357f0f4_8.bin b/blog_data/images/blog_ffdea357f0f4_8.bin
new file mode 100644
index 0000000000000000000000000000000000000000..d18b3e713604c066c48e2ffb0200a32d9f1dfb71
--- /dev/null
+++ b/blog_data/images/blog_ffdea357f0f4_8.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d8d2ff2c1373dd79281df6b236f1a3811c8ffef3d370eeb9045eb1bf379bccea
+size 46760
diff --git a/blog_data/images/blog_ffdea357f0f4_9.bin b/blog_data/images/blog_ffdea357f0f4_9.bin
new file mode 100644
index 0000000000000000000000000000000000000000..27f73279504ded3a2680b6e8a2cde5a92195151e
--- /dev/null
+++ b/blog_data/images/blog_ffdea357f0f4_9.bin
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5a8e33148740ad54154226908881bf3a2a2080e3af0720b645f1829275df967d
+size 374867