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

;; QUESTION SECTION:
;80.82.69.57.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jun 29 00:57:59 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 57.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 57.69.82.80.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
106.13.45.131 attackspam
Dec 22 12:47:14 auw2 sshd\[13374\]: Invalid user lymer from 106.13.45.131
Dec 22 12:47:14 auw2 sshd\[13374\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.45.131
Dec 22 12:47:16 auw2 sshd\[13374\]: Failed password for invalid user lymer from 106.13.45.131 port 44268 ssh2
Dec 22 12:52:44 auw2 sshd\[13900\]: Invalid user abcd@321 from 106.13.45.131
Dec 22 12:52:44 auw2 sshd\[13900\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.45.131
2019-12-23 07:16:15
1.236.151.31 attackbotsspam
Dec 22 23:52:55 srv206 sshd[26500]: Invalid user mayman from 1.236.151.31
...
2019-12-23 07:06:12
164.132.53.185 attack
Dec 22 23:48:29 ns3042688 sshd\[14765\]: Invalid user ttl from 164.132.53.185
Dec 22 23:48:31 ns3042688 sshd\[14765\]: Failed password for invalid user ttl from 164.132.53.185 port 48246 ssh2
Dec 22 23:53:03 ns3042688 sshd\[16830\]: Invalid user teamspeak from 164.132.53.185
Dec 22 23:53:05 ns3042688 sshd\[16830\]: Failed password for invalid user teamspeak from 164.132.53.185 port 52350 ssh2
Dec 22 23:57:37 ns3042688 sshd\[18926\]: Invalid user transfer from 164.132.53.185
...
2019-12-23 07:15:50
220.158.148.132 attackspambots
$f2bV_matches
2019-12-23 06:53:30
163.172.223.186 attackspam
Dec 22 23:06:40 web8 sshd\[26651\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=163.172.223.186  user=root
Dec 22 23:06:42 web8 sshd\[26651\]: Failed password for root from 163.172.223.186 port 58404 ssh2
Dec 22 23:12:26 web8 sshd\[29724\]: Invalid user ching from 163.172.223.186
Dec 22 23:12:26 web8 sshd\[29724\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=163.172.223.186
Dec 22 23:12:28 web8 sshd\[29724\]: Failed password for invalid user ching from 163.172.223.186 port 35938 ssh2
2019-12-23 07:21:04
221.208.6.164 attackbots
12/22/2019-15:44:20.337373 221.208.6.164 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-12-23 06:49:58
210.182.116.41 attackbotsspam
Dec 22 12:47:06 eddieflores sshd\[21804\]: Invalid user test from 210.182.116.41
Dec 22 12:47:06 eddieflores sshd\[21804\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.182.116.41
Dec 22 12:47:08 eddieflores sshd\[21804\]: Failed password for invalid user test from 210.182.116.41 port 34716 ssh2
Dec 22 12:53:02 eddieflores sshd\[22351\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.182.116.41  user=backup
Dec 22 12:53:03 eddieflores sshd\[22351\]: Failed password for backup from 210.182.116.41 port 40016 ssh2
2019-12-23 07:01:43
94.23.27.21 attack
Dec 23 04:23:02 areeb-Workstation sshd[7295]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.23.27.21 
Dec 23 04:23:03 areeb-Workstation sshd[7295]: Failed password for invalid user vymazal from 94.23.27.21 port 40010 ssh2
...
2019-12-23 07:02:00
51.75.32.141 attackbots
Dec 22 23:52:50 vps647732 sshd[28460]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.32.141
Dec 22 23:52:51 vps647732 sshd[28460]: Failed password for invalid user rob from 51.75.32.141 port 51128 ssh2
...
2019-12-23 07:10:24
23.100.93.132 attack
Dec 22 15:36:12 ws12vmsma01 sshd[18455]: Invalid user monika from 23.100.93.132
Dec 22 15:36:14 ws12vmsma01 sshd[18455]: Failed password for invalid user monika from 23.100.93.132 port 56016 ssh2
Dec 22 15:44:43 ws12vmsma01 sshd[19662]: Invalid user weiss from 23.100.93.132
...
2019-12-23 06:47:21
103.3.226.228 attackbotsspam
Dec 22 15:49:59 linuxvps sshd\[61114\]: Invalid user test from 103.3.226.228
Dec 22 15:49:59 linuxvps sshd\[61114\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.3.226.228
Dec 22 15:50:02 linuxvps sshd\[61114\]: Failed password for invalid user test from 103.3.226.228 port 47958 ssh2
Dec 22 15:57:55 linuxvps sshd\[1263\]: Invalid user chwee from 103.3.226.228
Dec 22 15:57:55 linuxvps sshd\[1263\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.3.226.228
2019-12-23 06:55:06
106.13.128.71 attackbots
Dec 22 07:18:14 hpm sshd\[29572\]: Invalid user raidt from 106.13.128.71
Dec 22 07:18:14 hpm sshd\[29572\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.128.71
Dec 22 07:18:17 hpm sshd\[29572\]: Failed password for invalid user raidt from 106.13.128.71 port 58642 ssh2
Dec 22 07:25:27 hpm sshd\[30266\]: Invalid user azmina from 106.13.128.71
Dec 22 07:25:27 hpm sshd\[30266\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.128.71
2019-12-23 06:48:45
77.247.109.82 attackspam
Dec 22 23:58:44 debian-2gb-nbg1-2 kernel: \[708273.053326\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=77.247.109.82 DST=195.201.40.59 LEN=438 TOS=0x00 PREC=0x00 TTL=54 ID=0 DF PROTO=UDP SPT=5105 DPT=5060 LEN=418
2019-12-23 07:25:34
62.234.106.199 attackbots
Dec 22 23:52:39 [host] sshd[17595]: Invalid user seascape from 62.234.106.199
Dec 22 23:52:39 [host] sshd[17595]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.106.199
Dec 22 23:52:41 [host] sshd[17595]: Failed password for invalid user seascape from 62.234.106.199 port 55139 ssh2
2019-12-23 07:20:00
104.200.110.191 attackspam
Dec 22 11:27:00 server sshd\[29699\]: Failed password for invalid user baier from 104.200.110.191 port 56826 ssh2
Dec 23 01:41:27 server sshd\[31828\]: Invalid user mahanom from 104.200.110.191
Dec 23 01:41:27 server sshd\[31828\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.200.110.191 
Dec 23 01:41:28 server sshd\[31828\]: Failed password for invalid user mahanom from 104.200.110.191 port 38186 ssh2
Dec 23 01:53:07 server sshd\[2386\]: Invalid user Vellamo from 104.200.110.191
Dec 23 01:53:07 server sshd\[2386\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.200.110.191 
...
2019-12-23 06:59:11

Recently Reported IPs

94.102.48.47 106.11.153.169 125.26.124.189 125.24.47.81
43.153.59.96 113.14.131.204 14.255.17.216 36.33.154.171
36.2.178.213 27.79.180.184 31.42.214.66 169.229.153.44
41.216.202.154 27.73.101.129 151.231.185.84 180.76.14.13
27.156.199.130 140.255.151.245 179.175.191.156 121.56.217.20