Analysis indicates that the domain www.mgts.live is actively hosting a credential‑phishing page identified by the title “MGTCoin”. The site was registered on 31 Mar 2026 through NameCheap and is served behind Cloudflare (nameservers roan.ns.cloudflare.com and nola.ns.cloudflare.com, IP 188.114.97.3, located in Canada). TLS is provided by Let’s Encrypt (E8) and the site returns HTTP 200. Automated scans reveal a stack of PHP, Bootstrap, Swiper, OWL Carousel, jQuery UI, jQuery and Cloudflare Browser Insights, suggesting a typical web‑based lure rather than a specialized malware dropper. The domain appears on one public blocklist (PhishDestroy) and five of ninety‑four VirusTotal scanners have flagged it, while Gridinsoft assigns a trust score of 0 / 100. No further content analysis is available, so the exact credential‑collection mechanism and targeted brands remain unknown. Defenders should immediately block or sinkhole www.mgts.live at the DNS and proxy layers, monitor outbound connections to the associated Cloudflare IP, and add the domain to URL‑filtering policies. Continuous observation for newly‑registered look‑alike domains using the “mgts” string is advised, as the infrastructure indicates an opportunistic phishing campaign that could be leveraged against a broad audience.
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.
Certificate fingerprinta1159245e9aef9c86077d05d85a5945c151613b1daa260cbf60c61f1d2644d4eCertificate names · 1 SANs
mgts.live
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of duplicate-disabled-189213.invalid· checked Mar 31, 2026
49
Poor
Performance
FCP
6.9s
First Contentful Paint
LCP
12.06s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
315ms
Total Blocking Time
SI
10.1s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Registration & observation details1
Availability observations
Last reachable observation
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='duplicate-disabled-189213.invalid', port=80): Max retries exceeded with url: / (Caused by
duplicate-disabled-189213.invalid
Stored observation history1
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.
(US)
