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

;; QUESTION SECTION:
;218.202.214.49.			IN	A

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

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 28 22:08:11 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 49.214.202.218.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 49.214.202.218.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
79.52.153.58 attack
Automatic report - Port Scan Attack
2020-02-01 23:58:28
148.66.132.190 attack
detected by Fail2Ban
2020-02-01 23:59:25
109.225.103.168 attackspambots
Unauthorized connection attempt detected from IP address 109.225.103.168 to port 5555 [J]
2020-02-02 00:32:51
148.70.1.30 attackspam
...
2020-02-01 23:57:30
148.235.82.68 attackbotsspam
Feb  1 16:54:36 legacy sshd[7753]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.235.82.68
Feb  1 16:54:38 legacy sshd[7753]: Failed password for invalid user deploy from 148.235.82.68 port 49050 ssh2
Feb  1 16:59:26 legacy sshd[8144]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.235.82.68
...
2020-02-02 00:07:50
168.0.237.125 attack
20/2/1@08:36:06: FAIL: Alarm-Network address from=168.0.237.125
20/2/1@08:36:07: FAIL: Alarm-Network address from=168.0.237.125
...
2020-02-02 00:26:11
148.66.142.135 attackspam
...
2020-02-01 23:58:07
49.235.81.235 attackbots
Unauthorized connection attempt detected from IP address 49.235.81.235 to port 2220 [J]
2020-02-02 00:45:40
147.135.130.142 attackspam
...
2020-02-02 00:35:40
80.82.64.171 attackbotsspam
670/tcp 243/tcp 213/tcp...
[2019-12-24/2020-02-01]269pkt,249pt.(tcp)
2020-02-02 00:09:33
92.222.136.169 attackbots
2020-02-01T10:37:29.400769vostok sshd\[18943\]: Invalid user thuntington from 92.222.136.169 port 58506
2020-02-01T10:37:29.403998vostok sshd\[18943\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=blog.minable.xyz | Triggered by Fail2Ban at Vostok web server
2020-02-02 00:20:22
1.162.144.40 attack
23/tcp 23/tcp
[2020-01-26/02-01]2pkt
2020-02-02 00:27:57
45.141.84.44 attackbots
Unauthorized connection attempt detected from IP address 45.141.84.44 to port 555 [T]
2020-02-02 00:20:42
180.251.92.31 attackspam
Honeypot attack, port: 445, PTR: PTR record not found
2020-02-02 00:11:16
148.66.135.178 attackspambots
Dec  1 16:50:58 v22018076590370373 sshd[11154]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.66.135.178 
...
2020-02-01 23:59:04

Recently Reported IPs

159.251.125.192 25.33.230.210 151.71.204.19 88.100.94.135
209.238.0.192 144.135.158.58 237.216.107.83 181.62.105.160
202.207.219.4 246.187.168.184 84.137.239.82 14.233.196.41
47.188.133.104 30.241.144.126 253.33.91.41 254.179.212.212
186.113.223.222 156.50.193.143 211.214.70.29 238.131.50.43