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

Region: Balearic Islands

Country: Spain

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

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

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

;; Query time: 84 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jul 06 07:08:02 CST 2020
;; MSG SIZE  rcvd: 117
Host info
139.237.59.80.in-addr.arpa domain name pointer 139.red-80-59-237.staticip.rima-tde.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
139.237.59.80.in-addr.arpa	name = 139.red-80-59-237.staticip.rima-tde.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
217.113.28.5 attack
Unauthorized SSH login attempts
2019-10-21 18:01:08
104.144.45.176 attack
(From edwardfleetwood1@gmail.com) Hello there!

I'm a freelance digital marketing specialist who provides SEO services that can improve your search rankings. The boost in your ranking on Google search results will result in getting more unique visits from potential clients on your website, thus making the search engines like Google consider you as a more trusted website. This eventually leads to better credibility and more sales. 

If you're interested, I'll give you a free consultation to inform you about where your site currently stands, what can be done and what to expect once the site has been optimized. Please let me know what you think. I hope to speak with you soon. 

Best regards,
Edward Fleetwood
2019-10-21 18:04:31
211.159.149.29 attackbots
Oct 20 18:33:45 hpm sshd\[28311\]: Invalid user Box@2017 from 211.159.149.29
Oct 20 18:33:45 hpm sshd\[28311\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.159.149.29
Oct 20 18:33:47 hpm sshd\[28311\]: Failed password for invalid user Box@2017 from 211.159.149.29 port 49468 ssh2
Oct 20 18:38:27 hpm sshd\[28691\]: Invalid user ztj from 211.159.149.29
Oct 20 18:38:27 hpm sshd\[28691\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.159.149.29
2019-10-21 18:04:04
106.12.198.21 attackspambots
Oct 20 18:54:36 wbs sshd\[2276\]: Invalid user Dark@2017 from 106.12.198.21
Oct 20 18:54:36 wbs sshd\[2276\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.198.21
Oct 20 18:54:37 wbs sshd\[2276\]: Failed password for invalid user Dark@2017 from 106.12.198.21 port 38904 ssh2
Oct 20 19:00:03 wbs sshd\[2700\]: Invalid user xianzi123 from 106.12.198.21
Oct 20 19:00:03 wbs sshd\[2700\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.198.21
2019-10-21 17:37:13
159.65.148.91 attackbots
Oct 21 10:18:22 tuxlinux sshd[10316]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.148.91  user=root
Oct 21 10:18:24 tuxlinux sshd[10316]: Failed password for root from 159.65.148.91 port 33982 ssh2
Oct 21 10:18:22 tuxlinux sshd[10316]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.148.91  user=root
Oct 21 10:18:24 tuxlinux sshd[10316]: Failed password for root from 159.65.148.91 port 33982 ssh2
Oct 21 10:52:53 tuxlinux sshd[10847]: Invalid user gpadmin from 159.65.148.91 port 55734
...
2019-10-21 17:32:04
87.241.167.50 attackbots
Automatic report - Port Scan Attack
2019-10-21 17:50:26
185.211.245.170 attackbots
SASL broute force
2019-10-21 17:32:26
122.224.240.250 attack
Oct 21 06:17:58 mail sshd[12881]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.224.240.250  user=root
Oct 21 06:18:00 mail sshd[12881]: Failed password for root from 122.224.240.250 port 51390 ssh2
Oct 21 06:34:09 mail sshd[6014]: Invalid user administrator from 122.224.240.250
Oct 21 06:34:09 mail sshd[6014]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.224.240.250
Oct 21 06:34:09 mail sshd[6014]: Invalid user administrator from 122.224.240.250
Oct 21 06:34:11 mail sshd[6014]: Failed password for invalid user administrator from 122.224.240.250 port 38434 ssh2
...
2019-10-21 17:59:47
113.199.40.202 attack
Automatic report - Banned IP Access
2019-10-21 17:29:01
106.12.49.244 attack
Oct 21 07:05:45 ns37 sshd[14483]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.49.244
2019-10-21 18:06:33
46.10.208.213 attack
2019-10-21T12:14:55.493529enmeeting.mahidol.ac.th sshd\[10761\]: User root from 46.10.208.213 not allowed because not listed in AllowUsers
2019-10-21T12:14:55.639485enmeeting.mahidol.ac.th sshd\[10761\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.10.208.213  user=root
2019-10-21T12:14:57.409586enmeeting.mahidol.ac.th sshd\[10761\]: Failed password for invalid user root from 46.10.208.213 port 55938 ssh2
...
2019-10-21 17:43:59
95.66.200.92 attack
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/95.66.200.92/ 
 
 RU - 1H : (152)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : RU 
 NAME ASN : ASN35645 
 
 IP : 95.66.200.92 
 
 CIDR : 95.66.200.0/23 
 
 PREFIX COUNT : 29 
 
 UNIQUE IP COUNT : 28416 
 
 
 ATTACKS DETECTED ASN35645 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-10-21 05:46:15 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-10-21 17:35:20
77.42.124.12 attackbots
Automatic report - Port Scan Attack
2019-10-21 17:48:30
139.59.61.134 attack
Oct 21 02:59:03 server sshd[4950]: reveeclipse mapping checking getaddrinfo for 248138.cloudwaysapps.com [139.59.61.134] failed - POSSIBLE BREAK-IN ATTEMPT!
Oct 21 02:59:03 server sshd[4950]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.61.134  user=r.r
Oct 21 02:59:05 server sshd[4950]: Failed password for r.r from 139.59.61.134 port 41457 ssh2
Oct 21 02:59:06 server sshd[4950]: Received disconnect from 139.59.61.134: 11: Bye Bye [preauth]
Oct 21 03:08:51 server sshd[5068]: reveeclipse mapping checking getaddrinfo for 248138.cloudwaysapps.com [139.59.61.134] failed - POSSIBLE BREAK-IN ATTEMPT!
Oct 21 03:08:51 server sshd[5068]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.61.134  user=r.r
Oct 21 03:08:53 server sshd[5068]: Failed password for r.r from 139.59.61.134 port 47418 ssh2
Oct 21 03:08:53 server sshd[5068]: Received disconnect from 139.59.61.134: 11: Bye Bye [pre........
-------------------------------
2019-10-21 17:44:55
87.253.87.3 attackbotsspam
port scan and connect, tcp 23 (telnet)
2019-10-21 17:47:59

Recently Reported IPs

62.140.106.61 189.163.145.207 66.89.135.191 92.143.217.149
18.139.181.255 88.39.192.253 218.113.168.194 44.199.116.249
182.68.97.65 93.170.92.186 69.142.251.42 69.75.36.6
13.76.2.113 58.59.146.58 32.79.212.180 202.38.182.21
31.174.24.130 168.126.103.41 65.218.66.92 213.199.163.128