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

;; QUESTION SECTION:
;80.82.69.192.			IN	A

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

;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jul 01 03:59:24 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 192.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 192.69.82.80.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
84.213.176.207 attackbotsspam
1564226732 - 07/27/2019 18:25:32 Host: cm-84.213.176.207.getinternet.no/84.213.176.207 Port: 23 TCP Blocked
...
2019-08-04 04:21:53
185.129.216.51 attack
Aug  4 00:10:36 our-server-hostname postfix/smtpd[31335]: connect from unknown[185.129.216.51]
Aug x@x
Aug x@x
Aug x@x
Aug x@x
Aug x@x
Aug x@x
Aug x@x
Aug x@x
Aug x@x
Aug x@x
Aug x@x
Aug x@x
Aug x@x
Aug x@x
Aug  4 00:10:52 our-server-hostname postfix/smtpd[31335]: lost connection after RCPT from unknown[185.129.216.51]
Aug  4 00:10:52 our-server-hostname postfix/smtpd[31335]: disconnect from unknown[185.129.216.51]
Aug  4 00:12:24 our-server-hostname postfix/smtpd[29490]: connect from unknown[185.129.216.51]
Aug x@x
Aug  4 00:12:27 our-server-hostname postfix/smtpd[29490]: lost connection after RCPT from unknown[185.129.216.51]
Aug  4 00:12:27 our-server-hostname postfix/smtpd[29490]: disconnect from unknown[185.129.216.51]
Aug  4 00:30:24 our-server-hostname postfix/smtpd[21164]: connect from unknown[185.129.216.51]
Aug x@x
Aug x@x
Aug x@x
Aug x@x
Aug x@x
Aug x@x
Aug x@x
Aug x@x
Aug x@x
Aug x@x
Aug x@x


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=185.129
2019-08-04 04:22:14
162.247.74.74 attack
Jul 30 10:16:18 *** sshd[15522]: Failed password for invalid user cirros from 162.247.74.74 port 60878 ssh2
Aug  1 05:45:06 *** sshd[32053]: Failed password for invalid user admin from 162.247.74.74 port 38400 ssh2
Aug  1 05:45:09 *** sshd[32053]: Failed password for invalid user admin from 162.247.74.74 port 38400 ssh2
Aug  1 05:45:15 *** sshd[32061]: Failed password for invalid user Administrator from 162.247.74.74 port 41938 ssh2
Aug  3 05:03:09 *** sshd[26183]: Failed password for invalid user Administrator from 162.247.74.74 port 40404 ssh2
Aug  3 05:06:16 *** sshd[26307]: Failed password for invalid user vagrant from 162.247.74.74 port 55988 ssh2
2019-08-04 04:50:32
70.75.69.162 attack
Aug  3 20:03:16 lnxded63 sshd[19155]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=70.75.69.162
2019-08-04 04:08:10
118.72.171.142 attackspam
DATE:2019-08-03 17:09:33, IP:118.72.171.142, PORT:ssh SSH brute force auth on honeypot server (honey-neo-dc)
2019-08-04 04:48:43
88.121.72.24 attackspambots
Aug  3 16:50:40 localhost sshd\[29424\]: Invalid user sydney from 88.121.72.24 port 46168
Aug  3 16:50:40 localhost sshd\[29424\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.121.72.24
...
2019-08-04 04:13:59
162.144.109.122 attack
Aug  3 22:34:41 srv-4 sshd\[29618\]: Invalid user lionel from 162.144.109.122
Aug  3 22:34:41 srv-4 sshd\[29618\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.144.109.122
Aug  3 22:34:43 srv-4 sshd\[29618\]: Failed password for invalid user lionel from 162.144.109.122 port 49664 ssh2
...
2019-08-04 04:24:48
192.42.116.16 attackspambots
Jul 31 04:43:32 *** sshd[3166]: Failed password for invalid user admin from 192.42.116.16 port 57676 ssh2
Aug  2 10:42:05 *** sshd[1689]: Failed password for invalid user vagrant from 192.42.116.16 port 37876 ssh2
Aug  3 08:27:01 *** sshd[30316]: Failed password for invalid user Administrator from 192.42.116.16 port 51218 ssh2
Aug  3 19:49:25 *** sshd[9042]: Failed password for invalid user admin from 192.42.116.16 port 51884 ssh2
Aug  3 19:50:02 *** sshd[9058]: Failed password for invalid user fwupgrade from 192.42.116.16 port 46986 ssh2
2019-08-04 04:19:30
71.237.171.150 attack
Aug  3 22:48:08 srv-4 sshd\[7575\]: Invalid user samba from 71.237.171.150
Aug  3 22:48:08 srv-4 sshd\[7575\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=71.237.171.150
Aug  3 22:48:11 srv-4 sshd\[7575\]: Failed password for invalid user samba from 71.237.171.150 port 49566 ssh2
...
2019-08-04 04:26:46
142.93.179.95 attack
2019-08-03 14:43:01,837 fail2ban.actions        [1802]: NOTICE  [sshd] Ban 142.93.179.95
2019-08-04 04:28:24
36.33.133.89 attack
Aug  3 16:34:43 ip-172-31-1-72 sshd\[1846\]: Invalid user admin from 36.33.133.89
Aug  3 16:34:43 ip-172-31-1-72 sshd\[1846\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.33.133.89
Aug  3 16:34:45 ip-172-31-1-72 sshd\[1846\]: Failed password for invalid user admin from 36.33.133.89 port 40867 ssh2
Aug  3 16:34:47 ip-172-31-1-72 sshd\[1846\]: Failed password for invalid user admin from 36.33.133.89 port 40867 ssh2
Aug  3 16:34:49 ip-172-31-1-72 sshd\[1846\]: Failed password for invalid user admin from 36.33.133.89 port 40867 ssh2
2019-08-04 04:20:15
105.73.80.253 attack
2019-08-02T10:07:40.209271WS-Zach sshd[24484]: Invalid user lzhang from 105.73.80.253 port 15158
2019-08-02T10:07:40.212775WS-Zach sshd[24484]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=105.73.80.253
2019-08-02T10:07:40.209271WS-Zach sshd[24484]: Invalid user lzhang from 105.73.80.253 port 15158
2019-08-02T10:07:42.000937WS-Zach sshd[24484]: Failed password for invalid user lzhang from 105.73.80.253 port 15158 ssh2
2019-08-03T13:22:16.501458WS-Zach sshd[2524]: Invalid user test from 105.73.80.253 port 15161
...
2019-08-04 04:35:11
118.244.196.89 attackbotsspam
SSH Brute-Forcing (ownc)
2019-08-04 04:17:52
92.222.71.125 attackspambots
2019-08-03T20:07:57.477722abusebot-7.cloudsearch.cf sshd\[17711\]: Invalid user akai from 92.222.71.125 port 43850
2019-08-04 04:49:10
46.196.250.74 attack
2019-08-03T17:02:04.322273abusebot-6.cloudsearch.cf sshd\[2252\]: Invalid user contabil from 46.196.250.74 port 60890
2019-08-04 04:33:25

Recently Reported IPs

180.76.164.254 137.226.218.173 21.11.136.9 137.226.146.56
180.76.127.57 80.82.69.91 190.115.143.6 80.82.76.224
66.42.79.211 93.126.144.81 45.184.92.224 36.90.106.153
116.58.239.169 180.76.122.55 80.82.76.210 94.102.63.10
180.76.138.251 80.82.66.9 80.82.66.116 94.102.57.238