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: unknown

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

;; QUESTION SECTION:
;138.94.224.239.			IN	A

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

;; Query time: 66 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 07:55:31 CST 2022
;; MSG SIZE  rcvd: 107
Host info
239.224.94.138.in-addr.arpa domain name pointer host-138-94-224-239.consoftmg.com.br.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
239.224.94.138.in-addr.arpa	name = host-138-94-224-239.consoftmg.com.br.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
167.160.160.138 attackspam
Nov 30 08:28:05 elektron postfix/smtpd\[25141\]: NOQUEUE: reject: RCPT from unknown\[167.160.160.138\]: 450 4.7.1 Client host rejected: cannot find your hostname, \[167.160.160.138\]\; from=\ to=\ proto=ESMTP helo=\
Nov 30 08:38:05 elektron postfix/smtpd\[28710\]: NOQUEUE: reject: RCPT from unknown\[167.160.160.138\]: 450 4.7.1 Client host rejected: cannot find your hostname, \[167.160.160.138\]\; from=\ to=\ proto=ESMTP helo=\
Nov 30 08:39:38 elektron postfix/smtpd\[28710\]: NOQUEUE: reject: RCPT from unknown\[167.160.160.138\]: 450 4.7.1 Client host rejected: cannot find your hostname, \[167.160.160.138\]\; from=\ to=\ proto=ESMTP helo=\
Nov 30 08:48:06 elektron postfix/smtpd\[28710\]: NOQUEUE: reject: RCPT from unknown\[167.160.160.138\]: 450 4.7.1 Client host rejected: cannot find your hostname, \[167.160.160.138\]\; from=\ to=\
2019-11-30 15:35:03
42.157.129.158 attackbotsspam
Nov 29 21:17:31 php1 sshd\[29750\]: Invalid user guhl from 42.157.129.158
Nov 29 21:17:31 php1 sshd\[29750\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.157.129.158
Nov 29 21:17:33 php1 sshd\[29750\]: Failed password for invalid user guhl from 42.157.129.158 port 52992 ssh2
Nov 29 21:22:01 php1 sshd\[30202\]: Invalid user yoyo from 42.157.129.158
Nov 29 21:22:01 php1 sshd\[30202\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.157.129.158
2019-11-30 15:39:22
204.93.180.6 attack
port scanning
2019-11-30 15:51:43
187.141.128.42 attack
Nov 30 07:41:13 hcbbdb sshd\[12922\]: Invalid user harford from 187.141.128.42
Nov 30 07:41:13 hcbbdb sshd\[12922\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.141.128.42
Nov 30 07:41:15 hcbbdb sshd\[12922\]: Failed password for invalid user harford from 187.141.128.42 port 53904 ssh2
Nov 30 07:44:36 hcbbdb sshd\[13201\]: Invalid user admin from 187.141.128.42
Nov 30 07:44:36 hcbbdb sshd\[13201\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.141.128.42
2019-11-30 15:56:47
129.211.75.184 attack
Nov 30 07:06:26 localhost sshd\[97018\]: Invalid user gesino from 129.211.75.184 port 48064
Nov 30 07:06:26 localhost sshd\[97018\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.75.184
Nov 30 07:06:28 localhost sshd\[97018\]: Failed password for invalid user gesino from 129.211.75.184 port 48064 ssh2
Nov 30 07:10:25 localhost sshd\[97178\]: Invalid user admin from 129.211.75.184 port 56108
Nov 30 07:10:25 localhost sshd\[97178\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.75.184
...
2019-11-30 15:26:38
222.186.180.9 attack
Nov 30 09:50:47 dri sshd[29867]: error: PAM: Authentication failure for root from 222.186.180.9
Nov 30 09:50:52 dri sshd[29867]: error: PAM: Authentication failure for root from 222.186.180.9
Nov 30 0
...
2019-11-30 15:53:29
106.12.6.136 attackspam
Nov 30 07:25:58 legacy sshd[7780]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.6.136
Nov 30 07:26:00 legacy sshd[7780]: Failed password for invalid user temp from 106.12.6.136 port 55786 ssh2
Nov 30 07:29:49 legacy sshd[7879]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.6.136
...
2019-11-30 15:24:54
103.85.255.40 attackbotsspam
22/tcp
[2019-11-30]1pkt
2019-11-30 15:47:52
67.55.92.89 attackspam
Nov 29 20:42:10 tdfoods sshd\[18005\]: Invalid user root111 from 67.55.92.89
Nov 29 20:42:10 tdfoods sshd\[18005\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.55.92.89
Nov 29 20:42:12 tdfoods sshd\[18005\]: Failed password for invalid user root111 from 67.55.92.89 port 46926 ssh2
Nov 29 20:45:18 tdfoods sshd\[18199\]: Invalid user dede from 67.55.92.89
Nov 29 20:45:18 tdfoods sshd\[18199\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.55.92.89
2019-11-30 15:21:29
218.92.0.168 attackspam
Nov 30 08:30:25 MK-Soft-Root2 sshd[25060]: Failed password for root from 218.92.0.168 port 64063 ssh2
Nov 30 08:30:30 MK-Soft-Root2 sshd[25060]: Failed password for root from 218.92.0.168 port 64063 ssh2
...
2019-11-30 15:38:29
112.85.42.173 attackbotsspam
Nov 30 08:52:52 nextcloud sshd\[24766\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.173  user=root
Nov 30 08:52:53 nextcloud sshd\[24766\]: Failed password for root from 112.85.42.173 port 62065 ssh2
Nov 30 08:53:04 nextcloud sshd\[24766\]: Failed password for root from 112.85.42.173 port 62065 ssh2
...
2019-11-30 15:55:34
211.159.182.44 attackspam
Nov 29 21:14:03 wbs sshd\[11821\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.159.182.44  user=root
Nov 29 21:14:05 wbs sshd\[11821\]: Failed password for root from 211.159.182.44 port 34598 ssh2
Nov 29 21:18:03 wbs sshd\[12077\]: Invalid user kieran from 211.159.182.44
Nov 29 21:18:03 wbs sshd\[12077\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.159.182.44
Nov 29 21:18:05 wbs sshd\[12077\]: Failed password for invalid user kieran from 211.159.182.44 port 39036 ssh2
2019-11-30 15:20:47
36.85.240.227 attackbots
Honeypot attack, port: 23, PTR: PTR record not found
2019-11-30 15:50:33
51.89.148.180 attackspam
$f2bV_matches
2019-11-30 15:48:05
132.232.14.180 attack
Nov 30 02:33:51 linuxvps sshd\[5647\]: Invalid user lande from 132.232.14.180
Nov 30 02:33:51 linuxvps sshd\[5647\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.14.180
Nov 30 02:33:53 linuxvps sshd\[5647\]: Failed password for invalid user lande from 132.232.14.180 port 38942 ssh2
Nov 30 02:38:33 linuxvps sshd\[8254\]: Invalid user 12345 from 132.232.14.180
Nov 30 02:38:33 linuxvps sshd\[8254\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.14.180
2019-11-30 15:42:12

Recently Reported IPs

138.94.224.23 118.190.159.244 138.94.224.66 138.94.224.128
138.94.224.87 138.94.202.90 138.94.209.97 138.94.233.77
138.94.225.83 138.94.234.162 138.94.226.132 118.190.159.6
138.94.225.33 138.94.225.56 138.94.236.161 138.94.236.87
138.94.236.250 138.94.236.69 138.94.237.8 138.94.237.22