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:
IP Type Details Datetime
124.90.55.101 attackspam
Unauthorized connection attempt detected from IP address 124.90.55.101 to port 8118 [J]
2020-01-19 16:02:36
124.90.55.88 attackbots
Unauthorized connection attempt detected from IP address 124.90.55.88 to port 80 [J]
2020-01-14 15:18:47
124.90.55.178 attack
Unauthorized connection attempt detected from IP address 124.90.55.178 to port 3129 [T]
2020-01-07 01:17:20
124.90.55.150 attack
Unauthorized connection attempt detected from IP address 124.90.55.150 to port 8118
2020-01-04 08:00:11
124.90.55.179 attack
Fail2Ban Ban Triggered
2019-12-29 14:05:25
124.90.55.2 attackbots
The IP has triggered Cloudflare WAF. CF-Ray: 5433fc593db0285c | WAF_Rule_ID: 3b40188685924a32bf11d40edea05a27 | WAF_Kind: firewall | CF_Action: drop | Country: CN | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: ip.skk.moe | User-Agent: Mozilla/5.084743666 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/17.17134 | CF_DC: SJC. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-12 05:37:13
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 124.90.55.20
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 39081
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;124.90.55.20.			IN	A

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

;; Query time: 22 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 14:25:37 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 20.55.90.124.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 20.55.90.124.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
218.92.0.145 attackspam
Nov 25 06:10:49 nextcloud sshd\[10511\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.145  user=root
Nov 25 06:10:50 nextcloud sshd\[10511\]: Failed password for root from 218.92.0.145 port 12536 ssh2
Nov 25 06:10:54 nextcloud sshd\[10511\]: Failed password for root from 218.92.0.145 port 12536 ssh2
...
2019-11-25 13:18:44
115.238.48.116 attack
Unauthorized SSH login attempts
2019-11-25 13:21:12
218.92.0.139 attackspam
Nov 25 06:11:53 odroid64 sshd\[17303\]: User root from 218.92.0.139 not allowed because not listed in AllowUsers
Nov 25 06:11:54 odroid64 sshd\[17303\]: Failed none for invalid user root from 218.92.0.139 port 28247 ssh2
...
2019-11-25 13:13:07
125.75.128.231 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-25 09:29:10
222.186.190.2 attackbots
SSH Brute Force, server-1 sshd[7461]: Failed password for root from 222.186.190.2 port 37244 ssh2
2019-11-25 13:26:24
210.72.24.20 attackbotsspam
Nov 25 05:51:54 fr01 sshd[14026]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.72.24.20  user=mysql
Nov 25 05:51:56 fr01 sshd[14026]: Failed password for mysql from 210.72.24.20 port 52928 ssh2
Nov 25 05:59:15 fr01 sshd[15305]: Invalid user mihoko from 210.72.24.20
...
2019-11-25 13:19:08
103.24.61.245 attackbotsspam
PHI,WP GET /wp-login.php
2019-11-25 13:14:06
112.85.42.175 attackbotsspam
Nov 25 02:10:59 firewall sshd[18307]: Failed password for root from 112.85.42.175 port 59495 ssh2
Nov 25 02:11:03 firewall sshd[18307]: Failed password for root from 112.85.42.175 port 59495 ssh2
Nov 25 02:11:06 firewall sshd[18307]: Failed password for root from 112.85.42.175 port 59495 ssh2
...
2019-11-25 13:16:50
73.221.250.221 attackbots
73.221.250.221 was recorded 5 times by 1 hosts attempting to connect to the following ports: 51413. Incident counter (4h, 24h, all-time): 5, 5, 5
2019-11-25 13:15:06
122.5.46.22 attack
Nov 25 05:33:53 Ubuntu-1404-trusty-64-minimal sshd\[21000\]: Invalid user mysql from 122.5.46.22
Nov 25 05:33:53 Ubuntu-1404-trusty-64-minimal sshd\[21000\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.5.46.22
Nov 25 05:33:55 Ubuntu-1404-trusty-64-minimal sshd\[21000\]: Failed password for invalid user mysql from 122.5.46.22 port 38250 ssh2
Nov 25 05:59:04 Ubuntu-1404-trusty-64-minimal sshd\[8368\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.5.46.22  user=root
Nov 25 05:59:06 Ubuntu-1404-trusty-64-minimal sshd\[8368\]: Failed password for root from 122.5.46.22 port 52730 ssh2
2019-11-25 13:27:42
125.227.164.62 attack
Nov 25 07:22:17 server sshd\[13184\]: Invalid user server from 125.227.164.62
Nov 25 07:22:17 server sshd\[13184\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125-227-164-62.hinet-ip.hinet.net 
Nov 25 07:22:19 server sshd\[13184\]: Failed password for invalid user server from 125.227.164.62 port 39708 ssh2
Nov 25 07:59:18 server sshd\[22185\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125-227-164-62.hinet-ip.hinet.net  user=root
Nov 25 07:59:20 server sshd\[22185\]: Failed password for root from 125.227.164.62 port 36814 ssh2
...
2019-11-25 13:16:19
151.80.254.73 attack
2019-11-25T04:52:35.353433shield sshd\[18411\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=151.80.254.73  user=root
2019-11-25T04:52:37.696090shield sshd\[18411\]: Failed password for root from 151.80.254.73 port 47816 ssh2
2019-11-25T04:59:22.834331shield sshd\[20018\]: Invalid user admin from 151.80.254.73 port 55622
2019-11-25T04:59:22.838462shield sshd\[20018\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=151.80.254.73
2019-11-25T04:59:25.055486shield sshd\[20018\]: Failed password for invalid user admin from 151.80.254.73 port 55622 ssh2
2019-11-25 13:13:31
222.186.190.92 attack
2019-11-25T05:09:55.829770abusebot-6.cloudsearch.cf sshd\[21812\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.190.92  user=root
2019-11-25 13:19:28
118.70.233.163 attack
Nov 25 01:02:00 venus sshd\[22418\]: Invalid user install from 118.70.233.163 port 60832
Nov 25 01:02:00 venus sshd\[22418\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.70.233.163
Nov 25 01:02:02 venus sshd\[22418\]: Failed password for invalid user install from 118.70.233.163 port 60832 ssh2
...
2019-11-25 09:27:50
182.61.108.215 attack
Nov 25 06:35:27 vibhu-HP-Z238-Microtower-Workstation sshd\[25598\]: Invalid user apache from 182.61.108.215
Nov 25 06:35:27 vibhu-HP-Z238-Microtower-Workstation sshd\[25598\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.108.215
Nov 25 06:35:30 vibhu-HP-Z238-Microtower-Workstation sshd\[25598\]: Failed password for invalid user apache from 182.61.108.215 port 41366 ssh2
Nov 25 06:42:23 vibhu-HP-Z238-Microtower-Workstation sshd\[25917\]: Invalid user bakow from 182.61.108.215
Nov 25 06:42:23 vibhu-HP-Z238-Microtower-Workstation sshd\[25917\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.108.215
...
2019-11-25 09:27:31

Recently Reported IPs

124.90.55.42 124.90.55.71 124.91.227.121 124.90.55.62
124.94.225.192 124.94.237.138 125.105.188.208 124.92.180.168
125.104.96.18 125.105.212.14 124.92.78.241 125.105.209.240
125.105.60.47 125.105.77.184 125.106.30.153 125.105.38.27
125.106.40.174 125.106.108.208 125.106.84.117 125.106.71.161