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 Kingdom of Great Britain and Northern Ireland (the)

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

;; QUESTION SECTION:
;164.136.154.129.		IN	A

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

;; Query time: 31 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 07:58:27 CST 2025
;; MSG SIZE  rcvd: 108
Host info
Host 129.154.136.164.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 129.154.136.164.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
106.75.214.239 attack
SSH Brute Force
2020-04-17 05:36:31
183.234.11.43 attack
SSH Brute Force
2020-04-17 05:28:35
45.225.216.80 attackbotsspam
SSH Brute Force
2020-04-17 05:44:25
129.211.51.65 attackbotsspam
SSH Brute Force
2020-04-17 05:33:32
139.59.13.53 attackspam
Apr 16 23:18:46 srv-ubuntu-dev3 sshd[24014]: Invalid user cj from 139.59.13.53
Apr 16 23:18:46 srv-ubuntu-dev3 sshd[24014]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.13.53
Apr 16 23:18:46 srv-ubuntu-dev3 sshd[24014]: Invalid user cj from 139.59.13.53
Apr 16 23:18:48 srv-ubuntu-dev3 sshd[24014]: Failed password for invalid user cj from 139.59.13.53 port 33162 ssh2
Apr 16 23:22:34 srv-ubuntu-dev3 sshd[24663]: Invalid user postgres from 139.59.13.53
Apr 16 23:22:34 srv-ubuntu-dev3 sshd[24663]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.13.53
Apr 16 23:22:34 srv-ubuntu-dev3 sshd[24663]: Invalid user postgres from 139.59.13.53
Apr 16 23:22:36 srv-ubuntu-dev3 sshd[24663]: Failed password for invalid user postgres from 139.59.13.53 port 36528 ssh2
Apr 16 23:26:16 srv-ubuntu-dev3 sshd[25294]: Invalid user gf from 139.59.13.53
...
2020-04-17 05:32:44
190.181.88.13 attackbots
SSH Brute Force
2020-04-17 05:26:22
178.32.117.80 attack
Apr 16 23:13:44 [host] sshd[17363]: Invalid user u
Apr 16 23:13:44 [host] sshd[17363]: pam_unix(sshd:
Apr 16 23:13:46 [host] sshd[17363]: Failed passwor
2020-04-17 05:29:39
103.145.12.50 attackbots
103.145.12.50 was recorded 9 times by 7 hosts attempting to connect to the following ports: 5060. Incident counter (4h, 24h, all-time): 9, 21, 129
2020-04-17 05:57:19
194.204.194.11 attack
SSH Brute Force
2020-04-17 05:25:13
188.254.0.112 attackspambots
SSH Brute Force
2020-04-17 05:26:39
115.231.231.3 attackbotsspam
SSH Brute Force
2020-04-17 05:35:00
82.64.153.14 attackbotsspam
SSH Brute Force
2020-04-17 05:39:47
217.78.1.59 attack
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-04-17 05:48:26
129.211.46.112 attackspambots
SSH Brute Force
2020-04-17 05:33:47
203.192.204.168 attack
SSH Brute Force
2020-04-17 05:22:41

Recently Reported IPs

252.132.16.165 38.220.216.172 47.200.221.228 204.38.0.234
226.209.199.204 3.108.92.59 73.125.173.107 155.27.198.126
211.55.207.40 151.124.72.68 232.243.58.120 231.206.60.237
41.61.212.59 206.225.137.63 3.88.156.68 177.92.239.167
99.101.219.36 165.204.134.25 220.43.4.94 151.240.127.204