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

;; QUESTION SECTION:
;54.95.47.244.			IN	A

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

;; Query time: 34 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 06:06:55 CST 2025
;; MSG SIZE  rcvd: 105
Host info
244.47.95.54.in-addr.arpa domain name pointer ec2-54-95-47-244.ap-northeast-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
244.47.95.54.in-addr.arpa	name = ec2-54-95-47-244.ap-northeast-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
94.23.208.211 attackspambots
Sep  1 12:28:58 web8 sshd\[9003\]: Invalid user florin from 94.23.208.211
Sep  1 12:28:58 web8 sshd\[9003\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.23.208.211
Sep  1 12:29:01 web8 sshd\[9003\]: Failed password for invalid user florin from 94.23.208.211 port 50726 ssh2
Sep  1 12:32:30 web8 sshd\[10742\]: Invalid user 123456 from 94.23.208.211
Sep  1 12:32:30 web8 sshd\[10742\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.23.208.211
2019-09-01 23:20:35
178.21.164.100 attackspambots
k+ssh-bruteforce
2019-09-01 22:53:52
45.55.177.230 attackspam
Automatic report - Banned IP Access
2019-09-01 22:37:49
43.226.69.182 attack
$f2bV_matches_ltvn
2019-09-01 23:02:47
40.73.25.111 attackspam
Aug 28 10:43:33 itv-usvr-01 sshd[10279]: Invalid user user from 40.73.25.111
Aug 28 10:43:33 itv-usvr-01 sshd[10279]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=40.73.25.111
Aug 28 10:43:33 itv-usvr-01 sshd[10279]: Invalid user user from 40.73.25.111
Aug 28 10:43:35 itv-usvr-01 sshd[10279]: Failed password for invalid user user from 40.73.25.111 port 30086 ssh2
Aug 28 10:48:13 itv-usvr-01 sshd[10459]: Invalid user flopy from 40.73.25.111
2019-09-01 22:29:13
178.128.242.233 attack
Sep  1 10:55:51 mail sshd\[34066\]: Invalid user xy from 178.128.242.233
Sep  1 10:55:51 mail sshd\[34066\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.242.233
...
2019-09-01 23:07:52
142.93.15.1 attackbotsspam
Sep  1 11:53:08 eventyay sshd[9818]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.15.1
Sep  1 11:53:10 eventyay sshd[9818]: Failed password for invalid user tar from 142.93.15.1 port 40578 ssh2
Sep  1 11:57:15 eventyay sshd[10891]: Failed password for root from 142.93.15.1 port 57982 ssh2
...
2019-09-01 22:50:03
107.174.33.130 attack
(From DonaldThompson704@gmail.com) Hi!

Some issues on your website prevent potential clients from finding it while they're searching for products/services online. I'm an online marketing specialist who has made sites that have crawled their way up the rankings in the search results dominate the first page of Goggle and other major search engines. 

Would you like to generate more sales using your site? Having your website show up the top search results means that your business is more relevant and more trusted compared to others. This is the most effective way to attract clients. I can show you case studies about companies I've worked with in the past and how their business gained a boost when after the SEO work I did for them.

Let me know what you think. If you're interested, I'll give you a call at a time that works best for you so I can share some expert advice. All the helpful information I'll provide can benefit your business whether or not you choose to avail of my services. I look forward to sp
2019-09-01 22:35:42
43.226.69.133 attackbots
Sep  1 09:16:17 hb sshd\[29958\]: Invalid user java from 43.226.69.133
Sep  1 09:16:17 hb sshd\[29958\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.226.69.133
Sep  1 09:16:18 hb sshd\[29958\]: Failed password for invalid user java from 43.226.69.133 port 47170 ssh2
Sep  1 09:19:57 hb sshd\[30330\]: Invalid user test from 43.226.69.133
Sep  1 09:19:57 hb sshd\[30330\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.226.69.133
2019-09-01 23:17:57
179.184.217.83 attackspam
Sep  1 00:55:38 kapalua sshd\[25500\]: Invalid user ges from 179.184.217.83
Sep  1 00:55:38 kapalua sshd\[25500\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.184.217.83
Sep  1 00:55:40 kapalua sshd\[25500\]: Failed password for invalid user ges from 179.184.217.83 port 33670 ssh2
Sep  1 01:00:28 kapalua sshd\[26027\]: Invalid user meng from 179.184.217.83
Sep  1 01:00:28 kapalua sshd\[26027\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.184.217.83
2019-09-01 23:06:54
176.31.100.19 attack
Sep  1 16:57:23 vps647732 sshd[13906]: Failed password for root from 176.31.100.19 port 50528 ssh2
...
2019-09-01 23:15:04
223.241.16.224 attack
Sep  1 10:09:13 pl3server sshd[1401222]: Invalid user service from 223.241.16.224
Sep  1 10:09:13 pl3server sshd[1401222]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.241.16.224
Sep  1 10:09:15 pl3server sshd[1401222]: Failed password for invalid user service from 223.241.16.224 port 48915 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=223.241.16.224
2019-09-01 22:58:36
136.228.161.66 attack
2019-09-01T14:51:36.762616abusebot-6.cloudsearch.cf sshd\[26131\]: Invalid user kill from 136.228.161.66 port 37850
2019-09-01 23:07:23
41.78.201.48 attackbotsspam
Sep  1 11:10:02 xtremcommunity sshd\[1358\]: Invalid user tomcats from 41.78.201.48 port 36960
Sep  1 11:10:02 xtremcommunity sshd\[1358\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.78.201.48
Sep  1 11:10:04 xtremcommunity sshd\[1358\]: Failed password for invalid user tomcats from 41.78.201.48 port 36960 ssh2
Sep  1 11:15:30 xtremcommunity sshd\[1512\]: Invalid user ethernet from 41.78.201.48 port 59737
Sep  1 11:15:30 xtremcommunity sshd\[1512\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.78.201.48
...
2019-09-01 23:21:33
128.199.133.249 attack
Sep  1 10:34:16 debian sshd[14564]: Unable to negotiate with 128.199.133.249 port 47739: no matching key exchange method found. Their offer: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 [preauth]
Sep  1 10:41:14 debian sshd[14925]: Unable to negotiate with 128.199.133.249 port 41517: no matching key exchange method found. Their offer: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 [preauth]
...
2019-09-01 23:12:42

Recently Reported IPs

242.209.229.64 76.156.65.188 121.31.22.91 16.244.127.251
182.121.87.135 71.164.19.194 235.84.153.66 46.43.146.226
78.192.74.102 168.238.206.167 54.146.234.84 165.148.192.22
142.75.199.192 252.162.122.241 32.222.109.237 163.148.116.121
34.21.53.41 138.25.185.86 77.197.77.72 100.38.232.136