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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;136.2.129.164.			IN	A

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

;; Query time: 375 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Oct 31 08:22:33 CST 2019
;; MSG SIZE  rcvd: 117
Host info
Host 164.129.2.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 164.129.2.136.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
129.211.60.252 attack
Apr  6 19:42:37 NPSTNNYC01T sshd[11902]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.60.252
Apr  6 19:42:39 NPSTNNYC01T sshd[11902]: Failed password for invalid user ubuntu from 129.211.60.252 port 58066 ssh2
Apr  6 19:48:35 NPSTNNYC01T sshd[12213]: Failed password for root from 129.211.60.252 port 40838 ssh2
...
2020-04-07 07:59:36
189.223.104.100 attack
Automatic report - Port Scan Attack
2020-04-07 08:35:32
80.82.70.239 attackbotsspam
Automatic report - Port Scan
2020-04-07 08:00:38
185.176.27.90 attackbots
Apr  7 01:48:28 debian-2gb-nbg1-2 kernel: \[8475932.541693\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.90 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=1179 PROTO=TCP SPT=44329 DPT=45020 WINDOW=1024 RES=0x00 SYN URGP=0
2020-04-07 08:05:18
167.172.57.75 attack
Fail2Ban Ban Triggered
2020-04-07 08:31:36
45.13.93.82 attack
Multiple HTTP calls attempting to GET resources using common API calls or formats on port 8080
2020-04-07 08:17:19
110.93.200.118 attackspam
Apr  7 02:00:42 eventyay sshd[2918]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.93.200.118
Apr  7 02:00:44 eventyay sshd[2918]: Failed password for invalid user abc from 110.93.200.118 port 30412 ssh2
Apr  7 02:03:25 eventyay sshd[3027]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.93.200.118
...
2020-04-07 08:22:37
139.199.183.14 attackspam
Apr  7 01:18:44 ns382633 sshd\[29481\]: Invalid user vagrant from 139.199.183.14 port 44346
Apr  7 01:18:44 ns382633 sshd\[29481\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.183.14
Apr  7 01:18:45 ns382633 sshd\[29481\]: Failed password for invalid user vagrant from 139.199.183.14 port 44346 ssh2
Apr  7 01:50:29 ns382633 sshd\[6880\]: Invalid user deploy from 139.199.183.14 port 57580
Apr  7 01:50:29 ns382633 sshd\[6880\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.183.14
2020-04-07 08:26:27
140.143.207.57 attackspambots
Apr  7 01:33:09 Ubuntu-1404-trusty-64-minimal sshd\[25901\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.207.57  user=root
Apr  7 01:33:11 Ubuntu-1404-trusty-64-minimal sshd\[25901\]: Failed password for root from 140.143.207.57 port 33610 ssh2
Apr  7 01:50:43 Ubuntu-1404-trusty-64-minimal sshd\[1581\]: Invalid user deploy from 140.143.207.57
Apr  7 01:50:43 Ubuntu-1404-trusty-64-minimal sshd\[1581\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.207.57
Apr  7 01:50:45 Ubuntu-1404-trusty-64-minimal sshd\[1581\]: Failed password for invalid user deploy from 140.143.207.57 port 40284 ssh2
2020-04-07 08:26:09
201.49.127.212 attackbotsspam
Apr  6 23:32:55 ws26vmsma01 sshd[224236]: Failed password for root from 201.49.127.212 port 50740 ssh2
...
2020-04-07 08:25:26
89.46.127.207 attack
bruteforce detected
2020-04-07 08:04:19
45.249.94.125 attackbotsspam
(sshd) Failed SSH login from 45.249.94.125 (HK/Hong Kong/-): 5 in the last 3600 secs
2020-04-07 08:15:23
190.103.181.171 attackspam
2020-04-06T23:44:14.303586shield sshd\[9719\]: Invalid user test from 190.103.181.171 port 38216
2020-04-06T23:44:14.307579shield sshd\[9719\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.103.181.171
2020-04-06T23:44:15.956016shield sshd\[9719\]: Failed password for invalid user test from 190.103.181.171 port 38216 ssh2
2020-04-06T23:48:40.999906shield sshd\[10945\]: Invalid user server1 from 190.103.181.171 port 47362
2020-04-06T23:48:41.003466shield sshd\[10945\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.103.181.171
2020-04-07 07:55:54
112.85.42.173 attack
Apr  6 21:03:06 firewall sshd[31890]: Failed password for root from 112.85.42.173 port 1547 ssh2
Apr  6 21:03:09 firewall sshd[31890]: Failed password for root from 112.85.42.173 port 1547 ssh2
Apr  6 21:03:12 firewall sshd[31890]: Failed password for root from 112.85.42.173 port 1547 ssh2
...
2020-04-07 08:09:46
116.52.176.151 attackspambots
04/06/2020-19:48:20.122185 116.52.176.151 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2020-04-07 08:12:53

Recently Reported IPs

138.192.98.244 59.196.83.28 136.176.115.52 49.70.207.90
12.51.156.142 4.193.249.138 59.149.96.243 66.54.245.31
181.168.170.246 28.240.172.164 47.171.157.213 10.54.191.203
51.105.196.51 208.105.247.97 237.155.209.44 48.94.65.241
176.92.144.128 246.18.127.220 144.171.90.27 5.69.114.5