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

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

;; QUESTION SECTION:
;104.244.99.118.			IN	A

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

;; Query time: 68 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 02:56:00 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 118.99.244.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 118.99.244.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
64.40.115.151 attack
RDPBruteCAu
2020-01-23 14:25:04
41.155.203.100 attackspambots
Fail2Ban Ban Triggered
2020-01-23 14:59:02
182.61.104.130 attackspam
Jan 23 06:58:29 hosting sshd[22975]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.104.130  user=root
Jan 23 06:58:31 hosting sshd[22975]: Failed password for root from 182.61.104.130 port 41792 ssh2
...
2020-01-23 14:28:14
134.209.16.36 attackspambots
Invalid user teapot from 134.209.16.36 port 59774
2020-01-23 14:27:07
106.51.137.113 attack
Jan 15 06:48:51 host sshd[57661]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.51.137.113
Jan 15 06:48:51 host sshd[57661]: Invalid user deploy from 106.51.137.113 port 42586
Jan 15 06:48:53 host sshd[57661]: Failed password for invalid user deploy from 106.51.137.113 port 42586 ssh2
...
2020-01-23 15:11:33
35.233.93.152 attack
xmlrpc attack
2020-01-23 14:21:26
111.231.109.151 attackbotsspam
Unauthorized connection attempt detected from IP address 111.231.109.151 to port 2220 [J]
2020-01-23 14:17:38
134.73.51.161 attack
RBL listed IP. Trying to send Spam. IP autobanned
2020-01-23 14:55:00
190.121.19.1 attackspam
20/1/22@12:13:32: FAIL: Alarm-Intrusion address from=190.121.19.1
20/1/22@12:13:32: FAIL: Alarm-Intrusion address from=190.121.19.1
...
2020-01-23 15:12:15
18.191.144.17 attack
Unauthorized connection attempt detected from IP address 18.191.144.17 to port 2220 [J]
2020-01-23 14:54:04
222.186.180.6 attackbots
Jan2306:48:49server6sshd[29135]:refusedconnectfrom222.186.180.6\(222.186.180.6\)Jan2306:48:49server6sshd[29134]:refusedconnectfrom222.186.180.6\(222.186.180.6\)Jan2306:48:49server6sshd[29136]:refusedconnectfrom222.186.180.6\(222.186.180.6\)Jan2306:48:49server6sshd[29137]:refusedconnectfrom222.186.180.6\(222.186.180.6\)Jan2307:02:12server6sshd[29760]:refusedconnectfrom222.186.180.6\(222.186.180.6\)
2020-01-23 14:15:59
61.8.69.98 attack
Unauthorized connection attempt detected from IP address 61.8.69.98 to port 2220 [J]
2020-01-23 14:29:58
122.165.140.147 attack
Invalid user ads from 122.165.140.147 port 35510
2020-01-23 14:29:30
114.34.155.117 attackspambots
Unauthorized connection attempt detected from IP address 114.34.155.117 to port 8000 [J]
2020-01-23 14:57:13
218.92.0.138 attack
Unauthorized connection attempt detected from IP address 218.92.0.138 to port 22 [J]
2020-01-23 14:59:23

Recently Reported IPs

104.244.99.116 104.244.99.32 104.245.16.150 104.244.99.33
104.244.99.31 104.245.16.98 104.245.196.26 104.245.16.206
104.244.139.24 104.245.79.228 104.247.72.196 104.247.198.34
104.247.75.140 104.247.76.152 104.247.76.182 104.247.76.196
104.247.76.238 104.247.77.210 104.247.77.218 104.247.79.127