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.74.0.0/15, 40.112.0.0/13, 40.120.0.0/14, 40.76.0.0/14, 40.96.0.0/12, 40.125.0.0/17, 40.80.0.0/12, 40.124.0.0/16
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.119.28.169
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17816
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;40.119.28.169.			IN	A

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

;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Sep 01 18:31:46 CST 2026
;; MSG SIZE  rcvd: 106
Host info
169.28.119.40.in-addr.arpa domain name pointer azpdse17r3am.stretchoid.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
169.28.119.40.in-addr.arpa	name = azpdse17r3am.stretchoid.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
185.151.242.187 attackbots
Portscan or hack attempt detected by psad/fwsnort
2020-02-15 23:07:41
193.56.28.34 attackspambots
2020-02-15T13:53:24.455149newhq.d postfix/smtpd[14362]: warning: unknown[193.56.28.34]: SASL LOGIN authentication failed: generic failure
2020-02-15T13:53:32.419393newhq.d postfix/smtpd[14362]: warning: unknown[193.56.28.34]: SASL LOGIN authentication failed: generic failure
2020-02-15T13:53:36.746995newhq.d postfix/smtpd[14362]: warning: unknown[193.56.28.34]: SASL LOGIN authentication failed: generic failure
...
2020-02-15 22:50:58
187.170.232.5 attack
20/2/15@08:53:49: FAIL: Alarm-Network address from=187.170.232.5
20/2/15@08:53:49: FAIL: Alarm-Network address from=187.170.232.5
...
2020-02-15 22:27:55
77.40.3.64 attackspam
failed_logins
2020-02-15 22:56:39
58.27.99.112 attackbotsspam
Feb 15 15:13:37 sso sshd[28231]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.27.99.112
Feb 15 15:13:39 sso sshd[28231]: Failed password for invalid user bryan from 58.27.99.112 port 45430 ssh2
...
2020-02-15 22:54:05
212.232.25.224 attackspambots
Dec 16 20:40:11 ms-srv sshd[19581]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.232.25.224
Dec 16 20:40:13 ms-srv sshd[19581]: Failed password for invalid user asterisk from 212.232.25.224 port 59812 ssh2
2020-02-15 22:52:06
188.254.0.226 attackbots
Feb 15 10:53:17 ws24vmsma01 sshd[77350]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.226
Feb 15 10:53:20 ws24vmsma01 sshd[77350]: Failed password for invalid user test1 from 188.254.0.226 port 42274 ssh2
...
2020-02-15 23:07:24
118.43.4.238 attackspambots
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-15 22:28:49
198.12.152.199 attackspam
Feb 15 14:49:01 h2177944 sshd\[14971\]: Invalid user zabbix from 198.12.152.199 port 44890
Feb 15 14:49:01 h2177944 sshd\[14971\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.12.152.199
Feb 15 14:49:03 h2177944 sshd\[14971\]: Failed password for invalid user zabbix from 198.12.152.199 port 44890 ssh2
Feb 15 14:52:26 h2177944 sshd\[15092\]: Invalid user t7adm from 198.12.152.199 port 46802
...
2020-02-15 22:44:06
118.43.60.214 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-15 22:22:42
138.68.44.236 attack
Feb 15 05:02:38 hpm sshd\[6703\]: Invalid user dustin from 138.68.44.236
Feb 15 05:02:38 hpm sshd\[6703\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.44.236
Feb 15 05:02:40 hpm sshd\[6703\]: Failed password for invalid user dustin from 138.68.44.236 port 33048 ssh2
Feb 15 05:06:08 hpm sshd\[7118\]: Invalid user harman from 138.68.44.236
Feb 15 05:06:08 hpm sshd\[7118\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.44.236
2020-02-15 23:06:14
61.177.172.128 attack
Feb 15 15:46:36 vps647732 sshd[8689]: Failed password for root from 61.177.172.128 port 47980 ssh2
Feb 15 15:46:39 vps647732 sshd[8689]: Failed password for root from 61.177.172.128 port 47980 ssh2
...
2020-02-15 22:57:59
158.69.110.31 attackspambots
Feb 15 15:22:00 silence02 sshd[9867]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=158.69.110.31
Feb 15 15:22:02 silence02 sshd[9867]: Failed password for invalid user awstats from 158.69.110.31 port 45898 ssh2
Feb 15 15:25:13 silence02 sshd[10099]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=158.69.110.31
2020-02-15 22:31:12
103.75.149.106 attackbots
5x Failed Password
2020-02-15 22:47:52
92.63.194.105 attackbotsspam
Feb 15 15:16:05 srv01 sshd[14480]: Invalid user a from 92.63.194.105 port 36693
Feb 15 15:16:05 srv01 sshd[14480]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.63.194.105
Feb 15 15:16:05 srv01 sshd[14480]: Invalid user a from 92.63.194.105 port 36693
Feb 15 15:16:07 srv01 sshd[14480]: Failed password for invalid user a from 92.63.194.105 port 36693 ssh2
Feb 15 15:16:05 srv01 sshd[14480]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.63.194.105
Feb 15 15:16:05 srv01 sshd[14480]: Invalid user a from 92.63.194.105 port 36693
Feb 15 15:16:07 srv01 sshd[14480]: Failed password for invalid user a from 92.63.194.105 port 36693 ssh2
...
2020-02-15 22:21:06

Recently Reported IPs

111.227.123.217 110.82.38.3 106.118.71.27 34.96.36.84
109.105.193.73 2606:4700:10::6816:1205 91.92.40.149 123.150.138.194
58.20.119.198 42.49.174.171 42.226.114.27 223.88.220.8
183.253.75.109 183.211.251.193 123.11.184.223 120.239.101.215
120.221.100.116 119.248.60.133 119.2.164.175 101.66.0.124