frosttreasury.pages.dev returned HTTP status 404 during an automated check dated 2026-10-01, so no standard page content was served at that moment. The same domain was first observed in available records on 2026-09-08, which gives an earlier reference point for comparison.
Recorded Evidence
PhishDestroy listed frosttreasury.pages.dev in its internal catalogue according to the recorded evidence. VirusTotal recorded 14 detections across 89 scanners for this domain on 2026-09-17. The HTTP check on 2026-10-01 produced the 404 response noted above, and the first observation of the domain is dated 2026-09-08.
Interpretation
The PhishDestroy listing, the VirusTotal scan dated 2026-09-17 and the HTTP check dated 2026-10-01 come from different points in time, so their observations are not directly interchangeable. Because the first observation on 2026-09-08 precedes both later checks, a reviewer can compare how each named source described the domain at its own recorded date. The differing dates mean the records should be read as separate snapshots rather than a single combined result.
Recommended Actions
Retain the existing records for frosttreasury.pages.dev, including the PhishDestroy listing, the VirusTotal figures and the dated HTTP response, so later checks can be compared against them. When new observations of frosttreasury.pages.dev become available, note their exact dates and set them beside these earlier entries. Avoid submitting sensitive information to frosttreasury.pages.dev while review is ongoing, since the recorded checks do not describe what the domain currently serves.
탐지 회피 분석
클로킹 의심: 스캐너와 방문자 제목이 다름
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-11 10:06:09 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:06:09 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.
기술 · 3 identified
H
HSTS
보안
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Last analyzed First positive detection Previous stored snapshot: 14 detections
alphaMountain.ai
BitDefender
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
넷크래프트
PhishFort
소포스
VIPRE
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.
Domain Status Transition2026-10-09 01:25:38 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-15 22:00:22 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-15 21:33:10 UTC
Domain ingestion complete. Initial state is marked as alive.
위협 대응 Pipeline
발견
Analysis
Monitoring
11 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.
