The domain goodlife-6jp.pages.dev was observed returning an HTTP 403 status on 2026-10-01, indicating restricted access at that time. On 2026-09-15, a PageSpeed scan reported a perfect performance score for this domain.
Recorded Evidence
PhishDestroy internally listed goodlife-6jp.pages.dev as of 2026-09-05. VirusTotal checked the domain on 2026-09-17, recording 16 detections out of 89 scanners. An SSL scan on 2026-09-15 identified Google Trust Services / WE1 as the certificate issuer. The HTTP check on 2026-10-01 returned status 403. The PageSpeed scan on 2026-09-15 reported a performance score of 100.
Interpretation
These records from PhishDestroy, VirusTotal, and other sources were collected on different dates, so each describes the domain at a separate point in time. The variation in observation dates means that changes in status or detections may have occurred between scans, and direct comparisons should account for this timing.
Recommended Actions
Retain the evidence for goodlife-6jp.pages.dev with all observation dates clearly noted for future reference. When reviewing or investigating, compare new findings against these dated records and avoid submitting any sensitive or private information to the domain. Revisit the domain periodically to track any changes in its status or listings over time.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Observed timelinelast reachable: 2026-09-05 18:28:15 UTCcurrent episode first observed: 2026-10-01 01:39:24 UTCobserved RIP window: 2026-09-05 18:28:15 UTC → 2026-10-01 01:39:24 UTC · 607.19hmidpoint estimate ≈ 2026-09-18 10:03:49 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.
기술 · 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: 16 detections
alphaMountain.ai
BitDefender
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
카스퍼스키
LevelBlue
Lionic
넷크래프트
소포스
URLQuery
VIPRE
Webroot
사이트 성능 분석
Google PageSpeed Insights — mobile performance audit of goodlife-6jp.pages.dev· checked Sep 15, 2026
100
Good
Performance
FCP
0.77s
First Contentful Paint
LCP
1.82s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.77s
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.
Domain Status Transition2026-09-15 10:00:18 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-15 05:53:12 UTC
Domain ingestion complete. Initial state is marked as alive.
위협 대응 Pipeline
발견
Analysis
Monitoring
10 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.
