Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: San Antonio

Region: Texas

Country: United States

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
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.76.0.0/14, 40.112.0.0/13, 40.124.0.0/16, 40.80.0.0/12, 40.120.0.0/14, 40.74.0.0/15, 40.96.0.0/12, 40.125.0.0/17
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 info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 40.124.185.115
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9453
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;40.124.185.115.			IN	A

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

;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Sep 21 01:30:08 CST 2026
;; MSG SIZE  rcvd: 107
Host info
Host 115.185.124.40.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 115.185.124.40.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
218.92.0.220 attack
Jul 18 00:14:55 dev0-dcde-rnet sshd[30212]: Failed password for root from 218.92.0.220 port 48136 ssh2
Jul 18 00:15:04 dev0-dcde-rnet sshd[30214]: Failed password for root from 218.92.0.220 port 54978 ssh2
2020-07-18 06:21:16
159.65.245.182 attackbotsspam
419. On Jul 17 2020 experienced a Brute Force SSH login attempt -> 1 unique times by 159.65.245.182.
2020-07-18 05:58:54
171.38.194.142 attackspambots
Icarus honeypot on github
2020-07-18 06:19:51
122.51.217.131 attackspam
Jul 18 00:13:21 mout sshd[32000]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.217.131 
Jul 18 00:13:21 mout sshd[32000]: Invalid user share from 122.51.217.131 port 51502
Jul 18 00:13:23 mout sshd[32000]: Failed password for invalid user share from 122.51.217.131 port 51502 ssh2
2020-07-18 06:24:30
79.136.70.159 attack
Jul 17 23:49:11 minden010 sshd[29467]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.136.70.159
Jul 17 23:49:13 minden010 sshd[29467]: Failed password for invalid user avi from 79.136.70.159 port 57798 ssh2
Jul 17 23:56:06 minden010 sshd[30498]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.136.70.159
...
2020-07-18 06:19:15
155.94.156.84 attack
Jul 18 01:17:32 pkdns2 sshd\[3076\]: Address 155.94.156.84 maps to 155.94.156.84.static.quadranet.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Jul 18 01:17:32 pkdns2 sshd\[3076\]: Invalid user bill from 155.94.156.84Jul 18 01:17:34 pkdns2 sshd\[3076\]: Failed password for invalid user bill from 155.94.156.84 port 60682 ssh2Jul 18 01:22:12 pkdns2 sshd\[3311\]: Address 155.94.156.84 maps to 155.94.156.84.static.quadranet.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Jul 18 01:22:12 pkdns2 sshd\[3311\]: Invalid user lds from 155.94.156.84Jul 18 01:22:14 pkdns2 sshd\[3311\]: Failed password for invalid user lds from 155.94.156.84 port 57606 ssh2
...
2020-07-18 06:27:29
212.129.246.52 attack
Invalid user admin from 212.129.246.52 port 40232
2020-07-18 06:03:07
40.117.83.127 attackbotsspam
Jul 18 00:06:19 ns3164893 sshd[18001]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=40.117.83.127
Jul 18 00:06:21 ns3164893 sshd[18001]: Failed password for invalid user admin from 40.117.83.127 port 4753 ssh2
...
2020-07-18 06:16:40
114.252.251.190 attack
Jul 17 23:34:40 ns382633 sshd\[16877\]: Invalid user pablo from 114.252.251.190 port 32828
Jul 17 23:34:40 ns382633 sshd\[16877\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.252.251.190
Jul 17 23:34:42 ns382633 sshd\[16877\]: Failed password for invalid user pablo from 114.252.251.190 port 32828 ssh2
Jul 17 23:40:47 ns382633 sshd\[18516\]: Invalid user sami from 114.252.251.190 port 46220
Jul 17 23:40:47 ns382633 sshd\[18516\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.252.251.190
2020-07-18 06:04:46
13.78.230.118 attack
Tried sshing with brute force.
2020-07-18 06:01:43
218.92.0.168 attackbots
2020-07-17T23:43:45.395926ns386461 sshd\[3129\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.168  user=root
2020-07-17T23:43:48.242593ns386461 sshd\[3129\]: Failed password for root from 218.92.0.168 port 4798 ssh2
2020-07-17T23:43:51.853652ns386461 sshd\[3129\]: Failed password for root from 218.92.0.168 port 4798 ssh2
2020-07-17T23:43:54.681790ns386461 sshd\[3129\]: Failed password for root from 218.92.0.168 port 4798 ssh2
2020-07-17T23:43:58.115959ns386461 sshd\[3129\]: Failed password for root from 218.92.0.168 port 4798 ssh2
...
2020-07-18 05:59:38
186.10.125.209 attackbotsspam
Invalid user tb from 186.10.125.209 port 4937
2020-07-18 06:34:30
192.141.80.72 attackspambots
2020-07-17T21:48:44.053810shield sshd\[21237\]: Invalid user tobin from 192.141.80.72 port 10996
2020-07-17T21:48:44.066106shield sshd\[21237\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.141.80.72
2020-07-17T21:48:45.629276shield sshd\[21237\]: Failed password for invalid user tobin from 192.141.80.72 port 10996 ssh2
2020-07-17T21:53:30.348264shield sshd\[22598\]: Invalid user ted from 192.141.80.72 port 20364
2020-07-17T21:53:30.360993shield sshd\[22598\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.141.80.72
2020-07-18 06:00:07
185.39.9.30 attack
firewall-block, port(s): 12037/tcp, 12064/tcp, 12109/tcp, 12119/tcp, 12142/tcp, 12151/tcp, 12242/tcp, 12266/tcp, 12342/tcp, 12379/tcp, 12415/tcp, 12488/tcp, 12534/tcp, 12535/tcp, 12606/tcp, 12618/tcp, 12641/tcp, 12660/tcp, 12688/tcp, 12718/tcp
2020-07-18 06:08:17
123.207.99.184 attack
Invalid user tester from 123.207.99.184 port 32984
2020-07-18 06:31:06

Recently Reported IPs

114.80.142.19 210.78.28.166 156.225.1.64 2606:4700:10::6816:4121
154.12.50.28 77.56.172.154 40.124.186.145 3.16.136.88
40.74.213.31 31.204.150.78 40.119.45.52 216.73.216.114
2606:4700:10::6816:3105 2408:8459:4ce0:10eb:18d7:b3e:6c4:8772 8.138.207.158 146.190.147.229
197.231.203.32 34.147.204.78 123.56.131.100 110.38.250.182