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

Region: Noord Holland

Country: The Netherlands

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
80.82.65.90 attackbotsspam
Port Scan: UDP/389
2020-10-14 05:21:42
80.82.65.90 attackbotsspam
[portscan] udp/1900 [ssdp]
*(RWIN=-)(10100855)
2020-10-10 22:12:31
80.82.65.90 attackbots
 UDP 80.82.65.90:38382 -> port 1900, len 118
2020-10-10 14:05:52
80.82.65.74 attackspambots
Port Scan: TCP/9100
2020-10-08 01:16:53
80.82.65.74 attack
[portscan] tcp/23 [TELNET]
[scan/connect: 2 time(s)]
*(RWIN=1024)(10061547)
2020-10-07 17:25:30
80.82.65.90 attack
ET CINS Active Threat Intelligence Poor Reputation IP group 68 - port: 389 proto: udp cat: Misc Attackbytes: 94
2020-10-06 07:54:12
80.82.65.90 attackspambots
3702/udp 1900/udp 389/udp...
[2020-08-04/10-04]543pkt,5pt.(udp)
2020-10-06 00:15:59
80.82.65.90 attack
Port scanning [4 denied]
2020-10-05 16:15:25
80.82.65.90 attack
ET CINS Active Threat Intelligence Poor Reputation IP group 68 - port: 53 proto: dns cat: Misc Attackbytes: 78
2020-10-05 01:27:53
80.82.65.90 attackbots
 UDP 80.82.65.90:37612 -> port 1900, len 118
2020-10-04 17:10:45
80.82.65.213 attack
[N10.H2.VM2] Port Scanner Detected Blocked by UFW
2020-10-04 03:06:49
80.82.65.74 attack
scans 5 times in preceeding hours on the ports (in chronological order) 1080 10099 8200 10114 8200 resulting in total of 275 scans from 80.82.64.0/20 block.
2020-10-01 07:45:17
80.82.65.90 attackspambots
scans once in preceeding hours on the ports (in chronological order) 1900 resulting in total of 275 scans from 80.82.64.0/20 block.
2020-10-01 07:44:48
80.82.65.60 attackspam
Massive scans
2020-10-01 05:44:20
80.82.65.74 attack
 TCP (SYN) 80.82.65.74:48577 -> port 20002, len 44
2020-10-01 00:14:13
Whois info:
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See https://docs.db.ripe.net/terms-conditions.html

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to '80.82.65.0 - 80.82.65.255'

% Abuse contact for '80.82.65.0 - 80.82.65.255' is 'abuse@ipvolume.net'

inetnum:        80.82.65.0 - 80.82.65.255
netname:        NET-1-65
descr:          IPV NETBLOCK
country:        NL
geoloc:         52.370216 4.895168
org:            ORG-IVI1-RIPE
admin-c:        IVI24-RIPE
tech-c:         IVI24-RIPE
status:         ASSIGNED PA
mnt-by:         IPV
mnt-lower:      IPV
mnt-routes:     IPV
created:        2010-09-30T19:51:08Z
last-modified:  2019-02-01T18:25:33Z
source:         RIPE

organisation:   ORG-IVI1-RIPE
org-name:       IP Volume inc
country:        SC
reg-nr:         203857
org-type:       OTHER
address:        House of Francis, Room 303, Victoria, English River, Seychelles
abuse-c:        IVNO1-RIPE
mnt-ref:        IPV
mnt-by:         IPV
created:        2018-05-14T11:46:50Z
last-modified:  2026-05-13T05:23:58Z
source:         RIPE # Filtered

role:           IPV
address:        BZ
nic-hdl:        IVI24-RIPE
mnt-by:         IPV
created:        2018-05-16T13:28:41Z
last-modified:  2023-09-08T14:14:36Z
source:         RIPE # Filtered

% Information related to '80.82.65.0/24AS202425'

route:          80.82.65.0/24
origin:         AS202425
remarks:        +-----------------------------------------------
remarks:        | For abuse e-mail abuse@ipvolume.net
remarks:        | We do not always reply to abuse.
remarks:        | But we do take care your report is dealt with!
remarks:        +-----------------------------------------------
mnt-by:         IPV
created:        2019-02-01T14:49:03Z
last-modified:  2019-02-01T14:49:03Z
source:         RIPE

% This query was served by the RIPE Database Query Service version 1.124.1 (ABERDEEN)
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 80.82.65.22
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61268
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;80.82.65.22.			IN	A

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

;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Oct 26 08:30:28 CST 2026
;; MSG SIZE  rcvd: 104
Host info
22.65.82.80.in-addr.arpa domain name pointer no-reverse-dns-configured.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
22.65.82.80.in-addr.arpa	name = no-reverse-dns-configured.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
104.41.41.24 attack
SSH brutforce
2020-06-25 07:45:51
203.195.175.47 attack
2020-06-25T06:07:19.882105billing sshd[17203]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.195.175.47
2020-06-25T06:07:19.842585billing sshd[17203]: Invalid user mailtest from 203.195.175.47 port 44942
2020-06-25T06:07:22.078163billing sshd[17203]: Failed password for invalid user mailtest from 203.195.175.47 port 44942 ssh2
...
2020-06-25 07:46:49
59.145.221.103 attack
Jun 25 02:03:56 lukav-desktop sshd\[30191\]: Invalid user john1 from 59.145.221.103
Jun 25 02:03:56 lukav-desktop sshd\[30191\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.145.221.103
Jun 25 02:03:58 lukav-desktop sshd\[30191\]: Failed password for invalid user john1 from 59.145.221.103 port 33691 ssh2
Jun 25 02:07:37 lukav-desktop sshd\[6650\]: Invalid user sport from 59.145.221.103
Jun 25 02:07:37 lukav-desktop sshd\[6650\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.145.221.103
2020-06-25 07:31:00
192.241.202.169 attack
Jun 24 20:06:40 firewall sshd[21869]: Invalid user muan from 192.241.202.169
Jun 24 20:06:41 firewall sshd[21869]: Failed password for invalid user muan from 192.241.202.169 port 45246 ssh2
Jun 24 20:07:43 firewall sshd[21887]: Invalid user ubuntu from 192.241.202.169
...
2020-06-25 07:24:54
206.189.188.218 attack
trying to access non-authorized port
2020-06-25 07:41:54
180.76.103.27 attackspam
detected by Fail2Ban
2020-06-25 07:41:13
190.156.238.155 attackbotsspam
Jun 24 16:00:42 dignus sshd[5738]: Failed password for invalid user tar from 190.156.238.155 port 53572 ssh2
Jun 24 16:04:17 dignus sshd[6110]: Invalid user guest from 190.156.238.155 port 52630
Jun 24 16:04:17 dignus sshd[6110]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.156.238.155
Jun 24 16:04:19 dignus sshd[6110]: Failed password for invalid user guest from 190.156.238.155 port 52630 ssh2
Jun 24 16:07:47 dignus sshd[6574]: Invalid user marin from 190.156.238.155 port 51676
...
2020-06-25 07:23:01
151.61.204.109 attackspambots
port scan and connect, tcp 22 (ssh)
2020-06-25 07:44:00
192.241.217.63 attackspam
Scan or attack attempt on email service.
2020-06-25 07:37:35
134.175.196.241 attack
Jun 25 01:21:43 eventyay sshd[15163]: Failed password for root from 134.175.196.241 port 49966 ssh2
Jun 25 01:26:29 eventyay sshd[15323]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.196.241
Jun 25 01:26:31 eventyay sshd[15323]: Failed password for invalid user tiago from 134.175.196.241 port 49564 ssh2
...
2020-06-25 07:32:23
192.35.169.18 attackspam
Jun 25 01:07:17 debian-2gb-nbg1-2 kernel: \[15298701.872841\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=192.35.169.18 DST=195.201.40.59 LEN=44 TOS=0x00 PREC=0x00 TTL=34 ID=5800 PROTO=TCP SPT=18419 DPT=8443 WINDOW=1024 RES=0x00 SYN URGP=0
2020-06-25 07:47:56
49.233.162.198 attackspambots
2020-06-24T23:03:35.042524shield sshd\[12776\]: Invalid user yamazaki from 49.233.162.198 port 49956
2020-06-24T23:03:35.046119shield sshd\[12776\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.233.162.198
2020-06-24T23:03:36.862081shield sshd\[12776\]: Failed password for invalid user yamazaki from 49.233.162.198 port 49956 ssh2
2020-06-24T23:08:00.943714shield sshd\[13362\]: Invalid user css from 49.233.162.198 port 41858
2020-06-24T23:08:00.947464shield sshd\[13362\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.233.162.198
2020-06-25 07:12:28
161.202.18.153 attack
Jun 25 01:18:47 piServer sshd[11785]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=161.202.18.153 
Jun 25 01:18:50 piServer sshd[11785]: Failed password for invalid user user from 161.202.18.153 port 52986 ssh2
Jun 25 01:22:35 piServer sshd[12223]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=161.202.18.153 
...
2020-06-25 07:42:36
77.210.180.10 attackspambots
Jun 25 00:59:19 DAAP sshd[4873]: Invalid user ible from 77.210.180.10 port 35004
Jun 25 00:59:19 DAAP sshd[4873]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.210.180.10
Jun 25 00:59:19 DAAP sshd[4873]: Invalid user ible from 77.210.180.10 port 35004
Jun 25 00:59:21 DAAP sshd[4873]: Failed password for invalid user ible from 77.210.180.10 port 35004 ssh2
Jun 25 01:07:37 DAAP sshd[4947]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.210.180.10  user=root
Jun 25 01:07:39 DAAP sshd[4947]: Failed password for root from 77.210.180.10 port 57634 ssh2
...
2020-06-25 07:30:30
103.111.196.18 attackspambots
Unauthorized connection attempt: SRC=103.111.196.18
...
2020-06-25 07:24:34

Recently Reported IPs

115.60.94.19 110.52.175.218 110.246.18.156 101.26.28.237
101.24.181.78 162.216.150.7 34.150.128.205 199.165.159.73
20.65.202.135 199.165.159.79 199.165.159.78 118.213.34.132
34.203.242.177 18.208.214.137 139.59.13.193 102.39.205.125
5.133.192.160 146.19.248.35 185.143.14.119 134.33.66.242