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 of America (the)

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

;; QUESTION SECTION:
;132.121.72.20.			IN	A

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

;; Query time: 32 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 23 23:58:27 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 20.72.121.132.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
server can't find 132.121.72.20.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
185.234.219.114 attackbots
Mar  2 16:10:00 mail postfix/smtpd\[13162\]: warning: unknown\[185.234.219.114\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Mar  2 16:10:08 mail postfix/smtpd\[13162\]: warning: unknown\[185.234.219.114\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Mar  2 16:10:19 mail postfix/smtpd\[13162\]: warning: unknown\[185.234.219.114\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Mar  2 16:10:29 mail postfix/smtpd\[13162\]: warning: unknown\[185.234.219.114\]: SASL LOGIN authentication failed: Connection lost to authentication server\
2020-03-02 23:59:30
172.104.99.217 attack
Unauthorized connection attempt detected from IP address 172.104.99.217 to port 8181 [J]
2020-03-03 00:06:58
187.167.196.186 attackspambots
Unauthorized connection attempt detected from IP address 187.167.196.186 to port 23 [J]
2020-03-02 23:58:18
177.170.50.76 attackbots
Unauthorized connection attempt detected from IP address 177.170.50.76 to port 81 [J]
2020-03-03 00:03:42
222.217.65.239 attack
Unauthorized connection attempt detected from IP address 222.217.65.239 to port 1433 [J]
2020-03-03 00:23:57
96.255.250.230 attack
Unauthorized connection attempt detected from IP address 96.255.250.230 to port 1433 [J]
2020-03-03 00:13:36
111.206.120.250 attackbots
Unauthorized connection attempt detected from IP address 111.206.120.250 to port 1433 [J]
2020-03-03 00:12:28
62.63.237.141 attackspambots
Unauthorized connection attempt detected from IP address 62.63.237.141 to port 23 [J]
2020-03-03 00:18:04
189.174.213.1 attackbotsspam
Unauthorized connection attempt detected from IP address 189.174.213.1 to port 1433 [J]
2020-03-02 23:55:57
46.101.184.111 attack
Unauthorized connection attempt detected from IP address 46.101.184.111 to port 22 [J]
2020-03-02 23:48:47
175.196.206.113 attackbotsspam
Unauthorized connection attempt detected from IP address 175.196.206.113 to port 23 [J]
2020-03-03 00:05:02
46.107.81.114 attackspambots
Unauthorized connection attempt detected from IP address 46.107.81.114 to port 23 [J]
2020-03-02 23:48:31
170.106.38.182 attack
Unauthorized connection attempt detected from IP address 170.106.38.182 to port 8088 [J]
2020-03-03 00:07:19
189.212.91.137 attackspambots
Unauthorized connection attempt detected from IP address 189.212.91.137 to port 23 [J]
2020-03-02 23:55:20
134.209.81.63 attack
Unauthorized connection attempt detected from IP address 134.209.81.63 to port 8333 [J]
2020-03-03 00:08:40

Recently Reported IPs

126.240.204.185 150.124.22.73 167.5.3.163 209.77.13.159
187.48.195.154 184.219.44.115 186.154.29.96 41.227.217.205
172.30.231.10 95.92.59.224 212.255.128.226 93.207.231.87
241.143.10.1 41.9.89.49 132.253.195.112 26.205.39.253
17.7.170.197 214.136.42.230 80.134.168.136 232.173.30.80