城市(city): Utsunomiya
省份(region): Totigi (Tochigi)
国家(country): Japan
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
% [whois.apnic.net]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html
% Information related to '120.137.128.0 - 120.137.255.255'
% Abuse contact for '120.137.128.0 - 120.137.255.255' is 'hostmaster@nic.ad.jp'
inetnum: 120.137.128.0 - 120.137.255.255
netname: TOKAI
descr: TOKAI Communications Corporation
descr: 38,Oyaizu,Yaizu-city,SHIZUOKA 425-0073,JAPAN
country: JP
admin-c: JNIC1-AP
tech-c: JNIC1-AP
status: ALLOCATED PORTABLE
remarks: Email address for spam or abuse complaints : jpnic-tokaicom@tokai-grp.co.jp
mnt-irt: IRT-JPNIC-JP
mnt-by: MAINT-JPNIC
mnt-lower: MAINT-JPNIC
last-modified: 2012-03-27T07:22:02Z
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 '120.137.200.0 - 120.137.207.255'
inetnum: 120.137.200.0 - 120.137.207.255
netname: TOKAI-NET
descr: TOKAI Communications Corporation
country: JP
admin-c: JP00078326
tech-c: JP00078326
last-modified: 2018-01-22T23:26:04Z
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.36-SNAPSHOT (WHOIS-AU5); <<>> DiG 9.10.3-P4-Ubuntu <<>> 120.137.205.50
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 31583
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;120.137.205.50. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026040600 1800 900 604800 86400
;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Apr 06 18:08:24 CST 2026
;; MSG SIZE rcvd: 10750.205.137.120.in-addr.arpa domain name pointer 50.net120137205.t-com.ne.jp.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
50.205.137.120.in-addr.arpa name = 50.net120137205.t-com.ne.jp.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 180.167.155.211 | attackbots | Automatic report - XMLRPC Attack |
2020-01-16 05:32:53 |
| 222.186.42.4 | attack | 01/15/2020-15:56:15.105840 222.186.42.4 Protocol: 6 ET SCAN Potential SSH Scan |
2020-01-16 05:04:26 |
| 189.206.3.228 | attackbotsspam | 3389BruteforceFW22 |
2020-01-16 05:13:15 |
| 134.175.196.241 | attack | Jan 15 21:31:02 mail sshd[24675]: Invalid user operator from 134.175.196.241 Jan 15 21:31:02 mail sshd[24675]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.196.241 Jan 15 21:31:02 mail sshd[24675]: Invalid user operator from 134.175.196.241 Jan 15 21:31:04 mail sshd[24675]: Failed password for invalid user operator from 134.175.196.241 port 55256 ssh2 Jan 15 21:43:40 mail sshd[11432]: Invalid user yd from 134.175.196.241 ... |
2020-01-16 05:22:13 |
| 187.72.138.237 | attackbotsspam | Unauthorized connection attempt detected from IP address 187.72.138.237 to port 445 |
2020-01-16 05:07:58 |
| 49.88.112.62 | attackspambots | Jan 15 22:19:03 vps647732 sshd[30709]: Failed password for root from 49.88.112.62 port 18897 ssh2 Jan 15 22:19:16 vps647732 sshd[30709]: error: maximum authentication attempts exceeded for root from 49.88.112.62 port 18897 ssh2 [preauth] ... |
2020-01-16 05:30:24 |
| 122.51.88.138 | attackspam | 2020-01-15T15:11:40.7519011495-001 sshd[56264]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.88.138 user=root 2020-01-15T15:11:42.5177861495-001 sshd[56264]: Failed password for root from 122.51.88.138 port 39920 ssh2 2020-01-15T15:14:09.2979001495-001 sshd[56342]: Invalid user ajay from 122.51.88.138 port 33380 2020-01-15T15:14:09.3010611495-001 sshd[56342]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.88.138 2020-01-15T15:14:09.2979001495-001 sshd[56342]: Invalid user ajay from 122.51.88.138 port 33380 2020-01-15T15:14:11.1874031495-001 sshd[56342]: Failed password for invalid user ajay from 122.51.88.138 port 33380 ssh2 2020-01-15T15:16:40.3523731495-001 sshd[56406]: Invalid user kusanagi from 122.51.88.138 port 55070 2020-01-15T15:16:40.3713701495-001 sshd[56406]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.88.138 2020-01-15T15:16:4 ... |
2020-01-16 05:18:42 |
| 95.65.99.81 | attack | 3389BruteforceFW22 |
2020-01-16 05:33:15 |
| 59.53.213.225 | attackbotsspam | Unauthorized connection attempt from IP address 59.53.213.225 on Port 445(SMB) |
2020-01-16 05:22:56 |
| 95.222.110.113 | attack | Jan 11 06:28:23 odroid64 sshd\[5430\]: User root from 95.222.110.113 not allowed because not listed in AllowUsers Jan 11 06:28:23 odroid64 sshd\[5430\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.222.110.113 user=root ... |
2020-01-16 05:17:12 |
| 159.65.77.43 | attackbotsspam | Jan 15 21:52:01 mail sshd[8744]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.77.43 Jan 15 21:52:03 mail sshd[8744]: Failed password for invalid user tela from 159.65.77.43 port 48950 ssh2 ... |
2020-01-16 05:23:37 |
| 14.29.224.14 | attack | Jan 15 22:12:20 localhost sshd\[22974\]: Invalid user kk from 14.29.224.14 Jan 15 22:12:20 localhost sshd\[22974\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.29.224.14 Jan 15 22:12:22 localhost sshd\[22974\]: Failed password for invalid user kk from 14.29.224.14 port 42078 ssh2 Jan 15 22:14:56 localhost sshd\[23016\]: Invalid user sk from 14.29.224.14 Jan 15 22:14:56 localhost sshd\[23016\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.29.224.14 ... |
2020-01-16 05:28:02 |
| 78.189.203.87 | attack | Unauthorized connection attempt from IP address 78.189.203.87 on Port 445(SMB) |
2020-01-16 05:07:27 |
| 27.90.200.17 | attackbotsspam | Unauthorized connection attempt from IP address 27.90.200.17 on Port 445(SMB) |
2020-01-16 05:14:44 |
| 83.123.16.104 | attackbots | Unauthorized connection attempt from IP address 83.123.16.104 on Port 445(SMB) |
2020-01-16 05:03:58 |