India Phone Numbers: Format, Area Code & Validation Guide

This comprehensive guide covers everything you need to know about India phone number formats, including E.164 validation rules, STD area codes, mobile vs. landline formatting, emergency services, and TRAI regulatory requirements. Whether you're integrating telephony APIs (SMS gateways, voice services, two-factor authentication), establishing customer support operations in India, or managing telecom compliance, this guide provides the technical details and code examples you need.

How to Format and Validate Indian Phone Numbers

Understanding India's Mobile vs. Landline Number Format

India uses distinct formats for mobile and landline numbers:

• Mobile Numbers: 10 digits starting with 6, 7, 8, or 9 (e.g., 9876543210). Mobile numbers don't use area codes.
• Landline Numbers: Area code (STD code) + subscriber number = 10 total digits. Area codes range from 2–5 digits.
  • Delhi landline: 011-12345678 (011 = STD code, 12345678 = subscriber number)
  • Mumbai landline: 022-12345678 (022 = STD code)

National vs. International Dialing:

• National (Domestic) Dialing: Prefix with 0 for STD calls
  • Landline: 0 + area code + subscriber number (e.g., 011-12345678)
  • Mobile: 0 + 10-digit mobile number (e.g., 09876543210)
• International Dialing: Use the E.164 format with country code +91
  • Format: +91 + 10-digit number (no leading 0)
  • Example: +919876543210 (mobile) or +911112345678 (landline)

Indian phone numbers follow the international E.164 standard, ensuring global interoperability. Understanding this format is essential for accurate dialing and seamless communication system integration. For more details on implementing E.164 across different countries, see our E.164 phone format guide.

E.164 Format:

• +91: Country code for India
• [1-9]\d{9}: National significant number (10 digits). First digit must be 1–9, followed by nine more digits.

Example: +919876543210

Validation:

You can validate Indian phone numbers using regular expressions. Here are examples in multiple languages:

JavaScript:

// E.164 format Validation
const e164Regex = /^\+91[1-9]\d{9}$/;
const mobileRegex = /^\+91[6-9]\d{9}$/; // Stricter mobile-only validation

const validateNumber = (number) => {
  return e164Regex.test(number);
};

// Sanitize user input (remove spaces, dashes, parentheses)
const sanitizePhone = (input) => {
  let cleaned = input.replace(/[\s\-\(\)]/g, '');
  // Add +91 if missing but starts with valid digits
  if (/^[6-9]\d{9}$/.test(cleaned)) {
    cleaned = '+91' + cleaned;
  } else if (/^0[6-9]\d{9}$/.test(cleaned)) {
    cleaned = '+91' + cleaned.substring(1);
  }
  return cleaned;
};

// Example usage with error handling
try {
  const userInput = "098 7654-3210";
  const sanitized = sanitizePhone(userInput);
  if (validateNumber(sanitized)) {
    console.log("Valid:", sanitized); // +919876543210
  } else {
    console.error("Invalid phone number format");
  }
} catch (error) {
  console.error("Validation error:", error.message);
}

console.log(validateNumber("+919876543210")); // true
console.log(validateNumber("+910123456789")); // false (invalid first digit)
console.log(validateNumber("+91987654321"));  // false (incorrect length)

Python:

import re

def sanitize_phone(input_str):
    """Remove formatting characters and normalize to E.164"""
    cleaned = re.sub(r'[\s\-\(\)]', '', input_str)
    # Add +91 if missing
    if re.match(r'^[6-9]\d{9}$', cleaned):
        cleaned = '+91' + cleaned
    elif re.match(r'^0[6-9]\d{9}$', cleaned):
        cleaned = '+91' + cleaned[1:]
    return cleaned

def validate_indian_phone(number):
    """Validate Indian phone number in E.164 format"""
    e164_pattern = r'^\+91[1-9]\d{9}$'
    return bool(re.match(e164_pattern, number))

# Example usage
print(validate_indian_phone("+919876543210"))  # True
print(validate_indian_phone("+910123456789"))  # False
print(sanitize_phone("098 7654-3210"))  # +919876543210

PHP:

<?php
function sanitizePhone($input) {
    $cleaned = preg_replace('/[\s\-\(\)]/'_ ''_ $input);
    if (preg_match('/^[6-9]\d{9}$/'_ $cleaned)) {
        $cleaned = '+91' . $cleaned;
    } elseif (preg_match('/^0[6-9]\d{9}$/'_ $cleaned)) {
        $cleaned = '+91' . substr($cleaned_ 1);
    }
    return $cleaned;
}

function validateIndianPhone($number) {
    return preg_match('/^\+91[1-9]\d{9}$/'_ $number) === 1;
}

// Example usage
var_dump(validateIndianPhone("+919876543210")); // true
var_dump(validateIndianPhone("+910123456789")); // false
echo sanitizePhone("098 7654-3210"); // +919876543210
?>

Input Sanitization Best Practices:

• Remove common formatting characters: spaces, dashes, parentheses, dots
• Handle both national format (starting with 0) and international format (starting with +91)
• Validate after sanitization to catch malformed inputs
• Implement proper error handling and user feedback
• Consider using specialized libraries like libphonenumber for production systems

Best Practice: Always validate and sanitize user-provided phone numbers to ensure data integrity and prevent errors. For region-specific formatting requirements, refer to country-specific guides such as our Albania SMS guide for European implementations.

India Area Codes (STD Codes): Complete City Reference

Mobile vs. Landline Area Codes:

• Mobile Numbers: Don't use area codes. Mobile numbers are nationally unique 10-digit numbers starting with 6, 7, 8, or 9. Mobile Number Portability (MNP) allows users to retain their numbers when changing operators or locations, so mobile numbers don't indicate geographic location.
• Landline Numbers: Require STD (Subscriber Trunk Dialing) codes indicating geographic regions. For domestic calls, dial 0 + STD code + subscriber number.

Major City STD Codes:

Important Notes:

• India uses a closed numbering plan, meaning the trunk prefix 0 is required for all domestic long-distance calls. For comparison with other regional numbering systems, see our guide on international phone number formats
• STD codes range from 2–5 digits in length; shorter codes typically indicate larger metropolitan areas
• The total length of STD code + subscriber number always equals 10 digits
• Number portability for landlines also exists, though less common than mobile portability
• For international format, drop the leading 0 and use +91 + complete 10-digit number

India Emergency Numbers: 112 System and ERSS

India's Emergency Response Support System (ERSS) is a unified platform that streamlines emergency response nationwide. It uses centralized number allocation and integrated dispatch services.

Key ERSS Features:

• Centralized Response: 24/7 operation centers in all states and union territories with multi-language support (23 official languages), GPS-based dispatch optimization, and real-time incident tracking
• Integration Capabilities: ERSS integrates with Computer-Aided Dispatch (CAD) systems, Geographic Information Systems (GIS), Mobile Data Terminals (MDT), and Automated Vehicle Location (AVL) technology
• Service Provider Requirements: 99.999% uptime reliability, sub-3-second connection times, mandatory location tracking, backup power systems, and redundant communication channels

Core Emergency Numbers:

Specialized Emergency & Helpline Numbers:

Important: While legacy numbers like 100, 101, and 102 remain functional, 112 is now the primary emergency number. The 112 system automatically routes calls to appropriate services.

The Indian Telecom Market: Growth and Position

India's telecommunications sector drives the country's digital transformation with significant growth and technological advancement.

Market Statistics (2023-2025):

• Subscriber Base: Over 1.17 billion wireless subscribers (TRAI Performance Indicator Reports)
• Global Position: Second-largest telecommunications market globally after China
• FDI Policy: 100% FDI through automatic route (Department of Telecommunications)
• Revenue Projection: $48.61 billion in 2025, projected to reach $76.16 billion by 2029 (CAGR: 9.40%)

Note: Verify current figures at TRAI's official website.

Growth Drivers:

• Digital Infrastructure Expansion: Rapid 5G rollout, extensive fiber optic network (2.3 million km), and growing mobile tower count (700,000+)
• Increasing Market Penetration: Rural area growth drives overall tele-density despite high urban tele-density
• Significant Investments: FDI inflows, spectrum auctions, and infrastructure projects fuel growth

Challenges:

• Limited Fixed-Line Penetration: Fixed-line penetration remains below 2% of the population, constraining broadband infrastructure development in some regions
• Spectrum Scarcity: High demand for spectrum amid 5G rollout creates allocation challenges and cost pressures on operators
• Regulatory Compliance Complexity: Operators must navigate multiple regulations including licensing, quality of service norms, tariff regulations, and consumer protection mandates
• Rural-Urban Digital Divide: Despite growth, significant infrastructure gaps persist in remote and rural areas
• Financial Stress: Operators face high debt levels from spectrum auctions and infrastructure investments while managing price competition

Telecom Regulatory Authority of India (TRAI)

Established in 1997 under the TRAI Act, the Telecom Regulatory Authority of India shapes the country's telecommunications landscape. Official website: https://www.trai.gov.in/

TRAI's Core Mandate:

• Promoting Orderly Growth: Ensuring fair competition and consumer protection
• Evidence-Based Policymaking: Conducting research and analysis to inform regulatory decisions
• Strategic Oversight: Monitoring market trends and enforcing regulations
• Tariff and Quality Regulation: Setting standards for service quality and pricing transparency

DND Registry and Commercial Messaging Regulations

TRAI operates the National Do Not Disturb (NDND) Registry to protect consumers from unsolicited commercial communications (UCC).

Key Regulations:

• Registration: Subscribers can register on the DND registry by sending SMS or through their operator's portal
• Telemarketer Requirements: All commercial entities must obtain consent before sending promotional messages or making telemarketing calls
• Headers and Templates: Commercial SMS must use registered headers and pre-approved templates
• Scrubbing Obligation: Telemarketers must check numbers against the DND registry before contacting
• Time Restrictions: Commercial calls permitted only between 9 AM – 9 PM
• Penalties: Non-compliance can result in disconnection of telemarketing resources and financial penalties

For Businesses Using SMS/Voice Services:

• Register as an entity with your telecom service provider
• Obtain a unique sender ID (header) for SMS campaigns
• Submit message templates for approval via DLT (Distributed Ledger Technology) platforms
• Maintain opt-in records and honor opt-out requests
• Monitor compliance with TRAI's Telecom Commercial Communications Customer Preference Regulations

Compliance Resources:

• TRAI Regulations - Full regulatory framework
• Quality of Service Norms - Service standards for operators
• Tariff Orders - Pricing and billing regulations

TRAI's regulatory impact assessments (RIAs) are a key part of its decision-making process, ensuring that regulations are well-informed and consider the potential impact on various stakeholders.

Technical Specifications and Interoperability

India's telecom infrastructure adheres to international standards to ensure interoperability and seamless communication.

Key Standards and Protocols:

• SIP/IMS (Session Initiation Protocol / IP Multimedia Subsystem): Core protocols for VoIP and voice services over IP networks. Handles call setup, management, and termination in modern networks.
• DIAMETER: Authentication, authorization, and accounting (AAA) protocol. Successor to RADIUS for subscriber authentication and policy management.
• MAP/CAMEL (Mobile Application Part / Customized Applications for Mobile Enhanced Logic): Enables roaming services, prepaid charging, and value-added services across networks. MAP handles inter-network signaling.
• SS7/SIGTRAN (Signaling System 7 / Signaling Transport): Core signaling protocols for circuit-switched networks and SS7 message transport over IP. Critical for call routing and network management.

Developer Implementation Guidance:

For developers integrating with Indian telecom services:

• API Standards: Most operators and aggregators provide REST/HTTP APIs for SMS, voice, and OTP services
• Authentication: Implement OAuth 2.0 or API key-based authentication as required by your provider
• Number Format: Always use E.164 format (+91XXXXXXXXXX) for API calls
• Rate Limiting: Implement exponential backoff and respect provider rate limits (typically 100–1000 msg/sec)
• Delivery Reports: Monitor DLR (Delivery Report) callbacks for message status
• Testing: Use operator-provided sandbox environments before production deployment
• Compliance: Ensure DLT registration for commercial messaging (see TRAI section)

Common Integration Libraries:

• Twilio SDK - Multi-language support for SMS/Voice
• Plivo SDK - Python, Node.js, PHP, Ruby, Java
• Native operator APIs from Airtel, Jio, Vodafone Idea

Security:

Security is paramount in telecommunications. Indian telecom operators must comply with stringent security requirements:

Encryption Standards:

• In-Transit: TLS 1.2+ for data transmission, IPSec for network-layer security
• Voice Encryption: SRTP (Secure Real-time Transport Protocol) for VoIP calls
• SMS: End-to-end encryption not mandated but recommended for sensitive data. Use app-layer encryption.
• API Security: HTTPS mandatory for all API endpoints. Certificate pinning recommended.

Data Protection and Compliance:

• IT Act 2000 & Amendments: Governs electronic communications and data protection (link)
• Digital Personal Data Protection Act 2023: Establishes data protection framework including consent, storage, and breach notification
• Data Localization: Critical personal data must be stored within India per RBI and data protection guidelines
• Lawful Interception: Operators must comply with lawful interception requirements under Telegraph Act
• Know Your Customer (KYC): Mandatory subscriber verification using Aadhaar or approved documents

Security Best Practices for Developers:

• Implement rate limiting and anomaly detection to prevent abuse
• Store credentials securely using hardware security modules (HSM) or key management services
• Enable two-factor authentication (2FA) for administrative access
• Conduct regular security audits and penetration testing
• Implement logging and monitoring for security events
• Follow OWASP Top 10 guidelines for web applications
• Encrypt sensitive data at rest using AES-256 or equivalent
• Maintain audit trails for compliance verification

Conclusion

India's telecommunications sector is dynamic and rapidly evolving. This guide covers the key aspects: number formatting, emergency services, market dynamics, and regulatory oversight.

Key Takeaways:

• Always use E.164 format (+91XXXXXXXXXX) for international compatibility
• Mobile numbers (starting with 6–9) differ from landlines (using STD codes)
• Comply with TRAI's DND regulations before sending commercial communications
• Implement proper validation and sanitization for user phone inputs
• Stay current with regulatory changes via TRAI and DoT websites

Developer Resources:

• Testing Tools:
  • libphonenumber - Google's phone number validation library
  • Twilio Phone Number Lookup - Verify number validity and carrier
• API Documentation:
  • Twilio India Docs
  • Plivo India Documentation
  • MSG91 API - Local Indian SMS provider
• Regulatory Resources:
  • TRAI Official Portal - Regulations and guidelines
  • Department of Telecommunications - Policy and licensing
  • DLT Platform - Commercial messaging registration
• Standards Documentation:
  • ITU-T E.164 Standard - International numbering plan
  • 3GPP Specifications - Mobile network standards

Next Steps:

1. Review your current phone number handling for E.164 compliance
2. Register for DLT if sending commercial SMS in India
3. Implement sanitization and validation using provided code examples
4. Test with Indian numbers in both national and international formats
5. Monitor TRAI website for regulatory updates affecting your use case

By understanding these elements, developers, businesses, and individuals can effectively navigate the Indian telecom environment.