1. Explore the map
Pick a state, then tap any district on the map — or choose a district from the list (the list works with a keyboard or screen reader, no map needed).
Selected districtDistrict boundary
2. Search by town
Type a town or city name and pick your state. If a town crosses district lines, every district it touches is shown — never just one.
At least 2 letters. Your search never leaves this page.
3. Search by ZIP code
Enter a 5-digit ZIP code. If it crosses district lines, every district it touches is shown.
ZIP codes are not addresses — a ZIP alone can’t identify your home. Your search never leaves this page.
About our district data
Sources and vintage
District shapes come from the U.S. Census Bureau’s TIGER/Line 2026 files for the 120th Congress — the districts in use for the November 3, 2026 general election. Where a Census file disagreed with a state’s official 2026 map, the state’s official map governs: that rule applied to Missouri, which uses its official 2022 map because courts blocked the 2025 redraw for November 2026.
Town lookups use Census 2026 place and municipality shapes (cities, towns, townships, boroughs, villages) overlaid on the district lines; ZIP lookups use Census 2026 ZIP-code areas (ZCTAs). A town or ZIP that touches more than one district lists every district it touches.
Verification
All 50 states were verified for the November 3, 2026 election on October 8, 2026 — including the nine states that redrew their maps in 2025–26. If a state’s boundaries were ever unverified, this page would say so plainly instead of showing you its map. The boundary source for each state is shown with every result.
What this covers — and what it doesn’t
This lookup covers U.S. House districts only (all 435). It is not a full ballot: Senate, governor, state legislature, and local races are not included.
Privacy: what this page does and doesn’t do
- No home address is ever asked for. Town and ZIP searches are approximate lookups, not addresses.
- Your device’s location is never requested (no geolocation API).
- What you type stays on your device: town and ZIP searches run entirely in your browser. This page sets no cookies, keeps no record of your searches, and runs no analytics of its own.
- Loading this page fetches ordinary files from polivion.com (listed below). Like any website, the hosting server may keep standard server logs noting that a file was requested — those logs don’t contain your search terms, because your searches never leave your browser.
Every network request this page makes
Everything except the map tiles comes from polivion.com:
- This page itself, plus lib/leaflet/leaflet.js and lib/leaflet/leaflet.css (the map software, hosted by us — no third-party code).
- data/district_index.json — district names and race-page links (31 KB, loaded on open).
- data/verification.json — per-state boundary source and verification date (21 KB, loaded on open).
- data/candidates.json — the 2026 House nominees per district, taken from our own race pages (83 KB, loaded on open).
- data/geo/states.geojson — state outlines for the starting map (116 KB, loaded when the map starts).
- data/geo/<STATE>.geojson — district shapes for the state you pick (largest: California, 201 KB; only the states you look at are loaded).
- data/places/<STATE>.json — town-to-district table for the state you search (only loaded when you use town search).
- data/zip2dist.json — ZIP-to-district table (817 KB; loaded once, only if you use ZIP search).
The only outside request: map tiles from *.basemaps.cartocdn.com (CartoDB’s Positron basemap, which draws the town and road labels). To be honest about it: a tile server sees your IP address and which map tiles your browser loads, which roughly reveals the area you’re viewing. It does not see your searches, and we send it nothing ourselves.
See every race, every nominee
All 470 midterm races, with the money behind each candidate.
View all midterm elections →← Back to home