submitcase-92841074.com returned HTTP status 200 on 2026-10-01, according to the HTTP check recorded for that date. The domain was first observed on 2026-09-16, and its registration date is listed as 2026-05-25 with Name.com, Inc. as registrar.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 200, while the first observation of this domain dates to 2026-09-16. VirusTotal, checked on 2026-09-29, reported 17 detections across 91 scanners. OTX, checked on 2026-09-19, showed 4 pulses, and the PhishDestroy internal listing was recorded as true. The SSL certificate, scanned on 2026-09-17, was issued by Let's Encrypt / YE2. The IP address 63.176.8.218 is associated with AWS EC2 (eu-central-1) in DE.
Interpretation
The OTX and VirusTotal observations were made on different dates, so their counts reflect separate snapshots rather than a single synchronized measurement. The PhishDestroy internal listing and the HTTP response were also recorded on separate dates, meaning the catalogue entry and the reachability check describe distinct moments. Because the observation dates differ, a reader can compare the sequence of records but cannot treat them as one contemporaneous state.
Recommended Actions
Anyone reviewing submitcase-92841074.com should retain the dated records, including the HTTP check, SSL scan, and VirusTotal and OTX observations, so later comparisons use the same reference points. Subsequent checks of submitcase-92841074.com should be logged with their own dates to show how the recorded values change over time. During any review, avoid submitting sensitive information to the domain until the collected evidence has been assessed.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-13 22:14:38 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:29:34 UTClast content: 2026-10-13 22:14:38 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.
技术 · 3 identified
R
React
JavaScript frameworks
React is an open-source JavaScript library for building user interfaces or UI components.
Last analyzed Previous stored snapshot: 18 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
ESET
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
卡巴斯基
Lionic
Seclookup
SOCRadar
Sophos
URLQuery
VIPRE
Webroot
desenmascara.me
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
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.
VirusTotal Detections Update2026-09-16 21:41:25 UTC
VirusTotal scanner detections updated from 17 to 18. Added scanner alerts: desenmascara.me.
Threat First Observed2026-09-16 19:04:33 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 63.176.8.218.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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.
(US)
