Security engines reporting a detection: 4. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
On 2026-10-09, s0l.app was observed as listed on the MetaMask and SEAL external blocklists, according to a recorded source observation. Additional evidence from the same date documents its presence on multiple external blocklists.
Recorded Evidence
On 2026-10-09, s0l.app appeared on both the MetaMask and SEAL external blocklists. VirusTotal recorded 4 detections out of 92 scanners for this domain on 2026-10-09. PhishDestroy internally listed s0l.app, and OTX referenced the domain in 3 separate pulses, all on the same date. The registrar was Namecheap Inc., and the SSL certificate was issued by Let's Encrypt / YR1, with these details also recorded on 2026-10-09.
Interpretation
PhishDestroy’s internal listing contains a record of s0l.app as part of its monitored domains. VirusTotal provides a measurement of scanner-based detections, representing technical findings from multiple sources. The MetaMask and SEAL blocklist entries, as well as OTX pulse references, expand the context of network intelligence for s0l.app on the recorded date.
Recommended Actions
Retain the VirusTotal, OTX, and PhishDestroy records for s0l.app for ongoing reference and comparison. Review the MetaMask and SEAL blocklist entries alongside these records to track any future developments. Use the PageSpeed performance score as a technical baseline for subsequent evaluations of s0l.app.
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
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
RegistrationCreated Mar 25, 2026 (197d)—Expires Mar 25, 2027
Technical detailsProvenance & timestamps
First DetectedOct 9, 2026
Submitted URLhttp://s0l.app/
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.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-09 15:59:51 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-09 15:59:51 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.
Google PageSpeed Insights — mobile performance audit of s0l.app· checked Oct 9, 2026
70
Needs Work
Performance
FCP
3.13s
First Contentful Paint
LCP
5.78s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
63ms
Total Blocking Time
SI
4.54s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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-09 15:59:51 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 216.198.79.1.
Threat Response Pipeline
Discovery
Analysis
Monitoring
8 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.
5 evidence signal groups linked0 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 · s0l.app
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.
(SE)
