IPv4 address
3.136.119.21
Last fetched
3.136.119.21 is announced in 3.136.0.0/13 by AMAZON-02 - Amazon.com, Inc. and geolocates to US. 3.136.119.21 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
- 3.136.0.0/13
- Announcing network
- AMAZON-02 - Amazon.com, Inc.
- RIR-registered prefix
- 3.128.0.0/9
- 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
- ec2-3-136-119-21.us-east-2.compute.amazonaws.com
- amp.code.storage
- anthropic.code.storage
- anything.code.storage
- basehub.code.storage
- lovable-us.code.storage
- million.code.storage
- openai.code.storage
- parahelp.code.storage
- relace.code.storage
- steercode.code.storage
- strapi-staging.code.storage
- tldraw.code.storage
- vybe.code.storage
- vybe-staging.code.storage
- weaver.code.storage
- amp.git.storage
- anthropic.git.storage
- anysphere.git.storage
- anything.git.storage
- api.git.storage
- basehub.git.storage
- bragai.git.storage
- lovable-us.git.storage
- million.git.storage
- moment-staging.git.storage
- morph.git.storage
- openai.git.storage
- orchids.git.storage
- parahelp.git.storage
- pierre.git.storage
- relace.git.storage
- stackblitz.git.storage
- steercode.git.storage
- strapi.git.storage
- strapi-staging.git.storage
- tldraw.git.storage
- v0.git.storage
- vybe.git.storage
- vybe-staging.git.storage
- hercules.code.storage
- alan.git.storage
- 65fn.git.storage
- endex.code.storage
- slider.code.storage
- gitbutler.git.storage
- vendpark.git.storage
- bitrig-staging.git.storage
- t3.git.storage
- t3.code.storage
Geographic detail
- City
- Dublin, US
- Country
- US
Threat-feed evidence
History
Related pages
Pivot from 3.136.119.21 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: "3.136.119.21"})
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.