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

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

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

;; Query time: 103 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Oct 23 02:13:46 CST 2019
;; MSG SIZE  rcvd: 118
Host info
149.235.248.54.in-addr.arpa domain name pointer ec2-54-248-235-149.ap-northeast-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
149.235.248.54.in-addr.arpa	name = ec2-54-248-235-149.ap-northeast-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
52.130.66.9 attackspambots
Dec  3 07:22:35 raspberrypi sshd\[30886\]: Did not receive identification string from 52.130.66.9
...
2019-12-03 21:55:40
164.132.80.137 attack
Dec  3 06:44:02 firewall sshd[12627]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.80.137
Dec  3 06:44:02 firewall sshd[12627]: Invalid user rimey from 164.132.80.137
Dec  3 06:44:04 firewall sshd[12627]: Failed password for invalid user rimey from 164.132.80.137 port 36346 ssh2
...
2019-12-03 21:57:54
61.247.235.94 attackspambots
Dec  3 07:11:32 new sshd[13936]: reveeclipse mapping checking getaddrinfo for abts-north-static-094.235.247.61.airtelbroadband.in [61.247.235.94] failed - POSSIBLE BREAK-IN ATTEMPT!
Dec  3 07:11:32 new sshd[13938]: reveeclipse mapping checking getaddrinfo for abts-north-static-094.235.247.61.airtelbroadband.in [61.247.235.94] failed - POSSIBLE BREAK-IN ATTEMPT!
Dec  3 07:11:32 new sshd[13937]: reveeclipse mapping checking getaddrinfo for abts-north-static-094.235.247.61.airtelbroadband.in [61.247.235.94] failed - POSSIBLE BREAK-IN ATTEMPT!
Dec  3 07:11:34 new sshd[13937]: Failed password for invalid user user1 from 61.247.235.94 port 53211 ssh2
Dec  3 07:11:34 new sshd[13936]: Failed password for invalid user user1 from 61.247.235.94 port 4134 ssh2
Dec  3 07:11:34 new sshd[13938]: Failed password for invalid user user1 from 61.247.235.94 port 7199 ssh2
Dec  3 07:11:34 new sshd[13937]: Connection closed by 61.247.235.94 [preauth]
Dec  3 07:11:34 new sshd[13936]: Connecti........
-------------------------------
2019-12-03 22:33:35
222.92.139.158 attack
Dec  3 02:01:01 TORMINT sshd\[26956\]: Invalid user dbus from 222.92.139.158
Dec  3 02:01:01 TORMINT sshd\[26956\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.92.139.158
Dec  3 02:01:04 TORMINT sshd\[26956\]: Failed password for invalid user dbus from 222.92.139.158 port 41932 ssh2
...
2019-12-03 21:57:42
23.129.64.203 attackspambots
12/03/2019-07:22:18.173176 23.129.64.203 Protocol: 6 ET TOR Known Tor Exit Node Traffic group 61
2019-12-03 22:15:37
175.39.8.105 attackbotsspam
Dec  3 07:12:46 h2022099 sshd[13947]: Invalid user pi from 175.39.8.105
Dec  3 07:12:46 h2022099 sshd[13946]: Invalid user pi from 175.39.8.105
Dec  3 07:12:46 h2022099 sshd[13947]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.39.8.105 
Dec  3 07:12:46 h2022099 sshd[13946]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.39.8.105 
Dec  3 07:12:48 h2022099 sshd[13947]: Failed password for invalid user pi from 175.39.8.105 port 43880 ssh2
Dec  3 07:12:48 h2022099 sshd[13946]: Failed password for invalid user pi from 175.39.8.105 port 43878 ssh2
Dec  3 07:12:48 h2022099 sshd[13947]: Connection closed by 175.39.8.105 [preauth]
Dec  3 07:12:48 h2022099 sshd[13946]: Connection closed by 175.39.8.105 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=175.39.8.105
2019-12-03 22:30:20
51.77.148.248 attackspam
<6 unauthorized SSH connections
2019-12-03 22:29:25
159.65.157.194 attackbotsspam
Dec  3 10:29:47 MK-Soft-VM7 sshd[30573]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.157.194 
Dec  3 10:29:48 MK-Soft-VM7 sshd[30573]: Failed password for invalid user matt from 159.65.157.194 port 51808 ssh2
...
2019-12-03 22:02:35
37.187.60.182 attackspam
Dec  3 14:49:09 localhost sshd\[18093\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.187.60.182  user=backup
Dec  3 14:49:11 localhost sshd\[18093\]: Failed password for backup from 37.187.60.182 port 40122 ssh2
Dec  3 14:58:43 localhost sshd\[18724\]: Invalid user system from 37.187.60.182
Dec  3 14:58:43 localhost sshd\[18724\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.187.60.182
Dec  3 14:58:45 localhost sshd\[18724\]: Failed password for invalid user system from 37.187.60.182 port 52002 ssh2
...
2019-12-03 22:29:03
45.174.234.15 attack
Honeypot attack, port: 23, PTR: PTR record not found
2019-12-03 22:05:03
58.219.156.83 attackspambots
DATE:2019-12-03 09:10:13, IP:58.219.156.83, PORT:1433 MSSQL brute force auth on honeypot server (honey-neo-dc)
2019-12-03 22:09:32
39.105.208.39 attackbotsspam
2019-12-03T16:24:54.889585tmaserv sshd\[10662\]: Invalid user barra from 39.105.208.39 port 51310
2019-12-03T16:24:54.896585tmaserv sshd\[10662\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=39.105.208.39
2019-12-03T16:24:56.773884tmaserv sshd\[10662\]: Failed password for invalid user barra from 39.105.208.39 port 51310 ssh2
2019-12-03T16:28:15.909566tmaserv sshd\[10850\]: Invalid user user2 from 39.105.208.39 port 41456
2019-12-03T16:28:15.915725tmaserv sshd\[10850\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=39.105.208.39
2019-12-03T16:28:17.385745tmaserv sshd\[10850\]: Failed password for invalid user user2 from 39.105.208.39 port 41456 ssh2
...
2019-12-03 22:37:55
35.196.239.92 attackbotsspam
Dec  3 14:12:40 pornomens sshd\[11544\]: Invalid user alexia from 35.196.239.92 port 56170
Dec  3 14:12:40 pornomens sshd\[11544\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.196.239.92
Dec  3 14:12:42 pornomens sshd\[11544\]: Failed password for invalid user alexia from 35.196.239.92 port 56170 ssh2
...
2019-12-03 21:51:45
165.22.58.247 attackbotsspam
Dec  3 13:53:01 venus sshd\[22781\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.58.247  user=root
Dec  3 13:53:03 venus sshd\[22781\]: Failed password for root from 165.22.58.247 port 56258 ssh2
Dec  3 13:59:45 venus sshd\[22930\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.58.247  user=root
...
2019-12-03 22:30:47
154.221.17.24 attackbots
F2B jail: sshd. Time: 2019-12-03 14:42:19, Reported by: VKReport
2019-12-03 21:54:43

Recently Reported IPs

112.165.50.32 84.27.116.188 193.168.152.51 37.150.248.59
201.217.159.98 209.167.222.33 151.237.199.36 202.59.128.88
221.240.226.25 60.121.135.242 36.219.12.38 86.121.139.217
78.122.212.215 2.70.253.57 71.255.162.207 145.239.38.88
118.253.9.191 88.162.30.244 103.233.123.177 221.111.228.161