onchaininv.com was recorded in a blocklist context as of 2026-10-11, with a listing on MetaMask noted on that date. The domain was also observed in other security sources on the same day.
Recorded Evidence
MetaMask and SEAL both included onchaininv.com on their external blocklists as of 2026-10-11. PhishDestroy internally listed the domain on the same date. The domain's registration was recorded with Gransy, s.r.o. on 2026-09-11.
Interpretation
The MetaMask blocklist record contains a listing event for onchaininv.com, which is a type of external security measurement. The PhishDestroy internal listing documents an internal security assessment. These records together provide a snapshot of the domain's presence in multiple monitoring systems as of their respective dates.
Recommended Actions
For onchaininv.com, retain the MetaMask and SEAL blocklist records as references for future security reviews. Compare the PhishDestroy internal listing with other external blocklist entries to track any changes in the domain's security profile over time.
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:36:24 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 11:36:24 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:36:24 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 104.21.22.249.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
6 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.
Blocklist hits included with submission:MetaMask, SEAL
PDF notice generated Notice text archived (856 chars)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
