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

Internet Service Provider: Digital Ocean Inc.

Hostname: unknown

Organization: unknown

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attackbotsspam
Feb 18 18:40:57 plex sshd[18446]: Invalid user grey from 139.59.137.154 port 48890
2020-02-19 03:12:03
attack
Feb  7 13:05:24 hpm sshd\[21483\]: Invalid user mqr from 139.59.137.154
Feb  7 13:05:24 hpm sshd\[21483\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=brianbak.dk
Feb  7 13:05:26 hpm sshd\[21483\]: Failed password for invalid user mqr from 139.59.137.154 port 35958 ssh2
Feb  7 13:08:06 hpm sshd\[21821\]: Invalid user da from 139.59.137.154
Feb  7 13:08:06 hpm sshd\[21821\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=brianbak.dk
2020-02-08 07:23:50
attackbotsspam
SSH Brute-Force reported by Fail2Ban
2020-02-07 09:05:27
Comments on same subnet:
IP Type Details Datetime
139.59.137.184 attackbotsspam
(imapd) Failed IMAP login from 139.59.137.184 (DE/Germany/-): 1 in the last 3600 secs
2019-12-19 02:58:52
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.59.137.154
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10628
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 109 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 07 09:05:19 CST 2020
;; MSG SIZE  rcvd: 118
Host info
154.137.59.139.in-addr.arpa domain name pointer brianbak.dk.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
154.137.59.139.in-addr.arpa	name = brianbak.dk.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
190.47.136.120 attackbots
May  3 22:29:38 h2646465 sshd[31719]: Invalid user quest from 190.47.136.120
May  3 22:29:38 h2646465 sshd[31719]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.47.136.120
May  3 22:29:38 h2646465 sshd[31719]: Invalid user quest from 190.47.136.120
May  3 22:29:40 h2646465 sshd[31719]: Failed password for invalid user quest from 190.47.136.120 port 41290 ssh2
May  3 22:34:19 h2646465 sshd[32360]: Invalid user admin from 190.47.136.120
May  3 22:34:19 h2646465 sshd[32360]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.47.136.120
May  3 22:34:19 h2646465 sshd[32360]: Invalid user admin from 190.47.136.120
May  3 22:34:21 h2646465 sshd[32360]: Failed password for invalid user admin from 190.47.136.120 port 37254 ssh2
May  3 22:37:10 h2646465 sshd[459]: Invalid user amssys from 190.47.136.120
...
2020-05-04 07:27:37
162.243.164.246 attack
May  3 16:23:20 server1 sshd\[23971\]: Invalid user admin from 162.243.164.246
May  3 16:23:20 server1 sshd\[23971\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.243.164.246 
May  3 16:23:23 server1 sshd\[23971\]: Failed password for invalid user admin from 162.243.164.246 port 36196 ssh2
May  3 16:25:43 server1 sshd\[24574\]: Invalid user git from 162.243.164.246
May  3 16:25:43 server1 sshd\[24574\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.243.164.246 
...
2020-05-04 07:45:02
177.134.204.10 attack
20/5/3@16:36:48: FAIL: Alarm-Network address from=177.134.204.10
20/5/3@16:36:48: FAIL: Alarm-Network address from=177.134.204.10
...
2020-05-04 07:43:02
49.235.11.46 attackspambots
SASL PLAIN auth failed: ruser=...
2020-05-04 07:17:15
139.199.7.216 attackbots
$f2bV_matches
2020-05-04 07:37:33
114.67.117.53 attackbotsspam
May  3 22:37:40 cloud sshd[29627]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.67.117.53 
May  3 22:37:43 cloud sshd[29627]: Failed password for invalid user up from 114.67.117.53 port 37630 ssh2
2020-05-04 07:09:02
188.166.208.131 attack
May  3 22:59:49 ip-172-31-62-245 sshd\[23160\]: Failed password for root from 188.166.208.131 port 59514 ssh2\
May  3 23:04:18 ip-172-31-62-245 sshd\[23256\]: Invalid user ns from 188.166.208.131\
May  3 23:04:20 ip-172-31-62-245 sshd\[23256\]: Failed password for invalid user ns from 188.166.208.131 port 41130 ssh2\
May  3 23:08:39 ip-172-31-62-245 sshd\[23342\]: Invalid user ftptest from 188.166.208.131\
May  3 23:08:41 ip-172-31-62-245 sshd\[23342\]: Failed password for invalid user ftptest from 188.166.208.131 port 50972 ssh2\
2020-05-04 07:21:20
80.82.64.124 attack
2020-05-03T22:37:13.148505amanda2.illicoweb.com sshd\[23195\]: Invalid user pi from 80.82.64.124 port 45762
2020-05-03T22:37:13.176384amanda2.illicoweb.com sshd\[23195\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.82.64.124
2020-05-03T22:37:14.520227amanda2.illicoweb.com sshd\[23195\]: Failed password for invalid user pi from 80.82.64.124 port 45762 ssh2
2020-05-03T22:37:14.774248amanda2.illicoweb.com sshd\[23198\]: Invalid user admin from 80.82.64.124 port 46326
2020-05-03T22:37:14.800232amanda2.illicoweb.com sshd\[23198\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.82.64.124
...
2020-05-04 07:25:52
167.114.203.73 attackbotsspam
$f2bV_matches
2020-05-04 07:08:32
92.63.196.3 attackspambots
05/03/2020-16:37:17.286264 92.63.196.3 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-05-04 07:24:30
159.203.30.208 attackspambots
May  3 22:29:27 localhost sshd[118590]: Invalid user zzz from 159.203.30.208 port 52834
May  3 22:29:27 localhost sshd[118590]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.30.208
May  3 22:29:27 localhost sshd[118590]: Invalid user zzz from 159.203.30.208 port 52834
May  3 22:29:29 localhost sshd[118590]: Failed password for invalid user zzz from 159.203.30.208 port 52834 ssh2
May  3 22:34:39 localhost sshd[119073]: Invalid user postgres from 159.203.30.208 port 58219
...
2020-05-04 07:32:19
222.186.52.39 attackspam
May  4 06:12:33 webhost01 sshd[8492]: Failed password for root from 222.186.52.39 port 18741 ssh2
...
2020-05-04 07:29:38
119.147.23.134 attackbotsspam
(sshd) Failed SSH login from 119.147.23.134 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: May  4 01:36:14 s1 sshd[22106]: Invalid user fogo from 119.147.23.134 port 54652
May  4 01:36:16 s1 sshd[22106]: Failed password for invalid user fogo from 119.147.23.134 port 54652 ssh2
May  4 01:47:59 s1 sshd[22559]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.147.23.134  user=root
May  4 01:48:01 s1 sshd[22559]: Failed password for root from 119.147.23.134 port 51554 ssh2
May  4 01:50:57 s1 sshd[22714]: Invalid user solr from 119.147.23.134 port 57626
2020-05-04 07:44:16
129.211.38.207 attackbotsspam
May  4 00:32:23 home sshd[6704]: Failed password for root from 129.211.38.207 port 58750 ssh2
May  4 00:36:21 home sshd[7577]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.38.207
May  4 00:36:23 home sshd[7577]: Failed password for invalid user sysadm from 129.211.38.207 port 51172 ssh2
...
2020-05-04 07:39:02
180.243.20.155 attack
k+ssh-bruteforce
2020-05-04 07:42:13

Recently Reported IPs

114.104.239.204 23.254.165.201 222.223.114.111 193.77.243.73
215.162.76.151 82.132.201.65 104.217.200.82 138.209.236.118
162.78.141.251 62.183.56.102 202.107.207.226 5.135.89.197
82.165.71.187 41.58.82.192 115.204.26.52 83.167.230.21
202.166.201.226 202.166.72.79 122.51.234.86 2603:1026:302:80::5