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

;; QUESTION SECTION:
;104.22.4.139.			IN	A

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

;; Query time: 73 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 20 19:42:25 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 139.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 139.4.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
159.203.88.67 attackspam
Feb 10 08:27:14 legacy sshd[20253]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.88.67
Feb 10 08:27:16 legacy sshd[20253]: Failed password for invalid user nfh from 159.203.88.67 port 45674 ssh2
Feb 10 08:30:32 legacy sshd[20459]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.88.67
...
2020-02-10 19:46:28
185.131.63.86 attack
Feb  9 22:10:15 hpm sshd\[30644\]: Invalid user fsy from 185.131.63.86
Feb  9 22:10:15 hpm sshd\[30644\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.131.63.86
Feb  9 22:10:17 hpm sshd\[30644\]: Failed password for invalid user fsy from 185.131.63.86 port 57882 ssh2
Feb  9 22:13:46 hpm sshd\[31080\]: Invalid user uma from 185.131.63.86
Feb  9 22:13:46 hpm sshd\[31080\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.131.63.86
2020-02-10 19:31:35
203.143.12.26 attackspam
Feb 10 08:14:34 sd-53420 sshd\[32460\]: Invalid user scv from 203.143.12.26
Feb 10 08:14:34 sd-53420 sshd\[32460\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.143.12.26
Feb 10 08:14:36 sd-53420 sshd\[32460\]: Failed password for invalid user scv from 203.143.12.26 port 17683 ssh2
Feb 10 08:17:05 sd-53420 sshd\[32706\]: Invalid user kbl from 203.143.12.26
Feb 10 08:17:05 sd-53420 sshd\[32706\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.143.12.26
...
2020-02-10 19:56:06
40.107.5.104 spam
Used for SPAM, PHISHING and SCAM for SEXE on STOLLEN list we don't know, as usual with LIERS and ROBERS !
2020-02-10 19:38:18
104.248.150.47 attackbotsspam
$f2bV_matches
2020-02-10 19:23:37
129.154.67.65 attackspam
Feb  9 23:47:27 web1 sshd\[19058\]: Invalid user ttw from 129.154.67.65
Feb  9 23:47:27 web1 sshd\[19058\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.154.67.65
Feb  9 23:47:29 web1 sshd\[19058\]: Failed password for invalid user ttw from 129.154.67.65 port 13377 ssh2
Feb  9 23:53:01 web1 sshd\[19515\]: Invalid user ehl from 129.154.67.65
Feb  9 23:53:01 web1 sshd\[19515\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.154.67.65
2020-02-10 19:51:23
51.178.27.197 attack
Feb 10 12:13:30 srv01 postfix/smtpd\[21895\]: warning: 197.ip-51-178-27.eu\[51.178.27.197\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Feb 10 12:16:18 srv01 postfix/smtpd\[21895\]: warning: 197.ip-51-178-27.eu\[51.178.27.197\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Feb 10 12:16:51 srv01 postfix/smtpd\[21895\]: warning: 197.ip-51-178-27.eu\[51.178.27.197\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Feb 10 12:16:59 srv01 postfix/smtpd\[21895\]: warning: 197.ip-51-178-27.eu\[51.178.27.197\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Feb 10 12:17:00 srv01 postfix/smtpd\[1280\]: warning: 197.ip-51-178-27.eu\[51.178.27.197\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-02-10 19:50:23
185.176.27.94 attackspambots
02/10/2020-11:10:21.609125 185.176.27.94 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2020-02-10 19:47:25
200.110.174.137 attackbots
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.110.174.137
Failed password for invalid user goe from 200.110.174.137 port 44901 ssh2
Invalid user cgi from 200.110.174.137 port 58555
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.110.174.137
Failed password for invalid user cgi from 200.110.174.137 port 58555 ssh2
2020-02-10 19:45:58
113.194.97.249 attackspam
firewall-block, port(s): 137/udp
2020-02-10 19:48:27
59.127.40.64 attack
Honeypot attack, port: 81, PTR: 59-127-40-64.HINET-IP.hinet.net.
2020-02-10 19:24:06
49.235.90.120 attackspam
Feb 10 09:52:32 ns382633 sshd\[7787\]: Invalid user sfj from 49.235.90.120 port 52512
Feb 10 09:52:32 ns382633 sshd\[7787\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.90.120
Feb 10 09:52:34 ns382633 sshd\[7787\]: Failed password for invalid user sfj from 49.235.90.120 port 52512 ssh2
Feb 10 10:09:01 ns382633 sshd\[10487\]: Invalid user obr from 49.235.90.120 port 45092
Feb 10 10:09:01 ns382633 sshd\[10487\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.90.120
2020-02-10 19:14:49
121.229.59.100 attackbots
Feb 10 11:36:39 MK-Soft-VM3 sshd[21288]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.229.59.100 
Feb 10 11:36:41 MK-Soft-VM3 sshd[21288]: Failed password for invalid user hxx from 121.229.59.100 port 42386 ssh2
...
2020-02-10 19:57:48
41.223.117.68 attackspam
The IP address signed into my Google account without authorization
2020-02-10 19:52:57
223.14.97.24 attack
unauthorized connection attempt
2020-02-10 19:25:54

Recently Reported IPs

104.22.4.13 104.22.39.96 104.22.4.14 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