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:
IP Type Details Datetime
167.94.145.64 botsattack
Apache attacker IP
2025-07-04 12:34:41
167.94.145.107 botsattackproxy
SSH bot
2025-07-02 13:03:32
167.94.145.103 spamattackproxy
Postfix attacker IP
2025-07-01 12:41:43
167.94.145.102 botsattackproxy
SSH bot
2025-06-10 14:47:50
167.94.145.99 botsattackproxy
SSH bot
2025-03-19 20:57:58
167.94.145.104 botsattackproxy
BOOT SSH
2025-03-13 13:54:18
167.94.145.97 spambotsattackproxy
SSH bot
2025-02-10 14:24:23
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 167.94.145.53
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51458
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;167.94.145.53.			IN	A

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

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 16 16:19:55 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 53.145.94.167.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 53.145.94.167.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
67.140.97.108 attackspam
Unauthorized connection attempt detected from IP address 67.140.97.108 to port 2220 [J]
2020-01-19 02:45:54
79.175.166.110 attackspam
Unauthorized connection attempt detected from IP address 79.175.166.110 to port 2220 [J]
2020-01-19 02:45:16
123.126.20.94 attack
Unauthorized connection attempt detected from IP address 123.126.20.94 to port 2220 [J]
2020-01-19 02:32:44
1.255.153.167 attackbotsspam
Unauthorized connection attempt detected from IP address 1.255.153.167 to port 2220 [J]
2020-01-19 02:53:52
202.137.134.40 attackspambots
Invalid user admin from 202.137.134.40 port 57827
2020-01-19 02:59:11
131.255.191.4 attack
Invalid user doru from 131.255.191.4 port 45450
2020-01-19 02:31:13
151.29.189.160 attackbots
Invalid user pi from 151.29.189.160 port 40450
2020-01-19 02:29:00
45.14.150.130 attack
Unauthorized connection attempt detected from IP address 45.14.150.130 to port 2220 [J]
2020-01-19 02:50:03
218.78.54.84 attack
Unauthorized connection attempt detected from IP address 218.78.54.84 to port 2220 [J]
2020-01-19 02:55:33
106.13.222.115 attackspambots
Autoban   106.13.222.115 CONNECT/AUTH
2020-01-19 02:39:36
148.70.226.228 attackspambots
Unauthorized connection attempt detected from IP address 148.70.226.228 to port 2220 [J]
2020-01-19 02:29:29
125.137.191.215 attackbotsspam
Unauthorized connection attempt detected from IP address 125.137.191.215 to port 2220 [J]
2020-01-19 02:32:16
51.38.224.110 attackbotsspam
Unauthorized connection attempt detected from IP address 51.38.224.110 to port 2220 [J]
2020-01-19 02:48:44
209.141.55.231 attack
Unauthorized connection attempt detected from IP address 209.141.55.231 to port 2220 [J]
2020-01-19 02:57:44
199.19.224.191 attackbots
SSH Brute-Force reported by Fail2Ban
2020-01-19 02:59:47

Recently Reported IPs

193.27.10.18 5.182.39.156 167.94.146.164 196.52.43.251
45.141.86.87 167.94.145.210 92.119.160.121 93.174.89.245
45.192.136.87 193.56.28.25 193.56.28.83 185.11.146.37
193.56.28.139 185.235.230.89 85.255.234.116 95.181.151.36
14.167.40.217 14.251.75.163 45.140.189.203 3.219.70.225