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

Region: Sao Paulo

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:       138.122.0.0 - 138.122.255.255
CIDR:           138.122.0.0/16
NetName:        LACNIC-ERX-138-122-0-0
NetHandle:      NET-138-122-0-0-1
Parent:         NET138 (NET-138-0-0-0-0)
NetType:        Transferred to LACNIC
OriginAS:       
Organization:   Latin American and Caribbean IP address Regional Registry (LACNIC)
RegDate:        2010-11-19
Updated:        2010-11-19
Comment:        This IP address range is under LACNIC responsibility
Comment:        for further allocations to users in LACNIC region.
Comment:        Please see http://www.lacnic.net/ for further details,
Comment:        or check the WHOIS server located at http://whois.lacnic.net
Ref:            https://rdap.arin.net/registry/ip/138.122.0.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-09-18T01:30:53-03:00 - 124.223.158.242

inetnum:     138.122.164.0/22
aut-num:     AS52800
abuse-c:     OMJSO2
owner:       OS CONNECT INFORMATICA EIRELI - EPP
ownerid:     09.813.165/0001-57
responsible: OMAR JOSE SOUZA
owner-c:     OMJSO2
tech-c:      OMJSO2
inetrev:     138.122.164.0/22
nserver:     os1.frsys.com.br
nsstat:      20260916 AA
nslastaa:    20260916
nserver:     os2.frsys.com.br
nsstat:      20260916 AA
nslastaa:    20260916
created:     20150623
changed:     20150709

nic-hdl-br:  OMJSO2
person:      omar jose souza
created:     20140414
changed:     20260911

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

;; QUESTION SECTION:
;138.122.164.97.			IN	A

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

;; Query time: 29 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 18 12:30:54 CST 2026
;; MSG SIZE  rcvd: 107
Host info
97.164.122.138.in-addr.arpa domain name pointer 138-122-164-97.dynamic.osconnect.com.br.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
97.164.122.138.in-addr.arpa	name = 138-122-164-97.dynamic.osconnect.com.br.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
45.14.150.133 attack
Mar 25 07:41:10 yesfletchmain sshd\[29506\]: Invalid user deadly from 45.14.150.133 port 33860
Mar 25 07:41:10 yesfletchmain sshd\[29506\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.14.150.133
Mar 25 07:41:13 yesfletchmain sshd\[29506\]: Failed password for invalid user deadly from 45.14.150.133 port 33860 ssh2
Mar 25 07:49:51 yesfletchmain sshd\[29798\]: Invalid user informix from 45.14.150.133 port 48706
Mar 25 07:49:51 yesfletchmain sshd\[29798\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.14.150.133
...
2020-03-25 16:37:18
27.79.131.49 attack
Unauthorized connection attempt detected from IP address 27.79.131.49 to port 445
2020-03-25 17:12:20
174.138.1.99 attackbotsspam
174.138.1.99 - - [25/Mar/2020:10:05:29 +0100] "POST /wp-login.php HTTP/1.0" 200 2195 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
174.138.1.99 - - [25/Mar/2020:10:05:35 +0100] "POST /wp-login.php HTTP/1.0" 200 2184 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-03-25 17:14:44
36.74.200.209 attackbotsspam
20/3/24@23:50:37: FAIL: Alarm-Network address from=36.74.200.209
...
2020-03-25 17:15:42
175.24.109.49 attackspam
Mar 25 06:42:57 *** sshd[28215]: Invalid user kasutaja from 175.24.109.49
2020-03-25 16:59:00
152.136.76.230 attackbots
Mar 25 09:19:36 mout sshd[16898]: Invalid user de from 152.136.76.230 port 38729
2020-03-25 17:05:27
106.13.77.182 attackspambots
Brute-force attempt banned
2020-03-25 16:48:53
113.88.133.74 attackbots
2020-03-25 04:59:38,906 fail2ban.actions: WARNING [ssh] Ban 113.88.133.74
2020-03-25 17:16:16
51.83.42.185 attackbotsspam
Mar 25 08:01:05 cloud sshd[19517]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.83.42.185 
Mar 25 08:01:07 cloud sshd[19517]: Failed password for invalid user site from 51.83.42.185 port 53342 ssh2
2020-03-25 16:25:10
92.222.167.246 attackspam
Mar 25 09:28:55 dev0-dcde-rnet sshd[11068]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.222.167.246
Mar 25 09:28:57 dev0-dcde-rnet sshd[11068]: Failed password for invalid user support from 92.222.167.246 port 46296 ssh2
Mar 25 09:30:42 dev0-dcde-rnet sshd[11074]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.222.167.246
2020-03-25 16:51:25
211.220.27.191 attackspambots
2020-03-25T09:49:12.023343vps773228.ovh.net sshd[14566]: Invalid user ts from 211.220.27.191 port 34758
2020-03-25T09:49:12.037144vps773228.ovh.net sshd[14566]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.220.27.191
2020-03-25T09:49:12.023343vps773228.ovh.net sshd[14566]: Invalid user ts from 211.220.27.191 port 34758
2020-03-25T09:49:14.753001vps773228.ovh.net sshd[14566]: Failed password for invalid user ts from 211.220.27.191 port 34758 ssh2
2020-03-25T09:51:13.818527vps773228.ovh.net sshd[15324]: Invalid user lifeixin from 211.220.27.191 port 54036
...
2020-03-25 17:20:42
49.235.81.23 attack
Mar 25 09:03:32 lock-38 sshd[135026]: Invalid user steve from 49.235.81.23 port 60700
Mar 25 09:03:32 lock-38 sshd[135026]: Failed password for invalid user steve from 49.235.81.23 port 60700 ssh2
Mar 25 09:07:33 lock-38 sshd[135052]: Invalid user loki from 49.235.81.23 port 51604
Mar 25 09:07:33 lock-38 sshd[135052]: Invalid user loki from 49.235.81.23 port 51604
Mar 25 09:07:33 lock-38 sshd[135052]: Failed password for invalid user loki from 49.235.81.23 port 51604 ssh2
...
2020-03-25 16:41:22
87.236.27.177 attackbotsspam
Port 80 (HTTP) access denied
2020-03-25 16:48:09
222.186.31.83 attackspambots
Mar 25 10:05:31 vmanager6029 sshd\[5348\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.83  user=root
Mar 25 10:05:33 vmanager6029 sshd\[5346\]: error: PAM: Authentication failure for root from 222.186.31.83
Mar 25 10:05:33 vmanager6029 sshd\[5349\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.83  user=root
2020-03-25 17:08:24
156.200.198.122 attackspambots
Brute force attempt
2020-03-25 16:40:21

Recently Reported IPs

186.46.220.98 123.178.210.142 36.138.85.38 34.156.6.176
20.169.84.24 34.62.75.201 94.126.225.181 188.188.125.97
188.188.68.20 188.188.117.228 43.98.184.126 36.139.162.104
86.149.185.73 95.108.213.191 216.180.246.26 91.196.152.164
68.186.212.123 36.137.207.109 195.96.139.16 118.114.157.116