Paste raw digits, a formatted phone number, an area code, an NPA-NXX block, or a short code. US and Canada phone lookups route automatically, and international iMessage checks are available separately.
Server-rendered context for this exact phone page based on public records, reports, search interest, and routing data already stored on phone.gd.
202-558-2010 does not currently have a confirmed public business label on phone.gd, but it remains an active research target because complaint records, anonymous reports, or verified on-site searches continue to surface it.
Current page signals include 11 public complaint records.
Carrier or assignee data points to PAETEC ITEL, LLC and the rate center is WSHNGTNZN1 (WASHINGTON ZONE 1, DC).
The rows below combine cached caller-intelligence data, NANPA assignment records, public business matches, and phone.gd lookup context.
| Label | Value |
|---|---|
| Input Number | 202-558-2010 |
| Phone Number | +12025582010 |
| National Format | (202) 558-2010 |
| Country Code | US |
| Caller Name | No public caller label found. |
| Caller Type | |
| Carrier Name | PAETEC ITEL, LLC |
| Phone Type | |
| Apple iMessage Status | Not Registered |
| Raw Number | 2025582010 |
| Basic Format | 202-558-2010 |
| NPA (Area Code) | 202 |
| NXX | 558 |
| Rate Center | WSHNGTNZN1 |
| Location | WASHINGTON ZONE 1, DC |
| OCN (Carrier Number) | 829J |
| Call Type | Unknown Type |
| Number Assignment | Assigned |
| Search |
|
| state | DC |
| ocn | 6117 |
| company | LEVEL 3 COMMUNICATIONS, LLC - DC |
| rate_center | WSHNGTNZN1 |
| Location | WASHINGTON ZONE 1, DC |
| use_type | AS |
| pooled_code | Y |
| in_service | Yes |
| region | MA |
| state | DC |
| status | AS |
| rate_center | WSHNGTNZN1 |
| Location | WASHINGTON ZONE 1, DC |
| block_effective_date | 08/25/2004 |
| assigned_to | PAETEC ITEL, LLC |
| ocn | 829J |
| date_assigned | 08/13/2004 |
| region | MA |
| state | DC |
| status | AS |
| rate_center | WSHNGTNZN1 |
| Location | WASHINGTON ZONE 1, DC |
| block_effective_date | 08/25/2004 |
| assigned_to | PAETEC ITEL, LLC |
| ocn | 829J |
| date_assigned | 08/13/2004 |
| Bold | 𝟐𝟎𝟐-𝟓𝟓𝟖-𝟐𝟎𝟏𝟎 [click to copy] |
| Full-Width | 202-558-2010 [click to copy] |
| Superscript | ²⁰²-⁵⁵⁸-²⁰¹⁰ [click to copy] |
| Subscript | ₂₀₂-₅₅₈-₂₀₁₀ [click to copy] |
| Enclosed Alphanumerics | ②⓪②-⑤⑤⑧-②⓪①⓪ [click to copy] |
| Mathematical Bold | 𝟮𝟬𝟮-𝟱𝟱𝟴-𝟮𝟬𝟭𝟬 [click to copy] |
| Mathematical Italic | 𝟤𝟢𝟤-𝟧𝟧𝟪-𝟤𝟢𝟣𝟢 [click to copy] |
| Mathematical Sans-Serif | 𝟸𝟶𝟸-𝟻𝟻𝟾-𝟸𝟶𝟷𝟶 [click to copy] |
| Emoji | 2️⃣0️⃣2️⃣-5️⃣5️⃣8️⃣-2️⃣0️⃣1️⃣0️⃣ [click to copy] |
| Spelled Out | two zero two - five five eight - two zero one zero [click to copy] |
Using these number formats when publishing your phone number online can help reduce spam calls/texts by making it harder for scammers to copy your number
Submit an anonymous report
Choose the report type that best matches this number, then optionally add a short note about what happened. Your city and state may be shown publicly, but your IP address is not displayed on the page.
Report a spam or fraud caller
Answer a few quick questions and this page will point you to the right official complaint flow, plus carrier-specific reporting options where available.
Step 1
What happened?
Choose the option that best matches this phone number.
Step 2
How did it reach you?
The FCC and carrier advice changes slightly for calls versus texts.
Step 3
Did they ask for money or sensitive information?
This helps decide whether the FTC should be part of the next step.
Step 4
Which carrier do you use?
Carrier tools help get the number flagged or blocked inside that network.
Latest community reports for 202-558-2010
Anonymous User from Philadelphia, PA
March 21, 2017 at 3:41 PM
Anonymous User from Philadelphia, PA
March 21, 2017 at 3:39 PM
Anonymous User from Arlington, MA
March 21, 2017 at 3:35 PM
Anonymous User from Colorado Springs, CO
March 20, 2017 at 11:01 PM
Anonymous User from Hampstead, NH
March 20, 2017 at 7:59 PM
Anonymous User from Groton, MA
March 20, 2017 at 3:08 PM
Anonymous User from Golden, CO
March 17, 2017 at 6:42 PM