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

;; QUESTION SECTION:
;167.94.145.70.			IN	A

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

;; Query time: 49 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Sep 14 22:15:29 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 70.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 70.145.94.167.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
190.141.32.190 attackbots
RDP Bruteforce
2020-03-20 09:05:11
91.230.153.121 attack
Mar 20 02:13:55 debian-2gb-nbg1-2 kernel: \[6925940.091214\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=91.230.153.121 DST=195.201.40.59 LEN=40 TOS=0x10 PREC=0x60 TTL=244 ID=39970 PROTO=TCP SPT=41425 DPT=55492 WINDOW=1024 RES=0x00 SYN URGP=0
2020-03-20 09:19:23
162.222.212.46 attackbotsspam
Mar 20 02:15:18 163-172-32-151 sshd[21962]: Invalid user test from 162.222.212.46 port 33952
...
2020-03-20 09:24:12
47.58.78.47 attackbotsspam
Automatic report - Port Scan Attack
2020-03-20 09:34:08
138.97.95.165 attackspam
$f2bV_matches
2020-03-20 09:27:08
106.12.199.191 attackbots
Mar 20 00:44:10 h1745522 sshd[10916]: Invalid user fof from 106.12.199.191 port 33310
Mar 20 00:44:10 h1745522 sshd[10916]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.199.191
Mar 20 00:44:10 h1745522 sshd[10916]: Invalid user fof from 106.12.199.191 port 33310
Mar 20 00:44:12 h1745522 sshd[10916]: Failed password for invalid user fof from 106.12.199.191 port 33310 ssh2
Mar 20 00:48:21 h1745522 sshd[11088]: Invalid user user from 106.12.199.191 port 48044
Mar 20 00:48:21 h1745522 sshd[11088]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.199.191
Mar 20 00:48:21 h1745522 sshd[11088]: Invalid user user from 106.12.199.191 port 48044
Mar 20 00:48:23 h1745522 sshd[11088]: Failed password for invalid user user from 106.12.199.191 port 48044 ssh2
Mar 20 00:52:38 h1745522 sshd[11287]: Invalid user pms from 106.12.199.191 port 34554
...
2020-03-20 09:37:51
10.255.37.137 attack
firewall-block, port(s): 18787/tcp
2020-03-20 09:33:24
197.32.203.197 attack
Mar 19 22:50:00 haigwepa sshd[15417]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=197.32.203.197 
Mar 19 22:50:02 haigwepa sshd[15417]: Failed password for invalid user admin from 197.32.203.197 port 44938 ssh2
...
2020-03-20 09:31:57
83.205.40.144 attackbots
Mar 20 02:59:57 www sshd\[70063\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.205.40.144  user=root
Mar 20 02:59:59 www sshd\[70063\]: Failed password for root from 83.205.40.144 port 43250 ssh2
Mar 20 03:08:26 www sshd\[70111\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.205.40.144  user=root
...
2020-03-20 09:33:08
156.204.242.229 attack
1584654592 - 03/19/2020 22:49:52 Host: 156.204.242.229/156.204.242.229 Port: 23 TCP Blocked
2020-03-20 09:38:59
101.95.162.58 attackspambots
20/3/19@17:49:55: FAIL: Alarm-Network address from=101.95.162.58
20/3/19@17:49:56: FAIL: Alarm-Network address from=101.95.162.58
...
2020-03-20 09:36:52
148.70.136.94 attackbotsspam
Mar 20 02:11:07 localhost sshd\[22945\]: Invalid user nodeserver from 148.70.136.94 port 41727
Mar 20 02:11:07 localhost sshd\[22945\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.136.94
Mar 20 02:11:10 localhost sshd\[22945\]: Failed password for invalid user nodeserver from 148.70.136.94 port 41727 ssh2
2020-03-20 09:36:09
27.66.204.199 attackspambots
Mar 19 22:49:59 v22018086721571380 sshd[23994]: Failed password for invalid user admin from 27.66.204.199 port 34771 ssh2
Mar 19 22:50:03 v22018086721571380 sshd[24001]: Failed password for invalid user admin from 27.66.204.199 port 34793 ssh2
2020-03-20 09:31:22
177.129.8.26 attack
Brute force SMTP login attempted.
...
2020-03-20 09:12:38
128.199.104.242 attackbots
Scanned 3 times in the last 24 hours on port 22
2020-03-20 09:03:54

Recently Reported IPs

169.54.244.95 92.118.160.192 92.118.161.20 196.52.43.82
167.94.145.182 185.62.190.77 92.118.37.130 92.118.160.228
185.62.190.237 92.118.161.34 45.141.86.114 188.209.52.94
89.248.172.152 92.118.161.201 45.132.187.30 45.141.86.247
45.141.86.112 167.94.145.122 169.53.184.23 45.141.86.85