Skip to content

IPv4 address

127.0.0.2

Last fetched

127.0.0.2 is an IPv4 address in WhisperGraph with no current BGP announcement covering it. 127.0.0.2 is listed by 18 threat feeds; reconciled level INFO.

Threat posture

0threat score (procedure-native scale)

INFO

Listed by 18 threat feeds. Advisory: allowlist-vouched.

Threat feeds listing this
18
Verdict coverage
known-clean
First seen on a feed
Wed, 26 Aug 2026 14:45:21 GMT
Last seen on a feed
Sun, 22 Nov 2026 08:01:16 GMT

Nutrition Label

WHISPER CANON · 127.0.0.2Routing diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings1.5/10WHOIS transparency—Resolver footprint—canon.whisper.security/ip/127.0.0.2

Attribution

127.0.0.2 is not currently announced in BGP. It has no routing attribution in WhisperGraph.

Network context

Attributed threat actor
Axiom

Anycast detection

This does not appear to be an anycast address on the three signals Canon evaluates: reverse DNS, announced-prefix width and the announcing network's peer count.

Reverse DNS

Threat-feed listings

  • maltrail-static-malware-apt-kimsuky-ip · c2
  • usom-urls-ip · phishing
  • scamsniffer-blacklist-ip · crypto-scam
  • romainmarcoux-malicious-ab-ip · blacklists
  • bambenek-dga-high-ip · malicious-domains
  • interserver-level1 · blacklists
  • phishing-army-ip · phishing
  • maltrail-static-malware-asyncrat-ip · c2
  • tw-165-suspended-ip · consumer-scam
  • romainmarcoux-malicious-aa-ip · blacklists
  • cert-pl-domains-ip · malicious-domains
  • phishing-database-domains-ip · phishing
  • phishdestroy-destroylist-ip · phishing
  • hagezi-dyndns-ip · reputation
  • hagezi-tif-full-ip · malware-distribution
  • abuse-ch-threatfox-domain-ip · c2
  • maltrail-static-malware-cobaltstrike-2-ip · c2
  • metamask-eth-phishing-detect-ip · phishing

Threat-feed evidence

History

Related pages

Pivot from 127.0.0.2 into the prefix, network and country that carry it.

Queries

This address's full card — routing attribution, reverse DNS and listed feeds.


MATCH (ip:IPV4 {name: $ip})
OPTIONAL MATCH (ip)-[:BELONGS_TO]->(rp:REGISTERED_PREFIX)
OPTIONAL MATCH (ip)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
OPTIONAL MATCH (a:ASN)-[:ROUTES]->(ap) WHERE a.name IS NOT NULL
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (ip)-[:LOCATED_IN]->(city:CITY)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(ipc:COUNTRY)
WITH ip, rp, ap, a, an, city, ipc
LIMIT 10
WITH ip,
     collect(rp.name) AS registeredPrefixes,
     collect(rp.abuseEmail) AS registeredAbuseEmails,
     collect({prefix: ap.name, asn: a.name, network: an.name, isMoas: ap.isMoas, rpkiStatus: ap.rpkiStatus, isAnycast: ap.isAnycast, dominantCity: ap.dominantCity, abuseEmail: ap.abuseEmail, networkAbuseEmail: a.abuseEmail}) AS announcements,
     collect(city.name) AS cities,
     collect(ipc.name) AS countries,
     collect(a.name) AS announcerNames,
     head(collect(a)) AS primaryAsn,
     head(collect(ap)) AS primaryPrefix
OPTIONAL MATCH (primaryPrefix)-[:CONFLICTS_WITH]->(conflict:ASN) WHERE conflict.name IS NOT NULL
WITH ip, registeredPrefixes, registeredAbuseEmails, announcements, cities, countries, announcerNames, primaryAsn,
     collect(conflict.name) AS conflictAsns
CALL { WITH primaryAsn MATCH (primaryAsn)-[:ROUTES]->(p:ANNOUNCED_PREFIX) RETURN count(p) AS asnPrefixCount }
CALL { WITH primaryAsn MATCH (primaryAsn)-[:BGP_NEIGHBOR]-(peer:ASN) RETURN count(peer) AS asnPeerCount }
RETURN ip.name AS name,
       ip.verdictLevel AS verdictLevel,
       ip.verdictScore AS verdictScore,
       ip.verdictBlocking AS verdictBlocking,
       ip.verdictCoverage AS verdictCoverage,
       ip.verdictAdvisory AS verdictAdvisory,
       ip.threatSources AS threatSources,
       ip.threatFirstSeen AS threatFirstSeen,
       ip.threatLastSeen AS threatLastSeen,
       ip.isTor AS isTor,
       ip.isVpn AS isVpn,
       ip.isProxy AS isProxy,
       ip.isC2 AS isC2,
       ip.isPhishing AS isPhishing,
       registeredPrefixes, registeredAbuseEmails, announcements, cities, countries, announcerNames, conflictAsns,
       asnPrefixCount, asnPeerCount
Run yourself →

Network context — Tor exit relays, attributed actors, and the covering blocks' signals, cloud region and vendor.


MATCH (ip:IPV4 {name: $ip})
OPTIONAL MATCH (ip)-[:OPERATES_EXIT_NODE]->(tor:TOR_RELAY)
WITH ip, count(tor) AS torRelays
OPTIONAL MATCH (ip)-[:ATTRIBUTED_TO]->(actor:ACTOR)
WITH ip, torRelays, collect(actor.name)[0..5] AS actors
OPTIONAL MATCH (ip)-[:BELONGS_TO]->(p:PREFIX)
WITH torRelays, actors, collect(p.name) AS coveringPrefixes
UNWIND (CASE WHEN size(coveringPrefixes) = 0 THEN [null] ELSE coveringPrefixes END) AS pn
OPTIONAL MATCH (cp:PREFIX {name: pn})
OPTIONAL MATCH (cp)-[:HAS_SIGNAL]->(sig:THREAT_SIGNAL_TYPE)
OPTIONAL MATCH (cp)-[:PREFIX_IN_REGION]->(reg:CLOUD_REGION)
OPTIONAL MATCH (cp)-[:DELEGATED_TO]->(v:VENDOR)
RETURN torRelays, actors,
       collect(sig.name) AS signals,
       collect(reg.name) AS regions,
       collect(v.name) AS vendors
Run yourself →

Or query Whisper from your own LLM workflow via the Whisper MCP server.