The domain morphilina.me was observed in several security intelligence sources, with a CryptoFirewall blocklist entry recorded on 2026-10-13. A PageSpeed performance score was also measured on the same date, providing a technical benchmark for the domain.
Recorded Evidence
On 2026-10-13, morphilina.me was listed on the CryptoFirewall external blocklist. VirusTotal checked the domain on 2026-10-11, recording 8 detections from 92 total scanners. OTX referenced morphilina.me in 6 pulses as of 2026-10-13. The domain is also listed internally by PhishDestroy, and its PageSpeed performance score was measured at 56 on 2026-10-13. The registration date is recorded as 2025-11-10 with the registrar Regional Network Information Center, JSC dba RU-CENTER.
Interpretation
VirusTotal records for morphilina.me contain quantitative detection data from a large set of scanners, offering insight into how the domain is viewed by various security vendors. The CryptoFirewall blocklist and OTX pulse references document that the domain has appeared in multiple external threat intelligence sources. These records provide a multi-faceted view of the domain's presence in security monitoring systems.
Recommended Actions
Preserve the VirusTotal detection record and the CryptoFirewall blocklist entry for morphilina.me for future reference. Compare the OTX pulse references and the PhishDestroy internal listing to track changes in external and internal intelligence sources. Retain the PageSpeed performance score as a technical point of comparison in subsequent reviews.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: StaleRegistration: Unknown
Latest HTTP observation활성 콘텐츠Ordinary HTTP content served90%2026-10-13 01:00:11 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-13 01:00:11 UTClast content: 2026-10-13 01:00: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.
Google PageSpeed Insights — mobile performance audit of morphilina.me· checked Oct 13, 2026
56
Needs Work
Performance
FCP
7.94s
First Contentful Paint
LCP
9.47s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
33ms
Total Blocking Time
SI
7.94s
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-12 23:34:32 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 132.243.113.25.
위협 대응 Pipeline
발견
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.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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.
(VN)
