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

;; QUESTION SECTION:
;136.12.164.82.			IN	A

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

;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 17 11:18:21 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 82.164.12.136.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 82.164.12.136.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
159.203.198.34 attack
2020-05-03T18:46:23.986716struts4.enskede.local sshd\[23058\]: Invalid user front from 159.203.198.34 port 58822
2020-05-03T18:46:23.993047struts4.enskede.local sshd\[23058\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.198.34
2020-05-03T18:46:26.960214struts4.enskede.local sshd\[23058\]: Failed password for invalid user front from 159.203.198.34 port 58822 ssh2
2020-05-03T18:54:08.479496struts4.enskede.local sshd\[23090\]: Invalid user school from 159.203.198.34 port 54208
2020-05-03T18:54:08.488284struts4.enskede.local sshd\[23090\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.198.34
...
2020-05-04 00:58:27
2607:f298:5:102f::7f2:4236 attackbotsspam
C1,WP GET /daisuki/wp-login.php
2020-05-04 00:57:12
113.117.180.144 attack
20 attempts against mh-ssh on river
2020-05-04 00:37:16
162.243.144.135 attack
Hits on port : 2376
2020-05-04 00:37:39
138.197.185.188 attackbots
firewall-block, port(s): 9941/tcp
2020-05-04 00:38:40
112.16.211.200 attackspam
(sshd) Failed SSH login from 112.16.211.200 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: May  3 14:46:40 s1 sshd[27250]: Invalid user comercial from 112.16.211.200 port 54106
May  3 14:46:42 s1 sshd[27250]: Failed password for invalid user comercial from 112.16.211.200 port 54106 ssh2
May  3 15:06:17 s1 sshd[28489]: Invalid user syw from 112.16.211.200 port 39194
May  3 15:06:18 s1 sshd[28489]: Failed password for invalid user syw from 112.16.211.200 port 39194 ssh2
May  3 15:11:02 s1 sshd[28713]: Invalid user test from 112.16.211.200 port 57200
2020-05-04 00:10:38
92.242.40.249 attack
firewall-block, port(s): 10003/tcp, 33897/tcp
2020-05-04 00:48:56
113.210.188.139 attack
...
2020-05-04 00:33:38
71.246.210.34 attackspambots
$f2bV_matches
2020-05-04 00:21:55
200.187.127.8 attackspambots
$f2bV_matches
2020-05-04 00:19:11
45.142.183.224 attackbotsspam
Email rejected due to spam filtering
2020-05-04 00:41:18
178.62.125.120 attack
Unauthorized connection attempt detected from IP address 178.62.125.120 to port 23
2020-05-04 00:17:58
61.0.171.19 attack
05/03/2020-08:10:43.631246 61.0.171.19 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2020-05-04 00:28:46
91.121.7.146 attackspam
CMS (WordPress or Joomla) login attempt.
2020-05-04 00:11:13
45.77.103.56 attackbotsspam
IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking.
2020-05-04 00:19:57

Recently Reported IPs

4.148.83.8 197.204.252.131 96.28.207.119 200.132.239.120
136.190.89.223 9.24.189.4 100.232.24.153 247.87.170.200
173.164.208.106 198.226.64.231 180.119.210.39 9.225.238.18
218.75.140.123 222.80.227.112 183.22.106.21 253.216.35.48
98.143.12.241 161.0.111.246 98.8.219.49 179.29.57.4