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: Germany

Internet Service Provider: 1&1 Versatel Deutschland GmbH

Hostname: unknown

Organization: unknown

Usage Type: Fixed Line ISP

Comments:
Type Details Datetime
attack
Aug 27 01:41:25 vps691689 sshd[16669]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.207.219.66
Aug 27 01:41:26 vps691689 sshd[16669]: Failed password for invalid user admin from 82.207.219.66 port 56936 ssh2
Aug 27 01:41:33 vps691689 sshd[16669]: Failed password for invalid user admin from 82.207.219.66 port 56936 ssh2
...
2019-08-27 09:13:55
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 82.207.219.66
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 32224
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;82.207.219.66.			IN	A

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

;; Query time: 2 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Tue Aug 27 09:13:50 CST 2019
;; MSG SIZE  rcvd: 117
Host info
66.219.207.82.in-addr.arpa domain name pointer muedsl-82-207-219-066.citykom.de.
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

Non-authoritative answer:
66.219.207.82.in-addr.arpa	name = muedsl-82-207-219-066.citykom.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
90.3.32.60 attackspambots
Unauthorized connection attempt detected from IP address 90.3.32.60 to port 23 [J]
2020-01-31 01:52:42
41.35.166.219 attack
Unauthorized connection attempt detected from IP address 41.35.166.219 to port 23 [J]
2020-01-31 01:36:30
182.176.117.197 attackspam
Unauthorized connection attempt detected from IP address 182.176.117.197 to port 3389 [J]
2020-01-31 01:45:33
190.234.63.216 attack
Unauthorized connection attempt detected from IP address 190.234.63.216 to port 80 [J]
2020-01-31 01:41:09
95.215.163.108 attack
Unauthorized connection attempt detected from IP address 95.215.163.108 to port 8080 [J]
2020-01-31 01:31:02
119.192.55.100 attack
Unauthorized connection attempt detected from IP address 119.192.55.100 to port 2220 [J]
2020-01-31 01:48:09
78.85.40.133 attackspambots
Unauthorized connection attempt detected from IP address 78.85.40.133 to port 80 [J]
2020-01-31 01:54:02
188.241.196.70 attackbotsspam
Unauthorized connection attempt detected from IP address 188.241.196.70 to port 23 [J]
2020-01-31 01:41:55
93.144.142.173 attackspambots
Unauthorized connection attempt detected from IP address 93.144.142.173 to port 8080 [J]
2020-01-31 01:31:26
200.194.31.140 attack
Unauthorized connection attempt detected from IP address 200.194.31.140 to port 23 [J]
2020-01-31 01:18:46
117.50.50.44 attackspam
2020-1-30 5:55:39 PM: failed ssh attempt
2020-01-31 01:27:26
177.72.21.98 attackbots
Unauthorized connection attempt detected from IP address 177.72.21.98 to port 80 [J]
2020-01-31 01:46:30
200.236.121.40 attackspam
Unauthorized connection attempt detected from IP address 200.236.121.40 to port 23 [J]
2020-01-31 01:18:13
187.163.121.62 attackbots
Unauthorized connection attempt detected from IP address 187.163.121.62 to port 23 [J]
2020-01-31 01:20:38
68.183.193.4 attackbotsspam
Unauthorized connection attempt detected from IP address 68.183.193.4 to port 80 [J]
2020-01-31 01:35:36

Recently Reported IPs

103.137.70.234 45.132.227.178 192.9.206.213 182.37.0.81
120.2.114.64 171.25.175.215 187.45.57.134 137.74.158.143
52.163.82.162 183.151.107.159 195.231.70.115 191.254.134.245
47.53.189.216 179.217.118.237 89.35.73.255 60.184.182.67
177.196.54.94 140.127.218.200 110.138.151.182 51.75.13.156