VirusTotal
4 / 91 engine detections
Open reportmg-market-ssylka.ru is a blocklisted domain detected by PhishDestroy on 2026-09-28. Risk: critical (71/100). Hosting: Cloudflare, Inc. VirusTotal: 4/91 engines flag it. Do not enter credentials or connect a wallet.
“mg-market-ssylka.ru | 523: Origin is unreachable”
4 / 91 engine detections
Open report2 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
mg-market-ssylka.ru is an impersonation phishing page built around a lure of a "market link." "Ssylka" is Russian for "link," so the domain is aimed at Russian-speaking users searching for a working entry point to a marketplace. PhishDestroy first flagged it on 2026-09-28. As of 2026-10-19 the page content was unreachable and the site's state could not be confirmed.
Link-portal impersonation relies on people who search for a site's "current link" or "mirror" instead of typing a known address. The fake domain presents itself as the genuine gateway, then shows a copied login or account page that captures whatever the visitor enters. Victims typically lose their account credentials, and any balance or funds tied to that account. When last loaded, the page title showed a Cloudflare "523: Origin is unreachable" error rather than impersonation content, while our classification remains impersonation phishing.
On 2026-10-01, four of 91 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker and SOCRadar. That is a modest count, but the four vendors are independent and use different detection methods. The domain also appears in two AlienVault OTX threat pulses, which means other researchers have tied it to malicious activity. Among blocklists, it is carried by PhishDestroy.
The domain resolves to 172.67.139.74 on Cloudflare's network, geolocated to Canada. Because Cloudflare acts as a reverse proxy, that address belongs to Cloudflare and not to the operator, so the real server stays hidden. The 523 error means Cloudflare could not reach the origin behind it. The site uses a free automated certificate from the E7 issuer, so its padlock only shows the connection is encrypted and says nothing about whether the site is legitimate.
If you entered a username or password here, change it right away on the real service and on any other site where you reuse it. Turn on two-factor authentication and review recent logins, sessions and balance changes. Open marketplaces only from an address you have already verified, never from search results or link-sharing pages. Defenders should block mg-market-ssylka.ru at DNS and proxy level and check logs for past visits. Reports to Cloudflare can help get the hidden origin server traced and taken down.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 019d00d0-787c-767e-af22-c12f89790779 |
|---|---|
| Final url | https://mg-market-ssylka.ru/ |
| Status | 200 |
| Ip | 172.67.139.74 |
| Contacted domains | [
"mc.yandex.com",
"mc.yandex.ru",
"fonts.gstatic.com",
"static.cloudflareinsights.com",
"fonts.googleapis.com"
] |
| Contacted IP addresses | [
"172.253.115.94",
"87.250.251.119",
"104.16.80.73",
"142.251.163.95",
"172.67.139.74"
] |
| Asns | [
"15169",
"13238",
"13335"
] |
| Countries | [
"US",
"RU"
] |
| Document hash | b40a200f07465b1544d1704e6d36c8b4fc6ccb17e543dcef14f3a5c1333ca1a5 |
| Globals | [
"ym",
"__cfBeacon",
"Ya",
"yaCounter106507079",
"dataLayer"
] |
| Cookies | [
"bh",
"_ym_uid",
"_ym_d",
"_ym_isad",
"sync_cookie_csrf",
"yabs-sid",
"i",
"yandexuid",
"yuidss",
"ymex",
"receive-cookie-deprecation"
] |
| Storage keys | [
"_ymBRC",
"_ym_synced",
"_ym106507079_lsid",
"_ym106507079:0_reqNum",
"_ym_uid",
"_ym_retryReqs"
] |
| Tls | {
"san": [
"*.mg-market-ssylka.ru",
"mg-market-ssylka.ru"
],
"cipher": "AES_128_GCM",
"issuer": "E7",
"subject": "mg-market-ssylka.ru",
"protocol": "QUIC",
"valid_to": "2026-06-09T10:26:31Z",
"valid_from": "2026-03-11T10:26:32Z"
} |
| Domain age days | 7 |
| Apex age days | 7 |
| Tls age days | 7 |
| Tls valid days | 89 |
| Requests | 16 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 80,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "cloudflare",
"content-type": "text/html"
} |
Observed: · Retrieved:
| Uuid | 14fb877d-2185-42eb-85df-627c869132d1 |
|---|---|
| Final url | https://mg-market-ssylka.ru/ |
| Status | 523 |
| History | [
{
"url": "https://mg-market-ssylka.ru/",
"status": 523
}
] |
| DOM structure hash | 44f83b86670a53701e60f71195a3f41260783e3e1297f0ec6a48f6f4d16a372e |
| Document hash | fbac9d1fa05d271713e9b41a6c8b588ee7e5e01d6d6fd3f8f7468cad872c6ad9 |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "mg-market-ssylka.ru",
"type": "A",
"value": "172.67.139.74"
},
{
"name": "mg-market-ssylka.ru",
"type": "A",
"value": "104.21.70.205"
},
{
"name": "mg-market-ssylka.ru",
"type": "AAAA",
"value": "2606:4700:3035::6815:46cd"
},
{
"name": "mg-market-ssylka.ru",
"type": "AAAA",
"value": "2606:4700:3034::ac43:8b4a"
}
] |
| Dnssec valid | false |
| Ip | 172.67.139.74 |
| Registration record | {
"registrar": "REGRU-RU",
"created": "2026-03-11T08:41:45Z",
"expires": "2027-03-11T08:41:45Z",
"nameservers": [
"brenna.ns.cloudflare.com",
"louis.ns.cloudflare.com"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 53,
"malicious": 3,
"suspicious": 2,
"undetected": 34
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"SOCRadar": "suspicious",
"Gridinsoft": "suspicious",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Tags | [
"dga"
] |
| Categories | {
"Dr.Web": "drugs",
"alphaMountain.ai": "Phishing (alphaMountain.ai)",
"Forcepoint ThreatSeeker": "phishing and other frauds"
} |
| Created | 2026-03-11T00:00:00Z |
| First seen | 2026-03-11T11:42:13Z |
| DNS records | [
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3035::6815:46cd"
},
{
"ttl": 300,
"type": "A",
"value": "104.21.70.205"
},
{
"ttl": 21600,
"type": "NS",
"value": "louis.ns.cloudflare.com"
},
{
"ttl": 1800,
"type": "SOA",
"rname": "dns.cloudflare.com",
"value": "brenna.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "A",
"value": "172.67.139.74"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3034::ac43:8b4a"
},
{
"ttl": 21600,
"type": "NS",
"value": "brenna.ns.cloudflare.com"
}
] |
| Dns at | 2026-10-15T23:28:08Z |
| Jarm | 27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c |
| Certificate | {
"san": [
"*.mg-market-ssylka.ru",
"mg-market-ssylka.ru"
],
"issuer": "Let's Encrypt / YE2",
"serial": "5a144ec3965e9533294eed412a0a306c403",
"sha256": "618691461b8f55d1ebb923890db4717c76cb96c4d0d7354a6b4955ecc977c5f3",
"subject": "mg-market-ssylka.ru",
"valid_to": "2026-12-03T21:24:38Z",
"valid_from": "2026-09-04T21:24:39Z"
} |
No. PhishDestroy classifies mg-market-ssylka.ru as a blocklisted domain (risk: critical, 71/100); it was first detected on 2026-09-28. VirusTotal: 4/91 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on mg-market-ssylka.ru. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
618691461b8f55d1ebb923890db4717c76cb96c4d0d7354a6b4955ecc977c5f3*.mg-market-ssylka.rumg-market-ssylka.ruSaved 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 mg-market-ssylka.ru · checked Sep 28, 2026
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
3→4
2→3
1→2
0→1
No threat flag
View source4/91 engine detections
View source2 community references
View sourcemg-market-ssylka.ru
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
mg-market-ssylka.ru
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
mg-market-ssylka.ru)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.