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

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

;; QUESTION SECTION:
;159.211.54.254.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 21 13:33:08 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 254.54.211.159.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 254.54.211.159.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
35.161.225.17 attackbots
suspicious action Mon, 24 Feb 2020 01:44:46 -0300
2020-02-24 20:06:02
190.104.243.12 attack
web-1 [ssh_2] SSH Attack
2020-02-24 20:15:49
47.111.232.88 attackspambots
Port scan on 5 port(s): 2375 2376 2377 4243 4244
2020-02-24 20:19:25
112.133.244.184 attack
unauthorized connection attempt
2020-02-24 20:00:12
92.222.92.64 attackbotsspam
ssh brute force
2020-02-24 20:29:06
27.72.56.236 attackbots
Port probing on unauthorized port 445
2020-02-24 20:01:54
176.31.116.214 attack
Feb 24 12:33:06 lnxweb62 sshd[24355]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.31.116.214
Feb 24 12:33:06 lnxweb62 sshd[24355]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.31.116.214
Feb 24 12:33:07 lnxweb62 sshd[24355]: Failed password for invalid user tifkai from 176.31.116.214 port 44561 ssh2
2020-02-24 19:56:13
125.165.62.239 attackspam
Unauthorized connection attempt from IP address 125.165.62.239 on Port 445(SMB)
2020-02-24 19:52:41
92.63.194.57 attack
TCP port 3389: Scan and connection
2020-02-24 20:18:28
192.241.237.157 attack
suspicious action Mon, 24 Feb 2020 01:44:36 -0300
2020-02-24 20:09:57
164.132.83.81 attackspambots
02/24/2020-08:50:20.804282 164.132.83.81 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2020-02-24 20:18:53
49.149.69.166 attackspambots
WordPress wp-login brute force :: 49.149.69.166 0.088 BYPASS [24/Feb/2020:04:44:54  0000] [censored_2] "POST /wp-login.php HTTP/1.1" 200 2254 "https://[censored_2]/wp-login.php" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36"
2020-02-24 20:02:48
192.241.239.195 attackspam
" "
2020-02-24 20:07:15
80.82.77.189 attackspam
Feb 24 13:13:06 debian-2gb-nbg1-2 kernel: \[4805587.467490\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=80.82.77.189 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=61276 PROTO=TCP SPT=58355 DPT=58787 WINDOW=1024 RES=0x00 SYN URGP=0
2020-02-24 20:14:25
88.204.179.142 attackspambots
Unauthorized connection attempt from IP address 88.204.179.142 on Port 445(SMB)
2020-02-24 19:50:51

Recently Reported IPs

198.7.65.130 135.30.57.236 243.110.13.166 123.142.165.25
131.15.151.246 151.3.148.161 97.149.24.182 143.53.16.89
97.169.89.23 221.89.86.170 119.133.195.5 233.29.170.250
25.122.112.47 152.219.59.187 120.38.35.61 81.253.26.210
184.82.109.44 38.243.101.240 175.200.122.0 70.48.87.154