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: unknown

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
119.82.240.122 attack
Apr 18 10:54:33 firewall sshd[30622]: Invalid user test from 119.82.240.122
Apr 18 10:54:35 firewall sshd[30622]: Failed password for invalid user test from 119.82.240.122 port 37860 ssh2
Apr 18 10:59:11 firewall sshd[30818]: Invalid user virus from 119.82.240.122
...
2020-04-18 22:56:18
119.82.240.122 attack
Apr  2 15:35:07 vps647732 sshd[2840]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.82.240.122
Apr  2 15:35:09 vps647732 sshd[2840]: Failed password for invalid user dg from 119.82.240.122 port 51380 ssh2
...
2020-04-02 21:47:05
119.82.240.122 attack
Apr  2 10:58:56 server sshd\[28606\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.82.240.122  user=root
Apr  2 10:58:57 server sshd\[28606\]: Failed password for root from 119.82.240.122 port 53394 ssh2
Apr  2 11:22:29 server sshd\[1941\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.82.240.122  user=root
Apr  2 11:22:31 server sshd\[1941\]: Failed password for root from 119.82.240.122 port 56040 ssh2
Apr  2 11:29:44 server sshd\[3534\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.82.240.122  user=root
...
2020-04-02 17:59:38
119.82.240.122 attackspambots
Mar 27 06:56:55 silence02 sshd[24494]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.82.240.122
Mar 27 06:56:58 silence02 sshd[24494]: Failed password for invalid user cerasela from 119.82.240.122 port 57258 ssh2
Mar 27 07:04:05 silence02 sshd[27781]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.82.240.122
2020-03-27 14:27:53
119.82.240.122 attack
Invalid user rhedyn from 119.82.240.122 port 43764
2020-03-27 08:50:05
119.82.240.122 attackspambots
Invalid user ftp1 from 119.82.240.122 port 41950
2020-03-21 08:43:10
119.82.240.122 attackspam
(sshd) Failed SSH login from 119.82.240.122 (ID/Indonesia/ip-240-122.datautama.net.id): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Mar 19 00:19:22 ubnt-55d23 sshd[13286]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.82.240.122  user=root
Mar 19 00:19:25 ubnt-55d23 sshd[13286]: Failed password for root from 119.82.240.122 port 52830 ssh2
2020-03-19 08:46:06
119.82.240.123 attackspambots
"Account brute force using dictionary attack against Exchange Online"
2019-08-06 02:22:55
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 119.82.240.74
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16114
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;119.82.240.74.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 16:08:11 CST 2022
;; MSG SIZE  rcvd: 106
Host info
74.240.82.119.in-addr.arpa domain name pointer ip-240-74.datautama.net.id.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
74.240.82.119.in-addr.arpa	name = ip-240-74.datautama.net.id.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
106.110.17.28 attackspam
Unauthorized connection attempt detected from IP address 106.110.17.28 to port 8080 [T]
2020-01-27 07:56:52
60.172.70.212 attackspam
Unauthorized connection attempt detected from IP address 60.172.70.212 to port 6656 [T]
2020-01-27 08:00:28
119.120.77.159 attack
Unauthorized connection attempt detected from IP address 119.120.77.159 to port 5555 [T]
2020-01-27 07:50:16
78.239.45.63 attack
Unauthorized connection attempt detected from IP address 78.239.45.63 to port 2220 [J]
2020-01-27 07:58:37
47.106.113.196 attackbotsspam
Unauthorized connection attempt detected from IP address 47.106.113.196 to port 80 [J]
2020-01-27 07:36:13
183.164.234.197 attackbots
Unauthorized connection attempt detected from IP address 183.164.234.197 to port 6656 [T]
2020-01-27 07:44:06
111.75.117.73 attackspambots
Unauthorized connection attempt detected from IP address 111.75.117.73 to port 6656 [T]
2020-01-27 07:55:42
49.68.190.247 attack
Unauthorized connection attempt detected from IP address 49.68.190.247 to port 6656 [T]
2020-01-27 08:02:11
164.52.24.162 attack
Unauthorized connection attempt detected from IP address 164.52.24.162 to port 443 [J]
2020-01-27 08:10:21
39.76.83.25 attackbots
Unauthorized connection attempt detected from IP address 39.76.83.25 to port 23 [J]
2020-01-27 08:02:58
47.104.192.106 attackbotsspam
Unauthorized connection attempt detected from IP address 47.104.192.106 to port 23 [J]
2020-01-27 08:02:38
163.179.207.44 attack
Unauthorized connection attempt detected from IP address 163.179.207.44 to port 6656 [T]
2020-01-27 07:46:01
59.46.43.58 attack
Unauthorized connection attempt detected from IP address 59.46.43.58 to port 1433 [T]
2020-01-27 07:35:25
112.113.152.116 attack
Unauthorized connection attempt detected from IP address 112.113.152.116 to port 6656 [T]
2020-01-27 07:54:59
49.85.98.97 attackspam
Unauthorized connection attempt detected from IP address 49.85.98.97 to port 6656 [T]
2020-01-27 08:01:47

Recently Reported IPs

119.82.240.69 119.82.241.138 119.82.241.140 119.82.241.156
119.85.12.76 119.85.12.92 119.85.13.10 119.85.13.106
119.85.13.148 119.85.13.16 119.85.13.172 119.85.13.184
119.85.13.193 119.85.13.214 119.85.13.46 119.85.136.6
119.85.14.120 119.85.14.154 119.85.14.167 33.208.217.85