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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 221.53.161.112
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 8484
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;221.53.161.112.			IN	A

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

;; Query time: 39 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 07:38:07 CST 2025
;; MSG SIZE  rcvd: 107
Host info
112.161.53.221.in-addr.arpa domain name pointer softbank221053161112.bbtec.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
112.161.53.221.in-addr.arpa	name = softbank221053161112.bbtec.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
139.59.82.78 attack
Sep  4 11:03:12 mail sshd[31712]: Invalid user rsyncuser from 139.59.82.78
Sep  4 11:03:12 mail sshd[31712]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.82.78
Sep  4 11:03:12 mail sshd[31712]: Invalid user rsyncuser from 139.59.82.78
Sep  4 11:03:14 mail sshd[31712]: Failed password for invalid user rsyncuser from 139.59.82.78 port 34366 ssh2
Sep  4 11:10:42 mail sshd[32728]: Invalid user hunter from 139.59.82.78
...
2019-09-04 19:10:01
78.136.95.189 attack
[Aegis] @ 2019-09-04 04:22:10  0100 -> Attempted Administrator Privilege Gain: ET SCAN LibSSH Based Frequent SSH Connections Likely BruteForce Attack
2019-09-04 18:57:35
201.190.147.72 attackspam
DATE:2019-09-04 05:15:39, IP:201.190.147.72, PORT:telnet Telnet brute force auth on honeypot server (honey-neo-dc-bis)
2019-09-04 18:05:35
176.31.172.40 attackbots
Sep  4 12:13:30 SilenceServices sshd[1301]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.31.172.40
Sep  4 12:13:32 SilenceServices sshd[1301]: Failed password for invalid user moo from 176.31.172.40 port 41104 ssh2
Sep  4 12:17:23 SilenceServices sshd[2831]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.31.172.40
2019-09-04 19:08:51
157.230.175.60 attackspam
2019-09-04T11:10:34.293440abusebot-3.cloudsearch.cf sshd\[12380\]: Invalid user was from 157.230.175.60 port 52960
2019-09-04 19:13:01
122.161.192.206 attack
2019-09-04T10:34:20.051838hub.schaetter.us sshd\[8535\]: Invalid user P@ssw0rd123! from 122.161.192.206
2019-09-04T10:34:20.109554hub.schaetter.us sshd\[8535\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.161.192.206
2019-09-04T10:34:21.451579hub.schaetter.us sshd\[8535\]: Failed password for invalid user P@ssw0rd123! from 122.161.192.206 port 50484 ssh2
2019-09-04T10:39:07.641314hub.schaetter.us sshd\[8551\]: Invalid user 123123 from 122.161.192.206
2019-09-04T10:39:07.675295hub.schaetter.us sshd\[8551\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.161.192.206
...
2019-09-04 18:53:31
51.144.160.217 attackbotsspam
SSH Brute-Force attacks
2019-09-04 18:54:24
132.232.181.252 attackspam
2019-09-04T10:41:04.220308abusebot-5.cloudsearch.cf sshd\[32606\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.181.252  user=root
2019-09-04 18:53:15
178.33.185.70 attackbots
Sep  3 21:11:55 tdfoods sshd\[17946\]: Invalid user akhavan from 178.33.185.70
Sep  3 21:11:55 tdfoods sshd\[17946\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.33.185.70
Sep  3 21:11:57 tdfoods sshd\[17946\]: Failed password for invalid user akhavan from 178.33.185.70 port 12182 ssh2
Sep  3 21:16:12 tdfoods sshd\[18400\]: Invalid user maint from 178.33.185.70
Sep  3 21:16:12 tdfoods sshd\[18400\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.33.185.70
2019-09-04 18:23:10
181.49.102.190 attack
$f2bV_matches
2019-09-04 18:18:35
91.200.126.90 attackspambots
[SMB remote code execution attempt: port tcp/445]
*(RWIN=1024)(09040856)
2019-09-04 18:05:59
129.204.4.244 attack
23/tcp 23/tcp 23/tcp...
[2019-07-30/09-04]20pkt,1pt.(tcp)
2019-09-04 17:46:00
23.129.64.201 attackspam
Aug 10 23:13:58 vtv3 sshd\[24160\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.129.64.201  user=root
Aug 10 23:14:00 vtv3 sshd\[24160\]: Failed password for root from 23.129.64.201 port 23153 ssh2
Aug 10 23:14:05 vtv3 sshd\[24237\]: Invalid user cirros from 23.129.64.201 port 36758
Aug 10 23:14:05 vtv3 sshd\[24237\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.129.64.201
Aug 10 23:14:07 vtv3 sshd\[24237\]: Failed password for invalid user cirros from 23.129.64.201 port 36758 ssh2
Aug 16 07:15:08 vtv3 sshd\[29863\]: Invalid user Administrator from 23.129.64.201 port 40314
Aug 16 07:15:08 vtv3 sshd\[29863\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.129.64.201
Aug 16 07:15:10 vtv3 sshd\[29863\]: Failed password for invalid user Administrator from 23.129.64.201 port 40314 ssh2
Aug 16 07:15:17 vtv3 sshd\[30250\]: Invalid user guest from 23.129.64.201 port 24158
A
2019-09-04 18:00:12
49.49.242.104 attack
Lines containing failures of 49.49.242.104
Sep  4 04:41:51 server sshd[12449]: Connection from 49.49.242.104 port 53283 on 62.116.165.82 port 22
Sep  4 04:41:51 server sshd[12449]: Did not receive identification string from 49.49.242.104 port 53283
Sep  4 04:41:53 server sshd[12451]: Connection from 49.49.242.104 port 50382 on 62.116.165.82 port 22
Sep  4 04:41:54 server sshd[12451]: reveeclipse mapping checking getaddrinfo for mx-ll-49.49.242-104.dynamic.3bb.in.th [49.49.242.104] failed - POSSIBLE BREAK-IN ATTEMPT!
Sep  4 04:41:54 server sshd[12451]: Invalid user noc from 49.49.242.104 port 50382
Sep  4 04:41:54 server sshd[12451]: Connection closed by 49.49.242.104 port 50382 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=49.49.242.104
2019-09-04 19:03:55
200.150.74.114 attack
SSH invalid-user multiple login try
2019-09-04 18:58:40

Recently Reported IPs

72.44.233.157 71.111.125.75 92.132.58.236 76.252.246.241
15.71.63.36 212.75.245.130 33.85.213.253 78.189.190.9
189.156.102.112 207.28.150.69 137.197.5.69 163.216.59.203
169.124.225.152 196.136.103.149 90.153.133.66 129.119.205.91
142.23.38.193 228.169.219.123 254.36.137.52 85.172.89.161