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.64.0.0/10, 20.34.0.0/15, 20.40.0.0/13, 20.48.0.0/12, 20.36.0.0/14, 20.33.0.0/16, 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.202.50
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 5563
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;20.65.202.50.			IN	A

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

;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Oct 10 16:01:16 CST 2026
;; MSG SIZE  rcvd: 105
Host info
Host 50.202.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 50.202.65.20.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
178.128.108.19 attackspam
Dec  5 23:13:09 legacy sshd[6405]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.108.19
Dec  5 23:13:12 legacy sshd[6405]: Failed password for invalid user allaman from 178.128.108.19 port 57130 ssh2
Dec  5 23:19:42 legacy sshd[6748]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.108.19
...
2019-12-06 09:35:16
189.240.58.174 attackspam
Unauthorized connection attempt from IP address 189.240.58.174 on Port 445(SMB)
2019-12-06 09:42:11
119.29.203.106 attackbots
Dec  5 21:53:58 localhost sshd\[14848\]: Invalid user com from 119.29.203.106
Dec  5 21:53:58 localhost sshd\[14848\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.203.106
Dec  5 21:54:00 localhost sshd\[14848\]: Failed password for invalid user com from 119.29.203.106 port 37428 ssh2
Dec  5 22:00:35 localhost sshd\[15332\]: Invalid user nixie from 119.29.203.106
Dec  5 22:00:35 localhost sshd\[15332\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.203.106
...
2019-12-06 09:20:17
111.230.29.17 attackbots
F2B jail: sshd. Time: 2019-12-06 02:01:40, Reported by: VKReport
2019-12-06 09:13:46
185.31.163.237 attackspam
calcul.legrand.ru [185.31.163.237] - - [05/Dec/2019:22:50:33 +0900] "POST /images.php HTTP/1.1" 406 249 "-" "curl/7.58.0"
2019-12-06 09:50:22
45.125.66.183 attack
Rude login attack (12 tries in 1d)
2019-12-06 09:12:06
51.38.126.92 attackspam
Dec  5 22:00:28 MK-Soft-VM5 sshd[17412]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.126.92 
Dec  5 22:00:30 MK-Soft-VM5 sshd[17412]: Failed password for invalid user latyia from 51.38.126.92 port 59288 ssh2
...
2019-12-06 09:27:07
62.234.154.64 attack
Dec  6 02:38:21 localhost sshd\[12544\]: Invalid user miro from 62.234.154.64
Dec  6 02:38:21 localhost sshd\[12544\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.154.64
Dec  6 02:38:23 localhost sshd\[12544\]: Failed password for invalid user miro from 62.234.154.64 port 33976 ssh2
Dec  6 02:44:26 localhost sshd\[12842\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.154.64  user=www-data
Dec  6 02:44:28 localhost sshd\[12842\]: Failed password for www-data from 62.234.154.64 port 33456 ssh2
...
2019-12-06 09:47:31
81.28.100.96 attack
Dec  5 23:00:31 grey postfix/smtpd\[30310\]: NOQUEUE: reject: RCPT from smiling.shrewdmhealth.com\[81.28.100.96\]: 554 5.7.1 Service unavailable\; Client host \[81.28.100.96\] blocked using truncate.gbudb.net\; http://www.gbudb.com/truncate/ \[81.28.100.96\]\; from=\ to=\ proto=ESMTP helo=\
...
2019-12-06 09:28:42
176.110.120.250 attackspambots
Unauthorized connection attempt from IP address 176.110.120.250 on Port 445(SMB)
2019-12-06 09:39:15
172.81.250.132 attackbots
Dec  5 22:37:01 tuxlinux sshd[2880]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.81.250.132  user=root
Dec  5 22:37:03 tuxlinux sshd[2880]: Failed password for root from 172.81.250.132 port 43516 ssh2
Dec  5 22:37:01 tuxlinux sshd[2880]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.81.250.132  user=root
Dec  5 22:37:03 tuxlinux sshd[2880]: Failed password for root from 172.81.250.132 port 43516 ssh2
Dec  5 22:44:48 tuxlinux sshd[3074]: Invalid user edward from 172.81.250.132 port 60592
...
2019-12-06 09:15:05
27.254.90.106 attackspam
Dec  5 15:24:13 wbs sshd\[28952\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.254.90.106  user=root
Dec  5 15:24:16 wbs sshd\[28952\]: Failed password for root from 27.254.90.106 port 55808 ssh2
Dec  5 15:31:14 wbs sshd\[29605\]: Invalid user abby from 27.254.90.106
Dec  5 15:31:14 wbs sshd\[29605\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.254.90.106
Dec  5 15:31:16 wbs sshd\[29605\]: Failed password for invalid user abby from 27.254.90.106 port 32788 ssh2
2019-12-06 09:36:47
92.118.160.29 attack
firewall-block, port(s): 5909/tcp
2019-12-06 09:15:56
186.233.59.28 attack
firewall-block, port(s): 23/tcp
2019-12-06 09:34:50
213.6.8.38 attackbots
Dec  6 01:32:44 nextcloud sshd\[12471\]: Invalid user guest from 213.6.8.38
Dec  6 01:32:44 nextcloud sshd\[12471\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.6.8.38
Dec  6 01:32:47 nextcloud sshd\[12471\]: Failed password for invalid user guest from 213.6.8.38 port 38951 ssh2
...
2019-12-06 09:19:49

Recently Reported IPs

86.38.187.98 86.38.187.92 86.38.187.40 86.38.187.118
77.67.26.70 64.205.72.119 200.138.46.86 200.138.46.74
20.70.184.248 20.80.93.119 35.190.218.120 34.77.91.206
174.253.12.115 52.146.19.226 245.47.214.104 159.65.207.41
24.177.34.61 24.176.53.166 188.245.193.111 134.122.80.75