| IP address is rejected | Malformed input or unsupported notation | Check the format and paste only a valid address, domain, ASN or CIDR value. |
| City shown is inaccurate | Provider estimation, gateway routing or VPN | Treat city as approximate and compare alternate legitimate sources. |
| No ISP is displayed | Enrichment provider lacks a mapping | Check ASN and RDAP fields and retry later. |
| No ASN is returned | Private/reserved address or limited provider coverage | Verify public routability and examine registry context. |
| WHOIS contacts are missing | Registry redaction or incomplete RDAP data | Consult the responsible registry and do not infer that ownership is absent. |
| PTR record is blank | No reverse DNS was published | Do not treat missing PTR as proof of maliciousness. |
| Forward DNS differs from PTR | Stale, customized or multi-host DNS setup | Check the original hostname and current DNS answers. |
| VPN flag disagrees with known VPN | Provider feed is incomplete or delayed | Review current exit address and supporting network indicators. |
| Tor flag seems outdated | Exit-node membership changes | Recheck official exit-list status at the relevant time. |
| IP appears blacklisted incorrectly | False positive or recycled address | Inspect the named list and follow its appeal or removal guidance. |
| IP has no blacklist hits | Limited list coverage or recent activity | Continue reviewing other risk and behavior signals. |
| Reputation differs from another tool | Different scoring models and data sources | Inspect contributing flags instead of comparing headline scores alone. |
| A private IP has no map location | Private addresses have no unique public geolocation | Look up the actual public source IP if appropriate. |
| My IP shows VPN location | Remote service sees the VPN exit address | Compare the VPN region and network, then assess other leak protections separately. |
| My IP changes frequently | Dynamic addressing or mobile gateway changes | Record each observation timestamp and relevant session. |
| A domain resolves to multiple addresses | CDN or load balancing | Check each relevant IPv4/IPv6 result separately. |
| CIDR lookup differs from single IP | Prefix and host inquiries refer to different scopes | Verify the network prefix and address you intended. |
| ASN lookup produces little detail | Registry or feed coverage varies | Check originating network references and RDAP records. |
| Bulk CSV is not parsed | Unexpected delimiters, headers or quoting | Use a straightforward address column and validate the file format. |
| Bulk results contain duplicates | Repeated source lines | Deduplicate the input when unique-address results are desired. |
| Bulk lookup is slow | Multiple provider calls and rate limits | Use smaller batches and wait for provider recovery. |
| One provider times out | Third-party outage or throttling | Review other fields and retry the missing data later. |
| Export is empty | No completed lookup or browser download issue | Complete an analysis and verify download permissions. |
| PDF report differs from live screen | Export formatting and timing differ | Use JSON for structured evidence and review the PDF layout. |
| API request fails | Invalid JSON, route, network or server error | Test the documented POST payload and inspect the response status. |
| History disappeared | Local browser storage was cleared | Save required exports externally; local history is not a backup. |
| Mobile IP shows a distant region | Carrier gateway location differs from physical device | Do not use it as exact location evidence. |
| Anycast resolver appears in strange city | Same address is routed from multiple sites | Rely on network context rather than a single mapped point. |
| DNSBL result is unavailable for IPv6 | Some providers cover IPv4 only | Mark the result as unsupported, not clean. |
| Lookup cannot identify an individual | Shared IPs and lack of subscriber mapping | Use permitted investigative channels; do not speculate about identity. |