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

;; QUESTION SECTION:
;124.90.52.159.			IN	A

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

;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 21 06:13:41 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 159.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 159.52.90.124.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
150.95.54.141 attackspam
Brute force attempt
2019-06-24 09:52:23
103.39.134.126 attackspam
Received: from namchimachine.org.uk (namchimachine.org.uk. [103.39.134.126])
        by mx.google.com with ESMTP id k4si7545384pgq.293.2019.06.23.10.25.12
        for ;
        Sun, 23 Jun 2019 10:25:12 -0700 (PDT)
Received-SPF: neutral (google.com: 103.39.134.126 is neither permitted nor denied by best guess record for domain of waat@iclasse.mydns.jp5) client-ip=103.39.134.126;
Authentication-Results: mx.google.com;
       dkim=neutral (body hash did not verify) header.i=@gmail.com header.s=gamma header.b=F87jySDZ;
       spf=neutral (google.com: 103.39.134.126 is neither permitted nor denied by best guess record for domain of waat@iclasse.mydns.jp5) smtp.mailfrom=waat@iclasse.mydns.jp5;
       dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=se.edu
Received: from namchimachine.org.uk (127.0.0.1) by namchimachine.org.uk id 3928052589459 for ; Mon, 1 Oct 2018 09:38:26 -0400 (envelope-from )
2019-06-24 09:36:41
159.65.96.102 attackbots
Automatic report - Web App Attack
2019-06-24 09:37:44
178.128.57.53 attackspam
scan z
2019-06-24 09:35:36
205.185.214.99 attackbotsspam
NAME : SECUREDCONNECTIVITY-205-185-209-0-24 CIDR : 205.185.209.0/24 | STATUS : 200 ROBOT {Looking for resource vulnerabilities} DDoS Attack USA - Texas - block certain countries :) IP: 205.185.214.99  Denial-of-Service Attack (DoS) Detected and Blocked by ADMIN  - data recovery https://help-dysk.pl
2019-06-24 10:16:28
118.118.153.115 attackspam
Invalid user support from 118.118.153.115 port 39510
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.118.153.115
Failed password for invalid user support from 118.118.153.115 port 39510 ssh2
Invalid user cisco from 118.118.153.115 port 40267
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.118.153.115
2019-06-24 09:47:35
62.102.148.69 attack
detected by Fail2Ban
2019-06-24 10:05:31
197.53.78.202 attackbotsspam
" "
2019-06-24 09:42:54
74.82.47.56 attack
Portscan or hack attempt detected by psad/fwsnort
2019-06-24 10:17:22
177.67.165.35 attackspambots
Jun 23 17:01:07 web1 postfix/smtpd[27735]: warning: unknown[177.67.165.35]: SASL PLAIN authentication failed: authentication failure
...
2019-06-24 10:11:43
119.3.247.96 attackbots
Malicious brute force vulnerability hacking attacks
2019-06-24 10:18:22
205.186.161.61 attackspam
205.186.161.61 - - \[23/Jun/2019:21:57:18 +0200\] "GET /wp-login.php HTTP/1.1" 200 1301 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
205.186.161.61 - - \[23/Jun/2019:21:57:18 +0200\] "POST /wp-login.php HTTP/1.1" 200 1704 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
205.186.161.61 - - \[23/Jun/2019:21:57:19 +0200\] "GET /wp-login.php HTTP/1.1" 200 1301 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
205.186.161.61 - - \[23/Jun/2019:21:57:19 +0200\] "POST /wp-login.php HTTP/1.1" 200 1684 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
205.186.161.61 - - \[23/Jun/2019:21:57:19 +0200\] "GET /wp-login.php HTTP/1.1" 200 1301 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
205.186.161.61 - - \[23/Jun/2019:21:57:20 +0200\] "POST /wp-login.php HTTP/1.1" 200 1688 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:6
2019-06-24 09:33:38
84.1.244.52 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2019-06-24 09:51:44
123.188.18.154 attackspam
" "
2019-06-24 10:15:08
168.196.148.195 attackbots
23.06.2019 21:55:46 - Login Fail on hMailserver 
Detected by ELinOX-hMail-A2F
2019-06-24 09:54:59

Recently Reported IPs

124.90.52.120 124.90.52.211 124.90.53.114 124.90.53.111
124.90.53.145 124.90.53.216 124.90.53.247 124.90.53.29
124.90.54.165 124.90.55.172 124.90.54.20 124.90.55.231
124.92.182.204 124.94.50.3 124.95.244.153 125.105.186.171
125.105.63.43 125.106.133.133 125.106.133.97 125.106.252.35