CloudFront
tcp/443
awselb 2.0
tcp/80
.DS_Store” is an abbreviation for “Desktop Services Store”. These files are created automatically by Apples “Finder” software (which is part of their OS).
They store information about the files within a folder, including display options of folders, such as icon positions and view settings.
It may happen that .DS_Store files inadvertently leak filenames such as database backups or private administration panels.
Severity: low
Fingerprint: 5f32cf5d6962f09c63442d9d63442d9db7f4c636b7f4c636b7f4c636b7f4c636
Found 1 files trough .DS_Store spidering: /images
Open service 18.66.192.56:443 · unknownbanger.com
2026-01-09 05:30
HTTP/1.1 400 Bad Request Server: CloudFront Date: Fri, 09 Jan 2026 05:30:02 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 5cc4b35b46cb9b55d49e7f47442e6838.cloudfront.net (CloudFront) X-Amz-Cf-Pop: MUC50-P1 X-Amz-Cf-Id: tZ2rm6baalaIbiHASo2tIiWKpZui28PRpHJAdqPsVj1utRIjtFkdnA== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>400 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't 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 clear="all"> 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 clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: tZ2rm6baalaIbiHASo2tIiWKpZui28PRpHJAdqPsVj1utRIjtFkdnA== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 18.66.192.56:443 · unknownbanger.com
2026-01-02 06:00
HTTP/1.1 400 Bad Request Server: CloudFront Date: Fri, 02 Jan 2026 06:00:17 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 3ddbbcaacc1ba68ddfab04ef45c3ca98.cloudfront.net (CloudFront) X-Amz-Cf-Pop: MUC50-P1 X-Amz-Cf-Id: 8I20DOpS9VrEiF3GXv8aQ6ZQOwIZU9QZrgqWfP9P7BC3ZV6yLgzXUw== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>400 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't 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 clear="all"> 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 clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: 8I20DOpS9VrEiF3GXv8aQ6ZQOwIZU9QZrgqWfP9P7BC3ZV6yLgzXUw== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 18.66.192.56:443 · unknownbanger.com
2025-12-30 13:35
HTTP/1.1 400 Bad Request Server: CloudFront Date: Tue, 30 Dec 2025 13:35:50 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 32700c539a5f821aadd3624288c4aeb6.cloudfront.net (CloudFront) X-Amz-Cf-Pop: MUC50-P1 X-Amz-Cf-Id: mMWuIOaIqoHxgijsen7PrGD2vq1kx55H-nSMi1jvGPAtM89lHPKfQw== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>400 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't 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 clear="all"> 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 clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: mMWuIOaIqoHxgijsen7PrGD2vq1kx55H-nSMi1jvGPAtM89lHPKfQw== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 18.66.192.56:443 · unknownbanger.com
2025-12-22 16:44
HTTP/1.1 400 Bad Request Server: CloudFront Date: Mon, 22 Dec 2025 16:44:30 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 878a01abbb158ab50d28bd4e882dc33a.cloudfront.net (CloudFront) X-Amz-Cf-Pop: MUC50-P1 X-Amz-Cf-Id: HRwRbbZPXrp-fiWLN4kfQeD9cYgll86xyW4-cXFJdZhnkQYfqtdCCQ== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>400 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't 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 clear="all"> 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 clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: HRwRbbZPXrp-fiWLN4kfQeD9cYgll86xyW4-cXFJdZhnkQYfqtdCCQ== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 18.66.192.56:443 · unknownbanger.com
2025-12-20 22:50
HTTP/1.1 400 Bad Request Server: CloudFront Date: Sat, 20 Dec 2025 22:50:35 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 c414bd1a4ce7ace94cbfdfa8efcbe5a6.cloudfront.net (CloudFront) X-Amz-Cf-Pop: MUC50-P1 X-Amz-Cf-Id: CWrhXCTgFjE7l3etoiG-YNzu9t18Q79ipqgMY0xYJSFqD_T6QszkXA== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>400 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't 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 clear="all"> 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 clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: CWrhXCTgFjE7l3etoiG-YNzu9t18Q79ipqgMY0xYJSFqD_T6QszkXA== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 3.33.251.168:80 · unknownbanger.com
2025-12-19 01:27
HTTP/1.1 403 Forbidden Server: awselb/2.0 Date: Fri, 19 Dec 2025 01:27:43 GMT Content-Type: text/html Content-Length: 118 Connection: close Page title: 403 Forbidden <html> <head><title>403 Forbidden</title></head> <body> <center><h1>403 Forbidden</h1></center> </body> </html>
Open service 15.197.225.128:80 · unknownbanger.com
2025-12-19 01:27
HTTP/1.1 403 Forbidden Server: awselb/2.0 Date: Fri, 19 Dec 2025 01:27:43 GMT Content-Type: text/html Content-Length: 118 Connection: close Page title: 403 Forbidden <html> <head><title>403 Forbidden</title></head> <body> <center><h1>403 Forbidden</h1></center> </body> </html>
Open service 15.197.225.128:443 · unknownbanger.com
2025-12-19 01:27
HTTP/1.0 400 Bad Request Client sent an HTTP request to an HTTPS server.
Open service 3.33.251.168:443 · unknownbanger.com
2025-12-19 01:27
HTTP/1.0 400 Bad Request Client sent an HTTP request to an HTTPS server.
Open service 18.66.192.56:443 · unknownbanger.com
2025-12-19 00:32
HTTP/1.1 400 Bad Request Server: CloudFront Date: Fri, 19 Dec 2025 00:32:55 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 dcfe318aa268be733627ea7884246be4.cloudfront.net (CloudFront) X-Amz-Cf-Pop: MUC50-P1 X-Amz-Cf-Id: 4d3OfdKe1MuTmFT-e0VUo5mpH-c8lnTSDXcjl9sOTJRqdTsxPD2PGA== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>400 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't 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 clear="all"> 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 clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: 4d3OfdKe1MuTmFT-e0VUo5mpH-c8lnTSDXcjl9sOTJRqdTsxPD2PGA== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>