IP reputation check

Check two named threat feeds. See the evidence, its age and its limits before deciding what to investigate.

Source and scope details

Your address is checked on our server against cached CINS Army and Emerging Threats public files. We do not send the checked address to either publisher or connect to it.

Shared files refresh at most hourly, with a 15-minute retry delay on failure. Source age limits: CINS Army 48 hours; Emerging Threats 7 days. File dates do not identify when abuse occurred.

Enter an address to compare the two feeds.

Source results

CINS Army

Not checked yet

Public subset of CINS threat intelligence. Inclusion reflects the publisher’s sensor and scoring criteria; we do not receive or invent its private scores.

Emerging Threats — Compromised IPs

Not checked yet

Addresses in the publisher’s Compromised IPs file. The file does not provide per-address incident dates, attack categories or evidence of current device compromise.

How a threat-feed observation is made

  1. Choose the relevant address

    Use the address and time connected to the event.

  2. Retrieve public files

    Keep the named source and file metadata.

  3. Apply freshness and coverage

    Only supported current files establish membership.

  4. Review exact matches

    Investigate against your own authorized records.

Current source membership is evidence about an address, not a malware diagnosis or a personal judgment.
On this page

Learn more about IP reputation check

An IP reputation check helps you investigate whether a public address appears in a named threat feed. It is useful when a connection is blocked, a server behaves unexpectedly, or you want context before reviewing an abuse report. The IP reputation check result is evidence from a particular source at a particular time. It cannot certify a person, device or connection as trustworthy.

Two public files are checked independently: CINS Army and Emerging Threats Compromised IPs. Each keeps its own file date and download date. These files do not supply calibrated probabilities, so the page does not invent a numerical risk score.

How to use this IP reputation check

Enter one public IPv4 or IPv6 address, without a URL, port or prefix. Private, loopback and documentation addresses are rejected. Mapped IPv4 notation is normalized to its IPv4 identity.

Read more

Use my IP fills this site’s observed address without running a check. Review it after changing a VPN or connection. The example fills a public resolver, without implying a permanent clean status.

Check reputation compares the chosen address with separately cached public files. The publishers receive file-download requests rather than your entered lookup address. The tool performs no target scan, port connection or login.

Stop discards the pending report; editing invalidates old evidence; Clear resets the form. Shared refresh work may still finish for other lookups. Copy deliberately includes the checked address, so review before sharing.

Read each result independently

Listed in this snapshot means the exact IPv4 address matched a usable file. It does not extend the listing to neighbors, a provider or a country, or establish who caused the activity.

Read more

A Not listed in this snapshot result means the address was absent from a supported, sufficiently recent file. An IP reputation check cannot turn that absence into a guarantee. A source may not observe a particular network, may omit an incident or may remove an address. Newly assigned addresses and newly detected activity also create timing differences.

Address family not covered means these files do not support an IPv6 membership result. No nearby IPv4 substitute or negative verdict is invented.

Source too old withholds current membership classification. Unavailable preserves the distinction between a failed source and absence. A previous file within its age limit can remain usable with a visible failed-refresh notice.

A Source unavailable result means no usable snapshot could be obtained. This IP reputation check preserves a distinction between a failed request and a negative membership result. If a refresh fails but a previous file remains within the age limit, it can still supply a result with a visible refresh warning. Treat the warning as part of the evidence.

CINS Army: the scope of its public list

CINS Army publishes an address subset of its threat intelligence. It does not expose full incident narratives or individualized scores in this file. A match needs comparison with your own event records.

Emerging Threats: a second source with distinct limits

Emerging Threats Compromised IPs provides a plain address file. Per-entry incident time, confidence and attack category are absent; those details remain unknown rather than inferred from the filename.

Understand the dates and content fingerprint

Source file modified comes from HTTP Last-Modified; Downloaded records retrieval. Neither is an incident timestamp. File content has a SHA-256 fingerprint for comparison, not a publisher signature or proof of observation accuracy.

Source details in the IP reputation check include the number of unique addresses, supported address family and a SHA-256 fingerprint of the downloaded UTF-8 text. An IP reputation check fingerprint identifies file content for comparison. It is not a publisher signature and does not independently authenticate the underlying observations. The source link opens the publisher’s current file, which may have changed.

Shared files refresh at most hourly, with at least fifteen minutes before a retry after failure. Freshness limits are forty-eight hours for CINS Army and seven days for Emerging Threats. They are service limits, not publisher schedules.

What this IP reputation check cannot establish

An IP reputation check is not a malware scan of your device. A compromised machine may use an unlisted address, while an address in a feed may have been reassigned or remediated. To investigate a device, review security alerts, updates, account activity and endpoint protections. Use competent incident-response support when you have evidence of an actual compromise.

Read more

For email delivery, complement the IP reputation check with the mail blacklist checker. Mail-oriented lists use different policies and evidence. A delivery failure may instead involve authentication, sending practices, recipient policy or configuration. Preserve the actual rejection message and inspect the sending server’s address before assuming a general threat feed caused the problem.

Investigate a listing without making assumptions

After a positive IP reputation check, confirm the address and event time against your own records. Determine whether you control the address, rent it from a provider or share it with other users. Review outbound traffic and service logs within your authorization. Avoid testing or scanning someone else’s infrastructure simply because a public file contains an address.

Retain source and date for comparisons. Follow the publisher’s review process with remediation or reassignment evidence when relevant. This website cannot remove an entry or promise a correction time.

Common IP reputation check questions

Why can another service show a different answer?

Another IP reputation check may use paid reports, different sensors, mail lists or proprietary scoring. Compare the named datasets, dates and address families before comparing conclusions. A red badge with no supporting information offers less context than a specific dated observation. We disclose the limited feeds used here rather than claiming comprehensive coverage of every reputation provider.

Can changing my public address solve a listing?

A new address can change an IP reputation check result, but it does not repair a compromised device, stolen account or insecure service. Fix the underlying cause where evidence supports one. Providers also reassign addresses over time, so a listing can predate the current subscriber. Record reassignment evidence instead of assuming either innocence or responsibility from the address alone.

Is an unlisted address safe to allow automatically?

No. An IP reputation check should support a broader decision that includes authentication, behavior, least privilege and operational context. Automatically allowing every unlisted address creates a gap in protection. Automatically blocking every listed address can disrupt legitimate users. Choose controls appropriate to your service and provide a way to review mistaken restrictions.

How is my input handled?

The IP reputation check sends the entered address to our service over HTTPS for matching. The catalog stores public source data and refresh state, not a visitor lookup history. Results are not placed in the URL, browser storage or a shared response cache. Hosting infrastructure still processes requests; see the privacy policy for the wider data flow.

privacy policy

Where can I verify the method and sources?

The IP reputation check follows our testing methodology and source documentation. Read CINS Army’s explanation, the Emerging Threats licensing clarification, and our dataset notices. These links explain provenance and reuse terms; they do not imply that either publisher endorses this website.

testing methodology

source documentation

CINS Army’s explanation

Emerging Threats licensing clarification

dataset notices

Is this the same as a mail-server blacklist test?

No. The named threat feeds and mail delivery lists have different purposes and coverage. If a delivery notice identifies a sending server, check the relevant mail sources separately instead of treating this threat-list result as an explanation for every rejected message.

Does accepting IPv6 mean every feed has IPv6 coverage?

No. Supported input and source coverage are different properties. Read each source’s result and limitations independently. A source that supplies no suitable IPv6 evidence cannot establish the same coverage as a populated IPv4 dataset.

Does a match identify the person responsible for abuse?

No. An address can be shared or reassigned, and a source entry records its own evidence rather than a subscriber identity. Preserve the source and dates when escalating an incident; do not infer an individual from the address alone.