SSL certificate is invalid or expired. Issuer: Amazon RSA 2048 M04
Evidence Summary
Critical
VirusTotal
10/89
URLScan
Stored capture
Assessment
On 2026-10-03, d2cx10dsi4ptcz.cloudfront.net returned an HTTP 502 status code, indicating a server-side error was recorded on that date. Google Safe Browsing also flagged this domain for social engineering as of 2026-09-19.
Recorded Evidence
Google Safe Browsing identified d2cx10dsi4ptcz.cloudfront.net for social engineering on 2026-09-19. VirusTotal reported 10 detections out of 89 scanners for this domain on 2026-09-19. The domain was listed in the PhishDestroy internal catalogue. An HTTP check on 2026-10-03 recorded a 502 status code response.
Interpretation
The records from Google Safe Browsing, VirusTotal, and PhishDestroy show that d2cx10dsi4ptcz.cloudfront.net was noted by several security sources. The HTTP 502 status code documents a server error at the time of the most recent check, while earlier security source observations were also recorded.
Recommended Actions
Preserve the Google Safe Browsing, VirusTotal, and PhishDestroy records for d2cx10dsi4ptcz.cloudfront.net for reference. Compare future HTTP status responses with the recorded 502 code to track any changes. Use these dated observations to inform further review of this domain.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='d2cx10dsi4ptcz.cloudfront.net', port=80): Max retries exceeded with url: / (Caused by NewC
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Google Safe BrowsingFlaggedSocial engineeringchecked Sep 19, 2026
Platform providerMarkMonitor(US)
Time to First Unavailability7 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 12, 2026
Favicon Hash
Page Title
Service Health
TLS Certificate
Hostname coverage not recorded·
Issued by Amazon RSA 2048 M04
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
54.192.87.209
Network ASN
AS16509
Organization
Amazon.com, Inc.
Observed location
Frankfurt am Main, DE
Server header
railway-hikari
Nameservers 1
ns-666.awsdns-19.net
Location describes the IP network.
TLS certificate
Issuer
Amazon RSA 2048 M04
Hostname coverage
Hostname coverage not recorded
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:30:23 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-12 16:28:08 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-09-19 22:00:23 UTC
Domain state transitioned from alive to dead.
Status Check2026-09-19 11:00:04 UTC
Telemetry event observed.
Threat First Observed2026-09-19 10:53:12 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
d2cx10dsi4ptcz.cloudfront.net detected and queued for full analysis
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 20, 2026
Time to First Unavailability
175 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
3 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
(US)
