Domain > api.g.stage.context.cloud.sap

More information on this domain is in AlienVault OTX

DNS Resolutions

Date	IP Address
2020-08-06	13.227.40.72 (ClassC)
2021-04-07	65.8.49.54 (ClassC)
2021-06-16	65.8.48.77 (ClassC)
2021-06-16	65.8.48.97 (ClassC)
2021-06-16	65.8.48.47 (ClassC)
2021-07-14	13.225.66.88 (ClassC)
2021-09-09	65.8.56.62 (ClassC)
2021-09-09	65.8.56.83 (ClassC)
2021-09-30	52.84.145.96 (ClassC)
2021-09-30	54.192.58.22 (ClassC)
2021-11-23	13.249.93.10 (ClassC)
2022-02-12	108.156.107.30 (ClassC)
2024-11-05	99.84.66.68 (ClassC)
2025-02-20	99.84.66.25 (ClassC)
2025-04-16	99.84.66.105 (ClassC)
2025-04-21	18.238.238.2 (ClassC)
2025-05-07	99.84.66.104 (ClassC)
2025-06-17	18.238.238.125 (ClassC)

HTTP/1.1 403 ForbiddenServer: CloudFrontDate: Wed, 17 Jan 2024 06:18:22 GMTContent-Type: text/htmlContent-Length: 915Connection: keep-aliveX-Cache: Error from cloudfrontVia: 1.1 a20e81b65d2465c729ce2f

!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: zbFPDCytY2sOeOFXznk2T0W8KV-SGsBDnCzr2uDNt6FN7G8twzD9Ww/PRE>ADDRESS>/ADDRESS>/BODY>/HTML>

Port 443

HTTP/1.1 502 Bad GatewayContent-Type: text/htmlContent-Length: 951Connection: keep-aliveServer: CloudFrontDate: Wed, 17 Jan 2024 06:18:23 GMTX-Cache: Error from cloudfrontVia: 1.1 5ab5dc09da67e3ea794e

!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>502 ERROR/H1>H2>The request could not be satisfied./H2>HR noshade size1px>CloudFront wasnt able to connect to the origin.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: boNXj2By6dsEhRoy_nMA80q8vWYabJ_2RLA-5nMUHYm05eZ8qD1kRg/PRE>ADDRESS>/ADDRESS>/BODY>/HTML>

Subdomains

Date	Domain	IP
api2.stage.context.cloud.sap	2024-11-12	52.204.40.139
api3.stage.context.cloud.sap	2024-07-27	54.145.155.119
api2.b.stage.context.cloud.sap	2024-05-04	34.238.199.226
api3.b.stage.context.cloud.sap	2024-07-04	54.147.209.198
api.b.stage.context.cloud.sap	2024-10-31	18.64.67.89
api.g.stage.context.cloud.sap	2024-11-05	99.84.66.68
api.stage.context.cloud.sap	2024-10-02	99.84.66.68

View on OTX | View on ThreatMiner

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

Domain > api.g.stage.context.cloud.sap

Is this malicious?

DNS Resolutions

Port 80

Port 443

Subdomains