On 2026-10-01, gfshsezwrdrf4.framer.wiki returned an HTTP 404 status code, indicating the requested resource was not found at that time. The domain was also observed to have a high PageSpeed performance score in a separate assessment.
Recorded Evidence
The domain was first observed on 2026-09-07. On 2026-09-15, a PageSpeed check recorded a performance score of 100. VirusTotal, checked on 2026-09-17, reported 12 detections out of 89 scanners. The domain is listed in the PhishDestroy internal catalogue. An HTTP check on 2026-10-01 returned a 404 status code.
Interpretation
These source records provide a timeline of technical and security-related observations for gfshsezwrdrf4.framer.wiki. The HTTP 404 response and PageSpeed score are distinct technical measurements, while the VirusTotal and PhishDestroy catalogue entries reflect security assessments. The dates allow comparison of these observations, but do not establish any change or activity between them.
Recommended Actions
For gfshsezwrdrf4.framer.wiki, retain the VirusTotal scan result and the PhishDestroy internal listing for reference. Compare the HTTP status code and PageSpeed score in future reviews to monitor any changes. Avoid submitting sensitive information to the domain based on its recorded detections. Keep all source records for chronological context and further analysis.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Attributionactor class: Hostingmechanism: Placeholder Pagesource: Current Http Probe
Evidence layersAvailability: Root path has no contentContent: Absent At RootDNS: ResolvedRegistration: Unknown
Latest HTTP observation非活动Hosting Placeholderactor class: HostingPlaceholder Page45%2026-10-13 01:15:56 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-07 20:28:24 UTCcurrent episode first observed: 2026-10-01 01:39:29 UTCobserved RIP window: 2026-09-07 20:28:24 UTC → 2026-10-01 01:39:29 UTC · 557.18hmidpoint estimate ≈ 2026-09-19 11:03:56 UTC · precision low · 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.
技术 · 4 identified
F
Framer Sites
CMSPage builders
Framer is a no-code web design platform for designing and publishing responsive websites.
Last analyzed First positive detection Previous stored snapshot: 12 detections
alphaMountain.ai
CyRadar
ESET
Forcepoint ThreatSeeker
G-Data
Gridinsoft
LevelBlue
Lionic
SOCRadar
Sophos
VIPRE
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of gfshsezwrdrf4.framer.wiki· checked Sep 15, 2026
100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
0.76s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.76s
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.
VirusTotal Detections Update2026-09-17 15:15:13 UTC
VirusTotal scanner detections updated from 10 to 12. Added scanner alerts: LevelBlue, SOCRadar.
Domain Status Transition2026-09-15 22:00:20 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-15 19:53:12 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
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.
(US)
