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

;; QUESTION SECTION:
;139.5.70.160.			IN	A

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

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 04:07:14 CST 2022
;; MSG SIZE  rcvd: 105
Host info
160.70.5.139.in-addr.arpa domain name pointer waf-vip1.wlink.com.np.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
160.70.5.139.in-addr.arpa	name = waf-vip1.wlink.com.np.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
49.86.216.90 attackbots
firewall-block, port(s): 23/tcp
2019-12-25 14:48:04
206.189.142.10 attackbotsspam
Dec 25 11:26:00 vibhu-HP-Z238-Microtower-Workstation sshd\[16252\]: Invalid user test from 206.189.142.10
Dec 25 11:26:00 vibhu-HP-Z238-Microtower-Workstation sshd\[16252\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.142.10
Dec 25 11:26:02 vibhu-HP-Z238-Microtower-Workstation sshd\[16252\]: Failed password for invalid user test from 206.189.142.10 port 55532 ssh2
Dec 25 11:29:11 vibhu-HP-Z238-Microtower-Workstation sshd\[16472\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.142.10  user=root
Dec 25 11:29:12 vibhu-HP-Z238-Microtower-Workstation sshd\[16472\]: Failed password for root from 206.189.142.10 port 55334 ssh2
...
2019-12-25 14:08:17
223.111.157.138 attackspambots
MultiHost/MultiPort Probe, Scan, Hack -
2019-12-25 14:23:12
199.195.252.213 attack
Dec 25 10:50:00 vibhu-HP-Z238-Microtower-Workstation sshd\[13859\]: Invalid user cpa from 199.195.252.213
Dec 25 10:50:00 vibhu-HP-Z238-Microtower-Workstation sshd\[13859\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=199.195.252.213
Dec 25 10:50:02 vibhu-HP-Z238-Microtower-Workstation sshd\[13859\]: Failed password for invalid user cpa from 199.195.252.213 port 32824 ssh2
Dec 25 10:52:07 vibhu-HP-Z238-Microtower-Workstation sshd\[14026\]: Invalid user nobody8888 from 199.195.252.213
Dec 25 10:52:07 vibhu-HP-Z238-Microtower-Workstation sshd\[14026\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=199.195.252.213
...
2019-12-25 14:03:05
62.234.79.230 attack
Dec 25 06:57:50 MK-Soft-Root1 sshd[7569]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.79.230 
Dec 25 06:57:52 MK-Soft-Root1 sshd[7569]: Failed password for invalid user Eeva from 62.234.79.230 port 54586 ssh2
...
2019-12-25 14:06:19
104.236.176.175 attackbots
Invalid user Hockey from 104.236.176.175 port 40179
2019-12-25 14:28:36
218.92.0.179 attackbots
Dec 25 07:48:04 ovpn sshd\[31509\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.179  user=root
Dec 25 07:48:06 ovpn sshd\[31509\]: Failed password for root from 218.92.0.179 port 27579 ssh2
Dec 25 07:48:37 ovpn sshd\[31654\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.179  user=root
Dec 25 07:48:39 ovpn sshd\[31654\]: Failed password for root from 218.92.0.179 port 18827 ssh2
Dec 25 07:48:54 ovpn sshd\[31654\]: Failed password for root from 218.92.0.179 port 18827 ssh2
2019-12-25 14:51:39
222.186.180.41 attackbotsspam
12/25/2019-01:09:42.891884 222.186.180.41 Protocol: 6 ET SCAN Potential SSH Scan
2019-12-25 14:12:51
201.48.170.252 attackbots
2019-12-25T06:26:39.486166abusebot-3.cloudsearch.cf sshd[29456]: Invalid user squid from 201.48.170.252 port 41578
2019-12-25T06:26:39.493653abusebot-3.cloudsearch.cf sshd[29456]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.48.170.252
2019-12-25T06:26:39.486166abusebot-3.cloudsearch.cf sshd[29456]: Invalid user squid from 201.48.170.252 port 41578
2019-12-25T06:26:41.783623abusebot-3.cloudsearch.cf sshd[29456]: Failed password for invalid user squid from 201.48.170.252 port 41578 ssh2
2019-12-25T06:30:02.875094abusebot-3.cloudsearch.cf sshd[29462]: Invalid user guest from 201.48.170.252 port 41868
2019-12-25T06:30:02.881216abusebot-3.cloudsearch.cf sshd[29462]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.48.170.252
2019-12-25T06:30:02.875094abusebot-3.cloudsearch.cf sshd[29462]: Invalid user guest from 201.48.170.252 port 41868
2019-12-25T06:30:04.704692abusebot-3.cloudsearch.cf sshd[29462]:
...
2019-12-25 14:41:44
194.61.24.250 attack
Dec 24 19:58:11 hpm sshd\[25498\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=194.61.24.250  user=root
Dec 24 19:58:13 hpm sshd\[25498\]: Failed password for root from 194.61.24.250 port 57354 ssh2
Dec 24 19:58:15 hpm sshd\[25500\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=194.61.24.250  user=root
Dec 24 19:58:17 hpm sshd\[25500\]: Failed password for root from 194.61.24.250 port 58406 ssh2
Dec 24 19:58:21 hpm sshd\[25519\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=194.61.24.250  user=root
2019-12-25 14:05:47
69.12.92.28 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-12-25 14:18:48
113.162.84.44 attack
Unauthorized connection attempt from IP address 113.162.84.44 on Port 445(SMB)
2019-12-25 14:49:50
113.172.152.177 attackspam
Dec 24 21:25:47 mxgate1 postfix/postscreen[781]: CONNECT from [113.172.152.177]:35525 to [176.31.12.44]:25
Dec 24 21:25:47 mxgate1 postfix/dnsblog[785]: addr 113.172.152.177 listed by domain zen.spamhaus.org as 127.0.0.11
Dec 24 21:25:47 mxgate1 postfix/dnsblog[785]: addr 113.172.152.177 listed by domain zen.spamhaus.org as 127.0.0.3
Dec 24 21:25:47 mxgate1 postfix/dnsblog[785]: addr 113.172.152.177 listed by domain zen.spamhaus.org as 127.0.0.4
Dec 24 21:25:47 mxgate1 postfix/dnsblog[783]: addr 113.172.152.177 listed by domain cbl.abuseat.org as 127.0.0.2
Dec 24 21:25:47 mxgate1 postfix/dnsblog[782]: addr 113.172.152.177 listed by domain b.barracudacentral.org as 127.0.0.2
Dec 24 21:25:48 mxgate1 postfix/dnsblog[784]: addr 113.172.152.177 listed by domain bl.spamcop.net as 127.0.0.2
Dec 24 21:25:53 mxgate1 postfix/postscreen[781]: DNSBL rank 5 for [113.172.152.177]:35525
Dec 24 21:25:54 mxgate1 postfix/tlsproxy[836]: CONNECT from [113.172.152.177]:35525
Dec x@x
Dec 24 ........
-------------------------------
2019-12-25 14:45:06
104.197.75.152 attackbotsspam
104.197.75.152 - - [25/Dec/2019:04:56:37 +0000] "POST /wp-login.php HTTP/1.1" 200 6393 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
104.197.75.152 - - [25/Dec/2019:04:56:38 +0000] "POST /xmlrpc.php HTTP/1.1" 200 403 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2019-12-25 14:07:12
122.96.166.177 attack
Dec 25 05:56:05 debian-2gb-nbg1-2 kernel: \[902501.311178\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=122.96.166.177 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=41 ID=39865 PROTO=TCP SPT=47877 DPT=23 WINDOW=50549 RES=0x00 SYN URGP=0
2019-12-25 14:22:31

Recently Reported IPs

139.5.39.179 139.5.37.164 139.5.71.84 139.59.1.0
139.59.11.133 139.59.110.168 139.59.111.74 139.59.106.77
139.59.114.93 139.59.112.219 139.59.115.56 139.59.113.84
139.59.117.194 237.189.204.212 139.59.17.3 139.59.180.146
139.59.185.86 139.59.183.12 139.59.173.113 139.59.18.220