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: 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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 217.2.94.54
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 43477
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;217.2.94.54.			IN	A

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

;; Query time: 37 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 29 09:33:03 CST 2025
;; MSG SIZE  rcvd: 104
Host info
54.94.2.217.in-addr.arpa domain name pointer pd9025e36.dip0.t-ipconnect.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
54.94.2.217.in-addr.arpa	name = pd9025e36.dip0.t-ipconnect.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
77.76.52.142 attack
Jan 26 09:55:25 lanister sshd[3348]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.76.52.142
Jan 26 09:55:25 lanister sshd[3348]: Invalid user somsak from 77.76.52.142
Jan 26 09:55:27 lanister sshd[3348]: Failed password for invalid user somsak from 77.76.52.142 port 54330 ssh2
Jan 26 10:07:09 lanister sshd[3445]: Invalid user tfc from 77.76.52.142
...
2020-01-27 00:26:40
123.163.114.64 attackbots
Unauthorized connection attempt detected from IP address 123.163.114.64 to port 8081 [J]
2020-01-27 00:17:46
42.113.229.228 attackbots
Unauthorized connection attempt detected from IP address 42.113.229.228 to port 23 [J]
2020-01-27 00:53:17
212.64.50.202 attackspambots
Unauthorized connection attempt detected from IP address 212.64.50.202 to port 6379 [J]
2020-01-27 00:36:18
213.32.92.57 attackspambots
Unauthorized connection attempt detected from IP address 213.32.92.57 to port 2220 [J]
2020-01-27 00:35:56
114.67.90.149 attackbots
Unauthorized connection attempt detected from IP address 114.67.90.149 to port 2220 [J]
2020-01-27 00:48:00
42.2.71.199 attackbotsspam
Unauthorized connection attempt detected from IP address 42.2.71.199 to port 5555 [J]
2020-01-27 00:53:51
112.247.171.112 attackspambots
Unauthorized connection attempt detected from IP address 112.247.171.112 to port 23 [J]
2020-01-27 00:49:28
150.109.167.20 attackbots
Unauthorized connection attempt detected from IP address 150.109.167.20 to port 8887 [J]
2020-01-27 00:43:21
190.24.119.9 attackbotsspam
Unauthorized connection attempt detected from IP address 190.24.119.9 to port 23 [J]
2020-01-27 00:37:48
23.129.64.209 attack
Unauthorized connection attempt detected from IP address 23.129.64.209 to port 2022 [J]
2020-01-27 00:31:20
114.37.79.33 attack
Unauthorized connection attempt detected from IP address 114.37.79.33 to port 23 [J]
2020-01-27 00:48:35
5.105.1.49 attack
Unauthorized connection attempt detected from IP address 5.105.1.49 to port 222 [J]
2020-01-27 00:31:59
123.145.37.225 attackbots
Unauthorized connection attempt detected from IP address 123.145.37.225 to port 8081 [J]
2020-01-27 00:18:03
121.57.228.214 attackspam
Unauthorized connection attempt detected from IP address 121.57.228.214 to port 8081 [J]
2020-01-27 00:45:24

Recently Reported IPs

48.85.229.212 36.253.56.80 21.26.164.8 151.199.43.137
148.223.99.252 179.183.132.98 89.176.245.38 222.215.16.101
233.151.132.35 70.108.176.194 240.31.128.230 235.136.132.67
87.199.184.223 254.79.94.3 29.123.219.124 93.162.56.53
98.197.219.11 86.162.38.115 242.215.18.176 72.61.238.69