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

;; QUESTION SECTION:
;104.149.74.72.			IN	A

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

;; Query time: 71 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 10:40:50 CST 2022
;; MSG SIZE  rcvd: 106
Host info
b'Host 72.74.149.104.in-addr.arpa not found: 2(SERVFAIL)
'
Nslookup info:
server can't find 104.149.74.72.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
74.120.14.34 attackspam
Icarus honeypot on github
2020-10-02 02:46:53
45.129.33.148 attack
[N3.H3.VM3] Port Scanner Detected Blocked by UFW
2020-10-02 02:25:23
74.106.249.155 attackbots
 TCP (SYN) 74.106.249.155:56411 -> port 3389, len 40
2020-10-02 02:34:57
121.32.48.30 attack
Brute forcing email accounts
2020-10-02 02:26:23
142.93.226.235 attack
142.93.226.235 - - [01/Oct/2020:19:13:57 +0100] "POST /wp-login.php HTTP/1.1" 200 2426 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
142.93.226.235 - - [01/Oct/2020:19:14:06 +0100] "POST /wp-login.php HTTP/1.1" 200 2407 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
142.93.226.235 - - [01/Oct/2020:19:14:11 +0100] "POST /wp-login.php HTTP/1.1" 200 2441 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-10-02 02:21:36
49.235.99.209 attackspam
Invalid user george from 49.235.99.209 port 39390
2020-10-02 02:41:05
218.92.0.204 attackbots
2020-10-01T11:54:14.033877abusebot-4.cloudsearch.cf sshd[21326]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.204  user=root
2020-10-01T11:54:16.416825abusebot-4.cloudsearch.cf sshd[21326]: Failed password for root from 218.92.0.204 port 51534 ssh2
2020-10-01T11:54:18.993290abusebot-4.cloudsearch.cf sshd[21326]: Failed password for root from 218.92.0.204 port 51534 ssh2
2020-10-01T11:54:14.033877abusebot-4.cloudsearch.cf sshd[21326]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.204  user=root
2020-10-01T11:54:16.416825abusebot-4.cloudsearch.cf sshd[21326]: Failed password for root from 218.92.0.204 port 51534 ssh2
2020-10-01T11:54:18.993290abusebot-4.cloudsearch.cf sshd[21326]: Failed password for root from 218.92.0.204 port 51534 ssh2
2020-10-01T11:54:14.033877abusebot-4.cloudsearch.cf sshd[21326]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rho
...
2020-10-02 02:20:38
201.134.205.138 attackbots
(smtpauth) Failed SMTP AUTH login from 201.134.205.138 (MX/Mexico/customer-201-134-205-138.uninet-ide.com.mx): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-10-01 16:21:38 login authenticator failed for (USER) [201.134.205.138]: 535 Incorrect authentication data (set_id=info@jahanayegh.com)
2020-10-02 02:48:02
82.77.18.151 attack
Automatic report - Port Scan Attack
2020-10-02 02:25:05
106.54.224.217 attack
Invalid user tt from 106.54.224.217 port 40024
pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.224.217
Invalid user tt from 106.54.224.217 port 40024
Failed password for invalid user tt from 106.54.224.217 port 40024 ssh2
Invalid user hue from 106.54.224.217 port 53280
2020-10-02 02:42:27
106.13.92.126 attack
Oct  1 16:48:58 Server sshd[1169702]: Failed password for root from 106.13.92.126 port 46582 ssh2
Oct  1 16:53:20 Server sshd[1171792]: Invalid user sftpuser from 106.13.92.126 port 37522
Oct  1 16:53:20 Server sshd[1171792]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.92.126 
Oct  1 16:53:20 Server sshd[1171792]: Invalid user sftpuser from 106.13.92.126 port 37522
Oct  1 16:53:22 Server sshd[1171792]: Failed password for invalid user sftpuser from 106.13.92.126 port 37522 ssh2
...
2020-10-02 02:39:04
49.207.4.16 attackspambots
Automatic report - Port Scan Attack
2020-10-02 02:37:37
177.0.108.210 attackspam
(sshd) Failed SSH login from 177.0.108.210 (BR/Brazil/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct  1 18:10:35 elude sshd[11825]: Invalid user vanessa from 177.0.108.210 port 52226
Oct  1 18:10:37 elude sshd[11825]: Failed password for invalid user vanessa from 177.0.108.210 port 52226 ssh2
Oct  1 18:29:59 elude sshd[14718]: Invalid user ark from 177.0.108.210 port 44590
Oct  1 18:30:00 elude sshd[14718]: Failed password for invalid user ark from 177.0.108.210 port 44590 ssh2
Oct  1 18:48:01 elude sshd[17442]: Invalid user solr from 177.0.108.210 port 33016
2020-10-02 02:46:22
121.121.134.33 attackspam
SSH bruteforce
2020-10-02 02:21:51
101.27.96.247 attackbots
20/9/30@16:35:06: FAIL: IoT-Telnet address from=101.27.96.247
...
2020-10-02 02:17:45

Recently Reported IPs

104.149.74.71 104.149.74.76 104.149.74.74 104.149.74.75
104.16.17.98 104.158.228.135 104.16.33.106 104.16.47.74
104.16.83.96 104.16.83.8 104.16.84.8 104.16.91.22
104.16.93.26 104.160.25.68 104.160.23.245 104.161.48.242
104.16.82.96 104.163.141.120 104.160.27.204 104.163.140.10