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:
IP Type Details Datetime
138.185.166.218 attack
spam
2020-04-15 16:02:51
138.185.166.133 attackspam
email spam
2020-03-01 19:46:06
138.185.166.254 attack
Sending SPAM email
2020-02-06 23:44:58
138.185.166.173 attackbotsspam
spam
2020-01-22 16:23:34
138.185.166.136 attackbots
Absender hat Spam-Falle ausgel?st
2019-12-19 16:15:01
138.185.166.194 attackspam
Brute force attempt
2019-08-15 05:13:26
138.185.166.166 attackspambots
Lines containing failures of 138.185.166.166
Jul 27 03:25:46 omfg postfix/smtpd[27121]: connect from unknown[138.185.166.166]
Jul x@x


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=138.185.166.166
2019-07-29 08:50:12
138.185.166.149 attackspam
Jul 17 15:34:24 h2421860 postfix/postscreen[29334]: CONNECT from [138.185.166.149]:57743 to [85.214.119.52]:25
Jul 17 15:34:24 h2421860 postfix/dnsblog[29337]: addr 138.185.166.149 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Jul 17 15:34:24 h2421860 postfix/dnsblog[29338]: addr 138.185.166.149 listed by domain bl.spamcop.net as 127.0.0.2
Jul 17 15:34:24 h2421860 postfix/dnsblog[29338]: addr 138.185.166.149 listed by domain zen.spamhaus.org as 127.0.0.4
Jul 17 15:34:24 h2421860 postfix/dnsblog[29338]: addr 138.185.166.149 listed by domain zen.spamhaus.org as 127.0.0.3
Jul 17 15:34:24 h2421860 postfix/dnsblog[29342]: addr 138.185.166.149 listed by domain Unknown.trblspam.com as 185.53.179.7
Jul 17 15:34:24 h2421860 postfix/dnsblog[29339]: addr 138.185.166.149 listed by domain b.barracudacentral.org as 127.0.0.2
Jul 17 15:34:24 h2421860 postfix/dnsblog[29338]: addr 138.185.166.149 listed by domain dnsbl.sorbs.net as 127.0.0.6
Jul 17 15:34:24 h2421860 postfix/postscre........
-------------------------------
2019-07-18 18:23:59
138.185.166.194 attack
Jul 10 20:09:44 mxgate1 postfix/postscreen[26117]: CONNECT from [138.185.166.194]:49880 to [176.31.12.44]:25
Jul 10 20:09:44 mxgate1 postfix/dnsblog[26118]: addr 138.185.166.194 listed by domain zen.spamhaus.org as 127.0.0.4
Jul 10 20:09:44 mxgate1 postfix/dnsblog[26118]: addr 138.185.166.194 listed by domain zen.spamhaus.org as 127.0.0.3
Jul 10 20:09:44 mxgate1 postfix/dnsblog[26122]: addr 138.185.166.194 listed by domain cbl.abuseat.org as 127.0.0.2
Jul 10 20:09:44 mxgate1 postfix/dnsblog[26119]: addr 138.185.166.194 listed by domain bl.spamcop.net as 127.0.0.2
Jul 10 20:09:44 mxgate1 postfix/dnsblog[26121]: addr 138.185.166.194 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Jul 10 20:09:45 mxgate1 postfix/dnsblog[26166]: addr 138.185.166.194 listed by domain b.barracudacentral.org as 127.0.0.2
Jul 10 20:09:45 mxgate1 postfix/postscreen[26117]: PREGREET 38 after 0.53 from [138.185.166.194]:49880: EHLO ip138-185-166-194.netjat.com.br

Jul 10 20:09:45 mxgate1 postfix........
-------------------------------
2019-07-11 18:27:41
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 138.185.166.162
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 6582
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;138.185.166.162.		IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 07:29:59 CST 2022
;; MSG SIZE  rcvd: 108
Host info
162.166.185.138.in-addr.arpa domain name pointer ip138-185-166-162.netjat.com.br.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
162.166.185.138.in-addr.arpa	name = ip138-185-166-162.netjat.com.br.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
45.136.108.67 attackbotsspam
Connection by 45.136.108.67 on port: 6424 got caught by honeypot at 10/31/2019 12:57:35 PM
2019-11-01 01:22:25
106.75.86.217 attackspambots
sshd jail - ssh hack attempt
2019-11-01 01:33:05
177.135.93.227 attackspam
Oct 31 13:06:24 XXX sshd[30744]: Invalid user marlon from 177.135.93.227 port 50014
2019-11-01 01:44:12
117.55.241.178 attack
Oct 31 02:46:19 sachi sshd\[2656\]: Invalid user tonnage from 117.55.241.178
Oct 31 02:46:19 sachi sshd\[2656\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.55.241.178
Oct 31 02:46:21 sachi sshd\[2656\]: Failed password for invalid user tonnage from 117.55.241.178 port 36179 ssh2
Oct 31 02:51:54 sachi sshd\[3131\]: Invalid user Lucas@2017 from 117.55.241.178
Oct 31 02:51:54 sachi sshd\[3131\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.55.241.178
2019-11-01 01:19:15
41.41.98.250 attackspam
Unauthorized connection attempt from IP address 41.41.98.250 on Port 445(SMB)
2019-11-01 01:42:04
208.100.26.231 attackbots
591:20191031:130130.599 failed to accept an incoming connection: connection from "208.100.26.231" rejected
   592:20191031:130130.804 failed to accept an incoming connection: connection from "208.100.26.231" rejected
2019-11-01 01:40:24
94.75.103.54 attack
Unauthorized connection attempt from IP address 94.75.103.54 on Port 445(SMB)
2019-11-01 01:16:45
122.165.167.55 attack
XMLRPC script access attempt: "GET /xmlrpc.php"
2019-11-01 01:15:21
221.133.18.250 attack
Unauthorized connection attempt from IP address 221.133.18.250 on Port 445(SMB)
2019-11-01 01:29:25
181.115.189.130 attackspambots
Unauthorized connection attempt from IP address 181.115.189.130 on Port 445(SMB)
2019-11-01 01:23:18
103.122.34.202 attackbots
Unauthorized connection attempt from IP address 103.122.34.202 on Port 445(SMB)
2019-11-01 01:36:00
23.19.226.131 attackspambots
HTTP 503 XSS Attempt
2019-11-01 01:28:36
54.37.156.188 attackbots
Failed password for invalid user ginnie from 54.37.156.188 port 53711 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.156.188  user=root
Failed password for root from 54.37.156.188 port 45242 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.156.188  user=root
Failed password for root from 54.37.156.188 port 36765 ssh2
2019-11-01 01:24:41
139.99.98.248 attackspambots
Oct 31 14:43:38 server sshd\[8579\]: Invalid user hj from 139.99.98.248
Oct 31 14:43:38 server sshd\[8579\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.99.98.248 
Oct 31 14:43:40 server sshd\[8579\]: Failed password for invalid user hj from 139.99.98.248 port 57028 ssh2
Oct 31 15:01:42 server sshd\[12581\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.99.98.248  user=root
Oct 31 15:01:45 server sshd\[12581\]: Failed password for root from 139.99.98.248 port 51844 ssh2
...
2019-11-01 01:26:40
41.43.219.22 attackbotsspam
Oct 31 07:01:34 mailman sshd[29454]: Invalid user admin from 41.43.219.22
Oct 31 07:01:34 mailman sshd[29454]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.43.219.22 
Oct 31 07:01:35 mailman sshd[29454]: Failed password for invalid user admin from 41.43.219.22 port 34508 ssh2
2019-11-01 01:33:23

Recently Reported IPs

138.185.166.156 138.185.166.164 138.185.166.160 138.185.166.167
138.185.166.172 138.185.166.168 138.185.166.170 138.185.166.174
118.175.169.238 138.185.166.176 138.185.166.178 138.185.166.179
118.175.169.24 138.185.166.184 138.185.166.186 138.185.166.180
138.185.166.182 138.185.166.188 138.185.166.190 138.185.166.197