IPure IP purity check

IP purity report

208.67.222.222

OpenDNS

93/ 100

Clean

confidence: high

Good reputation; at the IP level it rarely draws extra verification.

Based on signals observed from public and partner data sources at 2026-10-26 07:30 UTC. This describes IP-level risk only; platforms' internal risk data is not visible to us.

Profile

What this IP is

Country / region
United States · California · San Jose
IP type
Hosting / data center
Native / broadcast
Native IP
Network
AS36692 Cisco OpenDNS, LLC
Reverse DNS
dns.umbrella.com
Devices seen in subnet
3

Suitability

What it is good for

Each use case weighs the evidence differently; these are not one overall score.

Per-use-case suitability does not apply

This is a public DNS service address, not a network exit that users can browse from, so there is nothing to log in or sign up from. The purity score only describes its network reputation.

Evidence

Why it got this score

  • −25

    IP type: Hosting / data center

    Hosting / data center IPs are the main source of automated traffic

    What it means
    This IP sits in a hosting / datacenter range. Platforms assume real people browse from home or a phone, and machines live in datacenters.
    Which uses care
    Cares most: AI services, Social sign-up, Gaming platforms, Cross-border e-commerce; Barely looks at it: Email sending
    Why it is weighted this way
    The most basic signal there is: scrapers, bulk sign-ups and fake traffic overwhelmingly come from datacenters, so risk systems discount the whole range. It says nothing about what you did, only that you share the range.
    Can it be fixed
    The range type cannot be changed. What helps is not stacking other issues on top: stay off blocklists, close unneeded ports, avoid crowded exits.
  • −6

    4 open ports

    Open ports: 53, 80, 443, 5353

    What it means
    Scanners see ports open on this IP. With admin ports such as 22 or 3389 it is almost certainly a server, not a home router.
    Which uses care
    Barely looks at it: AI services
    Why it is weighted this way
    Mainly corroboration that "this is a server", which the datacenter item already charged for, so only a few points here; AI-type scenarios weight it at 0.3 to avoid charging the same fact three times.
    Can it be fixed
    Close or restrict ports that do not need public access (firewall, non-default port, fail2ban); scanners update within days, then re-check. One of the few items you can change yourself.
  • +4

    Very low observed sharing

    Only 3 devices observed in the same subnet

    What it means
    Only a few devices were observed in the same subnet. Your behaviour mostly represents you alone.
    Which uses care
    Cares most: Social sign-up, Streaming / short video, Cross-border e-commerce
    Why it is weighted this way
    A small bonus. This is an observation, not proof of true exclusivity.
    Can it be fixed
    An inherent attribute of the IP or its range; nothing a user can change short of a different IP.
  • +5

    Native IP

    Registered and used in the same country, allocated directly by a local carrier

    What it means
    Registered and used in the same country, allocated directly by a local carrier: a "native IP".
    Which uses care
    Cares most: Streaming / short video, Gaming platforms; Barely looks at it: Email sending
    Why it is weighted this way
    A bonus: region-based checks will not trip.
    Can it be fixed
    An inherent attribute of the IP or its range; nothing a user can change short of a different IP.
  • +15

    Whitelisted IP

    Listed as an official address of a well-known service or crawler

    What it means
    This address is listed as the official IP of a well-known service or search engine.
    Which uses care
    All six uses treat it about the same, at the same weight as the overall score.
    Why it is weighted this way
    A bonus, and it also means this is nobody's egress, so scenario assessment does not apply.
    Can it be fixed
    An inherent attribute of the IP or its range; nothing a user can change short of a different IP.

Reputation

Blocklists and abuse history

Not listed on any of the 8 blocklists checked (Spamhaus ZEN, SpamCop, PSBL, blocklist.de, UCEPROTECT L1, s5h.net, DroneBL, SpamRats).

  • abuseipdb abuse confidence 0%, 7 reports in 90 days

Open ports observed: 53, 80, 443, 5353

Limits

What an IP check cannot tell you

Each platform's internal risk labels
Platforms keep their own IP reputation data and ban records and do not publish them. No hit in public sources does not mean a platform has nothing on this IP.
Whether the IP is truly exclusive
Sharing is only the number of devices observed in the same subnet. It cannot show who else is using this exit right now, or what they are doing.
Which accounts this IP has been tied to
Account-to-IP links exist only inside each platform. Accounts previously banned on this IP are invisible to us.
Device, browser and behaviour
Risk systems look at IP + device fingerprint + behavioural rhythm together. A clean IP with an odd fingerprint or behaviour still gets blocked.
Whether the account profile matches the IP
When sign-up country, phone number, payment method, language or time zone disagree with the IP's location, platforms verify further. That is unrelated to IP purity.

Sources

Data sources and responses

  • rdap
    206ms
  • team-cymru
    59ms
  • ip-api.com
    99ms
  • proxycheck.io
    147ms
  • abuseipdb
    98ms
  • cloud-ranges
    9ms
  • tor-exits
    9ms
  • rdns
    370ms
  • shodan-internetdb
    90ms
  • dnsbl
    216ms

Machine-readable versions of this report: JSON · plain text · 中文报告