PhishDestroy first observed fortvexa.top on Oct 5, 2026. Current evidence score: 25/100 (medium).
One source contains a positive finding: Spamhaus DBL. Spamhaus DBL: DBL_SPAM on Oct 5, 2026 at 02:30 UTC. Additional recorded evidence: URLScan captured the page on Oct 5, 2026 at 01:03 UTC.
The collector marked the hostname reachable on Oct 5, 2026 at 01:03 UTC, but did not retain the HTTP response code. Latest classified outcome: unknown; cause probe inconclusive on Oct 4, 2026 at 23:03 UTC. Registration records for the domain list Spaceship, Inc. as the registrar and Aug 25, 2026 as the creation date. At collection time, the hostname resolved to 46.29.26.38 on AS132359 (M/S ROBI TRADERS). The recorded endpoint location is Istanbul, TR. DOM analysis on Oct 5, 2026 at 02:20 UTC returned 15/100. The evidence archive retains 3 visual captures from PhishDestroy and URLScan; the captures preserve the landing-page appearance.
The source finding supports the recorded classification.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
RegistrationCreated Aug 25, 2026 (40d · New)—Expires Aug 25, 2027
Technical detailsProvenance & timestamps
First DetectedOct 5, 2026
DOM Analysisanalyzed Oct 5, 2026score 15/100
Submitted URLhttps://fortvexa.top/
Favicon Hash
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-05 01:03:09 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-05 01:03:09 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-10-05 01:03:09 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 46.29.26.38.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
fortvexa.top detected and queued for full analysis
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.
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Oct 5, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 5, 2026
Sent Report Recorded
Stored outgoing record associated with registrar Spaceship, Inc., 2 abuse contacts
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.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · fortvexa.top
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(US)
