US Phone Number

Detects North American Numbering Plan (NANP) telephone numbers in US contexts: the domestic NPA-NXX-XXXX form (bracketed, hyphenated, dotted, spaced, or bare, with an optional leading trunk "1") and the international +1 NPA-NXX-XXXX form. Area-code (NPA) and exchange-code (NXX) groups are constrained to a leading digit of 2-9 with the N11 service-code shape (211/311/411/511/611/711/811/911) excluded from both groups, per NANPA's published format rules. NANP area codes are drawn from a single pool shared by the US, Canada, and Caribbean member territories — the digit structure itself cannot distinguish a US number from a Canadian one (see ca-phone-number for the sibling pattern). Differentiation between the two patterns is by jurisdiction/regulation metadata and country-specific corroborative evidence keywords only, not by regex — this is the documented convention for the whole NANP pair.

Type: regex
Engine: universal
Confidence: medium
Confidence justification: Medium confidence: NPA/NXX leading-digit constraints (2-9) and N11 exclusion narrow the format meaningfully, but NANP numbers carry no checksum and a 10-digit US-shaped sequence still collides with invoice numbers, order numbers, and other structured identifiers. Per the phone-family convention set by au-fixed-line-telephone (every tier requires positive corroborative evidence; high digit-collision formats never get a zero-evidence tier), both the domestic and +1 international sub-regexes are evidence-gated at every tier: 75 requires generic phone-context evidence and 85 requires country-specific phone keywords with template/noise exclusion. The literal +1 prefix improves precision when present but is not by itself sufficient gating.
Jurisdictions: us
Regulations: CCPA/CPRA, TCPA
Frameworks: ISO 27001, ISO 27701, SOC 2
Data categories: pii, contact-information
Scope: narrow
Risk rating: 5
Platform compatibility: Purview: Compatible, GCP DLP: Unsupported, Macie: Unsupported, Zscaler: Compatible, Palo Alto: Unsupported, Netskope: Unsupported

Pattern

(?<!\d)(?:\+1[\s.-]?\(?[2-9](?!11)\d{2}\)?[\s.-]?[2-9](?!11)\d{2}[\s.-]?\d{4}|(?:1[\s.-]?)?\(?[2-9](?!11)\d{2}\)?[\s.-]?[2-9](?!11)\d{2}[\s.-]?\d{4})(?!\d)

Corroborative evidence keywords

phone, mobile, cell, call, text, contact number, US phone number, call me at, telephone, tel, dial, text me, text message, [object Object], WhatsApp, voicemail, phone number, mobile number, landline

Proximity: 300 characters

Should match

Call me at (212) 555-0148 — Domestic bracketed NYC area code with fictional NANPA 555-01XX exchange
Mobile: 415-555-0172 — Domestic hyphenated San Francisco area code
Contact: +1 202 555 0134 — International +1 form, Washington DC area code, space-separated
Phone number: 3125550199 — Domestic bare digits with no separators, Chicago area code

Should not match

112-555-0148 — Area code starts with 1 (NPA must start 2-9, not 0 or 1)
212-911-0148 — Exchange code is 911, an N11 service code, excluded from the NXX position
555-0148 — Only exchange + subscriber digits, no area code — not a full 10-digit number
42125550147123 — Valid-shaped digit run embedded inside a longer reference number, rejected by digit boundaries

Known false positives

A bare 10-digit sequence with NPA/NXX leading digits in the 2-9 range and no N11 shape can still coincidentally match invoice numbers, tracking numbers, or other structured identifiers of the same length and leading-digit distribution. Mitigation: Every tier — for both the domestic and +1 international sub-regexes — requires positive phone-context or country-specific evidence within 300 characters; no zero-evidence tier exists, so a bare digit run without corroborating context never fires at any confidence level.
NANP area codes are shared across the US, Canada, and Caribbean NANP member territories, so this pattern's regex will also structurally match Canadian- or Caribbean-issued numbers with no way to tell from the digits alone. Mitigation: Deploy alongside ca-phone-number using each pattern's jurisdiction-specific evidence keywords (e.g. "US phone number" vs "Canadian phone number") to bias classification, and rely on surrounding document context (postal addresses, currency, entity names) for jurisdiction attribution rather than the number itself.