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

Internet Service Provider: Speedynet Comunicacao Multimidia

Hostname: unknown

Organization: unknown

Usage Type: Commercial

Comments:
Type Details Datetime
attackspam
Jan 26 05:28:50 vzmaster sshd[2363]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.168.34.0  user=r.r
Jan 26 05:28:52 vzmaster sshd[2363]: Failed password for r.r from 45.168.34.0 port 34539 ssh2
Jan 26 05:28:53 vzmaster sshd[2363]: Failed password for r.r from 45.168.34.0 port 34539 ssh2
Jan 26 05:28:56 vzmaster sshd[2363]: Failed password for r.r from 45.168.34.0 port 34539 ssh2
Jan 26 05:28:58 vzmaster sshd[2363]: Failed password for r.r from 45.168.34.0 port 34539 ssh2
Jan 26 05:29:00 vzmaster sshd[2363]: Failed password for r.r from 45.168.34.0 port 34539 ssh2
Jan 26 05:29:02 vzmaster sshd[2363]: Failed password for r.r from 45.168.34.0 port 34539 ssh2
Jan 26 05:29:02 vzmaster sshd[2363]: PAM 5 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.168.34.0  user=r.r
Jan 26 05:29:06 vzmaster sshd[2796]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.168.34.........
-------------------------------
2020-01-26 20:11:54
Comments on same subnet:
IP Type Details Datetime
45.168.34.176 attackbotsspam
Unauthorized connection attempt detected from IP address 45.168.34.176 to port 23
2020-04-10 04:20:26
45.168.34.62 attackspambots
2019-10-29T21:22:01.512Z CLOSE host=45.168.34.62 port=34139 fd=4 time=20.021 bytes=7
...
2020-03-13 04:10:01
45.168.34.148 attackbots
2019-12-03T15:11:53.212Z CLOSE host=45.168.34.148 port=56540 fd=4 time=20.020 bytes=26
...
2020-03-13 04:09:45
45.168.34.36 attackbotsspam
ssh intrusion attempt
2020-01-15 15:09:55
45.168.34.64 attackspambots
Dec 17 15:08:13 pl3server sshd[14609]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.168.34.64  user=r.r
Dec 17 15:08:15 pl3server sshd[14609]: Failed password for r.r from 45.168.34.64 port 44982 ssh2
Dec 17 15:08:17 pl3server sshd[14609]: Failed password for r.r from 45.168.34.64 port 44982 ssh2
Dec 17 15:08:19 pl3server sshd[14609]: Failed password for r.r from 45.168.34.64 port 44982 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=45.168.34.64
2019-12-18 02:45:55
45.168.34.76 attack
SSH login attempts brute force.
2019-11-29 22:28:12
45.168.34.149 attackbotsspam
[Wed Oct  9 21:28:03 2019] Failed password for r.r from 45.168.34.149 port 51074 ssh2
[Wed Oct  9 21:28:07 2019] Failed password for r.r from 45.168.34.149 port 51074 ssh2
[Wed Oct  9 21:28:11 2019] Failed password for r.r from 45.168.34.149 port 51074 ssh2
[Wed Oct  9 21:28:14 2019] Failed password for r.r from 45.168.34.149 port 51074 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=45.168.34.149
2019-10-10 05:23:52
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 45.168.34.0
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 43322
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 30 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 26 20:11:49 CST 2020
;; MSG SIZE  rcvd: 115
Host info
Host 0.34.168.45.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 0.34.168.45.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
183.193.234.70 attackbotsspam
Unauthorized connection attempt detected from IP address 183.193.234.70 to port 23 [T]
2020-01-16 00:44:00
120.211.29.106 attackspambots
Unauthorized connection attempt detected from IP address 120.211.29.106 to port 22 [T]
2020-01-16 00:52:39
61.178.14.202 attackbots
Unauthorized connection attempt detected from IP address 61.178.14.202 to port 445 [T]
2020-01-16 01:04:10
39.96.8.155 attack
Unauthorized connection attempt detected from IP address 39.96.8.155 to port 8080 [T]
2020-01-16 01:12:56
119.165.5.206 attack
Unauthorized connection attempt detected from IP address 119.165.5.206 to port 23 [J]
2020-01-16 00:53:01
220.248.173.29 attack
Unauthorized connection attempt detected from IP address 220.248.173.29 to port 3389 [T]
2020-01-16 00:41:15
27.223.203.187 attackbots
Unauthorized connection attempt detected from IP address 27.223.203.187 to port 2323 [J]
2020-01-16 00:37:33
110.153.66.90 attackbotsspam
Unauthorized connection attempt detected from IP address 110.153.66.90 to port 23 [T]
2020-01-16 01:01:09
42.113.68.98 attackspambots
Unauthorized connection attempt detected from IP address 42.113.68.98 to port 23 [J]
2020-01-16 01:11:03
42.116.43.103 attackspambots
Unauthorized connection attempt detected from IP address 42.116.43.103 to port 23 [T]
2020-01-16 01:10:16
180.123.120.94 attackbots
Unauthorized connection attempt detected from IP address 180.123.120.94 to port 8080 [T]
2020-01-16 00:46:37
111.61.120.147 attack
Unauthorized connection attempt detected from IP address 111.61.120.147 to port 22 [T]
2020-01-16 01:00:18
42.118.70.183 attack
Unauthorized connection attempt detected from IP address 42.118.70.183 to port 23 [J]
2020-01-16 01:08:41
42.119.139.190 attackbots
Telnetd brute force attack detected by fail2ban
2020-01-16 01:08:06
223.10.70.165 attack
Unauthorized connection attempt detected from IP address 223.10.70.165 to port 23 [J]
2020-01-16 01:14:58

Recently Reported IPs

61.228.30.24 93.41.154.177 45.190.220.136 95.3.96.61
166.145.142.208 46.28.77.192 194.78.5.52 82.137.201.69
121.98.55.251 104.131.162.164 37.78.239.209 148.255.79.92
62.234.186.27 27.180.251.40 125.25.180.172 210.209.72.232
113.64.145.36 174.219.13.28 123.175.100.13 180.76.177.194