Domain > osf.splendid.cl

More information on this domain is in AlienVault OTX

DNS Resolutions

Date	IP Address
2023-09-13	184.28.43.149 (ClassC)
2024-01-10	104.112.191.21 (ClassC)
2024-09-13	23.222.149.49 (ClassC)
2025-09-07	23.198.148.78 (ClassC)
2026-02-12	104.90.240.42 (ClassC)

HTTP/1.1 401 UnauthorizedContent-Type: text/html; charsetutf-8Content-Length: 1468WWW-Authenticate: Basic realmOracle Cloud Commerce Testingoraclecommercecloud-sandiego: LTkxNzQ5NTc0NjQyMTE0NTgzODQx-o

!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Draft//EN>HTML>HEAD>TITLE>Error 401--Unauthorized/TITLE>/HEAD>BODY bgcolorwhite>FONT FACEHelvetica>BR CLEARall>TABLE border0 cellspacing5>TR>TD>BR CLEARall>FONT FACEHelvetica COLORblack SIZE3>H2>Error 401--Unauthorized/H2>/FONT>/TD>/TR>/TABLE>TABLE border0 width100% cellpadding10>TR>TD VALIGNtop WIDTH100% BGCOLORwhite>FONT FACECourier New>FONT FACEHelvetica SIZE3>H3>From RFC 2068 i>Hypertext Transfer Protocol -- HTTP/1.1/i>:/H3>/FONT>FONT FACEHelvetica SIZE3>H4>10.4.2 401 Unauthorized/H4>/FONT>P>FONT FACECourier New>The request requires user authentication. The response MUST include a WWW-Authenticate header field (section 14.46) containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header field (section 14.8). If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity MAY include relevant diagnostic information. HTTP access authentication is explained in section 11./FONT>/P>/FONT>/TD>/TR>/TABLE>/BODY>/HTML>

View on OTX | View on ThreatMiner

Data with thanks to AlienVault OTX, VirusTotal, Malwr and others. [Sitemap]

Domain > osf.splendid.cl

Is this malicious?

DNS Resolutions

Port 443