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

Region: Bavaria

Country: Germany

Internet Service Provider: Telekom

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
93.104.211.168 attack
Jun 18 06:31:24 vps10825 sshd[30869]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.104.211.168
Jun 18 06:31:26 vps10825 sshd[30869]: Failed password for invalid user steam from 93.104.211.168 port 54274 ssh2
...
2020-06-18 12:49:55
93.104.211.117 attackbots
Apr 30 12:15:12 host sshd[21441]: User r.r from 93.104.211.117 not allowed because none of user's groups are listed in AllowGroups
Apr 30 12:15:12 host sshd[21441]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.104.211.117  user=r.r
Apr 30 12:15:14 host sshd[21441]: Failed password for invalid user r.r from 93.104.211.117 port 37922 ssh2
Apr 30 12:15:14 host sshd[21441]: Received disconnect from 93.104.211.117 port 37922:11: Bye Bye [preauth]
Apr 30 12:15:14 host sshd[21441]: Disconnected from invalid user r.r 93.104.211.117 port 37922 [preauth]
Apr 30 12:27:22 host sshd[24228]: User backup from 93.104.211.117 not allowed because none of user's groups are listed in AllowGroups
Apr 30 12:27:22 host sshd[24228]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.104.211.117  user=backup
Apr 30 12:27:24 host sshd[24228]: Failed password for invalid user backup from 93.104.211.117 port 4815........
-------------------------------
2020-05-01 03:58:03
93.104.211.50 attackbotsspam
...
2019-11-18 03:24:07
93.104.211.50 attackbots
Masscan Port Scanning Tool Detection
2019-11-11 02:01:38
93.104.211.70 attackspam
Nov  1 04:53:22 vmd38886 sshd\[5748\]: Failed password for root from 93.104.211.70 port 49468 ssh2
Nov  1 04:53:24 vmd38886 sshd\[5762\]: Failed password for root from 93.104.211.70 port 49508 ssh2
Nov  1 04:53:24 vmd38886 sshd\[5724\]: Failed password for root from 93.104.211.70 port 49426 ssh2
2019-11-01 15:11:01
93.104.211.50 attackbots
" "
2019-10-16 10:14:17
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 93.104.211.69
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 22095
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;93.104.211.69.			IN	A

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

;; Query time: 21 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jun 12 06:07:29 CST 2022
;; MSG SIZE  rcvd: 106
Host info
69.211.104.93.in-addr.arpa domain name pointer schoppi.eu.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
69.211.104.93.in-addr.arpa	name = schoppi.eu.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
181.53.251.181 attack
Mar  2 11:52:51 hcbbdb sshd\[18017\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.53.251.181  user=root
Mar  2 11:52:53 hcbbdb sshd\[18017\]: Failed password for root from 181.53.251.181 port 48366 ssh2
Mar  2 12:01:21 hcbbdb sshd\[18889\]: Invalid user user from 181.53.251.181
Mar  2 12:01:21 hcbbdb sshd\[18889\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.53.251.181
Mar  2 12:01:24 hcbbdb sshd\[18889\]: Failed password for invalid user user from 181.53.251.181 port 57844 ssh2
2020-03-02 20:25:18
222.82.54.8 attack
Unauthorized connection attempt detected from IP address 222.82.54.8 to port 3389 [J]
2020-03-02 20:45:46
190.236.197.218 attack
Unauthorized connection attempt detected from IP address 190.236.197.218 to port 8080 [J]
2020-03-02 20:53:56
220.200.161.65 attackbots
Unauthorized connection attempt detected from IP address 220.200.161.65 to port 999 [J]
2020-03-02 20:48:55
200.89.114.82 attackspambots
Unauthorized connection attempt detected from IP address 200.89.114.82 to port 8080 [J]
2020-03-02 20:20:58
223.166.75.237 attackbotsspam
Unauthorized connection attempt detected from IP address 223.166.75.237 to port 8899 [J]
2020-03-02 20:45:02
220.200.167.234 attackspam
Unauthorized connection attempt detected from IP address 220.200.167.234 to port 999 [J]
2020-03-02 20:47:52
218.253.254.100 attackbots
Unauthorized connection attempt detected from IP address 218.253.254.100 to port 1433 [J]
2020-03-02 20:50:16
221.205.137.60 attackbotsspam
Unauthorized connection attempt detected from IP address 221.205.137.60 to port 8118 [J]
2020-03-02 20:17:58
157.0.78.79 attack
Unauthorized connection attempt detected from IP address 157.0.78.79 to port 1433 [J]
2020-03-02 20:57:37
95.172.47.108 attack
Unauthorized connection attempt detected from IP address 95.172.47.108 to port 8080 [J]
2020-03-02 20:39:32
113.200.71.110 attackbots
Unauthorized connection attempt detected from IP address 113.200.71.110 to port 8899 [J]
2020-03-02 20:33:59
190.213.178.181 attack
Unauthorized connection attempt detected from IP address 190.213.178.181 to port 23 [J]
2020-03-02 20:22:55
182.113.227.46 attackspam
Unauthorized connection attempt detected from IP address 182.113.227.46 to port 23 [J]
2020-03-02 20:24:31
100.14.178.204 attackbots
Unauthorized connection attempt detected from IP address 100.14.178.204 to port 8080 [J]
2020-03-02 20:39:10

Recently Reported IPs

146.190.30.169 80.94.93.15 195.133.20.245 137.226.0.211
5.167.64.194 133.167.231.130 137.226.0.124 137.226.0.79
95.140.202.165 36.95.34.108 137.226.0.252 137.226.0.90
172.252.1.53 2a03:b0c0:3:e0::4d:c001 149.113.32.194 137.226.0.133
43.133.1.214 137.226.1.125 137.226.1.182 201.103.130.220