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.76.0.0/14, 40.124.0.0/16, 40.120.0.0/14, 40.125.0.0/17, 40.74.0.0/15, 40.80.0.0/12, 40.112.0.0/13, 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
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.178.103
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54710
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;40.124.178.103. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026092601 1800 900 604800 86400
;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Sep 27 05:00:15 CST 2026
;; MSG SIZE rcvd: 107103.178.124.40.in-addr.arpa domain name pointer azpdsgp4e48c.stretchoid.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
103.178.124.40.in-addr.arpa name = azpdsgp4e48c.stretchoid.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 190.145.78.66 | attackspam | Mar 26 09:52:36 icinga sshd[35867]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.145.78.66 Mar 26 09:52:38 icinga sshd[35867]: Failed password for invalid user is from 190.145.78.66 port 55096 ssh2 Mar 26 10:00:59 icinga sshd[49633]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.145.78.66 ... |
2020-03-26 19:53:57 |
| 51.68.174.177 | attackspam | Mar 26 07:35:10 ip-172-31-62-245 sshd\[7796\]: Invalid user giosue from 51.68.174.177\ Mar 26 07:35:13 ip-172-31-62-245 sshd\[7796\]: Failed password for invalid user giosue from 51.68.174.177 port 40506 ssh2\ Mar 26 07:39:07 ip-172-31-62-245 sshd\[7928\]: Invalid user gabi from 51.68.174.177\ Mar 26 07:39:09 ip-172-31-62-245 sshd\[7928\]: Failed password for invalid user gabi from 51.68.174.177 port 56522 ssh2\ Mar 26 07:43:03 ip-172-31-62-245 sshd\[7997\]: Invalid user hara from 51.68.174.177\ |
2020-03-26 19:27:54 |
| 202.77.105.100 | attack | Mar 26 12:43:12 ArkNodeAT sshd\[1075\]: Invalid user crichard from 202.77.105.100 Mar 26 12:43:12 ArkNodeAT sshd\[1075\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.77.105.100 Mar 26 12:43:14 ArkNodeAT sshd\[1075\]: Failed password for invalid user crichard from 202.77.105.100 port 53822 ssh2 |
2020-03-26 19:47:34 |
| 81.182.248.193 | attackbots | Mar 26 07:37:34 Tower sshd[3880]: Connection from 81.182.248.193 port 47131 on 192.168.10.220 port 22 rdomain "" Mar 26 07:37:45 Tower sshd[3880]: Invalid user england from 81.182.248.193 port 47131 Mar 26 07:37:45 Tower sshd[3880]: error: Could not get shadow information for NOUSER Mar 26 07:37:45 Tower sshd[3880]: Failed password for invalid user england from 81.182.248.193 port 47131 ssh2 Mar 26 07:37:45 Tower sshd[3880]: Received disconnect from 81.182.248.193 port 47131:11: Bye Bye [preauth] Mar 26 07:37:45 Tower sshd[3880]: Disconnected from invalid user england 81.182.248.193 port 47131 [preauth] |
2020-03-26 19:44:47 |
| 79.157.219.48 | attack | [AUTOMATIC REPORT] - 21 tries in total - SSH BRUTE FORCE - IP banned |
2020-03-26 19:55:40 |
| 125.124.30.186 | attackbotsspam | Mar 26 11:54:20 mout sshd[7531]: Invalid user gk from 125.124.30.186 port 55504 |
2020-03-26 19:35:03 |
| 189.163.200.155 | attackspam | port 23 |
2020-03-26 19:38:29 |
| 122.15.82.87 | attackbots | Mar 26 11:40:05 hosting180 sshd[27536]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.15.82.87 user=root Mar 26 11:40:07 hosting180 sshd[27536]: Failed password for root from 122.15.82.87 port 52530 ssh2 ... |
2020-03-26 19:48:25 |
| 58.56.164.166 | attack | (sshd) Failed SSH login from 58.56.164.166 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Mar 26 09:14:12 amsweb01 sshd[5988]: Invalid user lb from 58.56.164.166 port 46414 Mar 26 09:14:13 amsweb01 sshd[5988]: Failed password for invalid user lb from 58.56.164.166 port 46414 ssh2 Mar 26 09:23:36 amsweb01 sshd[7425]: Did not receive identification string from 58.56.164.166 port 42716 Mar 26 09:26:16 amsweb01 sshd[7751]: User daemon from 58.56.164.166 not allowed because not listed in AllowUsers Mar 26 09:26:16 amsweb01 sshd[7751]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.56.164.166 user=daemon |
2020-03-26 19:22:23 |
| 167.71.234.134 | attackbotsspam | Mar 25 14:33:29 xxxxxxx9247313 sshd[15260]: Invalid user op from 167.71.234.134 Mar 25 14:33:29 xxxxxxx9247313 sshd[15260]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.234.134 Mar 25 14:33:31 xxxxxxx9247313 sshd[15260]: Failed password for invalid user op from 167.71.234.134 port 50278 ssh2 Mar 25 14:38:09 xxxxxxx9247313 sshd[15394]: Invalid user sharee from 167.71.234.134 Mar 25 14:38:09 xxxxxxx9247313 sshd[15394]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.234.134 Mar 25 14:38:11 xxxxxxx9247313 sshd[15394]: Failed password for invalid user sharee from 167.71.234.134 port 37880 ssh2 Mar 25 14:42:41 xxxxxxx9247313 sshd[15517]: Invalid user mb from 167.71.234.134 Mar 25 14:42:41 xxxxxxx9247313 sshd[15517]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.234.134 Mar 25 14:42:43 xxxxxxx9247313 sshd[15517]: Failed password f........ ------------------------------ |
2020-03-26 19:16:15 |
| 89.189.186.45 | attackbotsspam | $f2bV_matches |
2020-03-26 19:48:43 |
| 198.100.146.67 | attackspam | 2020-03-26T11:42:35.569322vps751288.ovh.net sshd\[22904\]: Invalid user omsagent from 198.100.146.67 port 56795 2020-03-26T11:42:35.578428vps751288.ovh.net sshd\[22904\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns506165.ip-198-100-146.net 2020-03-26T11:42:37.780060vps751288.ovh.net sshd\[22904\]: Failed password for invalid user omsagent from 198.100.146.67 port 56795 ssh2 2020-03-26T11:45:57.289429vps751288.ovh.net sshd\[22937\]: Invalid user webadmin from 198.100.146.67 port 35398 2020-03-26T11:45:57.301444vps751288.ovh.net sshd\[22937\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns506165.ip-198-100-146.net |
2020-03-26 19:35:40 |
| 113.21.115.221 | attackbots | $f2bV_matches |
2020-03-26 19:52:04 |
| 213.87.101.176 | attackbots | Mar 26 11:57:37 ns382633 sshd\[28386\]: Invalid user db2fenc1 from 213.87.101.176 port 50594 Mar 26 11:57:37 ns382633 sshd\[28386\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.87.101.176 Mar 26 11:57:39 ns382633 sshd\[28386\]: Failed password for invalid user db2fenc1 from 213.87.101.176 port 50594 ssh2 Mar 26 12:07:50 ns382633 sshd\[30583\]: Invalid user mc from 213.87.101.176 port 37268 Mar 26 12:07:50 ns382633 sshd\[30583\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.87.101.176 |
2020-03-26 19:31:00 |
| 163.172.247.30 | attack | Invalid user support from 163.172.247.30 port 58286 |
2020-03-26 19:33:40 |