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

;; QUESTION SECTION:
;104.22.52.108.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 20 19:43:33 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 108.52.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 108.52.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
37.187.140.206 attack
Automatic report - XMLRPC Attack
2019-10-27 06:01:33
148.70.223.115 attackbotsspam
Oct 26 23:00:54 legacy sshd[23705]: Failed password for root from 148.70.223.115 port 41854 ssh2
Oct 26 23:05:39 legacy sshd[23833]: Failed password for root from 148.70.223.115 port 53662 ssh2
Oct 26 23:10:23 legacy sshd[23942]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.223.115
...
2019-10-27 05:50:58
60.191.111.66 attack
Oct 26 22:37:33 pornomens sshd\[18834\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.191.111.66  user=root
Oct 26 22:37:34 pornomens sshd\[18834\]: Failed password for root from 60.191.111.66 port 35790 ssh2
Oct 26 22:45:36 pornomens sshd\[18864\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.191.111.66  user=root
...
2019-10-27 06:01:52
139.59.78.236 attack
$f2bV_matches
2019-10-27 05:51:13
181.189.133.34 attackspam
10/26/2019-16:27:47.529960 181.189.133.34 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-10-27 05:39:08
195.224.138.61 attackbotsspam
Oct 26 23:27:47 cvbnet sshd[25855]: Failed password for root from 195.224.138.61 port 33636 ssh2
...
2019-10-27 06:07:53
202.152.0.14 attack
Oct 26 22:23:41 h2177944 sshd\[19979\]: Invalid user korost from 202.152.0.14 port 48824
Oct 26 22:23:41 h2177944 sshd\[19979\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.152.0.14
Oct 26 22:23:43 h2177944 sshd\[19979\]: Failed password for invalid user korost from 202.152.0.14 port 48824 ssh2
Oct 26 22:27:55 h2177944 sshd\[20147\]: Invalid user rooty1 from 202.152.0.14 port 56946
...
2019-10-27 05:31:43
182.61.176.105 attackspam
2019-10-26T22:21:49.021764tmaserv sshd\[13025\]: Failed password for invalid user gnbc from 182.61.176.105 port 59848 ssh2
2019-10-26T23:22:43.799311tmaserv sshd\[15733\]: Invalid user pluto from 182.61.176.105 port 57460
2019-10-26T23:22:43.804682tmaserv sshd\[15733\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.176.105
2019-10-26T23:22:45.824787tmaserv sshd\[15733\]: Failed password for invalid user pluto from 182.61.176.105 port 57460 ssh2
2019-10-26T23:27:02.088483tmaserv sshd\[15978\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.176.105  user=root
2019-10-26T23:27:04.329767tmaserv sshd\[15978\]: Failed password for root from 182.61.176.105 port 38492 ssh2
...
2019-10-27 05:33:27
164.132.81.106 attackbots
Invalid user aguirre from 164.132.81.106 port 33494
2019-10-27 06:04:17
178.128.85.193 attackbots
Invalid user user from 178.128.85.193 port 38596
2019-10-27 06:00:32
124.156.50.145 attackspambots
Fail2Ban Ban Triggered
2019-10-27 05:58:33
45.227.255.203 attack
Oct 22 17:30:40 h2022099 sshd[22121]: reveeclipse mapping checking getaddrinfo for hostby.SEIMO98net.org [45.227.255.203] failed - POSSIBLE BREAK-IN ATTEMPT!
Oct 22 17:30:40 h2022099 sshd[22121]: Invalid user user from 45.227.255.203
Oct 22 17:30:40 h2022099 sshd[22121]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.227.255.203 
Oct 22 17:30:42 h2022099 sshd[22121]: Failed password for invalid user user from 45.227.255.203 port 29378 ssh2
Oct 22 17:30:42 h2022099 sshd[22121]: Received disconnect from 45.227.255.203: 11: Client disconnecting normally [preauth]
Oct 22 17:30:42 h2022099 sshd[22123]: reveeclipse mapping checking getaddrinfo for hostby.SEIMO98net.org [45.227.255.203] failed - POSSIBLE BREAK-IN ATTEMPT!
Oct 22 17:30:42 h2022099 sshd[22123]: Invalid user default from 45.227.255.203
Oct 22 17:30:42 h2022099 sshd[22123]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.227.255........
-------------------------------
2019-10-27 05:35:11
178.128.221.162 attackbots
Oct 26 23:18:30 localhost sshd\[6460\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.221.162  user=root
Oct 26 23:18:32 localhost sshd\[6460\]: Failed password for root from 178.128.221.162 port 49006 ssh2
Oct 26 23:22:27 localhost sshd\[6800\]: Invalid user lisherness from 178.128.221.162 port 59104
2019-10-27 05:34:40
24.2.205.235 attackspam
2019-10-26T21:53:53.962223abusebot-5.cloudsearch.cf sshd\[23221\]: Invalid user andre from 24.2.205.235 port 44017
2019-10-27 05:57:10
46.38.144.32 attackbotsspam
Oct 26 23:28:03 mail postfix/smtpd\[13710\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Oct 26 23:58:47 mail postfix/smtpd\[14737\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Oct 26 23:59:46 mail postfix/smtpd\[14737\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Oct 27 00:00:47 mail postfix/smtpd\[14852\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
2019-10-27 06:02:16

Recently Reported IPs

104.22.52.117 104.22.52.160 104.22.52.155 104.22.52.142
104.22.52.197 104.22.52.122 104.22.52.211 104.196.239.80
104.22.52.216 34.233.68.241 104.22.52.240 104.22.52.232
104.22.52.245 104.22.52.222 104.22.52.243 104.22.52.95
104.196.24.218 104.196.240.239 104.198.251.120 104.198.26.61