IPure IP purity check

IP purity report

8.8.8.8

Google Public DNS

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-09-19 14:35 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 · Virginia · Ashburn
IP type
Hosting / data center
Native / broadcast
Native IP
Network
AS15169 Google Public DNS
Reverse DNS
dns.google
Devices seen in subnet
6

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

  • −6

    2 open ports

    Open ports: 53, 443

  • +4

    Very low observed sharing

    Only 6 devices observed in the same subnet

  • +5

    Native IP

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

  • +15

    Whitelisted IP

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

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%, 203 reports in 90 days

Open ports observed: 53, 443

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
    172ms
  • team-cymru
    94ms
  • ip-api.com
    89ms
  • proxycheck.io
    113ms
  • abuseipdb
    125ms
  • cloud-ranges
    22ms
  • tor-exits
    22ms
  • rdns
    1019ms
  • shodan-internetdb
    89ms
  • ipwho.is
    83ms
  • dnsbl
    222ms

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