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

;; QUESTION SECTION:
;138.219.48.12.			IN	A

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

;; Query time: 65 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 07:44:07 CST 2022
;; MSG SIZE  rcvd: 106
Host info
12.48.219.138.in-addr.arpa domain name pointer 138-219-48-12.host.sistemtelecom.com.br.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
12.48.219.138.in-addr.arpa	name = 138-219-48-12.host.sistemtelecom.com.br.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
217.112.142.179 attack
Dec 18 15:22:28 h2421860 postfix/postscreen[18477]: CONNECT from [217.112.142.179]:58558 to [85.214.119.52]:25
Dec 18 15:22:28 h2421860 postfix/dnsblog[18480]: addr 217.112.142.179 listed by domain b.barracudacentral.org as 127.0.0.2
Dec 18 15:22:28 h2421860 postfix/dnsblog[18479]: addr 217.112.142.179 listed by domain bl.mailspike.net as 127.0.0.10
Dec 18 15:22:28 h2421860 postfix/dnsblog[18483]: addr 217.112.142.179 listed by domain Unknown.trblspam.com as 185.53.179.7
Dec 18 15:22:34 h2421860 postfix/postscreen[18477]: DNSBL rank 6 for [217.112.142.179]:58558
Dec x@x
Dec 18 15:22:34 h2421860 postfix/postscreen[18477]: DISCONNECT [217.112.142.179]:58558


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=217.112.142.179
2019-12-19 02:58:24
118.127.10.152 attackspam
Dec 18 08:45:43 hpm sshd\[30820\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=fattony.subscriptiondata.com  user=root
Dec 18 08:45:46 hpm sshd\[30820\]: Failed password for root from 118.127.10.152 port 42440 ssh2
Dec 18 08:52:35 hpm sshd\[31434\]: Invalid user libuuid from 118.127.10.152
Dec 18 08:52:35 hpm sshd\[31434\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=fattony.subscriptiondata.com
Dec 18 08:52:40 hpm sshd\[31434\]: Failed password for invalid user libuuid from 118.127.10.152 port 45926 ssh2
2019-12-19 02:59:12
104.245.145.123 attack
(From glossop.santiago@gmail.com) Are You interested in an advertising service that charges less than $50 every month and sends thousands of people who are ready to buy directly to your website? Have a look at: http://www.moreleadsandsales.xyz
2019-12-19 02:56:27
51.38.234.224 attack
$f2bV_matches
2019-12-19 03:21:57
64.113.32.29 attackspam
Dec 18 19:04:25 vpn01 sshd[3961]: Failed password for root from 64.113.32.29 port 34537 ssh2
Dec 18 19:04:33 vpn01 sshd[3961]: Failed password for root from 64.113.32.29 port 34537 ssh2
...
2019-12-19 03:16:38
46.21.111.93 attackbotsspam
Dec 18 19:32:45 dev0-dcde-rnet sshd[16062]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.21.111.93
Dec 18 19:32:46 dev0-dcde-rnet sshd[16062]: Failed password for invalid user kurochi from 46.21.111.93 port 33954 ssh2
Dec 18 19:40:04 dev0-dcde-rnet sshd[16163]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.21.111.93
2019-12-19 02:56:40
185.176.27.254 attack
12/18/2019-13:48:46.086009 185.176.27.254 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-12-19 02:57:47
188.131.145.98 attack
Dec 18 09:04:25 web1 sshd\[7137\]: Invalid user osmc from 188.131.145.98
Dec 18 09:04:25 web1 sshd\[7137\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.131.145.98
Dec 18 09:04:27 web1 sshd\[7137\]: Failed password for invalid user osmc from 188.131.145.98 port 55360 ssh2
Dec 18 09:09:14 web1 sshd\[7671\]: Invalid user chaddy from 188.131.145.98
Dec 18 09:09:14 web1 sshd\[7671\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.131.145.98
2019-12-19 03:22:42
185.200.118.68 attackspambots
proto=tcp  .  spt=57522  .  dpt=3389  .  src=185.200.118.68  .  dst=xx.xx.4.1  .     (Found on   Alienvault Dec 18)     (857)
2019-12-19 03:23:10
196.192.110.100 attackspambots
Dec 18 13:51:28 linuxvps sshd\[61414\]: Invalid user ne from 196.192.110.100
Dec 18 13:51:28 linuxvps sshd\[61414\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.192.110.100
Dec 18 13:51:31 linuxvps sshd\[61414\]: Failed password for invalid user ne from 196.192.110.100 port 40546 ssh2
Dec 18 13:57:59 linuxvps sshd\[645\]: Invalid user asfazadour from 196.192.110.100
Dec 18 13:57:59 linuxvps sshd\[645\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.192.110.100
2019-12-19 03:10:55
68.183.50.149 attackbotsspam
Dec 18 17:46:26 localhost sshd\[6007\]: Invalid user gloria from 68.183.50.149 port 47266
Dec 18 17:46:26 localhost sshd\[6007\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.50.149
Dec 18 17:46:29 localhost sshd\[6007\]: Failed password for invalid user gloria from 68.183.50.149 port 47266 ssh2
2019-12-19 03:13:44
176.31.191.173 attackspam
Dec 18 16:37:40 vpn01 sshd[30518]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.31.191.173
Dec 18 16:37:42 vpn01 sshd[30518]: Failed password for invalid user shyamala from 176.31.191.173 port 54958 ssh2
...
2019-12-19 03:09:04
36.110.118.136 attackspam
k+ssh-bruteforce
2019-12-19 03:13:08
74.50.224.194 attackbotsspam
Automatic report - XMLRPC Attack
2019-12-19 03:18:55
122.228.19.80 attackspam
122.228.19.80 was recorded 105 times by 26 hosts attempting to connect to the following ports: 8087,5443,12345,1883,3388,4800,3260,623,9090,25,2048,8003,8123,4022,17185,21,1025,264,83,502,990,16993,2083,4070,520,5009,1010,993,2000,515,2087,771,4040,79,626,7547,636,9595,2123,40001,8069,9943,37777,2404,5006,8000,8060,3690,113,631,64738,3268,9306,5985,1962,9418,8554,8889,1777,1521,110,587,16992,8333,8010,5222,41794,5351,5984,7002,2480,3306,9000,28017,9600,4500,37215,789,3283,554,50070,9295,25565,1194,9191,5000,2525. Incident counter (4h, 24h, all-time): 105, 568, 20617
2019-12-19 03:25:54

Recently Reported IPs

118.175.252.44 118.175.252.53 118.175.252.68 118.175.252.81
118.175.252.82 118.175.253.150 118.175.253.155 118.175.253.193
138.255.12.235 138.255.13.209 138.255.13.233 138.255.12.60
138.255.12.249 118.175.253.215 138.255.12.64 138.255.12.46
39.136.186.204 138.255.12.225 138.255.13.207 138.255.125.8