Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: Japan

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
IP Type Details Datetime
221.249.140.17 attackspam
2020-09-09T18:13:25.725420shield sshd\[28545\]: Invalid user tracker from 221.249.140.17 port 49746
2020-09-09T18:13:25.735560shield sshd\[28545\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221x249x140x17.ap221.ftth.ucom.ne.jp
2020-09-09T18:13:28.041568shield sshd\[28545\]: Failed password for invalid user tracker from 221.249.140.17 port 49746 ssh2
2020-09-09T18:18:42.494418shield sshd\[28960\]: Invalid user ubuntu from 221.249.140.17 port 55936
2020-09-09T18:18:42.503595shield sshd\[28960\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221x249x140x17.ap221.ftth.ucom.ne.jp
2020-09-10 02:31:51
221.249.140.17 attackspam
Aug 22 21:57:35 fhem-rasp sshd[24345]: Invalid user wke from 221.249.140.17 port 40820
...
2020-08-23 04:01:55
221.249.140.17 attack
Aug 17 08:05:41 pve1 sshd[6861]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.249.140.17 
Aug 17 08:05:42 pve1 sshd[6861]: Failed password for invalid user wanghaiyan from 221.249.140.17 port 49130 ssh2
...
2020-08-17 15:50:36
221.249.140.17 attackspambots
Aug  9 09:52:46 gw1 sshd[26104]: Failed password for root from 221.249.140.17 port 40138 ssh2
...
2020-08-09 18:34:38
221.249.140.17 attackbotsspam
Aug  5 23:47:22 PorscheCustomer sshd[31594]: Failed password for root from 221.249.140.17 port 47544 ssh2
Aug  5 23:51:02 PorscheCustomer sshd[31703]: Failed password for root from 221.249.140.17 port 35072 ssh2
...
2020-08-06 07:17:16
221.249.140.17 attack
Jul 29 15:30:05 vlre-nyc-1 sshd\[10397\]: Invalid user ncs from 221.249.140.17
Jul 29 15:30:05 vlre-nyc-1 sshd\[10397\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.249.140.17
Jul 29 15:30:07 vlre-nyc-1 sshd\[10397\]: Failed password for invalid user ncs from 221.249.140.17 port 42488 ssh2
Jul 29 15:37:32 vlre-nyc-1 sshd\[10596\]: Invalid user zhaojp from 221.249.140.17
Jul 29 15:37:32 vlre-nyc-1 sshd\[10596\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.249.140.17
...
2020-07-30 01:20:00
221.249.140.17 attackspambots
Jul 26 14:03:34 Ubuntu-1404-trusty-64-minimal sshd\[15070\]: Invalid user csgo from 221.249.140.17
Jul 26 14:03:34 Ubuntu-1404-trusty-64-minimal sshd\[15070\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.249.140.17
Jul 26 14:03:36 Ubuntu-1404-trusty-64-minimal sshd\[15070\]: Failed password for invalid user csgo from 221.249.140.17 port 56062 ssh2
Jul 26 14:11:12 Ubuntu-1404-trusty-64-minimal sshd\[19853\]: Invalid user student from 221.249.140.17
Jul 26 14:11:12 Ubuntu-1404-trusty-64-minimal sshd\[19853\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.249.140.17
2020-07-26 22:08:09
221.249.140.17 attackbotsspam
SSH Brute-Forcing (server1)
2020-07-12 03:31:16
221.249.140.17 attack
2020-07-07T06:26:03.680252randservbullet-proofcloud-66.localdomain sshd[19706]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221x249x140x17.ap221.ftth.ucom.ne.jp  user=root
2020-07-07T06:26:05.664528randservbullet-proofcloud-66.localdomain sshd[19706]: Failed password for root from 221.249.140.17 port 34172 ssh2
2020-07-07T06:28:08.532394randservbullet-proofcloud-66.localdomain sshd[19732]: Invalid user vr from 221.249.140.17 port 55400
...
2020-07-07 15:11:48
221.249.140.17 attack
Jun 30 20:20:56 ns382633 sshd\[17922\]: Invalid user bacula from 221.249.140.17 port 42734
Jun 30 20:20:56 ns382633 sshd\[17922\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.249.140.17
Jun 30 20:20:58 ns382633 sshd\[17922\]: Failed password for invalid user bacula from 221.249.140.17 port 42734 ssh2
Jun 30 21:03:34 ns382633 sshd\[25510\]: Invalid user mar from 221.249.140.17 port 35156
Jun 30 21:03:34 ns382633 sshd\[25510\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.249.140.17
2020-07-02 01:36:38
221.249.140.17 attackspam
Invalid user splunk from 221.249.140.17 port 44452
2020-06-28 07:24:49
221.249.140.17 attackbots
Jun 13 14:21:25 mellenthin sshd[30086]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.249.140.17
Jun 13 14:21:27 mellenthin sshd[30086]: Failed password for invalid user cz from 221.249.140.17 port 46410 ssh2
2020-06-14 03:05:47
221.249.140.17 attack
Jun 13 07:47:27 server sshd[31950]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.249.140.17
Jun 13 07:47:30 server sshd[31950]: Failed password for invalid user test from 221.249.140.17 port 48636 ssh2
Jun 13 07:52:21 server sshd[32416]: Failed password for root from 221.249.140.17 port 49772 ssh2
...
2020-06-13 14:23:39
221.249.140.17 attackspambots
2020-06-04T00:56:52.2239701495-001 sshd[39148]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221x249x140x17.ap221.ftth.ucom.ne.jp  user=root
2020-06-04T00:56:54.5010661495-001 sshd[39148]: Failed password for root from 221.249.140.17 port 39954 ssh2
2020-06-04T01:02:22.2801641495-001 sshd[39366]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221x249x140x17.ap221.ftth.ucom.ne.jp  user=root
2020-06-04T01:02:23.8598731495-001 sshd[39366]: Failed password for root from 221.249.140.17 port 44442 ssh2
2020-06-04T01:07:50.8261561495-001 sshd[39613]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221x249x140x17.ap221.ftth.ucom.ne.jp  user=root
2020-06-04T01:07:53.7659191495-001 sshd[39613]: Failed password for root from 221.249.140.17 port 48850 ssh2
...
2020-06-04 14:30:48
221.249.140.17 attackspambots
May 16 01:16:31 * sshd[1225]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.249.140.17
May 16 01:16:34 * sshd[1225]: Failed password for invalid user postgres from 221.249.140.17 port 49690 ssh2
2020-05-16 07:20:31
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 221.249.140.163
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 33599
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;221.249.140.163.		IN	A

;; AUTHORITY SECTION:
.			29	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2025031301 1800 900 604800 86400

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Mar 14 01:09:56 CST 2025
;; MSG SIZE  rcvd: 108
Host info
163.140.249.221.in-addr.arpa domain name pointer 221x249x140x163.ap221.ftth.ucom.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
163.140.249.221.in-addr.arpa	name = 221x249x140x163.ap221.ftth.ucom.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
116.136.19.117 attack
Unauthorized connection attempt detected from IP address 116.136.19.117 to port 222
2020-06-01 00:09:29
177.207.204.230 attackbots
Unauthorized connection attempt detected from IP address 177.207.204.230 to port 1433
2020-05-31 23:56:56
116.136.19.138 attackspam
Unauthorized connection attempt detected from IP address 116.136.19.138 to port 222
2020-06-01 00:07:31
61.54.107.171 attackspam
Unauthorized connection attempt detected from IP address 61.54.107.171 to port 22
2020-05-31 23:40:33
121.146.7.109 attackspam
Unauthorized connection attempt detected from IP address 121.146.7.109 to port 23
2020-06-01 00:03:57
64.64.104.10 attackspam
Unauthorized connection attempt detected from IP address 64.64.104.10 to port 2000
2020-06-01 00:17:00
94.53.213.121 attackbotsspam
Unauthorized connection attempt detected from IP address 94.53.213.121 to port 23
2020-06-01 00:12:01
116.136.19.119 attackbotsspam
Unauthorized connection attempt detected from IP address 116.136.19.119 to port 222
2020-06-01 00:08:56
116.136.19.141 attackspambots
Unauthorized connection attempt detected from IP address 116.136.19.141 to port 222
2020-06-01 00:06:58
106.75.64.59 attackspambots
Unauthorized connection attempt detected from IP address 106.75.64.59 to port 1863
2020-06-01 00:10:23
71.6.146.130 attackbots
Unauthorized connection attempt detected from IP address 71.6.146.130 to port 2379
2020-06-01 00:16:00
41.138.88.26 attackbots
Unauthorized connection attempt detected from IP address 41.138.88.26 to port 445
2020-06-01 00:20:16
185.132.58.225 attack
Unauthorized connection attempt detected from IP address 185.132.58.225 to port 3390
2020-05-31 23:55:10
2.136.182.204 attackbotsspam
Unauthorized connection attempt detected from IP address 2.136.182.204 to port 23
2020-05-31 23:46:13
198.143.158.82 attack
Unauthorized connection attempt detected from IP address 198.143.158.82 to port 3310
2020-05-31 23:50:47

Recently Reported IPs

221.191.200.207 232.193.47.92 75.197.34.42 85.235.79.109
221.8.105.26 88.180.213.114 111.113.88.245 162.186.248.249
21.117.197.89 197.248.173.186 53.244.153.177 157.70.247.139
74.254.162.87 230.102.113.253 169.170.22.156 125.45.191.63
28.114.254.16 242.201.24.107 69.97.55.97 137.244.181.95