Security engines reporting a detection: 10. Public blocklists reporting a match: 3. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@ownregistrar.com.
The latest stored availability evidence still shows the domain reachable; 7 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
SSL certificate is invalid or expired. Issuer: Let's Encrypt / YE2
Evidence Summary
Critical
VirusTotal
10/91
OTX
4 community refs
URLScan
Stored capture
Assessment
The domain solfre.xyz appeared on two external blocklists according to records from 2026-10-05, with MetaMask and SEAL both listing it. An internal listing was also noted around the same time, providing additional context for its detection.
Recorded Evidence
MetaMask and SEAL each included solfre.xyz on their blocklists as of 2026-10-05. The domain was first observed in monitoring sources on 2026-10-04. Phishdestroy also recorded an internal listing. Registration was through OwnRegistrar, Inc. on 2026-10-02, and Let's Encrypt / YE2 issued its SSL certificate, which was scanned on 2026-10-04.
Interpretation
The inclusion of solfre.xyz on both MetaMask and SEAL blocklists shows that multiple external sources recorded its presence. Internal monitoring further documented the domain, and the close timing of these records highlights a period of increased observation. The registration and SSL scan dates provide background on when the domain became visible to monitoring systems.
Recommended Actions
Review of solfre.xyz should reference its presence on MetaMask and SEAL blocklists, as well as the internal listing. Preserve these source records for future comparison and to track any updates. Additional monitoring for changes in external blocklist status is recommended.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='solfre.xyz', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SOC
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
RegistrationCreated Oct 2, 2026 (9d · Very New!)—Expires Oct 2, 2027
Technical detailsProvenance & timestamps
First DetectedOct 4, 2026
DOM Analysisanalyzed Oct 9, 2026score 100/1001 brand signal
Submitted URLhttp://solfre.xyz/
Favicon Hash
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 10:38:39 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-04 05:39:14 UTCcurrent episode first observed: 2026-10-05 22:25:19 UTCobserved RIP window: 2026-10-04 05:39:14 UTC → 2026-10-05 22:25:19 UTC · 40.77hmidpoint estimate ≈ 2026-10-05 02:02:16 UTC · precision medium · basis bounded
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.
Last analyzed First positive detection Previous stored snapshot: 10 detections
alphaMountain.ai
CRDF
CyRadar
Emsisoft
Forcepoint ThreatSeeker
Fortinet
Kaspersky
Netcraft
Seclookup
Webroot
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-04 05:39:14 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 104.21.31.117.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
12 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.
Blocklist hits included with submission:MetaMask, SEAL
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (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.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
6 evidence signal groups linked1 reports recordedUnverified
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · solfre.xyz
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
