plencos.com is an impersonation phishing site: it passed itself off as a legitimate service so visitors would trust it with sensitive information. PhishDestroy first flagged it on 2026-09-15. The site went offline on 2026-09-16, and as of 2026-10-19 its DNS no longer resolves. Anyone who interacted with it before then should still act on the steps below.
How the scam works
Impersonation pages copy the look, wording and flow of a real brand. Victims land on them through ads, search results or messages, then type in credentials, personal details or payment information that go straight to the operator. When PhishDestroy captured it, the page showed only the title "Just a moment...", a generic browser-check screen rather than branded content. That differs from the impersonation we classified, which is based on the site's purpose rather than that loading screen. Stolen logins are typically reused quickly to take over accounts or sold on.
Evidence
Independent detection is thin but consistent. On 2026-09-15, 3 of 89 VirusTotal engines flagged the domain: alphaMountain.ai, Gridinsoft and SOCRadar. Spamhaus lists it in its Domain Block List under the malware category, so mail and DNS filters using that feed will block it. One AlienVault OTX threat pulse references it, and it appears on the PhishDestroy blocklist. The low VirusTotal count reflects how briefly the site was live, not a clean bill of health.
Infrastructure
The domain was registered through NameCheap, Inc. on 2026-04-17, roughly five months before it surfaced as a phishing page. A domain left idle that long before use is a common pattern, since an aged domain draws less suspicion from filters than a fresh one. The site was served from a US-based network over a certificate from Google Trust Services. It stopped responding one day after we detected it.
What to do
If you entered a password on plencos.com, change it right away on the real service and on any other account that shares it. Then turn on app-based two-factor authentication and review recent logins and sessions. If you submitted card or banking details, contact your bank to block the card and dispute any unfamiliar charges. Watch for follow-up phishing emails that use the personal details you entered. Defenders should block the domain at DNS and the mail gateway and search proxy logs for visits since 2026-09-15 to find users who may need credential resets.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 01:14:04 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-15 22:00:17 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-15 22:00:17 UTC → 2026-09-30 16:14:55 UTC · 354.24hmidpoint estimate ≈ 2026-09-23 07:07:36 UTC · precision low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
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)
