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

;; QUESTION SECTION:
;104.22.4.5.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 20:00:38 CST 2022
;; MSG SIZE  rcvd: 103
Host info
Host 5.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 5.4.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
45.55.80.186 attack
Nov 23 17:45:59 plusreed sshd[7379]: Invalid user server from 45.55.80.186
...
2019-11-24 06:50:44
203.145.165.94 attackspam
Unauthorized connection attempt from IP address 203.145.165.94 on Port 445(SMB)
2019-11-24 06:58:01
68.183.160.63 attackspam
2019-11-23T22:34:33.813954shield sshd\[9491\]: Invalid user ramesh from 68.183.160.63 port 56514
2019-11-23T22:34:33.818719shield sshd\[9491\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.160.63
2019-11-23T22:34:36.104210shield sshd\[9491\]: Failed password for invalid user ramesh from 68.183.160.63 port 56514 ssh2
2019-11-23T22:41:34.181183shield sshd\[11235\]: Invalid user rakhi from 68.183.160.63 port 43996
2019-11-23T22:41:34.185405shield sshd\[11235\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.160.63
2019-11-24 06:46:32
190.180.73.228 attackspambots
Unauthorized access or intrusion attempt detected from Thor banned IP
2019-11-24 06:31:52
114.220.10.183 attack
Nov 23 23:16:02 mx1 postfix/smtpd\[9817\]: warning: unknown\[114.220.10.183\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6Nov 23 23:16:22 mx1 postfix/smtpd\[9817\]: warning: unknown\[114.220.10.183\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6Nov 23 23:16:49 mx1 postfix/smtpd\[9816\]: warning: unknown\[114.220.10.183\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-11-24 06:31:32
47.148.108.250 attackspam
DATE:2019-11-23 15:16:45, IP:47.148.108.250, PORT:telnet - Telnet brute force auth on a honeypot server (epe-dc)
2019-11-24 06:34:40
222.186.173.180 attack
Nov 23 23:52:01 icinga sshd[24798]: Failed password for root from 222.186.173.180 port 38102 ssh2
Nov 23 23:52:14 icinga sshd[24798]: error: maximum authentication attempts exceeded for root from 222.186.173.180 port 38102 ssh2 [preauth]
...
2019-11-24 06:55:16
46.101.17.215 attackbotsspam
Nov 23 20:56:37 serwer sshd\[6625\]: User sshd from 46.101.17.215 not allowed because not listed in AllowUsers
Nov 23 20:56:37 serwer sshd\[6625\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.17.215  user=sshd
Nov 23 20:56:39 serwer sshd\[6625\]: Failed password for invalid user sshd from 46.101.17.215 port 53360 ssh2
...
2019-11-24 06:38:52
43.225.109.39 attackspambots
Unauthorised access (Nov 24) SRC=43.225.109.39 LEN=40 TTL=244 ID=59290 TCP DPT=445 WINDOW=1024 SYN
2019-11-24 06:59:07
94.23.208.211 attackspambots
5x Failed Password
2019-11-24 06:29:25
152.136.180.82 attack
152.136.180.82 was recorded 65 times by 26 hosts attempting to connect to the following ports: 2376,4243,2375,2377. Incident counter (4h, 24h, all-time): 65, 365, 373
2019-11-24 06:36:29
80.252.147.210 attack
Unauthorized connection attempt from IP address 80.252.147.210 on Port 445(SMB)
2019-11-24 06:44:25
114.67.82.158 attackbotsspam
114.67.82.158 was recorded 103 times by 27 hosts attempting to connect to the following ports: 2375,2377,4243,2376. Incident counter (4h, 24h, all-time): 103, 328, 328
2019-11-24 06:28:20
49.206.195.70 attackspambots
Unauthorized connection attempt from IP address 49.206.195.70 on Port 445(SMB)
2019-11-24 06:45:21
5.90.78.230 attackbots
Nov2319:02:45server2dovecot:imap-login:Disconnected:Inactivity\(authfailed\,1attemptsin180secs\):user=\\,method=PLAIN\,rip=37.182.15.244\,lip=81.17.25.230\,session=\Nov2319:02:45server2dovecot:imap-login:Disconnected:Inactivity\(authfailed\,1attemptsin179secs\):user=\\,method=PLAIN\,rip=37.182.15.244\,lip=81.17.25.230\,session=\Nov2319:44:45server2dovecot:imap-login:Abortedlogin\(authfailed\,1attemptsin3secs\):user=\\,method=PLAIN\,rip=5.90.78.230\,lip=81.17.25.230\,session=\Nov2319:45:05server2dovecot:imap-login:Abortedlogin\(authfailed\,1attemptsin2secs\):user=\\,method=PLAIN\,rip=5.90.78.230\,lip=81.17.25.230\,session=\Nov2319:45:05server2dovecot:imap-login:Abortedlogin\(authfailed\,1attemptsin2secs\):user=\\,method=PLAIN\,rip=5.90.78.230\,lip=81.17.25.230\,session=\
2019-11-24 06:33:19

Recently Reported IPs

104.22.4.65 104.22.40.132 104.22.4.67 104.22.40.114
104.22.40.193 104.22.40.164 104.22.40.206 104.22.40.136
104.22.40.66 104.22.40.234 104.22.41.114 104.22.41.132
101.109.29.119 104.22.40.77 104.22.41.164 104.22.41.136
104.22.41.193 104.22.41.206 216.117.175.225 104.22.41.234