solflare-wal.com was recorded with an HTTP status 404 on 2026-10-11, documenting a not found response at that time. Additionally, the domain was observed on external blocklists during the same period.
Recorded Evidence
MetaMask and SEAL both listed solflare-wal.com on their external blocklists as of 2026-10-11. OTX recorded four pulses for the domain on 2026-10-11. The registrar was Hosting Concepts B.V. d/b/a Registrar.eu, and the SSL certificate was issued by Let's Encrypt / YR1, both documented on 2026-10-11. The domain was registered on 2026-08-09, and PhishDestroy internally listed it as of 2026-10-11.
Interpretation
The HTTP status source documents a technical response from solflare-wal.com, measuring its availability at a specific moment. PhishDestroy provides an internal listing, which is a distinct type of record compared to external blocklists such as MetaMask and SEAL. OTX pulses represent another form of intelligence, capturing community-driven observations. These sources collectively offer a snapshot of the domain's recorded context without asserting any ongoing activity.
Recommended Actions
For solflare-wal.com, preserve the HTTP status and blocklist records for future comparison with new data. Retain OTX pulse counts and PhishDestroy internal listings as reference points for subsequent security reviews. Use these dated records to inform ongoing monitoring and evidence-based assessments of the domain.
탐지 회피 분석
클로킹 의심: 스캐너와 방문자 제목이 다름
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcome비활성reason: Http No Content70% confidence
Attributionsource: Current Http Probe
Evidence layersAvailability: Root path has no contentContent: Absent At RootDNS: ResolvedRegistration: Unknown
Latest HTTP observation비활성Http No Content70%2026-10-11 11:02:13 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 09:38:11 UTCcurrent episode first observed: 2026-10-11 11:02:13 UTCobserved RIP window: 2026-10-11 09:38:11 UTC → 2026-10-11 11:02:13 UTC · 1.40hmidpoint estimate ≈ 2026-10-11 10:20:12 UTC · precision high · 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.
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 09:38:11 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 194.238.57.99.
위협 대응 Pipeline
발견
Analysis
Notifications
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
최근에 저장된 확인 결과에 따르면 보고된 콘텐츠를 사용할 수 없습니다. 이는 변경의 원인이 누구인지, 원인이 무엇인지 확인하지 않습니다.
How we investigate & report
Public scans, evidence and abuse channels
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 (846 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 (UA):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and UA'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.
(UA)
