城市(city): San Antonio
省份(region): Texas
国家(country): United States
运营商(isp): 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.33.0.0/16, 20.48.0.0/12, 20.34.0.0/15, 20.40.0.0/13, 20.128.0.0/16, 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: IPHOS5-ARIN
OrgTechName: IPHostmaster, IPHostmaster
OrgTechPhone: +1-425-538-6637
OrgTechEmail: iphostmaster@microsoft.com
OrgTechRef: https://rdap.arin.net/registry/entity/IPHOS5-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
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: SINGH683-ARIN
OrgTechName: Singh, Prachi
OrgTechPhone: +1-425-707-5601
OrgTechEmail: pracsin@microsoft.com
OrgTechRef: https://rdap.arin.net/registry/entity/SINGH683-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.193.155
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 41315
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;20.65.193.155. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026012401 1800 900 604800 86400
;; Query time: 5 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 25 04:00:20 CST 2026
;; MSG SIZE rcvd: 106155.193.65.20.in-addr.arpa domain name pointer azpdss8w51fx.stretchoid.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
155.193.65.20.in-addr.arpa name = azpdss8w51fx.stretchoid.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 222.186.30.248 | attack | Apr 8 00:41:52 server sshd[26425]: Failed password for root from 222.186.30.248 port 24959 ssh2 Apr 8 00:41:54 server sshd[26425]: Failed password for root from 222.186.30.248 port 24959 ssh2 Apr 8 00:41:57 server sshd[26425]: Failed password for root from 222.186.30.248 port 24959 ssh2 |
2020-04-08 06:42:19 |
| 157.230.42.206 | attackspam | Apr 8 03:10:49 gw1 sshd[14348]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.42.206 Apr 8 03:10:51 gw1 sshd[14348]: Failed password for invalid user jony from 157.230.42.206 port 49772 ssh2 ... |
2020-04-08 06:23:09 |
| 103.224.157.233 | attackspambots | Attempted connection to port 1433. |
2020-04-08 06:40:33 |
| 191.242.244.173 | attackbotsspam | Unauthorized connection attempt from IP address 191.242.244.173 on Port 445(SMB) |
2020-04-08 06:26:50 |
| 223.171.32.66 | attack | prod8 ... |
2020-04-08 06:30:39 |
| 41.223.4.155 | attack | k+ssh-bruteforce |
2020-04-08 06:35:50 |
| 178.60.39.163 | attackbotsspam | SASL PLAIN auth failed: ruser=... |
2020-04-08 06:11:24 |
| 103.10.30.207 | attackbotsspam | Apr 7 18:42:15 ws12vmsma01 sshd[7273]: Invalid user user from 103.10.30.207 Apr 7 18:42:17 ws12vmsma01 sshd[7273]: Failed password for invalid user user from 103.10.30.207 port 55318 ssh2 Apr 7 18:45:10 ws12vmsma01 sshd[7774]: Invalid user server from 103.10.30.207 ... |
2020-04-08 06:25:27 |
| 92.33.9.202 | attackbots | Automatic report - XMLRPC Attack |
2020-04-08 06:12:57 |
| 179.232.1.252 | attack | Apr 8 00:01:31 host01 sshd[13168]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.232.1.252 Apr 8 00:01:34 host01 sshd[13168]: Failed password for invalid user test from 179.232.1.252 port 35482 ssh2 Apr 8 00:06:54 host01 sshd[14357]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.232.1.252 ... |
2020-04-08 06:07:55 |
| 183.245.83.174 | attackbots | Attempted connection to port 1433. |
2020-04-08 06:34:01 |
| 116.22.199.20 | attack | Attempted connection to port 445. |
2020-04-08 06:37:22 |
| 111.231.109.151 | attackbotsspam | $f2bV_matches |
2020-04-08 06:39:23 |
| 222.186.15.114 | attack | Apr 8 00:21:38 vserver sshd\[8823\]: Failed password for root from 222.186.15.114 port 31339 ssh2Apr 8 00:21:40 vserver sshd\[8823\]: Failed password for root from 222.186.15.114 port 31339 ssh2Apr 8 00:21:42 vserver sshd\[8823\]: Failed password for root from 222.186.15.114 port 31339 ssh2Apr 8 00:28:58 vserver sshd\[8871\]: Failed password for root from 222.186.15.114 port 54194 ssh2 ... |
2020-04-08 06:31:27 |
| 96.27.249.5 | attackbots | Apr 8 00:16:57 srv-ubuntu-dev3 sshd[107960]: Invalid user test from 96.27.249.5 Apr 8 00:16:57 srv-ubuntu-dev3 sshd[107960]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=96.27.249.5 Apr 8 00:16:57 srv-ubuntu-dev3 sshd[107960]: Invalid user test from 96.27.249.5 Apr 8 00:16:59 srv-ubuntu-dev3 sshd[107960]: Failed password for invalid user test from 96.27.249.5 port 58762 ssh2 Apr 8 00:20:11 srv-ubuntu-dev3 sshd[108473]: Invalid user pvkii from 96.27.249.5 Apr 8 00:20:11 srv-ubuntu-dev3 sshd[108473]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=96.27.249.5 Apr 8 00:20:11 srv-ubuntu-dev3 sshd[108473]: Invalid user pvkii from 96.27.249.5 Apr 8 00:20:12 srv-ubuntu-dev3 sshd[108473]: Failed password for invalid user pvkii from 96.27.249.5 port 57596 ssh2 Apr 8 00:23:17 srv-ubuntu-dev3 sshd[108984]: Invalid user test from 96.27.249.5 ... |
2020-04-08 06:35:18 |