Part 107 UAS pilot reported flying in airspace with UAS restrictions near a Class B airport.

Narrative

On Day 0; at approximately XA:00; I was operating a small UAS as a contractor performing utility inspection work in Hillside; Illinois. Prior to flight; I checked airspace resources and did not see an active TFR in the area. The flight was conducted under the assumption that LAANC authorization and normal controlled airspace procedures were sufficient.After the flight; I became aware that there was a broader federal restriction in effect for the Chicago area airspace; which was not immediately visible in the pre-flight airspace tools I reviewed.Chain of Events:Problem arose due to reliance on standard airspace check tools that did not clearly display the ongoing Department of Homeland Security (DHS) restriction.Discovered only after reviewing updated notices post-flight.Corrective actions: I will add additional cross-checks of FAA TFR listings and DHS/NOTAM announcements in addition to LAANC and app-based airspace maps before any future operations.Human Performance Considerations:Contributing factor: misinterpretation/assumption that absence of TFR in the app equaled no restrictions.Judgment/perception issue: relying on a single tool without confirming through FAA's official TFR database.Corrective action: expanded preflight checklist to include direct FAA TFR website review to prevent recurrence.