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

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

;; QUESTION SECTION:
;124.120.169.40.			IN	A

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

;; Query time: 70 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Mar 10 10:04:39 CST 2022
;; MSG SIZE  rcvd: 107
Host info
40.169.120.124.in-addr.arpa domain name pointer ppp-124-120-169-40.revip2.asianet.co.th.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
40.169.120.124.in-addr.arpa	name = ppp-124-120-169-40.revip2.asianet.co.th.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
106.12.109.89 attack
Oct 30 01:16:04 gw1 sshd[32458]: Failed password for root from 106.12.109.89 port 54542 ssh2
...
2019-10-30 04:22:58
83.13.91.50 attack
Automatic report - Port Scan Attack
2019-10-30 04:15:25
91.189.88.24 attackbots
Oct 29 11:28:48   TCP Attack: SRC=91.189.88.24 DST=[Masked] LEN=1500 TOS=0x00 PREC=0x00 TTL=54  DF PROTO=TCP SPT=80 DPT=47224 WINDOW=237 RES=0x00 ACK URGP=0
2019-10-30 04:05:35
117.203.253.153 attackspam
Unauthorized connection attempt from IP address 117.203.253.153 on Port 445(SMB)
2019-10-30 03:57:42
222.186.175.216 attackspambots
2019-10-29T20:14:26.129009abusebot-7.cloudsearch.cf sshd\[11126\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.216  user=root
2019-10-30 04:17:08
196.74.115.124 attackspam
NOQUEUE: reject: RCPT from unknown\[196.74.115.124\]: 554 5.7.1 Service unavailable\; host \[196.74.115.124\] blocked using sbl-xbl.spamhaus.org\; https://www.spamhaus.org/sbl/query/SBLCSS
2019-10-30 03:48:28
128.199.184.127 attackbots
Oct 29 14:52:58 ncomp sshd[21533]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.184.127  user=root
Oct 29 14:53:00 ncomp sshd[21533]: Failed password for root from 128.199.184.127 port 37874 ssh2
Oct 29 15:11:44 ncomp sshd[22121]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.184.127  user=root
Oct 29 15:11:47 ncomp sshd[22121]: Failed password for root from 128.199.184.127 port 58068 ssh2
2019-10-30 04:02:09
187.135.172.38 attackbots
" "
2019-10-30 03:50:59
91.121.211.34 attack
$f2bV_matches
2019-10-30 04:28:52
5.249.145.73 attackspam
2019-10-29T20:00:33.768139shield sshd\[15664\]: Invalid user redis from 5.249.145.73 port 50250
2019-10-29T20:00:33.773631shield sshd\[15664\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.249.145.73
2019-10-29T20:00:35.517624shield sshd\[15664\]: Failed password for invalid user redis from 5.249.145.73 port 50250 ssh2
2019-10-29T20:03:59.431455shield sshd\[16121\]: Invalid user mass from 5.249.145.73 port 41101
2019-10-29T20:03:59.437232shield sshd\[16121\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.249.145.73
2019-10-30 04:12:39
185.176.221.214 attackbotsspam
RDP brute force attack detected by fail2ban
2019-10-30 03:52:32
89.179.246.46 attackspam
Oct 29 07:31:36 *** sshd[11785]: Failed password for invalid user ubnt from 89.179.246.46 port 4725 ssh2
Oct 29 07:46:16 *** sshd[12073]: Failed password for invalid user 123 from 89.179.246.46 port 56906 ssh2
Oct 29 07:51:20 *** sshd[12162]: Failed password for invalid user password from 89.179.246.46 port 10468 ssh2
Oct 29 07:56:16 *** sshd[12216]: Failed password for invalid user passw0rd08 from 89.179.246.46 port 27915 ssh2
Oct 29 08:01:13 *** sshd[12292]: Failed password for invalid user 123456 from 89.179.246.46 port 45525 ssh2
Oct 29 08:06:24 *** sshd[12397]: Failed password for invalid user 123456 from 89.179.246.46 port 63244 ssh2
Oct 29 08:11:20 *** sshd[12516]: Failed password for invalid user yk from 89.179.246.46 port 16794 ssh2
Oct 29 08:16:17 *** sshd[12578]: Failed password for invalid user mak2311 from 89.179.246.46 port 34485 ssh2
Oct 29 08:34:29 *** sshd[27468]: Failed password for invalid user admin12346789 from 89.179.246.46 port 54740 ssh2
Oct 29 08:39:17 *** sshd[27584]: Failed password
2019-10-30 04:28:35
34.212.63.114 attack
10/29/2019-21:04:02.297262 34.212.63.114 Protocol: 6 SURICATA TLS invalid record/traffic
2019-10-30 04:09:34
176.107.130.17 attackspambots
Oct 29 20:03:22 localhost sshd\[26730\]: Invalid user student5 from 176.107.130.17
Oct 29 20:03:22 localhost sshd\[26730\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.107.130.17
Oct 29 20:03:24 localhost sshd\[26730\]: Failed password for invalid user student5 from 176.107.130.17 port 33838 ssh2
Oct 29 20:07:25 localhost sshd\[26940\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.107.130.17  user=root
Oct 29 20:07:28 localhost sshd\[26940\]: Failed password for root from 176.107.130.17 port 44904 ssh2
...
2019-10-30 03:53:45
106.12.212.139 attack
Tried sshing with brute force.
2019-10-30 04:27:10

Recently Reported IPs

124.120.169.248 124.120.169.51 124.120.169.73 124.120.169.87
124.120.170.121 124.120.170.157 124.120.170.184 124.120.170.190
124.120.170.22 124.120.170.228 124.120.170.235 124.120.170.56
124.120.170.72 124.120.170.82 124.120.171.114 124.120.171.246
124.120.171.249 124.120.171.81 124.120.172.143 124.120.172.174