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: Vitória da Conquista

Region: Bahia

Country: Brazil

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:
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#


NetRange:       45.183.8.0 - 45.191.163.255
CIDR:           45.183.8.0/21, 45.191.128.0/19, 45.183.64.0/18, 45.184.0.0/14, 45.188.0.0/15, 45.183.16.0/20, 45.191.0.0/17, 45.183.128.0/17, 45.190.0.0/16, 45.191.160.0/22, 45.183.32.0/19
NetName:        LACNIC
NetHandle:      NET-45-183-8-0-1
Parent:         NET45 (NET-45-0-0-0-0)
NetType:        Transferred to LACNIC
OriginAS:       
Organization:   Latin American and Caribbean IP address Regional Registry (LACNIC)
RegDate:        2014-09-10
Updated:        2023-03-28
Ref:            https://rdap.arin.net/registry/ip/45.183.8.0

ResourceLink:  http://lacnic.net/cgi-bin/lacnic/whois
ResourceLink:  whois.lacnic.net


OrgName:        Latin American and Caribbean IP address Regional Registry
OrgId:          LACNIC
Address:        Rambla Republica de Mexico 6125
City:           Montevideo
StateProv:      
PostalCode:     11400
Country:        UY
RegDate:        2002-07-27
Updated:        2018-03-15
Ref:            https://rdap.arin.net/registry/entity/LACNIC

ReferralServer:  whois://whois.lacnic.net
ResourceLink:  http://lacnic.net/cgi-bin/lacnic/whois

OrgTechHandle: LACNIC-ARIN
OrgTechName:   LACNIC Whois Info
OrgTechPhone:  +598-2604-2222 
OrgTechEmail:  whois-contact@lacnic.net
OrgTechRef:    https://rdap.arin.net/registry/entity/LACNIC-ARIN

OrgAbuseHandle: LWI100-ARIN
OrgAbuseName:   LACNIC Whois Info
OrgAbusePhone:  +598-2604-2222 
OrgAbuseEmail:  abuse@lacnic.net
OrgAbuseRef:    https://rdap.arin.net/registry/entity/LWI100-ARIN


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#



Found a referral to whois.lacnic.net.

% IP Client: 124.223.158.242
 % Copyright (c) Nic.br - Use of this data is governed by the Use and
% Privacy Policy at https://registro.br/upp . Distribution,
% commercialization, reproduction, and use for advertising or similar
% purposes are expressly prohibited.
% 2026-05-14T08:01:07-03:00 - 124.223.158.242

inetnum:     45.188.120.0/22
aut-num:     AS53005
abuse-c:     JGQFR
owner:       REDE CONNECT TELECOMUNICACOES LTDA
ownerid:     12.664.949/0001-75
responsible: JORDAN GERALDO QUEIROZ FREITAS
owner-c:     JGQFR
tech-c:      JGQFR
inetrev:     45.188.120.0/22
nserver:     dns1.connectba.com.br
nsstat:      20260513 AA
nslastaa:    20260513
nserver:     dns2.connectba.com.br
nsstat:      20260513 AA
nslastaa:    20260513
created:     20191104
changed:     20230213

nic-hdl-br:  JGQFR
person:      jordan geraldo queiroz freitas
created:     20120229
changed:     20260304

% Security and mail abuse issues should also be addressed to cert.br,
% respectivelly to cert@cert.br and mail-abuse@cert.br
%
% whois.registro.br only accepts exact match queries for domains,
% registrants, contacts, tickets, providers, IPs, and ASNs.
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 45.188.123.45
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 11324
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;45.188.123.45.			IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu May 14 19:01:08 CST 2026
;; MSG SIZE  rcvd: 106
Host info
45.123.188.45.in-addr.arpa domain name pointer 45.188.123.45-connectba.com.br.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
45.123.188.45.in-addr.arpa	name = 45.188.123.45-connectba.com.br.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
115.159.214.200 attackbotsspam
Aug 10 06:20:48 h2829583 sshd[1176]: Failed password for root from 115.159.214.200 port 36730 ssh2
2020-08-10 13:26:25
39.59.7.12 attackbotsspam
IP 39.59.7.12 attacked honeypot on port: 8080 at 8/9/2020 8:54:56 PM
2020-08-10 13:18:59
177.242.46.46 attack
Aug 10 05:55:03 cp sshd[15173]: Failed password for root from 177.242.46.46 port 47132 ssh2
Aug 10 05:55:44 cp sshd[15560]: Failed password for root from 177.242.46.46 port 54448 ssh2
2020-08-10 12:57:40
103.75.101.59 attackbots
Aug 10 00:45:28 ny01 sshd[30091]: Failed password for root from 103.75.101.59 port 41060 ssh2
Aug 10 00:48:54 ny01 sshd[30501]: Failed password for root from 103.75.101.59 port 35738 ssh2
2020-08-10 13:08:24
182.75.115.59 attack
Aug 10 02:38:51 host sshd[12079]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.75.115.59  user=root
Aug 10 02:38:52 host sshd[12079]: Failed password for root from 182.75.115.59 port 34990 ssh2
...
2020-08-10 12:46:47
69.132.114.174 attack
Aug 10 05:07:20 vps1 sshd[3750]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.132.114.174  user=root
Aug 10 05:07:22 vps1 sshd[3750]: Failed password for invalid user root from 69.132.114.174 port 52566 ssh2
Aug 10 05:10:34 vps1 sshd[3835]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.132.114.174  user=root
Aug 10 05:10:36 vps1 sshd[3835]: Failed password for invalid user root from 69.132.114.174 port 47610 ssh2
Aug 10 05:13:47 vps1 sshd[3880]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.132.114.174  user=root
Aug 10 05:13:49 vps1 sshd[3880]: Failed password for invalid user root from 69.132.114.174 port 42652 ssh2
Aug 10 05:16:51 vps1 sshd[3937]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.132.114.174  user=root
...
2020-08-10 12:48:05
51.210.151.242 attack
Aug 10 05:45:49 vm0 sshd[32310]: Failed password for root from 51.210.151.242 port 47464 ssh2
...
2020-08-10 13:02:38
87.246.7.143 attackspam
SSH invalid-user multiple login try
2020-08-10 13:21:17
121.28.69.85 attack
$f2bV_matches
2020-08-10 13:19:22
212.70.149.19 attackspambots
2020-08-10 06:37:58 dovecot_login authenticator failed for \(User\) \[212.70.149.19\]: 535 Incorrect authentication data
2020-08-10 06:38:00 dovecot_login authenticator failed for \(User\) \[212.70.149.19\]: 535 Incorrect authentication data
2020-08-10 06:42:19 dovecot_login authenticator failed for \(User\) \[212.70.149.19\]: 535 Incorrect authentication data \(set_id=yucan@no-server.de\)
2020-08-10 06:42:32 dovecot_login authenticator failed for \(User\) \[212.70.149.19\]: 535 Incorrect authentication data \(set_id=yucel@no-server.de\)
2020-08-10 06:42:35 dovecot_login authenticator failed for \(User\) \[212.70.149.19\]: 535 Incorrect authentication data \(set_id=yucel@no-server.de\)
2020-08-10 06:42:43 dovecot_login authenticator failed for \(User\) \[212.70.149.19\]: 535 Incorrect authentication data \(set_id=yucel@no-server.de\)
2020-08-10 06:42:45 dovecot_login authenticator failed for \(User\) \[212.70.149.19\]: 535 Incorrect authentication data \(set_id=yucel@no-server.de\)
202
...
2020-08-10 13:00:17
37.49.224.88 attackspam
Aug 10 06:55:05 jane sshd[28845]: Failed password for root from 37.49.224.88 port 50164 ssh2
...
2020-08-10 13:19:48
222.186.30.218 attackbotsspam
Aug 10 05:20:23 vmanager6029 sshd\[2259\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.218  user=root
Aug 10 05:20:26 vmanager6029 sshd\[2257\]: error: PAM: Authentication failure for root from 222.186.30.218
Aug 10 05:20:26 vmanager6029 sshd\[2260\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.218  user=root
2020-08-10 12:49:40
146.88.240.4 attack
146.88.240.4 was recorded 19 times by 4 hosts attempting to connect to the following ports: 27970,5093,161,1900,5353,1701,123,1434,1194,17. Incident counter (4h, 24h, all-time): 19, 65, 83977
2020-08-10 13:25:27
49.69.158.159 attackspambots
Lines containing failures of 49.69.158.159
Aug  4 09:04:05 neweola sshd[5283]: Bad protocol version identification '' from 49.69.158.159 port 40699
Aug  4 09:04:10 neweola sshd[5284]: Invalid user pi from 49.69.158.159 port 40970
Aug  4 09:04:11 neweola sshd[5284]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.69.158.159 
Aug  4 09:04:12 neweola sshd[5284]: Failed password for invalid user pi from 49.69.158.159 port 40970 ssh2
Aug  4 09:04:16 neweola sshd[5284]: Connection closed by invalid user pi 49.69.158.159 port 40970 [preauth]
Aug  4 09:04:21 neweola sshd[5287]: Invalid user pi from 49.69.158.159 port 45583
Aug  4 09:04:22 neweola sshd[5287]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.69.158.159 


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=49.69.158.159
2020-08-10 12:48:47
180.105.155.157 attack
Port probing on unauthorized port 23
2020-08-10 13:28:04

Recently Reported IPs

77.91.118.46 14.22.117.194 14.22.117.17 2606:4700:10::6814:5333
64.90.18.181 200.36.8.0 200.36.9.117 200.36.9.0
216.194.172.68 2606:4700:10::6816:3235 2606:4700:10::6816:4343 61.223.77.219
223.104.160.70 240e::e:1:200f:102 129.211.172.249 47.83.254.1
212.73.148.39 2606:4700:10::6814:5677 2606:4700:10::6816:1462 57.141.2.17