When Was This Number Ported? LRN Activation Date

What is LRN Activation Date?

LRN Activation Date is the date when a phone number was last ported to its current carrier. When someone ports their number from one carrier to another, this date updates in the NPAC database.

This data point is exclusive to VeriRoute Intel — most phone intelligence providers don't offer it. We include it free with every LRN lookup.

Why Activation Date Matters

SIM Swap Fraud Detection

In a SIM swap attack, fraudsters convince a carrier to port a victim's number to a new SIM. This triggers an LRN change. By checking the activation date, you can:

• Flag recent ports — Numbers ported in the last 7-30 days warrant scrutiny
• Require additional verification — Step up authentication for risky numbers
• Block high-risk transactions — Prevent fraud before it happens

Trust Scoring

The length of time a number has been with its current carrier indicates stability:

• Years with same carrier — High trust indicator
• Months with same carrier — Normal, low risk
• Days/weeks with carrier — May warrant additional verification

Account Takeover Prevention

When someone attempts a high-risk action (password reset, wire transfer, account access from new device), check the activation date. A recent port combined with a sensitive action is a red flag.

Implementation Examples

Risk Scoring Logic

# Pseudocode for activation date risk scoring
activation_date = lookup_result['lrn']['activation_date']
days_since_port = (today - activation_date).days

if days_since_port < 7:
    risk_level = "HIGH"
    action = "block_or_step_up_auth"
elif days_since_port < 30:
    risk_level = "MEDIUM"
    action = "additional_verification"
elif days_since_port < 90:
    risk_level = "LOW"
    action = "normal_flow"
else:
    risk_level = "MINIMAL"
    action = "trusted"

API Response

curl -X POST https://api-service.verirouteintel.io/api/v1/lrn \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"phone_number": "15551234567"}'

# Response
{
  "data": {
    "phone_number": "15551234567",
    "lrn": "5551230000",
    "carrier": "T-Mobile"
  },
  "success": true
}

Real-World Scenarios

Scenario 1: Banking Authentication

A customer requests a wire transfer of $50,000. Your system checks their phone:

• Activation date: 3 days ago
• Action: Require in-person verification or alternative authentication

Scenario 2: E-commerce Account Recovery

User requests password reset via SMS:

• Activation date: 2 years ago
• Action: Proceed normally — stable number indicates legitimacy

Scenario 3: New Account Signup

New user signs up with phone verification:

• Activation date: 10 days ago
• Action: Allow signup but flag for monitoring; may be legitimate new phone

Best Practices

1. Don't reject automatically — Recent ports have legitimate reasons
2. Combine with other signals — Use with device fingerprinting, IP analysis
3. Adjust thresholds by risk — Higher-value transactions = stricter rules
4. Log and monitor — Track activation date patterns for fraud rings
5. Consider VoIP separately — VoIP numbers port differently