Domain > api.stg.splunkcloud.systems

More information on this domain is in AlienVault OTX

DNS Resolutions

Date	IP Address
2019-03-02	13.249.87.90 (ClassC)
2019-03-02	13.249.142.3 (ClassC)
2019-03-02	13.249.87.97 (ClassC)
2019-03-02	13.249.142.50 (ClassC)
2019-03-02	13.249.142.76 (ClassC)
2019-03-02	13.249.87.64 (ClassC)
2020-02-03	52.85.77.100 (ClassC)
2020-02-03	52.85.77.62 (ClassC)
2020-02-03	143.204.160.33 (ClassC)
2020-02-03	52.85.77.77 (ClassC)
2020-02-03	143.204.160.85 (ClassC)
2021-01-03	52.85.79.98 (ClassC)
2024-08-31	99.84.66.123 (ClassC)
2024-09-30	99.84.66.89 (ClassC)
2025-04-13	99.84.66.37 (ClassC)
2025-05-11	99.84.66.78 (ClassC)
2025-06-06	3.163.189.78 (ClassC)

HTTP/1.1 403 ForbiddenServer: CloudFrontDate: Sun, 23 Jul 2023 11:03:12 GMTContent-Type: text/htmlContent-Length: 915Connection: keep-aliveX-Cache: Error from cloudfrontVia: 1.1 f13aef0c4b52f6f681401f

!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN http://www.w3.org/TR/html4/loose.dtd>HTML>HEAD>META HTTP-EQUIVContent-Type CONTENTtext/html; charsetiso-8859-1>TITLE>ERROR: The request could not be satisfied/TITLE>/HEAD>BODY>H1>403 ERROR/H1>H2>The request could not be satisfied./H2>HR noshade size1px>Bad request.We cant connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.BR clearall>If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.BR clearall>HR noshade size1px>PRE>Generated by cloudfront (CloudFront)Request ID: qQPcJ-ncEw-zvsGzVAq5ILTYGgsnBEqYgZiHTUKsCh8FRSrEtNGKBg/PRE>ADDRESS>/ADDRESS>/BODY>/HTML>

View on OTX | View on ThreatMiner

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

Domain > api.stg.splunkcloud.systems

Is this malicious?

DNS Resolutions

Port 80