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: Shanghai

Region: Shanghai

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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 113.250.162.22
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1729
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;113.250.162.22.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Aug 27 21:51:56 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 22.162.250.113.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 22.162.250.113.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
139.59.2.181 attackbotsspam
139.59.2.181 - - [03/Jan/2020:13:08:44 +0000] "POST /wp-login.php HTTP/1.1" 200 6393 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
139.59.2.181 - - [03/Jan/2020:13:08:46 +0000] "POST /xmlrpc.php HTTP/1.1" 200 403 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-01-03 21:19:25
132.148.129.180 attackbots
Automatically reported by fail2ban report script (powermetal)
2020-01-03 21:17:26
36.75.141.143 attack
Honeypot attack, port: 445, PTR: PTR record not found
2020-01-03 21:01:28
107.170.249.243 attack
Jan  3 14:03:17 legacy sshd[17590]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.170.249.243
Jan  3 14:03:20 legacy sshd[17590]: Failed password for invalid user zy from 107.170.249.243 port 44496 ssh2
Jan  3 14:08:39 legacy sshd[17943]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.170.249.243
...
2020-01-03 21:22:48
134.175.7.36 attack
Jan  3 02:15:24 hanapaa sshd\[21915\]: Invalid user hms from 134.175.7.36
Jan  3 02:15:25 hanapaa sshd\[21915\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.7.36
Jan  3 02:15:27 hanapaa sshd\[21915\]: Failed password for invalid user hms from 134.175.7.36 port 49910 ssh2
Jan  3 02:17:23 hanapaa sshd\[22091\]: Invalid user faxserver from 134.175.7.36
Jan  3 02:17:23 hanapaa sshd\[22091\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.7.36
2020-01-03 20:57:20
5.89.64.166 attack
Jan  3 10:08:20 marvibiene sshd[36649]: Invalid user no-reply from 5.89.64.166 port 34900
Jan  3 10:08:20 marvibiene sshd[36649]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.89.64.166
Jan  3 10:08:20 marvibiene sshd[36649]: Invalid user no-reply from 5.89.64.166 port 34900
Jan  3 10:08:22 marvibiene sshd[36649]: Failed password for invalid user no-reply from 5.89.64.166 port 34900 ssh2
...
2020-01-03 20:53:33
47.206.80.165 attackspam
20/1/3@08:08:50: FAIL: Alarm-Network address from=47.206.80.165
...
2020-01-03 21:16:58
182.184.61.107 attackbotsspam
Automatic report - Banned IP Access
2020-01-03 21:35:23
79.58.50.145 attackbotsspam
sshd jail - ssh hack attempt
2020-01-03 21:20:10
182.61.175.96 attack
Jan  3 03:21:52 wbs sshd\[17847\]: Invalid user ftp from 182.61.175.96
Jan  3 03:21:52 wbs sshd\[17847\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.175.96
Jan  3 03:21:54 wbs sshd\[17847\]: Failed password for invalid user ftp from 182.61.175.96 port 52876 ssh2
Jan  3 03:27:45 wbs sshd\[18375\]: Invalid user xty from 182.61.175.96
Jan  3 03:27:45 wbs sshd\[18375\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.175.96
2020-01-03 21:30:16
92.50.249.92 attackbots
Jan  3 13:08:38 ws26vmsma01 sshd[110463]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.50.249.92
Jan  3 13:08:40 ws26vmsma01 sshd[110463]: Failed password for invalid user iinstall from 92.50.249.92 port 38448 ssh2
...
2020-01-03 21:22:08
31.192.230.171 attackbotsspam
(sshd) Failed SSH login from 31.192.230.171 (SE/Sweden/31-192-230-171-static.glesys.net): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Jan  3 09:54:28 svr sshd[3345553]: Invalid user system from 31.192.230.171 port 59726
Jan  3 09:54:30 svr sshd[3345553]: Failed password for invalid user system from 31.192.230.171 port 59726 ssh2
Jan  3 10:07:24 svr sshd[3385903]: Invalid user userftp from 31.192.230.171 port 41716
Jan  3 10:07:26 svr sshd[3385903]: Failed password for invalid user userftp from 31.192.230.171 port 41716 ssh2
Jan  3 10:10:40 svr sshd[3395897]: Invalid user django from 31.192.230.171 port 56830
2020-01-03 21:33:58
125.27.78.199 attackbotsspam
Honeypot attack, port: 445, PTR: node-fk7.pool-125-27.dynamic.totinternet.net.
2020-01-03 20:56:28
37.191.244.133 attackspam
Jan  3 14:05:41 legacy sshd[17693]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.191.244.133
Jan  3 14:05:43 legacy sshd[17693]: Failed password for invalid user chipmast from 37.191.244.133 port 47380 ssh2
Jan  3 14:08:55 legacy sshd[17972]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.191.244.133
...
2020-01-03 21:12:23
1.236.151.31 attackbots
SSH Brute-Force reported by Fail2Ban
2020-01-03 21:34:54

Recently Reported IPs

119.8.36.109 122.246.0.154 45.142.154.27 10.177.183.81
52.195.190.75 35.77.4.87 86.97.133.52 182.84.83.7
182.84.83.13 182.84.83.37 182.84.83.71 182.84.83.228
182.84.83.137 182.84.83.189 182.84.83.148 182.84.83.196
113.85.110.164 146.190.116.130 113.215.188.113 168.80.19.178