城市(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: 40.74.0.0 - 40.125.127.255
CIDR: 40.125.0.0/17, 40.112.0.0/13, 40.80.0.0/12, 40.124.0.0/16, 40.120.0.0/14, 40.74.0.0/15, 40.76.0.0/14, 40.96.0.0/12
NetName: MSFT
NetHandle: NET-40-74-0-0-1
Parent: NET40 (NET-40-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Microsoft Corporation (MSFT)
RegDate: 2015-02-23
Updated: 2021-12-14
Ref: https://rdap.arin.net/registry/ip/40.74.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
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
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
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
#
# 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 <<>> 40.124.173.157
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 6136
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;40.124.173.157. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026071403 1800 900 604800 86400
;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jul 15 07:30:31 CST 2026
;; MSG SIZE rcvd: 107157.173.124.40.in-addr.arpa domain name pointer azpdsgz1e1m2.stretchoid.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
157.173.124.40.in-addr.arpa name = azpdsgz1e1m2.stretchoid.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 107.170.18.163 | attackbotsspam | $f2bV_matches |
2019-07-22 23:26:53 |
| 188.166.41.192 | attack | Jul 22 19:06:49 yabzik sshd[18358]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.41.192 Jul 22 19:06:51 yabzik sshd[18358]: Failed password for invalid user cloud from 188.166.41.192 port 43902 ssh2 Jul 22 19:11:28 yabzik sshd[20159]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.41.192 |
2019-07-23 00:14:38 |
| 14.161.17.230 | attack | 3389BruteforceFW23 |
2019-07-22 22:57:21 |
| 77.77.217.119 | attackbots | Jul 22 17:53:38 eventyay sshd[17062]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.77.217.119 Jul 22 17:53:41 eventyay sshd[17062]: Failed password for invalid user lexis from 77.77.217.119 port 6025 ssh2 Jul 22 17:58:41 eventyay sshd[18272]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.77.217.119 ... |
2019-07-23 00:00:53 |
| 132.145.32.73 | attackbotsspam | Looking for resource vulnerabilities |
2019-07-22 22:40:36 |
| 165.227.209.96 | attackbots | Jul 22 15:49:27 OPSO sshd\[9380\]: Invalid user pr from 165.227.209.96 port 50008 Jul 22 15:49:27 OPSO sshd\[9380\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.209.96 Jul 22 15:49:28 OPSO sshd\[9380\]: Failed password for invalid user pr from 165.227.209.96 port 50008 ssh2 Jul 22 15:54:58 OPSO sshd\[10197\]: Invalid user test5 from 165.227.209.96 port 45724 Jul 22 15:54:58 OPSO sshd\[10197\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.209.96 |
2019-07-22 22:53:20 |
| 46.101.10.42 | attack | Jul 22 17:05:21 eventyay sshd[5067]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.10.42 Jul 22 17:05:23 eventyay sshd[5067]: Failed password for invalid user ban from 46.101.10.42 port 50512 ssh2 Jul 22 17:09:39 eventyay sshd[6116]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.10.42 ... |
2019-07-22 23:12:02 |
| 220.194.237.43 | attackbots | 22.07.2019 15:30:41 Connection to port 6380 blocked by firewall |
2019-07-22 23:40:46 |
| 178.128.84.122 | attackbots | 2019-07-22T14:56:46.199317abusebot-5.cloudsearch.cf sshd\[27440\]: Invalid user roberto from 178.128.84.122 port 55742 |
2019-07-22 23:40:01 |
| 177.91.194.70 | attack | $f2bV_matches |
2019-07-22 22:50:07 |
| 211.181.237.92 | attackbots | Unauthorised access (Jul 22) SRC=211.181.237.92 LEN=52 TTL=106 ID=19954 DF TCP DPT=445 WINDOW=8192 SYN |
2019-07-22 23:04:26 |
| 182.61.34.79 | attackspam | Jul 22 15:20:55 ArkNodeAT sshd\[7363\]: Invalid user proftpd from 182.61.34.79 Jul 22 15:20:55 ArkNodeAT sshd\[7363\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.34.79 Jul 22 15:20:57 ArkNodeAT sshd\[7363\]: Failed password for invalid user proftpd from 182.61.34.79 port 18469 ssh2 |
2019-07-22 23:23:37 |
| 46.239.15.242 | attackspam | firewall-block, port(s): 2323/tcp |
2019-07-23 00:10:12 |
| 123.112.196.68 | attackspambots | [portscan] Port scan |
2019-07-22 23:17:11 |
| 185.220.101.29 | attackbotsspam | Jul 22 16:47:08 km20725 sshd\[1728\]: Failed password for root from 185.220.101.29 port 43161 ssh2Jul 22 16:47:11 km20725 sshd\[1728\]: Failed password for root from 185.220.101.29 port 43161 ssh2Jul 22 16:47:14 km20725 sshd\[1728\]: Failed password for root from 185.220.101.29 port 43161 ssh2Jul 22 16:47:17 km20725 sshd\[1728\]: Failed password for root from 185.220.101.29 port 43161 ssh2 ... |
2019-07-22 22:54:29 |