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

;; QUESTION SECTION:
;104.22.9.9.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 03:47:10 CST 2022
;; MSG SIZE  rcvd: 103
Host info
Host 9.9.22.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 9.9.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
167.99.183.191 attackspambots
Invalid user 02 from 167.99.183.191 port 41638
2020-02-23 19:54:08
94.200.107.2 attack
Unauthorized connection attempt detected from IP address 94.200.107.2 to port 23 [J]
2020-02-23 19:32:45
181.197.64.77 attackspambots
Feb 23 10:59:32 ns382633 sshd\[11092\]: Invalid user suporte from 181.197.64.77 port 42444
Feb 23 10:59:32 ns382633 sshd\[11092\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.197.64.77
Feb 23 10:59:34 ns382633 sshd\[11092\]: Failed password for invalid user suporte from 181.197.64.77 port 42444 ssh2
Feb 23 11:02:37 ns382633 sshd\[11734\]: Invalid user ts3 from 181.197.64.77 port 37740
Feb 23 11:02:37 ns382633 sshd\[11734\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.197.64.77
2020-02-23 19:51:45
118.69.64.250 attackspambots
Unauthorized connection attempt detected from IP address 118.69.64.250 to port 23 [J]
2020-02-23 19:56:37
217.9.50.219 attack
Unauthorized connection attempt detected from IP address 217.9.50.219 to port 2220 [J]
2020-02-23 19:44:22
186.249.29.190 attackbotsspam
Unauthorized connection attempt detected from IP address 186.249.29.190 to port 23 [J]
2020-02-23 19:18:52
200.175.44.191 attackspam
Unauthorized connection attempt detected from IP address 200.175.44.191 to port 23 [J]
2020-02-23 19:47:20
121.153.179.122 attack
Unauthorized connection attempt detected from IP address 121.153.179.122 to port 8000 [J]
2020-02-23 19:56:17
185.50.56.226 attackbotsspam
Unauthorized connection attempt detected from IP address 185.50.56.226 to port 81 [J]
2020-02-23 19:19:29
177.152.66.4 attackbots
Unauthorized connection attempt detected from IP address 177.152.66.4 to port 23 [J]
2020-02-23 19:21:14
183.80.212.62 attackbots
Unauthorized connection attempt detected from IP address 183.80.212.62 to port 23 [J]
2020-02-23 19:19:57
220.74.104.157 attackbotsspam
Unauthorized connection attempt detected from IP address 220.74.104.157 to port 5555 [J]
2020-02-23 19:43:47
116.110.220.136 attackspambots
Unauthorized connection attempt detected from IP address 116.110.220.136 to port 26 [J]
2020-02-23 19:28:41
95.78.171.222 attackbotsspam
Unauthorized connection attempt detected from IP address 95.78.171.222 to port 80 [J]
2020-02-23 19:32:23
172.105.125.93 attack
Unauthorized connection attempt detected from IP address 172.105.125.93 to port 902 [J]
2020-02-23 19:53:47

Recently Reported IPs

104.22.9.83 104.22.9.87 104.220.232.82 104.22.9.91
104.221.59.188 104.22.9.95 104.222.176.201 104.222.176.10
67.44.177.16 104.222.43.112 104.22.9.94 104.222.43.159
104.222.43.170 104.222.43.17 104.222.43.197 104.222.43.245
104.222.43.31 104.222.98.128 104.223.83.165 104.223.62.200