tr.mertking-offical22.net is a suspicious domain on the PhishDestroy blocklist. Its name carries a "tr." prefix and the misspelling "offical", but no specific brand or audience has been confirmed. PhishDestroy first saw it on 2026-08-09. As of 2026-10-19 the server still responds, but no page content loads.
How the scam works
The page currently returns only a "403 Forbidden" title, while independent security vendors and Spamhaus have tagged the domain as phishing. A forbidden page does not show what the site served earlier or may serve again, so no specific scheme is confirmed here. Phishing verdicts usually mean a page that harvests logins, personal details or payments, or tricks visitors into sending money. Anyone reaching this domain through a message, ad or social post should treat that lure as an attempt to collect credentials or funds.
Evidence
On 2026-09-16, 10 of 89 VirusTotal engines flagged the domain. They include alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Kaspersky and PhishFort, a mix of mainstream antivirus firms and a phishing-focused takedown provider. Spamhaus lists it in its domain blocklist under the phishing category, which matters because mail filters widely use that list to block links. Apart from PhishDestroy, no other blocklist carries it.
Infrastructure
The domain was registered on 2026-07-28 through Cloudflare, Inc. and was on PhishDestroy's radar just 12 days later. That short gap is typical of throwaway domains set up for a single campaign. It is hosted on the Omegatech LTD network in the Netherlands and uses a free Let's Encrypt certificate. That certificate gives the site a padlock in the browser, which says nothing about whether the site is legitimate.
What to do
If you entered a password or login on this domain, change it at once on the real service and anywhere you reused it, and turn on two-factor authentication. If you made a payment or shared card or bank details, contact your bank or payment provider to dispute the charge and watch for follow-up fraud. Report any message that led you here to the platform it came from. Defenders should block the domain and its hosting address at DNS and the mail gateway, and search logs for earlier visits. Hosts using the Spamhaus phishing listing are already covered.
Certificate fingerprint249ea60953aaa54f0a7b4ed75c7505e25c72e2474d0da3e7a656dbaa54694551Certificate names · 1 SANs
obsidian-project.site
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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)
