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

;; QUESTION SECTION:
;80.82.69.188.			IN	A

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

;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jun 29 16:28:22 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 188.69.82.80.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 188.69.82.80.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
139.59.58.155 attackspam
SSH Brute-Force reported by Fail2Ban
2020-04-23 08:06:51
200.194.25.98 attackbotsspam
Automatic report - Port Scan Attack
2020-04-23 07:58:29
51.137.94.78 attackspambots
Invalid user zy from 51.137.94.78 port 51198
2020-04-23 07:53:20
191.235.91.156 attackbots
Invalid user test from 191.235.91.156 port 35986
2020-04-23 07:48:06
51.77.147.5 attackspambots
k+ssh-bruteforce
2020-04-23 08:04:37
222.239.28.177 attackbotsspam
Invalid user nx from 222.239.28.177 port 60088
2020-04-23 07:41:16
206.189.225.85 attackspambots
Invalid user vo from 206.189.225.85 port 53808
2020-04-23 07:52:00
144.217.34.148 attackspambots
144.217.34.148 was recorded 15 times by 11 hosts attempting to connect to the following ports: 30120,1900,2303. Incident counter (4h, 24h, all-time): 15, 22, 2082
2020-04-23 08:12:00
18.162.124.44 attack
Apr 22 20:07:46 game-panel sshd[14960]: Failed password for root from 18.162.124.44 port 41908 ssh2
Apr 22 20:12:29 game-panel sshd[15239]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=18.162.124.44
Apr 22 20:12:31 game-panel sshd[15239]: Failed password for invalid user postgres from 18.162.124.44 port 50074 ssh2
2020-04-23 07:50:42
220.178.75.153 attack
$f2bV_matches
2020-04-23 08:01:43
134.122.73.25 attack
Apr 23 01:34:36 vps sshd[803163]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.73.25
Apr 23 01:34:39 vps sshd[803163]: Failed password for invalid user wq from 134.122.73.25 port 41274 ssh2
Apr 23 01:38:00 vps sshd[821307]: Invalid user zh from 134.122.73.25 port 44508
Apr 23 01:38:00 vps sshd[821307]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.73.25
Apr 23 01:38:02 vps sshd[821307]: Failed password for invalid user zh from 134.122.73.25 port 44508 ssh2
...
2020-04-23 07:42:54
51.91.77.104 attackbots
SASL PLAIN auth failed: ruser=...
2020-04-23 07:48:21
120.151.222.78 attackspam
Invalid user tester from 120.151.222.78 port 55850
2020-04-23 08:08:49
51.77.148.77 attack
detected by Fail2Ban
2020-04-23 08:16:39
171.103.158.58 attackspambots
Unauthorized SMTP/IMAP/POP3 connection attempt
2020-04-23 07:54:47

Recently Reported IPs

180.76.6.224 180.76.86.181 180.76.149.41 180.76.7.201
180.76.182.123 80.82.78.41 180.76.187.214 180.76.117.214
180.76.6.64 180.76.28.164 180.76.6.162 169.229.198.231
180.76.6.145 180.76.86.180 91.250.41.15 180.76.7.206
169.229.54.217 137.226.53.193 180.224.145.145 200.183.184.146