PolicySource: HousingWire
HW: FL + NE AGs sue First Street — Risk Factor still on Zillow, Redfin, Realtor.com
Original headline: “Climate risk scores could be hurting home sales, two states allege in lawsuits” — HousingWire, Oct 27, 2026
HousingWire’s Brooklee Han reports (Oct. 27, 2026) that climate-risk analytics firm First Street faces AG lawsuits in Florida and Nebraska over property-level Risk Factor grades for flood, wildfire, wind, heat and air quality that appear beside listings on portals. Florida AG James Uthmeier’s Polk County suit under FDUTPA alleges scores are presented as accurate/scientific while models are uncertain and can contradict FEMA classifications, seeks injunctive relief, consumer redress, disgorgement and civil penalties of $10,000–$15,000 per violation, and notes homeowners lack a path to correct disputed scores; Nebraska AG Mike Hilgers filed a similar suit about two months earlier alleging inaccurate parcel predictions depressed prices and stalled sales. HousingWire says as of Tuesday morning Zillow, Redfin and Realtor.com still displayed First Street data or links (Zillow removed some after a December 2025 CRMLS accuracy challenge; Redfin’s Daryl Fairweather previously defended keeping the scores), First Street and the portals did not immediately comment, and a June 2025 NY homeowner suit against First Street and Zillow remains pending.
Our take (opinion & analysis, not reporting)
For US agents: this HousingWire write-up adds Nebraska’s earlier suit and a Tuesday check that Zillow/Redfin/Realtor.com still surface First Street scores — so keep your buyer/seller scripts ready even if you already saw Florida’s Oct. 23 AG filing. When a portal Risk Factor conflicts with FEMA/NFIP or local disclosure, document both and let the client’s insurer/attorney weigh in rather than arguing the model on a showing. Do not invent portal-removal timelines beyond what HW reported (some Zillow removals after CRMLS in Dec. 2025; still showing as of the Oct. 27 check).
Online discussion: no notable public discussion found yet (checked Oct 28, 2026).