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

;; QUESTION SECTION:
;124.121.20.16.			IN	A

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

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Mar 10 10:36:41 CST 2022
;; MSG SIZE  rcvd: 106
Host info
16.20.121.124.in-addr.arpa domain name pointer ppp-124-121-20-16.revip2.asianet.co.th.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
16.20.121.124.in-addr.arpa	name = ppp-124-121-20-16.revip2.asianet.co.th.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
91.197.18.221 attackbotsspam
firewall-block, port(s): 85/tcp
2019-12-29 03:26:54
188.226.171.36 attackbots
2019-12-28T14:52:14.391293shield sshd\[6694\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.226.171.36  user=root
2019-12-28T14:52:15.792972shield sshd\[6694\]: Failed password for root from 188.226.171.36 port 53000 ssh2
2019-12-28T14:55:42.941359shield sshd\[7521\]: Invalid user fritz from 188.226.171.36 port 56564
2019-12-28T14:55:42.945548shield sshd\[7521\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.226.171.36
2019-12-28T14:55:45.235283shield sshd\[7521\]: Failed password for invalid user fritz from 188.226.171.36 port 56564 ssh2
2019-12-29 03:43:11
187.147.132.139 attackbotsspam
Unauthorized connection attempt detected from IP address 187.147.132.139 to port 445
2019-12-29 03:43:50
190.104.146.28 attackbots
Unauthorized connection attempt detected from IP address 190.104.146.28 to port 5900
2019-12-29 03:42:24
154.128.79.188 attackbotsspam
Unauthorized connection attempt detected from IP address 154.128.79.188 to port 445
2019-12-29 03:48:46
195.230.131.182 attackspam
Unauthorized connection attempt detected from IP address 195.230.131.182 to port 445
2019-12-29 03:41:14
66.42.108.136 attackspam
Unauthorized connection attempt detected from IP address 66.42.108.136 to port 445
2019-12-29 03:31:27
71.6.165.200 attackbotsspam
Unauthorized connection attempt detected from IP address 71.6.165.200 to port 2081
2019-12-29 03:30:21
88.250.134.236 attackbots
Unauthorized connection attempt detected from IP address 88.250.134.236 to port 23
2019-12-29 03:27:37
114.251.216.146 attack
Unauthorized connection attempt detected from IP address 114.251.216.146 to port 1433
2019-12-29 03:49:22
165.22.163.227 attackspam
Unauthorized connection attempt detected from IP address 165.22.163.227 to port 5900
2019-12-29 03:48:27
196.52.43.59 attack
Unauthorized connection attempt detected from IP address 196.52.43.59 to port 443
2019-12-29 03:40:29
216.218.206.67 attackspam
Unauthorized connection attempt detected from IP address 216.218.206.67 to port 4786
2019-12-29 03:36:49
54.70.117.67 attackbotsspam
Unauthorized connection attempt detected from IP address 54.70.117.67 to port 8008
2019-12-29 03:32:38
189.19.105.192 attack
Unauthorized connection attempt detected from IP address 189.19.105.192 to port 445
2019-12-29 03:18:46

Recently Reported IPs

124.121.20.157 124.121.20.165 124.121.20.174 124.121.20.178
124.121.20.180 124.121.20.181 124.121.20.182 124.121.20.19
124.121.20.195 124.121.20.200 124.121.20.201 124.121.20.209
124.121.20.21 124.121.20.215 124.121.20.217 124.121.20.219
124.121.20.221 124.121.20.222 124.121.20.226 124.121.20.231