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

;; QUESTION SECTION:
;104.22.4.14.			IN	A

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

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 20 19:42:26 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 14.4.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 14.4.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
112.220.85.26 attackbots
Aug 30 11:09:23 lcprod sshd\[7110\]: Invalid user ctrls from 112.220.85.26
Aug 30 11:09:23 lcprod sshd\[7110\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.220.85.26
Aug 30 11:09:25 lcprod sshd\[7110\]: Failed password for invalid user ctrls from 112.220.85.26 port 40656 ssh2
Aug 30 11:14:02 lcprod sshd\[7489\]: Invalid user pratik from 112.220.85.26
Aug 30 11:14:02 lcprod sshd\[7489\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.220.85.26
2019-08-31 05:15:59
23.94.173.252 attackspam
RDP Brute-Force (Grieskirchen RZ1)
2019-08-31 05:30:56
183.134.65.123 attack
Aug 30 06:38:27 web1 sshd\[7525\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.134.65.123  user=root
Aug 30 06:38:29 web1 sshd\[7525\]: Failed password for root from 183.134.65.123 port 37402 ssh2
Aug 30 06:43:18 web1 sshd\[8032\]: Invalid user oracle from 183.134.65.123
Aug 30 06:43:18 web1 sshd\[8032\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.134.65.123
Aug 30 06:43:20 web1 sshd\[8032\]: Failed password for invalid user oracle from 183.134.65.123 port 40014 ssh2
2019-08-31 05:34:34
104.131.224.81 attackbots
Aug 30 11:45:15 wbs sshd\[14910\]: Invalid user ruben from 104.131.224.81
Aug 30 11:45:15 wbs sshd\[14910\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.224.81
Aug 30 11:45:17 wbs sshd\[14910\]: Failed password for invalid user ruben from 104.131.224.81 port 36377 ssh2
Aug 30 11:50:21 wbs sshd\[15378\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.224.81  user=root
Aug 30 11:50:23 wbs sshd\[15378\]: Failed password for root from 104.131.224.81 port 58748 ssh2
2019-08-31 05:54:18
222.231.27.29 attack
Aug 30 23:09:18 plex sshd[21540]: Invalid user username from 222.231.27.29 port 57286
2019-08-31 05:22:55
202.131.152.2 attackbotsspam
"Fail2Ban detected SSH brute force attempt"
2019-08-31 05:49:56
60.52.166.41 attack
[Aegis] @ 2019-08-30 17:23:39  0100 -> Attempted Administrator Privilege Gain: ET SCAN LibSSH Based Frequent SSH Connections Likely BruteForce Attack
2019-08-31 05:28:07
180.168.156.210 attackbots
ssh failed login
2019-08-31 05:40:45
167.71.239.25 attack
Aug 30 11:23:26 hiderm sshd\[3326\]: Invalid user sistemas from 167.71.239.25
Aug 30 11:23:26 hiderm sshd\[3326\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.239.25
Aug 30 11:23:27 hiderm sshd\[3326\]: Failed password for invalid user sistemas from 167.71.239.25 port 53036 ssh2
Aug 30 11:28:18 hiderm sshd\[3776\]: Invalid user testing from 167.71.239.25
Aug 30 11:28:18 hiderm sshd\[3776\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.239.25
2019-08-31 05:43:56
183.6.176.182 attack
Aug 30 18:46:43 mail sshd\[8050\]: Invalid user pop3 from 183.6.176.182 port 47494
Aug 30 18:46:43 mail sshd\[8050\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.6.176.182
...
2019-08-31 05:24:16
134.73.76.204 attackspam
Postfix RBL failed
2019-08-31 05:45:51
192.241.136.237 attackspam
WordPress brute force
2019-08-31 05:23:28
51.254.214.215 attack
WordPress brute force
2019-08-31 05:16:55
68.183.224.118 attackspam
Aug 30 22:10:52 vps691689 sshd[2363]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.224.118
Aug 30 22:10:54 vps691689 sshd[2363]: Failed password for invalid user ccradio from 68.183.224.118 port 34308 ssh2
...
2019-08-31 05:57:17
185.181.8.98 attack
Unauthorised access (Aug 30) SRC=185.181.8.98 LEN=40 TTL=56 ID=49497 TCP DPT=8080 WINDOW=62665 SYN 
Unauthorised access (Aug 28) SRC=185.181.8.98 LEN=40 TTL=56 ID=39781 TCP DPT=8080 WINDOW=62665 SYN 
Unauthorised access (Aug 26) SRC=185.181.8.98 LEN=40 TTL=56 ID=19437 TCP DPT=8080 WINDOW=62665 SYN
2019-08-31 05:45:17

Recently Reported IPs

104.22.39.96 104.22.4.133 104.22.4.240 104.22.4.145
104.22.4.161 104.196.227.216 104.22.4.175 104.22.4.190
104.22.4.26 104.22.4.21 104.22.4.29 104.22.4.250
104.22.4.32 104.22.4.58 104.196.227.88 104.22.40.101
104.22.4.89 104.22.4.59 104.22.4.9 104.22.4.45