City: Tokyo
Region: Tokyo
Country: Japan
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
NetRange: 160.11.0.0 - 160.18.255.255
CIDR: 160.16.0.0/15, 160.11.0.0/16, 160.12.0.0/14, 160.18.0.0/16
NetName: APNIC
NetHandle: NET-160-11-0-0-1
Parent: NET160 (NET-160-0-0-0-0)
NetType: Early Registrations, Transferred to APNIC
OriginAS:
Organization: Asia Pacific Network Information Centre (APNIC)
RegDate: 2016-09-02
Updated: 2016-09-02
Ref: https://rdap.arin.net/registry/ip/160.11.0.0
OrgName: Asia Pacific Network Information Centre
OrgId: APNIC
Address: PO Box 3646
City: South Brisbane
StateProv: QLD
PostalCode: 4101
Country: AU
RegDate:
Updated: 2012-01-24
Ref: https://rdap.arin.net/registry/entity/APNIC
ReferralServer: whois://whois.apnic.net
ResourceLink: http://wq.apnic.net/whois-search/static/search.html
OrgTechHandle: AWC12-ARIN
OrgTechName: APNIC Whois Contact
OrgTechPhone: +61 7 3858 3188
OrgTechEmail: search-apnic-not-arin@apnic.net
OrgTechRef: https://rdap.arin.net/registry/entity/AWC12-ARIN
OrgAbuseHandle: AWC12-ARIN
OrgAbuseName: APNIC Whois Contact
OrgAbusePhone: +61 7 3858 3188
OrgAbuseEmail: search-apnic-not-arin@apnic.net
OrgAbuseRef: https://rdap.arin.net/registry/entity/AWC12-ARIN
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
Found a referral to whois.apnic.net.
% [whois.apnic.net]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html
% Information related to '160.16.0.0 - 160.16.255.255'
% Abuse contact for '160.16.0.0 - 160.16.255.255' is 'hostmaster@nic.ad.jp'
inetnum: 160.16.0.0 - 160.16.255.255
netname: SAKURA
descr: SAKURA Internet Inc.
descr: GRAND GREEN OSAKA North, JAM BASE 3F, 6-38 Ofukacho, Kita-ku, Osaka-shi, Osaka 530-0011, Japan
country: JP
admin-c: JNIC1-AP
tech-c: JNIC1-AP
status: ALLOCATED PORTABLE
remarks: Email address for spam or abuse complaints : abuse@sakura.ad.jp
mnt-irt: IRT-JPNIC-JP
mnt-by: MAINT-JPNIC
mnt-lower: MAINT-JPNIC
last-modified: 2024-09-29T23:29:57Z
source: APNIC
irt: IRT-JPNIC-JP
address: Uchikanda OS Bldg 4F, 2-12-6 Uchi-Kanda
address: Chiyoda-ku, Tokyo 101-0047, japan
e-mail: hostmaster@nic.ad.jp
abuse-mailbox: hostmaster@nic.ad.jp
phone: +81-3-5297-2311
fax-no: +81-3-5297-2312
admin-c: JNIC1-AP
tech-c: JNIC1-AP
auth: # Filtered
remarks: hostmaster@nic.ad.jp was validated on 2024-11-27
mnt-by: MAINT-JPNIC
last-modified: 2025-09-04T01:00:00Z
source: APNIC
role: Japan Network Information Center
address: Uchikanda OS Bldg 4F, 2-12-6 Uchi-Kanda
address: Chiyoda-ku, Tokyo 101-0047, Japan
country: JP
phone: +81-3-5297-2311
fax-no: +81-3-5297-2312
e-mail: hostmaster@nic.ad.jp
admin-c: JI13-AP
tech-c: JE53-AP
nic-hdl: JNIC1-AP
mnt-by: MAINT-JPNIC
last-modified: 2022-01-05T03:04:02Z
source: APNIC
% Information related to '160.16.124.0 - 160.16.124.255'
inetnum: 160.16.124.0 - 160.16.124.255
netname: SAKURA-NET
descr: SAKURA Internet Inc.
country: JP
admin-c: KT749JP
tech-c: JP00072233
last-modified: 2014-10-08T21:44:03Z
remarks: This information has been partially mirrored by APNIC from
remarks: JPNIC. To obtain more specific information, please use the
remarks: JPNIC WHOIS Gateway at
remarks: http://www.nic.ad.jp/en/db/whois/en-gateway.html or
remarks: whois.nic.ad.jp for WHOIS client. (The WHOIS client
remarks: defaults to Japanese output, use the /e switch for English
remarks: output)
source: JPNIC
% This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-AU4)
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 160.16.124.107
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17895
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;160.16.124.107. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026042501 1800 900 604800 86400
;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Apr 26 07:30:22 CST 2026
;; MSG SIZE rcvd: 107
107.124.16.160.in-addr.arpa domain name pointer tk2-238-28603.vs.sakura.ne.jp.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
107.124.16.160.in-addr.arpa name = tk2-238-28603.vs.sakura.ne.jp.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 106.12.16.234 | attackbotsspam | Dec 2 13:52:17 hcbbdb sshd\[6688\]: Invalid user test from 106.12.16.234 Dec 2 13:52:17 hcbbdb sshd\[6688\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.16.234 Dec 2 13:52:20 hcbbdb sshd\[6688\]: Failed password for invalid user test from 106.12.16.234 port 45634 ssh2 Dec 2 14:00:11 hcbbdb sshd\[7619\]: Invalid user tsmuse from 106.12.16.234 Dec 2 14:00:11 hcbbdb sshd\[7619\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.16.234 |
2019-12-02 23:02:50 |
| 220.246.26.51 | attackspambots | ssh failed login |
2019-12-02 23:19:45 |
| 41.41.0.14 | attackbotsspam | Dec 02 16:35:52 auth-worker(31761): Info: sql(mobobmen-minsk@htcd.gov.by,41.41.0.14, |
2019-12-02 23:10:36 |
| 51.38.186.47 | attackspam | Dec 2 15:23:05 web8 sshd\[14862\]: Invalid user pcbtools from 51.38.186.47 Dec 2 15:23:05 web8 sshd\[14862\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.186.47 Dec 2 15:23:07 web8 sshd\[14862\]: Failed password for invalid user pcbtools from 51.38.186.47 port 56532 ssh2 Dec 2 15:28:42 web8 sshd\[17571\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.186.47 user=root Dec 2 15:28:44 web8 sshd\[17571\]: Failed password for root from 51.38.186.47 port 39848 ssh2 |
2019-12-02 23:35:07 |
| 188.254.0.170 | attack | Nov 24 20:21:12 microserver sshd[5107]: Invalid user racz from 188.254.0.170 port 43816 Nov 24 20:21:12 microserver sshd[5107]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.170 Nov 24 20:21:14 microserver sshd[5107]: Failed password for invalid user racz from 188.254.0.170 port 43816 ssh2 Nov 24 20:27:58 microserver sshd[5859]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.170 user=root Nov 24 20:28:00 microserver sshd[5859]: Failed password for root from 188.254.0.170 port 50500 ssh2 Nov 24 20:41:17 microserver sshd[7757]: Invalid user okkyii from 188.254.0.170 port 35632 Nov 24 20:41:17 microserver sshd[7757]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.170 Nov 24 20:41:19 microserver sshd[7757]: Failed password for invalid user okkyii from 188.254.0.170 port 35632 ssh2 Nov 24 20:48:03 microserver sshd[8524]: Invalid user undernet from 188.254.0.170 |
2019-12-02 22:58:20 |
| 154.209.5.49 | attackspam | Dec 2 15:48:30 legacy sshd[27182]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.209.5.49 Dec 2 15:48:31 legacy sshd[27182]: Failed password for invalid user santo from 154.209.5.49 port 46326 ssh2 Dec 2 15:55:12 legacy sshd[27345]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.209.5.49 ... |
2019-12-02 23:04:13 |
| 185.209.0.97 | attackspam | RDPBruteCAu |
2019-12-02 23:34:33 |
| 125.227.130.5 | attackbots | Dec 2 15:17:40 minden010 sshd[22962]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.227.130.5 Dec 2 15:17:42 minden010 sshd[22962]: Failed password for invalid user byer from 125.227.130.5 port 38403 ssh2 Dec 2 15:23:47 minden010 sshd[24920]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.227.130.5 ... |
2019-12-02 23:23:11 |
| 111.230.53.144 | attack | Dec 2 14:26:54 MainVPS sshd[19035]: Invalid user kore from 111.230.53.144 port 51562 Dec 2 14:26:54 MainVPS sshd[19035]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.230.53.144 Dec 2 14:26:54 MainVPS sshd[19035]: Invalid user kore from 111.230.53.144 port 51562 Dec 2 14:26:56 MainVPS sshd[19035]: Failed password for invalid user kore from 111.230.53.144 port 51562 ssh2 Dec 2 14:35:47 MainVPS sshd[2548]: Invalid user guest from 111.230.53.144 port 35942 ... |
2019-12-02 23:20:28 |
| 106.12.128.24 | attack | 2019-12-02T14:17:09.360595shield sshd\[16882\]: Invalid user cobbe from 106.12.128.24 port 38700 2019-12-02T14:17:09.365231shield sshd\[16882\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.128.24 2019-12-02T14:17:11.192723shield sshd\[16882\]: Failed password for invalid user cobbe from 106.12.128.24 port 38700 ssh2 2019-12-02T14:25:43.105327shield sshd\[18225\]: Invalid user mohsin from 106.12.128.24 port 47514 2019-12-02T14:25:43.109962shield sshd\[18225\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.128.24 |
2019-12-02 23:16:31 |
| 27.105.103.3 | attackspambots | Dec 2 15:07:08 meumeu sshd[9011]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.105.103.3 Dec 2 15:07:09 meumeu sshd[9011]: Failed password for invalid user webmaster from 27.105.103.3 port 54288 ssh2 Dec 2 15:13:25 meumeu sshd[10049]: Failed password for root from 27.105.103.3 port 36810 ssh2 ... |
2019-12-02 23:16:47 |
| 118.238.4.201 | attack | WordPress login Brute force / Web App Attack on client site. |
2019-12-02 23:23:31 |
| 42.114.13.80 | attackspambots | phishing |
2019-12-02 23:03:15 |
| 220.225.126.55 | attackspambots | Dec 2 05:12:10 php1 sshd\[23220\]: Invalid user ident from 220.225.126.55 Dec 2 05:12:10 php1 sshd\[23220\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.225.126.55 Dec 2 05:12:13 php1 sshd\[23220\]: Failed password for invalid user ident from 220.225.126.55 port 49016 ssh2 Dec 2 05:19:11 php1 sshd\[24091\]: Invalid user pp from 220.225.126.55 Dec 2 05:19:11 php1 sshd\[24091\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.225.126.55 |
2019-12-02 23:21:32 |
| 180.76.105.165 | attackbotsspam | Jun 21 04:10:51 vtv3 sshd[27890]: Invalid user test1 from 180.76.105.165 port 56576 Jun 21 04:10:51 vtv3 sshd[27890]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.105.165 Jun 21 04:10:53 vtv3 sshd[27890]: Failed password for invalid user test1 from 180.76.105.165 port 56576 ssh2 Jun 21 04:22:24 vtv3 sshd[734]: Invalid user ts3 from 180.76.105.165 port 46132 Jun 21 04:22:24 vtv3 sshd[734]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.105.165 Jun 21 04:22:26 vtv3 sshd[734]: Failed password for invalid user ts3 from 180.76.105.165 port 46132 ssh2 Jun 21 04:23:49 vtv3 sshd[1281]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.105.165 user=root Jun 21 04:23:51 vtv3 sshd[1281]: Failed password for root from 180.76.105.165 port 58932 ssh2 Dec 2 13:19:49 vtv3 sshd[18622]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.105. |
2019-12-02 23:37:00 |