lumetracceec.com was observed on 2026-10-11 with a recorded blocklist entry from MetaMask, providing a dated indicator relevant to security assessments. The domain was also listed internally by PhishDestroy, adding another layer of recorded evidence to its profile.
Recorded Evidence
MetaMask and SEAL both documented lumetracceec.com on their external blocklists as of 2026-10-11. PhishDestroy included the domain in its internal listing on the same date. The domain's registration was recorded with Realtime Register B.V. on 2026-07-29, establishing its timeline within the available evidence.
Interpretation
PhishDestroy's internal listing contains a specific measurement of lumetracceec.com, documenting its presence in a monitored environment. External blocklists such as MetaMask and SEAL provide additional references that expand the scope of recorded observations. The evidence covers both internal and external sources, offering a snapshot of the domain's profile as of the documented dates.
Recommended Actions
Preserve the blocklist records for lumetracceec.com from MetaMask and SEAL for ongoing comparison and review. Retain the PhishDestroy internal listing as a reference point for future assessments. Use these dated observations to inform any subsequent checks or security reviews of the domain.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 11:37:27 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 11:37:27 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.
Threat First Observed2026-10-11 11:37:27 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.164.64.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
5 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
レポート 
