SSL certificate is invalid or expired. Issuer: Google Trust Services / WR1
証拠の概要
クリティカル
VirusTotal
18/91
URLScan
Stored capture
Assessment
rft28.vercel.app returned HTTP status 200 on 2026-10-01, according to the recorded HTTP check. The same record set shows a first observation date of 2026-09-17, which is earlier than the HTTP check.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 200 for rft28.vercel.app. The first observation date in the evidence is 2026-09-17. VirusTotal reported 18 detections across 91 scanners on 2026-10-01. The SSL certificate was scanned on 2026-09-23 and its issuer was Google Trust Services / WR1. The PhishDestroy internal listing was recorded as true, and the blocklist check date was 2026-10-01.
Interpretation
The VirusTotal figures and the HTTP status come from the same 2026-10-01 check, so they describe one point in time. The SSL scan on 2026-09-23 and the first observation on 2026-09-17 fall on different dates, so they cannot be directly aligned with the later checks. The PhishDestroy listing and the blocklist check share the 2026-10-01 date, which allows those two records to be compared together.
Recommended Actions
Reviewers should retain the dated records for rft28.vercel.app, including the HTTP check and the VirusTotal result, so later observations can be compared against them. Any subsequent check of rft28.vercel.app should be logged with its own date to show how the recorded values change over time. During review, avoid submitting sensitive information to rft28.vercel.app until the recorded status and detections have been reassessed.
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 10:11:10 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-13 10:11:10 UTClast content: 2026-10-13 10:11:10 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.
Threat First Observed2026-09-23 10:33:11 UTC
Domain ingestion complete. Initial state is marked as alive.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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)
