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

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

;; QUESTION SECTION:
;195.80.185.34.			IN	A

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

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 12 21:37:53 CST 2025
;; MSG SIZE  rcvd: 106
Host info
34.185.80.195.in-addr.arpa domain name pointer linek34.ba.psg.sk.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
34.185.80.195.in-addr.arpa	name = linek34.ba.psg.sk.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
162.144.102.140 attackspam
Jul  5 06:16:06 mxgate1 postfix/postscreen[8519]: CONNECT from [162.144.102.140]:55156 to [176.31.12.44]:25
Jul  5 06:16:06 mxgate1 postfix/dnsblog[8673]: addr 162.144.102.140 listed by domain cbl.abuseat.org as 127.0.0.2
Jul  5 06:16:06 mxgate1 postfix/dnsblog[8675]: addr 162.144.102.140 listed by domain zen.spamhaus.org as 127.0.0.4
Jul  5 06:16:06 mxgate1 postfix/dnsblog[8674]: addr 162.144.102.140 listed by domain bl.spamcop.net as 127.0.0.2
Jul  5 06:16:06 mxgate1 postfix/dnsblog[8672]: addr 162.144.102.140 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Jul  5 06:16:06 mxgate1 postfix/dnsblog[8671]: addr 162.144.102.140 listed by domain b.barracudacentral.org as 127.0.0.2
Jul  5 06:16:12 mxgate1 postfix/postscreen[8519]: DNSBL rank 6 for [162.144.102.140]:55156
Jul x@x
Jul  5 06:16:13 mxgate1 postfix/postscreen[8519]: HANGUP after 0.81 from [162.144.102.140]:55156 in tests after SMTP handshake
Jul  5 06:16:13 mxgate1 postfix/postscreen[8519]: DISCONNECT [162.144........
-------------------------------
2019-07-07 02:09:44
60.255.146.181 attackbots
Jul  6 17:26:21 microserver sshd[47244]: Invalid user admin from 60.255.146.181 port 38444
Jul  6 17:26:21 microserver sshd[47244]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.255.146.181
Jul  6 17:26:23 microserver sshd[47244]: Failed password for invalid user admin from 60.255.146.181 port 38444 ssh2
Jul  6 17:26:27 microserver sshd[47244]: Failed password for invalid user admin from 60.255.146.181 port 38444 ssh2
Jul  6 17:26:32 microserver sshd[47244]: Failed password for invalid user admin from 60.255.146.181 port 38444 ssh2
2019-07-07 02:34:09
110.76.149.161 attackspam
Autoban   110.76.149.161 AUTH/CONNECT
2019-07-07 02:17:22
187.85.214.44 attack
failed_logins
2019-07-07 02:10:06
91.144.129.129 attack
WordPress wp-login brute force :: 91.144.129.129 0.064 BYPASS [06/Jul/2019:23:27:17  1000] www.[censored_4] "POST /wp-login.php HTTP/1.1" 200 3538 "https://[censored_4]/wp-login.php" "Mozilla/5.0 (Windows NT 6.0; rv:34.0) Gecko/20100101 Firefox/34.0"
2019-07-07 02:18:18
59.31.90.206 attackspambots
Mail sent to address obtained from MySpace hack
2019-07-07 02:30:13
89.248.160.193 attackbotsspam
MultiHost/MultiPort Probe, Scan, Hack -
2019-07-07 01:51:06
112.222.29.147 attackbots
Jul  6 16:15:12 vps647732 sshd[2115]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.222.29.147
Jul  6 16:15:14 vps647732 sshd[2115]: Failed password for invalid user ws from 112.222.29.147 port 51244 ssh2
...
2019-07-07 01:53:59
185.211.245.170 attackbots
Jul  6 13:15:43 web1 postfix/smtpd[15600]: warning: unknown[185.211.245.170]: SASL LOGIN authentication failed: authentication failure
...
2019-07-07 01:43:43
210.13.45.70 attackbots
Jul  6 16:55:22 mail sshd\[24094\]: Invalid user qaz_2wsx from 210.13.45.70 port 53720
Jul  6 16:55:22 mail sshd\[24094\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.13.45.70
Jul  6 16:55:25 mail sshd\[24094\]: Failed password for invalid user qaz_2wsx from 210.13.45.70 port 53720 ssh2
Jul  6 16:58:30 mail sshd\[24420\]: Invalid user ftpuser!@\# from 210.13.45.70 port 48910
Jul  6 16:58:30 mail sshd\[24420\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.13.45.70
2019-07-07 02:25:42
201.245.172.74 attack
Jul  6 13:27:18 *** sshd[29624]: Invalid user vertige from 201.245.172.74
2019-07-07 02:16:16
178.128.84.246 attackspambots
$f2bV_matches
2019-07-07 01:49:19
128.199.202.206 attackbotsspam
Repeated brute force against a port
2019-07-07 01:44:13
139.219.6.45 attackbots
Lines containing failures of 139.219.6.45


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=139.219.6.45
2019-07-07 02:05:23
173.249.7.108 attackbotsspam
Jul  6 18:28:43 mail1 sshd\[12144\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.249.7.108  user=root
Jul  6 18:28:45 mail1 sshd\[12144\]: Failed password for root from 173.249.7.108 port 52612 ssh2
Jul  6 18:29:08 mail1 sshd\[12371\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.249.7.108  user=root
Jul  6 18:29:10 mail1 sshd\[12371\]: Failed password for root from 173.249.7.108 port 55724 ssh2
Jul  6 18:29:34 mail1 sshd\[12521\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.249.7.108  user=root
...
2019-07-07 02:28:19

Recently Reported IPs

61.189.66.66 227.37.143.23 40.175.90.0 249.81.25.188
37.153.53.92 240.87.212.88 122.76.19.56 49.66.196.185
22.20.13.147 32.236.21.140 187.211.108.10 114.132.153.133
201.182.218.180 22.97.212.50 33.118.57.7 5.48.35.201
115.185.48.148 229.209.202.115 138.144.124.186 251.225.241.191