On 2026-10-01, polymarket.com-events.v2i.us returned an HTTP 403 status in a recorded observation. The same source records the IP address 35.214.225.47, located in NL and associated with Google Cloud (europe-west4).
Recorded Evidence
The domain was first observed on 2026-09-27, when a PageSpeed performance score of 42 was recorded. An SSL certificate issued by Let's Encrypt / YR2 was scanned on 2026-09-27. VirusTotal recorded 9 detections across 91 scanners on 2026-09-29. PhishDestroy's internal listing was recorded on 2026-10-01, and the blocklist check shares that date.
Interpretation
The PhishDestroy listing and HTTP check both carry the 2026-10-01 date, while the SSL and PageSpeed scans date to 2026-09-27 and the VirusTotal scan to 2026-09-29. Because these named sources observed the domain on different dates, their results describe separate moments rather than one synchronized snapshot. Comparing them requires keeping each source's own date attached to its value.
Recommended Actions
For polymarket.com-events.v2i.us, retain the dated records from each named source so later observations can be compared against them. When reviewing the domain, avoid submitting sensitive information, and note that a dated HTTP response does not establish present availability. Subsequent checks should be logged with their own dates before any comparison is drawn.
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: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-13 10:10:35 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 10:10:35 UTClast content: 2026-10-13 10:10:35 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.com-events.v2i.us· checked Sep 27, 2026
42
Poor
Performance
FCP
22.21s
First Contentful Paint
LCP
52.35s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
539ms
Total Blocking Time
SI
22.21s
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-28 04:45:59 UTC
VirusTotal scanner detections updated from 11 to 9. Resolved alerts: Lionic, Sophos.
VirusTotal Detections Update2026-09-28 02:12:36 UTC
Domain ingestion complete. Initial state is marked as alive 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.
(CA)
