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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.211.36.94
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56087
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.211.36.94.			IN	A

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

;; Query time: 23 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 08:22:20 CST 2022
;; MSG SIZE  rcvd: 106
Host info
94.36.211.139.in-addr.arpa domain name pointer 94.36.211.139.adsl-pool.jlccptt.net.cn.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
94.36.211.139.in-addr.arpa	name = 94.36.211.139.adsl-pool.jlccptt.net.cn.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
110.77.238.136 attackspam
20/1/7@23:55:57: FAIL: Alarm-Network address from=110.77.238.136
20/1/7@23:55:57: FAIL: Alarm-Network address from=110.77.238.136
...
2020-01-08 13:49:43
200.187.7.20 attackspam
1578459372 - 01/08/2020 05:56:12 Host: 200.187.7.20/200.187.7.20 Port: 445 TCP Blocked
2020-01-08 13:43:04
95.55.109.220 attackspambots
Unauthorized connection attempt detected from IP address 95.55.109.220 to port 22
2020-01-08 13:40:29
222.186.3.249 attackspambots
Jan  8 06:20:49 vps691689 sshd[13404]: Failed password for root from 222.186.3.249 port 31492 ssh2
Jan  8 06:22:43 vps691689 sshd[13423]: Failed password for root from 222.186.3.249 port 33877 ssh2
...
2020-01-08 13:32:58
159.203.172.181 attackspambots
" "
2020-01-08 13:26:11
200.44.50.155 attack
Unauthorized connection attempt detected from IP address 200.44.50.155 to port 2220 [J]
2020-01-08 13:11:19
5.101.0.209 attackbots
Unauthorized connection attempt detected from IP address 5.101.0.209 to port 8081 [J]
2020-01-08 13:40:41
222.186.30.76 attackbotsspam
Unauthorized connection attempt detected from IP address 222.186.30.76 to port 22 [J]
2020-01-08 13:10:55
114.88.122.235 attackspambots
Jan  8 06:22:34 amit sshd\[30665\]: Invalid user admin from 114.88.122.235
Jan  8 06:22:34 amit sshd\[30665\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.88.122.235
Jan  8 06:22:37 amit sshd\[30665\]: Failed password for invalid user admin from 114.88.122.235 port 13577 ssh2
...
2020-01-08 13:48:06
80.15.74.9 attackspambots
MultiHost/MultiPort Probe, Scan, Hack -
2020-01-08 13:35:02
164.132.196.98 attackbotsspam
$f2bV_matches
2020-01-08 13:33:13
185.220.101.79 attackspambots
Input Traffic from this IP, but critial abuseconfidencescore
2020-01-08 13:11:49
37.144.138.108 attackbotsspam
Automatic report - Port Scan Attack
2020-01-08 13:16:07
220.126.227.74 attackbots
Jan  8 10:42:58 gw1 sshd[5529]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.126.227.74
Jan  8 10:43:00 gw1 sshd[5529]: Failed password for invalid user db2inst3 from 220.126.227.74 port 35090 ssh2
...
2020-01-08 13:45:39
37.139.9.23 attack
kp-sea2-01 recorded 2 login violations from 37.139.9.23 and was blocked at 2020-01-08 05:13:57. 37.139.9.23 has been blocked on 1 previous occasions. 37.139.9.23's first attempt was recorded at 2019-08-29 21:03:30
2020-01-08 13:42:37

Recently Reported IPs

139.211.38.37 139.211.38.98 139.211.32.176 139.211.39.26
118.249.207.6 139.211.4.87 139.211.46.185 139.211.5.138
139.211.41.124 139.211.67.130 139.211.76.3 139.211.8.242
139.211.68.185 139.211.67.36 118.249.53.79 139.211.67.70
139.211.90.223 139.211.67.234 139.211.90.4 139.211.83.250