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
219.140.118.129 attackspam
Unauthorized connection attempt detected from IP address 219.140.118.129 to port 123
2020-06-13 06:33:48
219.140.118.161 attackbots
Web Server Scan. RayID: 592cd913b8b39388, UA: Mozilla/4.066686748 Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1), Country: CN
2020-05-21 03:47:57
219.140.118.20 attackbotsspam
Unauthorized connection attempt detected from IP address 219.140.118.20 to port 80 [T]
2020-01-29 09:53:19
219.140.118.186 attackspambots
Unauthorized connection attempt detected from IP address 219.140.118.186 to port 9080
2019-12-31 09:07:47
219.140.118.230 attackbotsspam
Unauthorized connection attempt detected from IP address 219.140.118.230 to port 3128
2019-12-31 08:19:35
219.140.118.171 attackbotsspam
Unauthorized connection attempt detected from IP address 219.140.118.171 to port 8081
2019-12-31 06:37:51
219.140.118.241 attackbots
The IP has triggered Cloudflare WAF. CF-Ray: 5415933c8f89e50a | WAF_Rule_ID: 1025440 | 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 (iPad; CPU OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1 | CF_DC: LAX. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-08 07:03:12
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 219.140.118.45
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 44401
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;219.140.118.45.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 16:48:22 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 45.118.140.219.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 45.118.140.219.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
139.59.76.85 attack
Automatic report - XMLRPC Attack
2019-12-10 04:18:01
51.91.251.20 attack
sshd jail - ssh hack attempt
2019-12-10 04:24:39
212.44.65.22 attack
Dec  9 20:24:01 legacy sshd[26633]: Failed password for root from 212.44.65.22 port 63080 ssh2
Dec  9 20:29:41 legacy sshd[26826]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.44.65.22
Dec  9 20:29:44 legacy sshd[26826]: Failed password for invalid user webmaster from 212.44.65.22 port 61588 ssh2
...
2019-12-10 03:50:16
185.7.95.79 attack
firewall-block, port(s): 8080/tcp
2019-12-10 04:20:00
103.210.31.118 attackbots
Port 1433 Scan
2019-12-10 03:52:26
201.156.38.190 attack
Probing for vulnerable services
2019-12-10 03:59:34
112.133.251.51 attackbotsspam
Unauthorized connection attempt from IP address 112.133.251.51 on Port 445(SMB)
2019-12-10 04:08:57
219.93.20.155 attackbots
Dec  9 17:40:19 ws12vmsma01 sshd[38668]: Failed password for invalid user test from 219.93.20.155 port 43119 ssh2
Dec  9 17:47:36 ws12vmsma01 sshd[39740]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=219.93.20.155  user=root
Dec  9 17:47:38 ws12vmsma01 sshd[39740]: Failed password for root from 219.93.20.155 port 49470 ssh2
...
2019-12-10 03:53:57
92.52.196.10 attackbots
Unauthorized connection attempt from IP address 92.52.196.10 on Port 445(SMB)
2019-12-10 03:51:59
41.131.119.107 attackbots
2019-12-09T19:50:44.387314shield sshd\[22092\]: Invalid user mysql from 41.131.119.107 port 48645
2019-12-09T19:50:44.393446shield sshd\[22092\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.131.119.107
2019-12-09T19:50:46.104336shield sshd\[22092\]: Failed password for invalid user mysql from 41.131.119.107 port 48645 ssh2
2019-12-09T19:56:33.528148shield sshd\[23206\]: Invalid user systaad from 41.131.119.107 port 40403
2019-12-09T19:56:33.533534shield sshd\[23206\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.131.119.107
2019-12-10 04:03:30
149.56.23.154 attackbotsspam
Dec  9 20:31:22 sso sshd[3359]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.56.23.154
Dec  9 20:31:24 sso sshd[3359]: Failed password for invalid user wittich from 149.56.23.154 port 33700 ssh2
...
2019-12-10 04:12:47
77.247.109.50 attackspam
Portscan or hack attempt detected by psad/fwsnort
2019-12-10 03:50:04
94.229.66.131 attackspambots
$f2bV_matches_ltvn
2019-12-10 03:58:31
182.74.169.98 attack
Oct 31 19:44:20 odroid64 sshd\[4677\]: User root from 182.74.169.98 not allowed because not listed in AllowUsers
Oct 31 19:44:20 odroid64 sshd\[4677\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.74.169.98  user=root
...
2019-12-10 04:04:00
93.174.95.106 attack
Fail2Ban Ban Triggered
2019-12-10 03:51:27

Recently Reported IPs

219.140.118.56 219.140.118.78 219.140.119.117 219.140.119.163
219.140.119.233 219.140.119.204 219.140.119.230 219.143.174.0
219.140.119.143 219.143.174.113 219.140.119.57 219.143.174.131
219.142.86.34 219.140.119.68 219.143.174.145 219.142.227.62
219.143.174.20 219.143.174.19 219.143.174.219 219.143.174.187