PhishDestroy identifies www.dofus-retro-devblog.com as an active crypto credential theft portal masquerading as the Dofus Retro developer blog. The domain was created on April 25, 2026, using Hosting Concepts B.V. (Registrar.eu) and resolved to IP 176.123.0.199 at the time of analysis. The site leverages a Let’s Encrypt SSL certificate to mimic legitimacy, while security blocklists and scanning engines (2 out of 95 on VirusTotal) have already flagged its malicious nature. This domain represents a targeted threat to gamers and cryptocurrency users who may be tricked into entering wallet credentials or downloading malicious files under the guise of accessing exclusive game content or development updates. The combination of a recently registered domain, low detection rate on VirusTotal, and presence on one blocklist indicates elevated risk and opportunistic behavior. Attackers registered the domain through a European registrar and deployed it rapidly to capitalize on interest in retro gaming communities and crypto tokens associated with in-game assets. The use of a legitimate-looking subdomain (devblog) and SSL certificate are classic tactics to bypass browser warnings and social engineering filters. Unlike generic phishing pages, this portal specifically harvests cryptocurrency wallet private keys or mnemonic phrases under the pretense of unlocking beta features or rare in-game items. Users who visited www.dofus-retro-devblog.com should immediately disconnect from any associated wallets, revoke any session tokens, and perform a full malware scan. Do not re-enter any credentials or seed phrases on this site. Report the domain to your antivirus provider and browser vendor using official reporting channels. If funds were lost, contact your wallet provider and file a complaint with local cybercrime units. Always verify URLs via official channels and use hardware wallets or two-factor authentication when transacting.
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 fingerprint7d58094470897f3aed4a9e98badc8d679548cd445ca4db054354f4b8b67d2fc1Certificate names · 1 SANs
dofus-retro-devblog.com
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-216098.invalid· checked May 11, 2026
66
Needs Work
Performance
FCP
3.32s
First Contentful Paint
LCP
10.57s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
4.72s
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-216098.invalid', port=80): Max retries exceeded with url: / (Caused by
duplicate-disabled-216098.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.
(MA)
