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

;; QUESTION SECTION:
;104.149.53.222.			IN	A

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

;; Query time: 57 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 16 01:16:12 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 222.53.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 222.53.149.104.in-addr.arpa: SERVFAIL

Related IP info:
Related comments:
IP Type Details Datetime
58.59.25.2 attackbots
Unauthorized connection attempt from IP address 58.59.25.2 on Port 445(SMB)
2020-01-03 19:13:31
120.29.225.101 attackspam
Unauthorized connection attempt from IP address 120.29.225.101 on Port 445(SMB)
2020-01-03 19:02:57
138.68.82.220 attackbotsspam
2020-01-03T06:04:34.971289shield sshd\[30100\]: Invalid user ci from 138.68.82.220 port 49274
2020-01-03T06:04:34.975432shield sshd\[30100\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.82.220
2020-01-03T06:04:36.969561shield sshd\[30100\]: Failed password for invalid user ci from 138.68.82.220 port 49274 ssh2
2020-01-03T06:07:22.646470shield sshd\[31396\]: Invalid user vpo from 138.68.82.220 port 49120
2020-01-03T06:07:22.650509shield sshd\[31396\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.82.220
2020-01-03 18:56:31
113.88.87.206 attackspambots
Unauthorized connection attempt from IP address 113.88.87.206 on Port 445(SMB)
2020-01-03 19:09:42
184.105.139.106 attackspam
3389BruteforceFW23
2020-01-03 19:09:26
14.176.48.129 attack
20/1/2@23:46:01: FAIL: Alarm-Network address from=14.176.48.129
...
2020-01-03 18:54:02
200.253.164.2 attackbotsspam
SMB Server BruteForce Attack
2020-01-03 18:58:49
124.158.169.34 attackbotsspam
Unauthorized connection attempt from IP address 124.158.169.34 on Port 445(SMB)
2020-01-03 18:53:29
128.199.154.60 attack
Jan  3 08:11:47 mail sshd[16084]: Invalid user saf from 128.199.154.60
Jan  3 08:11:47 mail sshd[16084]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.154.60
Jan  3 08:11:47 mail sshd[16084]: Invalid user saf from 128.199.154.60
Jan  3 08:11:48 mail sshd[16084]: Failed password for invalid user saf from 128.199.154.60 port 51038 ssh2
...
2020-01-03 19:18:33
117.158.94.153 attackbots
port scan and connect, tcp 1433 (ms-sql-s)
2020-01-03 18:44:24
139.199.22.148 attack
Jan  3 10:38:57 dedicated sshd[20038]: Invalid user server from 139.199.22.148 port 46000
2020-01-03 18:53:02
125.163.56.104 attack
1578026745 - 01/03/2020 05:45:45 Host: 125.163.56.104/125.163.56.104 Port: 445 TCP Blocked
2020-01-03 19:07:40
106.13.121.175 attack
Invalid user asterisk from 106.13.121.175 port 48503
2020-01-03 19:16:34
185.216.34.230 attackbotsspam
SQL Injection attack
2020-01-03 18:55:18
203.81.91.112 attackbots
Unauthorized connection attempt from IP address 203.81.91.112 on Port 445(SMB)
2020-01-03 18:47:33

Recently Reported IPs

104.149.53.201 104.149.53.230 104.149.53.239 104.149.59.27
104.149.62.142 104.149.62.154 104.149.62.155 104.149.62.189
104.149.63.138 104.149.63.147 104.149.63.154 104.149.74.73
104.149.85.112 104.152.108.115 104.152.108.206 104.152.109.108
104.152.109.154 104.152.109.2 104.152.109.214 104.152.109.41