IPv4 address
116.162.51.217
Last fetched
116.162.51.217 is announced in 116.162.0.0/16 by CHINA169-Backbone - CHINA UNICOM China169 Backbone and geolocates to CN. 116.162.51.217 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
- 116.162.0.0/16
- Announcing network
- CHINA169-Backbone - CHINA UNICOM China169 Backbone
- RIR-registered prefix
- 116.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
- www.360mon.cn
- sdk.babigame.cn
- www.bjyuanlai.cn
- gwm.com.cn
- haval.com.cn
- statres.quickapp.cn
- preview.21cnjy.com
- community-hs.233leyuan.com
- html.baizlink.com
- zx-img-v4.bytegslb.com
- m.cdfancy.com
- cipanqingli.com
- ganjutech.com
- iduba.com
- static-prod.ituchong.com
- jiansheku.com
- qihuiai.com
- shihengtech.com
- shuiyinyun.com
- sucaicloud.com
- xinyiwan.com
- www.xinyiwan.com
- m.xunche.com
- www.zhaosheng.com
- activity.gongkaoleida.net
- dubbing.tech
- tangshuojiaoyu.top
- easyclaw.cn
- root-certs-verify-globalsign.meituan.net
- sz-mt-v4.volcgtm.com
- p5-sign.douyinpic.com.yangyi19.com
- w-quic.meituan.net
- cdn-qh360br-kantu.yuanqidesk.com
- game-cdn.acmemob.com
- volcdn.deerlingo.com
- w.jichengzhidao.com
- xiaoe.lingshipyjy.com
- douyin.binxiangvideo.cn
- tf.zms18.cn
- w.houniaoshengwu.com
- www.tangshuojiaoyu.top
- xet.hzxuwen.cn
- volcengine.layaidea.com
- cdn.aixinhe.com
- minilive260423.fjzxzq.com
- mail.laohanguihua.com
- a.nlqy.asia
- h5.zhijiantiaodongwh.cn
- xiaoet.szjinmu.top
- a.xinhuashuyuan.net
Geographic detail
- City
- Beijing, CN
- Country
- CN
Threat-feed evidence
History
Related pages
Pivot from 116.162.51.217 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: "116.162.51.217"})
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.