militarydefensewelfare.online is an impersonation phishing site whose name suggests an official military or defense welfare body. That kind of branding targets service members' families, partners and people approached by someone claiming to be a soldier. PhishDestroy first flagged the domain on 2026-09-03. It has been offline since 2026-10-14 and was still unreachable when checked on 2026-10-19.
How the scam works
Fake military welfare portals usually support a story told elsewhere: a "soldier" met online needs a leave permit, a welfare release or a communication fee, and the victim is sent to an official-looking site to pay it or submit identity documents. Payments are often requested in crypto or gift cards because they are hard to reverse. Victims lose the money they send and any personal or ID data they enter. When last captured, the page returned only the title "406 Not Acceptable," an error response rather than branded content, while our classification is impersonation phishing.
Evidence
Fourteen of 89 VirusTotal engines flagged the domain as of 2026-09-11. Those engines include Bfore.Ai PreCrime, BitDefender, CRDF, ESET, Emsisoft, Fortinet, G-Data and Gridinsoft, so several unrelated vendors independently reached the same verdict. The domain also appears in four AlienVault OTX threat pulses. Among blocklists, it is listed by PhishDestroy.
Infrastructure
The domain was registered through Spaceship, Inc. on 2025-11-03, about ten months before PhishDestroy detected it. That gap suggests the domain was either held in reserve or ran quietly before it was put to use. It was hosted in the US on the Aquiryn LLC network at 23.153.104.17, with a free Let's Encrypt certificate that gave it a padlock but says nothing about who runs it.
What to do
If you paid a "welfare," leave or release fee through this site, stop all further payments, because these schemes keep inventing new charges. Report the transfer to your bank, card issuer or the exchange you sent crypto from. If you uploaded ID documents or personal details, watch for identity fraud and consider a credit freeze. Report the contact who sent you the link to the platform where you met them, and to your national fraud authority. Defenders should block the domain and the 23.153.104.17 address and search mail and proxy logs for earlier visits.
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.
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.
