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: China

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

;; QUESTION SECTION:
;120.132.48.149.			IN	A

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

;; Query time: 22 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 12 11:55:47 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 149.48.132.120.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 149.48.132.120.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
222.186.190.17 attackbotsspam
Nov 19 13:04:34 ip-172-31-62-245 sshd\[13907\]: Failed password for root from 222.186.190.17 port 32024 ssh2\
Nov 19 13:04:36 ip-172-31-62-245 sshd\[13907\]: Failed password for root from 222.186.190.17 port 32024 ssh2\
Nov 19 13:04:39 ip-172-31-62-245 sshd\[13907\]: Failed password for root from 222.186.190.17 port 32024 ssh2\
Nov 19 13:04:55 ip-172-31-62-245 sshd\[13911\]: Failed password for root from 222.186.190.17 port 16103 ssh2\
Nov 19 13:05:46 ip-172-31-62-245 sshd\[13920\]: Failed password for root from 222.186.190.17 port 37660 ssh2\
2019-11-19 21:20:05
119.235.30.160 attackbotsspam
Automatic report - XMLRPC Attack
2019-11-19 21:16:42
45.91.151.37 attackspam
Web App Attack
2019-11-19 21:17:10
195.37.175.10 attackspam
Nov 18 13:00:32 prometheus imapd-ssl: LOGIN, user=2nd@x
Nov 18 13:00:35 prometheus imapd-ssl: LOGIN, user=2nd@x
Nov 18 13:00:35 prometheus imapd-ssl: LOGIN, user=2nd@x
Nov 18 13:00:35 prometheus imapd-ssl: LOGIN, user=2nd@x
Nov 18 13:00:37 prometheus imapd-ssl: LOGOUT, user=2nd@x
Nov 18 13:00:37 prometheus imapd-ssl: LOGOUT, user=2nd@x
Nov 18 13:00:39 prometheus imapd-ssl: LOGIN, user=2nd@x
Nov 18 13:00:40 prometheus imapd-ssl: LOGOUT, user=2nd@x
Nov 18 13:10:18 prometheus imapd-ssl: DISCONNECTED, user=2nd@x
Nov 18 13:10:18 prometheus imapd-ssl: DISCONNECTED, user=2nd@x
Nov 18 13:10:18 prometheus imapd-ssl: LOGIN, user=2nd@x
Nov 18 13:15:19 prometheus imapd-ssl: LOGIN, user=2nd@x
Nov 18 13:31:05 prometheus imapd-ssl: LOGIN FAILED, method=PLAIN, ip=[::ffff:195.37.175.10]
Nov 18 13:31:10 prometheus imapd-ssl: LOGIN FAILED, method=PLAIN, ip=[::ffff:195.37.175.10]
Nov 18 13:31:15 prometheus imapd-ssl: LOGIN FAILED, user=2nd@x
Nov 18 13:31:20 prometheus imapd-ssl: LOGOUT, ip........
-------------------------------
2019-11-19 21:23:40
125.211.197.252 attack
Nov 19 13:59:54 ns37 sshd[22279]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.211.197.252
Nov 19 13:59:56 ns37 sshd[22279]: Failed password for invalid user sarojiny from 125.211.197.252 port 41061 ssh2
Nov 19 14:05:31 ns37 sshd[23105]: Failed password for root from 125.211.197.252 port 57187 ssh2
2019-11-19 21:32:51
193.56.28.130 attack
Nov 19 13:05:18 heicom postfix/smtpd\[18427\]: warning: unknown\[193.56.28.130\]: SASL LOGIN authentication failed: authentication failure
Nov 19 13:05:19 heicom postfix/smtpd\[18427\]: warning: unknown\[193.56.28.130\]: SASL LOGIN authentication failed: authentication failure
Nov 19 13:05:19 heicom postfix/smtpd\[18427\]: warning: unknown\[193.56.28.130\]: SASL LOGIN authentication failed: authentication failure
Nov 19 13:05:19 heicom postfix/smtpd\[18427\]: warning: unknown\[193.56.28.130\]: SASL LOGIN authentication failed: authentication failure
Nov 19 13:05:19 heicom postfix/smtpd\[18427\]: warning: unknown\[193.56.28.130\]: SASL LOGIN authentication failed: authentication failure
...
2019-11-19 21:44:40
51.75.52.127 attackbotsspam
11/19/2019-08:05:33.190856 51.75.52.127 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 52
2019-11-19 21:30:36
118.80.77.188 attack
" "
2019-11-19 21:26:06
185.143.223.147 attackspam
11/19/2019-08:05:03.912241 185.143.223.147 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-11-19 21:58:04
167.99.65.138 attackspambots
Nov 19 03:33:49 php1 sshd\[2958\]: Invalid user 123 from 167.99.65.138
Nov 19 03:33:49 php1 sshd\[2958\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.65.138
Nov 19 03:33:51 php1 sshd\[2958\]: Failed password for invalid user 123 from 167.99.65.138 port 33528 ssh2
Nov 19 03:37:58 php1 sshd\[3344\]: Invalid user anurag from 167.99.65.138
Nov 19 03:37:58 php1 sshd\[3344\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.65.138
2019-11-19 21:51:00
78.128.112.114 attackspam
Port scan: Attack repeated for 24 hours
2019-11-19 21:50:01
45.141.86.108 attackbots
RDP over non-standard port attempt
2019-11-19 21:15:47
63.88.23.206 attackspambots
63.88.23.206 was recorded 15 times by 7 hosts attempting to connect to the following ports: 80. Incident counter (4h, 24h, all-time): 15, 97, 337
2019-11-19 21:47:48
172.87.221.196 attackspam
1574168733 - 11/19/2019 14:05:33 Host: 172.87.221.196/172.87.221.196 Port: 5060 UDP Blocked
2019-11-19 21:32:01
84.14.254.44 attackspambots
11/19/2019-14:05:31.820991 84.14.254.44 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-11-19 21:33:40

Recently Reported IPs

120.132.28.94 120.132.50.44 120.132.52.1 120.132.52.10
120.132.52.12 120.132.52.128 120.132.52.144 120.132.52.15
120.132.52.152 120.132.52.16 120.132.52.169 120.132.52.170
120.132.52.172 120.132.52.176 120.132.52.18 120.132.52.183
120.132.52.192 120.132.52.2 120.132.52.20 120.132.52.22