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

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

;; QUESTION SECTION:
;196.57.158.214.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 11 14:09:45 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 214.158.57.196.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 214.158.57.196.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
185.19.213.169 attackbots
NAME : ES-OPERADORA-GREDOS-20160104 + e-mail abuse : abuse@qtc404.com CIDR : 185.19.212.0/22 | STATUS : 403 {Looking for resource vulnerabilities} DDoS Attack ES - block certain countries :) IP: 185.19.213.169  Denial-of-Service Attack (DoS) Detected and Blocked by ADMIN  - data recovery https://help-dysk.pl
2019-08-19 08:23:17
195.154.27.239 attackbots
Multiple SSH auth failures recorded by fail2ban
2019-08-19 08:06:31
186.31.142.28 attackspam
port scan and connect, tcp 23 (telnet)
2019-08-19 08:04:22
79.7.217.174 attack
Aug 18 20:07:31 debian sshd\[23197\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.7.217.174  user=root
Aug 18 20:07:32 debian sshd\[23197\]: Failed password for root from 79.7.217.174 port 56297 ssh2
Aug 18 20:11:39 debian sshd\[23304\]: Invalid user aaa from 79.7.217.174 port 53572
...
2019-08-19 08:16:41
180.126.171.111 attackspambots
[Aegis] @ 2019-08-18 23:09:27  0100 -> Maximum authentication attempts exceeded.
2019-08-19 08:29:50
87.119.65.98 attackbotsspam
firewall-block, port(s): 23/tcp
2019-08-19 08:07:33
79.188.68.90 attack
Aug 19 02:25:11 v22019058497090703 sshd[22347]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.188.68.90
Aug 19 02:25:13 v22019058497090703 sshd[22347]: Failed password for invalid user legal3 from 79.188.68.90 port 41722 ssh2
Aug 19 02:30:58 v22019058497090703 sshd[22759]: Failed password for root from 79.188.68.90 port 38391 ssh2
...
2019-08-19 08:34:29
58.246.125.198 attackbots
SSH/22 MH Probe, BF, Hack -
2019-08-19 08:28:44
201.225.172.116 attack
Aug 18 20:00:10 plusreed sshd[29695]: Invalid user bill from 201.225.172.116
...
2019-08-19 08:17:28
187.162.136.19 attack
Automatic report - Port Scan Attack
2019-08-19 08:19:19
106.12.109.188 attack
Aug 18 13:55:28 auw2 sshd\[11886\]: Invalid user complex from 106.12.109.188
Aug 18 13:55:28 auw2 sshd\[11886\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.109.188
Aug 18 13:55:30 auw2 sshd\[11886\]: Failed password for invalid user complex from 106.12.109.188 port 51284 ssh2
Aug 18 13:58:36 auw2 sshd\[12199\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.109.188  user=root
Aug 18 13:58:37 auw2 sshd\[12199\]: Failed password for root from 106.12.109.188 port 51706 ssh2
2019-08-19 08:30:43
190.67.116.12 attackspam
Aug 19 00:42:10 debian sshd\[29624\]: Invalid user bogdan from 190.67.116.12 port 52388
Aug 19 00:42:10 debian sshd\[29624\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.67.116.12
...
2019-08-19 08:15:24
116.25.251.168 attackbotsspam
Aug 18 17:35:41 wp sshd[24638]: Invalid user resolve from 116.25.251.168
Aug 18 17:35:41 wp sshd[24638]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.25.251.168 
Aug 18 17:35:43 wp sshd[24638]: Failed password for invalid user resolve from 116.25.251.168 port 46676 ssh2
Aug 18 17:35:43 wp sshd[24638]: Received disconnect from 116.25.251.168: 11: Bye Bye [preauth]
Aug 18 18:05:06 wp sshd[25224]: Invalid user khostnameo from 116.25.251.168
Aug 18 18:05:06 wp sshd[25224]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.25.251.168 
Aug 18 18:05:08 wp sshd[25224]: Failed password for invalid user khostnameo from 116.25.251.168 port 40316 ssh2
Aug 18 18:05:09 wp sshd[25224]: Received disconnect from 116.25.251.168: 11: Bye Bye [preauth]
Aug 18 18:09:30 wp sshd[25327]: Invalid user console from 116.25.251.168
Aug 18 18:09:30 wp sshd[25327]: pam_unix(sshd:auth): authentication failure; lo........
-------------------------------
2019-08-19 08:37:21
148.240.211.253 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-08-19 07:58:56
141.98.80.71 attackbotsspam
Aug 19 02:29:16 srv-4 sshd\[11822\]: Invalid user admin from 141.98.80.71
Aug 19 02:29:16 srv-4 sshd\[11823\]: Invalid user admin from 141.98.80.71
Aug 19 02:29:16 srv-4 sshd\[11822\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.98.80.71
Aug 19 02:29:16 srv-4 sshd\[11823\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.98.80.71
...
2019-08-19 08:13:16

Recently Reported IPs

133.41.176.88 129.170.228.226 171.152.100.23 35.124.62.75
98.225.163.8 124.250.111.95 251.113.194.186 204.102.48.146
8.162.12.239 41.2.21.178 96.91.93.216 154.178.12.59
254.235.64.232 34.190.160.227 127.137.73.90 31.18.40.145
134.24.56.209 154.110.5.118 193.192.97.203 58.178.135.109