mintandmetacred.xyz was recorded on the MetaMask external blocklist as of 2026-10-14, providing a dated indicator of its status in security monitoring systems. The domain also received a PageSpeed performance score of 91, reflecting a technical measurement from another perspective.
Recorded Evidence
On 2026-10-14, mintandmetacred.xyz appeared on both the MetaMask and SEAL external blocklists. VirusTotal checked the domain on that date, recording 1 detection out of 92 total scanners. OTX listed 4 pulses for this domain as of 2026-10-14. The domain was also internally listed by PhishDestroy, and its PageSpeed performance score was documented as 91.
Interpretation
The VirusTotal record for mintandmetacred.xyz contains a measurement of detections from multiple security vendors, which can be compared to blocklist entries for broader context. OTX documents collaborative security intelligence through its pulse entries, offering insight into the domain’s mention in shared threat data. These sources provide varied perspectives, with external blocklists and internal listings capturing different aspects of the domain’s security profile.
Recommended Actions
For mintandmetacred.xyz, preserve the VirusTotal, OTX, and PhishDestroy records for ongoing reference. Compare external blocklist entries with internal listings to track changes in monitoring. Use these documented results to inform future checks and guide any necessary follow-up based on their recorded findings.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Latest HTTP observation未知Probe Inconclusive20%2026-10-14 19:31:11 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-14 19:31:11 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.
Values retained by the collector; long values may be shortened during collection.
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.
Threat First Observed2026-10-14 19:28:05 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.214.23.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
9 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)
