IPv4 address
160.16.146.135
Last fetched
160.16.146.135 is announced in 160.16.128.0/17 by SAKURA-B - SAKURA Internet Inc. and geolocates to JP. 160.16.146.135 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
- 160.16.128.0/17
- Announcing network
- SAKURA-B - SAKURA Internet Inc.
- RIR-registered prefix
- 160.16.0.0/16
- 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
- mailyweb.com
- tokyo2-130.mailyweb.com
- www.mailyweb.com
- makareus.com
- globalserv.hmy.makareus.com
- www.makareus.com
- surgespace.com
- corptokyo2.surgespace.com
- corpwebo.surgespace.com
- corpwebr.surgespace.com
- partner.surgespace.com
- www.surgespace.com
- surgespacenetworks.com
- www.surgespacenetworks.com
- surgestar.com
- 0-0-0-tokyo2.surgestar.com
- www.surgestar.com
- undersnow.com
- bn.cx
- www.bn.cx
- comingup.jp
- digitalswift.jp
- www.digitalswift.jp
- incoming.jp
- go.incoming.jp
- ijp134o.incoming.jp
- ijp134r.incoming.jp
- ijp135o.incoming.jp
- ijp139o.incoming.jp
- ijp139r.incoming.jp
- ijp143o.incoming.jp
- ijp143r.incoming.jp
- mb138r.incoming.jp
- rumikan.incoming.jp
- www.incoming.jp
- xero.incoming.jp
- yam.incoming.jp
- yamaty.incoming.jp
- tk2-409-45631.vs.sakura.ne.jp
- buttobi.net
- adv.buttobi.net
- bc.buttobi.net
- com.buttobi.net
- www.com.buttobi.net
- linkstaff.buttobi.net
- www.linkstaff.buttobi.net
- wave.buttobi.net
- www.wave.buttobi.net
- www.buttobi.net
- digitalswift.net
Geographic detail
- City
- Osaka, JP
- Country
- JP
- Dominant city of the prefix
- Osaka, JP
Threat-feed evidence
History
Related pages
Pivot from 160.16.146.135 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: "160.16.146.135"})
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.