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

;; QUESTION SECTION:
;89.56.243.54.			IN	A

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

;; Query time: 37 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 06:51:33 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 54.243.56.89.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 54.243.56.89.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
99.191.118.206 attack
Invalid user pi from 99.191.118.206 port 33498
2019-12-19 08:30:51
149.129.173.223 attack
Dec 19 00:56:26 lnxmail61 sshd[20597]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.129.173.223
2019-12-19 08:05:37
176.255.0.63 attackbotsspam
Automatic report - Port Scan Attack
2019-12-19 08:08:44
58.87.120.53 attack
Dec 18 23:19:07 ns382633 sshd\[30384\]: Invalid user furukawa from 58.87.120.53 port 59864
Dec 18 23:19:07 ns382633 sshd\[30384\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.87.120.53
Dec 18 23:19:09 ns382633 sshd\[30384\]: Failed password for invalid user furukawa from 58.87.120.53 port 59864 ssh2
Dec 18 23:39:06 ns382633 sshd\[1306\]: Invalid user 1234 from 58.87.120.53 port 39474
Dec 18 23:39:06 ns382633 sshd\[1306\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.87.120.53
2019-12-19 08:09:14
94.191.47.240 attack
Dec 18 23:38:51 dedicated sshd[3194]: Invalid user bluedoor from 94.191.47.240 port 51996
2019-12-19 08:29:21
106.54.185.253 attackspam
Port scan detected on ports: 1433[TCP], 1433[TCP], 65529[TCP]
2019-12-19 08:17:22
139.59.38.94 attack
Invalid user twister from 139.59.38.94 port 51812
2019-12-19 08:23:12
210.51.167.245 attack
Brute force SMTP login attempted.
...
2019-12-19 08:06:08
103.45.101.220 attackbots
Dec 19 00:53:08 vps58358 sshd\[19319\]: Invalid user ching from 103.45.101.220Dec 19 00:53:10 vps58358 sshd\[19319\]: Failed password for invalid user ching from 103.45.101.220 port 36858 ssh2Dec 19 00:57:26 vps58358 sshd\[19368\]: Invalid user wave from 103.45.101.220Dec 19 00:57:29 vps58358 sshd\[19368\]: Failed password for invalid user wave from 103.45.101.220 port 44890 ssh2Dec 19 01:01:48 vps58358 sshd\[19419\]: Invalid user sicco from 103.45.101.220Dec 19 01:01:50 vps58358 sshd\[19419\]: Failed password for invalid user sicco from 103.45.101.220 port 53046 ssh2
...
2019-12-19 08:30:21
3.228.20.34 attackspam
3.228.20.34 was recorded 5 times by 5 hosts attempting to connect to the following ports: 5683. Incident counter (4h, 24h, all-time): 5, 5, 5
2019-12-19 08:06:28
1.255.153.167 attackbots
2019-12-18T23:41:26.542851shield sshd\[18867\]: Invalid user vagrant from 1.255.153.167 port 47154
2019-12-18T23:41:26.547027shield sshd\[18867\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.255.153.167
2019-12-18T23:41:28.792480shield sshd\[18867\]: Failed password for invalid user vagrant from 1.255.153.167 port 47154 ssh2
2019-12-18T23:47:16.297581shield sshd\[20884\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.255.153.167  user=daemon
2019-12-18T23:47:18.593774shield sshd\[20884\]: Failed password for daemon from 1.255.153.167 port 52922 ssh2
2019-12-19 08:21:32
206.189.129.38 attackbotsspam
Dec 18 19:18:12 plusreed sshd[4701]: Invalid user keystone from 206.189.129.38
...
2019-12-19 08:24:14
222.186.173.226 attackspam
Dec 19 01:41:28 sso sshd[3002]: Failed password for root from 222.186.173.226 port 13274 ssh2
Dec 19 01:41:32 sso sshd[3002]: Failed password for root from 222.186.173.226 port 13274 ssh2
...
2019-12-19 08:41:49
27.78.14.83 attackspambots
Dec 15 23:39:02 foo sshd[9259]: Address 27.78.14.83 maps to localhost, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Dec 15 23:39:02 foo sshd[9259]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.78.14.83  user=r.r
Dec 15 23:39:04 foo sshd[9259]: Failed password for r.r from 27.78.14.83 port 21178 ssh2
Dec 15 23:39:05 foo sshd[9259]: Connection closed by 27.78.14.83 [preauth]
Dec 15 23:39:13 foo sshd[9284]: Address 27.78.14.83 maps to localhost, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Dec 15 23:39:13 foo sshd[9284]: Invalid user test from 27.78.14.83
Dec 15 23:39:13 foo sshd[9282]: Address 27.78.14.83 maps to localhost, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Dec 15 23:39:13 foo sshd[9282]: Invalid user system from 27.78.14.83
Dec 15 23:39:13 foo sshd[9286]: Address 27.78.14.83 maps to localhost, but this does not map back to the address - P........
-------------------------------
2019-12-19 08:14:59
178.175.132.72 attack
fell into ViewStateTrap:nairobi
2019-12-19 08:22:15

Recently Reported IPs

157.250.146.100 187.172.117.3 193.174.122.37 41.40.165.169
23.45.95.81 240.4.49.176 107.175.121.182 16.205.78.51
64.15.226.41 231.25.238.61 199.145.15.85 162.177.164.158
28.116.153.184 223.46.228.87 95.178.107.180 205.8.149.147
161.133.195.160 22.133.120.226 232.127.45.122 224.169.186.198