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: Amazon.com, Inc.

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

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

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

;; Query time: 2 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Fri Jul 12 03:21:04 CST 2019
;; MSG SIZE  rcvd: 118
Host info
150.239.248.54.in-addr.arpa domain name pointer ec2-54-248-239-150.ap-northeast-1.compute.amazonaws.com.
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

Non-authoritative answer:
150.239.248.54.in-addr.arpa	name = ec2-54-248-239-150.ap-northeast-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
220.73.134.138 attackspambots
Mar 10 18:50:08 targaryen sshd[12710]: Invalid user eupa from 220.73.134.138
Mar 10 18:54:38 targaryen sshd[12746]: Invalid user ftpuser from 220.73.134.138
Mar 10 18:59:02 targaryen sshd[12801]: Invalid user eupa from 220.73.134.138
Mar 10 19:03:38 targaryen sshd[12836]: Invalid user oracle from 220.73.134.138
...
2020-03-11 07:45:00
62.234.83.138 attackspambots
Invalid user ubuntu from 62.234.83.138 port 56662
2020-03-11 08:03:51
176.37.177.78 attackbots
Mar 10 08:39:45 tdfoods sshd\[23941\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=host-176-37-177-78.la.net.ua  user=root
Mar 10 08:39:48 tdfoods sshd\[23941\]: Failed password for root from 176.37.177.78 port 49562 ssh2
Mar 10 08:48:19 tdfoods sshd\[24637\]: Invalid user dave from 176.37.177.78
Mar 10 08:48:19 tdfoods sshd\[24637\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=host-176-37-177-78.la.net.ua
Mar 10 08:48:21 tdfoods sshd\[24637\]: Failed password for invalid user dave from 176.37.177.78 port 52562 ssh2
2020-03-11 07:45:32
36.110.114.32 attackspam
fail2ban -- 36.110.114.32
...
2020-03-11 08:14:48
212.47.240.88 attackspam
SSH auth scanning - multiple failed logins
2020-03-11 08:09:05
182.184.44.6 attack
Mar 10 22:40:40 ws26vmsma01 sshd[152698]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.184.44.6
Mar 10 22:40:41 ws26vmsma01 sshd[152698]: Failed password for invalid user jyc from 182.184.44.6 port 58434 ssh2
...
2020-03-11 08:21:01
119.28.176.26 attack
Mar 10 17:46:36 ws19vmsma01 sshd[74195]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.28.176.26
Mar 10 17:46:38 ws19vmsma01 sshd[74195]: Failed password for invalid user sdtdserver from 119.28.176.26 port 34696 ssh2
...
2020-03-11 07:57:44
180.168.47.66 attackspambots
SSH-BruteForce
2020-03-11 07:54:16
46.24.14.61 attack
20/3/10@14:11:34: FAIL: Alarm-Network address from=46.24.14.61
20/3/10@14:11:34: FAIL: Alarm-Network address from=46.24.14.61
...
2020-03-11 07:48:31
27.72.173.184 attackbots
IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking.
2020-03-11 08:14:18
89.189.197.22 attack
SSH Server BruteForce Attack
2020-03-11 08:18:24
79.0.181.149 attackbotsspam
Total attacks: 2
2020-03-11 07:59:43
218.92.0.189 attack
Mar 11 00:17:43 legacy sshd[22713]: Failed password for root from 218.92.0.189 port 52041 ssh2
Mar 11 00:18:42 legacy sshd[22725]: Failed password for root from 218.92.0.189 port 59846 ssh2
Mar 11 00:18:44 legacy sshd[22725]: Failed password for root from 218.92.0.189 port 59846 ssh2
...
2020-03-11 07:41:16
222.84.254.102 attack
suspicious action Tue, 10 Mar 2020 15:10:56 -0300
2020-03-11 08:10:03
104.206.128.78 attack
Unauthorized connection attempt detected from IP address 104.206.128.78 to port 3389
2020-03-11 08:01:50

Recently Reported IPs

44.151.131.8 2a02:8108:97c0:15c3:f413:e83e:97c1:4a59 181.155.1.121 73.1.241.174
96.162.163.160 115.73.167.72 144.2.136.244 252.226.187.240
201.207.71.86 61.78.221.236 94.0.152.76 77.125.88.169
141.100.175.84 176.150.55.76 85.113.21.8 190.196.226.170
172.95.49.162 168.205.236.10 180.216.12.191 194.0.230.121