The domain myriads.market is a generic phishing site designed to deceive users into disclosing sensitive information, such as login credentials or personal data. It does not impersonate a specific brand or utilize a known drainer kit. As of the latest verification, myriads.market has been taken offline, though it previously posed an elevated risk to visitors.
Technical analysis of myriads.market reveals limited but notable detection. The domain was flagged by 2 of 95 security vendors on VirusTotal, including Gridinsoft and SOCRadar, with a Gridinsoft trust score of 0/100. It appears on 3 security blocklists, specifically PhishDestroy, MetaMask, and SEAL. Registered through HOSTINGER operations, UAB on February 21, 2026, the domain resolved to the IP address 84.32.84.32, located in Lithuania under AS47583 Hostinger International Limited. No SSL certificate was issued, and the observed page title was 'myriad.en-int.com'. The domain used nameservers ns1.dns-parking.com and ns2.dns-parking.com and returned an HTTP 429 status code at the time of assessment.
Users who may have interacted with myriads.market should take immediate action to secure their accounts. If login credentials were entered, change passwords for all affected accounts and enable two-factor authentication where available. Monitor accounts for unauthorized activity and report any suspected fraud to relevant financial institutions. To report the phishing domain, submit it to platforms such as Google Safe Browsing, PhishTank, or the Anti-Phishing Working Group. Additionally, victims can file complaints with local cybercrime authorities or consumer protection agencies.
Extracted from stored page analysis
Observed indicators
20 wallet · 0 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
IoC Extractionscanned 2026年8月2日20 wallet · 0 Telegram IoCs
Submitted URLhttp://myriads.market/
ICANN OVERSIGHT
認定と RAA の背景
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.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 01:09:21 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-06-15 22:24:12 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-15 22:24:12 UTC → 2026-09-30 16:14:55 UTC · 2,561.85hmidpoint estimate ≈ 2026-08-08 07:19:33 UTC · precision very low · basis bounded
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.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='myriads.market', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
myriads.market
保存済みの結果
到達不能
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
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.
(LT)
