RDAP WHOIS lookup of '134.160.187.0'

RDAP response recieved from apnic.net in a total of 704ms

134.160.0.0/16

Handle:
134.160.0.0 - 134.160.255.255
Name:
RIKEN-NET
Type:
ASSIGNED PORTABLE
Country:
JP

CIDR:
134.160.0.0/16

Remarks:
RIKEN

Events

Created:
04-09-2008
Last change:
13-07-2022

Administrative, Technical

Handle:
IS284-AP
 
Individual
Name:
Information Systems Division
Adress:
2-1 Hirosawa, Wako, Saitama 351-0198, Japan
Contact:
voice +81-50-3502-2817
voice +81-50-3500-6037
accc-net@ml.riken.jp

Abuse

Handle:
IRT-JPNIC-JP
 
Group
Name:
IRT-JPNIC-JP
Adress:
Uchikanda OS Bldg 4F, 2-12-6 Uchi-Kanda
Chiyoda-ku, Tokyo 101-0047, Japan
Contact:
voice +81-3-5297-2311
fax +81-3-5297-2312
hostmaster@nic.ad.jp
hostmaster@nic.ad.jp

Raw RDAP response

Click here to see the raw RDAP response from apnic.net (3.321 bytes of JSON data). Opens as modal.

API

You may perform this lookup using the API and get the results as easy-to-parse JSON data.

Read more on the API at https://iamroot.tech/about/api (regarding authentication and rate limits, among other things), or give it a go right away using the 'try it' button.

 
GET
 https://iamroot.tech/whois/api/?host=134.160.187.0 copy try it
 

Log

000+000
  • Try RDAP lookup
707+707
  • Figure out server to ask
707+000
  • Asking 'whois.iana.org' for info on '134.160.187.0' - recieved a valid response of 311 bytes in 118ms.
707+000
  • IP is managed by arin.net. Response from IANA WHOIS in 185ms.
707+000
  • Starting lookup
707+000
  • Querying 'arin.net' for RDAP info on '134.160.187.0'. Response in 147ms. Got redirected (via http location) to 'apnic.net'.
707+000
  • Querying 'apnic.net' for RDAP info on '134.160.187.0'. Response in 219ms.
707+000
  • Done
New features inbound 🚀
Within a couple of weeks, I'll launch a couple of new awesome features. Signup for the newsletter to stay updated, and get early access as a beta tester.

Signup using Google, Microsoft or Facebook .