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

;; QUESTION SECTION:
;139.243.22.177.			IN	A

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

;; Query time: 69 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 08:28:27 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 177.22.243.139.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 177.22.243.139.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
89.138.191.179 attackspam
Jan  8 05:47:49 debian-2gb-nbg1-2 kernel: \[718184.903579\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=89.138.191.179 DST=195.201.40.59 LEN=44 TOS=0x00 PREC=0x00 TTL=241 ID=35983 DF PROTO=TCP SPT=26568 DPT=81 WINDOW=14600 RES=0x00 SYN URGP=0
2020-01-08 18:41:59
101.99.15.135 attackbots
1578458859 - 01/08/2020 05:47:39 Host: 101.99.15.135/101.99.15.135 Port: 445 TCP Blocked
2020-01-08 18:45:34
27.76.186.204 attackbots
Unauthorized connection attempt detected from IP address 27.76.186.204 to port 445
2020-01-08 19:05:26
112.33.253.165 attackspambots
2020-01-05T18:01:34.8756901495-001 sshd[53250]: Invalid user test from 112.33.253.165 port 47732
2020-01-05T18:01:34.8786161495-001 sshd[53250]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.33.253.165
2020-01-05T18:01:34.8756901495-001 sshd[53250]: Invalid user test from 112.33.253.165 port 47732
2020-01-05T18:01:37.6173251495-001 sshd[53250]: Failed password for invalid user test from 112.33.253.165 port 47732 ssh2
2020-01-05T18:12:10.4942901495-001 sshd[53697]: Invalid user maven from 112.33.253.165 port 48020
2020-01-05T18:12:10.4972511495-001 sshd[53697]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.33.253.165
2020-01-05T18:12:10.4942901495-001 sshd[53697]: Invalid user maven from 112.33.253.165 port 48020
2020-01-05T18:12:12.8841201495-001 sshd[53697]: Failed password for invalid user maven from 112.33.253.165 port 48020 ssh2
2020-01-05T18:16:07.0672901495-001 sshd[53814]: ........
------------------------------
2020-01-08 18:55:04
195.225.229.214 attackspambots
Unauthorized connection attempt detected from IP address 195.225.229.214 to port 2220 [J]
2020-01-08 18:34:46
192.241.213.168 attack
Jan  8 06:20:22 powerpi2 sshd[1713]: Invalid user lijy from 192.241.213.168 port 49696
Jan  8 06:20:24 powerpi2 sshd[1713]: Failed password for invalid user lijy from 192.241.213.168 port 49696 ssh2
Jan  8 06:23:16 powerpi2 sshd[1835]: Invalid user aaron from 192.241.213.168 port 49670
...
2020-01-08 18:43:47
41.41.241.234 attack
unauthorized connection attempt
2020-01-08 19:05:57
187.162.23.75 attackspambots
Automatic report - Port Scan Attack
2020-01-08 18:58:55
104.131.68.92 attackspambots
Automatic report - XMLRPC Attack
2020-01-08 19:10:10
101.108.191.131 attackspambots
20/1/7@23:48:00: FAIL: Alarm-Network address from=101.108.191.131
...
2020-01-08 18:32:37
159.192.70.92 attack
1578469877 - 01/08/2020 08:51:17 Host: 159.192.70.92/159.192.70.92 Port: 445 TCP Blocked
2020-01-08 19:00:14
3.234.2.192 attackbotsspam
Jan  6 18:04:56 sanyalnet-cloud-vps4 sshd[15453]: Connection from 3.234.2.192 port 60206 on 64.137.160.124 port 22
Jan  6 18:05:00 sanyalnet-cloud-vps4 sshd[15453]: Invalid user support from 3.234.2.192
Jan  6 18:05:00 sanyalnet-cloud-vps4 sshd[15453]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-3-234-2-192.compute-1.amazonaws.com 
Jan  6 18:05:02 sanyalnet-cloud-vps4 sshd[15453]: Failed password for invalid user support from 3.234.2.192 port 60206 ssh2
Jan  6 18:05:02 sanyalnet-cloud-vps4 sshd[15453]: Received disconnect from 3.234.2.192: 11: Normal Shutdown, Thank you for playing [preauth]
Jan  6 18:16:55 sanyalnet-cloud-vps4 sshd[15728]: Connection from 3.234.2.192 port 52010 on 64.137.160.124 port 22
Jan  6 18:16:58 sanyalnet-cloud-vps4 sshd[15728]: Invalid user butter from 3.234.2.192
Jan  6 18:16:58 sanyalnet-cloud-vps4 sshd[15728]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rho........
-------------------------------
2020-01-08 18:43:17
67.102.20.40 attack
[portscan] tcp/1433 [MsSQL]
*(RWIN=1024)(01081307)
2020-01-08 18:58:07
202.117.111.133 attackbots
Unauthorized connection attempt detected from IP address 202.117.111.133 to port 2220 [J]
2020-01-08 18:56:20
101.71.3.102 attackbotsspam
Unauthorized connection attempt detected from IP address 101.71.3.102 to port 2220 [J]
2020-01-08 19:10:29

Recently Reported IPs

139.243.12.177 139.243.36.177 118.250.2.102 139.243.2.177
139.255.1.142 139.255.1.173 139.255.100.146 139.244.1.177
139.255.10.74 139.255.100.34 139.243.65.177 139.255.101.106
139.255.100.38 139.255.101.132 139.255.101.242 139.255.101.134
118.250.2.105 139.255.101.244 139.255.102.242 139.255.103.210