93414.xyz is a numeric .xyz domain on the PhishDestroy blocklist. PhishDestroy first saw it on 2026-08-10. No impersonated brand or page title has been tied to it, so it is listed as suspicious rather than as a named scheme. As of 2026-10-19 the domain still resolves, but it serves no reachable content, which means it could be reactivated at any time.
How the scam works
The available evidence points to phishing. Spamhaus files the domain under its phishing category, and a brand-protection vendor is among those flagging it. Disposable numeric domains like this one are commonly used to host short-lived pages that trick visitors into entering credentials or personal details on a lookalike form. No specific lure or target has been confirmed for 93414.xyz. Treat any page it shows, and any link pointing to it, as hostile.
Evidence
On 2026-09-13, VirusTotal showed 5 of 89 engines flagging the domain: alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, PhishFort and SOCRadar. That count is modest, but it comes from a mix of reputation, web-filtering and anti-phishing vendors rather than a single source. Spamhaus DBL independently lists it as DBL_PHISH. It also appears in four AlienVault OTX threat pulses, which shows that several analysts have tracked it separately.
Infrastructure
The domain was registered on 2026-03-17 through Gname.com Pte. Ltd., almost five months before PhishDestroy picked it up. That gap fits a domain bought ahead of time and held until it was needed. It resolves to 207.56.0.115 on the Zillion Network Inc. network in Canada.
What to do
If you typed a password into a page on this domain, change it right away. Do the same anywhere else you reuse that password, and turn on two-factor authentication. If you shared personal or payment details, watch for follow-up phishing and contact your bank about any card you entered. Defenders should block 93414.xyz and its IP at DNS and proxy level. They should also search their logs for past connections and report any new content on the domain to its host and registrar.
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
(SG)
