City: San Antonio
Region: Texas
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
#
# 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.36.0.0/14, 20.64.0.0/10, 20.128.0.0/16, 20.33.0.0/16, 20.48.0.0/12, 20.40.0.0/13, 20.34.0.0/15
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: IPHOS5-ARIN
OrgTechName: IPHostmaster, IPHostmaster
OrgTechPhone: +1-425-538-6637
OrgTechEmail: iphostmaster@microsoft.com
OrgTechRef: https://rdap.arin.net/registry/entity/IPHOS5-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
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 9.10.3-P4-Ubuntu <<>> 20.65.137.167
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12523
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;20.65.137.167. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026041801 1800 900 604800 86400
;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Apr 19 03:00:06 CST 2026
;; MSG SIZE rcvd: 106167.137.65.20.in-addr.arpa domain name pointer azpdsg1s0zlq.stretchoid.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
167.137.65.20.in-addr.arpa name = azpdsg1s0zlq.stretchoid.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 49.235.35.12 | attack | Nov 3 11:01:36 plusreed sshd[29167]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.35.12 user=root Nov 3 11:01:38 plusreed sshd[29167]: Failed password for root from 49.235.35.12 port 38970 ssh2 ... |
2019-11-04 05:37:59 |
| 46.101.77.58 | attackbotsspam | Failed password for root from 46.101.77.58 port 49190 ssh2 |
2019-11-04 05:41:59 |
| 104.219.232.118 | attackspambots | 3 failed ftp login attempts in 3600s |
2019-11-04 05:50:19 |
| 51.75.143.32 | attackbotsspam | Nov 3 20:24:14 dedicated sshd[9452]: Invalid user shsf123 from 51.75.143.32 port 58002 |
2019-11-04 05:33:16 |
| 210.177.54.141 | attackbotsspam | Nov 3 21:46:29 ArkNodeAT sshd\[23036\]: Invalid user postfix from 210.177.54.141 Nov 3 21:46:29 ArkNodeAT sshd\[23036\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.177.54.141 Nov 3 21:46:31 ArkNodeAT sshd\[23036\]: Failed password for invalid user postfix from 210.177.54.141 port 49910 ssh2 |
2019-11-04 05:42:20 |
| 80.211.115.16 | attackbotsspam | Nov 3 18:07:35 firewall sshd[19670]: Failed password for invalid user kreo from 80.211.115.16 port 51128 ssh2 Nov 3 18:11:59 firewall sshd[19715]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.115.16 user=root Nov 3 18:12:01 firewall sshd[19715]: Failed password for root from 80.211.115.16 port 37796 ssh2 ... |
2019-11-04 05:35:33 |
| 139.180.134.138 | attackspambots | Nov 3 11:18:56 sachi sshd\[379\]: Invalid user com from 139.180.134.138 Nov 3 11:18:56 sachi sshd\[379\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.180.134.138 Nov 3 11:18:58 sachi sshd\[379\]: Failed password for invalid user com from 139.180.134.138 port 33649 ssh2 Nov 3 11:23:19 sachi sshd\[758\]: Invalid user 123456 from 139.180.134.138 Nov 3 11:23:19 sachi sshd\[758\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.180.134.138 |
2019-11-04 05:30:10 |
| 78.100.200.34 | attackspam | Unauthorised access (Nov 3) SRC=78.100.200.34 LEN=40 TTL=54 ID=43396 TCP DPT=8080 WINDOW=13454 SYN Unauthorised access (Nov 3) SRC=78.100.200.34 LEN=40 TTL=54 ID=43447 TCP DPT=8080 WINDOW=13454 SYN |
2019-11-04 05:41:23 |
| 5.23.79.3 | attack | Nov 3 21:55:10 lnxded63 sshd[10211]: Failed password for root from 5.23.79.3 port 56437 ssh2 Nov 3 21:58:58 lnxded63 sshd[10399]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.23.79.3 Nov 3 21:59:00 lnxded63 sshd[10399]: Failed password for invalid user stanchion from 5.23.79.3 port 47281 ssh2 |
2019-11-04 05:28:48 |
| 104.210.62.21 | attackspam | Nov 3 17:23:58 work-partkepr sshd\[22123\]: Invalid user sb from 104.210.62.21 port 29632 Nov 3 17:23:58 work-partkepr sshd\[22123\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.210.62.21 ... |
2019-11-04 05:43:29 |
| 157.245.69.186 | attackspam | Automatic report - XMLRPC Attack |
2019-11-04 05:53:16 |
| 159.203.74.227 | attack | SSH bruteforce |
2019-11-04 05:56:17 |
| 119.226.30.54 | attackbots | 2019-11-03T16:07:56.900646abusebot-8.cloudsearch.cf sshd\[13488\]: Invalid user siesa1 from 119.226.30.54 port 53722 |
2019-11-04 05:21:50 |
| 180.168.141.246 | attack | Nov 3 22:35:29 jane sshd[23588]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.168.141.246 Nov 3 22:35:31 jane sshd[23588]: Failed password for invalid user from 180.168.141.246 port 54802 ssh2 ... |
2019-11-04 05:52:24 |
| 99.243.34.136 | attackbots | IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/99.243.34.136/ CA - 1H : (19) Protection Against DDoS WordPress plugin : "odzyskiwanie danych help-dysk" IP Address Ranges by Country : CA NAME ASN : ASN812 IP : 99.243.34.136 CIDR : 99.243.0.0/17 PREFIX COUNT : 720 UNIQUE IP COUNT : 4040704 ATTACKS DETECTED ASN812 : 1H - 1 3H - 1 6H - 2 12H - 4 24H - 4 DateTime : 2019-11-03 15:28:47 INFO : Port MAX SCAN Scan Detected and Blocked by ADMIN - data recovery |
2019-11-04 05:41:06 |