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: 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:
IP Type Details Datetime
5.134.192.232 attackbots
SSH login attempts.
2020-08-22 21:11:36
5.134.196.122 attackbots
Unauthorized connection attempt from IP address 5.134.196.122 on Port 445(SMB)
2020-05-07 22:57:58
5.134.195.143 attackspam
unauthorized connection attempt
2020-02-26 13:41:39
5.134.198.114 attackspambots
unauthorized connection attempt
2020-02-07 21:42:29
5.134.194.110 attackspambots
Honeypot attack, port: 81, PTR: PTR record not found
2020-02-07 20:13:19
5.134.193.211 attackbots
1578260806 - 01/05/2020 22:46:46 Host: 5.134.193.211/5.134.193.211 Port: 445 TCP Blocked
2020-01-06 09:33:07
5.134.198.114 attack
Telnet/23 MH Probe, BF, Hack -
2019-11-14 21:59:23
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 5.134.19.0
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51455
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 2 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Wed Jun 26 01:40:33 CST 2019
;; MSG SIZE  rcvd: 114
Host info
Host 0.19.134.5.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

** server can't find 0.19.134.5.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
178.62.240.29 attackbotsspam
Oct 31 10:25:56 gw1 sshd[12562]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.240.29
Oct 31 10:25:58 gw1 sshd[12562]: Failed password for invalid user 12345678 from 178.62.240.29 port 58471 ssh2
...
2019-10-31 13:28:28
193.70.90.59 attack
Oct 30 18:25:27 sachi sshd\[23512\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.ip-193-70-90.eu  user=root
Oct 30 18:25:29 sachi sshd\[23512\]: Failed password for root from 193.70.90.59 port 39078 ssh2
Oct 30 18:28:49 sachi sshd\[23788\]: Invalid user ubnt from 193.70.90.59
Oct 30 18:28:49 sachi sshd\[23788\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.ip-193-70-90.eu
Oct 30 18:28:50 sachi sshd\[23788\]: Failed password for invalid user ubnt from 193.70.90.59 port 48920 ssh2
2019-10-31 13:19:08
60.216.181.115 attackspambots
Oct 31 06:55:18 server sshd\[31388\]: Invalid user pi from 60.216.181.115
Oct 31 06:55:19 server sshd\[31388\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.216.181.115 
Oct 31 06:55:19 server sshd\[31386\]: Invalid user pi from 60.216.181.115
Oct 31 06:55:19 server sshd\[31386\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.216.181.115 
Oct 31 06:55:21 server sshd\[31388\]: Failed password for invalid user pi from 60.216.181.115 port 33494 ssh2
...
2019-10-31 13:24:37
178.212.228.81 attack
[portscan] Port scan
2019-10-31 13:10:06
180.68.177.209 attack
2019-10-31T04:47:52.420363shield sshd\[18403\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.68.177.209  user=root
2019-10-31T04:47:54.199640shield sshd\[18403\]: Failed password for root from 180.68.177.209 port 36980 ssh2
2019-10-31T04:52:16.600219shield sshd\[19689\]: Invalid user mp from 180.68.177.209 port 50892
2019-10-31T04:52:16.604905shield sshd\[19689\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.68.177.209
2019-10-31T04:52:17.957893shield sshd\[19689\]: Failed password for invalid user mp from 180.68.177.209 port 50892 ssh2
2019-10-31 12:57:30
36.77.3.90 attackspam
SSH/22 MH Probe, BF, Hack -
2019-10-31 13:08:40
222.186.180.41 attackspam
F2B jail: sshd. Time: 2019-10-31 06:11:23, Reported by: VKReport
2019-10-31 13:13:22
222.186.175.182 attackspambots
Oct 31 06:00:56 h2177944 sshd\[22631\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.182  user=root
Oct 31 06:00:58 h2177944 sshd\[22631\]: Failed password for root from 222.186.175.182 port 55776 ssh2
Oct 31 06:01:02 h2177944 sshd\[22631\]: Failed password for root from 222.186.175.182 port 55776 ssh2
Oct 31 06:01:06 h2177944 sshd\[22631\]: Failed password for root from 222.186.175.182 port 55776 ssh2
...
2019-10-31 13:27:04
115.159.143.217 attack
2019-10-31T03:55:25.666283abusebot-5.cloudsearch.cf sshd\[26954\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.159.143.217  user=root
2019-10-31 13:20:44
46.38.144.146 attackbotsspam
Oct 31 06:44:18 relay postfix/smtpd\[22799\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: VXNlcm5hbWU6
Oct 31 06:45:04 relay postfix/smtpd\[21108\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: VXNlcm5hbWU6
Oct 31 06:45:33 relay postfix/smtpd\[18823\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: VXNlcm5hbWU6
Oct 31 06:46:18 relay postfix/smtpd\[21108\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: VXNlcm5hbWU6
Oct 31 06:46:47 relay postfix/smtpd\[18381\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: VXNlcm5hbWU6
...
2019-10-31 13:48:30
177.2.148.187 attack
19/10/30@23:54:37: FAIL: IoT-Telnet address from=177.2.148.187
...
2019-10-31 13:46:09
185.176.27.178 attackbots
Oct 31 06:14:16 mc1 kernel: \[3785176.756247\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.178 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=598 PROTO=TCP SPT=46086 DPT=12545 WINDOW=1024 RES=0x00 SYN URGP=0 
Oct 31 06:14:48 mc1 kernel: \[3785209.307149\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.178 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=51275 PROTO=TCP SPT=46086 DPT=22466 WINDOW=1024 RES=0x00 SYN URGP=0 
Oct 31 06:18:04 mc1 kernel: \[3785404.861853\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.178 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=38996 PROTO=TCP SPT=46086 DPT=48141 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-10-31 13:19:41
185.50.196.127 attackspambots
Attempted WordPress login: "GET /wp-login.php"
2019-10-31 12:54:30
45.227.253.140 attack
2019-10-31T06:11:54.090366mail01 postfix/smtpd[20998]: warning: unknown[45.227.253.140]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-10-31T06:12:01.218586mail01 postfix/smtpd[14279]: warning: unknown[45.227.253.140]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-10-31T06:12:33.060803mail01 postfix/smtpd[21490]: warning: unknown[45.227.253.140]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-10-31 13:13:42
117.159.84.145 attack
'IP reached maximum auth failures for a one day block'
2019-10-31 13:18:31

Recently Reported IPs

156.162.241.237 105.190.246.141 155.102.191.119 230.100.50.215
13.104.207.170 63.165.219.24 184.207.215.150 191.239.245.97
82.147.98.229 11.238.101.231 201.64.63.76 141.21.167.137
102.62.68.153 213.159.154.29 5.243.252.216 163.172.106.112
60.37.79.145 93.155.85.51 114.238.127.158 45.13.39.56