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

;; QUESTION SECTION:
;104.20.25.53.			IN	A

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

;; Query time: 21 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 12:09:36 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 53.25.20.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 53.25.20.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
182.253.228.184 attack
Fail2Ban Ban Triggered
2019-12-04 14:54:20
54.39.44.47 attackbots
Dec  3 20:24:43 php1 sshd\[24516\]: Invalid user supriya from 54.39.44.47
Dec  3 20:24:43 php1 sshd\[24516\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.39.44.47
Dec  3 20:24:46 php1 sshd\[24516\]: Failed password for invalid user supriya from 54.39.44.47 port 43076 ssh2
Dec  3 20:30:14 php1 sshd\[25025\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.39.44.47  user=backup
Dec  3 20:30:16 php1 sshd\[25025\]: Failed password for backup from 54.39.44.47 port 53954 ssh2
2019-12-04 15:06:46
195.56.253.49 attackspam
Dec  4 07:30:11 vpn01 sshd[9868]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.56.253.49
Dec  4 07:30:13 vpn01 sshd[9868]: Failed password for invalid user server from 195.56.253.49 port 38820 ssh2
...
2019-12-04 14:51:56
200.19.156.22 attackbots
Attempted to connect 2 times to port 53 UDP
2019-12-04 14:51:10
118.68.0.62 attackspam
Dec  4 07:03:21 vpn01 sshd[9112]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.68.0.62
Dec  4 07:03:23 vpn01 sshd[9112]: Failed password for invalid user milsid from 118.68.0.62 port 47620 ssh2
...
2019-12-04 14:24:38
121.142.111.98 attack
Automatic report - Banned IP Access
2019-12-04 14:44:33
59.58.209.253 attackbotsspam
12/03/2019-23:56:31.818609 59.58.209.253 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-12-04 14:25:32
49.234.56.194 attackbotsspam
2019-12-04T06:40:07.769617abusebot-2.cloudsearch.cf sshd\[13577\]: Invalid user com from 49.234.56.194 port 47300
2019-12-04 15:07:32
188.166.211.194 attackspambots
2019-12-04T06:23:43.240586shield sshd\[3822\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.211.194  user=root
2019-12-04T06:23:45.181142shield sshd\[3822\]: Failed password for root from 188.166.211.194 port 46391 ssh2
2019-12-04T06:30:37.737386shield sshd\[5037\]: Invalid user zmzizi from 188.166.211.194 port 51293
2019-12-04T06:30:37.741971shield sshd\[5037\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.211.194
2019-12-04T06:30:39.852773shield sshd\[5037\]: Failed password for invalid user zmzizi from 188.166.211.194 port 51293 ssh2
2019-12-04 14:39:52
103.63.109.74 attackbots
2019-12-04T07:16:43.681963  sshd[1978]: Invalid user guest from 103.63.109.74 port 56434
2019-12-04T07:16:43.694573  sshd[1978]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.63.109.74
2019-12-04T07:16:43.681963  sshd[1978]: Invalid user guest from 103.63.109.74 port 56434
2019-12-04T07:16:45.309435  sshd[1978]: Failed password for invalid user guest from 103.63.109.74 port 56434 ssh2
2019-12-04T07:30:00.074377  sshd[2197]: Invalid user pups from 103.63.109.74 port 37074
...
2019-12-04 15:12:21
153.254.113.26 attack
Dec  3 22:04:36 server sshd\[4377\]: Failed password for invalid user diag from 153.254.113.26 port 38622 ssh2
Dec  4 09:21:22 server sshd\[31816\]: Invalid user rpm from 153.254.113.26
Dec  4 09:21:22 server sshd\[31816\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=153.254.113.26 
Dec  4 09:21:24 server sshd\[31816\]: Failed password for invalid user rpm from 153.254.113.26 port 52774 ssh2
Dec  4 09:30:01 server sshd\[1197\]: Invalid user kiley from 153.254.113.26
Dec  4 09:30:02 server sshd\[1197\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=153.254.113.26 
...
2019-12-04 14:40:20
177.23.196.77 attackspambots
Dec  3 20:47:06 web9 sshd\[12109\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.23.196.77  user=root
Dec  3 20:47:07 web9 sshd\[12109\]: Failed password for root from 177.23.196.77 port 43502 ssh2
Dec  3 20:55:25 web9 sshd\[13308\]: Invalid user svk from 177.23.196.77
Dec  3 20:55:25 web9 sshd\[13308\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.23.196.77
Dec  3 20:55:27 web9 sshd\[13308\]: Failed password for invalid user svk from 177.23.196.77 port 57786 ssh2
2019-12-04 14:55:37
202.207.0.141 attackbots
12/04/2019-01:30:02.011466 202.207.0.141 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-12-04 15:10:29
222.186.180.17 attackbotsspam
Dec  4 07:30:51 icinga sshd[59429]: Failed password for root from 222.186.180.17 port 60654 ssh2
Dec  4 07:30:54 icinga sshd[59429]: Failed password for root from 222.186.180.17 port 60654 ssh2
Dec  4 07:30:58 icinga sshd[59429]: Failed password for root from 222.186.180.17 port 60654 ssh2
Dec  4 07:31:02 icinga sshd[59429]: Failed password for root from 222.186.180.17 port 60654 ssh2
...
2019-12-04 14:46:41
188.166.42.50 attackbotsspam
Dec  4 07:14:36 relay postfix/smtpd\[26989\]: warning: unknown\[188.166.42.50\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec  4 07:15:49 relay postfix/smtpd\[27106\]: warning: unknown\[188.166.42.50\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec  4 07:16:22 relay postfix/smtpd\[27106\]: warning: unknown\[188.166.42.50\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec  4 07:20:56 relay postfix/smtpd\[31254\]: warning: unknown\[188.166.42.50\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec  4 07:30:24 relay postfix/smtpd\[21937\]: warning: unknown\[188.166.42.50\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-12-04 14:42:40

Recently Reported IPs

104.20.25.177 104.20.26.177 104.20.26.239 104.20.250.13
104.20.28.74 104.20.27.74 104.20.27.239 104.20.30.33
104.20.30.220 104.22.79.130 104.20.251.13 104.20.31.205
104.20.31.33 104.20.31.220 104.20.32.101 104.20.33.101
104.20.32.205 104.22.79.131 104.20.33.238 104.20.33.58