City: Arakawa Ku
Region: Tokyo
Country: Japan
Internet Service Provider: NTT docomo
Hostname: unknown
Organization: unknown
Usage Type: unknown
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See https://docs.db.ripe.net/terms-conditions.html
% Note: this output has been filtered.
% To receive output for a database update, use the "-B" flag.
% Information related to '92.200.0.0 - 92.203.255.255'
% No abuse contact registered for 92.200.0.0 - 92.203.255.255
inetnum: 92.200.0.0 - 92.203.255.255
netname: NON-RIPE-NCC-MANAGED-ADDRESS-BLOCK
descr: IPv4 address block not managed by the RIPE NCC
remarks: ------------------------------------------------------
remarks:
remarks: For registration information,
remarks: you can consult the following sources:
remarks:
remarks: IANA
remarks: http://www.iana.org/assignments/ipv4-address-space
remarks: http://www.iana.org/assignments/iana-ipv4-special-registry
remarks: http://www.iana.org/assignments/ipv4-recovered-address-space
remarks:
remarks: AFRINIC (Africa)
remarks: http://www.afrinic.net/ whois.afrinic.net
remarks:
remarks: APNIC (Asia Pacific)
remarks: http://www.apnic.net/ whois.apnic.net
remarks:
remarks: ARIN (Northern America)
remarks: http://www.arin.net/ whois.arin.net
remarks:
remarks: LACNIC (Latin America and the Carribean)
remarks: http://www.lacnic.net/ whois.lacnic.net
remarks:
remarks: ------------------------------------------------------
country: EU # Country is really world wide
admin-c: IANA1-RIPE
tech-c: IANA1-RIPE
status: ALLOCATED UNSPECIFIED
mnt-by: RIPE-NCC-HM-MNT
created: 2025-07-23T16:30:36Z
last-modified: 2025-07-23T16:30:36Z
source: RIPE
role: Internet Assigned Numbers Authority
address: see http://www.iana.org.
admin-c: IANA1-RIPE
tech-c: IANA1-RIPE
nic-hdl: IANA1-RIPE
remarks: For more information on IANA services
remarks: go to IANA web site at http://www.iana.org.
mnt-by: RIPE-NCC-MNT
created: 1970-01-01T00:00:00Z
last-modified: 2001-09-22T09:31:27Z
source: RIPE # Filtered
% This query was served by the RIPE Database Query Service version 1.123 (ABERDEEN); <<>> DiG 9.10.3-P4-Ubuntu <<>> 92.203.225.242
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 36574
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;92.203.225.242. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026081601 1800 900 604800 86400
;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Aug 17 05:17:16 CST 2026
;; MSG SIZE rcvd: 107242.225.203.92.in-addr.arpa domain name pointer fp5ccbe1f2.tkyc401.ap.nuro.jp.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
242.225.203.92.in-addr.arpa name = fp5ccbe1f2.tkyc401.ap.nuro.jp.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 112.35.75.46 | attackspam | Unauthorized connection attempt detected from IP address 112.35.75.46 to port 2220 [J] |
2020-01-18 13:32:31 |
| 186.225.63.82 | attack | Unauthorized connection attempt detected from IP address 186.225.63.82 to port 8080 [J] |
2020-01-18 13:51:13 |
| 177.84.210.217 | attackbotsspam | Unauthorized connection attempt detected from IP address 177.84.210.217 to port 85 [J] |
2020-01-18 13:54:01 |
| 78.25.122.209 | attackspambots | Unauthorized connection attempt detected from IP address 78.25.122.209 to port 8000 [J] |
2020-01-18 13:37:43 |
| 73.19.208.41 | attackspam | Unauthorized connection attempt detected from IP address 73.19.208.41 to port 9000 [J] |
2020-01-18 13:38:48 |
| 78.169.36.28 | attackspam | Unauthorized connection attempt detected from IP address 78.169.36.28 to port 23 [J] |
2020-01-18 13:37:23 |
| 102.40.233.165 | attack | Unauthorized connection attempt detected from IP address 102.40.233.165 to port 23 [J] |
2020-01-18 14:02:29 |
| 187.59.111.108 | attack | Unauthorized connection attempt detected from IP address 187.59.111.108 to port 23 [J] |
2020-01-18 13:50:16 |
| 106.54.124.250 | attack | Jan 18 06:20:23 localhost sshd\[26460\]: Invalid user casa from 106.54.124.250 Jan 18 06:20:23 localhost sshd\[26460\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.124.250 Jan 18 06:20:25 localhost sshd\[26460\]: Failed password for invalid user casa from 106.54.124.250 port 51334 ssh2 Jan 18 06:22:10 localhost sshd\[26507\]: Invalid user gerrard from 106.54.124.250 Jan 18 06:22:10 localhost sshd\[26507\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.124.250 ... |
2020-01-18 13:59:59 |
| 106.12.176.188 | attack | Unauthorized connection attempt detected from IP address 106.12.176.188 to port 2220 [J] |
2020-01-18 13:34:31 |
| 49.51.10.24 | attackspambots | Unauthorized connection attempt detected from IP address 49.51.10.24 to port 5269 [J] |
2020-01-18 13:40:52 |
| 211.154.6.65 | attackbots | Unauthorized connection attempt detected from IP address 211.154.6.65 to port 1433 [J] |
2020-01-18 13:46:30 |
| 117.144.121.123 | attackspambots | Unauthorized connection attempt detected from IP address 117.144.121.123 to port 23 [J] |
2020-01-18 13:58:29 |
| 36.72.2.182 | attack | Unauthorized connection attempt detected from IP address 36.72.2.182 to port 4567 [J] |
2020-01-18 14:08:40 |
| 112.111.0.245 | attackbots | Unauthorized connection attempt detected from IP address 112.111.0.245 to port 2220 [J] |
2020-01-18 13:32:05 |