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

;; QUESTION SECTION:
;104.22.68.46.			IN	A

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

;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 22 06:16:56 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 46.68.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 46.68.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
159.203.21.134 attackbots
Attempted connection to port 3288.
2020-04-02 22:12:16
106.12.14.130 attackspambots
SSH invalid-user multiple login attempts
2020-04-02 22:00:47
14.248.83.92 attack
Attempted connection to port 5555.
2020-04-02 22:18:06
172.73.138.24 attackbotsspam
Attempted connection to port 32946.
2020-04-02 22:03:22
170.231.187.24 attackbots
Attempted connection to port 32763.
2020-04-02 22:09:27
67.205.135.65 attackbots
Invalid user admin from 67.205.135.65 port 54154
2020-04-02 21:47:34
106.13.132.192 attack
2020-04-02T05:46:59.195578-07:00 suse-nuc sshd[5910]: Invalid user qn from 106.13.132.192 port 38104
...
2020-04-02 21:50:53
78.128.113.73 attack
IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking.
2020-04-02 22:15:07
220.190.13.218 attackbots
Thu Apr  2 15:46:21 2020 \[pid 43056\] \[anonymous\] FAIL LOGIN: Client "220.190.13.218"Thu Apr  2 15:46:26 2020 \[pid 43069\] \[www\] FAIL LOGIN: Client "220.190.13.218"Thu Apr  2 15:46:30 2020 \[pid 43076\] \[www\] FAIL LOGIN: Client "220.190.13.218"Thu Apr  2 15:46:37 2020 \[pid 43086\] \[www\] FAIL LOGIN: Client "220.190.13.218"Thu Apr  2 15:46:43 2020 \[pid 43091\] \[www\] FAIL LOGIN: Client "220.190.13.218"
...
2020-04-02 22:19:59
189.148.200.203 attackbotsspam
Attempted connection to port 1433.
2020-04-02 21:35:01
128.199.199.217 attack
Invalid user bh from 128.199.199.217 port 39872
2020-04-02 22:17:48
139.199.168.18 attackspambots
Apr  2 16:50:37 lukav-desktop sshd\[15704\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.168.18  user=root
Apr  2 16:50:39 lukav-desktop sshd\[15704\]: Failed password for root from 139.199.168.18 port 40542 ssh2
Apr  2 16:56:20 lukav-desktop sshd\[15999\]: Invalid user ling from 139.199.168.18
Apr  2 16:56:20 lukav-desktop sshd\[15999\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.168.18
Apr  2 16:56:22 lukav-desktop sshd\[15999\]: Failed password for invalid user ling from 139.199.168.18 port 41478 ssh2
2020-04-02 22:20:20
160.16.203.152 attackspam
Attempted connection to port 65191.
2020-04-02 22:10:43
167.99.210.237 attackspam
Attempted connection to port 17031.
2020-04-02 22:10:12
120.253.63.34 attackspam
Attempted connection to port 43113.
2020-04-02 22:27:51

Recently Reported IPs

104.22.68.132 104.22.71.158 104.22.74.194 104.22.75.194
104.22.78.23 104.221.178.196 104.223.147.110 104.225.8.62
119.19.255.185 104.227.13.79 104.233.149.108 104.233.151.3
104.233.158.146 219.120.189.189 247.177.234.193 104.248.128.151
104.248.133.7 104.248.16.56 104.248.169.45 104.248.203.125