erebor.casa was observed on 2026-10-13 with entries on both the MetaMask and SEAL external blocklists, reflecting its inclusion in multiple security monitoring sources. The same date also saw a PageSpeed performance score recorded, providing a technical benchmark alongside reputational data.
Recorded Evidence
On 2026-10-13, erebor.casa appeared on the MetaMask and SEAL external blocklists. VirusTotal checked the domain on 2026-10-13, reporting 0 detections out of 92 total scanners. OTX recorded 4 pulses for erebor.casa on 2026-10-13. PhishDestroy internally listed the domain, and a PageSpeed performance score of 100 was documented on 2026-10-13. The domain was registered with Cloudflare, Inc. on 2026-10-12, and its SSL certificate was issued by Google Trust Services / WE1 as of 2026-10-13.
Interpretation
PhishDestroy contains an internal listing for erebor.casa, which documents its presence within a security-focused context. VirusTotal provides a measurement of detections from a broad set of scanners, while OTX records intelligence pulses relevant to the domain. These records reflect a combination of technical and reputational monitoring from several distinct sources within a short timeframe.
Recommended Actions
Retain the blocklist entries and VirusTotal scan results for erebor.casa as reference points for future assessments. Compare OTX pulse records and PhishDestroy listings periodically to track any changes in observed intelligence.
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.
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-13 15:58:46 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 15:58:46 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-13 15:58:46 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 104.21.6.72.
威胁响应 Pipeline
发现
Analysis
Monitoring
7 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.
黑名单检测
见于 2 blocklists: MetaMask, SEAL
2026年10月13日
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月13日
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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)
