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

Region: Tokyo

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;54.64.56.104.			IN	A

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

;; Query time: 117 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Oct 15 03:21:39 CST 2019
;; MSG SIZE  rcvd: 116
Host info
104.56.64.54.in-addr.arpa domain name pointer ec2-54-64-56-104.ap-northeast-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
104.56.64.54.in-addr.arpa	name = ec2-54-64-56-104.ap-northeast-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
174.76.35.28 attack
(imapd) Failed IMAP login from 174.76.35.28 (US/United States/-): 1 in the last 3600 secs
2020-01-05 02:56:30
42.113.229.254 attackbots
Unauthorized connection attempt detected from IP address 42.113.229.254 to port 23 [J]
2020-01-05 02:29:04
49.235.216.174 attack
Jan  4 19:35:07 ns381471 sshd[26237]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.216.174
Jan  4 19:35:09 ns381471 sshd[26237]: Failed password for invalid user qjc from 49.235.216.174 port 42762 ssh2
2020-01-05 02:48:33
106.13.191.19 attackbotsspam
Unauthorized connection attempt detected from IP address 106.13.191.19 to port 2220 [J]
2020-01-05 02:21:26
177.55.188.207 attackbots
Unauthorized connection attempt detected from IP address 177.55.188.207 to port 23 [J]
2020-01-05 02:56:16
91.65.130.172 attackbotsspam
Unauthorized connection attempt detected from IP address 91.65.130.172 to port 80 [J]
2020-01-05 02:45:07
122.116.140.56 attackbots
Unauthorized connection attempt detected from IP address 122.116.140.56 to port 4567 [J]
2020-01-05 02:18:14
45.248.71.28 attackspam
Unauthorized connection attempt detected from IP address 45.248.71.28 to port 2220 [J]
2020-01-05 02:49:01
49.119.55.245 attackbots
Unauthorized connection attempt detected from IP address 49.119.55.245 to port 23 [J]
2020-01-05 02:27:49
124.124.44.157 attack
Unauthorized connection attempt detected from IP address 124.124.44.157 to port 23 [J]
2020-01-05 02:40:42
200.41.116.42 attackbots
Unauthorized connection attempt detected from IP address 200.41.116.42 to port 80 [J]
2020-01-05 02:53:40
111.231.108.97 attackbots
Unauthorized connection attempt detected from IP address 111.231.108.97 to port 2220 [J]
2020-01-05 02:20:27
95.5.8.59 attackspambots
Unauthorized connection attempt detected from IP address 95.5.8.59 to port 23 [J]
2020-01-05 02:23:16
117.223.130.253 attackspam
Unauthorized connection attempt detected from IP address 117.223.130.253 to port 23 [J]
2020-01-05 02:19:29
196.218.101.171 attack
Unauthorized connection attempt detected from IP address 196.218.101.171 to port 23 [J]
2020-01-05 02:35:30

Recently Reported IPs

87.111.38.182 145.18.146.139 185.90.116.82 213.25.151.76
103.97.136.57 79.103.163.183 93.119.52.36 183.2.88.15
146.94.17.146 120.89.64.8 32.99.23.73 86.197.74.98
122.7.84.36 81.193.92.85 103.6.76.106 197.148.103.130
66.168.154.25 92.239.177.198 39.88.137.240 179.113.53.247