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

Region: Guangdong

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;14.121.199.244.			IN	A

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

;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Dec 20 05:05:42 CST 2019
;; MSG SIZE  rcvd: 118
Host info
Host 244.199.121.14.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 244.199.121.14.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
51.75.180.145 attackbots
Autoban   51.75.180.145 AUTH/CONNECT
2019-12-13 03:36:10
5.39.104.207 attackbotsspam
Autoban   5.39.104.207 AUTH/CONNECT
2019-12-13 04:08:37
95.213.177.122 attackspambots
Dec 12 18:39:38   TCP Attack: SRC=95.213.177.122 DST=[Masked] LEN=40 TOS=0x08 PREC=0x20 TTL=241  PROTO=TCP SPT=55976 DPT=8000 WINDOW=1024 RES=0x00 SYN URGP=0
2019-12-13 03:31:33
124.160.83.138 attack
Dec 12 20:57:39 server sshd\[8200\]: Invalid user bf3server from 124.160.83.138
Dec 12 20:57:39 server sshd\[8200\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.160.83.138 
Dec 12 20:57:41 server sshd\[8200\]: Failed password for invalid user bf3server from 124.160.83.138 port 43454 ssh2
Dec 12 21:22:00 server sshd\[15757\]: Invalid user katsuro from 124.160.83.138
Dec 12 21:22:00 server sshd\[15757\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.160.83.138 
...
2019-12-13 04:07:20
116.236.85.130 attack
$f2bV_matches
2019-12-13 03:56:28
201.140.209.33 attackbots
Unauthorized connection attempt detected from IP address 201.140.209.33 to port 445
2019-12-13 03:38:45
51.38.239.171 attackbots
Autoban   51.38.239.171 AUTH/CONNECT
2019-12-13 03:44:03
51.38.147.190 attack
Autoban   51.38.147.190 AUTH/CONNECT
2019-12-13 03:45:30
95.111.74.98 attackbotsspam
Dec 12 08:40:19 web9 sshd\[3489\]: Invalid user hell from 95.111.74.98
Dec 12 08:40:19 web9 sshd\[3489\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.111.74.98
Dec 12 08:40:20 web9 sshd\[3489\]: Failed password for invalid user hell from 95.111.74.98 port 52998 ssh2
Dec 12 08:46:09 web9 sshd\[4454\]: Invalid user jubb from 95.111.74.98
Dec 12 08:46:09 web9 sshd\[4454\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.111.74.98
2019-12-13 03:54:57
138.68.248.239 attackbots
2019-12-12T14:37:49Z - RDP login failed multiple times. (138.68.248.239)
2019-12-13 04:03:21
51.38.6.14 attackspambots
Autoban   51.38.6.14 AUTH/CONNECT
2019-12-13 03:43:21
50.236.77.190 attackspambots
Autoban   50.236.77.190 AUTH/CONNECT
2019-12-13 04:00:19
5.43.7.215 attack
Autoban   5.43.7.215 AUTH/CONNECT
2019-12-13 04:06:46
51.75.160.230 attackbots
Autoban   51.75.160.230 AUTH/CONNECT
2019-12-13 03:40:04
51.255.49.128 attackbots
Autoban   51.255.49.128 AUTH/CONNECT
2019-12-13 03:52:25

Recently Reported IPs

2a02:587:3c1f:e8cc:a0e9:20d4:991a:26c3 52.83.31.93 75.202.37.166 123.201.228.246
12.182.142.194 62.158.202.205 131.106.237.236 178.156.103.60
114.32.141.253 100.139.23.38 198.118.26.86 23.129.64.220
216.57.187.152 100.6.101.137 90.16.54.15 205.194.38.250
122.89.211.226 102.174.157.180 1.12.165.38 45.176.208.169