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

;; QUESTION SECTION:
;80.82.69.210.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jul 01 02:17:16 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 210.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 210.69.82.80.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
176.197.234.82 attackbots
23/tcp
[2020-02-12]1pkt
2020-02-13 05:42:42
125.160.222.128 attack
23/tcp
[2020-02-12]1pkt
2020-02-13 06:00:48
101.71.3.102 attackspambots
Feb 12 16:40:28 mout sshd[10173]: Invalid user buildbot from 101.71.3.102 port 9708
2020-02-13 05:44:07
31.46.202.12 attackbots
Feb 12 14:39:30 ArkNodeAT sshd\[21125\]: Invalid user carly from 31.46.202.12
Feb 12 14:39:30 ArkNodeAT sshd\[21125\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.46.202.12
Feb 12 14:39:32 ArkNodeAT sshd\[21125\]: Failed password for invalid user carly from 31.46.202.12 port 53358 ssh2
2020-02-13 05:31:31
175.113.235.76 attack
Seq 2995002506
2020-02-13 05:26:54
1.4.185.26 attackbots
23/tcp
[2020-02-12]1pkt
2020-02-13 05:37:22
54.148.226.208 attackbots
02/12/2020-22:46:46.847494 54.148.226.208 Protocol: 6 SURICATA TLS invalid record/traffic
2020-02-13 05:58:28
164.132.49.98 attack
Automatic report - SSH Brute-Force Attack
2020-02-13 05:23:15
162.247.74.201 attackspambots
02/12/2020-20:44:08.324295 162.247.74.201 Protocol: 6 ET TOR Known Tor Exit Node Traffic group 14
2020-02-13 05:22:29
104.248.154.62 attackbotsspam
Telnet/23 MH Probe, BF, Hack -
2020-02-13 05:59:17
187.15.6.250 attack
1581514754 - 02/12/2020 14:39:14 Host: 187.15.6.250/187.15.6.250 Port: 445 TCP Blocked
2020-02-13 05:51:12
194.187.249.41 attackbots
Feb 12 10:39:19 ws24vmsma01 sshd[225396]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=194.187.249.41
Feb 12 10:39:21 ws24vmsma01 sshd[225396]: Failed password for invalid user openelec from 194.187.249.41 port 37457 ssh2
...
2020-02-13 05:42:19
35.224.199.230 attackspam
Feb 12 17:40:31 server sshd\[27737\]: Invalid user donrepara from 35.224.199.230
Feb 12 17:40:31 server sshd\[27737\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=230.199.224.35.bc.googleusercontent.com 
Feb 12 17:40:32 server sshd\[27737\]: Failed password for invalid user donrepara from 35.224.199.230 port 41188 ssh2
Feb 12 17:44:08 server sshd\[28123\]: Invalid user cinstall from 35.224.199.230
Feb 12 17:44:08 server sshd\[28123\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=230.199.224.35.bc.googleusercontent.com 
...
2020-02-13 05:56:37
117.7.200.193 attackspambots
20/2/12@08:39:38: FAIL: IoT-Telnet address from=117.7.200.193
...
2020-02-13 05:27:22
218.92.0.189 attackspambots
Feb 12 22:49:48 legacy sshd[29266]: Failed password for root from 218.92.0.189 port 35659 ssh2
Feb 12 22:50:48 legacy sshd[29367]: Failed password for root from 218.92.0.189 port 26652 ssh2
Feb 12 22:50:50 legacy sshd[29367]: Failed password for root from 218.92.0.189 port 26652 ssh2
...
2020-02-13 05:53:55

Recently Reported IPs

80.82.67.144 180.76.193.188 180.76.212.76 180.76.192.107
28.74.23.71 62.46.224.207 180.76.185.171 180.76.185.237
180.76.192.55 180.76.122.206 180.76.104.86 80.82.69.54
80.82.69.51 80.82.69.47 80.82.70.60 169.229.253.201
154.30.185.33 180.76.210.141 80.82.77.60 62.171.168.103