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:
IP Type Details Datetime
124.121.232.153 attackspam
Automatic report - Port Scan Attack
2020-06-06 13:15:23
124.121.244.210 attack
Honeypot attack, port: 445, PTR: ppp-124-121-244-210.revip2.asianet.co.th.
2020-04-12 20:39:17
124.121.232.48 attackspambots
Honeypot attack, port: 81, PTR: ppp-124-121-232-48.revip2.asianet.co.th.
2020-01-14 14:04:31
124.121.216.35 attackspambots
1433/tcp
[2019-10-26]1pkt
2019-10-26 17:23:27
124.121.26.244 attackspambots
[portscan] Port scan
2019-09-28 23:28:31
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 124.121.2.94
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54862
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;124.121.2.94.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Mar 10 10:35:36 CST 2022
;; MSG SIZE  rcvd: 105
Host info
94.2.121.124.in-addr.arpa domain name pointer ppp-124-121-2-94.revip2.asianet.co.th.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
94.2.121.124.in-addr.arpa	name = ppp-124-121-2-94.revip2.asianet.co.th.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
111.229.157.147 attack
SSH/22 MH Probe, BF, Hack -
2020-01-14 17:34:11
49.51.161.77 attack
Unauthorized connection attempt detected from IP address 49.51.161.77 to port 5820 [J]
2020-01-14 17:44:07
41.41.241.187 attack
Unauthorized connection attempt detected from IP address 41.41.241.187 to port 23 [J]
2020-01-14 17:17:31
186.210.66.95 attack
Unauthorized connection attempt detected from IP address 186.210.66.95 to port 8080 [J]
2020-01-14 17:24:13
42.115.192.200 attack
Unauthorized connection attempt detected from IP address 42.115.192.200 to port 23 [J]
2020-01-14 17:16:23
164.52.24.171 attackspam
Unauthorized connection attempt detected from IP address 164.52.24.171 to port 1723 [J]
2020-01-14 17:56:39
85.72.51.33 attack
Unauthorized connection attempt detected from IP address 85.72.51.33 to port 3389 [J]
2020-01-14 17:39:37
70.18.218.223 attackbotsspam
$f2bV_matches
2020-01-14 17:41:40
167.114.26.52 attackbots
Unauthorized connection attempt detected from IP address 167.114.26.52 to port 1433 [J]
2020-01-14 17:29:00
220.134.171.109 attackbots
Unauthorized connection attempt detected from IP address 220.134.171.109 to port 4567 [J]
2020-01-14 17:19:26
189.183.240.198 attack
Unauthorized connection attempt detected from IP address 189.183.240.198 to port 88 [J]
2020-01-14 17:23:09
150.109.180.100 attackspam
Unauthorized connection attempt detected from IP address 150.109.180.100 to port 7547 [J]
2020-01-14 17:29:42
85.234.30.66 attackbots
Unauthorized connection attempt detected from IP address 85.234.30.66 to port 23 [J]
2020-01-14 17:39:08
94.183.241.96 attack
Unauthorized connection attempt detected from IP address 94.183.241.96 to port 23 [J]
2020-01-14 17:38:27
200.116.203.38 attack
Unauthorized connection attempt detected from IP address 200.116.203.38 to port 23 [J]
2020-01-14 17:50:15

Recently Reported IPs

124.121.2.93 124.121.2.96 124.121.2.99 124.121.20.100
124.121.20.105 124.121.20.106 124.121.20.117 124.121.20.118
124.121.20.123 124.121.20.124 124.121.20.128 124.121.20.130
124.121.20.133 124.121.20.135 124.121.20.137 124.121.20.139
124.121.20.14 124.121.20.140 124.121.20.143 124.121.20.145