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

;; QUESTION SECTION:
;104.20.44.132.			IN	A

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

;; Query time: 82 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 22 06:12:52 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 132.44.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 132.44.20.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
45.32.171.70 attack
Automatic report - XMLRPC Attack
2019-12-30 21:16:53
217.145.45.2 attack
$f2bV_matches
2019-12-30 20:47:29
222.124.149.138 attackbotsspam
$f2bV_matches
2019-12-30 21:00:26
189.228.90.84 attackbots
Automatic report - Port Scan Attack
2019-12-30 21:27:06
162.243.14.185 attackspambots
Dec 30 14:01:42 sd-53420 sshd\[6761\]: Invalid user fairis from 162.243.14.185
Dec 30 14:01:42 sd-53420 sshd\[6761\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.243.14.185
Dec 30 14:01:44 sd-53420 sshd\[6761\]: Failed password for invalid user fairis from 162.243.14.185 port 54070 ssh2
Dec 30 14:03:45 sd-53420 sshd\[7465\]: Invalid user koeber from 162.243.14.185
Dec 30 14:03:45 sd-53420 sshd\[7465\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.243.14.185
...
2019-12-30 21:18:08
27.78.12.22 attackspambots
Invalid user post from 27.78.12.22 port 41424
2019-12-30 20:59:41
114.80.101.104 attackbots
SMB Server BruteForce Attack
2019-12-30 21:01:17
96.56.66.142 attackspam
19/12/30@01:21:31: FAIL: Alarm-Telnet address from=96.56.66.142
...
2019-12-30 21:07:40
109.194.175.27 attack
$f2bV_matches
2019-12-30 20:58:19
71.6.232.4 attack
Unauthorized connection attempt detected from IP address 71.6.232.4 to port 8080
2019-12-30 21:19:25
39.152.54.180 attackbotsspam
Dec 30 07:21:55 163-172-32-151 proftpd[23917]: 0.0.0.0 (39.152.54.180[39.152.54.180]) - USER anonymous: no such user found from 39.152.54.180 [39.152.54.180] to 163.172.32.151:21
...
2019-12-30 20:54:04
207.46.13.36 attackbotsspam
Automatic report - Banned IP Access
2019-12-30 21:17:44
92.63.194.31 attackspam
PPTP VPN Brute-Force login. Usernames it tries are: 1, 11, 111, 1111, 123, 1234, Admin, admin, test, user, vpn
2019-12-30 21:23:13
5.196.42.123 attackspam
Dec 30 13:47:46 v22018086721571380 sshd[1404]: Failed password for invalid user roloff from 5.196.42.123 port 53810 ssh2
Dec 30 13:50:55 v22018086721571380 sshd[1644]: Failed password for invalid user mysql from 5.196.42.123 port 41615 ssh2
2019-12-30 21:04:44
23.94.81.50 attackspambots
xmlrpc attack
2019-12-30 21:17:12

Recently Reported IPs

216.105.46.196 104.20.46.222 9.49.212.16 104.20.47.222
104.20.5.59 104.20.55.247 104.20.56.247 104.20.64.80
104.20.65.80 104.20.79.32 104.20.80.32 104.20.84.3
104.200.110.147 106.75.95.184 145.92.143.30 104.206.118.204
57.153.132.91 104.206.89.198 104.207.143.149 104.207.159.114