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: United Kingdom

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.69.130 attackbots
scans 3 times in preceeding hours on the ports (in chronological order) 30030 30074 30027 resulting in total of 33 scans from 80.82.64.0/20 block.
2020-05-22 01:32:15
80.82.69.130 attackbots
May 20 09:49:40 debian-2gb-nbg1-2 kernel: \[12219807.374803\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=80.82.69.130 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=57727 PROTO=TCP SPT=50683 DPT=30034 WINDOW=1024 RES=0x00 SYN URGP=0
2020-05-20 16:17:46
80.82.69.130 attackbots
TCP ports : 30143 / 30157
2020-05-17 05:01:38
80.82.69.130 attackspam
Multiport scan : 21 ports scanned 25018 25020 25033 25046 25050 25054 25059 25077 25081 25085 25088 25092 25100 25104 25111 25121 25127 25149 25166 25176 25190
2020-05-12 08:41:28
80.82.69.130 attackbotsspam
 TCP (SYN) 80.82.69.130:54845 -> port 25098, len 44
2020-05-11 02:11:49
80.82.69.130 attackbots
ET CINS Active Threat Intelligence Poor Reputation IP group 67 - port: 25133 proto: TCP cat: Misc Attack
2020-05-09 22:35:39
80.82.69.130 attack
05/06/2020-12:53:14.669050 80.82.69.130 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-05-07 03:04:46
80.82.69.130 attackbots
firewall-block, port(s): 25020/tcp, 25050/tcp, 25092/tcp, 25097/tcp, 25099/tcp, 25126/tcp, 25178/tcp
2020-05-06 14:33:23
80.82.69.130 attack
[MK-Root1] Blocked by UFW
2020-05-03 05:20:41
80.82.69.130 attackspam
Port scan(s) denied
2020-05-01 21:26:00
80.82.69.130 attackbotsspam
Scanning for open ports and vulnerable services: 34909,34912,34914,34925,34933,34943,34952,34957,34961,34964,34977,34978,34982,34985,34988,34989,34990
2020-04-30 15:00:47
80.82.69.130 attackspambots
Apr 27 00:14:52 debian-2gb-nbg1-2 kernel: \[10198225.924146\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=80.82.69.130 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=16347 PROTO=TCP SPT=52921 DPT=34916 WINDOW=1024 RES=0x00 SYN URGP=0
2020-04-27 06:19:42
80.82.69.130 attackspambots
04/25/2020-10:43:36.973333 80.82.69.130 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-04-25 22:49:41
80.82.69.129 attackspambots
" "
2020-04-21 04:41:24
80.82.69.249 attackbotsspam
Tried sshing with brute force.
2020-04-05 17:47:02
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 80.82.69.237
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 7433
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;80.82.69.237.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jun 29 14:40:20 CST 2022
;; MSG SIZE  rcvd: 105
Host info
237.69.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:
237.69.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
123.253.228.162 attack
Jul 27 23:53:33 r.ca sshd[14029]: Failed password for invalid user smrtuser from 123.253.228.162 port 39670 ssh2
2020-07-28 12:14:09
143.255.130.2 attackbotsspam
2020-07-28T01:47:13.420997lavrinenko.info sshd[26577]: Invalid user ldf from 143.255.130.2 port 60110
2020-07-28T01:47:13.428343lavrinenko.info sshd[26577]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=143.255.130.2
2020-07-28T01:47:13.420997lavrinenko.info sshd[26577]: Invalid user ldf from 143.255.130.2 port 60110
2020-07-28T01:47:15.537071lavrinenko.info sshd[26577]: Failed password for invalid user ldf from 143.255.130.2 port 60110 ssh2
2020-07-28T01:50:36.391353lavrinenko.info sshd[26714]: Invalid user bishe from 143.255.130.2 port 53390
...
2020-07-28 07:56:49
39.101.185.232 attack
SSH Brute-Forcing (server2)
2020-07-28 08:15:29
36.89.251.105 attack
36.89.251.105 - - [28/Jul/2020:01:00:39 +0200] "POST /xmlrpc.php HTTP/1.1" 403 146 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
36.89.251.105 - - [28/Jul/2020:01:18:46 +0200] "POST /xmlrpc.php HTTP/1.1" 403 146 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-07-28 08:05:27
132.232.14.159 attack
2020-07-27T20:26:02.571843ionos.janbro.de sshd[55088]: Invalid user sunhaibo from 132.232.14.159 port 41580
2020-07-27T20:26:04.764603ionos.janbro.de sshd[55088]: Failed password for invalid user sunhaibo from 132.232.14.159 port 41580 ssh2
2020-07-27T20:32:17.297668ionos.janbro.de sshd[55138]: Invalid user zhaoyue from 132.232.14.159 port 52866
2020-07-27T20:32:17.497436ionos.janbro.de sshd[55138]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.14.159
2020-07-27T20:32:17.297668ionos.janbro.de sshd[55138]: Invalid user zhaoyue from 132.232.14.159 port 52866
2020-07-27T20:32:19.497944ionos.janbro.de sshd[55138]: Failed password for invalid user zhaoyue from 132.232.14.159 port 52866 ssh2
2020-07-27T20:38:35.659056ionos.janbro.de sshd[55174]: Invalid user xinyi from 132.232.14.159 port 35922
2020-07-27T20:38:35.932739ionos.janbro.de sshd[55174]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232
...
2020-07-28 08:00:45
139.59.116.115 attackspambots
2020-07-28T03:55:31.779400shield sshd\[17703\]: Invalid user helirong from 139.59.116.115 port 51884
2020-07-28T03:55:31.788286shield sshd\[17703\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.116.115
2020-07-28T03:55:34.347098shield sshd\[17703\]: Failed password for invalid user helirong from 139.59.116.115 port 51884 ssh2
2020-07-28T03:57:49.879215shield sshd\[18226\]: Invalid user bitnami from 139.59.116.115 port 46988
2020-07-28T03:57:49.890278shield sshd\[18226\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.116.115
2020-07-28 12:14:47
178.62.22.142 attack
Multiple SSH authentication failures from 178.62.22.142
2020-07-28 07:56:22
51.210.107.84 attackbotsspam
Jul 28 14:00:01 NG-HHDC-SVS-001 sshd[13299]: Invalid user it from 51.210.107.84
...
2020-07-28 12:17:07
37.187.104.135 attackbotsspam
Jul 28 00:17:21 vserver sshd\[4351\]: Invalid user yamamichi from 37.187.104.135Jul 28 00:17:22 vserver sshd\[4351\]: Failed password for invalid user yamamichi from 37.187.104.135 port 33872 ssh2Jul 28 00:20:50 vserver sshd\[4449\]: Invalid user guojingjing from 37.187.104.135Jul 28 00:20:51 vserver sshd\[4449\]: Failed password for invalid user guojingjing from 37.187.104.135 port 45028 ssh2
...
2020-07-28 08:07:45
217.27.120.241 attackspambots
Port 22 Scan, PTR: None
2020-07-28 08:12:34
103.153.78.56 attackspambots
E-Mail Spam (RBL) [REJECTED]
2020-07-28 12:04:03
202.29.33.245 attackbots
Jul 28 09:15:52 NG-HHDC-SVS-001 sshd[6609]: Invalid user dig from 202.29.33.245
...
2020-07-28 08:07:22
122.224.0.74 attackspambots
20/7/27@23:57:50: FAIL: Alarm-Network address from=122.224.0.74
...
2020-07-28 12:14:28
186.16.14.107 attack
"fail2ban match"
2020-07-28 12:16:24
90.177.244.100 attackbots
Automatic report - Banned IP Access
2020-07-28 07:57:40

Recently Reported IPs

187.145.45.242 178.137.16.130 187.142.80.253 187.28.105.98
187.200.9.252 190.134.168.108 80.82.64.60 169.229.182.25
169.229.182.74 169.229.208.134 169.229.220.86 169.229.222.74
169.229.217.173 169.229.182.27 169.229.222.231 94.102.49.48
14.236.0.86 180.76.80.197 169.229.247.111 94.102.62.226