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

;; QUESTION SECTION:
;80.82.69.54.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jul 01 02:20:20 CST 2022
;; MSG SIZE  rcvd: 104
Host info
54.69.82.80.in-addr.arpa domain name pointer reverse.v4.constellationservers.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
54.69.82.80.in-addr.arpa	name = reverse.v4.constellationservers.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
115.112.61.221 attack
Invalid user danilete from 115.112.61.221 port 49414
2020-02-13 02:25:32
51.83.104.120 attack
$f2bV_matches
2020-02-13 02:12:09
177.1.214.207 attackbots
Automatic report - Banned IP Access
2020-02-13 02:16:38
35.206.156.221 attackspambots
Feb 12 18:47:16 markkoudstaal sshd[13401]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.206.156.221
Feb 12 18:47:18 markkoudstaal sshd[13401]: Failed password for invalid user jupyter from 35.206.156.221 port 39662 ssh2
Feb 12 18:50:23 markkoudstaal sshd[13950]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.206.156.221
2020-02-13 02:24:28
137.74.171.160 attackspam
$f2bV_matches
2020-02-13 01:56:45
106.75.30.102 attackbots
Fail2Ban Ban Triggered
2020-02-13 01:53:47
157.43.144.183 attack
1581515009 - 02/12/2020 14:43:29 Host: 157.43.144.183/157.43.144.183 Port: 445 TCP Blocked
2020-02-13 01:49:26
77.68.81.58 attackspam
Brute forcing email accounts
2020-02-13 02:05:17
190.151.105.182 attack
Feb 12 07:42:43 hpm sshd\[9443\]: Invalid user client1 from 190.151.105.182
Feb 12 07:42:43 hpm sshd\[9443\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.151.105.182
Feb 12 07:42:45 hpm sshd\[9443\]: Failed password for invalid user client1 from 190.151.105.182 port 32914 ssh2
Feb 12 07:47:22 hpm sshd\[10052\]: Invalid user postgres from 190.151.105.182
Feb 12 07:47:22 hpm sshd\[10052\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.151.105.182
2020-02-13 01:58:33
46.232.250.110 attackbotsspam
Feb 12 12:37:23 plusreed sshd[16515]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.232.250.110  user=postgres
Feb 12 12:37:25 plusreed sshd[16515]: Failed password for postgres from 46.232.250.110 port 51580 ssh2
...
2020-02-13 01:51:54
122.114.216.85 attackbots
Failed password for invalid user 12345qwert from 122.114.216.85 port 56790 ssh2
Invalid user sarah from 122.114.216.85 port 39296
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.114.216.85
Failed password for invalid user sarah from 122.114.216.85 port 39296 ssh2
Invalid user aces from 122.114.216.85 port 50034
2020-02-13 02:23:15
192.99.36.166 attackbotsspam
20 attempts against mh-misbehave-ban on sand
2020-02-13 01:52:18
103.130.105.132 attack
Automatic report - SSH Brute-Force Attack
2020-02-13 02:29:55
113.54.156.52 attack
SSH login attempts brute force.
2020-02-13 02:35:55
159.192.166.83 attackspam
Lines containing failures of 159.192.166.83
auth.log:Feb 12 14:30:57 omfg sshd[25735]: Connection from 159.192.166.83 port 56067 on 78.46.60.40 port 22
auth.log:Feb 12 14:30:57 omfg sshd[25736]: Connection from 159.192.166.83 port 56118 on 78.46.60.41 port 22
auth.log:Feb 12 14:30:57 omfg sshd[25737]: Connection from 159.192.166.83 port 56127 on 78.46.60.42 port 22
auth.log:Feb 12 14:31:00 omfg sshd[25735]: Did not receive identification string from 159.192.166.83
auth.log:Feb 12 14:31:00 omfg sshd[25736]: Did not receive identification string from 159.192.166.83
auth.log:Feb 12 14:31:00 omfg sshd[25737]: Did not receive identification string from 159.192.166.83
auth.log:Feb 12 14:31:07 omfg sshd[25738]: Connection from 159.192.166.83 port 64650 on 78.46.60.16 port 22
auth.log:Feb 12 14:31:07 omfg sshd[25739]: Connection from 159.192.166.83 port 64869 on 78.46.60.40 port 22
auth.log:Feb 12 14:31:07 omfg sshd[25740]: Connection from 159.192.166.83 port 64884 on 78.46.60.5........
------------------------------
2020-02-13 01:53:00

Recently Reported IPs

180.76.104.86 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 180.76.210.93 180.76.172.59 89.248.167.249
94.102.54.146 180.76.17.73 169.229.207.117 180.76.82.80
180.76.166.99 180.76.81.196 94.102.62.203 180.76.111.243