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: San Antonio

Region: Texas

Country: United States

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:       20.33.0.0 - 20.128.255.255
CIDR:           20.34.0.0/15, 20.33.0.0/16, 20.48.0.0/12, 20.64.0.0/10, 20.36.0.0/14, 20.40.0.0/13, 20.128.0.0/16
NetName:        MSFT
NetHandle:      NET-20-33-0-0-1
Parent:         NET20 (NET-20-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   Microsoft Corporation (MSFT)
RegDate:        2017-10-18
Updated:        2021-12-14
Ref:            https://rdap.arin.net/registry/ip/20.33.0.0



OrgName:        Microsoft Corporation
OrgId:          MSFT
Address:        One Microsoft Way
City:           Redmond
StateProv:      WA
PostalCode:     98052
Country:        US
RegDate:        1998-07-10
Updated:        2025-06-10
Comment:        To report suspected security issues specific to traffic emanating from Microsoft online services, including the distribution of malicious content or other illicit or illegal material through a Microsoft online service, please submit reports to:
Comment:        * https://cert.microsoft.com.  
Comment:        
Comment:        For SPAM and other abuse issues, such as Microsoft Accounts, please contact:
Comment:        * abuse@microsoft.com.  
Comment:        
Comment:        To report security vulnerabilities in Microsoft products and services, please contact:
Comment:        * secure@microsoft.com.  
Comment:        
Comment:        For legal and law enforcement-related requests, please contact:
Comment:        * msndcc@microsoft.com
Comment:        
Comment:        For routing, peering or DNS issues, please 
Comment:        contact:
Comment:        * IOC@microsoft.com
Ref:            https://rdap.arin.net/registry/entity/MSFT


OrgTechHandle: BEDAR6-ARIN
OrgTechName:   Bedard, Dawn 
OrgTechPhone:  +1-425-538-6637 
OrgTechEmail:  dabedard@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/BEDAR6-ARIN

OrgTechHandle: MRPD-ARIN
OrgTechName:   Microsoft Routing, Peering, and DNS
OrgTechPhone:  +1-425-882-8080 
OrgTechEmail:  IOC@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/MRPD-ARIN

OrgTechHandle: SINGH683-ARIN
OrgTechName:   Singh, Prachi 
OrgTechPhone:  +1-425-707-5601 
OrgTechEmail:  pracsin@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/SINGH683-ARIN

OrgRoutingHandle: CHATU3-ARIN
OrgRoutingName:   Chaturmohta, Somesh 
OrgRoutingPhone:  +1-425-882-8080 
OrgRoutingEmail:  someshch@microsoft.com
OrgRoutingRef:    https://rdap.arin.net/registry/entity/CHATU3-ARIN

OrgTechHandle: IPHOS5-ARIN
OrgTechName:   IPHostmaster, IPHostmaster 
OrgTechPhone:  +1-425-538-6637 
OrgTechEmail:  iphostmaster@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/IPHOS5-ARIN

OrgAbuseHandle: MAC74-ARIN
OrgAbuseName:   Microsoft Abuse Contact
OrgAbusePhone:  +1-425-882-8080 
OrgAbuseEmail:  abuse@microsoft.com
OrgAbuseRef:    https://rdap.arin.net/registry/entity/MAC74-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.
#
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 20.65.178.152
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 34888
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;20.65.178.152.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Oct 12 08:30:41 CST 2026
;; MSG SIZE  rcvd: 106
Host info
Host 152.178.65.20.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 152.178.65.20.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
59.145.221.103 attack
Dec  9 22:54:05 * sshd[32093]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.145.221.103
Dec  9 22:54:07 * sshd[32093]: Failed password for invalid user dave from 59.145.221.103 port 54543 ssh2
2019-12-10 06:02:29
45.67.14.162 attack
Dec  9 15:14:03 XXX sshd[34073]: Invalid user ubnt from 45.67.14.162 port 49052
2019-12-10 05:53:47
31.44.177.83 attack
Botnet spam UTC Dec 9 18:36:34 from= proto=ESMTP helo=
2019-12-10 05:36:23
185.17.120.51 attackspambots
fell into ViewStateTrap:vaduz
2019-12-10 06:06:44
104.161.34.97 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2019-12-10 06:12:47
104.206.128.10 attack
52311/tcp 21/tcp 5432/tcp...
[2019-10-11/12-08]45pkt,12pt.(tcp),1pt.(udp)
2019-12-10 05:48:37
183.239.44.164 attack
Dec  9 20:19:38 [host] sshd[28506]: Invalid user ching from 183.239.44.164
Dec  9 20:19:38 [host] sshd[28506]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.239.44.164
Dec  9 20:19:40 [host] sshd[28506]: Failed password for invalid user ching from 183.239.44.164 port 33956 ssh2
2019-12-10 05:33:59
162.243.94.34 attackspam
Dec  9 22:39:54 sso sshd[18667]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.243.94.34
Dec  9 22:39:56 sso sshd[18667]: Failed password for invalid user squid from 162.243.94.34 port 53131 ssh2
...
2019-12-10 05:58:00
52.142.216.102 attackspam
Dec  9 22:33:06 vpn01 sshd[21155]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.142.216.102
Dec  9 22:33:08 vpn01 sshd[21155]: Failed password for invalid user apache from 52.142.216.102 port 36344 ssh2
...
2019-12-10 05:44:38
37.49.231.116 attackspambots
Dec  9 17:59:49 debian-2gb-vpn-nbg1-1 kernel: [281976.471785] [UFW BLOCK] IN=eth0 OUT= MAC=96:00:00:38:96:44:d2:74:7f:6e:37:e3:08:00 SRC=37.49.231.116 DST=78.46.192.101 LEN=53 TOS=0x00 PREC=0x00 TTL=118 ID=2878 PROTO=UDP SPT=60621 DPT=69 LEN=33
2019-12-10 06:05:22
158.69.204.172 attackspam
Dec  9 22:14:09 sauna sshd[90166]: Failed password for news from 158.69.204.172 port 54278 ssh2
...
2019-12-10 05:58:26
177.1.214.207 attackbots
Dec  9 22:59:34 meumeu sshd[23003]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.1.214.207 
Dec  9 22:59:36 meumeu sshd[23003]: Failed password for invalid user uploader from 177.1.214.207 port 38367 ssh2
Dec  9 23:08:12 meumeu sshd[24211]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.1.214.207 
...
2019-12-10 06:09:31
148.70.136.94 attackspambots
SSH bruteforce
2019-12-10 06:11:55
45.143.221.30 attack
SIPVicious Scanner Detection, PTR: PTR record not found
2019-12-10 05:49:21
111.231.144.219 attack
$f2bV_matches
2019-12-10 06:07:39

Recently Reported IPs

193.34.161.34 193.176.86.122 192.61.1.87 153.117.40.83
192.69.145.160 192.26.97.174 192.251.59.55 192.6.96.187
192.254.70.17 192.248.142.52 192.188.47.70 192.168.8.201
192.168.134.130 192.168.123.180 192.168.17.170 191.154.228.45
192.168.63.30 192.2.40.13 190.170.17.92 85.217.149.55