IPv4 address
8.136.9.42
Last fetched
8.136.9.42 is announced in 8.136.0.0/17 by ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd. and geolocates to CN. 8.136.9.42 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
- 8.136.0.0/17
- Announcing network
- ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd.
- RIR-registered prefix
- 8.128.0.0/10
- 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
- ad2.0574dc.com
- m.0574dc.com
- 2sc.eyuyao.com
- ad.eyuyao.com
- ad2.eyuyao.com
- app.eyuyao.com
- auto.eyuyao.com
- audiaudi.auto.eyuyao.com
- bhmc.auto.eyuyao.com
- breezemu.auto.eyuyao.com
- bydbyd.auto.eyuyao.com
- changan.auto.eyuyao.com
- chsuzuki.auto.eyuyao.com
- cixiludehang.auto.eyuyao.com
- dffs.auto.eyuyao.com
- gacyyyy.auto.eyuyao.com
- hd132.auto.eyuyao.com
- honda.auto.eyuyao.com
- huade.auto.eyuyao.com
- huatai.auto.eyuyao.com
- junjia.auto.eyuyao.com
- toyota.auto.eyuyao.com
- yinglun.auto.eyuyao.com
- yuyaobaofeng.auto.eyuyao.com
- yuyaobh.auto.eyuyao.com
- yuyaodongjiang.auto.eyuyao.com
- yuyaohengtian.auto.eyuyao.com
- yuyaohuade.auto.eyuyao.com
- yuyaohuake.auto.eyuyao.com
- yuyaoningxing.auto.eyuyao.com
- yuyaoshenzhe.auto.eyuyao.com
- yuyaoxinlongjili.auto.eyuyao.com
- yyaodi.auto.eyuyao.com
- yyford.auto.eyuyao.com
- yykangda.auto.eyuyao.com
- yyxfl.auto.eyuyao.com
- yyxj.auto.eyuyao.com
- yyxtl.auto.eyuyao.com
- yyys.auto.eyuyao.com
- erp.eyuyao.com
- game.eyuyao.com
- home.eyuyao.com
- m.eyuyao.com
- wj.eyuyao.com
- wz.eyuyao.com
- wz2.eyuyao.com
- yyad.eyuyao.com
Geographic detail
- City
- Hangzhou, CN
- Country
- CN
- Dominant city of the prefix
- Hangzhou, CN
Threat-feed evidence
History
Related pages
Pivot from 8.136.9.42 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: "8.136.9.42"})
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.