VirusTotal
4 / 89
“YNPFM”
ynppek.com returned HTTP status 403 in a check dated 2026-10-01, a recorded response that does not by itself describe all content hosted on the domain. The same domain appears in the publisher-owned PhishDestroy internal listing, a separate observation from the HTTP result.
The domain was first observed on 2026-09-07 and registered on 2026-07-23 with registrar Name.com, Inc. An SSL scan on 2026-09-15 recorded issuer Google Trust Services / WE1. VirusTotal, checked 2026-09-17, reported 4 detections across 89 scanners, and OTX, checked the same date, showed 4 pulses. The HTTP check on 2026-10-01 resolved to IP address 188.114.97.9, in CA, associated with CloudFlare, Inc.
The PhishDestroy listing and the VirusTotal and OTX counts are distinct source records, each with its own scope and method, so they should be read separately rather than merged into one conclusion. The dates span from registration through the HTTP check, but the differing collection points do not establish that conditions changed between them. The HTTP 403 describes only the response recorded on that date, not the domain's full content or present state.
Preserve the PhishDestroy listing entry and the VirusTotal record for ynppek.com as separate source artifacts. Compare the VirusTotal record with the OTX record in a later review, and compare the HTTP response record against a future response for the same domain. Retain the first-observed and registration records alongside these for context.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
Provider response during scan: cloudflare_phishing_interstitial
Edge-IP reputation is not attributed to this domain.
rose.ns.cloudflare.comLocation describes the IP network.
995f3051ab146f4ee5b646072fe79e8f65acae321c9c35f356e857c6ce6a6f8eSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
1 community report
CategoryOTHER_INVESTMENT_SCAM
1. Summary A victim was induced by a fraudulent "investment/trading" platform to buy USDT and transfer it to an address controlled by the operation. The funds were moved, on-chain, through a single-use burner address into a high-volume automated consolidation wallet, then into a
“1. Summary A victim was induced by a fraudulent "investment/trading" platform to buy USDT and transfer it to an address controlled by the operation. The funds were moved, on-chain, through a single-use burner address into a high-volume automated consolidation wallet, then into a large secondary consolidator (4,622 transfers), which cashes out to KYC-verified deposit addresses at Binance, Bitget, and Coinmania. The exchange deposit addresses at the end of this chain are the actionable endpoints”
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
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