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: unknown

Region: unknown

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

;; QUESTION SECTION:
;104.16.109.149.			IN	A

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

;; Query time: 54 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 01:34:11 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 149.109.16.104.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 149.109.16.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
189.39.65.210 attack
Unauthorized connection attempt from IP address 189.39.65.210 on Port 445(SMB)
2019-11-24 22:38:47
71.6.146.185 attackbots
771/tcp 4567/tcp 5001/tcp...
[2019-09-23/11-24]435pkt,200pt.(tcp),41pt.(udp)
2019-11-24 22:31:37
195.49.186.210 attackbotsspam
195.49.186.210 was recorded 5 times by 1 hosts attempting to connect to the following ports: 23. Incident counter (4h, 24h, all-time): 5, 5, 133
2019-11-24 22:57:21
121.166.81.15 attackspam
Nov 24 13:53:24 [host] sshd[13624]: Invalid user gateway from 121.166.81.15
Nov 24 13:53:24 [host] sshd[13624]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.166.81.15
Nov 24 13:53:26 [host] sshd[13624]: Failed password for invalid user gateway from 121.166.81.15 port 57360 ssh2
2019-11-24 22:46:01
182.61.33.47 attackbots
Nov 24 06:17:03 ms-srv sshd[43297]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.33.47
Nov 24 06:17:06 ms-srv sshd[43297]: Failed password for invalid user girl from 182.61.33.47 port 36102 ssh2
2019-11-24 22:19:59
5.148.3.212 attackbotsspam
2019-11-24T19:39:02.955855luisaranguren sshd[3884251]: Connection from 5.148.3.212 port 57154 on 10.10.10.6 port 22 rdomain ""
2019-11-24T19:39:04.646622luisaranguren sshd[3884251]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.148.3.212  user=root
2019-11-24T19:39:06.641816luisaranguren sshd[3884251]: Failed password for root from 5.148.3.212 port 57154 ssh2
2019-11-24T19:57:28.459422luisaranguren sshd[3886965]: Connection from 5.148.3.212 port 33812 on 10.10.10.6 port 22 rdomain ""
2019-11-24T19:57:30.150486luisaranguren sshd[3886965]: Invalid user mykayla from 5.148.3.212 port 33812
...
2019-11-24 22:21:53
46.101.41.162 attackspambots
$f2bV_matches
2019-11-24 23:00:44
185.142.236.35 attackspambots
12345/tcp 3299/tcp 636/tcp...
[2019-09-23/11-24]406pkt,212pt.(tcp),37pt.(udp)
2019-11-24 22:51:27
13.224.132.122 attackspam
TCP Port Scanning
2019-11-24 22:32:19
118.70.190.188 attackspam
2019-11-24T14:57:05.537053abusebot-5.cloudsearch.cf sshd\[17622\]: Invalid user jrun from 118.70.190.188 port 38304
2019-11-24 23:04:56
148.72.213.52 attack
SSH brute-force: detected 7 distinct usernames within a 24-hour window.
2019-11-24 22:36:17
196.216.206.2 attackspam
Nov 24 16:59:35 microserver sshd[42716]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.216.206.2  user=daemon
Nov 24 16:59:37 microserver sshd[42716]: Failed password for daemon from 196.216.206.2 port 52248 ssh2
Nov 24 17:03:40 microserver sshd[43348]: Invalid user webmaster from 196.216.206.2 port 33682
Nov 24 17:03:40 microserver sshd[43348]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.216.206.2
Nov 24 17:03:42 microserver sshd[43348]: Failed password for invalid user webmaster from 196.216.206.2 port 33682 ssh2
Nov 24 17:17:35 microserver sshd[45358]: Invalid user walas from 196.216.206.2 port 35364
Nov 24 17:17:35 microserver sshd[45358]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.216.206.2
Nov 24 17:17:37 microserver sshd[45358]: Failed password for invalid user walas from 196.216.206.2 port 35364 ssh2
Nov 24 17:21:59 microserver sshd[45988]: Invalid user host fr
2019-11-24 23:03:02
81.22.45.39 attackbotsspam
2019-11-24T15:21:34.910461+01:00 lumpi kernel: [4427657.474420] INPUT:DROP:SPAMHAUS_EDROP:IN=eth0 OUT= MAC=52:54:a2:01:a5:04:d2:74:7f:6e:37:e3:08:00 SRC=81.22.45.39 DST=172.31.1.100 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=61921 PROTO=TCP SPT=41891 DPT=4333 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-11-24 22:25:23
167.114.115.22 attack
2019-11-24T14:57:09.345818abusebot-6.cloudsearch.cf sshd\[17092\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=22.ip-167-114-115.net  user=root
2019-11-24 23:00:29
91.225.79.162 attackbots
DATE:2019-11-24 15:57:07, IP:91.225.79.162, PORT:telnet - Telnet brute force auth on a honeypot server (epe-dc)
2019-11-24 23:04:12

Recently Reported IPs

104.16.108.239 104.16.108.149 104.16.109.239 104.16.109.231
106.233.194.59 104.21.63.193 104.16.110.149 104.16.109.43
104.16.109.18 104.16.109.79 104.16.110.231 104.16.110.239
104.16.111.71 104.16.111.239 104.16.110.43 104.16.112.239
104.21.63.194 104.16.111.149 104.16.112.149 104.16.113.65