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: Korea (the Republic of)

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 <<>> 122.41.80.249
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 18802
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;122.41.80.249.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 26 19:47:31 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 249.80.41.122.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 249.80.41.122.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
180.167.225.118 attack
Apr 10 01:13:44 sso sshd[6434]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.167.225.118
Apr 10 01:13:47 sso sshd[6434]: Failed password for invalid user test from 180.167.225.118 port 51332 ssh2
...
2020-04-10 08:04:47
185.220.101.141 attack
Brute force attempt
2020-04-10 08:21:08
176.165.48.246 attackbotsspam
SSH brute force
2020-04-10 08:00:11
54.36.86.216 attackspam
GET /admin/ HTTP/1.1
2020-04-10 07:55:00
165.22.77.163 attack
Apr 10 01:36:54 hell sshd[22352]: Failed password for postgres from 165.22.77.163 port 56370 ssh2
...
2020-04-10 08:07:05
177.9.120.133 attackspambots
1586469310 - 04/09/2020 23:55:10 Host: 177.9.120.133/177.9.120.133 Port: 445 TCP Blocked
2020-04-10 08:15:15
99.247.21.62 attackspambots
SSH login attempts with user(s): fabian.
2020-04-10 08:13:25
140.249.22.238 attack
SSH brute force
2020-04-10 08:02:16
49.73.61.26 attackbotsspam
Apr 10 00:43:06 h1745522 sshd[22618]: Invalid user test from 49.73.61.26 port 60699
Apr 10 00:43:06 h1745522 sshd[22618]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.73.61.26
Apr 10 00:43:06 h1745522 sshd[22618]: Invalid user test from 49.73.61.26 port 60699
Apr 10 00:43:08 h1745522 sshd[22618]: Failed password for invalid user test from 49.73.61.26 port 60699 ssh2
Apr 10 00:47:07 h1745522 sshd[22719]: Invalid user gitianuser from 49.73.61.26 port 60040
Apr 10 00:47:07 h1745522 sshd[22719]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.73.61.26
Apr 10 00:47:07 h1745522 sshd[22719]: Invalid user gitianuser from 49.73.61.26 port 60040
Apr 10 00:47:09 h1745522 sshd[22719]: Failed password for invalid user gitianuser from 49.73.61.26 port 60040 ssh2
Apr 10 00:51:13 h1745522 sshd[22896]: Invalid user test from 49.73.61.26 port 59381
...
2020-04-10 08:17:49
211.22.202.197 attackbots
Unauthorized connection attempt detected from IP address 211.22.202.197 to port 5555
2020-04-10 08:25:15
177.45.93.8 attackspam
Apr  9 17:47:49 web1 sshd[20604]: Address 177.45.93.8 maps to 177-45-93-8.user.ajato.com.br, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Apr  9 17:47:49 web1 sshd[20604]: Invalid user debian from 177.45.93.8
Apr  9 17:47:49 web1 sshd[20604]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.45.93.8 
Apr  9 17:47:51 web1 sshd[20604]: Failed password for invalid user debian from 177.45.93.8 port 58656 ssh2
Apr  9 17:47:51 web1 sshd[20604]: Received disconnect from 177.45.93.8: 11: Bye Bye [preauth]
Apr  9 18:03:10 web1 sshd[21972]: Address 177.45.93.8 maps to 177-45-93-8.user.ajato.com.br, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Apr  9 18:03:10 web1 sshd[21972]: Invalid user deploy from 177.45.93.8
Apr  9 18:03:10 web1 sshd[21972]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.45.93.8 
Apr  9 18:03:13 web1 sshd[21972]: Failed pa........
-------------------------------
2020-04-10 08:06:40
84.39.244.131 attack
Automatic report - Port Scan Attack
2020-04-10 08:03:56
120.70.102.239 attack
SSH Brute-Forcing (server1)
2020-04-10 08:10:51
121.229.48.89 attackspambots
Apr 10 00:05:56 h2779839 sshd[10115]: Invalid user formation from 121.229.48.89 port 33498
Apr 10 00:05:56 h2779839 sshd[10115]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.229.48.89
Apr 10 00:05:56 h2779839 sshd[10115]: Invalid user formation from 121.229.48.89 port 33498
Apr 10 00:05:58 h2779839 sshd[10115]: Failed password for invalid user formation from 121.229.48.89 port 33498 ssh2
Apr 10 00:09:16 h2779839 sshd[11065]: Invalid user hadoop1 from 121.229.48.89 port 57506
Apr 10 00:09:18 h2779839 sshd[11065]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.229.48.89
Apr 10 00:09:16 h2779839 sshd[11065]: Invalid user hadoop1 from 121.229.48.89 port 57506
Apr 10 00:09:19 h2779839 sshd[11065]: Failed password for invalid user hadoop1 from 121.229.48.89 port 57506 ssh2
Apr 10 00:12:57 h2779839 sshd[11122]: Invalid user ralph from 121.229.48.89 port 53282
...
2020-04-10 07:51:13
49.234.30.113 attack
Ssh brute force
2020-04-10 08:15:51

Recently Reported IPs

148.48.187.19 91.226.201.142 109.235.95.118 59.133.132.147
246.40.46.125 70.71.78.152 249.19.89.218 124.115.127.224
123.54.148.176 91.55.112.134 200.80.139.173 122.39.22.26
194.113.158.239 7.45.24.184 227.218.132.138 85.67.155.174
168.189.49.222 195.4.55.68 215.25.107.101 180.45.54.24