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:
IP Type Details Datetime
124.90.52.214 attackspambots
Web Server Scan. RayID: 58f1c6a568b293c4, UA: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.90 Safari/537.36, Country: CN
2020-05-21 03:59:29
124.90.52.158 attackbots
Fail2Ban Ban Triggered
2020-04-16 14:48:59
124.90.52.243 attackspam
Unauthorized connection attempt detected from IP address 124.90.52.243 to port 8081 [J]
2020-01-26 05:00:54
124.90.52.189 attack
Unauthorized connection attempt detected from IP address 124.90.52.189 to port 82 [T]
2020-01-10 08:46:03
124.90.52.114 attackspambots
Unauthorized connection attempt detected from IP address 124.90.52.114 to port 3128
2019-12-31 07:33:14
124.90.52.137 attackbots
The IP has triggered Cloudflare WAF. CF-Ray: 5414e5dd78c695f3 | WAF_Rule_ID: 1112824 | WAF_Kind: firewall | CF_Action: challenge | Country: CN | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: img.skk.moe | User-Agent: Mozilla/5.0 (Linux; U; Android 4.3; en-us; SM-N900T Build/JSS15J) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30 | CF_DC: SJC. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-08 04:31:03
124.90.52.118 attack
The IP has triggered Cloudflare WAF. CF-Ray: 5416098bfab493ac | WAF_Rule_ID: 3b40188685924a32bf11d40edea05a27 | WAF_Kind: firewall | CF_Action: challenge | Country: CN | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: d.skk.moe | User-Agent: Mozilla/5.082584686 Mozilla/5.0 (iPhone; CPU iPhone OS 11_4_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/11.0 Mobile/15E148 Safari/604.1 | CF_DC: SJC. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-08 04:09:19
124.90.52.86 attackbotsspam
The IP has triggered Cloudflare WAF. CF-Ray: 541380e48a61ed3b | WAF_Rule_ID: 3b40188685924a32bf11d40edea05a27 | WAF_Kind: firewall | CF_Action: challenge | Country: CN | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: disqus.skk.moe | User-Agent: Mozilla/5.064213590 Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 | CF_DC: SJC. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-08 01:54:23
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 124.90.52.18
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 52520
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;124.90.52.18.			IN	A

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

;; Query time: 22 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 00:37:05 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 18.52.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 18.52.90.124.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
117.102.105.203 attackbotsspam
Nov  3 08:47:54 ip-172-31-62-245 sshd\[18251\]: Invalid user 12345 from 117.102.105.203\
Nov  3 08:47:56 ip-172-31-62-245 sshd\[18251\]: Failed password for invalid user 12345 from 117.102.105.203 port 58060 ssh2\
Nov  3 08:52:30 ip-172-31-62-245 sshd\[18273\]: Invalid user 1z2x3c4v5b6n from 117.102.105.203\
Nov  3 08:52:32 ip-172-31-62-245 sshd\[18273\]: Failed password for invalid user 1z2x3c4v5b6n from 117.102.105.203 port 40990 ssh2\
Nov  3 08:57:04 ip-172-31-62-245 sshd\[18342\]: Invalid user wuxueyins20sys@126 from 117.102.105.203\
2019-11-03 17:34:01
101.36.151.65 attackspam
Nov  3 02:51:15 firewall sshd[24166]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.36.151.65
Nov  3 02:51:15 firewall sshd[24166]: Invalid user ftptest from 101.36.151.65
Nov  3 02:51:17 firewall sshd[24166]: Failed password for invalid user ftptest from 101.36.151.65 port 44982 ssh2
...
2019-11-03 17:40:29
187.131.211.5 attackbotsspam
Nov  3 01:47:01 TORMINT sshd\[31622\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.131.211.5  user=root
Nov  3 01:47:03 TORMINT sshd\[31622\]: Failed password for root from 187.131.211.5 port 44038 ssh2
Nov  3 01:50:37 TORMINT sshd\[31801\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.131.211.5  user=root
...
2019-11-03 18:07:32
77.137.89.16 attackbots
Unauthorised access (Nov  3) SRC=77.137.89.16 LEN=52 TTL=111 ID=7722 DF TCP DPT=445 WINDOW=8192 SYN 
Unauthorised access (Nov  3) SRC=77.137.89.16 LEN=52 TTL=111 ID=29196 DF TCP DPT=445 WINDOW=8192 SYN 
Unauthorised access (Nov  3) SRC=77.137.89.16 LEN=52 TTL=111 ID=17004 DF TCP DPT=445 WINDOW=8192 SYN
2019-11-03 17:42:44
192.42.116.22 attackspambots
Automatic report - XMLRPC Attack
2019-11-03 17:55:01
207.46.13.100 attack
Automatic report - Banned IP Access
2019-11-03 18:05:04
209.17.96.42 attackspam
Connection by 209.17.96.42 on port: 4567 got caught by honeypot at 11/3/2019 4:50:52 AM
2019-11-03 17:59:33
202.44.250.118 attackbotsspam
scan z
2019-11-03 18:11:42
94.23.215.90 attack
Nov  3 10:54:31 dedicated sshd[13179]: Failed password for root from 94.23.215.90 port 56772 ssh2
Nov  3 10:58:01 dedicated sshd[13732]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.23.215.90  user=root
Nov  3 10:58:03 dedicated sshd[13732]: Failed password for root from 94.23.215.90 port 56896 ssh2
Nov  3 10:58:01 dedicated sshd[13732]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.23.215.90  user=root
Nov  3 10:58:03 dedicated sshd[13732]: Failed password for root from 94.23.215.90 port 56896 ssh2
2019-11-03 18:13:56
111.246.145.177 attackbots
23/tcp
[2019-11-03]1pkt
2019-11-03 18:06:48
185.143.221.186 attackbots
185.143.221.186 was recorded 10 times by 4 hosts attempting to connect to the following ports: 3347,32733,55339,43890,55745,55429,32409,3215,3159,55543. Incident counter (4h, 24h, all-time): 10, 84, 195
2019-11-03 18:12:14
186.220.216.139 attack
DATE:2019-11-03 06:50:34, IP:186.220.216.139, PORT:telnet Telnet brute force auth on honeypot server (honey-neo-dc)
2019-11-03 18:09:43
60.191.82.92 attackspambots
03.11.2019 07:43:05 Connection to port 8088 blocked by firewall
2019-11-03 17:54:14
167.99.65.138 attackspam
2019-11-03T07:49:42.427463shield sshd\[23712\]: Invalid user qa from 167.99.65.138 port 57416
2019-11-03T07:49:42.431765shield sshd\[23712\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.65.138
2019-11-03T07:49:43.942159shield sshd\[23712\]: Failed password for invalid user qa from 167.99.65.138 port 57416 ssh2
2019-11-03T07:54:00.656400shield sshd\[25147\]: Invalid user Sun@123 from 167.99.65.138 port 38946
2019-11-03T07:54:00.662351shield sshd\[25147\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.65.138
2019-11-03 18:04:02
185.43.211.234 attackspam
11/03/2019-06:51:26.796229 185.43.211.234 Protocol: 6 ET POLICY Cleartext WordPress Login
2019-11-03 17:35:45

Recently Reported IPs

117.64.227.38 124.90.52.162 124.90.52.186 124.90.52.180
124.90.52.206 124.90.52.208 124.90.52.190 124.90.52.232
124.90.52.220 117.64.227.47 124.90.52.240 124.90.52.46
124.90.52.250 124.90.52.42 124.90.52.48 124.90.52.52
124.90.52.66 124.90.52.6 124.90.52.69 124.90.52.74