ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@purpleit.com.
The latest stored availability evidence still shows the domain reachable; 26 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
On 2026-10-01, event.vortexgptcom.com returned an HTTP 502 status code in a recorded check, a server-side error response at that time. The same domain was first observed on 2026-09-15, and a PhishDestroy internal listing flags it in that publisher-owned catalogue.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 502 for event.vortexgptcom.com. The first observation date for the domain is 2026-09-15. VirusTotal recorded 9 detections out of 91 scanners on 2026-09-25. The SSL certificate, scanned on 2026-09-15, was issued by Google Trust Services / WE1. The PhishDestroy internal listing entry is dated 2026-10-01.
Interpretation
The HTTP 502 record describes only the response captured during that check, not all content served by the domain. The VirusTotal count reflects scanner output on its own date, while the PhishDestroy internal listing reflects a separate catalogue entry. The first observation and SSL scan share a calendar date, but that alone does not establish simultaneous measurement. These records allow comparison of what each source captured without combining them into a single conclusion.
Recommended Actions
Preserve the HTTP status record for event.vortexgptcom.com and the PhishDestroy internal listing entry as separate source records. Compare the VirusTotal scan output against those records to see where the sources diverge. Retain the first observation and SSL certificate scan for later comparison. Recheck the domain's HTTP response and catalogue status before acting on any single record.
Certificate hostname mismatch·
発行者 Google Trust Services / WE1· stored validity ends in 17 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP の評判はこのドメインに起因しません。
ネームサーバー 2
bart.ns.cloudflare.com
teagan.ns.cloudflare.com
Location describes the IP network.
TLS証明書
Issuer
Google Trust Services / WE1
Valid from
2026-07-31 08:22:10
Valid until
2026-10-29 09:12:54
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-15 16:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprintb51377ed8552515f72d0011959dc1875f5eef8731c702653ac0f0d7b2008c241Certificate names · 1 SANs
vortexgptcom.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-11 10:08:22 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:08:22 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
Cloudflare
CDN
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Last analyzed Previous stored snapshot: 8 detections
alphaMountain.ai
BitDefender
CRDF
Forcepoint ThreatSeeker
Fortinet
G-Data
カスペルスキー
SOCRadar
ソフォス
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of event.vortexgptcom.com· checked Sep 15, 2026
98
Good
Performance
FCP
1.71s
First Contentful Paint
LCP
1.71s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.41s
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-03 01:54:24 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-27 10:41:21 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-16 17:30:44 UTC
VirusTotal scanner detections updated from 7 to 8. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-15 13:29:43 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.96.3.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
11 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.
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)
