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

;; QUESTION SECTION:
;104.22.1.21.			IN	A

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

;; Query time: 70 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 13:58:19 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 21.1.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 21.1.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
152.32.170.248 attackbotsspam
Jan 19 06:07:54 h2812830 sshd[15353]: Invalid user sanchez from 152.32.170.248 port 46932
Jan 19 06:07:54 h2812830 sshd[15353]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.32.170.248
Jan 19 06:07:54 h2812830 sshd[15353]: Invalid user sanchez from 152.32.170.248 port 46932
Jan 19 06:07:56 h2812830 sshd[15353]: Failed password for invalid user sanchez from 152.32.170.248 port 46932 ssh2
Jan 19 06:18:25 h2812830 sshd[15824]: Invalid user coffer from 152.32.170.248 port 52062
...
2020-01-19 15:05:11
222.82.57.159 attack
Unauthorized connection attempt detected from IP address 222.82.57.159 to port 80 [J]
2020-01-19 15:23:24
88.243.33.180 attack
unauthorized connection attempt
2020-01-19 14:50:57
94.191.108.37 attackbotsspam
Unauthorized connection attempt detected from IP address 94.191.108.37 to port 2220 [J]
2020-01-19 14:49:20
31.149.33.86 attack
Unauthorized connection attempt detected from IP address 31.149.33.86 to port 22 [T]
2020-01-19 14:54:09
220.132.0.42 attackspam
Unauthorized connection attempt detected from IP address 220.132.0.42 to port 4567 [J]
2020-01-19 15:24:26
39.82.95.117 attackspambots
Unauthorized connection attempt detected from IP address 39.82.95.117 to port 80 [J]
2020-01-19 15:18:56
27.109.244.90 attackbots
Unauthorized connection attempt detected from IP address 27.109.244.90 to port 85 [J]
2020-01-19 15:20:40
37.191.211.98 attackbots
Unauthorized connection attempt detected from IP address 37.191.211.98 to port 23 [J]
2020-01-19 15:19:22
46.190.103.149 attackbots
Unauthorized connection attempt detected from IP address 46.190.103.149 to port 23 [J]
2020-01-19 14:52:50
211.22.65.186 attackspam
Unauthorized connection attempt detected from IP address 211.22.65.186 to port 23 [J]
2020-01-19 15:26:51
37.110.33.192 attack
Unauthorized connection attempt detected from IP address 37.110.33.192 to port 22 [J]
2020-01-19 15:19:48
45.113.71.200 attackspambots
Unauthorized connection attempt detected from IP address 45.113.71.200 to port 2160 [J]
2020-01-19 15:17:08
218.208.183.164 attack
Unauthorized connection attempt detected from IP address 218.208.183.164 to port 2323 [J]
2020-01-19 15:26:11
195.158.108.80 attack
Unauthorized connection attempt detected from IP address 195.158.108.80 to port 8081 [J]
2020-01-19 15:28:07

Recently Reported IPs

104.22.1.237 104.22.1.71 104.22.1.76 104.22.12.185
104.22.10.70 104.22.12.123 104.22.1.69 104.22.11.70
104.22.1.56 104.22.12.146 104.22.12.18 105.213.102.132
104.22.12.65 104.22.12.76 104.22.12.202 104.22.13.185
104.22.13.123 104.22.13.18 104.22.13.146 105.213.102.143