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.
212-384-1000 is most strongly associated on phone.gd with Federal Bureau of Investigation New York Field Office in NEW YORK CITY ZONE 01, NY.
Current page signals include 45 public complaint records.
Carrier or assignee data points to VERIZON NEW YORK, INC. and the rate center is NWYRCYZN01 (NEW YORK CITY ZONE 01, NY).
The rows below combine cached caller-intelligence data, NANPA assignment records, public business matches, and phone.gd lookup context.
| Label | Value |
|---|---|
| Input Number | 212-384-1000 |
| Phone Number | +12123841000 |
| National Format | (212) 384-1000 |
| Country Code | US |
| Caller Name | FEDERAL BUREAU OF INVESTIGATION NEW YORK FIELD OFFICE |
| Caller Type | |
| Carrier Name | VERIZON NEW YORK, INC. |
| Phone Type | |
| Apple iMessage Status | Not Registered |
| Raw Number | 2123841000 |
| Basic Format | 212-384-1000 |
| NPA (Area Code) | 212 |
| NXX | 384 |
| Rate Center | NWYRCYZN01 |
| Location | NEW YORK CITY ZONE 01, NY |
| SMS/MMS Email Gateways | 2123841000@vtext.com 2123841000@vtext.com SMS/MMS gateways may be invalid (i.e. the number has been ported or purchased by another carrier) |
| OCN (Carrier Number) | 9104 |
| Call Type | Unknown Type |
| Number Assignment | Assigned |
| Search |
 |
These stored listings match the exact phone number, which helps reinforce any named caller identity shown above.
| Source | Name | Detail |
|---|---|---|
| OSM business listing | Federal Bureau of Investigation New York Field Office | 26 Federal Plaza New York 10278 US |
| state | NY |
| ocn | 9104 |
| company | VERIZON NEW YORK, INC. |
| rate_center | NWYRCYZN01 |
| Location | NEW YORK CITY ZONE 01, NY |
| use_type | AS |
| pooled_code | N |
| in_service | Yes |
| Bold | 𝟐𝟏𝟐-𝟑𝟖𝟒-𝟏𝟎𝟎𝟎 [click to copy] |
| Full-Width | ２１２-３８４-１０００ [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️⃣1️⃣2️⃣-3️⃣8️⃣4️⃣-1️⃣0️⃣0️⃣0️⃣ [click to copy] |
| Spelled Out | two one two - three eight four - one zero zero 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 212-384-1000
Anonymous User from Elkhorn, Nebraska
May 14, 2026 at 6:27 PM
Anonymous User from University Place, Washington
May 8, 2026 at 6:33 PM
Anonymous User from Conway, South Carolina
April 22, 2026 at 2:41 PM
Anonymous User from Conway, South Carolina
April 16, 2026 at 5:20 PM
Anonymous User from Temecula, California
April 10, 2026 at 10:47 AM
Anonymous User from Union City, California
March 20, 2026 at 1:50 PM
Anonymous User from Lewes, Delaware
February 14, 2026 at 12:21 PM
Anonymous User from Twin Falls, Idaho
February 12, 2026 at 1:33 PM
Anonymous User from Lyman, South Carolina
February 4, 2026 at 3:00 PM
Anonymous User from Milford, Pennsylvania
January 16, 2026 at 1:48 PM
Anonymous User from North Las Vegas, Nevada
January 9, 2026 at 3:00 PM
Anonymous User from Huntington Beach, California
January 6, 2026 at 2:43 PM
Anonymous User from Frisco, Texas
January 5, 2026 at 5:15 PM
Anonymous User from Frisco, New York
January 4, 2026 at 9:22 PM
Anonymous User from Frisco, New York
January 4, 2026 at 9:22 PM
Anonymous User from Frisco, New York
January 4, 2026 at 9:21 PM
Anonymous User from Frisco, Texas
January 4, 2026 at 9:20 PM
Anonymous User from Lafayette, New Jersey
January 3, 2026 at 5:23 PM
Anonymous User from Kaysville, UT
January 2, 2026 at 6:42 PM
Anonymous User from King Of Prussia, Pennsylvania
January 2, 2026 at 4:36 PM
Anonymous User from Orem, Utah
January 1, 2026 at 10:07 PM
Anonymous User from Midland, Texas
December 31, 2025 at 5:29 PM
Anonymous User from Lakewood, Colorado
December 25, 2025 at 8:12 PM
Anonymous User from Lawrenceville, Georgia
December 21, 2025 at 3:16 PM
Anonymous User from Tampa, FL
December 20, 2025 at 6:44 PM
Anonymous User from North Miami, FL
November 23, 2025 at 4:47 PM
Anonymous User from Port Ludlow, WA
September 2, 2025 at 5:34 PM