城市(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.112.0.0/13, 40.120.0.0/14, 40.76.0.0/14, 40.124.0.0/16, 40.96.0.0/12, 40.74.0.0/15, 40.125.0.0/17, 40.80.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
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 <<>> 40.124.81.207
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30736
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;40.124.81.207. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026103101 1800 900 604800 86400
;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Nov 01 09:00:35 CST 2026
;; MSG SIZE rcvd: 106207.81.124.40.in-addr.arpa domain name pointer azpdsgrbkcck.stretchoid.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
207.81.124.40.in-addr.arpa name = azpdsgrbkcck.stretchoid.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 164.132.54.215 | attack | Mar 5 05:43:32 pixelmemory sshd[16158]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.54.215 Mar 5 05:43:35 pixelmemory sshd[16158]: Failed password for invalid user ts3 from 164.132.54.215 port 41130 ssh2 Mar 5 06:30:03 pixelmemory sshd[23547]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.54.215 ... |
2020-03-06 02:24:30 |
| 173.8.39.117 | attackspam | Telnet/23 MH Probe, Scan, BF, Hack - |
2020-03-06 02:56:29 |
| 179.99.2.155 | attackbots | Unauthorized connection attempt from IP address 179.99.2.155 on Port 445(SMB) |
2020-03-06 02:59:28 |
| 45.125.65.35 | attack | Mar 5 18:25:55 mail postfix/smtpd[21951]: warning: unknown[45.125.65.35]: SASL LOGIN authentication failed: generic failure Mar 5 18:32:30 mail postfix/smtpd[21977]: warning: unknown[45.125.65.35]: SASL LOGIN authentication failed: generic failure Mar 5 18:35:27 mail postfix/smtpd[21979]: warning: unknown[45.125.65.35]: SASL LOGIN authentication failed: generic failure ... |
2020-03-06 02:38:47 |
| 120.132.30.27 | attack | 2020-03-05T17:45:51.187561shield sshd\[14924\]: Invalid user phuket from 120.132.30.27 port 59854 2020-03-05T17:45:51.192292shield sshd\[14924\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.132.30.27 2020-03-05T17:45:53.298074shield sshd\[14924\]: Failed password for invalid user phuket from 120.132.30.27 port 59854 ssh2 2020-03-05T17:51:52.352540shield sshd\[16147\]: Invalid user doi from 120.132.30.27 port 42512 2020-03-05T17:51:52.360723shield sshd\[16147\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.132.30.27 |
2020-03-06 02:27:29 |
| 115.79.61.20 | attackbots | firewall-block, port(s): 445/tcp |
2020-03-06 02:32:23 |
| 122.160.95.104 | attackspam | Unauthorized connection attempt from IP address 122.160.95.104 on Port 445(SMB) |
2020-03-06 02:30:36 |
| 118.171.108.224 | attack | Unauthorized connection attempt from IP address 118.171.108.224 on Port 445(SMB) |
2020-03-06 02:47:20 |
| 164.132.44.25 | attackbotsspam | Oct 21 10:20:16 odroid64 sshd\[16319\]: User root from 164.132.44.25 not allowed because not listed in AllowUsers Oct 21 10:20:16 odroid64 sshd\[16319\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.44.25 user=root Oct 21 10:20:18 odroid64 sshd\[16319\]: Failed password for invalid user root from 164.132.44.25 port 36444 ssh2 Oct 21 10:20:16 odroid64 sshd\[16319\]: User root from 164.132.44.25 not allowed because not listed in AllowUsers Oct 21 10:20:16 odroid64 sshd\[16319\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.44.25 user=root Oct 21 10:20:18 odroid64 sshd\[16319\]: Failed password for invalid user root from 164.132.44.25 port 36444 ssh2 Feb 3 20:17:57 odroid64 sshd\[6767\]: Invalid user archiva from 164.132.44.25 Feb 3 20:17:57 odroid64 sshd\[6767\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.44.25 Feb 28 01:4 ... |
2020-03-06 02:29:09 |
| 2a03:2880:11ff:9::face:b00c | attack | Fail2Ban Ban Triggered |
2020-03-06 02:47:37 |
| 129.28.154.240 | attack | suspicious action Thu, 05 Mar 2020 10:32:53 -0300 |
2020-03-06 02:49:59 |
| 62.234.156.24 | attackspambots | Mar 5 13:14:44 NPSTNNYC01T sshd[15773]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.156.24 Mar 5 13:14:46 NPSTNNYC01T sshd[15773]: Failed password for invalid user robi from 62.234.156.24 port 45980 ssh2 Mar 5 13:22:30 NPSTNNYC01T sshd[16259]: Failed password for root from 62.234.156.24 port 43548 ssh2 ... |
2020-03-06 02:33:45 |
| 164.132.81.106 | attackbotsspam | Nov 11 08:53:24 odroid64 sshd\[15379\]: Invalid user fritsvold from 164.132.81.106 Nov 11 08:53:24 odroid64 sshd\[15379\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.81.106 Jan 13 20:14:17 odroid64 sshd\[22691\]: User root from 164.132.81.106 not allowed because not listed in AllowUsers Jan 13 20:14:17 odroid64 sshd\[22691\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.81.106 user=root ... |
2020-03-06 02:22:06 |
| 109.110.52.77 | attackspam | Mar 5 18:19:00 localhost sshd[25958]: Invalid user alotrolado2001 from 109.110.52.77 port 56280 Mar 5 18:19:00 localhost sshd[25958]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.110.52.77 Mar 5 18:19:00 localhost sshd[25958]: Invalid user alotrolado2001 from 109.110.52.77 port 56280 Mar 5 18:19:02 localhost sshd[25958]: Failed password for invalid user alotrolado2001 from 109.110.52.77 port 56280 ssh2 Mar 5 18:22:51 localhost sshd[26388]: Invalid user ftpuser from 109.110.52.77 port 54050 ... |
2020-03-06 02:50:15 |
| 164.132.107.245 | attackspam | Nov 7 00:19:58 odroid64 sshd\[7270\]: User root from 164.132.107.245 not allowed because not listed in AllowUsers Nov 7 00:19:58 odroid64 sshd\[7270\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.107.245 user=root Jan 29 09:48:18 odroid64 sshd\[18692\]: Invalid user prasun from 164.132.107.245 Jan 29 09:48:18 odroid64 sshd\[18692\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.107.245 Mar 2 06:48:13 odroid64 sshd\[11045\]: User saned from 164.132.107.245 not allowed because not listed in AllowUsers Mar 2 06:48:13 odroid64 sshd\[11045\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.107.245 user=saned ... |
2020-03-06 02:50:46 |