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

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

;; QUESTION SECTION:
;2.2.164.36.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 05:38:00 CST 2025
;; MSG SIZE  rcvd: 103
Host info
Host 36.164.2.2.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 36.164.2.2.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
51.68.65.174 attackspam
Feb 28 21:37:58 mockhub sshd[7157]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.68.65.174
Feb 28 21:38:00 mockhub sshd[7157]: Failed password for invalid user michael from 51.68.65.174 port 36922 ssh2
...
2020-02-29 21:11:53
103.100.209.228 attack
Feb 29 11:08:43 server sshd[2651606]: Failed password for invalid user nazrul from 103.100.209.228 port 39141 ssh2
Feb 29 11:15:23 server sshd[2653187]: Failed password for invalid user diana from 103.100.209.228 port 37305 ssh2
Feb 29 11:22:07 server sshd[2654620]: Failed password for invalid user sandbox from 103.100.209.228 port 35469 ssh2
2020-02-29 21:25:56
182.69.158.191 attack
$f2bV_matches
2020-02-29 20:55:50
101.71.2.165 attackspambots
Feb 29 08:10:07 NPSTNNYC01T sshd[21896]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.71.2.165
Feb 29 08:10:10 NPSTNNYC01T sshd[21896]: Failed password for invalid user test1 from 101.71.2.165 port 15979 ssh2
Feb 29 08:11:08 NPSTNNYC01T sshd[21921]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.71.2.165
...
2020-02-29 21:31:15
192.241.224.136 attack
" "
2020-02-29 21:33:27
77.81.224.88 attack
[Mon Feb 10 03:42:00.042941 2020] [access_compat:error] [pid 2236] [client 77.81.224.88:54036] AH01797: client denied by server configuration: /var/www/html/luke/wp-login.php, referer: http://www.lukegirvin.co.uk/wp-login.php
...
2020-02-29 21:21:06
162.243.99.164 attack
Feb 29 07:42:06 plusreed sshd[18875]: Invalid user divya from 162.243.99.164
...
2020-02-29 21:01:44
52.224.12.195 attackspam
Feb 29 06:38:20 haigwepa sshd[19011]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.224.12.195 
Feb 29 06:38:22 haigwepa sshd[19011]: Failed password for invalid user airbot from 52.224.12.195 port 57521 ssh2
...
2020-02-29 20:57:08
211.23.150.203 attackspam
Unauthorized connection attempt detected from IP address 211.23.150.203 to port 23 [J]
2020-02-29 21:38:24
178.62.248.130 attack
Feb 29 15:41:51 server sshd\[16594\]: Invalid user mailtest from 178.62.248.130
Feb 29 15:41:51 server sshd\[16594\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.248.130 
Feb 29 15:41:54 server sshd\[16594\]: Failed password for invalid user mailtest from 178.62.248.130 port 43768 ssh2
Feb 29 15:57:20 server sshd\[19424\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.248.130  user=root
Feb 29 15:57:22 server sshd\[19424\]: Failed password for root from 178.62.248.130 port 57820 ssh2
...
2020-02-29 21:16:09
69.94.131.136 attackspambots
Feb 29 06:37:56  exim[25563]: [1\50] 1j7uor-0006eJ-8U H=behave.avyatm.com (behave.sonicrh.com) [69.94.131.136] F= rejected after DATA: This message scored 103.0 spam points.
2020-02-29 21:10:13
110.177.40.238 attackbots
Unauthorized connection attempt detected from IP address 110.177.40.238 to port 23 [J]
2020-02-29 21:13:01
178.154.171.22 attack
[Sat Feb 29 15:25:05.774987 2020] [:error] [pid 28987:tid 139674565330688] [client 178.154.171.22:56555] [client 178.154.171.22] ModSecurity: Access denied with code 403 (phase 2). Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "696"] [id "920350"] [msg "Host header is a numeric IP address"] [data "103.27.207.197"] [severity "WARNING"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [hostname "103.27.207.197"] [uri "/"] [unique_id "Xlof4aDRKRWqkkhkwDIdTwAAADk"]
...
2020-02-29 21:30:11
119.254.155.187 attack
SSH Bruteforce attempt
2020-02-29 21:16:41
222.186.175.151 attackbots
tried it too often
2020-02-29 21:22:47

Recently Reported IPs

71.196.240.146 154.180.239.111 143.168.197.118 206.135.73.196
208.55.149.30 59.136.123.255 50.114.22.166 218.104.60.23
62.231.204.218 73.152.244.110 118.220.146.94 199.51.214.40
93.167.214.72 39.212.189.120 146.233.177.79 241.87.220.121
143.20.154.79 153.132.46.250 152.248.3.203 60.143.235.159