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: 40.74.0.0 - 40.125.127.255
CIDR: 40.112.0.0/13, 40.96.0.0/12, 40.80.0.0/12, 40.124.0.0/16, 40.120.0.0/14, 40.125.0.0/17, 40.74.0.0/15, 40.76.0.0/14
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
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: 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
OrgRoutingHandle: CHATU3-ARIN
OrgRoutingName: Chaturmohta, Somesh
OrgRoutingPhone: +1-425-882-8080
OrgRoutingEmail: someshch@microsoft.com
OrgRoutingRef: https://rdap.arin.net/registry/entity/CHATU3-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.80.46
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12420
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;40.124.80.46. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026091802 1800 900 604800 86400
;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Sep 19 09:30:30 CST 2026
;; MSG SIZE rcvd: 105
46.80.124.40.in-addr.arpa domain name pointer azpdsewwxqqp.stretchoid.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
46.80.124.40.in-addr.arpa name = azpdsewwxqqp.stretchoid.com.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 212.237.63.28 | attackbotsspam | Unauthorized connection attempt detected from IP address 212.237.63.28 to port 2220 [J] |
2020-01-18 02:51:52 |
| 68.183.84.44 | attack | Jan 17 18:02:48 mx01 sshd[22899]: Invalid user br from 68.183.84.44 Jan 17 18:02:48 mx01 sshd[22899]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.84.44 Jan 17 18:02:50 mx01 sshd[22899]: Failed password for invalid user br from 68.183.84.44 port 42304 ssh2 Jan 17 18:02:50 mx01 sshd[22899]: Received disconnect from 68.183.84.44: 11: Bye Bye [preauth] Jan 17 18:18:53 mx01 sshd[25072]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.84.44 user=r.r Jan 17 18:18:55 mx01 sshd[25072]: Failed password for r.r from 68.183.84.44 port 49388 ssh2 Jan 17 18:18:55 mx01 sshd[25072]: Received disconnect from 68.183.84.44: 11: Bye Bye [preauth] Jan 17 18:23:01 mx01 sshd[25591]: Invalid user deploy from 68.183.84.44 Jan 17 18:23:01 mx01 sshd[25591]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.84.44 Jan 17 18:23:03 mx01 sshd[25591]: Failed ........ ------------------------------- |
2020-01-18 02:44:23 |
| 112.162.191.160 | attackspambots | $f2bV_matches |
2020-01-18 02:40:53 |
| 106.13.84.151 | attackbots | Unauthorized connection attempt detected from IP address 106.13.84.151 to port 2220 [J] |
2020-01-18 02:42:11 |
| 112.78.1.247 | attack | SSH Login Bruteforce |
2020-01-18 02:25:47 |
| 203.148.20.254 | attackbotsspam | Invalid user ftpupload from 203.148.20.254 port 36672 |
2020-01-18 02:29:50 |
| 218.92.0.158 | attack | Jan 17 19:14:45 legacy sshd[10186]: Failed password for root from 218.92.0.158 port 47156 ssh2 Jan 17 19:14:58 legacy sshd[10186]: error: maximum authentication attempts exceeded for root from 218.92.0.158 port 47156 ssh2 [preauth] Jan 17 19:15:04 legacy sshd[10194]: Failed password for root from 218.92.0.158 port 14441 ssh2 ... |
2020-01-18 02:16:35 |
| 122.114.239.229 | attackbotsspam | Invalid user deploy from 122.114.239.229 port 37022 |
2020-01-18 02:38:43 |
| 112.17.190.29 | attackbotsspam | Unauthorized connection attempt detected from IP address 112.17.190.29 to port 2220 [J] |
2020-01-18 02:41:07 |
| 206.189.181.128 | attackbotsspam | Unauthorized connection attempt detected from IP address 206.189.181.128 to port 2220 [J] |
2020-01-18 02:24:25 |
| 220.76.77.121 | attackbotsspam | Invalid user nagios from 220.76.77.121 port 42534 |
2020-01-18 02:51:04 |
| 58.62.207.50 | attackspambots | Unauthorized connection attempt detected from IP address 58.62.207.50 to port 2220 [J] |
2020-01-18 02:45:37 |
| 153.101.244.134 | attackspambots | Unauthorized connection attempt detected from IP address 153.101.244.134 to port 2220 [J] |
2020-01-18 02:35:23 |
| 84.109.248.104 | attack | Jan 17 17:15:03 icinga sshd[25151]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.109.248.104 Jan 17 17:15:05 icinga sshd[25151]: Failed password for invalid user maxin from 84.109.248.104 port 44346 ssh2 ... |
2020-01-18 02:23:06 |
| 62.234.95.148 | attack | Unauthorized connection attempt detected from IP address 62.234.95.148 to port 2220 [J] |
2020-01-18 02:26:53 |