40.124.175.52 - IPInfo

Basic Info

City: San Antonio

Region: Texas

Country: United States

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:

Make a comment on this IP

No discussion about this IP yet. Click above link to make one.

Comments on same subnet:

IP	Type	Details	Datetime
40.124.175.184	spambotsattackproxy	Bot attacker IP	2025-06-03 13:06:39

Whois info:

#
# 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.96.0.0/12, 40.76.0.0/14, 40.125.0.0/17, 40.124.0.0/16, 40.120.0.0/14, 40.112.0.0/13, 40.80.0.0/12, 40.74.0.0/15
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: IPHOS5-ARIN
OrgTechName:   IPHostmaster, IPHostmaster 
OrgTechPhone:  +1-425-538-6637 
OrgTechEmail:  iphostmaster@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/IPHOS5-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

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 info:

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 40.124.175.52
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 58135
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;40.124.175.52.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2026050102 1800 900 604800 86400

;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat May 02 13:30:18 CST 2026
;; MSG SIZE  rcvd: 106

Host info

52.175.124.40.in-addr.arpa domain name pointer azpdsg13x2qz.stretchoid.com.

Nslookup info:

Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
52.175.124.40.in-addr.arpa	name = azpdsg13x2qz.stretchoid.com.

Authoritative answers can be found from:

Related IP info:

Related comments:

IP	Type	Details	Datetime
87.251.74.36	attackbots	TCP (SYN) 87.251.74.36:26520 -> port 22, len 60	2020-10-10 01:18:34
45.129.33.80	attack	TCP (SYN) 45.129.33.80:58315 -> port 1415, len 44	2020-10-10 01:01:51
159.65.222.152	attackspambots	$f2bV_matches	2020-10-10 01:03:54
212.70.149.20	attackspam	Oct 9 18:29:30 statusweb1.srvfarm.net postfix/smtpd[11337]: warning: unknown[212.70.149.20]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 9 18:29:54 statusweb1.srvfarm.net postfix/smtpd[11337]: warning: unknown[212.70.149.20]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 9 18:30:19 statusweb1.srvfarm.net postfix/smtpd[11337]: warning: unknown[212.70.149.20]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 9 18:30:43 statusweb1.srvfarm.net postfix/smtpd[11337]: warning: unknown[212.70.149.20]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 9 18:31:08 statusweb1.srvfarm.net postfix/smtpd[11337]: warning: unknown[212.70.149.20]: SASL LOGIN authentication failed: UGFzc3dvcmQ6	2020-10-10 01:09:10
93.191.20.34	attackspam	(sshd) Failed SSH login from 93.191.20.34 (RU/Russia/Ryazan Oblast/Ryazan/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct 9 03:29:52 atlas sshd[32702]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.191.20.34 user=root Oct 9 03:29:53 atlas sshd[32702]: Failed password for root from 93.191.20.34 port 42924 ssh2 Oct 9 03:33:06 atlas sshd[1856]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.191.20.34 user=root Oct 9 03:33:09 atlas sshd[1856]: Failed password for root from 93.191.20.34 port 36640 ssh2 Oct 9 03:34:20 atlas sshd[2329]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.191.20.34 user=root	2020-10-10 01:24:11
194.180.224.130	attackspambots	2020-10-09T17:26:32.150862randservbullet-proofcloud-66.localdomain sshd[23304]: Invalid user admin from 194.180.224.130 port 60582 2020-10-09T17:26:32.187078randservbullet-proofcloud-66.localdomain sshd[23302]: Invalid user admin from 194.180.224.130 port 60584 ...	2020-10-10 01:28:13
179.27.60.34	attackbotsspam	(sshd) Failed SSH login from 179.27.60.34 (UY/Uruguay/r179-27-60-34.static.adinet.com.uy): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct 9 11:02:25 server sshd[31679]: Failed password for root from 179.27.60.34 port 51845 ssh2 Oct 9 11:10:01 server sshd[1252]: Failed password for root from 179.27.60.34 port 27405 ssh2 Oct 9 11:11:58 server sshd[1848]: Invalid user pp from 179.27.60.34 port 52219 Oct 9 11:12:01 server sshd[1848]: Failed password for invalid user pp from 179.27.60.34 port 52219 ssh2 Oct 9 11:14:01 server sshd[2292]: Failed password for root from 179.27.60.34 port 26544 ssh2	2020-10-10 01:38:00
180.101.202.30	attackbots	Oct 9 14:44:47 vps-51d81928 sshd[685181]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.101.202.30 Oct 9 14:44:47 vps-51d81928 sshd[685181]: Invalid user smmsp from 180.101.202.30 port 33588 Oct 9 14:44:49 vps-51d81928 sshd[685181]: Failed password for invalid user smmsp from 180.101.202.30 port 33588 ssh2 Oct 9 14:49:16 vps-51d81928 sshd[685274]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.101.202.30 user=root Oct 9 14:49:18 vps-51d81928 sshd[685274]: Failed password for root from 180.101.202.30 port 57180 ssh2 ...	2020-10-10 01:34:48
51.116.176.229	attack	Lines containing failures of 51.116.176.229 Oct 8 00:46:49 node83 sshd[22143]: Did not receive identification string from 51.116.176.229 port 52692 Oct 8 00:47:07 node83 sshd[22259]: Did not receive identification string from 51.116.176.229 port 43878 Oct 8 00:47:41 node83 sshd[22368]: Did not receive identification string from 51.116.176.229 port 46470 Oct 8 00:47:43 node83 sshd[22370]: Did not receive identification string from 51.116.176.229 port 44146 Oct 8 00:48:19 node83 sshd[22897]: Invalid user ftpuser from 51.116.176.229 port 42612 Oct 8 00:48:19 node83 sshd[22897]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.116.176.229 Oct 8 00:48:21 node83 sshd[22897]: Failed password for invalid user ftpuser from 51.116.176.229 port 42612 ssh2 Oct 8 00:48:21 node83 sshd[22897]: Received disconnect from 51.116.176.229 port 42612:11: Normal Shutdown, Thank you for playing [preauth] Oct 8 00:48:21 node83 sshd[22897]: Disco........ ------------------------------	2020-10-10 01:29:56
159.203.188.175	attack	Oct 9 12:51:45 rotator sshd\[2828\]: Invalid user helpdesk from 159.203.188.175Oct 9 12:51:47 rotator sshd\[2828\]: Failed password for invalid user helpdesk from 159.203.188.175 port 38270 ssh2Oct 9 12:55:49 rotator sshd\[3634\]: Invalid user pgsql from 159.203.188.175Oct 9 12:55:51 rotator sshd\[3634\]: Failed password for invalid user pgsql from 159.203.188.175 port 43030 ssh2Oct 9 12:59:44 rotator sshd\[3657\]: Invalid user install from 159.203.188.175Oct 9 12:59:46 rotator sshd\[3657\]: Failed password for invalid user install from 159.203.188.175 port 47796 ssh2 ...	2020-10-10 01:20:23
179.235.137.203	attack	2020-10-09T09:37:22.108215abusebot-7.cloudsearch.cf sshd[11172]: Invalid user art1 from 179.235.137.203 port 42601 2020-10-09T09:37:22.113877abusebot-7.cloudsearch.cf sshd[11172]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.235.137.203 2020-10-09T09:37:22.108215abusebot-7.cloudsearch.cf sshd[11172]: Invalid user art1 from 179.235.137.203 port 42601 2020-10-09T09:37:23.851706abusebot-7.cloudsearch.cf sshd[11172]: Failed password for invalid user art1 from 179.235.137.203 port 42601 ssh2 2020-10-09T09:43:59.552037abusebot-7.cloudsearch.cf sshd[11182]: Invalid user test from 179.235.137.203 port 42299 2020-10-09T09:43:59.561000abusebot-7.cloudsearch.cf sshd[11182]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.235.137.203 2020-10-09T09:43:59.552037abusebot-7.cloudsearch.cf sshd[11182]: Invalid user test from 179.235.137.203 port 42299 2020-10-09T09:44:01.800578abusebot-7.cloudsearch.cf sshd[11182 ...	2020-10-10 01:21:43
60.190.226.187	attackbotsspam	Port Scan ...	2020-10-10 01:25:08
184.168.46.190	attackbots	"Restricted File Access Attempt - Matched Data: wp-config.php found within REQUEST_FILENAME: /wp-config.php.resetwp_bak"	2020-10-10 01:19:51
212.158.130.122	attackbotsspam	$f2bV_matches	2020-10-10 01:11:55
104.224.183.154	attack	Brute-force attempt banned	2020-10-10 01:00:43

Recently Reported IPs

2606:4700:10::6816:4294	191.176.194.150	101.36.121.140	43.165.126.130
213.199.36.187	2606:4700:10::6814:6268	2606:4700:10::6816:4797	158.28.54.174
43.248.109.147	110.78.153.115	2606:4700:10::6814:6880	2606:4700:10::6816:735
203.25.78.4	10.16.222.185	163.227.180.182	252.46.183.189
168.93.214.89	134.35.157.182	147.185.133.18	161.248.116.1