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.245.45 attackbots
W 31101,/var/log/nginx/access.log,-,-
2020-06-17 18:16:11
138.185.245.61 attack
Automatic report - Port Scan Attack
2020-06-04 04:22:12
138.185.245.3 attack
Automatic report - Port Scan Attack
2020-05-20 21:12:53
138.185.245.86 attack
Unauthorized connection attempt detected from IP address 138.185.245.86 to port 80 [J]
2020-01-07 07:30:12
138.185.245.237 attackspambots
Automatic report - Port Scan Attack
2019-10-04 04:03:58
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 138.185.245.28
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30128
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;138.185.245.28.			IN	A

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

;; Query time: 21 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 07:30:46 CST 2022
;; MSG SIZE  rcvd: 107
Host info
28.245.185.138.in-addr.arpa domain name pointer 138-185-245-28.pcnettelecom.com.br.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
28.245.185.138.in-addr.arpa	name = 138-185-245-28.pcnettelecom.com.br.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
185.176.27.94 attackbotsspam
ET DROP Dshield Block Listed Source group 1 - port: 7700 proto: TCP cat: Misc Attack
2019-12-28 03:46:09
106.56.83.174 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-12-28 03:47:06
14.29.79.178 attackspam
port scan and connect, tcp 23 (telnet)
2019-12-28 03:50:12
114.34.34.5 attack
SIP/5060 Probe, BF, Hack -
2019-12-28 03:49:44
192.169.216.233 attackspambots
2019-12-27T16:57:18.714761abusebot-2.cloudsearch.cf sshd[32018]: Invalid user test from 192.169.216.233 port 43088
2019-12-27T16:57:18.720898abusebot-2.cloudsearch.cf sshd[32018]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip-192-169-216-233.ip.secureserver.net
2019-12-27T16:57:18.714761abusebot-2.cloudsearch.cf sshd[32018]: Invalid user test from 192.169.216.233 port 43088
2019-12-27T16:57:20.410847abusebot-2.cloudsearch.cf sshd[32018]: Failed password for invalid user test from 192.169.216.233 port 43088 ssh2
2019-12-27T17:01:25.053687abusebot-2.cloudsearch.cf sshd[32036]: Invalid user lynnell from 192.169.216.233 port 38562
2019-12-27T17:01:25.059363abusebot-2.cloudsearch.cf sshd[32036]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip-192-169-216-233.ip.secureserver.net
2019-12-27T17:01:25.053687abusebot-2.cloudsearch.cf sshd[32036]: Invalid user lynnell from 192.169.216.233 port 38562
2019-12-27
...
2019-12-28 04:13:38
62.80.191.92 attack
firewall-block, port(s): 65225/tcp
2019-12-28 04:18:56
118.68.203.7 attack
Dec 27 16:04:01 vmanager6029 sshd\[8287\]: Invalid user guest from 118.68.203.7 port 42199
Dec 27 16:04:02 vmanager6029 sshd\[8287\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.68.203.7
Dec 27 16:04:04 vmanager6029 sshd\[8287\]: Failed password for invalid user guest from 118.68.203.7 port 42199 ssh2
2019-12-28 03:44:31
45.136.108.85 attack
2019-12-27T20:08:46.751088ns386461 sshd\[27090\]: Invalid user 0 from 45.136.108.85 port 9365
2019-12-27T20:08:47.951440ns386461 sshd\[27090\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.136.108.85
2019-12-27T20:08:50.330106ns386461 sshd\[27090\]: Failed password for invalid user 0 from 45.136.108.85 port 9365 ssh2
2019-12-27T20:08:56.787158ns386461 sshd\[27310\]: Invalid user 22 from 45.136.108.85 port 22523
2019-12-27T20:08:58.215204ns386461 sshd\[27310\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.136.108.85
...
2019-12-28 04:04:02
167.172.239.155 attackspambots
WordPress wp-login brute force :: 167.172.239.155 0.200 - [27/Dec/2019:19:00:10  0000] [censored_1] "POST /wp-login.php HTTP/1.1" 200 1806 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" "HTTP/1.1"
2019-12-28 04:17:21
51.38.35.2 attack
Unauthorized connection attempt detected from IP address 51.38.35.2 to port 3389
2019-12-28 03:43:01
109.88.29.50 attackspambots
php WP PHPmyadamin ABUSE blocked for 12h
2019-12-28 04:15:55
51.89.250.194 attack
Dec 27 16:55:33 grey postfix/smtpd\[11577\]: NOQUEUE: reject: RCPT from ip194.ip-51-89-250.eu\[51.89.250.194\]: 554 5.7.1 Service unavailable\; Client host \[51.89.250.194\] blocked using bl.spamcop.net\; Blocked - see https://www.spamcop.net/bl.shtml\?51.89.250.194\; from=\<4783-45-327424-1124-feher.eszter=kybest.hu@mail.stillhopelink.xyz\> to=\ proto=ESMTP helo=\
...
2019-12-28 04:09:10
218.92.0.179 attackbotsspam
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.179  user=root
Failed password for root from 218.92.0.179 port 19760 ssh2
Failed password for root from 218.92.0.179 port 19760 ssh2
Failed password for root from 218.92.0.179 port 19760 ssh2
Failed password for root from 218.92.0.179 port 19760 ssh2
2019-12-28 04:11:26
35.172.199.106 attackspam
Automatic report - XMLRPC Attack
2019-12-28 04:11:06
109.194.175.27 attack
Invalid user smmsp from 109.194.175.27 port 49062
2019-12-28 03:49:18

Recently Reported IPs

138.185.245.38 138.185.245.251 138.185.245.31 138.185.245.41
138.185.245.44 118.175.170.66 138.185.245.27 138.185.245.5
138.185.245.63 138.185.245.60 138.185.245.51 138.185.245.57
138.185.245.52 118.175.170.70 138.185.245.82 138.185.245.69
138.185.245.66 138.185.245.84 138.185.245.75 138.185.245.88