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: India

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.208.139.127 attackbots
Feb 25 08:19:51 debian-2gb-nbg1-2 kernel: \[4874389.908343\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=117.208.139.127 DST=195.201.40.59 LEN=48 TOS=0x08 PREC=0x00 TTL=108 ID=26335 DF PROTO=TCP SPT=59150 DPT=1433 WINDOW=8192 RES=0x00 SYN URGP=0
2020-02-25 21:15:16
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 117.208.139.2
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42631
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;117.208.139.2.			IN	A

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

;; Query time: 78 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 08 11:53:39 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 2.139.208.117.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 2.139.208.117.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
193.169.252.74 attack
445/tcp 445/tcp 445/tcp...
[2019-06-26/08-23]14pkt,1pt.(tcp)
2019-08-24 03:12:53
218.19.93.242 attack
Portscan or hack attempt detected by psad/fwsnort
2019-08-24 02:58:45
197.50.3.125 attack
Unauthorised access (Aug 23) SRC=197.50.3.125 LEN=52 TOS=0x10 PREC=0x40 TTL=111 ID=26883 DF TCP DPT=445 WINDOW=8192 SYN
2019-08-24 03:05:57
207.154.225.170 attackbots
2019-08-23T18:57:26.281969abusebot-6.cloudsearch.cf sshd\[1735\]: Invalid user jason1 from 207.154.225.170 port 53402
2019-08-24 03:31:27
118.221.41.82 attackspambots
Automatic report - Port Scan Attack
2019-08-24 03:05:27
187.188.154.87 attackspam
Unauthorized connection attempt from IP address 187.188.154.87 on Port 445(SMB)
2019-08-24 03:37:05
212.83.163.205 attackspambots
445/tcp 445/tcp 445/tcp...
[2019-06-26/08-23]4pkt,1pt.(tcp)
2019-08-24 03:30:08
117.48.208.251 attackspam
Aug 23 08:56:11 hcbb sshd\[17388\]: Invalid user ts from 117.48.208.251
Aug 23 08:56:11 hcbb sshd\[17388\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.48.208.251
Aug 23 08:56:13 hcbb sshd\[17388\]: Failed password for invalid user ts from 117.48.208.251 port 35080 ssh2
Aug 23 08:59:53 hcbb sshd\[17667\]: Invalid user nj from 117.48.208.251
Aug 23 08:59:53 hcbb sshd\[17667\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.48.208.251
2019-08-24 03:04:11
159.65.218.10 attackbotsspam
Wordpress Admin Login attack
2019-08-24 03:26:50
51.68.143.26 attackspam
Aug 23 18:49:33 hb sshd\[5293\]: Invalid user stanford from 51.68.143.26
Aug 23 18:49:33 hb sshd\[5293\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=26.ip-51-68-143.eu
Aug 23 18:49:35 hb sshd\[5293\]: Failed password for invalid user stanford from 51.68.143.26 port 45282 ssh2
Aug 23 18:53:46 hb sshd\[5723\]: Invalid user gmalloy from 51.68.143.26
Aug 23 18:53:46 hb sshd\[5723\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=26.ip-51-68-143.eu
2019-08-24 02:55:30
167.71.217.110 attackbots
Aug 23 08:48:29 friendsofhawaii sshd\[9036\]: Invalid user customer from 167.71.217.110
Aug 23 08:48:29 friendsofhawaii sshd\[9036\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.217.110
Aug 23 08:48:32 friendsofhawaii sshd\[9036\]: Failed password for invalid user customer from 167.71.217.110 port 45322 ssh2
Aug 23 08:53:13 friendsofhawaii sshd\[9440\]: Invalid user jeni from 167.71.217.110
Aug 23 08:53:13 friendsofhawaii sshd\[9440\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.217.110
2019-08-24 02:56:58
178.128.86.127 attackspambots
SSH Brute-Force reported by Fail2Ban
2019-08-24 03:15:07
212.64.91.146 attack
Aug 23 18:50:45 [host] sshd[5517]: Invalid user sym from 212.64.91.146
Aug 23 18:50:45 [host] sshd[5517]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.64.91.146
Aug 23 18:50:48 [host] sshd[5517]: Failed password for invalid user sym from 212.64.91.146 port 36798 ssh2
2019-08-24 02:55:51
222.175.157.234 attackbots
" "
2019-08-24 03:30:54
178.116.46.206 attack
$f2bV_matches
2019-08-24 03:14:21

Recently Reported IPs

120.242.128.235 142.93.114.5 60.19.136.101 189.207.106.85
221.176.163.26 206.189.48.241 78.169.19.137 220.198.206.2
159.223.53.152 150.158.136.41 178.150.66.141 189.207.96.204
115.150.224.206 49.205.252.135 42.230.148.234 189.206.239.114
110.78.81.126 183.245.54.93 124.223.44.78 89.227.205.106