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

Region: England

Country: United Kingdom

Internet Service Provider: unknown

Hostname: unknown

Organization: British Telecommunications PLC

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;86.139.96.108.			IN	A

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

;; Query time: 3 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Mon Aug 26 00:48:47 CST 2019
;; MSG SIZE  rcvd: 117
Host info
108.96.139.86.in-addr.arpa domain name pointer host86-139-96-108.range86-139.btcentralplus.com.
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

Non-authoritative answer:
108.96.139.86.in-addr.arpa	name = host86-139-96-108.range86-139.btcentralplus.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
139.59.38.169 attackspam
Oct 30 23:07:25 server sshd\[16161\]: Invalid user rl from 139.59.38.169
Oct 30 23:07:25 server sshd\[16161\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.38.169 
Oct 30 23:07:27 server sshd\[16161\]: Failed password for invalid user rl from 139.59.38.169 port 34656 ssh2
Oct 30 23:26:44 server sshd\[20852\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.38.169  user=root
Oct 30 23:26:46 server sshd\[20852\]: Failed password for root from 139.59.38.169 port 39064 ssh2
...
2019-10-31 06:30:55
179.33.137.117 attack
F2B jail: sshd. Time: 2019-10-30 23:04:16, Reported by: VKReport
2019-10-31 06:13:59
117.132.14.250 attackspam
Oct 30 23:51:47 www4 sshd\[27979\]: Invalid user 12345\^ from 117.132.14.250
Oct 30 23:51:47 www4 sshd\[27979\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.132.14.250
Oct 30 23:51:49 www4 sshd\[27979\]: Failed password for invalid user 12345\^ from 117.132.14.250 port 55926 ssh2
...
2019-10-31 06:16:52
78.81.152.246 attackbots
PHI,WP GET /wp-login.php
2019-10-31 06:30:30
196.189.89.162 attack
Oct 30 21:17:28 georgia postfix/smtpd[50706]: connect from unknown[196.189.89.162]
Oct 30 21:17:29 georgia postfix/smtpd[50706]: warning: unknown[196.189.89.162]: SASL LOGIN authentication failed: authentication failure
Oct 30 21:17:29 georgia postfix/smtpd[50706]: lost connection after AUTH from unknown[196.189.89.162]
Oct 30 21:17:29 georgia postfix/smtpd[50706]: disconnect from unknown[196.189.89.162] ehlo=1 auth=0/1 commands=1/2
Oct 30 21:17:30 georgia postfix/smtpd[50706]: connect from unknown[196.189.89.162]
Oct 30 21:17:31 georgia postfix/smtpd[50706]: warning: unknown[196.189.89.162]: SASL LOGIN authentication failed: authentication failure
Oct 30 21:17:31 georgia postfix/smtpd[50706]: lost connection after AUTH from unknown[196.189.89.162]
Oct 30 21:17:31 georgia postfix/smtpd[50706]: disconnect from unknown[196.189.89.162] ehlo=1 auth=0/1 commands=1/2
Oct 30 21:17:32 georgia postfix/smtpd[50706]: connect from unknown[196.189.89.162]
Oct 30 21:17:33 georgia pos........
-------------------------------
2019-10-31 06:22:16
95.80.252.189 attackbots
Mail sent to address harvested from public web site
2019-10-31 06:26:23
82.117.202.170 attackspambots
MultiHost/MultiPort Probe, Scan, Hack -
2019-10-31 06:37:45
159.89.169.137 attack
Oct 30 11:50:43 web9 sshd\[26816\]: Invalid user 123456 from 159.89.169.137
Oct 30 11:50:43 web9 sshd\[26816\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.169.137
Oct 30 11:50:45 web9 sshd\[26816\]: Failed password for invalid user 123456 from 159.89.169.137 port 48874 ssh2
Oct 30 11:55:15 web9 sshd\[27417\]: Invalid user jia7515798 from 159.89.169.137
Oct 30 11:55:15 web9 sshd\[27417\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.169.137
2019-10-31 06:13:07
170.238.46.6 attackspambots
Oct 30 22:27:37 icinga sshd[24835]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.238.46.6
Oct 30 22:27:39 icinga sshd[24835]: Failed password for invalid user pa$sword! from 170.238.46.6 port 50192 ssh2
...
2019-10-31 06:12:53
23.129.64.192 attackbots
Honeypot hit, critical abuseConfidenceScore, incoming Traffic from this IP
2019-10-31 06:09:14
125.161.148.59 attackspam
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/125.161.148.59/ 
 
 ID - 1H : (49)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : ID 
 NAME ASN : ASN17974 
 
 IP : 125.161.148.59 
 
 CIDR : 125.161.148.0/22 
 
 PREFIX COUNT : 1456 
 
 UNIQUE IP COUNT : 1245952 
 
 
 ATTACKS DETECTED ASN17974 :  
  1H - 2 
  3H - 2 
  6H - 3 
 12H - 5 
 24H - 8 
 
 DateTime : 2019-10-30 21:27:23 
 
 INFO : Server 403 - Looking for resource vulnerabilities Detected and Blocked by ADMIN  - data recovery
2019-10-31 06:11:55
42.104.97.242 attack
Oct 30 23:00:30 vps666546 sshd\[11756\]: Invalid user www-user from 42.104.97.242 port 44515
Oct 30 23:00:30 vps666546 sshd\[11756\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.104.97.242
Oct 30 23:00:32 vps666546 sshd\[11756\]: Failed password for invalid user www-user from 42.104.97.242 port 44515 ssh2
Oct 30 23:05:25 vps666546 sshd\[11829\]: Invalid user china22idc from 42.104.97.242 port 62069
Oct 30 23:05:25 vps666546 sshd\[11829\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.104.97.242
...
2019-10-31 06:20:18
185.53.91.21 attack
" "
2019-10-31 06:43:07
104.197.75.152 attackspam
enlinea.de 104.197.75.152 \[30/Oct/2019:21:26:47 +0100\] "POST /wp-login.php HTTP/1.1" 200 5768 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
enlinea.de 104.197.75.152 \[30/Oct/2019:21:26:48 +0100\] "POST /xmlrpc.php HTTP/1.1" 200 4076 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-10-31 06:30:07
129.45.59.80 attackspambots
Oct 30 21:14:28 mxgate1 postfix/postscreen[10169]: CONNECT from [129.45.59.80]:7049 to [176.31.12.44]:25
Oct 30 21:14:28 mxgate1 postfix/dnsblog[10173]: addr 129.45.59.80 listed by domain zen.spamhaus.org as 127.0.0.4
Oct 30 21:14:28 mxgate1 postfix/dnsblog[10173]: addr 129.45.59.80 listed by domain zen.spamhaus.org as 127.0.0.11
Oct 30 21:14:28 mxgate1 postfix/dnsblog[10170]: addr 129.45.59.80 listed by domain cbl.abuseat.org as 127.0.0.2
Oct 30 21:14:28 mxgate1 postfix/dnsblog[10171]: addr 129.45.59.80 listed by domain b.barracudacentral.org as 127.0.0.2
Oct 30 21:14:34 mxgate1 postfix/postscreen[10169]: DNSBL rank 4 for [129.45.59.80]:7049
Oct x@x
Oct 30 21:14:34 mxgate1 postfix/postscreen[10169]: HANGUP after 0.54 from [129.45.59.80]:7049 in tests after SMTP handshake
Oct 30 21:14:34 mxgate1 postfix/postscreen[10169]: DISCONNECT [129.45.59.80]:7049


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=129.45.59.80
2019-10-31 06:15:01

Recently Reported IPs

214.51.72.219 54.36.148.213 24.216.155.8 120.177.236.170
144.255.215.89 179.223.127.175 141.200.181.123 112.177.130.224
211.248.68.82 135.120.230.161 24.34.201.131 78.84.143.18
126.207.175.89 71.168.243.104 41.145.15.103 147.134.14.54
49.158.45.151 217.96.34.165 54.210.130.25 182.4.161.62