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

;; QUESTION SECTION:
;42.216.99.41.			IN	A

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

;; Query time: 74 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Dec 30 20:35:18 CST 2021
;; MSG SIZE  rcvd: 105
Host info
Host 41.99.216.42.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 41.99.216.42.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
49.247.192.42 attack
Unauthorized connection attempt detected from IP address 49.247.192.42 to port 2220 [J]
2020-01-17 04:21:38
117.248.94.211 attackspambots
Invalid user driver from 117.248.94.211 port 52294
2020-01-17 04:13:55
36.155.102.212 attackbots
Jan 16 23:20:10 server sshd\[24860\]: Invalid user sx from 36.155.102.212
Jan 16 23:20:10 server sshd\[24860\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.155.102.212 
Jan 16 23:20:12 server sshd\[24860\]: Failed password for invalid user sx from 36.155.102.212 port 57884 ssh2
Jan 16 23:23:34 server sshd\[25485\]: Invalid user test from 36.155.102.212
Jan 16 23:23:34 server sshd\[25485\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.155.102.212 
...
2020-01-17 04:23:59
188.166.160.107 attackspam
Invalid user gilberto from 188.166.160.107 port 53706
2020-01-17 04:33:46
194.150.197.86 attackbots
Unauthorized connection attempt detected from IP address 194.150.197.86 to port 2220 [J]
2020-01-17 04:01:45
106.13.120.176 attackspambots
Unauthorized connection attempt detected from IP address 106.13.120.176 to port 2220 [J]
2020-01-17 04:16:47
170.84.224.240 attack
Unauthorized connection attempt detected from IP address 170.84.224.240 to port 2220 [J]
2020-01-17 04:05:36
190.153.249.99 attackbotsspam
Unauthorized connection attempt detected from IP address 190.153.249.99 to port 2220 [J]
2020-01-17 04:33:22
193.255.125.180 attackbots
01/16/2020-13:59:16.574065 193.255.125.180 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2020-01-17 04:02:37
189.8.68.56 attackbots
Unauthorized connection attempt detected from IP address 189.8.68.56 to port 2220 [J]
2020-01-17 04:03:17
188.164.188.248 attack
Scanning
2020-01-17 04:34:01
202.29.220.114 attack
Unauthorized connection attempt detected from IP address 202.29.220.114 to port 2220 [J]
2020-01-17 04:30:08
212.91.77.226 attackbotsspam
Invalid user vmware from 212.91.77.226 port 42358
2020-01-17 04:27:52
103.87.93.20 attackbots
Invalid user test from 103.87.93.20 port 45036
2020-01-17 04:18:06
128.199.123.170 attack
Unauthorized connection attempt detected from IP address 128.199.123.170 to port 2220 [J]
2020-01-17 04:11:50

Recently Reported IPs

64.28.88.47 193.168.25.210 215.51.14.171 211.20.159.98
55.81.152.109 117.157.226.222 136.184.30.255 117.161.153.251
64.168.63.82 162.233.200.95 117.177.130.159 216.92.215.64
117.239.126.152 118.104.149.194 145.223.209.47 94.235.247.217
169.32.148.118 118.247.232.109 119.110.239.110 135.93.233.122