城市(city): Dulles Town Center
省份(region): Virginia
国家(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.128.0.0/16, 20.64.0.0/10, 20.48.0.0/12, 20.33.0.0/16, 20.34.0.0/15, 20.40.0.0/13, 20.36.0.0/14
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 9.10.3-P4-Ubuntu <<>> 20.83.163.76
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46389
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;20.83.163.76. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026100200 1800 900 604800 86400
;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Oct 02 14:01:24 CST 2026
;; MSG SIZE rcvd: 105
76.163.83.20.in-addr.arpa domain name pointer azpdeskznp5j.stretchoid.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
76.163.83.20.in-addr.arpa name = azpdeskznp5j.stretchoid.com.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 149.202.164.82 | attack | Jan 3 19:45:43 MK-Soft-VM8 sshd[6024]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.202.164.82 Jan 3 19:45:45 MK-Soft-VM8 sshd[6024]: Failed password for invalid user Ruut from 149.202.164.82 port 45432 ssh2 ... |
2020-01-04 03:27:15 |
| 109.169.0.110 | attack | SpamReport |
2020-01-04 03:37:51 |
| 125.64.94.211 | attackbots | 03.01.2020 18:31:42 Connection to port 5984 blocked by firewall |
2020-01-04 03:33:54 |
| 35.187.67.110 | attack | Time: Fri Jan 3 09:41:17 2020 -0300 IP: 35.187.67.110 (US/United States/110.67.187.35.bc.googleusercontent.com) Failures: 20 (WordPressBruteForcePOST) Interval: 3600 seconds Blocked: Permanent Block |
2020-01-04 03:26:09 |
| 107.174.149.19 | attackbotsspam | 1,47-05/05 [bc03/m102] PostRequest-Spammer scoring: Dodoma |
2020-01-04 03:57:29 |
| 159.224.226.164 | attackspambots | 159.224.226.164 has been banned for [spam] ... |
2020-01-04 03:27:03 |
| 222.82.250.4 | attackspambots | Jan 3 15:15:23 lnxweb61 sshd[9367]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.82.250.4 |
2020-01-04 03:44:42 |
| 149.202.18.41 | attackspambots | 5060/udp [2020-01-03]1pkt |
2020-01-04 03:23:17 |
| 185.156.73.52 | attackspambots | 01/03/2020-14:05:55.541608 185.156.73.52 Protocol: 6 ET SCAN NMAP -sS window 1024 |
2020-01-04 03:33:03 |
| 114.88.158.139 | attack | Dec 12 16:42:36 ms-srv sshd[10626]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.88.158.139 Dec 12 16:42:38 ms-srv sshd[10626]: Failed password for invalid user asterisk from 114.88.158.139 port 58275 ssh2 |
2020-01-04 03:46:40 |
| 2001:e68:506f:97d6:1e5f:2bff:fe36:2b30 | attackbotsspam | Hacked my HitBTC account |
2020-01-04 03:50:28 |
| 119.206.86.8 | attack | Jan 3 12:59:18 system,error,critical: login failure for user admin from 119.206.86.8 via telnet Jan 3 12:59:20 system,error,critical: login failure for user root from 119.206.86.8 via telnet Jan 3 12:59:21 system,error,critical: login failure for user admin from 119.206.86.8 via telnet Jan 3 12:59:26 system,error,critical: login failure for user root from 119.206.86.8 via telnet Jan 3 12:59:28 system,error,critical: login failure for user root from 119.206.86.8 via telnet Jan 3 12:59:30 system,error,critical: login failure for user admin from 119.206.86.8 via telnet Jan 3 12:59:35 system,error,critical: login failure for user root from 119.206.86.8 via telnet Jan 3 12:59:37 system,error,critical: login failure for user root from 119.206.86.8 via telnet Jan 3 12:59:39 system,error,critical: login failure for user tech from 119.206.86.8 via telnet Jan 3 12:59:44 system,error,critical: login failure for user service from 119.206.86.8 via telnet |
2020-01-04 03:49:20 |
| 211.106.172.50 | attackspambots | $f2bV_matches |
2020-01-04 03:48:05 |
| 203.109.45.228 | attackbots | Unauthorized connection attempt from IP address 203.109.45.228 on Port 445(SMB) |
2020-01-04 03:30:12 |
| 27.128.175.209 | attack | SSH Brute-Force reported by Fail2Ban |
2020-01-04 03:38:43 |