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

;; QUESTION SECTION:
;121.5.200.149.			IN	A

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

;; Query time: 34 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 16 15:26:20 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 149.200.5.121.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.200.5.121.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
60.250.23.233 attackbots
SSH Invalid Login
2020-05-03 05:53:52
37.59.100.22 attackspambots
2020-05-02T21:47:15.705849shield sshd\[16842\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=22.ip-37-59-100.eu  user=root
2020-05-02T21:47:18.372608shield sshd\[16842\]: Failed password for root from 37.59.100.22 port 48450 ssh2
2020-05-02T21:50:57.478205shield sshd\[17331\]: Invalid user niraj from 37.59.100.22 port 53217
2020-05-02T21:50:57.481814shield sshd\[17331\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=22.ip-37-59-100.eu
2020-05-02T21:50:59.956641shield sshd\[17331\]: Failed password for invalid user niraj from 37.59.100.22 port 53217 ssh2
2020-05-03 05:56:06
99.84.32.47 attackspambots
ET INFO TLS Handshake Failure - port: 47029 proto: TCP cat: Potentially Bad Traffic
2020-05-03 06:08:03
51.89.65.23 attackspambots
ET SCAN Sipvicious Scan - port: 5060 proto: UDP cat: Attempted Information Leak
2020-05-03 06:19:04
64.225.115.188 attackbots
ET CINS Active Threat Intelligence Poor Reputation IP group 51 - port: 8455 proto: TCP cat: Misc Attack
2020-05-03 06:15:47
31.134.209.80 attackbots
ET CINS Active Threat Intelligence Poor Reputation IP group 12 - port: 1315 proto: TCP cat: Misc Attack
2020-05-03 06:25:40
37.49.226.250 attack
ET CINS Active Threat Intelligence Poor Reputation IP group 16 - port: 5038 proto: TCP cat: Misc Attack
2020-05-03 06:24:14
43.243.168.63 attack
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-03 06:23:41
103.145.12.88 attackbotsspam
ET SCAN Sipvicious User-Agent Detected (friendly-scanner) - port: 5060 proto: UDP cat: Attempted Information Leak
2020-05-03 06:07:20
219.129.237.188 attack
Unauthorized connection attempt from IP address 219.129.237.188 on Port 3306(MYSQL)
2020-05-03 06:28:14
162.243.138.123 attack
ET SCAN Suspicious inbound to mySQL port 3306 - port: 3306 proto: TCP cat: Potentially Bad Traffic
2020-05-03 06:01:51
58.217.103.57 attackbotsspam
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-03 06:18:10
79.8.100.126 attackspam
ET CINS Active Threat Intelligence Poor Reputation IP group 64 - port: 8089 proto: TCP cat: Misc Attack
2020-05-03 06:12:29
64.227.10.240 attack
ET CINS Active Threat Intelligence Poor Reputation IP group 52 - port: 24191 proto: TCP cat: Misc Attack
2020-05-03 06:14:41
181.225.44.26 attackspambots
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-03 06:00:34

Recently Reported IPs

126.186.171.18 135.171.51.97 237.45.106.50 208.31.27.216
254.59.235.67 91.32.34.173 229.141.146.235 37.79.200.18
15.96.194.116 17.7.148.210 47.41.128.186 132.11.247.86
123.147.240.140 30.91.243.204 126.19.59.66 150.165.24.3
93.207.209.124 119.8.0.0 17.2.249.76 225.96.184.249