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
117.2.139.117 attackbots
20/3/8@23:47:04: FAIL: Alarm-Network address from=117.2.139.117
...
2020-03-09 17:13:09
117.2.139.91 attack
1576621576 - 12/17/2019 23:26:16 Host: 117.2.139.91/117.2.139.91 Port: 445 TCP Blocked
2019-12-18 07:26:14
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 117.2.139.102
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28424
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;117.2.139.102.			IN	A

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

;; Query time: 56 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 06:21:08 CST 2022
;; MSG SIZE  rcvd: 106
Host info
102.139.2.117.in-addr.arpa domain name pointer dynamic-ip-adsl.viettel.vn.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
102.139.2.117.in-addr.arpa	name = dynamic-ip-adsl.viettel.vn.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
14.225.3.37 attackbotsspam
Excessive Port-Scanning
2019-06-22 11:36:21
186.163.17.202 attackbots
Autoban   186.163.17.202 AUTH/CONNECT
2019-06-22 11:38:41
167.250.97.232 attack
Jun 21 16:18:10 mailman postfix/smtpd[23936]: warning: unknown[167.250.97.232]: SASL PLAIN authentication failed: authentication failure
2019-06-22 11:43:59
109.242.196.130 attack
Request: "GET / HTTP/1.1"
2019-06-22 11:37:08
43.226.38.26 attackbotsspam
Invalid user test1 from 43.226.38.26 port 37006
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.226.38.26
Failed password for invalid user test1 from 43.226.38.26 port 37006 ssh2
Invalid user www from 43.226.38.26 port 42568
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.226.38.26
2019-06-22 12:03:44
206.189.118.156 attack
Jun 22 01:02:42 cp sshd[30391]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.118.156
Jun 22 01:02:43 cp sshd[30391]: Failed password for invalid user odoo from 206.189.118.156 port 42758 ssh2
Jun 22 01:05:58 cp sshd[32257]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.118.156
2019-06-22 11:25:02
179.189.192.26 attack
Request: "GET / HTTP/1.1"
2019-06-22 11:39:12
118.70.190.95 attackspam
RDPBruteGam24
2019-06-22 11:51:36
64.90.186.102 attackspam
Request: "GET /user/register/ HTTP/1.1" Request: "GET /user/register/ HTTP/1.1" Request: "GET /user/register/ HTTP/1.1" Request: "GET /user/register/ HTTP/1.1" Request: "GET /user/register/ HTTP/1.1" Request: "GET /user/register/ HTTP/1.1" Request: "GET /user/register/ HTTP/1.1"
2019-06-22 11:52:00
191.241.48.180 attack
Request: "GET / HTTP/1.1" Request: "GET / HTTP/1.1"
2019-06-22 11:38:09
178.212.53.2 attackspambots
Request: "GET / HTTP/1.1"
2019-06-22 11:25:38
221.231.126.2 attackbots
Request: "GET / HTTP/1.1"
2019-06-22 11:48:47
197.255.188.147 attack
Request: "GET / HTTP/1.1"
2019-06-22 11:41:02
51.38.12.21 attack
Request: "GET / HTTP/1.1" Request: "GET / HTTP/1.1"
2019-06-22 11:53:00
46.101.163.220 attack
SSH Brute Force, server-1 sshd[6313]: Failed password for root from 46.101.163.220 port 47797 ssh2
2019-06-22 11:30:34

Recently Reported IPs

117.2.143.213 117.2.161.195 117.2.183.106 117.2.195.229
117.2.203.28 117.2.208.58 117.2.25.135 117.2.228.47
117.2.223.7 117.2.42.158 117.20.18.153 117.20.105.48
117.2.210.23 117.20.29.147 117.20.42.192 117.20.43.131
117.20.43.154 117.20.43.181 117.200.103.76 117.200.107.217