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: United States

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

;; QUESTION SECTION:
;107.20.139.170.			IN	A

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

;; Query time: 75 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 10:29:27 CST 2022
;; MSG SIZE  rcvd: 107
Host info
170.139.20.107.in-addr.arpa domain name pointer ec2-107-20-139-170.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
170.139.20.107.in-addr.arpa	name = ec2-107-20-139-170.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
101.132.139.7 attackspam
*Port Scan* detected from 101.132.139.7 (CN/China/-). 7 hits in the last 161 seconds
2020-02-17 00:26:28
112.140.185.64 attackbotsspam
Feb 16 14:54:27 internal-server-tf sshd\[12140\]: Invalid user admin from 112.140.185.64Feb 16 14:58:20 internal-server-tf sshd\[12208\]: Invalid user admin from 112.140.185.64
...
2020-02-17 00:36:26
176.223.120.40 attack
Automatic report - XMLRPC Attack
2020-02-17 00:26:09
188.95.77.74 attackspambots
Feb 16 14:40:40 minden010 sshd[1091]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.95.77.74
Feb 16 14:40:42 minden010 sshd[1091]: Failed password for invalid user user1 from 188.95.77.74 port 56623 ssh2
Feb 16 14:48:57 minden010 sshd[5634]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.95.77.74
...
2020-02-17 00:25:14
185.53.88.44 attackbotsspam
185.53.88.44 was recorded 5 times by 5 hosts attempting to connect to the following ports: 5060. Incident counter (4h, 24h, all-time): 5, 5, 5
2020-02-16 23:57:37
185.111.214.205 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-17 00:00:57
142.93.39.29 attackspam
Feb 16 15:08:39 hcbbdb sshd\[23776\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.39.29  user=root
Feb 16 15:08:41 hcbbdb sshd\[23776\]: Failed password for root from 142.93.39.29 port 44992 ssh2
Feb 16 15:12:05 hcbbdb sshd\[24110\]: Invalid user user from 142.93.39.29
Feb 16 15:12:05 hcbbdb sshd\[24110\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.39.29
Feb 16 15:12:06 hcbbdb sshd\[24110\]: Failed password for invalid user user from 142.93.39.29 port 46764 ssh2
2020-02-17 00:02:01
141.98.10.137 attack
Root attacks.
2020-02-17 00:32:48
118.175.131.253 attackbotsspam
Telnetd brute force attack detected by fail2ban
2020-02-17 00:31:13
80.68.89.30 attackspambots
Automatic report - XMLRPC Attack
2020-02-17 00:11:14
220.170.0.102 attack
[portscan] Port scan
2020-02-17 00:12:59
185.110.111.30 attackspambots
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-17 00:18:28
152.32.191.195 attack
Feb 16 09:58:01 plusreed sshd[11832]: Invalid user saward from 152.32.191.195
...
2020-02-17 00:17:56
51.68.44.13 attackbots
SSH Brute-Forcing (server2)
2020-02-17 00:12:21
185.110.244.108 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-17 00:11:56

Recently Reported IPs

13.226.31.63 107.190.137.114 107.194.43.240 107.20.203.231
107.191.57.154 107.20.3.116 107.20.5.122 107.21.239.186
107.21.219.2 107.22.137.123 107.21.31.135 107.22.185.65
107.22.226.50 107.20.42.34 13.226.31.64 107.22.254.97
107.22.232.39 107.22.63.131 107.22.3.181 107.22.6.193