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

;; QUESTION SECTION:
;167.94.145.113.			IN	A

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

;; Query time: 69 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 16 12:19:48 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 113.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 113.145.94.167.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
2.184.57.207 attackspambots
Unauthorized connection attempt from IP address 2.184.57.207 on Port 445(SMB)
2019-12-29 19:40:41
187.218.194.202 attack
Unauthorized connection attempt detected from IP address 187.218.194.202 to port 445
2019-12-29 19:44:20
104.244.72.98 attack
Unauthorized connection attempt detected from IP address 104.244.72.98 to port 22
2019-12-29 20:06:47
191.243.143.170 attackspambots
Dec 29 09:13:15 server sshd\[18456\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=191.243.143.170  user=nagios
Dec 29 09:13:17 server sshd\[18456\]: Failed password for nagios from 191.243.143.170 port 36898 ssh2
Dec 29 09:28:07 server sshd\[21509\]: Invalid user dorcas from 191.243.143.170
Dec 29 09:28:07 server sshd\[21509\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=191.243.143.170 
Dec 29 09:28:08 server sshd\[21509\]: Failed password for invalid user dorcas from 191.243.143.170 port 39754 ssh2
...
2019-12-29 19:50:48
208.82.18.165 attackbots
fail2ban honeypot
2019-12-29 20:01:47
147.135.208.234 attack
Dec 29 11:57:35 sso sshd[3442]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=147.135.208.234
Dec 29 11:57:37 sso sshd[3442]: Failed password for invalid user hung from 147.135.208.234 port 38876 ssh2
...
2019-12-29 19:55:04
37.49.231.183 attackbots
SIP Server BruteForce Attack
2019-12-29 19:58:57
103.110.169.141 attackbots
Dec 29 12:25:03 sd-53420 sshd\[32052\]: Invalid user jongwon from 103.110.169.141
Dec 29 12:25:03 sd-53420 sshd\[32052\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.110.169.141
Dec 29 12:25:04 sd-53420 sshd\[32052\]: Failed password for invalid user jongwon from 103.110.169.141 port 23713 ssh2
Dec 29 12:27:28 sd-53420 sshd\[721\]: Invalid user passwd12345 from 103.110.169.141
Dec 29 12:27:28 sd-53420 sshd\[721\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.110.169.141
...
2019-12-29 20:00:25
218.92.0.141 attackbotsspam
Dec 29 12:59:19 ns3110291 sshd\[20119\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.141  user=root
Dec 29 12:59:20 ns3110291 sshd\[20119\]: Failed password for root from 218.92.0.141 port 23431 ssh2
Dec 29 12:59:24 ns3110291 sshd\[20119\]: Failed password for root from 218.92.0.141 port 23431 ssh2
Dec 29 12:59:27 ns3110291 sshd\[20119\]: Failed password for root from 218.92.0.141 port 23431 ssh2
Dec 29 12:59:31 ns3110291 sshd\[20119\]: Failed password for root from 218.92.0.141 port 23431 ssh2
...
2019-12-29 20:02:27
46.38.144.57 attackspam
Dec 29 12:53:58 relay postfix/smtpd\[20534\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 29 12:55:07 relay postfix/smtpd\[12823\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 29 12:55:24 relay postfix/smtpd\[25952\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 29 12:56:33 relay postfix/smtpd\[16791\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 29 12:56:49 relay postfix/smtpd\[24077\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-12-29 19:59:28
79.137.77.131 attackbots
Dec 29 07:27:49 demo sshd[11015]: Invalid user guest from 79.137.77.131 port 51814
...
2019-12-29 20:00:50
37.202.116.56 attack
Unauthorized connection attempt detected from IP address 37.202.116.56 to port 23
2019-12-29 19:49:37
188.166.172.189 attackbots
$f2bV_matches
2019-12-29 20:13:25
129.213.42.20 attackspam
"SSH brute force auth login attempt."
2019-12-29 20:18:57
163.172.9.14 attackspambots
SIPVicious Scanner Detection, PTR: 163-172-9-14.rev.poneytelecom.eu.
2019-12-29 20:17:07

Recently Reported IPs

85.62.188.104 185.62.190.185 92.118.37.168 185.173.35.113
196.52.43.243 167.94.145.99 185.62.190.183 162.142.125.255
188.209.52.55 167.94.145.107 196.52.43.23 167.94.145.154
185.173.35.83 167.94.145.106 167.94.145.188 193.56.75.78
167.94.145.77 93.174.92.26 92.118.37.187 185.62.190.163