202 is a real DC code
Area code 202 serves Washington, District of Columbia, as part of the North American Numbering Plan. It is a geographic assignment for the District, unlike toll-free prefixes such as 855.
NANPA planning materials and the DC Public Service Commission describe 202 as the long-standing District NPA. Local residents, local businesses, and many federal and District offices have used 202 numbers for decades. That history is why a 202 display can feel "official" to people outside the capital.
Geographic status does not mean every call that flashes 202 is local or honest. It only means the three-digit NPA is a real assignment, not a reserved spam label.
771 overlays the same District geography
202 is no longer the only District area code. After number-exhaustion planning, the Public Service Commission of the District of Columbia approved an all-services overlay. The new 771 NPA serves the same geographic area as 202.
NANPA Planning Letter PL-547 set the industry timeline: mandatory 10-digit dialing in the 202/771 area began 12:01 a.m. ET on October 9, 2021, and 771 central-office codes could be activated as early as November 9, 2021. Existing 202 numbers stayed the same; new lines may receive 771.
DCPSC consumer pages state the same point in plain language: the District uses both 202 and 771 through an overlay. If you only police "202," you will miss legitimate 771 callers and still see spoofed 202 displays.
Decision rule: treat 202 and 771 as the same DC geography for "is this a real capital-region code?" questions. Treat neither display as proof of who is calling.
Why 202 shows up in spam complaints
Robocallers and spoofing tools can place almost any NPA on Caller ID. Neighbor spoofing and authority spoofing both apply: a 202 display can be chosen to imply a government or capital-region source even when the call originates elsewhere.
The FCC consumer guide on spoofing and Caller ID is the right frame: the displayed number is not a reliable location or brand check. Our scam area codes page covers the same pattern across many NPAs.
Political fundraising, fake "census" callbacks, warrant threats, and bank-lock scripts often pick codes that sound powerful. 202 is popular for that reason. So are some toll-free prefixes. The pattern is reputation abuse, not a secret FCC spam blacklist of 202.
| You see | Safer move |
|---|---|
| Cold call claiming IRS, SSA, or court action from a 202 number | Hang up; use the number on the official agency site |
| Political survey or donation ask with 202 Caller ID | Optional to answer; never give card numbers to unsolicited dialers |
| Callback request to a different 202, 771, or toll-free line | Verify the destination independently before dialing |
| Text that says a DC agency locked your account | Do not tap links; open the agency site yourself in a fresh browser |
Display versus dial-back risk
Separate two questions. First: does the screen show a plausible DC code? Second: is it safe to call back the number on the screen or the number a stranger reads aloud?
A spoofed inbound display can be 202 while the callback the scammer wants is a different 202, a 771, a toll-free line, or an international-looking string. Calling that callback can connect you to the fraud desk even if the first flash looked "local to DC."
Government and bank contact pages publish numbers you can trust better than a cold call. Use those published numbers. Do not trust a number dictated under urgency.
If you already answered and shared little, hang up. If you shared account data or remote-access codes, contact the real institution on a published channel and consider a fraud alert with the major credit bureaus when money or identity data was involved.
202 versus toll-free complaints
Toll-free codes such as 800 and 855 are non-geographic. They are sold and routed differently from District landline and mobile assignments. A 202 or 771 number is tied to the DC overlay plan; a toll-free number is not.
Scammers use both. The cleanup habit is identical: ignore urgency, refuse gift cards and wire instructions, and verify on a channel you open yourself. For toll-free legitimacy questions, see is 855 legit.
Blocking an entire NPA is a blunt tool. It cuts real DC callers along with junk. Prefer carrier spam folders, silence unknown callers, and number-specific blocks after a bad contact.
People also confuse "I keep getting 202 spam" with "202 must be illegitimate." Volume of complaint screenshots tracks spoof fashion, not NANPA assignment rules. Assignment truth and spam volume are separate facts.
Practical filters that do not depend on the NPA
Ask whether the caller demanded secrecy, immediate payment, or remote control of your device. Those asks fail a legitimacy test no matter which three digits appear.
Ask whether you can pause and call back using a number from an official website you typed yourself. If the caller forbids that pause, treat the call as hostile.
Ask whether the story requires you to move money to "protect" it. Real agencies and banks do not collect taxes or unlock accounts with gift cards, crypto ATMs, or courier cash pickups.
Keep STIR/SHAKEN and carrier spam labels in perspective. An unlabeled or "spam likely" tag is a hint, not a courtroom finding. A clean label is also not a guarantor. Your pitch checklist still matters.
What to do next
Silence unknown callers if that is your default, then return only to numbers you look up yourself.
Enable carrier spam filtering and report illegal robocalls through FTC and FCC consumer complaint tools when the pitch is fraudulent.
If you need the numbering basics (overlays, NPAs, and why displays lie); see how area codes work.
Keep one written rule: "202/771 means DC geography is possible; it never means the caller is verified."