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.138.155 botsattack
KnownAttacker - BadReputation
2025-07-07 12:50:52
167.94.138.63 botsattackproxy
SSH dictionary attack
2025-06-19 12:58:59
167.94.138.41 attackproxy
VoIP blacklist IP
2025-06-16 12:53:41
167.94.138.120 botsattackproxy
SSH bot
2025-06-03 12:57:02
167.94.138.163 botsattack
Fraud scan
2025-02-07 17:59:37
167.94.138.167 attack
Fraud connect
2025-01-22 13:53:35
167.94.138.147 proxy
VPN fraud
2023-06-07 12:46:29
167.94.138.33 proxy
VPN fraud.
2023-06-07 12:43:58
167.94.138.136 proxy
VPN fraud
2023-06-05 12:53:02
167.94.138.131 proxy
VPN fraud
2023-05-29 13:10:03
167.94.138.124 proxy
VPN fraud
2023-05-29 13:06:05
167.94.138.127 proxy
VPN fraud
2023-05-25 12:38:28
167.94.138.52 proxy
VPN fraud
2023-05-16 12:51:16
167.94.138.152 proxy
Scanner VPN
2023-03-21 13:50:31
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 167.94.138.245
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 196
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;167.94.138.245.			IN	A

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

;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 16 06:19:39 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 245.138.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 245.138.94.167.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
180.76.233.148 attack
Jan 10 09:59:06 ws19vmsma01 sshd[5465]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.233.148
Jan 10 09:59:08 ws19vmsma01 sshd[5465]: Failed password for invalid user cne from 180.76.233.148 port 42878 ssh2
...
2020-01-10 21:56:14
191.255.232.53 attack
Invalid user gek from 191.255.232.53 port 50771
2020-01-10 22:09:13
115.186.188.53 attackbotsspam
Jan 10 03:41:05 hanapaa sshd\[14458\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115-186-188-53.nayatel.pk  user=root
Jan 10 03:41:07 hanapaa sshd\[14458\]: Failed password for root from 115.186.188.53 port 58002 ssh2
Jan 10 03:44:13 hanapaa sshd\[14789\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115-186-188-53.nayatel.pk  user=root
Jan 10 03:44:15 hanapaa sshd\[14789\]: Failed password for root from 115.186.188.53 port 54546 ssh2
Jan 10 03:47:08 hanapaa sshd\[15072\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115-186-188-53.nayatel.pk  user=root
2020-01-10 22:06:22
39.74.113.99 attackbotsspam
Honeypot hit.
2020-01-10 22:08:00
188.17.156.43 attackbotsspam
Forged login request.
2020-01-10 21:51:06
148.235.57.183 attackbotsspam
$f2bV_matches
2020-01-10 22:04:50
106.12.36.42 attack
Jan 10 15:36:07 server sshd\[22107\]: Invalid user pos from 106.12.36.42
Jan 10 15:36:07 server sshd\[22107\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.36.42 
Jan 10 15:36:09 server sshd\[22107\]: Failed password for invalid user pos from 106.12.36.42 port 48510 ssh2
Jan 10 15:59:24 server sshd\[27709\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.36.42  user=root
Jan 10 15:59:27 server sshd\[27709\]: Failed password for root from 106.12.36.42 port 50026 ssh2
...
2020-01-10 21:34:55
211.23.46.73 attackspam
failed_logins
2020-01-10 21:46:32
81.22.45.29 attackbotsspam
2020-01-10T14:38:04.130933+01:00 lumpi kernel: [3953379.615798] INPUT:DROP:SPAMHAUS_EDROP:IN=eth0 OUT= MAC=52:54:a2:01:a5:04:d2:74:7f:6e:37:e3:08:00 SRC=81.22.45.29 DST=78.46.199.189 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=45277 PROTO=TCP SPT=51786 DPT=3401 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2020-01-10 21:44:04
213.6.172.134 attackbots
01/10/2020-08:46:20.612558 213.6.172.134 Protocol: 6 ET COMPROMISED Known Compromised or Hostile Host Traffic group 22
2020-01-10 21:49:09
159.203.201.127 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2020-01-10 21:34:42
129.204.37.181 attackbots
Jan 10 14:30:11 [host] sshd[31890]: Invalid user the1 from 129.204.37.181
Jan 10 14:30:11 [host] sshd[31890]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.37.181
Jan 10 14:30:13 [host] sshd[31890]: Failed password for invalid user the1 from 129.204.37.181 port 28657 ssh2
2020-01-10 22:14:15
31.215.203.95 attackspambots
Malicious/Probing: /wp-login.php
2020-01-10 21:56:57
113.189.146.54 attackspambots
1578661032 - 01/10/2020 13:57:12 Host: 113.189.146.54/113.189.146.54 Port: 445 TCP Blocked
2020-01-10 22:06:50
67.219.145.35 attackspambots
Portscan or hack attempt detected by psad/fwsnort
2020-01-10 21:35:16

Recently Reported IPs

176.32.34.129 92.118.161.236 167.94.145.121 167.94.145.34
185.61.138.187 181.174.164.25 185.61.138.133 229.16.253.154
167.94.145.174 176.121.14.108 185.62.189.95 185.62.189.76
185.62.189.34 144.168.253.249 181.174.165.127 181.174.165.140
181.174.164.157 181.174.164.185 181.174.165.159 181.174.165.169