An IP reputation check is a point-in-time observation, not a permanent certificate. Use several relevant signals, record when and where each result was obtained, and verify the authorized workflow instead of reducing the decision to one score.

Blacklist records and risk scores are different

A blacklist reports whether an address appears in a particular list under that list’s criteria. A risk score is a provider-specific assessment that may combine different data and weighting. Scores from different services are not directly interchangeable and should not be averaged as if they used one scale.

An “ISP” or “residential” label in a third-party database describes that database’s classification. It does not by itself prove physical deployment, account safety or acceptance by a target platform.

A practical review sequence

  1. Record the exit IP observed in the actual configured client.
  2. Compare reported country, region, ISP or ASN fields with the order and intended task.
  3. Check relevant blacklist or reputation sources and preserve the source name and timestamp.
  4. Inspect DNS and WebRTC behavior in the same browser profile when those surfaces matter to the workflow.
  5. Test only an authorized target action and record the actual response category.
  6. Decide against a written acceptance rule instead of reacting to a single unfamiliar label.

For a fixed, dedicated exit that remains the same through the purchased term, review Static ISP proxies.

Blank acceptance record

This is a blank teaching template, not a KiloProxy test result:

Checked at Source Observed exit IP Location/network fields Result Next action

Store only non-sensitive evidence. Do not include proxy passwords, account credentials or customer data in screenshots or support messages.

When to contact support

First confirm that the client is using the intended proxy. If the observed exit or network fields still differ materially from the selected order, collect the order reference and non-sensitive test evidence, then contact support. Do not infer the cause from a single database result.

For hands-on browser and lookup steps, use the separate ToDetect proxy testing guide.

FAQ

Does one clean score prove that an IP is safe for every platform?
No. Tools use different data, targets apply their own rules and reputation can change. Evaluate the actual authorized task as well.
Should I average scores from different providers?
No. Their models and scales may differ. Keep each source, result and timestamp separate.
Does an ISP label prove the IP is a home connection?
No. A database label is not proof of physical placement or universal classification.
What evidence is useful when contacting support?
The non-sensitive order reference, observed exit, timestamp, test source and the specific mismatch. Never send the proxy password in a public lookup or screenshot.

Use a written acceptance record, then verify the connection in the client where the proxy will be used.