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

Region: Municipalidad Metropolitana de Lima

Country: Peru

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

;; QUESTION SECTION:
;45.232.195.139.			IN	A

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

;; Query time: 22 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 14 08:55:04 CST 2023
;; MSG SIZE  rcvd: 107
Host info
Host 139.195.232.45.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 139.195.232.45.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
51.89.68.141 attackbots
Invalid user gotit from 51.89.68.141 port 50342
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.89.68.141
Failed password for invalid user gotit from 51.89.68.141 port 50342 ssh2
Invalid user qme from 51.89.68.141 port 51504
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.89.68.141
2020-01-08 15:05:01
79.177.2.142 attackbots
Unauthorized connection attempt detected from IP address 79.177.2.142 to port 23 [J]
2020-01-08 14:26:45
37.114.182.231 attackspam
smtp probe/invalid login attempt
2020-01-08 14:52:18
188.163.249.18 attackspam
Jan  8 05:43:21 zx01vmsma01 sshd[171793]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.163.249.18
Jan  8 05:43:23 zx01vmsma01 sshd[171793]: Failed password for invalid user mvd from 188.163.249.18 port 41958 ssh2
...
2020-01-08 14:49:20
188.93.127.142 attack
Jan  8 07:03:58 pi sshd[5645]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.93.127.142 
Jan  8 07:04:00 pi sshd[5645]: Failed password for invalid user dreyer from 188.93.127.142 port 45508 ssh2
2020-01-08 15:05:24
40.77.167.37 attack
Automatic report - Banned IP Access
2020-01-08 15:09:24
118.33.28.34 attackspambots
Unauthorized connection attempt detected from IP address 118.33.28.34 to port 22 [J]
2020-01-08 15:01:32
88.247.218.247 attack
Automatic report - Port Scan Attack
2020-01-08 15:02:22
178.128.201.239 attack
unauthorized connection attempt
2020-01-08 14:23:04
146.88.240.43 attack
Unauthorized connection attempt detected from IP address 146.88.240.43 to port 443 [J]
2020-01-08 14:45:54
5.189.151.105 attackspam
$f2bV_matches
2020-01-08 14:53:19
185.164.255.34 attackspam
01/07/2020-23:54:36.243168 185.164.255.34 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2020-01-08 14:47:10
112.206.225.82 attack
Unauthorized connection attempt detected from IP address 112.206.225.82 to port 2220 [J]
2020-01-08 14:48:44
125.214.57.87 attack
20/1/7@23:54:25: FAIL: Alarm-Intrusion address from=125.214.57.87
...
2020-01-08 14:56:05
103.219.112.98 attackspambots
Jan  8 05:55:05 MK-Soft-Root2 sshd[7076]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.219.112.98 
Jan  8 05:55:08 MK-Soft-Root2 sshd[7076]: Failed password for invalid user sth from 103.219.112.98 port 36418 ssh2
...
2020-01-08 14:23:33

Recently Reported IPs

224.126.94.247 62.20.167.238 187.190.208.207 115.232.215.112
130.48.47.53 144.31.244.178 139.189.134.53 151.55.186.190
144.31.244.166 235.47.116.197 105.234.57.234 236.83.180.101
223.234.120.49 217.217.177.172 157.180.200.218 104.82.167.6
184.78.72.143 134.230.79.144 190.190.119.165 120.181.118.38