17625 12th St NW Washington DC 20005
- Latitude
- 38.90496
- Longitude
- -77.02788
- ZCTA centroid
- 38.9044, -77.0316
- Time zone
- America/New_York
Coordinates fall inside the ZIP boundary. Street numbers are drawn from ranges with no delivery point. The city name shown is the official place boundary for this point — the USPS last-line city source is not yet live for every ZIP.
District of Columbia Address Data
Every figure below is measured from the underlying dataset, not estimated — the same data the generator above draws from. Need more than a handful of records? Bulk export returns up to 10,000 rows in one request, with no account required.
ZIP codes in the published dataset
Counties represented
DC address format
USPS Publication 28 last line: Washington, DC 20319
Telephone area codes
Bounding box / centroid
Top real street names
- 14th St NW112 segments
- 16th St NW94 segments
- 13th St NW89 segments
- Georgia Ave NW78 segments
- 5th St NW73 segments
- 9th St NW69 segments
Street-suffix distribution
- NW6093 streets
- NE2636 streets
- SE1961 streets
- SW437 streets
- Ave72 streets
- Ct6 streets
Population (counties represented)
Sum of Census county population for every county represented in the published dataset.
District of Columbia cities in the published dataset
District of Columbia has 1 District of Columbia cities with their own generator page and 0 more listed below with too few published data points yet for a page of their own.
| City | ZIP codes | Records | Own page |
|---|---|---|---|
| Washington | 27 | 61 | Yes |
Frequently Asked Questions
Is it legal to use a random address generator for District of Columbia addresses?
Yes, for testing and development — using a random address generator becomes illegal only when the output is used to deceive a real system, such as a government form or a bank. See the full legal guide for the specific statute, 18 U.S.C. § 1342, and what it actually covers.
Will these District of Columbia addresses pass address validation?
They pass format and parser validation, because every District of Columbia record is postal-format-valid per USPS Publication 28. They deliberately fail Delivery Point Validation, because the street number is drawn from a range with no registered delivery point — both are intentional.
Could a generated District of Columbia address belong to a real person?
No. Every District of Columbia record is built for geographic coherence from one point on a real street, with a street number chosen outside any range assigned to a real delivery point, so the address does not describe a real resident. The full method is on the methodology page.
Do the ZIP codes, counties and area codes across District of Columbia always agree with real geography?
Yes. District of Columbia has 27 usable ZIP codes across 1 counties in the dataset, and every generated record's county and area code are derived from the same point as its ZIP code, checked on every build. See the validation harness for the exact method.
Can I generate District of Columbia addresses in bulk?
Yes — up to 10,000 rows at once, in CSV, JSON, NDJSON, or SQL, with no account required. Add ?seed= to get the same District of Columbia records back on every run, which is useful for a CI fixture.
What is the difference between a fake address and a random address generator?
A fake address is meant to deceive a real recipient. A random address generator like Fake Addresses produces postal-format-valid, non-deliverable District of Columbia test data with no real recipient and no deception intended — the full comparison is in this guide.
More District of Columbia test data
Prohibited uses of Fake Addresses test dataProhibited use
Do not use these addresses to deceive anyone. Do not use them on government forms, tax filings, financial or KYC applications, school-enrolment records, voter registration, insurance claims, shipping labels, or anywhere a truthful address is legally required. In the US, using a fictitious address to defraud through the mail is a federal crime under 18 U.S.C. § 1342.