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: United States

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

;; QUESTION SECTION:
;132.139.15.22.			IN	A

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

;; Query time: 33 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Apr 01 21:55:56 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 22.15.139.132.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
server can't find 132.139.15.22.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
174.76.222.31 attackspam
3389BruteforceFW21
2019-08-07 19:07:50
104.149.191.178 attackspam
GET /xmlrpc.php?rsd HTTP/1.1 403 292 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36
2019-08-07 18:34:40
54.36.150.183 attackspambots
Automatic report - Banned IP Access
2019-08-07 18:43:27
218.92.0.207 attack
SSH Brute-Force reported by Fail2Ban
2019-08-07 19:18:18
160.120.50.154 attack
GET /wp-login.php HTTP/1.1 403 292 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101 Firefox/40.1
2019-08-07 18:14:06
101.109.83.140 attack
2019-08-07T10:38:18.113911abusebot-5.cloudsearch.cf sshd\[8722\]: Invalid user qa from 101.109.83.140 port 44620
2019-08-07 18:40:59
37.120.150.157 attackbots
Spam mails sent to address hacked/leaked from Nexus Mods in July 2013
2019-08-07 18:43:43
49.88.112.72 attack
Aug  7 13:01:16 * sshd[32155]: Failed password for root from 49.88.112.72 port 63900 ssh2
Aug  7 13:01:18 * sshd[32155]: Failed password for root from 49.88.112.72 port 63900 ssh2
2019-08-07 19:05:38
171.242.32.112 attackbots
SSH Brute-Force reported by Fail2Ban
2019-08-07 18:53:10
107.170.18.163 attackbots
$f2bV_matches
2019-08-07 18:44:10
117.239.128.188 attack
[portscan] tcp/23 [TELNET]
*(RWIN=3795)(08071017)
2019-08-07 19:16:51
112.221.179.133 attack
Invalid user updater from 112.221.179.133 port 39153
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.221.179.133
Failed password for invalid user updater from 112.221.179.133 port 39153 ssh2
Invalid user catering from 112.221.179.133 port 36601
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.221.179.133
2019-08-07 18:18:30
185.220.101.50 attackbots
2019-08-07T10:30:57.399008abusebot-3.cloudsearch.cf sshd\[16637\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.220.101.50  user=root
2019-08-07 18:41:36
202.85.220.177 attackbots
Aug  7 06:57:41 sshgateway sshd\[860\]: Invalid user deploy from 202.85.220.177
Aug  7 06:57:41 sshgateway sshd\[860\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.85.220.177
Aug  7 06:57:44 sshgateway sshd\[860\]: Failed password for invalid user deploy from 202.85.220.177 port 39080 ssh2
2019-08-07 19:06:02
185.208.209.7 attackspambots
Port scan on 4 port(s): 26917 43080 50953 62264
2019-08-07 19:06:17

Recently Reported IPs

62.189.85.33 78.112.224.70 18.178.149.222 123.220.94.127
138.200.117.79 8.131.97.122 20.169.104.93 39.155.177.200
156.6.191.31 80.59.33.19 239.206.102.151 221.47.34.195
132.131.58.250 76.165.66.98 20.104.33.10 164.105.201.61
226.43.105.182 121.130.214.126 143.247.115.250 222.135.199.42