SSL certificate is invalid or expired. Issuer: Google Trust Services / WR1
증거 요약
심각
VirusTotal
18/91
URLScan
Stored capture
Assessment
On 2026-10-08 the domain xbu55.vercel.app returned HTTP status 200, indicating a live server response. Google Safe Browsing flagged the page for social engineering on 2026-10-06.
Recorded Evidence
Google Safe Browsing detected social engineering threats on 2026-10-06. VirusTotal recorded 18 detections out of 91 scanners on 2026-10-01. The PhishDestroy internal catalogue listed the domain on 2026-10-08. SSL scanning by Google Trust Services occurred on 2026-09-23.
Interpretation
The recorded evidence spans multiple dated observations, showing a documented server response, a browser warning, and third-party detection results. The PhishDestroy listing indicates internal classification of the domain as a potential risk.
Recommended Actions
For xbu55.vercel.app, preserve the Google Safe Browsing threat record and VirusTotal detection report for comparison. Review the PhishDestroy internal listing alongside the urlscan report for context. Avoid relying on the HTTP 200 response alone when assessing safety.
탐지 회피 분석
클로킹 의심: 스캐너와 방문자 제목이 다름
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeReachable but protectedreason: HTTP access restricted50% confidence
Attributionmechanism: Access Restrictionsource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: StaleRegistration: Unknown
Latest HTTP observationReachable but protectedHTTP access restrictedAccess Restriction50%2026-10-13 01:45:27 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-13 01:45:27 UTClast content: 2026-10-12 10:11:37 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.
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.
Status Check2026-09-23 16:00:15 UTC
Telemetry event observed.
Threat First Observed2026-09-23 10:33:11 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.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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.
(US)
