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: Korea (the Republic of)

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

;; QUESTION SECTION:
;99.150.27.94.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 13 02:49:03 CST 2025
;; MSG SIZE  rcvd: 105
Host info
94.27.150.99.in-addr.arpa domain name pointer ec2-99-150-27-94.ap-northeast-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
94.27.150.99.in-addr.arpa	name = ec2-99-150-27-94.ap-northeast-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
180.76.182.144 attackbotsspam
2020-04-17 20:21:50,241 fail2ban.actions        [22360]: NOTICE  [sshd] Ban 180.76.182.144
2020-04-17 21:00:57,890 fail2ban.actions        [22360]: NOTICE  [sshd] Ban 180.76.182.144
2020-04-18 14:46:38,305 fail2ban.actions        [22360]: NOTICE  [sshd] Ban 180.76.182.144
2020-04-18 15:22:44,867 fail2ban.actions        [22360]: NOTICE  [sshd] Ban 180.76.182.144
2020-04-18 16:05:42,077 fail2ban.actions        [22360]: NOTICE  [sshd] Ban 180.76.182.144
...
2020-04-19 01:28:17
128.199.116.10 attackspambots
Apr 18 15:43:05 piServer sshd[30669]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.116.10 
Apr 18 15:43:07 piServer sshd[30669]: Failed password for invalid user ftpuser from 128.199.116.10 port 49409 ssh2
Apr 18 15:52:50 piServer sshd[31347]: Failed password for root from 128.199.116.10 port 40046 ssh2
...
2020-04-19 01:36:31
123.31.32.150 attackspambots
SSH authentication failure x 6 reported by Fail2Ban
...
2020-04-19 01:36:55
113.173.48.166 attack
Invalid user user from 113.173.48.166 port 45832
2020-04-19 01:42:44
149.56.141.193 attackbotsspam
Apr 19 00:14:59 itv-usvr-01 sshd[959]: Invalid user ic from 149.56.141.193
2020-04-19 01:33:48
165.227.58.61 attackspam
Apr 18 16:54:52 sshgateway sshd\[27581\]: Invalid user xd from 165.227.58.61
Apr 18 16:54:52 sshgateway sshd\[27581\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.58.61
Apr 18 16:54:54 sshgateway sshd\[27581\]: Failed password for invalid user xd from 165.227.58.61 port 57054 ssh2
2020-04-19 01:31:15
171.227.175.107 attackspam
Invalid user qw from 171.227.175.107 port 56992
2020-04-19 01:16:08
111.93.31.227 attackspambots
SSH Brute Force
2020-04-19 01:11:04
93.14.78.71 attack
Invalid user git from 93.14.78.71 port 53040
2020-04-19 01:45:46
41.232.212.247 attackspam
Invalid user admin from 41.232.212.247 port 40513
2020-04-19 01:49:56
203.110.166.51 attackbotsspam
2020-04-18T12:02:54.244280abusebot-7.cloudsearch.cf sshd[15672]: Invalid user oq from 203.110.166.51 port 58524
2020-04-18T12:02:54.249843abusebot-7.cloudsearch.cf sshd[15672]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.110.166.51
2020-04-18T12:02:54.244280abusebot-7.cloudsearch.cf sshd[15672]: Invalid user oq from 203.110.166.51 port 58524
2020-04-18T12:02:56.629495abusebot-7.cloudsearch.cf sshd[15672]: Failed password for invalid user oq from 203.110.166.51 port 58524 ssh2
2020-04-18T12:09:24.989829abusebot-7.cloudsearch.cf sshd[16009]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.110.166.51  user=root
2020-04-18T12:09:26.576540abusebot-7.cloudsearch.cf sshd[16009]: Failed password for root from 203.110.166.51 port 58526 ssh2
2020-04-18T12:11:00.346689abusebot-7.cloudsearch.cf sshd[16094]: Invalid user test from 203.110.166.51 port 58528
...
2020-04-19 01:25:31
87.110.181.30 attackbots
Apr 18 17:27:38 124388 sshd[2332]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=87.110.181.30
Apr 18 17:27:38 124388 sshd[2332]: Invalid user sr from 87.110.181.30 port 34524
Apr 18 17:27:40 124388 sshd[2332]: Failed password for invalid user sr from 87.110.181.30 port 34524 ssh2
Apr 18 17:30:08 124388 sshd[2346]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=87.110.181.30  user=root
Apr 18 17:30:11 124388 sshd[2346]: Failed password for root from 87.110.181.30 port 34360 ssh2
2020-04-19 01:46:11
117.36.74.58 attack
2020-04-18T18:11:44.636847  sshd[15232]: Invalid user dandany from 117.36.74.58 port 37262
2020-04-18T18:11:44.649648  sshd[15232]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.36.74.58
2020-04-18T18:11:44.636847  sshd[15232]: Invalid user dandany from 117.36.74.58 port 37262
2020-04-18T18:11:46.992535  sshd[15232]: Failed password for invalid user dandany from 117.36.74.58 port 37262 ssh2
...
2020-04-19 01:41:36
95.85.38.127 attackbots
(sshd) Failed SSH login from 95.85.38.127 (NL/Netherlands/-): 5 in the last 3600 secs
2020-04-19 01:45:17
122.51.255.33 attack
leo_www
2020-04-19 01:19:05

Recently Reported IPs

25.247.126.81 187.116.113.184 47.232.89.235 26.84.60.190
202.65.212.189 99.221.159.43 146.153.39.144 63.70.69.132
147.59.183.114 211.40.232.37 86.180.238.19 180.42.105.31
243.193.116.112 217.96.158.51 152.42.1.134 47.5.34.69
244.238.70.199 26.232.239.56 46.4.101.50 221.56.55.130