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: Los Angeles

Region: California

Country: United States

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

;; QUESTION SECTION:
;104.149.63.166.			IN	A

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

;; Query time: 25 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 10:40:28 CST 2022
;; MSG SIZE  rcvd: 107
Host info
b'Host 166.63.149.104.in-addr.arpa not found: 2(SERVFAIL)
'
Nslookup info:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 166.63.149.104.in-addr.arpa: SERVFAIL

Related IP info:
Related comments:
IP Type Details Datetime
180.94.172.217 attackspam
trying to access non-authorized port
2020-05-13 16:17:28
103.28.52.84 attack
May 13 02:51:48 NPSTNNYC01T sshd[20432]: Failed password for root from 103.28.52.84 port 32812 ssh2
May 13 02:55:44 NPSTNNYC01T sshd[20711]: Failed password for root from 103.28.52.84 port 36016 ssh2
...
2020-05-13 16:47:08
99.185.76.161 attackspambots
Invalid user user from 99.185.76.161 port 60888
2020-05-13 16:08:05
50.66.167.29 attackbots
2020-05-13T08:00:02.885752abusebot-5.cloudsearch.cf sshd[4055]: Invalid user pi from 50.66.167.29 port 39250
2020-05-13T08:00:03.167869abusebot-5.cloudsearch.cf sshd[4053]: Invalid user pi from 50.66.167.29 port 39248
2020-05-13T08:00:03.104699abusebot-5.cloudsearch.cf sshd[4055]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=s0106b827eb45b5c1.cg.shawcable.net
2020-05-13T08:00:02.885752abusebot-5.cloudsearch.cf sshd[4055]: Invalid user pi from 50.66.167.29 port 39250
2020-05-13T08:00:05.489780abusebot-5.cloudsearch.cf sshd[4055]: Failed password for invalid user pi from 50.66.167.29 port 39250 ssh2
2020-05-13T08:00:03.331785abusebot-5.cloudsearch.cf sshd[4053]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=s0106b827eb45b5c1.cg.shawcable.net
2020-05-13T08:00:03.167869abusebot-5.cloudsearch.cf sshd[4053]: Invalid user pi from 50.66.167.29 port 39248
2020-05-13T08:00:05.713536abusebot-5.cloudsearch.cf sshd
...
2020-05-13 16:05:02
82.148.18.194 attackspambots
postfix
2020-05-13 16:10:59
51.77.210.216 attackspam
$f2bV_matches
2020-05-13 16:15:51
27.145.208.97 attackbotsspam
2020-05-12 22:50:17.797939-0500  localhost sshd[55814]: Failed password for root from 27.145.208.97 port 56554 ssh2
2020-05-13 16:02:46
94.177.246.39 attackbots
May 13 04:08:28 localhost sshd\[17624\]: Invalid user masterkey from 94.177.246.39 port 36634
May 13 04:08:28 localhost sshd\[17624\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.177.246.39
May 13 04:08:30 localhost sshd\[17624\]: Failed password for invalid user masterkey from 94.177.246.39 port 36634 ssh2
...
2020-05-13 16:42:19
66.131.216.79 attack
May 13 08:54:47 gw1 sshd[15890]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.131.216.79
May 13 08:54:49 gw1 sshd[15890]: Failed password for invalid user ems from 66.131.216.79 port 50964 ssh2
...
2020-05-13 16:13:14
218.69.91.84 attack
$f2bV_matches
2020-05-13 16:19:04
124.204.65.82 attackspambots
May 13 06:15:57  sshd\[15957\]: User ftp from 124.204.65.82 not allowed because not listed in AllowUsersMay 13 06:15:59  sshd\[15957\]: Failed password for invalid user ftp from 124.204.65.82 port 13723 ssh2
...
2020-05-13 16:21:17
198.37.118.29 attackbots
198.37.118.29 - - \[13/May/2020:08:25:25 +0200\] "POST //wp-login.php HTTP/1.0" 200 6674 "https://wpmeetup-muenchen.org//wp-login.php" "Mozilla/5.0 \(Windows NT 10.0\; Win64\; x64\) AppleWebKit/537.36 \(KHTML, like Gecko\) Chrome/79.0 Safari/537.36"
198.37.118.29 - - \[13/May/2020:08:25:25 +0200\] "POST //wp-login.php HTTP/1.0" 200 6674 "https://wpmeetup-muenchen.org//wp-login.php" "Mozilla/5.0 \(Windows NT 10.0\; Win64\; x64\) AppleWebKit/537.36 \(KHTML, like Gecko\) Chrome/79.0 Safari/537.36"
198.37.118.29 - - \[13/May/2020:08:25:26 +0200\] "POST //wp-login.php HTTP/1.0" 200 6674 "https://wpmeetup-muenchen.org//wp-login.php" "Mozilla/5.0 \(Windows NT 10.0\; Win64\; x64\) AppleWebKit/537.36 \(KHTML, like Gecko\) Chrome/79.0 Safari/537.36"
2020-05-13 16:16:17
42.118.80.102 attackbotsspam
Unauthorized connection attempt detected from IP address 42.118.80.102 to port 85 [T]
2020-05-13 16:38:49
51.83.68.213 attackspam
(sshd) Failed SSH login from 51.83.68.213 (FR/France/213.ip-51-83-68.eu): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: May 13 09:24:52 amsweb01 sshd[20117]: Invalid user jaimito from 51.83.68.213 port 34632
May 13 09:24:54 amsweb01 sshd[20117]: Failed password for invalid user jaimito from 51.83.68.213 port 34632 ssh2
May 13 09:27:44 amsweb01 sshd[20371]: Invalid user viktor from 51.83.68.213 port 44310
May 13 09:27:46 amsweb01 sshd[20371]: Failed password for invalid user viktor from 51.83.68.213 port 44310 ssh2
May 13 09:29:30 amsweb01 sshd[20564]: Invalid user testftp from 51.83.68.213 port 44378
2020-05-13 16:13:51
116.240.199.23 attack
May 13 10:54:51 server2 sshd\[2655\]: Invalid user lroot from 116.240.199.23
May 13 10:54:54 server2 sshd\[2657\]: Invalid user DUP from 116.240.199.23
May 13 10:54:56 server2 sshd\[2659\]: User root from 116.240.199.23 not allowed because not listed in AllowUsers
May 13 10:54:59 server2 sshd\[2661\]: Invalid user admins from 116.240.199.23
May 13 10:55:01 server2 sshd\[2663\]: User bin from 116.240.199.23 not allowed because not listed in AllowUsers
May 13 10:55:04 server2 sshd\[2849\]: Invalid user butter from 116.240.199.23
2020-05-13 16:07:05

Recently Reported IPs

104.149.63.174 104.149.63.167 104.149.63.175 104.149.63.177
104.149.63.179 104.149.63.169 104.149.63.180 104.149.63.183
104.149.63.182 104.149.63.185 104.149.63.187 104.149.63.186
104.149.67.6 104.149.63.184 104.149.66.54 104.149.63.189
104.149.70.80 104.149.74.100 104.149.74.102 104.149.74.103