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: United States

Internet Service Provider: Lanset America Corporation

Hostname: unknown

Organization: unknown

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attackbotsspam
Autoban   63.80.189.139 AUTH/CONNECT
2019-12-13 01:59:28
Comments on same subnet:
IP Type Details Datetime
63.80.189.4 attackspam
$f2bV_matches
2019-12-31 06:04:11
63.80.189.137 attackspam
$f2bV_matches
2019-12-24 23:33:48
63.80.189.137 attack
[ER hit] Tried to deliver spam. Already well known.
2019-12-17 02:15:25
63.80.189.113 attack
Autoban   63.80.189.113 AUTH/CONNECT
2019-12-13 02:05:30
63.80.189.117 attackspambots
Autoban   63.80.189.117 AUTH/CONNECT
2019-12-13 02:03:46
63.80.189.118 attackbotsspam
Autoban   63.80.189.118 AUTH/CONNECT
2019-12-13 02:03:22
63.80.189.129 attack
Autoban   63.80.189.129 AUTH/CONNECT
2019-12-13 02:03:02
63.80.189.135 attackbotsspam
Autoban   63.80.189.135 AUTH/CONNECT
2019-12-13 02:01:38
63.80.189.136 attackbots
Autoban   63.80.189.136 AUTH/CONNECT
2019-12-13 02:01:17
63.80.189.137 attackbots
Autoban   63.80.189.137 AUTH/CONNECT
2019-12-13 02:00:22
63.80.189.138 attack
Autoban   63.80.189.138 AUTH/CONNECT
2019-12-13 01:59:54
63.80.189.142 attackbots
Autoban   63.80.189.142 AUTH/CONNECT
2019-12-13 01:58:04
63.80.189.143 attackbots
Autoban   63.80.189.143 AUTH/CONNECT
2019-12-13 01:55:43
63.80.189.144 attackbotsspam
Autoban   63.80.189.144 AUTH/CONNECT
2019-12-13 01:54:59
63.80.189.145 attack
Autoban   63.80.189.145 AUTH/CONNECT
2019-12-13 01:54:33
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 63.80.189.139
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 502
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 51 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Dec 13 01:59:23 CST 2019
;; MSG SIZE  rcvd: 117
Host info
139.189.80.63.in-addr.arpa domain name pointer flight.itsbem.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
139.189.80.63.in-addr.arpa	name = flight.itsbem.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
218.92.0.212 attackbots
Dec 27 00:03:20 jane sshd[17991]: Failed password for root from 218.92.0.212 port 28934 ssh2
Dec 27 00:03:24 jane sshd[17991]: Failed password for root from 218.92.0.212 port 28934 ssh2
...
2019-12-27 07:07:26
51.89.231.8 attackspam
fail2ban - Attack against WordPress
2019-12-27 06:55:38
213.254.157.12 attackspam
1577400416 - 12/26/2019 23:46:56 Host: 213.254.157.12/213.254.157.12 Port: 445 TCP Blocked
2019-12-27 06:49:20
41.184.234.121 attack
Unauthorized connection attempt from IP address 41.184.234.121 on Port 445(SMB)
2019-12-27 06:40:38
71.6.233.251 attack
Port 22 Scan, PTR: scanners.labs.rapid7.com.
2019-12-27 06:59:11
78.158.180.56 attackspambots
Unauthorized connection attempt from IP address 78.158.180.56 on Port 445(SMB)
2019-12-27 06:31:48
103.48.193.7 attackspam
2019-12-26T22:40:55.434777abusebot-2.cloudsearch.cf sshd[21264]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.48.193.7  user=root
2019-12-26T22:40:57.596729abusebot-2.cloudsearch.cf sshd[21264]: Failed password for root from 103.48.193.7 port 54852 ssh2
2019-12-26T22:43:46.635564abusebot-2.cloudsearch.cf sshd[21358]: Invalid user mysql from 103.48.193.7 port 49554
2019-12-26T22:43:46.641499abusebot-2.cloudsearch.cf sshd[21358]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.48.193.7
2019-12-26T22:43:46.635564abusebot-2.cloudsearch.cf sshd[21358]: Invalid user mysql from 103.48.193.7 port 49554
2019-12-26T22:43:48.276747abusebot-2.cloudsearch.cf sshd[21358]: Failed password for invalid user mysql from 103.48.193.7 port 49554 ssh2
2019-12-26T22:46:42.051318abusebot-2.cloudsearch.cf sshd[21469]: Invalid user fuh from 103.48.193.7 port 44354
...
2019-12-27 06:56:21
115.84.94.89 attackbots
Unauthorized connection attempt from IP address 115.84.94.89 on Port 445(SMB)
2019-12-27 06:42:03
218.92.0.164 attack
SSH bruteforce (Triggered fail2ban)
2019-12-27 06:58:47
59.63.210.222 attackspambots
Dec 26 23:46:44 vmanager6029 sshd\[7267\]: Invalid user test from 59.63.210.222 port 59466
Dec 26 23:46:44 vmanager6029 sshd\[7267\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.63.210.222
Dec 26 23:46:47 vmanager6029 sshd\[7267\]: Failed password for invalid user test from 59.63.210.222 port 59466 ssh2
2019-12-27 06:54:45
149.129.247.235 attackspam
$f2bV_matches
2019-12-27 07:09:08
181.129.16.34 attack
Unauthorized connection attempt from IP address 181.129.16.34 on Port 445(SMB)
2019-12-27 06:38:30
176.119.1.110 attackspambots
20 attempts against mh-misbehave-ban on air.magehost.pro
2019-12-27 06:53:20
112.85.42.182 attack
Dec 26 23:46:55 odroid64 sshd\[13595\]: User root from 112.85.42.182 not allowed because not listed in AllowUsers
Dec 26 23:46:55 odroid64 sshd\[13595\]: Failed none for invalid user root from 112.85.42.182 port 48209 ssh2
...
2019-12-27 06:49:43
71.6.233.142 attack
Port 22 Scan, PTR: None
2019-12-27 07:06:34

Recently Reported IPs

63.252.132.12 63.143.122.199 62.4.55.133 62.4.55.20
49.19.126.96 62.28.134.63 36.233.251.72 220.249.136.5
62.219.131.130 89.218.136.35 62.204.138.68 62.183.56.210
181.64.45.123 167.86.99.247 62.175.96.17 62.138.18.196
217.147.1.96 62.128.102.9 116.110.117.247 62.10.152.164