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

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

;; QUESTION SECTION:
;132.64.199.12.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 01 00:05:45 CST 2025
;; MSG SIZE  rcvd: 106
Host info
12.199.64.132.in-addr.arpa domain name pointer huji-132-64-199-12.xt.huji.ac.il.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
12.199.64.132.in-addr.arpa	name = huji-132-64-199-12.xt.huji.ac.il.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
78.46.232.98 attackbots
WordPress brute force
2019-09-29 09:11:55
219.105.120.15 attack
19/9/28@23:56:28: FAIL: IoT-Telnet address from=219.105.120.15
...
2019-09-29 12:23:39
91.121.155.215 attackbotsspam
WordPress brute force
2019-09-29 09:10:17
92.119.160.6 attackbotsspam
09/28/2019-23:56:48.364552 92.119.160.6 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-09-29 12:09:04
54.38.33.186 attackbots
Sep 29 07:13:49 www sshd\[124674\]: Invalid user sysa from 54.38.33.186
Sep 29 07:13:49 www sshd\[124674\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.38.33.186
Sep 29 07:13:51 www sshd\[124674\]: Failed password for invalid user sysa from 54.38.33.186 port 43646 ssh2
...
2019-09-29 12:15:29
119.50.99.34 attack
Automatic report - Port Scan Attack
2019-09-29 12:27:24
123.58.33.18 attackbots
2019-09-29T00:00:01.5418971495-001 sshd\[38193\]: Invalid user Jewel from 123.58.33.18 port 52936
2019-09-29T00:00:01.5450111495-001 sshd\[38193\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.58.33.18
2019-09-29T00:00:03.2974641495-001 sshd\[38193\]: Failed password for invalid user Jewel from 123.58.33.18 port 52936 ssh2
2019-09-29T00:06:27.8910661495-001 sshd\[38661\]: Invalid user microsoft from 123.58.33.18 port 45758
2019-09-29T00:06:27.8982461495-001 sshd\[38661\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.58.33.18
2019-09-29T00:06:29.9769271495-001 sshd\[38661\]: Failed password for invalid user microsoft from 123.58.33.18 port 45758 ssh2
...
2019-09-29 12:19:40
111.207.49.186 attackspam
Sep 29 05:51:41 v22019058497090703 sshd[32082]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.207.49.186
Sep 29 05:51:44 v22019058497090703 sshd[32082]: Failed password for invalid user ftpuser from 111.207.49.186 port 42618 ssh2
Sep 29 05:56:22 v22019058497090703 sshd[32676]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.207.49.186
...
2019-09-29 12:22:05
94.130.90.170 attack
xmlrpc attack
2019-09-29 09:06:00
49.234.56.201 attackspam
Sep 28 18:10:51 lcdev sshd\[15917\]: Invalid user ew from 49.234.56.201
Sep 28 18:10:51 lcdev sshd\[15917\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.56.201
Sep 28 18:10:53 lcdev sshd\[15917\]: Failed password for invalid user ew from 49.234.56.201 port 37636 ssh2
Sep 28 18:15:35 lcdev sshd\[16436\]: Invalid user rator from 49.234.56.201
Sep 28 18:15:35 lcdev sshd\[16436\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.56.201
2019-09-29 12:17:31
222.186.180.20 attackspambots
09/29/2019-00:18:11.927271 222.186.180.20 Protocol: 6 ET SCAN Potential SSH Scan
2019-09-29 12:23:22
222.186.42.241 attack
Sep 29 04:20:15 localhost sshd\[80439\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.241  user=root
Sep 29 04:20:17 localhost sshd\[80439\]: Failed password for root from 222.186.42.241 port 58522 ssh2
Sep 29 04:20:19 localhost sshd\[80439\]: Failed password for root from 222.186.42.241 port 58522 ssh2
Sep 29 04:20:22 localhost sshd\[80439\]: Failed password for root from 222.186.42.241 port 58522 ssh2
Sep 29 04:24:54 localhost sshd\[80579\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.241  user=root
...
2019-09-29 12:26:14
58.162.140.172 attack
Sep 29 04:26:18 venus sshd\[12588\]: Invalid user mt from 58.162.140.172 port 42487
Sep 29 04:26:18 venus sshd\[12588\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.162.140.172
Sep 29 04:26:20 venus sshd\[12588\]: Failed password for invalid user mt from 58.162.140.172 port 42487 ssh2
...
2019-09-29 12:27:04
106.13.148.33 attackspam
Automated report - ssh fail2ban:
Sep 29 05:52:43 wrong password, user=list, port=60594, ssh2
Sep 29 05:56:41 authentication failure 
Sep 29 05:56:43 wrong password, user=steam, port=34024, ssh2
2019-09-29 12:13:37
203.114.102.69 attackspambots
Sep 29 00:52:53 saschabauer sshd[25964]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.114.102.69
Sep 29 00:52:55 saschabauer sshd[25964]: Failed password for invalid user svaadmin from 203.114.102.69 port 45421 ssh2
2019-09-29 09:06:45

Recently Reported IPs

162.114.162.216 159.39.229.127 72.204.97.16 93.15.131.40
128.11.215.46 228.68.11.76 192.84.74.183 205.79.50.130
33.49.28.193 241.38.108.91 8.11.57.180 44.152.111.82
228.239.235.239 236.248.27.143 91.137.247.211 242.73.146.9
145.188.161.29 148.227.138.29 211.92.4.202 192.226.7.75