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

;; QUESTION SECTION:
;104.20.45.144.			IN	A

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

;; Query time: 68 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Apr 13 10:51:01 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 144.45.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 144.45.20.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
105.154.192.97 attackbotsspam
Brute forcing Wordpress login
2019-08-13 15:10:22
218.241.191.1 attack
Aug 13 09:35:02 srv206 sshd[862]: Invalid user ftpuser from 218.241.191.1
...
2019-08-13 16:08:24
52.17.153.36 attack
Brute forcing Wordpress login
2019-08-13 15:27:22
134.209.100.247 attack
Aug 13 10:53:26 microserver sshd[44573]: Invalid user alexie from 134.209.100.247 port 41480
Aug 13 10:53:26 microserver sshd[44573]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.100.247
Aug 13 10:53:28 microserver sshd[44573]: Failed password for invalid user alexie from 134.209.100.247 port 41480 ssh2
Aug 13 11:02:27 microserver sshd[45892]: Invalid user prashant from 134.209.100.247 port 55086
Aug 13 11:02:27 microserver sshd[45892]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.100.247
Aug 13 11:13:18 microserver sshd[47437]: Invalid user user from 134.209.100.247 port 40374
Aug 13 11:13:18 microserver sshd[47437]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.100.247
Aug 13 11:13:19 microserver sshd[47437]: Failed password for invalid user user from 134.209.100.247 port 40374 ssh2
Aug 13 11:18:46 microserver sshd[48224]: Invalid user kouno from 134.209.100
2019-08-13 15:56:07
91.134.248.253 attackbotsspam
Brute forcing Wordpress login
2019-08-13 15:14:30
222.175.55.138 attackspam
SMB Server BruteForce Attack
2019-08-13 16:08:02
189.121.250.2 attackspam
Aug 13 07:42:47 marvibiene sshd[26026]: Invalid user support from 189.121.250.2 port 47186
Aug 13 07:42:47 marvibiene sshd[26026]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.121.250.2
Aug 13 07:42:47 marvibiene sshd[26026]: Invalid user support from 189.121.250.2 port 47186
Aug 13 07:42:49 marvibiene sshd[26026]: Failed password for invalid user support from 189.121.250.2 port 47186 ssh2
...
2019-08-13 15:43:50
222.120.192.122 attack
Aug 13 03:35:00 debian sshd\[4828\]: Invalid user asalyers from 222.120.192.122 port 39754
Aug 13 03:35:00 debian sshd\[4828\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.120.192.122
Aug 13 03:35:02 debian sshd\[4828\]: Failed password for invalid user asalyers from 222.120.192.122 port 39754 ssh2
...
2019-08-13 16:07:20
52.166.120.45 attack
Brute forcing Wordpress login
2019-08-13 15:26:42
50.209.71.165 attackspam
Automated report - ssh fail2ban:
Aug 13 09:03:34 wrong password, user=cyrus, port=1389, ssh2
Aug 13 09:35:07 authentication failure 
Aug 13 09:35:10 wrong password, user=nagios, port=4405, ssh2
2019-08-13 15:57:50
149.202.93.130 attack
Brute forcing Wordpress login
2019-08-13 15:03:39
81.22.45.219 attack
Aug 13 08:58:28 h2177944 kernel: \[4003261.723037\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.219 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=45237 PROTO=TCP SPT=58115 DPT=9005 WINDOW=1024 RES=0x00 SYN URGP=0 
Aug 13 09:05:58 h2177944 kernel: \[4003711.305554\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.219 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=46595 PROTO=TCP SPT=58115 DPT=3535 WINDOW=1024 RES=0x00 SYN URGP=0 
Aug 13 09:10:34 h2177944 kernel: \[4003987.426790\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.219 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=5486 PROTO=TCP SPT=58115 DPT=60089 WINDOW=1024 RES=0x00 SYN URGP=0 
Aug 13 09:29:15 h2177944 kernel: \[4005108.054199\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.219 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=58325 PROTO=TCP SPT=58115 DPT=3150 WINDOW=1024 RES=0x00 SYN URGP=0 
Aug 13 09:35:05 h2177944 kernel: \[4005457.732875\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.219 DST=85.214.117.9 LEN=
2019-08-13 16:03:19
45.32.99.23 attackbots
Brute forcing Wordpress login
2019-08-13 15:30:56
49.88.112.60 attackbotsspam
Aug 13 09:34:42 vps01 sshd[3362]: Failed password for root from 49.88.112.60 port 13245 ssh2
2019-08-13 15:48:15
112.85.42.229 attackbotsspam
Splunk® : Brute-Force login attempt on SSH:
Aug 13 03:40:23 testbed sshd[10336]: Failed password for root from 112.85.42.229 port 50215 ssh2
2019-08-13 15:42:41

Recently Reported IPs

104.20.38.24 104.20.46.144 104.20.51.213 104.20.51.32
104.20.57.170 104.20.62.87 104.20.72.14 104.20.72.234
104.20.73.14 104.20.73.234 104.20.74.236 104.20.75.236
104.20.81.96 104.20.83.135 104.20.85.74 104.20.88.212
104.22.7.167 104.22.7.205 104.22.7.5 104.22.72.145