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: Czech Republic

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

;; QUESTION SECTION:
;5.45.62.80.			IN	A

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

;; Query time: 65 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 08 12:24:07 CST 2022
;; MSG SIZE  rcvd: 103
Host info
80.62.45.5.in-addr.arpa domain name pointer vpn-gw-prod-002.ams1.ff.avast.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
80.62.45.5.in-addr.arpa	name = vpn-gw-prod-002.ams1.ff.avast.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
179.43.160.47 attackbots
Autoban   179.43.160.47 AUTH/CONNECT
2019-06-25 12:05:21
181.170.195.204 attackbots
Autoban   181.170.195.204 AUTH/CONNECT
2019-06-25 11:35:01
180.93.191.232 attackbotsspam
Autoban   180.93.191.232 AUTH/CONNECT
2019-06-25 11:51:10
62.4.13.108 attack
Jun 25 02:54:09 MainVPS sshd[7873]: Invalid user cms from 62.4.13.108 port 52058
Jun 25 02:54:09 MainVPS sshd[7873]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.4.13.108
Jun 25 02:54:09 MainVPS sshd[7873]: Invalid user cms from 62.4.13.108 port 52058
Jun 25 02:54:11 MainVPS sshd[7873]: Failed password for invalid user cms from 62.4.13.108 port 52058 ssh2
Jun 25 02:56:36 MainVPS sshd[8075]: Invalid user mashby from 62.4.13.108 port 51188
...
2019-06-25 11:38:46
181.166.207.74 attack
Autoban   181.166.207.74 AUTH/CONNECT
2019-06-25 11:39:22
181.20.220.120 attackspam
Autoban   181.20.220.120 AUTH/CONNECT
2019-06-25 11:28:20
180.189.80.228 attackbotsspam
Autoban   180.189.80.228 AUTH/CONNECT
2019-06-25 11:55:11
191.184.203.71 attackspambots
Jun 25 05:06:58 lnxmail61 sshd[18785]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=191.184.203.71
Jun 25 05:06:58 lnxmail61 sshd[18785]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=191.184.203.71
2019-06-25 11:33:00
181.122.229.87 attack
Autoban   181.122.229.87 AUTH/CONNECT
2019-06-25 11:45:39
159.65.141.6 attackspambots
Brute forcing Wordpress login
2019-06-25 12:11:45
179.127.166.16 attackbots
Autoban   179.127.166.16 AUTH/CONNECT
2019-06-25 12:18:00
87.228.67.124 attackbots
Jun 25 00:01:59 xeon sshd[12494]: Invalid user zimbra from 87.228.67.124
2019-06-25 11:54:41
181.177.243.129 attackspambots
Autoban   181.177.243.129 AUTH/CONNECT
2019-06-25 11:29:42
46.209.216.43 attackbots
MYH,DEF GET /wp-login.php
GET /wp-login.php
2019-06-25 11:47:32
190.217.26.154 attack
$f2bV_matches
2019-06-25 11:28:57

Recently Reported IPs

47.98.150.143 105.112.113.193 103.172.115.188 123.205.186.144
101.33.69.253 52.2.46.34 146.120.175.254 103.85.159.225
175.107.2.171 167.58.21.153 109.86.231.5 182.61.133.15
177.78.57.99 177.119.248.139 5.199.202.129 14.207.179.92
14.190.77.102 103.104.183.65 194.158.72.220 14.183.177.120