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

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

;; QUESTION SECTION:
;114.99.201.1.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 05 03:44:22 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 1.201.99.114.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 1.201.99.114.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
111.207.49.186 attackbotsspam
Jun 30 10:17:07 pi sshd[2699]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.207.49.186 
Jun 30 10:17:09 pi sshd[2699]: Failed password for invalid user andrey from 111.207.49.186 port 60648 ssh2
2020-07-02 01:33:05
195.54.160.180 attackspambots
2020-06-30T20:39:43.211369abusebot-7.cloudsearch.cf sshd[10214]: Invalid user shell from 195.54.160.180 port 35165
2020-06-30T20:39:43.342528abusebot-7.cloudsearch.cf sshd[10214]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.54.160.180
2020-06-30T20:39:43.211369abusebot-7.cloudsearch.cf sshd[10214]: Invalid user shell from 195.54.160.180 port 35165
2020-06-30T20:39:44.759734abusebot-7.cloudsearch.cf sshd[10214]: Failed password for invalid user shell from 195.54.160.180 port 35165 ssh2
2020-06-30T20:39:45.969522abusebot-7.cloudsearch.cf sshd[10216]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.54.160.180  user=sync
2020-06-30T20:39:48.330024abusebot-7.cloudsearch.cf sshd[10216]: Failed password for sync from 195.54.160.180 port 37335 ssh2
2020-06-30T20:39:49.380706abusebot-7.cloudsearch.cf sshd[10218]: Invalid user username from 195.54.160.180 port 40135
...
2020-07-02 01:35:10
194.26.29.32 attack
Jun 30 22:08:20 debian-2gb-nbg1-2 kernel: \[15806337.187279\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=194.26.29.32 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=12769 PROTO=TCP SPT=43979 DPT=4356 WINDOW=1024 RES=0x00 SYN URGP=0
2020-07-02 01:11:53
106.124.139.161 attackspambots
Jun 30 20:18:53 game-panel sshd[18583]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.124.139.161
Jun 30 20:18:55 game-panel sshd[18583]: Failed password for invalid user vbox from 106.124.139.161 port 58898 ssh2
Jun 30 20:22:09 game-panel sshd[18743]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.124.139.161
2020-07-02 01:02:57
212.70.149.18 attackbotsspam
Jun 30 22:12:50 mail postfix/smtpd\[15344\]: warning: unknown\[212.70.149.18\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Jun 30 22:43:14 mail postfix/smtpd\[16926\]: warning: unknown\[212.70.149.18\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Jun 30 22:43:56 mail postfix/smtpd\[16927\]: warning: unknown\[212.70.149.18\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Jun 30 22:44:39 mail postfix/smtpd\[16926\]: warning: unknown\[212.70.149.18\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
2020-07-02 01:42:46
193.228.108.122 attackbots
Bruteforce detected by fail2ban
2020-07-02 01:23:23
77.42.91.178 attackspambots
port 23
2020-07-02 01:00:17
51.75.202.218 attack
Jun 30 22:15:33 rancher-0 sshd[62218]: Invalid user martyn from 51.75.202.218 port 36852
...
2020-07-02 00:58:58
5.182.210.228 attackbots
Unauthorized SSH login attempts
2020-07-02 01:03:32
46.38.150.203 attackbots
Jun 30 21:55:04 s1 postfix/submission/smtpd\[696\]: warning: unknown\[46.38.150.203\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 30 21:55:37 s1 postfix/submission/smtpd\[32393\]: warning: unknown\[46.38.150.203\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 30 21:56:09 s1 postfix/submission/smtpd\[695\]: warning: unknown\[46.38.150.203\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 30 21:56:42 s1 postfix/submission/smtpd\[696\]: warning: unknown\[46.38.150.203\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 30 21:57:15 s1 postfix/submission/smtpd\[696\]: warning: unknown\[46.38.150.203\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 30 21:57:48 s1 postfix/submission/smtpd\[32393\]: warning: unknown\[46.38.150.203\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 30 21:58:20 s1 postfix/submission/smtpd\[4847\]: warning: unknown\[46.38.150.203\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 30 21:58:53 s1 postfix/submission/smtpd\[4847\]: warning: unknown\[46.38.150.
2020-07-02 01:33:39
106.13.42.140 attackbots
Invalid user deploy from 106.13.42.140 port 55010
2020-07-02 01:55:27
144.21.71.72 attack
Unauthorized connection attempt detected from IP address 144.21.71.72 to port 8080 [T]
2020-07-02 01:02:36
185.220.101.145 attackbots
Unauthorized connection attempt detected from IP address 185.220.101.145 to port 7001
2020-07-02 01:45:13
117.232.67.150 attackbots
Unauthorized connection attempt: SRC=117.232.67.150
...
2020-07-02 01:18:20
131.100.139.153 attack
 TCP (SYN) 131.100.139.153:61474 -> port 23, len 40
2020-07-02 01:49:39

Recently Reported IPs

114.99.200.91 114.99.201.105 114.99.201.132 114.99.201.128
114.99.201.106 114.99.201.136 114.99.201.157 114.99.201.16
114.99.201.182 114.99.201.162 114.99.201.167 115.237.81.176
114.99.21.84 114.99.21.88 114.99.21.91 114.99.21.86
114.99.21.93 114.99.21.9 114.99.21.94 114.99.21.96