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
164.132.122.241 attackbotsspam
Honeypot attack, port: 445, PTR: ip241.ip-164-132-122.eu.
2020-02-08 00:48:41
164.132.122.241 attack
Honeypot attack, port: 445, PTR: ip241.ip-164-132-122.eu.
2020-02-06 17:49:30
164.132.122.255 attackbotsspam
Unauthorized connection attempt detected from IP address 164.132.122.255 to port 1433 [J]
2020-02-04 00:10:19
164.132.122.244 attackspam
WordPress wp-login brute force :: 164.132.122.244 0.104 BYPASS [27/Jul/2019:01:54:25  1000] [censored_1] "POST /wp-login.php HTTP/1.1" 200 3972 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-07-27 02:50:46
164.132.122.244 attackbots
WordPress wp-login brute force :: 164.132.122.244 0.156 BYPASS [26/Jul/2019:10:43:04  1000] [censored_1] "POST /wp-login.php HTTP/1.1" 200 3972 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-07-26 11:22:02
164.132.122.244 attackbots
Request: "GET /wp-login.php HTTP/1.1"
2019-07-26 03:53:55
164.132.122.244 attackspambots
WordPress login Brute force / Web App Attack on client site.
2019-07-08 16:49:13
164.132.122.244 attackbots
WordPress wp-login brute force :: 164.132.122.244 0.060 BYPASS [04/Jul/2019:23:14:25  1000] [censored_2] "POST /wp-login.php HTTP/1.1" 200 4630 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-07-04 23:23:13
164.132.122.244 attack
wp-login.php
2019-07-04 18:24:30
164.132.122.244 attackbots
web exploits
...
2019-07-04 00:09:52
164.132.122.244 attack
404 NOT FOUND
2019-06-27 18:52:20
164.132.122.244 attack
Multiple entries:
[client 164.132.122.244:33816] [client 164.132.122.244] ModSecurity: Warning. Pattern match "200" at RESPONSE_STATUS. [file "/etc/httpd/modsec/12_asl_brute.conf"] [line "61"] [id "377360"] [rev "2"] [msg "Atomicorp.com WAF Rules - Login Failure Detection
2019-06-25 20:40:08
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 164.132.122.212
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 19214
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;164.132.122.212.		IN	A

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

;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 20:31:43 CST 2022
;; MSG SIZE  rcvd: 108
Host info
212.122.132.164.in-addr.arpa domain name pointer ip212.ip-164-132-122.eu.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
212.122.132.164.in-addr.arpa	name = ip212.ip-164-132-122.eu.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
116.52.44.109 attackbots
23/tcp
[2019-06-30]1pkt
2019-06-30 16:05:23
87.250.73.31 attack
Jun 30 08:42:41 localhost sshd\[7093\]: Invalid user git from 87.250.73.31
Jun 30 08:42:41 localhost sshd\[7093\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=87.250.73.31
Jun 30 08:42:44 localhost sshd\[7093\]: Failed password for invalid user git from 87.250.73.31 port 42713 ssh2
Jun 30 08:44:22 localhost sshd\[7125\]: Invalid user mcserver from 87.250.73.31
Jun 30 08:44:22 localhost sshd\[7125\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=87.250.73.31
...
2019-06-30 15:42:04
117.208.225.35 attackbotsspam
22/tcp
[2019-06-30]1pkt
2019-06-30 15:35:11
42.56.154.146 attackspambots
60001/tcp
[2019-06-30]1pkt
2019-06-30 16:00:48
218.164.18.253 attackspambots
37215/tcp
[2019-06-30]1pkt
2019-06-30 16:06:22
223.80.179.95 attackspambots
DATE:2019-06-30_05:40:46, IP:223.80.179.95, PORT:telnet Telnet brute force auth on honeypot server (honey-neo-dc)
2019-06-30 16:04:20
170.244.13.81 attackspambots
Jun 29 23:40:37 web1 postfix/smtpd[3881]: warning: 8113244170-pppoe.signet.com.br[170.244.13.81]: SASL PLAIN authentication failed: authentication failure
...
2019-06-30 16:07:35
190.39.34.234 attack
5555/tcp
[2019-06-30]1pkt
2019-06-30 15:24:50
51.75.169.236 attack
Jun 30 08:11:28 debian sshd\[29704\]: Invalid user pos from 51.75.169.236 port 40876
Jun 30 08:11:28 debian sshd\[29704\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.169.236
...
2019-06-30 15:42:39
51.81.7.102 attackbotsspam
DATE:2019-06-30_05:41:36, IP:51.81.7.102, PORT:telnet Telnet brute force auth on honeypot server (honey-neo-dc)
2019-06-30 15:31:28
152.0.56.144 attack
Jun 30 07:54:09 vps647732 sshd[9616]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.0.56.144
Jun 30 07:54:11 vps647732 sshd[9616]: Failed password for invalid user diana123 from 152.0.56.144 port 36603 ssh2
...
2019-06-30 15:32:23
175.151.103.177 attackspambots
60001/tcp
[2019-06-30]1pkt
2019-06-30 15:47:32
116.106.223.124 attackspam
5555/tcp
[2019-06-30]1pkt
2019-06-30 15:48:58
43.224.128.39 attackbotsspam
Jun 30 05:41:33 bouncer sshd\[8832\]: Invalid user web3 from 43.224.128.39 port 43552
Jun 30 05:41:33 bouncer sshd\[8832\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.224.128.39 
Jun 30 05:41:35 bouncer sshd\[8832\]: Failed password for invalid user web3 from 43.224.128.39 port 43552 ssh2
...
2019-06-30 15:31:58
222.139.254.236 attackspam
23/tcp
[2019-06-30]1pkt
2019-06-30 15:30:56

Recently Reported IPs

164.132.12.213 164.132.128.226 164.132.127.192 149.102.248.151
164.132.168.204 164.132.166.29 164.132.170.227 164.132.164.220
164.132.168.182 164.132.170.19 164.132.168.171 164.132.171.194
164.132.168.147 164.132.169.172 164.132.169.16 164.132.169.215
164.132.181.210 164.132.172.233 164.132.186.165 164.132.18.225