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

;; QUESTION SECTION:
;104.22.69.68.			IN	A

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

;; Query time: 67 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 10:24:42 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 68.69.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 68.69.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
52.172.206.77 attackbots
Invalid user files from 52.172.206.77 port 38532
2020-03-13 03:34:16
45.83.66.253 attackspam
2019-12-27T21:53:10.407Z CLOSE host=45.83.66.253 port=37548 fd=4 time=20.011 bytes=12
...
2020-03-13 03:55:00
49.88.112.63 attack
2019-12-09T05:04:51.616Z CLOSE host=49.88.112.63 port=17433 fd=4 time=20.015 bytes=7
...
2020-03-13 03:20:31
222.186.31.83 attackbots
SSH Brute-Force reported by Fail2Ban
2020-03-13 03:31:39
49.4.122.27 attackspam
2019-10-19T17:36:11.887Z CLOSE host=49.4.122.27 port=54986 fd=4 time=20.018 bytes=6
...
2020-03-13 03:27:17
46.18.68.89 attackbotsspam
2020-02-18T17:09:13.395Z CLOSE host=46.18.68.89 port=62103 fd=5 time=20.007 bytes=25
...
2020-03-13 03:50:43
46.46.106.211 attackbots
2019-11-12T19:15:46.594Z CLOSE host=46.46.106.211 port=64590 fd=4 time=30.015 bytes=29
...
2020-03-13 03:46:19
49.88.112.61 attack
2020-01-10T12:33:39.022Z CLOSE host=49.88.112.61 port=46091 fd=4 time=20.020 bytes=26
...
2020-03-13 03:21:28
181.126.83.125 attackbots
Mar 12 19:28:08 mail sshd[11011]: Failed password for root from 181.126.83.125 port 47506 ssh2
...
2020-03-13 03:40:28
46.136.223.99 attackspam
2019-11-26T19:00:28.221Z CLOSE host=46.136.223.99 port=56368 fd=4 time=20.019 bytes=14
2019-11-26T19:00:28.222Z CLOSE host=46.136.223.99 port=56370 fd=5 time=20.012 bytes=31
...
2020-03-13 03:52:25
51.19.120.229 attackspambots
Telnet/23 MH Probe, Scan, BF, Hack -
2020-03-13 03:26:27
47.9.222.250 attack
2019-11-29T11:20:21.418Z CLOSE host=47.9.222.250 port=50902 fd=4 time=160.114 bytes=260
...
2020-03-13 03:41:34
49.49.238.240 attackspambots
2020-03-11T09:27:57.574Z CLOSE host=49.49.238.240 port=52908 fd=4 time=20.008 bytes=27
...
2020-03-13 03:26:04
206.189.193.135 attackspambots
Mar 12 20:17:11 mout sshd[6108]: Invalid user kame from 206.189.193.135 port 54094
2020-03-13 03:24:09
80.211.225.143 attack
Mar 12 14:41:17 Tower sshd[31266]: Connection from 80.211.225.143 port 43722 on 192.168.10.220 port 22 rdomain ""
Mar 12 14:41:19 Tower sshd[31266]: Invalid user ts3 from 80.211.225.143 port 43722
Mar 12 14:41:19 Tower sshd[31266]: error: Could not get shadow information for NOUSER
Mar 12 14:41:19 Tower sshd[31266]: Failed password for invalid user ts3 from 80.211.225.143 port 43722 ssh2
Mar 12 14:41:19 Tower sshd[31266]: Received disconnect from 80.211.225.143 port 43722:11: Bye Bye [preauth]
Mar 12 14:41:19 Tower sshd[31266]: Disconnected from invalid user ts3 80.211.225.143 port 43722 [preauth]
2020-03-13 03:54:10

Recently Reported IPs

104.22.69.174 104.22.69.222 104.22.69.226 104.22.7.133
104.22.7.234 104.22.7.177 13.226.31.116 104.22.7.7
104.22.7.249 104.22.70.169 104.22.71.169 104.22.70.177
104.22.71.177 104.22.72.162 104.22.72.195 104.22.72.215
104.22.72.114 104.22.73.114 104.22.72.86 104.22.72.89