Trestle - Identity Data Enrichment and Validation APIs Trestle - Identity Data Enrichment and Validation APIs Trestle - Identity Data Enrichment and Validation APIs Trestle - Identity Data Enrichment and Validation APIs
  • Products
        • Enrichment

        • Reverse Phone APIGLOBAL
        • Verify and enrich phone numbers
        • Reverse Address API
        • Verify and enrich address information
        • Caller Identification API
        • Identify and enrich caller information
        • Add-Ons

        • Litigator Check
        • Identify phone numbers associated with serial litigators
        • Email Deliverability
        • Confirm email inboxes accept mail in real-time
        • Spam Check
        • Flag phone numbers tied to high-risk calling activity
        • Email Age Score
        • Score how long an email has existed
        • Validation & Verification

        • Phone Validation APIGLOBAL
        • Validate phone numbers and identify disconnected numbers
        • Real Contact API
        • Verify phone, email, and address information
        • Address Validation API
        • Validate and normalize addresses
        • Assess Risk

        • Decision Console
        • Optimize identity verification for manual review
        • Decision Signals API
        • Automate identity verification for risk decisioning
        • Start using Trestle products today

          Get started for free—no credit card required

          Start Your Free Trial

  • Solutions
        • Industries

        • B2B Contact Data
        • eCommerce
        • Insurance
        • Lead Generation
        • Real Estate
        • Communications
        • Use Cases

        • Verify and Prioritize Leads
        • Outbound Dialing Optimization
        • Assess Risk And Prevent Fraud
        • Inbound Call Routing and Verification​
        • Signup and Onboarding​
        • Optimize AI Voice Agents
        • Start using Trestle products today

          Get started for free—no credit card required

          Start Your Free Trial

  • Pricing
  • Resources
        • API Documentation
        • Blog
        • Knowledge Base
        • Case Studies
        • Glossary
        • Partners and Integrations
  • Company
        • About Us
        • Why Trestle
        • Careers
        • Affiliate Program
        • Contact
  • Log In
  • Start for Free

Trestle Overview

19
  • Does Trestle Offer DNC Checks?
  • Does Trestle Have a Sandbox Environment To Test Integrations?
  • What is Trestle’s Coverage and Accuracy?
  • Which Countries’ Data Do You Have?
  • Does Trestle Normalize Phone Number Format?
  • How Do You Integrate Trestle’s APIs?
  • How Does Trestle’s API Pricing Work?
  • How Often is Trestle’s Data Updated?
  • How to Properly Sample a Test File and Evaluate Trestle
  • Understanding NPA-NXX and the Implications of Number Portability
  • Understanding Trestle’s Free API Trial and the API Access Request Process for Specific Products
  • What are the Response Times for Trestle’s APIs?
  • What are the Various Sources of Trestle’s Identity Data?
  • What are Trestle’s SLAs?
  • What Demographic Data Does Trestle Have?
  • What Is Our Global Phone Validation Coverage?
  • What is the Default and Max QPS Supported?
  • What Queries are Billable?
  • What Security Measures are Taken by Trestle?

Product Features

38
  • Everything to Know About IP Trust Scores
  • How to Check When an Email Address Was Made
  • Everything to Know About Spam Checks
  • Using IP Intelligence Checks to Verify Lead Legitimacy in Real Contact API
  • Everything to Know About Phone-to-Address Match
  • Real Contact API 1.1 vs. Real Contact API 2.0: What’s Changed and How to Upgrade
  • Everything to Know About Phone Activity Score
  • Everything to Know About Real Contact API 2.0
  • How Trestle’s Activity Score is Different From HLR Lookups
  • Everything To Know About Name Match Details
  • Everything To Know About Phone-to-Name Confidence Score
  • Everything To Know About Litigator Checks
  • Everything To Know About the Email Age Score Add-on
  • Everything To Know About the Email Deliverability Add-on
  • Explain Real Contact API Grading
  • Fine-Tuning Find Person API Results
  • How Can Trestle’s Email Data Be Used?
  • How Do I Determine Phone Validity?
  • How Do You Read Trestle’s Phone Activity Score?
  • How Does Our Real Contact API Name Matching Work?
  • How Does Trestle Assess Email Validity in Real Contact?
  • How is Trestle’s Phone Activity Score Calculated?
  • How To Read the Real Contact Data Assessment Report
  • International Reverse Phone API Explained
  • Line Type Fidelity and Confidence
  • Trestle API Response Attribute Ranking
  • Trestle Warnings – A Comprehensive Guide
  • Understanding the Difference: Phone Validity vs. Trestle’s Activity Score
  • What are the Different Address Types Returned by Trestle?
  • What Does a Name Match of Null Mean?
  • What Does the Carrier Name Mean?
  • What is the Difference Between CNAM and Trestle’s Smart CNAM API?
  • What is the Difference Between Fixed VoIP and Non-fixed VoIP?
  • What is the Difference Between Reverse Phone API, Caller Identification API, and Smart CNAM API?
  • What is the Link Date Associated with Phones and Addresses?
  • Why and When to Use Trestle’s Name Hint
  • Why Do We Return a Maximum of 100 Entities in Find Person API?
  • Why Does the Address Return as Invalid?

Integrations

22
  • HubSpot | Phone Validation App Integration Guide
  • ZoomInfo | Phone Validation, Real Contact, and Reverse Phone Integration Guide
  • Databar | Phone Validation Integration Guide
  • Make | Real Contact API Integration Guide
  • Make | Phone Validation API Integration Guide
  • Apollo | Phone Validation Integration Guide
  • HighLevel | Phone Validation Integration Guide
  • boberdoo | Real Contact API Integration Guide
  • Clay | Validate Phone Number Integration Guide
  • Clay | Verify Contact Integration Guide
  • HubSpot | Real Contact Phone Grading App Integration Guide
  • How Do I Use a HubSpot List To Grade My Contacts?
  • How Do I Use HubSpot Workflow Triggers To Grade My Contacts?
  • Lead Prosper | Phone Validation Integration Guide
  • Lead Prosper | Real Contact Integration Guide
  • Reverse Phone API Enrichment of Leads in Google Sheets via Zapier
  • Snowflake | Phone Validation Integration Guide
  • What is the Phone Validation Integration within ActiveProspect?
  • What is the Real Contact Integration within ActiveProspect?
  • Validate and Verify Leads with Trestle’s Phone Validation API in Sierra Interactive via Zapier
  • Validate Leads with Trestle’s Phone Validation API in LeadConnector via Zapier
  • Zapier | Grade Leads from a Google Sheet with Real Contact

Troubleshooting

9
  • How to Prevent 429 Errors by Sizing API Concurrency to Your QPS Limit
  • How to Fix 403 Forbidden Errors When Using Trestle’s APIs
  • Why Won’t My Email Work to Signup for Trestle?
  • Ruby Integrations: 403 Forbidden Errors
  • Getting 429: Too Many Requests Error – Why?
  • How to Remove or Deactivate a User in Trestle’s Developer Portal
  • How to Update Phone to Name/Address Linkage Records
  • Reviewing Usage Data
  • Why is the Name Associated with the Phone Incorrect?

Developer Portal

8
  • Business Verification Failed? Here’s What Documents You Need to Submit
  • How to Find and Download Your Receipt or Invoice
  • How to Monitor API Errors With Your Usage Graph
  • Batch Upload FAQ
  • Developer Portal Wallet Frequently Asked Questions
  • Export and Analyze Your Queries in Your Developer Portal Account
  • Getting Started with Trestle’s Developer Portal Wallet
  • Making Changes to Billing Settings for the Developer Portal Wallet

User Guides

9
  • Phone Validation in Java
  • Batch Upload Instructions
  • How Do I add Additional Members to My Trestle Account?
  • How to Handle Special Characters in API Queries
  • Phone Validation API with ASP.NET
  • Phone Validation with JavaScript and HTML: Leveraging Trestle’s API
  • Phone Validation API with PHP: Leveraging Trestle’s API
  • Phone Validation API with Python
  • Phone Validation API with React

Telephony Knowledge

9
  • Choosing the Right Number Lookup API
  • How to Identify Callers In Real-Time Using a Reverse Phone API
  • Why is Line Type Intelligence Important?
  • What is a “No Routes Found” Phone Message?
  • The Best Phone Validation API for Call Centers
  • How to Identify Disconnected Phone Numbers Automatically
  • What is a Phone Number Reputation Lookup?
  • What is a Carrier Number?
  • What is a Non-Fixed VoIP Phone?

Risk Suite Overview

8
  • How to Read Email Breach Reports and IP Abuse Reports in Decision Console
  • Everything to Know About Decision Signals API
  • How to Get Started With Decision Console
  • What is the Decision Overview and How Do I Read It?
  • What is an Attribute Card and How Do I Read It?
  • What is Link Builder and How Do I Use It?
  • Understanding Team and Account Management
  • FAQ and Troubleshooting: Decision Console
  • Home
  • Knowledge Base
  • Product Features
  • How Trestle’s Activity Score is Different From HLR Lookups
View Categories

How Trestle’s Activity Score is Different From HLR Lookups

7 min read

When evaluating a phone validation method, you’ll encounter different approaches to determining whether a phone number is active and reachable. Traditional methods like HLR (Home Location Register) lookups and LRN (Location Routing Number) lookups have been industry standards for years. However, they weren’t designed to answer the #1 question most businesses actually need answered: Will someone pick up when I call this number?

This article explains how these technologies work, what they can and can’t tell you, and why Trestle’s Phone Activity Score provides a much more comprehensive signal for lead contactability and customer verification.

What is an HLR Lookup? #

HLR lookups query a mobile network’s central subscriber database (called the Home Location Register) to retrieve information about a phone number. In modern LTE/5G networks, similar subscriber status information is maintained in HSS systems, though commercial ‘HLR lookups’ still commonly refer to signaling-based subscriber queries.

When you perform an HLR lookup, the request travels either to the mobile network operator (MNO) or to a signaling network (typically via SS7 or signaling intermediaries), to retrieve subscriber status information. 

HLR lookups can tell you:

  • Whether a number is currently assigned to a subscriber
  • The current network operator serving that number
  • Whether the number has been ported to a different carrier
  • Basic status (active, absent, or dead)

What HLR lookups cannot tell you:

  • Whether someone actually uses the phone regularly
  • The likelihood that someone will answer when you call
  • Activity patterns over time
  • Whether the number belongs to a secondary or rarely-used device

HLR lookups were originally designed for network routing and mobility management, not for predicting whether a lead will convert or a customer will be reachable. They provide a binary, point-in-time status that doesn’t account for user behavior. In other words, HLR lookups can indicate if a number is currently registered and reachable on the network (in other words, “absent” versus “active”), but does not provide connectivity signals, usage evidence, or activity history. 

A simple way to remember what HLR lookups can and can’t do:

→ An HLR lookup answers, “Can the network route to this number right now, and on what network/roaming state?”

→ An HLR lookup does NOT answer, “How does this person behave with their phone?” 

What is an LRN Lookup? #

LRN (Location Routing Number) lookups serve a different purpose entirely. When the U.S. Congress mandated local number portability in 1996, carriers needed a way to route calls to numbers that had been transferred between providers. The LRN system was created to solve this routing problem.

LRN ensures that a unique 10-digit number is assigned to each telephone switch. Therefore, when a call is made to a ported number, the originating carrier queries a Local Number Portability (LNP) database to get the LRN, which tells the network which switch currently serves that number.

LRN lookups can tell you:

  • Which carrier currently serves a phone number
  • Whether a number has been ported
  • The network switch serving the number

What LRN lookups cannot tell you:

  • Whether the number is connected or disconnected
  • Whether the phone is actively used
  • Any information about call activity or user engagement

LRN data is fundamentally about routing infrastructure, not about whether someone will answer when you dial. 

How is Trestle’s Activity Score Different? #

Trestle’s Activity Score approaches phone validation from the perspective that matters most to businesses: Is this number worth calling?

Rather than providing a simple binary status, our Phone Activity Score delivers a 0-100 rating based on actual phone activity observed over the past 12 months. A score of 100 indicates consistent activity, while a score of 0 indicates a number that is likely disconnected, or no observed activity.

Phone Activity Score incorporates multiple data sources that standard HLR and LRN lookups don’t access:

  • Call connectivity data from carriers and cross-carrier network enablers
  • Phone metadata including line type and carrier assignment
  • Name-to-number linkage data and duration of that linkage
  • Connection and porting status signals from carriers
  • Verified call activity observed across Trestle’s network

These network-level signals provide strong coverage in North American and growing international coverage. HLR lookups are one input that inform our Activity Score, but by combining HLR data with the variety of behavioral and network-level signals listed above, our solution is far more robust than any single lookup method.

What makes this approach fundamentally different is that a Phone Activity Score evaluates behavioral patterns, not just technical status. A phone number might pass an HLR lookup (it’s assigned to a subscriber) but still have an Activity Score of 30 because no one has used it in months.

When Does This Difference Matter? #

The distinction between these approaches is critical to understand in specific business scenarios. Here’s a few examples:

Lead Prioritization #

You’re calling leads, and you want to reach people who are more likely to answer their phone. A number that’s technically valid but rarely used wastes agent time. Trestle recommends prioritizing numbers with Activity Scores of 70 or above for outbound campaigns, as these indicate high confidence that someone will answer. 

Fraud Prevention #

Fraudulent sign-ups tend to use numbers that are technically valid but inactive or associated with temporary services, like non-fixed VoIP. This is a scenario where HLR lookups have a significant blind spot. HLR does not support VoIP numbers and typically returns an unknown or “Not Applicable” response. A low Phone Activity Score, by contrast, can reveal a lack of genuine usage patterns across all line types, helping flag suspicious sign-ups regardless of whether the number is mobile, landline, fixed VoIP or non-fixed VoIP.

SMS Campaign Optimization #

For SMS delivery, you need more than carrier routing information. Numbers with low activity scores may technically receive your message, but are very unlikely to engage with it.

What Can’t Activity Score Do? #

No phone validation method provides perfect information, and it’s important to understand the limitations:

  • Some regions, like Canada, have less data available for Activity Score calculations. This may affect score accuracy for certain numbers.
  • Users who primarily communicate through FaceTime, WhatsApp, or Messenger generate less traditional phone activity, which could result in lower scores even for numbers they actively use.
  • Secondary phones or numbers used only occasionally may have lower scores despite being actively monitored by their owners.

Trestle’s Phone Activity Score has an accuracy rate with false positives below 1% for identifying disconnected numbers, but edge cases exist, which is why the score provides a range rather than a binary verdict.

Advantages and Limitations of Each Method #

One of the most overlooked limitations of HLR lookups is that they are inherently restricted to mobile numbers. HLR databases are maintained by mobile network operations for SIM-based subscribers; they contain no records for landlines, fixed VoIP, non-fixed VoIP, or toll-free numbers.

In practice, this is a far bigger gap than many businesses realize. Across 3+ billion queries over the past 6 months, roughly 35% of phone numbers Trestle processed were non-mobile. For any business relying on HLR lookups as their primary validation method, that means a third or more of their phone records receive no validation at all.

Trestle’s Phone Validation API validates all phone line types with a single API call. This ensures comprehensive coverage regardless of what kind of phone number a lead or customer provides. 

MethodBest ForLimitations
HLR LookupsSMS delivery verification, mobile number confirmationPoint-in-time only, mobile numbers only, no activity insights
LRN LookupCall routing optimization, carrier identificationNo connectivity or activity information
Phone Activity ScoreLead prioritization, contactability prediction, fraud signalsMay underweight users of messaging apps

Trestle’s Phone Validation API combines carrier lookup, line type detection, and the Activity Score in a single API call, providing comprehensive phone intelligence without requiring multiple vendor integrations.

The Growing Risk of Relying on HLR Lookups #

Beyond just technical limitations, HLR lookups face an increasingly uncertain future due to regulatory and security pressures.

SS7 Security Vulnerabilities Driving Tighter Access Controls #

HLR lookups depend on the SS7 (Signaling System 7) signaling protocol, which dates back to the 1970s and was never designed with modern security in mind. Over the past decade, SS7 has been repeatedly exploited for location tracking, call interception, and SMS hijacking, prompting the FCC to begin pressuring carriers to implement tighter security protocols. As carriers lock down SS7 access to reduce their security exposure, the availability and reliability of HLR lookups will likely shrink. 

Operators Restricting Access to Signalling Networks #

Mobile operators routinely limit HLR access for certain countries and use cases, meaning coverage gaps are built into the system. In response to the SS7 security concerns mentioned above, these carriers have begun actively restricting who can query their networks. 

The future of HLR lookups as a source of truth for phone validation looks dim. The telecom infrastructure they rely on is becoming harder to access. Businesses building their phone validation strategy around HLR will face mounting uncertainty about their long-term reliability and availability. 

Trestle’s approach, which uses multiple data sources and proprietary signals rather than relying solely on SS7 queries, provides a far more sustainable foundation for phone intelligence.

How to Interpret Phone Activity Scores for Your Use Case #

Here’s how to apply Phone Activity Score thresholds:

  • 70-100: High confidence the phone is connected and regularly used. Prioritize these for outbound contact.
  • 50: Not enough signals to determine if the phone is connected or disconnected
  • 0-30: High confidence the phone is disconnected or inactive. Filter these from campaigns or flag for review.

For questions about Trestle’s Activity Score or to test phone validation with your data, contact support@trestleiq.com or start a free trial today.

Start a Free Trial

Updated on March 3, 2026
Everything to Know About Real Contact API 2.0Everything To Know About Name Match Details
Table of Contents
  • What is an HLR Lookup?
  • What is an LRN Lookup?
  • How is Trestle's Activity Score Different?
  • When Does This Difference Matter?
    • Lead Prioritization
    • Fraud Prevention
    • SMS Campaign Optimization
  • What Can't Activity Score Do?
  • Advantages and Limitations of Each Method
  • The Growing Risk of Relying on HLR Lookups
    • SS7 Security Vulnerabilities Driving Tighter Access Controls
    • Operators Restricting Access to Signalling Networks
  • How to Interpret Phone Activity Scores for Your Use Case
trestleLogo

Verified Identities. Trusted Interactions.

U.S. coverage for enrichment and verification.

Global coverage for phone validation and reverse phone.

Based in Bellevue, WA

Linkedin Github Postman

Company

  • About Us
  • Why Trestle
  • Careers
  • Affiliate Program
  • Contact

Products

  • Reverse Phone API
  • Reverse Address API
  • Caller Identification API
  • Phone Validation API
  • Real Contact API
  • Address Validation API
  • Batch Upload
  • Litigator Check Add-on
  • Free Lead Assessment

Use Cases

  • Outbound Dialing Optimization
  • Inbound Call Routing and Verification
  • Signup and Onboarding
  • Lead Verification
  • Optimize AI Voice Agents

Resources

  • Blog
  • Knowledge Base
  • Case Studies
  • Glossary
  • Data Dictionary
  • Changelog
  • Partners and Integrations

Developers

  • Developer Portal
  • API Documentation
  • API Live Status

Legal

  • Terms of Service
  • Privacy Policy
  • Data Processing Agreement
  • Service Level Agreement
  • Do Not Sell My Personal Information
Trestle - Identity Data Enrichment and Validation APIs
  • Products
        • Enrichment

        • Reverse Phone APIGLOBAL
        • Verify and enrich phone numbers
        • Reverse Address API
        • Verify and enrich address information
        • Caller Identification API
        • Identify and enrich caller information
        • Add-Ons

        • Litigator Check
        • Identify phone numbers associated with serial litigators
        • Email Deliverability
        • Confirm email inboxes accept mail in real-time
        • Spam Check
        • Flag phone numbers tied to high-risk calling activity
        • Email Age Score
        • Score how long an email has existed
        • Validation & Verification

        • Phone Validation APIGLOBAL
        • Validate phone numbers and identify disconnected numbers
        • Real Contact API
        • Verify phone, email, and address information
        • Address Validation API
        • Validate and normalize addresses
        • Assess Risk

        • Decision Console
        • Optimize identity verification for manual review
        • Decision Signals API
        • Automate identity verification for risk decisioning
        • Start using Trestle products today

          Get started for free—no credit card required

          Start Your Free Trial

  • Solutions
        • Industries

        • B2B Contact Data
        • eCommerce
        • Insurance
        • Lead Generation
        • Real Estate
        • Communications
        • Use Cases

        • Verify and Prioritize Leads
        • Outbound Dialing Optimization
        • Assess Risk And Prevent Fraud
        • Inbound Call Routing and Verification​
        • Signup and Onboarding​
        • Optimize AI Voice Agents
        • Start using Trestle products today

          Get started for free—no credit card required

          Start Your Free Trial

  • Pricing
  • Resources
        • API Documentation
        • Blog
        • Knowledge Base
        • Case Studies
        • Glossary
        • Partners and Integrations
  • Company
        • About Us
        • Why Trestle
        • Careers
        • Affiliate Program
        • Contact
  • Log In
  • Start for Free