IPv4 address
75.2.2.136
Last fetched
75.2.2.136 is announced in 75.2.0.0/20 by AMAZON-02 - Amazon.com, Inc. and geolocates to US. 75.2.2.136 is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- no-data
Nutrition Label
Attribution
- Announced prefix
- 75.2.0.0/20
- Announcing network
- AMAZON-02 - Amazon.com, Inc.
- RIR-registered prefix
- 75.2.0.0/17
- RPKI
- valid
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
- 107.clientpoint.net
- 18.clientpoint.net
- 3.clientpoint.net
- 34.clientpoint.net
- 35.clientpoint.net
- 52.clientpoint.net
- 54.clientpoint.net
- bluespinach.clientpoint.net
- canningstreetyoga.clientpoint.net
- docstore.clientpoint.net
- flavourscatering.clientpoint.net
- fr.clientpoint.net
- mx.fr.clientpoint.net
- 1.mx.fr.clientpoint.net
- sql.fr.clientpoint.net
- 1.sql.fr.clientpoint.net
- staceycain.fr.clientpoint.net
- www.fr.clientpoint.net
- 1.www.fr.clientpoint.net
- harisisani.clientpoint.net
- imr.clientpoint.net
- levitateholding.clientpoint.net
- lionsharepartners.clientpoint.net
- login.clientpoint.net
- messagingarchitects.clientpoint.net
- mx.clientpoint.net
- my.clientpoint.net
- ns.clientpoint.net
- 1.ns.clientpoint.net
- 2.ns.clientpoint.net
- 3.ns.clientpoint.net
- 4.ns.clientpoint.net
- pdftron-test.clientpoint.net
- proposal.clientpoint.net
- shanelundy.clientpoint.net
- staceycain.clientpoint.net
- uk.clientpoint.net
- mini.uk.clientpoint.net
- 1.mini.uk.clientpoint.net
- veganhippo.clientpoint.net
- webmail.clientpoint.net
- wildcard.clientpoint.net
Geographic detail
- City
- Seattle, US
- Country
- US
- Dominant city of the prefix
- Seattle, US
Threat-feed evidence
History
Related pages
Pivot from 75.2.2.136 into the prefix, network and country that carry it.
Cypher and MCP
Reproduce this address's routing attribution against graph.whisper.security:
MATCH (ip:IPV4 {name: "75.2.2.136"})
OPTIONAL MATCH (ip)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(c:COUNTRY)
RETURN ap.name AS prefix, a.name AS asn, n.name AS network, c.name AS countryOr query Whisper from your own LLM workflow via the Whisper MCP server.