HELO Los Angeles Credit Card Charge

https://explaincharges.com/helo-los-angeles-credit-card…

WACZ

Groupe59c2811-cef0-42e8-81db-147f65ef1eaasubmitted urlMember 1

Case summary

The target, observed result, and important findings.

Status
Current evaluation: Score 10: risk 15 less 5 for assurance evidence.
Limited evidence: critical response missing, identifier limit, interaction stalled
Findings: 8Medium
Kit source work: Loading related source work…
Discover or upload kit source
Submitted URL: http://explaincharges.com/vizoya-charge-on-credit-card Search for this value.
Effective URL: https://explaincharges.com/helo-los-angeles-credit-card-charge/ Search for this value.
Domain registration: explaincharges.comMore than 90 days oldRegistered 2024-04-02 · Registrar HOSTINGER operations, UAB
Language: Detecting...
Network: 2,154 requests across 268 hosts
Cookies: 1,305 observed
Infrastructure: Loading...
Behavior: 0 recorded events
Interaction: 10 actions · 1 submission · stopped: repeated state · download stage: no payload control
1. clicksucceededAccept all
2. clicksucceededSee also 1515 3rd Street San Francisco Charge on Credit Card?
3. clicksucceededcharge on credit card
4. clicksucceededSee also ICM Instant Checkmate Credit Card Charge
5. clicksucceededSee also HELO Los Angeles Credit Card Charge
6. fillsucceededtext | author | Name | Name *
7. fillsucceededemail | email | Email | Email *
8. submitsucceededPost Comment
9. validationobservedValidation (valueMissing) | textarea | comment | Comment
10. validationobservedValidation (valueMissing) | search | s | Search

Analysis metadata

How and when the analysis ran.

Input kind: url
Execution kind: capture
Duration: 2.9m
Navigation: 7 navigations
Engine version: 0.4.2

Created: 2026-11-15 20:52:19Z
Started: 2026-11-15 20:52:20Z
Finished: 2026-11-15 20:55:16Z
Archive: 14.6 MB
Analysis ID: bf8b6cf0-0efc...

Document-source diagnostics

These records identify rejected document reads. A current epoch does not prove that a replacement read succeeded. Later success does not erase an earlier evidence limit.

No rejected document reads were recorded.

Browser-observed navigation status

The browser status can differ from the normalized origin response, including during a proxy failure. Inspect the recorded document request for origin response evidence.

Navigation	Browser-observed HTTP status	Recorded requests
0	307	Inspect navigation 0 requests
1	301	Inspect navigation 1 requests
2	200	Inspect navigation 2 requests
3	200	Inspect navigation 3 requests
4	200	Inspect navigation 4 requests
5	200	Inspect navigation 5 requests
6	200	Inspect navigation 6 requests

Showing 0–0 of 0

Signals by severity

Detected findings grouped by risk

Request activity

Network requests grouped by resource type

Behavior

Recorded actions grouped by type

Network contacts

Requests to the most active hosts

Request ownership

First-party and third-party requests

Response MIME types

Network responses grouped by MIME type