outgentportal.vercel.app returned HTTP status 404 in the recorded check dated 2026-10-01, a response that describes only that request and not all content on the domain. Google Safe Browsing flagged the domain for social engineering on 2026-09-21, and the PhishDestroy internal listing also records it.
Recorded Evidence
Google Safe Browsing recorded a social engineering flag on 2026-09-21. VirusTotal recorded 16 detections across 89 scanners on 2026-09-21. PhishDestroy's internal listing records the domain, and the first observation date is 2026-09-17. The SSL scan on 2026-09-21 named Google Trust Services / WR1 as issuer, and the PageSpeed check that day returned a performance score of 100. The HTTP check on 2026-10-01 returned status 404.
Interpretation
The Safe Browsing flag, VirusTotal detections and PhishDestroy listing are separate source records with their own scopes, so they should be read individually rather than merged into one verdict. The first observation on 2026-09-17 precedes the 2026-09-21 checks, while the 2026-10-01 HTTP response falls later; these dates order the records without showing that any condition changed. The 404 response documents one request outcome, not the domain's full content.
Recommended Actions
For outgentportal.vercel.app, preserve the Safe Browsing flag record and the PhishDestroy listing as separate source documents. Preserve the VirusTotal detection record and the HTTP response record in the same way. Compare these records against one another rather than treating any single entry as complete. Review the domain's recorded status before relying on it for any purpose, and retain the dated source entries for future reference.
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 22:06:54 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:06:54 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.
技术 · 2 identified
V
Vercel
PaaS
Vercel is a cloud platform for static frontends and serverless functions.
Google PageSpeed Insights — mobile performance audit of outgentportal.vercel.app· checked Sep 21, 2026
100
Good
Performance
FCP
0.8s
First Contentful Paint
LCP
0.8s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.8s
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-10-09 01:43:27 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-21 22:00:22 UTC
Domain state transitioned from alive to dead.
Status Check2026-09-21 12:56:54 UTC
Telemetry event observed.
Threat First Observed2026-09-21 10:03:11 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
13 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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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)
