Regulatory & complaint record
Formal flags raised against an identifier, and the pattern of complaints filed by the people who received the calls.
phoneThe same scoring engine that runs inside carrier signaling paths, exposed as a public sample. Enter a phone number or an IP address and get a risk score and tier back in seconds.
Your last three lookups stack here, most recent first, so you can hold a clean number against a flagged one. Nothing is stored — the stack clears on reload.
The public lookup is capped per visitor. Partners query the same engine without limits, in bulk and in real time, with reason codes their switch can act on.
Your lookup was not scored, so nothing here is a verdict on that number or address. This affects the public sample only — carrier-side scoring runs on separate infrastructure.
Formal flags raised against an identifier, and the pattern of complaints filed by the people who received the calls.
phoneHow the identifier actually behaves on live traffic — call and session patterns over time, not a one-off snapshot.
phone · ipWhether the identifier is what it claims to be, and the kind of network or allocation it sits behind.
phone · ipWhere traffic on the identifier originates, and whether that origin fits the traffic it is presenting.
phone · ipTrafficIQ™ produces a risk verdict and reason codes. Carriers consume those codes into their own treatment decisions and attest using their own STIR/SHAKEN infrastructure.
Reputation scores are advisory indicators generated from network telemetry, threat intelligence, and public data. They describe behavior observed in association with a number or address — not the identity or conduct of any individual or organization. Scores are point-in-time and change as the underlying data changes.
This tool demonstrates TrafficIQ™ scoring and is not intended for automated or high-volume use. If you believe a number or address has been scored in error, contact us at reputation@trafficiq.ai.