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.64.0.0/10, 20.36.0.0/14, 20.33.0.0/16, 20.48.0.0/12, 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

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

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

OrgRoutingHandle: CHATU3-ARIN
OrgRoutingName:   Chaturmohta, Somesh 
OrgRoutingPhone:  +1-425-882-8080 
OrgRoutingEmail:  someshch@microsoft.com
OrgRoutingRef:    https://rdap.arin.net/registry/entity/CHATU3-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.171.78
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56339
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;20.65.171.78.			IN	A

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

;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Sep 17 05:00:20 CST 2026
;; MSG SIZE  rcvd: 105
Host info
Host 78.171.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 78.171.65.20.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
98.100.250.202 attack
[ssh] SSH attack
2020-07-29 17:34:33
41.38.44.180 attack
Jul 29 10:12:17 host sshd[25957]: Invalid user liyujiang from 41.38.44.180 port 57214
...
2020-07-29 17:45:27
49.145.42.13 attack
20/7/28@23:51:43: FAIL: Alarm-Network address from=49.145.42.13
...
2020-07-29 17:08:28
122.52.48.92 attackspambots
Brute-force attempt banned
2020-07-29 17:32:06
115.236.100.114 attackspambots
SSH brute-force attempt
2020-07-29 17:16:50
103.39.10.160 attackspambots
Port Scan detected!
...
2020-07-29 17:44:01
112.85.42.200 attackspam
Jul 29 11:21:45 jane sshd[32163]: Failed password for root from 112.85.42.200 port 33252 ssh2
Jul 29 11:21:50 jane sshd[32163]: Failed password for root from 112.85.42.200 port 33252 ssh2
...
2020-07-29 17:24:34
46.14.173.2 attackspambots
Jul 29 10:47:03 vserver sshd\[1974\]: Invalid user jayakumar from 46.14.173.2Jul 29 10:47:05 vserver sshd\[1974\]: Failed password for invalid user jayakumar from 46.14.173.2 port 55796 ssh2Jul 29 10:51:06 vserver sshd\[2007\]: Invalid user yliu from 46.14.173.2Jul 29 10:51:09 vserver sshd\[2007\]: Failed password for invalid user yliu from 46.14.173.2 port 33438 ssh2
...
2020-07-29 17:20:23
106.12.88.95 attack
Invalid user shenhan from 106.12.88.95 port 44608
2020-07-29 17:39:10
213.180.203.59 attackbots
[Wed Jul 29 14:22:36.719274 2020] [:error] [pid 1192:tid 139703724492544] [client 213.180.203.59:42522] [client 213.180.203.59] ModSecurity: Access denied with code 403 (phase 2). Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "696"] [id "920350"] [msg "Host header is a numeric IP address"] [data "103.27.207.197"] [severity "WARNING"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [hostname "103.27.207.197"] [uri "/"] [unique_id "XyEjvHHJSNX1MK11B3GAUwAAAOE"]
...
2020-07-29 17:25:36
198.55.109.217 attack
apache exploit attempt
2020-07-29 17:13:37
104.183.217.130 attackspambots
Invalid user ishihara from 104.183.217.130 port 41120
2020-07-29 17:28:19
193.70.39.135 attackspam
$f2bV_matches
2020-07-29 17:15:00
222.186.42.155 attackspam
Unauthorized connection attempt detected from IP address 222.186.42.155 to port 22
2020-07-29 17:35:33
196.52.43.62 attackspam
Unauthorized connection attempt detected from IP address 196.52.43.62 to port 2083
2020-07-29 17:41:05

Recently Reported IPs

64.233.190.95 2606:4700:10::6814:9268 2606:4700:10::6814:7690 34.78.224.200
31.70.77.215 102.220.161.102 194.103.139.33 193.235.141.126
34.135.189.108 117.153.22.187 138.91.108.245 3.22.187.122
223.67.46.7 113.56.194.122 27.247.205.13 27.152.58.87
43.226.182.184 64.34.87.5 112.9.104.140 13.89.125.87