BroadNet
Number reputation · real-time screening

Screen every number.
Before you dial or send.

Real-time number reputation for aggregators, telecom operators, contact centres, and app teams. Screen any number for risk, line type, and carrier before you dial or send — verdicts in about 25 milliseconds. Part of BroadNet's number-intelligence stack, alongside HLR Lookup.

Operator-grade SLAsCoverage across 200+ countriesGDPR-aligned · on-prem available
The BroadNet snow leopard screening a column of phone numbers — trusted numbers glow blue, risky ones red
BroadNet · number reputation
Reputation intelligence
200+
countries
25ms
verdict
99.99%
uptime
200+
Numbers covered
Growing daily
25 ms
Typical verdict
Faster than a TCP handshake
3 ms
Cached repeat
Free, never decrements credits
99.99%
Under 100 ms
Continuously refreshed

Broad coverage. No batch staleness. No third-party tax in the call path.

The silent cost

Every bad number you dial
is costing you right now.

The cost of carrying spam traffic compounds silently. Until it doesn't.

One bad campaign flags every DID in your range. Downstream traffic gets throttled or blocked.

One agent dialing dead numbers all morning burns a day of payroll on disconnected lines.

One spam complaint from a regulator escalates into a multi-month enforcement headache.

One signup bot ring burns through your verification SMS budget and your trial conversion.

Most of this is preventable at the source. Screen each number before you dial or send it, and the risk is caught upstream — where handling it is cheap and routine. BroadNet Phone Reputation is the API call that stops this from ever starting.

By the numbers

Number reputation, measured every day.

Broad coverage. No batch staleness. No third-party tax in the call path. Figures on this page are illustrative of the BroadNet number-reputation infrastructure.

Coverage
200+
phone numbers

Worldwide. No regional gaps. Refreshed continuously.

Verdict speed
25 ms
typical

Invisible to your dialer. Invisible to your caller.

Cache speed
3 ms
repeat verdicts

Cached repeats are free — they don't decrement credits.

Reliability
99.99%
under 100 ms

Continuously monitored. Regional failover on premium tiers.

How it scores

From your dialer
to the verdict, in 25 ms.

One HTTPS round-trip from your application to the regional edge, into the reputation engine, through your account threshold, and back — with the verdict logged for compliance and reporting.

  1. 01 · INGRESS
    Your dialer / app

    REST call, batch endpoint, or pre-flight check from your dialer. Bearer-token auth, no SDK required.

    p50 < 5 ms
  2. 02 · EDGE
    Regional edge

    Auth, schema validation, rate-limit check at the closest BroadNet PoP. Cache hit returns here.

    p50 < 5 ms
  3. 03 · SCORE
    Reputation engine

    Multi-source signal correlation, country-aware threshold, confidence scoring, category assignment.

  4. 04 · POLICY
    Your threshold

    Your account threshold + category-specific overrides applied. You set the line; we deliver the truth.

    p50 < 3 ms
  5. 05 · VERDICT
    Back to your app

    Verdict + category + confidence + country + observed latency. Logged for compliance and reporting.

    p50 < 25 ms total
  6. ← Verdict · category · confidence · latency_ms
Why teams switch

Four reasons,
measured in minutes, not months.

01 · REPUTATION

Defends your reputation before it breaks

Spam-rate KPIs at the carrier level are the existential threat to every operator and aggregator. Filter outbound traffic upstream and your downstream reputation stays clean. We make that automatic.

02 · COVERAGE

Worldwide — no exceptions

Your business doesn't stop at borders. Neither does our coverage. 390 million+ phone numbers globally, refreshed every day. US, EMEA, APAC, LATAM, Africa — wherever your traffic moves, we score it.

03 · LATENCY

Real-time, never the bottleneck

25 milliseconds typical. 3 milliseconds cached. Invisible to your dialer, invisible to your caller. We never become the reason a call took a beat longer.

04 · GRADE

Operator-grade engineering

Batch endpoints score thousands of numbers in one request. Volume tiers extend to hundreds of millions of checks per month. On-prem deployment for data-residency requirements. Built by the people who run dialers and signalling networks for a living.

Why operators and enterprises pick BroadNet

Built like a carrier, priced like an API.

The four things every operator, aggregator, and contact-centre director asks before signing — answered before the demo.

01 · NETWORK

1,000+ direct operator connections — not aggregator hops.

We hold our own SMPP and SS7 binds with destination operators in 86 countries, and every other route is a labelled partner route. No grey routes, no surprise re-routing, no opaque price markups in the middle.

1,000+Direct operator routes
02 · HERITAGE

Twenty-three years of carrier-grade messaging, audited continuously.

Operating since 2003, headquartered in Dubai. We carry 300M+ application-to-person messages a day for banks, governments, airlines, and the platforms that power the modern internet.

2003Operating since
03 · REACH

MENA-headquartered with reach to 200+ countries.

Local presence across the Middle East and North Africa, plus pan-African, South Asian, and South-East Asian operator relationships that make global rollouts feel like a single market.

200+Countries reached
04 · COMPLIANCE

Audit-grade by default, regulator-recognized in every market.

ISO 27001 / 9001 / 22301, SOC 2 Type II, GSMA Associate Member, HIPAA-aligned, GDPR-aligned. Sender-ID registrations handled by an in-region compliance team in every regulated market.

0Compliance incidents
Built for

Six teams,
one API call between them and the cost.

Voice and SMS aggregators

Stop routing traffic your downstream carriers will complain about.

Every flagged number you screen out is a downstream complaint you never receive — and a route you keep alive. Aggregators win on deliverability and complaint rate. We move both metrics in the right direction.

Talk to aggregator sales
Telecom operators

Defend your DID inventory before it gets blocked.

Your DID inventory is your business. One bad campaign flagged across your range and you are scrambling. We sit upstream of every outbound attempt and refuse the calls that would compromise your numbers.

Talk to telecom sales
Outbound contact centres

Dial only numbers that will answer.

Your agents are your most expensive resource. We make sure their time goes only to prospects worth dialing. Skip the disconnected. Skip the fraud-flagged. Skip the do-not-calls.

See the ROI framing
Lead-gen and sales teams

Qualify lists before you call them.

Bought a list? Inherited one? Run it through us first. We tell you what is worth dialing and what is a money-pit. No more guessing whether a contact list is salvageable.

Upload a list — spam-rate report free
SaaS and fintech

Block fraud at signup. Before it costs you a verification SMS.

Spam bots, fraud rings, disposable-number abuse — gone before they ever hit your verification flow. We screen at signup; you screen out the costs.

Request test access
Enterprise BPOs and regulated industries

Compliance, automated.

Every outbound attempt timestamped, scored, and logged. Built-in audit trail. On-prem deployment for data-residency requirements. SOC 2 Type II, GDPR-aligned by design.

Schedule compliance briefing
What you send

One lookup call,
documented inputs.

POST /sms/lookup takes the number as a query parameter and returns HTTP 200 with the number's current HLR / MNP status. The OpenAPI spec defines the request but no response schema, so read the body as data rather than hard-coding field names.

Field
Meaning
Type
destinationNumber
The number to check, with country code (query parameter)
string
reqType
Lookup type (optional query parameter; the spec does not list its values)
string
Authorization
Your access token, sent as Authorization: Bearer <token>
header
Responses

Three outcomes,
as documented.

The number shown is reserved for documentation use (Ofcom +44 7700 900). The spec documents the status codes for this call, not the fields of a successful response.

200 OK — number status
POST /sms/lookup?destinationNumber=447700900123
Authorization: Bearer $BROADNET_TOKEN

HTTP/1.1 200 OK
# body: the number's HLR / MNP status
# (the spec defines no response schema)
400 — ExceptionResponse
{
  "status": 400,
  "error": "Bad Request",
  "message": "…",
  "errorCode": "…",
  "requestUri": "/sms/lookup"
}
401 — token rejected at the gateway
{
  "error": "Unauthorized",
  "message": "Missing Authorization token"
}
Before / after

What changes
when reputation runs upstream.

Without phone reputation
With BroadNet
Many dials hit dead or bad numbers
Bad numbers screened out before the dial
Carriers warn you about spam-rate KPIs
Carriers stop hearing about you
Agents work through dirty lists
Agents only see qualified prospects
Manual list cleanup monthly
Automatic, in-line, per call
Compliance is a guess
Compliance is a log file
DID ranges flagged
DID ranges protected
Outbound conversion: flat
Outbound conversion: measurably higher
You find out from downstream
You prevent problems upstream
Spam-rate KPIs you can't explain
Spam-rate KPIs you control
Measuring the win

Four ways to put a number
on the savings.

Contact centres

Agent talk-time uplift × hourly cost. Teams recover the dial productivity they were losing to dead and flagged lines (illustrative; results vary).

Aggregators

Carrier complaints prevented × cost per complaint. Reputation defended at the route, not after.

SaaS / fintech

Fraud signups prevented × LTV impact. Stop the bot trial before it burns the verification SMS.

Operators

DID ranges saved × replacement cost. Spam-flag enforcement averted, attestation tier preserved.

Most customers see their first measurable result inside week one. Ready to put a number on yours? Request the ROI worksheet for your traffic →

Customer stories

What it looks like
when bad traffic stops at the door.

Tier-1 voice aggregatorVoice routing · globalAEGB
Challenge
downstream carriers were trending higher complaint rates on a subset of routes, threatening prioritisation tier.
Approach
pre-route screening on the BroadNet phone-reputation API in front of the routing engine, with per-route reputation analytics rolled into the NOC dashboard.
Director of routing
Pre-route
Screening
NOC
Reputation analytics
Outbound contact centre groupBPO · MENA + EMEAAEEG
Challenge
an agent fleet was spending materially more of the working day on disconnected and fraud-flagged lines than on prospects worth dialing.
Approach
pre-dial integration on the existing dialer plus daily batch cleanup of the next-day list against the BroadNet phone-reputation API.
Head of operations
Pre-dial
Inline screening
Daily
List cleanup
Pan-MENA fintech platformSaaS + fintech · MENA + AfricaAENG
Challenge
signup-flow OTP verification budget was being burned by repeated bot-driven trial registrations using disposable numbers.
Approach
inline phone-reputation check at signup, returning category + confidence so the signup form could decide between block, friction, or pass.
Head of trust + safety

Reputation infrastructure audited and certified — regulator-recognised across MENA, Africa, and Asia.

ISO27001ISO9001SOC 2Type IIGDPRReadyHIPAAAligned
Compliance + privacy

Reputation signals — not personal data.

TLS 1.3

All API traffic over TLS 1.3 with modern cipher suites. Bearer-token auth, scoped keys, rotation.

No PII stored

Phone number in, verdict out. No caller identity, no contents, no recordings — by design.

Audit trail

Every check logged with timestamp + verdict + latency. Exportable to your SIEM or BI tool.

GDPR + PDPL aligned

DPA on every contract. EU-only routing on request. Right-to-erasure tooling exposed via API.

On-prem option

Same API in your data centre or sovereign cloud. Common for carriers and regulated industries.

Fail-open default

If the service ever degrades, your dialer can default to dial-as-before. Safety first, by design.

Regional residency

EU, GCC, and APAC processing regions available on enterprise tier. Pin a region in your contract.

Webhook delivery

Every async event is posted to the webhook you register.

Questions buyers ask

Fourteen answers,
no marketing fog.

No. We respond in around 25 milliseconds — faster than any handshake to your downstream carrier. Calls still ring within the user's expectation window. Premium tiers ship with a regional failover endpoint so a network blip never blocks a call.

No. We only flag numbers with strong, multi-source evidence of abuse. Single weak signals never trigger a block. You set the confidence threshold; you keep control.

Build with a fail-open default and the worst case is you dial like you did before. Premium tiers include regional redundancy, fail-over endpoints, and uptime SLAs with service credits for breach.

Continuously refreshed. New threats are indexed every day. No batch staleness, no monthly CSV downloads, no waiting until the next quarter. Cached repeats are served from the regional edge in around 3 milliseconds.

Yes, on enterprise tier. Same API, your hardware, your data never leaves your network. Common for carriers and regulated industries that need data residency or sovereign deployment.

If it can make an HTTPS request, it integrates. Pre-built recipes for the major dialer platforms, CRMs, automation tools, and carrier signalling stacks ship in the developer docs.

Yes. We hold reputation signals — not personal data about callers or callees. The API surface is a phone number in, a verdict out. No PII is stored, no recordings, no contents. DPA is included on every contract.

No. We sit in front of your stack, not in place of it. Drop in, drop out. No contracts with your carriers required. You keep your routes, your DIDs, your relationships — we just keep them clean.

Repeat checks on the same number within the freshness window don't decrement your credits. We respond from the regional edge in around 3 milliseconds and don't bill the verdict.

Every check is logged with timestamp, verdict, category, confidence, and latency. We provide a dashboard, and the data is exportable to your BI tool. ROI is visible inside the first week.

Our platform uptime commitment is 99.99% per month, the same standard SLA as the rest of BroadNet. Enterprise contracts carry service credits if it is missed; the credit schedule is published on our Support & SLA page. Every customer uses the same API endpoints.

On enterprise, yes. Co-branded portal and white-label API endpoints available, including a private sub-domain on your DNS and per-customer credentials.

Cheaper, faster, and lower-risk. Building this in-house means data feeds, normalization, freshness pipelines, ongoing maintenance, and a team that owns it for the long term. Most operators we talk to estimate it as a year-one programme for a materially worse product.

Yes. Bring 1,000 of your real numbers to the demo and we score them live. You see the verdict distribution, the category breakdown, and the latency profile before any conversation about commercials.

Question not here? Ask our engineering team

Pricing

Test first. Scale on volume tiers.

Test access on request, with a reply within one business day. Volume-based pricing, with on-prem deployment and custom terms available on enterprise contracts.

The BroadNet snow leopard on a glowing highway of light under the infinity loop
Carrier-grade delivery

Delivered to 200+ countries, direct to the operator in 86.

No grey routes: a direct operator bind wherever one is commercially available, otherwise a labelled partner-managed route. One API to every channel, on a network built since 2003.

200+
Countries
1,000+
Operator connections
300M+
Msgs·day
Test on your own traffic. Measure the drop.

Verdicts in 25 ms.
Action on the next call.

Cleaner traffic. Higher conversions. Lower carrier complaints. One API between you and the spam your business has been carrying for free.

$ curl -X POST "https://api.broadnet.me/sms/lookup?destinationNumber=447700900123" -H "Authorization: Bearer $BROADNET_TOKEN"

Also from BroadNet

MobileValidatePrivate preview

Need a number's line type, or the messaging apps it can receive on, before you send? MobileValidate, a BroadNet brand in private preview, checks carrier and line type, apps such as Telegram, Viber and RCS, and e-mail mailboxes in one API request.