Domain > j-00fsfk7mqmqpgg0f-1.dashboard.emr-serverless.us-east-2.amazonaws.com

More information on this domain is in AlienVault OTX

DNS Resolutions

Date	IP Address
2025-07-02	108.138.128.82 (ClassC)
2025-07-29	3.163.24.87 (ClassC)

HTTP/1.1 403 ForbiddenServer: CloudFrontDate: Tue, 29 Jul 2025 17:54:38 GMTContent-Type: text/htmlContent-Length: 915Connection: keep-aliveX-Cache: Error from cloudfrontVia: 1.1 bafc250db6f7cbd43d1e23b2a31d8002.cloudfront.net (CloudFront)X-Amz-Cf-Pop: HIO52-P2X-Amz-Cf-Id: TGHg-Nw6WnRXHGSFFcbRi-B-sgkZoBEHQ1CnvIIEX0t3vNjuwks77gX-XSS-Protection: 1; modeblockX-Frame-Options: DENYReferrer-Policy: strict-origin-when-cross-originContent-Security-Policy: frame-ancestors none;X-Content-Type-Options: nosniffCache-Control: no-store

!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: TGHg-Nw6WnRXHGSFFcbRi-B-sgkZoBEHQ1CnvIIEX0t3vNjuwks77g/PRE>ADDRESS>/ADDRESS>/BODY>/HTML>

Port 443

HTTP/1.1 403 ForbiddenServer: CloudFrontDate: Tue, 29 Jul 2025 17:54:38 GMTContent-Type: text/htmlContent-Length: 919Connection: keep-aliveX-Cache: Error from cloudfrontVia: 1.1 1f941fcf288b6d0259a0f708c955afae.cloudfront.net (CloudFront)X-Amz-Cf-Pop: HIO52-P2X-Amz-Cf-Id: RFWocD8U7SBWYEY85k28cqyiMjHY34p-zdlr2ubiKaIzRn6ebAO1WAX-XSS-Protection: 1; modeblockX-Frame-Options: DENYReferrer-Policy: strict-origin-when-cross-originContent-Security-Policy: frame-ancestors none;X-Content-Type-Options: nosniffStrict-Transport-Security: max-age47304000; includeSubDomainsCache-Control: no-store

!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>Request blocked.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: RFWocD8U7SBWYEY85k28cqyiMjHY34p-zdlr2ubiKaIzRn6ebAO1WA/PRE>ADDRESS>/ADDRESS>/BODY>/HTML>

View on OTX | View on ThreatMiner

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

Domain > j-00fsfk7mqmqpgg0f-1.dashboard.emr-serverless.us-east-2.amazonaws.com

Is this malicious?

DNS Resolutions

Port 80

Port 443