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

;; QUESTION SECTION:
;20.65.201.49.			IN	A

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

;; Query time: 27 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 11 04:01:24 CST 2026
;; MSG SIZE  rcvd: 105
Host info
49.201.65.20.in-addr.arpa domain name pointer azpdsg6tzlqa.stretchoid.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
49.201.65.20.in-addr.arpa	name = azpdsg6tzlqa.stretchoid.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
223.240.84.49 attackspambots
Dec 28 22:33:02 sshgateway sshd\[6312\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.240.84.49  user=root
Dec 28 22:33:04 sshgateway sshd\[6312\]: Failed password for root from 223.240.84.49 port 55182 ssh2
Dec 28 22:37:56 sshgateway sshd\[6348\]: Invalid user mailnull from 223.240.84.49
2019-12-29 06:58:40
45.40.166.141 attack
ENG,WP GET /wp-login.php
GET /wp-login.php
2019-12-29 07:03:13
34.73.222.193 attackbotsspam
Automated report (2019-12-28T22:37:43+00:00). Misbehaving bot detected at this address.
2019-12-29 07:11:17
222.186.175.212 attack
2019-12-28T23:14:34.103316abusebot-2.cloudsearch.cf sshd[18410]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.212  user=root
2019-12-28T23:14:35.536154abusebot-2.cloudsearch.cf sshd[18410]: Failed password for root from 222.186.175.212 port 32922 ssh2
2019-12-28T23:14:38.141426abusebot-2.cloudsearch.cf sshd[18410]: Failed password for root from 222.186.175.212 port 32922 ssh2
2019-12-28T23:14:34.103316abusebot-2.cloudsearch.cf sshd[18410]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.212  user=root
2019-12-28T23:14:35.536154abusebot-2.cloudsearch.cf sshd[18410]: Failed password for root from 222.186.175.212 port 32922 ssh2
2019-12-28T23:14:38.141426abusebot-2.cloudsearch.cf sshd[18410]: Failed password for root from 222.186.175.212 port 32922 ssh2
2019-12-28T23:14:34.103316abusebot-2.cloudsearch.cf sshd[18410]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 
...
2019-12-29 07:15:21
106.13.120.176 attackspam
SSH Login Bruteforce
2019-12-29 06:51:12
82.212.60.75 attackspambots
Dec 28 23:37:57 MK-Soft-VM4 sshd[14163]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.212.60.75 
Dec 28 23:37:59 MK-Soft-VM4 sshd[14163]: Failed password for invalid user boaden from 82.212.60.75 port 41876 ssh2
...
2019-12-29 06:56:56
106.54.160.59 attack
Dec 28 23:35:35 MK-Soft-VM4 sshd[13128]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.160.59 
Dec 28 23:35:37 MK-Soft-VM4 sshd[13128]: Failed password for invalid user gp from 106.54.160.59 port 47176 ssh2
...
2019-12-29 07:06:12
189.91.239.194 attackbotsspam
3x Failed Password
2019-12-29 07:20:37
67.227.213.20 attackbotsspam
Automatic report - XMLRPC Attack
2019-12-29 07:07:10
68.171.212.2 attackspambots
Automatic report - XMLRPC Attack
2019-12-29 07:06:47
218.92.0.131 attackbots
2019-12-28T23:55:13.289766scmdmz1 sshd[27537]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.131  user=root
2019-12-28T23:55:15.335214scmdmz1 sshd[27537]: Failed password for root from 218.92.0.131 port 31438 ssh2
2019-12-28T23:55:18.684850scmdmz1 sshd[27537]: Failed password for root from 218.92.0.131 port 31438 ssh2
2019-12-28T23:55:13.289766scmdmz1 sshd[27537]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.131  user=root
2019-12-28T23:55:15.335214scmdmz1 sshd[27537]: Failed password for root from 218.92.0.131 port 31438 ssh2
2019-12-28T23:55:18.684850scmdmz1 sshd[27537]: Failed password for root from 218.92.0.131 port 31438 ssh2
2019-12-28T23:55:13.289766scmdmz1 sshd[27537]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.131  user=root
2019-12-28T23:55:15.335214scmdmz1 sshd[27537]: Failed password for root from 218.92.0.131 port 31438 ssh2
2019-12-28T23:55:
2019-12-29 07:11:55
176.185.218.124 attack
Lines containing failures of 176.185.218.124
Dec 23 12:39:03 shared01 sshd[19767]: Invalid user pi from 176.185.218.124 port 57200
Dec 23 12:39:03 shared01 sshd[19766]: Invalid user pi from 176.185.218.124 port 57194
Dec 23 12:39:03 shared01 sshd[19767]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.185.218.124
Dec 23 12:39:03 shared01 sshd[19766]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.185.218.124


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=176.185.218.124
2019-12-29 07:12:59
61.244.196.102 attackbots
C1,DEF GET /wp-login.php
2019-12-29 07:02:30
185.116.85.18 attackbotsspam
Unauthorized connection attempt detected from IP address 185.116.85.18 to port 445
2019-12-29 06:50:18
218.92.0.138 attackspambots
Dec 28 23:45:24 v22018076622670303 sshd\[3014\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.138  user=root
Dec 28 23:45:26 v22018076622670303 sshd\[3014\]: Failed password for root from 218.92.0.138 port 33704 ssh2
Dec 28 23:45:30 v22018076622670303 sshd\[3014\]: Failed password for root from 218.92.0.138 port 33704 ssh2
...
2019-12-29 06:45:43

Recently Reported IPs

223.74.233.119 183.253.115.229 183.251.245.83 183.229.91.130
183.229.47.144 183.221.102.176 183.198.102.170 183.197.46.225
180.233.64.7 180.233.64.148 123.13.12.83 120.82.84.247
120.239.66.100 120.230.64.64 120.230.22.84 120.219.245.96
120.211.187.251 120.207.165.98 119.2.160.15 116.114.65.124