The domain polymarket.v2.v2i.us returned an HTTP status 403 during a check conducted on 2026-10-01, indicating a restricted or denied response at that time. Additionally, the domain was first observed on 2026-09-27, providing a recent timeline for its recorded activity.
Recorded Evidence
A VirusTotal scan performed on 2026-09-29 found 7 detections out of 91 scanners for polymarket.v2.v2i.us. The domain is included in the PhishDestroy internal listing as of the current evidence. A PageSpeed check on 2026-09-27 recorded a performance score of 32. The SSL certificate issuer was identified as Let's Encrypt / YR2 during a scan on 2026-09-28.
Interpretation
The VirusTotal results and PhishDestroy internal listing represent separate observations about polymarket.v2.v2i.us, each providing distinct information about the domain. The HTTP 403 status is specific to the check on 2026-10-01 and does not describe all potential responses from the domain. The sequence of dates across the different checks shows when each source recorded its findings, but does not indicate any direct change or trend in the domain's behavior.
Recommended Actions
For polymarket.v2.v2i.us, retain the VirusTotal scan record, the PhishDestroy internal listing, and the HTTP check record for future reference. These records should be compared separately to assess any changes or new observations over time. Preserve the PageSpeed and SSL scan results alongside these sources to maintain a complete set of dated evidence for ongoing monitoring.
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: ResolvedRegistration: Unknown
Latest HTTP observationReachable but protectedHTTP access restrictedAccess Restriction50%2026-10-13 10:11:08 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 10:11:08 UTClast content: 2026-10-13 01:45:12 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.
技术 · 5 identified
N
Nginx
Web serversReverse proxies
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Google PageSpeed Insights — mobile performance audit of polymarket.v2.v2i.us· checked Sep 27, 2026
32
Poor
Performance
FCP
20.32s
First Contentful Paint
LCP
20.77s
Largest Contentful Paint
CLS
0.002
Cumulative Layout Shift
TBT
1097ms
Total Blocking Time
SI
20.32s
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.
VirusTotal Detections Update2026-09-29 09:10:04 UTC
VirusTotal scanner detections updated from 5 to 7. Added scanner alerts: SOCRadar, Sophos.
VirusTotal Detections Update2026-09-29 08:07:56 UTC
VirusTotal scanner detections updated from 6 to 5. Resolved alerts: SOCRadar.
VirusTotal Detections Update2026-09-28 07:18:06 UTC
VirusTotal scanner detections updated from 5 to 6. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-27 10:46:55 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 35.214.225.47.
威胁响应 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.
