This report shows only current, aggregate counts from three named official food-inspection publishers whose adapters preserve a narrow pest-related field. It helps a commercial pest-control team evaluate a source boundary before monitoring facilities it already serves or is authorized to review.
Named official publisher
literal publisher description “Controlling Pests”
6publisher rows in the most recent 14-day window
Latest retained inspection date in that window: 2026-09-16.
Last successful collection: 2026-09-18.
Cincinnati Health Department
Open official publisher ↗
Named official publisher
literal publisher FoodCodeText containing “pest,” “rodent,” or “insect”
This source does not currently meet the report’s fresh-collection and retained-row gate. Review the official publisher directly; ViolationNet will show a count only after the gate is met.
Minneapolis Health Department
Open official publisher ↗
Named official publisher
publisher rodents-and-insects field “Not In Compliance” (kept separate from inspection status)
41publisher rows in the most recent 14-day window
Latest retained inspection date in that window: 2026-09-16.
Last successful collection: 2026-09-18.
Montgomery County Department of Health and Human Services
Open official publisher ↗
Named official publisher
literal publisher text containing “vermin”
This source does not currently meet the report’s fresh-collection and retained-row gate. Review the official publisher directly; ViolationNet will show a count only after the gate is met.
San Francisco Department of Public Health
Open official publisher ↗
Compare source fields, not normalized scores. Cincinnati is limited to a literal publisher description, Montgomery County preserves its rodents-and-insects field separately from the inspection status, and San Francisco is limited to publisher text containing “vermin.” Counts are publisher rows rather than unique facilities, so a source’s native record structure stays visible. Confirm consequential information with the issuing agency and responsible facility team.
Check one selected account before setup. The private source receipt lets a team verify the named publisher against a facility it already serves or is authorized to review; account details are not stored by that check. A team can then choose whether to begin setup for selected accounts and keep the publisher and inspection date visible. This report does not create a prospect queue or change any monitoring rule.