Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 8. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
mydpd.cflxv.help favicon

mydpd.cflxv.help

In short

PhishDestroy stores a record for mydpd.cflxv.help. Source observations are dated separately; missing checks do not establish safety.

“mydpd.cflxv.help”

Review the evidence
Registrar
United StatesNameSilo
Resolved IP
United States209.141.47.167FranTech Solutions
First observed
Oct 27, 2026
PhishDestroy assessment Critical
100/100
Evidence score
First observed Oct 27, 2026 16:36 UTC · PhishDestroy
Risk signals
VirusTotal detections: 8/92 Spamhaus DBL: phishing domain Google Safe Browsing: threat flag recorded
VirusTotal
8 / 92
engine detections ·
Google Safe Browsing
Flagged
URLScan
Malicious
Page captures
3
open gallery
Oct 27, 2026
X Telegram API

Questions about mydpd.cflxv.help

Is mydpd.cflxv.help legit?

PhishDestroy stores a record for mydpd.cflxv.help. Source observations are dated separately; missing checks do not establish safety.

Is mydpd.cflxv.help safe to connect a wallet?

This report does not record which wallet requests mydpd.cflxv.help makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used mydpd.cflxv.help?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Source evidenceVirusTotal 8 / 92 · Google Safe Browsing: flagged 7 sources

VirusTotal

8 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
46
Malicious
7
Suspicious
1
Undetected
38

Vendor labels

CRDF
malicious
ESET
phishing
G-Data
phishing
Sophos
phishing
Fortinet
phishing
SOCRadar
suspicious
Gridinsoft
phishing
Google Safe Browsing
phishing

Reputation score

0

Registrar

NameSilo, LLC

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    7207
    Type
    A
    Value
    209.141.47.167

DNS records observed

JARM fingerprint

29d29d00029d29d00042d42d00000090d94d1f02cef4051cfd1d66dbe44eb0

Certificate

Subject alternative names
  • mydpd.cflxv.help
Issuer
Let's Encrypt / YR2
Serial
6a4c9d11f99778692a3b1152c3e773d3bb
SHA-256
87d858eaa23a98acebffc008eef94f7aedce632bf2de2da25e713d90c00c9b05
Subject
mydpd.cflxv.help
Valid until
Valid from

Registration record

Registrar
NameSilo, LLC
Registrar IANA ID
1479
Registrar URL
https://www.namesilo.com
Registered
Updated
Expires
Status
  • addPeriod
  • clientTransferProhibited
  • serverTransferProhibited
Nameservers
  • ns1.dnsowl.com
  • ns2.dnsowl.com
  • ns3.dnsowl.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 7,
    "suspicious": 1,
    "undetected": 38
}
Vendor labels
{
    "CRDF": "malicious",
    "ESET": "phishing",
    "G-Data": "phishing",
    "Sophos": "phishing",
    "Fortinet": "phishing",
    "SOCRadar": "suspicious",
    "Gridinsoft": "phishing",
    "Google Safe Browsing": "phishing"
}
Reputation
0
Registrar
NameSilo, LLC
Created
2026-10-26T09:28:40Z
Expires
2027-10-26T23:59:59Z
Updated
2026-10-26T09:28:43Z
First seen
2026-10-26T10:26:10Z
DNS records
[
    {
        "ttl": 7207,
        "type": "A",
        "value": "209.141.47.167"
    }
]
Dns at
2026-10-27T16:32:59Z
Jarm
29d29d00029d29d00042d42d00000090d94d1f02cef4051cfd1d66dbe44eb0
Certificate
{
    "san": [
        "mydpd.cflxv.help"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "6a4c9d11f99778692a3b1152c3e773d3bb",
    "sha256": "87d858eaa23a98acebffc008eef94f7aedce632bf2de2da25e713d90c00c9b05",
    "subject": "mydpd.cflxv.help",
    "valid_to": "2027-01-25T06:26:37Z",
    "valid_from": "2026-10-27T06:26:38Z"
}
Registration record
{
    "registrar": "NameSilo, LLC",
    "registrar_iana_id": "1479",
    "registrar_url": "https://www.namesilo.com",
    "created": "2026-10-26T09:28:40Z",
    "updated": "2026-10-26T09:28:43Z",
    "expires": "2027-10-26T23:59:59Z",
    "status": [
        "addPeriod",
        "clientTransferProhibited",
        "serverTransferProhibited"
    ],
    "nameservers": [
        "ns1.dnsowl.com",
        "ns2.dnsowl.com",
        "ns3.dnsowl.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 7 malicious + 1 suspicious / 92 · 2026-10-27 16:27:30 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-27T16:27:30Z
fetched_at
2026-10-27T17:56:48Z
stats
{"timeout":0,"harmless":46,"malicious":7,"suspicious":1,"undetected":38}

Google Safe Browsing

Threat flag recorded

Open report

Spamhaus DBL

phishing domain

URLScan

Malicious

SHA-256 81e73f3a94f827ded0dd85a7fa1c0b8080a67a51b6314021a80b2923f2bb8b51

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a17d72-db7c-7705-8d27-44e1bfaae9c1

Final URL

https://mydpd.cflxv.help/track-ch/

HTTP response

200

Redirect type

same-domain

IP address

209.141.47.167

Contacted IP addresses

  • 209.141.47.167

Autonomous systems (ASN)

  • 53667

Server countries

  • US

Document hash

48402ffd5ccd5e3aa1f289c9200028ad3bc38602744eeefa8d37022d27571bac

Script hashes

  • e9473ffd649e62a74805adc6cc89c6b29ce7f925748af7f5a1e8135e1e17e8ee
  • 08ddd24c236084d324a27b8287a3833a62facd69d50e01476d43ca410c24eb7d
  • d0b8826fb0964ef7b075835c14fe14a06f991eb3f606cd26d4452b1e3e1c2dd7

JavaScript globals

  • __VUE_INSTANCE_SETTERS__
  • __VUE_SSR_SETTERS__
  • HeadlessDetectorModules
  • HeadlessDetectorUtils
  • detectHeadless
  • getWorkerChecks
  • HeadlessDetector
  • __headlessDetectionReady
  • __VUE__

Cookies

  • _vt

Browser storage keys

  • 2e14a1ac17c37597f4579a51c5f26330

TLS session and certificate

Subject alternative names
  • mydpd.cflxv.help
Cipher
AES_256_GCM
Issuer
YR2
Subject
mydpd.cflxv.help
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

0

Registered domain age, days

0

Certificate age, days

0

Certificate validity, days

89

Page requests

24

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
97
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • dpd
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • DPD
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
openresty
Content-type
text/html;charset=utf-8
Strict-transport-security
max-age=31536000; includeSubDomains
X-content-type-options
nosniff
Original source fields · JSON
Uuid
01a17d72-db7c-7705-8d27-44e1bfaae9c1
Final url
https://mydpd.cflxv.help/track-ch/
Status
200
Redirected
same-domain
Ip
209.141.47.167
Contacted IP addresses
[
    "209.141.47.167"
]
Asns
[
    "53667"
]
Countries
[
    "US"
]
Document hash
48402ffd5ccd5e3aa1f289c9200028ad3bc38602744eeefa8d37022d27571bac
Script hashes
[
    "e9473ffd649e62a74805adc6cc89c6b29ce7f925748af7f5a1e8135e1e17e8ee",
    "08ddd24c236084d324a27b8287a3833a62facd69d50e01476d43ca410c24eb7d",
    "d0b8826fb0964ef7b075835c14fe14a06f991eb3f606cd26d4452b1e3e1c2dd7"
]
Globals
[
    "__VUE_INSTANCE_SETTERS__",
    "__VUE_SSR_SETTERS__",
    "HeadlessDetectorModules",
    "HeadlessDetectorUtils",
    "detectHeadless",
    "getWorkerChecks",
    "HeadlessDetector",
    "__headlessDetectionReady",
    "__VUE__"
]
Cookies
[
    "_vt"
]
Storage keys
[
    "2e14a1ac17c37597f4579a51c5f26330"
]
Tls
{
    "san": [
        "mydpd.cflxv.help"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR2",
    "subject": "mydpd.cflxv.help",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-25T06:26:37Z",
    "valid_from": "2026-10-27T06:26:38Z"
}
Domain age days
0
Apex age days
0
Tls age days
0
Tls valid days
89
Requests
24
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 97,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "dpd"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "DPD"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "openresty",
    "content-type": "text/html;charset=utf-8",
    "strict-transport-security": "max-age=31536000; includeSubDomains",
    "x-content-type-options": "nosniff"
}
Separate monitor record · 2026-10-28 04:31 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a17d72-db7c-7705-8d27-44e1bfaae9c1
score
100
malicious
true
result_at
2026-10-28T04:31:03Z
enriched_at
2026-10-28T09:17:22Z
source_timestamps
{"urlscan_result_at":"2026-10-28 05:31:03","urlscan_enriched_at":"2026-10-28 10:17:22"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

c034c297-d05a-4de1-8e94-3afc819b9dbb

Final URL

https://mydpd.cflxv.help/

HTTP response

404

Navigation history

  • URL
    https://mydpd.cflxv.help/
    Status
    404

DOM structure hash

4dbc72dffccc8f8b936ed5c6039471f9fdd0adc6168a644b2f27e26a223c4772

Document hash

e65e10a52cf5d599468b8b135038df39182bd78d807fb3ad20d551a56e8b2421

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    mydpd.cflxv.help
    Type
    A
    Value
    209.141.47.167

DNSSEC valid

No

IP address

127.0.1.16

127.0.1.16 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record

Registrar
NameSilo, LLC
Registered
Updated
Expires
Nameservers
  • ns1.dnsowl.com
  • ns2.dnsowl.com
  • ns3.dnsowl.com
Original source fields · JSON
Uuid
c034c297-d05a-4de1-8e94-3afc819b9dbb
Final url
https://mydpd.cflxv.help/
Status
404
History
[
    {
        "url": "https://mydpd.cflxv.help/",
        "status": 404
    }
]
DOM structure hash
4dbc72dffccc8f8b936ed5c6039471f9fdd0adc6168a644b2f27e26a223c4772
Document hash
e65e10a52cf5d599468b8b135038df39182bd78d807fb3ad20d551a56e8b2421
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "mydpd.cflxv.help",
        "type": "A",
        "value": "209.141.47.167"
    }
]
Dnssec valid
false
Ip
127.0.1.16

127.0.1.16 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record
{
    "registrar": "NameSilo, LLC",
    "created": "2026-10-26T09:28:40Z",
    "updated": "2026-10-26T09:28:43Z",
    "expires": "2027-10-26T23:59:59Z",
    "nameservers": [
        "ns1.dnsowl.com",
        "ns2.dnsowl.com",
        "ns3.dnsowl.com"
    ]
}

PhishDestroy DOM

0 / 100 · heuristic score · 0 brand references · 1 classification

Open report
Separate monitor score · 0 / 100 · 2026-10-27T18:02:21Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
0
analyzed_at
2026-10-27T18:02:21Z
source_timestamp
2026-10-27 19:02:21
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 16 fields

CAA records

Domain
mydpd.cflxv.help

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

TLS connection

ALPN
http/1.1
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 22
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    162.159.27.173
    Host
    ns1.dnsowl.com
  • IP address
    162.159.26.49
    Host
    ns2.dnsowl.com
  • IP address
    162.159.27.98
    Host
    ns3.dnsowl.com
DNS zone
cflxv.help

Location

IP address
209.141.47.167
ASN
53667
Organization
FranTech Solutions
City
Las Vegas
Country
US

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
mydpd.cflxv.help

DNS records

A
  • 209.141.47.167

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31536000; includeSubDomains
Observation
HSTS header does not contain the preload directive.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
max-age=31536000; includeSubDomains
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
209.141.47.167
IP version
4

Subdomains

Count
1
Subdomains
  • mydpd.cflxv.help

Technology stack

Technologies
  • Nginx
  • OpenResty
  • lit-html
  • lit-element
  • HSTS

Registration record

Registrar
NameSilo, LLC
Registered
Updated
Expires
Status
  • serverTransferProhibited https://icann.org/epp
  • clientTransferProhibited https://icann.org/epp
  • addPeriod https://icann.org/epp
Nameservers
  • ns1.dnsowl.com
  • ns2.dnsowl.com
  • ns3.dnsowl.com

HTTP headers

Response headers
Server
openresty
Strict-transport-security
max-age=31536000; includeSubDomains
Original source fields · JSON
Caa records
{
    "domain": "mydpd.cflxv.help"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.27.173",
            "host": "ns1.dnsowl.com"
        },
        {
            "ip": "162.159.26.49",
            "host": "ns2.dnsowl.com"
        },
        {
            "ip": "162.159.27.98",
            "host": "ns3.dnsowl.com"
        }
    ],
    "zone": "cflxv.help"
}
Location
{
    "ip": "209.141.47.167",
    "asn": "53667",
    "org": "FranTech Solutions",
    "city": "Las Vegas",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "mydpd.cflxv.help"
}
DNS records
{
    "A": [
        "209.141.47.167"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31536000; includeSubDomains",
    "message": "HSTS header does not contain the preload directive."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=31536000; includeSubDomains",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "209.141.47.167",
    "family": 4
}
Subdomains
{
    "count": 1,
    "subdomains": [
        "mydpd.cflxv.help"
    ]
}
Tech stack
{
    "technologies": [
        "Nginx",
        "OpenResty",
        "lit-html",
        "lit-element",
        "HSTS"
    ]
}
Registration record
{
    "registrar": "NameSilo, LLC",
    "created": "2026-10-26T09:28:40Z",
    "updated": "2026-10-26T09:28:43Z",
    "expires": "2027-10-26T23:59:59Z",
    "status": [
        "serverTransferProhibited https://icann.org/epp",
        "clientTransferProhibited https://icann.org/epp",
        "addPeriod https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.dnsowl.com",
        "ns2.dnsowl.com",
        "ns3.dnsowl.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "openresty",
        "strict-transport-security": "max-age=31536000; includeSubDomains"
    }
}
Network Security Intelligence Registrar context
Registrar context NameSilo
Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
Review source investigation
Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 3 captures

Primary capture 1 / 3
SourcePrimary capture
Recorded
StateStored capture
HTTP status200
Final URLhttps://mydpd.cflxv.help/track-ch/
Position1 / 3
Open capture Wayback Download
All capture links and hashes (3)
Observed page title
mydpd.cflxv.help
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 84 days
mydpd.cflxv.help: Phishing site — Flagged by Google Safe Browsing, Spamhaus DBL, 8/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card mydpd.cflxv.help: Phishing site — Flagged by Google Safe Browsing, Spamhaus DBL, 8/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v d02f44fa64ce

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Dpd report ↗
Google Safe Browsing Flagged Social engineering checked Oct 27, 2026
IP Reputation United States209.141.47.167 abuse score 0/100 0 reports checked Oct 27, 2026
Registrar (base domain) NameSilo US(US) PhishDestroy Investigation
Abuse contact["abuse@namesilo.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for cflxv.help →
Registration (base domain)cflxv.help · Expires Oct 26, 2027
WHOIS statusserverTransferProhibitedclientTransferProhibitedaddPeriod
Technical detailsProvenance & timestamps
First DetectedOct 27, 2026
DOM Analysisanalyzed Oct 27, 2026score 0/100
Submitted URLhttp://mydpd.cflxv.help/track-ch
ICANN OVERSIGHT Registration: cflxv.help

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain cflxv.help behind this subdomain, 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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States209.141.47.167
Network ASN
AS53667
AS name
PONYNET - FranTech Solutions, US
Organization
FranTech Solutions
Observed location
United StatesLas Vegas, US
Server header
openresty

Nameservers 3

  • ns1.dnsowl.com
  • ns2.dnsowl.com
  • ns3.dnsowl.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-10-27 06:26:38
Valid until
2027-01-25 06:26:37
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint87d858eaa23a98acebffc008eef94f7aedce632bf2de2da25e713d90c00c9b05
Certificate names · 1 SAN
  • mydpd.cflxv.help

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 209.141.47.167rapiddns.io

Latest Classified Outcome 2026-10-31 10:20:09 UTC

The domain no longer resolves in DNS.

Technical details
Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Probe Inconclusive 20% 2026-11-01 02:53:40 UTC
RDAP registration
Observed timeline current episode first observed: 2026-10-28 16:03:14 UTC first terminal observation: 2026-10-28 16:03:14 UTC
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.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

8 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 8 detections
CRDF
ESET
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
SOCRadar
Sophos
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://mydpd.cflxv.help/track-ch
Final URL: https://mydpd.cflxv.help/track-ch/
Response
HTTP 200
HTML body
2.4 KB
Compressed
947 B
Links
0 internal · 0 external
Selected response headers
Server: openresty
Content-Type: text/html;charset=utf-8
Content-Encoding: gzip
Security headers present
Strict-Transport-SecurityX-Content-Type-Options
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 9
Connection
keep-alive
Content-Encoding
gzip
Content-Length
947
Content-Type
text/html;charset=utf-8
Date
Tue, 27 Oct 2026 16:36:42 GMT
Expires
Thu, 01 Jan 1970 00:00:00 GMT
Server
openresty
Strict-Transport-Security
max-age=31536000; includeSubDomains
X-Content-Type-Options
nosniff

Values retained by the collector; long values may be shortened during collection.

Archived
Registration & observation details3

Availability observations

Outcome first observed
Observation window ends
Estimate basis
first_observation_only

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Captured network requests

Network requests: 24 SHA-256 hashes: 20 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 01:54 UTC.

Open this scan on URLScan 01a17d72-db7c-7705-8d27-44e1bfaae9c1 ↗

Stored observation history4

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  4. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

All retained availability observations20

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:53:40.000000
    Evidence SHA-256
    5552197ccf24f241281f8981972de723389a3ea8f5ad7e4b766ba2b0412df7b5
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 03:53:40
    Evidence reason
    unavailable
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:08:39.000000
    Evidence SHA-256
    a1f75bcb7323c486a0f7f32f50a6e30d820820fc367a26601f610bf0ef0ecb09
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 00:08:39
    Evidence reason
    unavailable
  3. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:09:24.000000
    Evidence SHA-256
    5087507d2fc588d2dd4e98da5a0b23811982a89b4c521d95749a39d9b86b92a2
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 12:09:24
    Evidence reason
    unavailable
  4. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 11:20:09.112163
    Evidence SHA-256
    2e34d2905787d1cb41d14eee10dd71d398cf25f60d14075bf54efbe7992ba1bf
    Evidence timestamp as recorded
    2026-10-31 11:20:09.112163
  5. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 11:20:09.112163
    Evidence SHA-256
    2e34d2905787d1cb41d14eee10dd71d398cf25f60d14075bf54efbe7992ba1bf
    Evidence timestamp as recorded
    2026-10-31 11:20:09.112163
  6. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:30:31.000000
    Evidence SHA-256
    fe7bdb4ba2e121a5aa9b5b7f28180ed55142f46d62a323df80ff0a1cb9a90c9c
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 03:30:31
    Evidence reason
    unavailable
  7. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:06:50.000000
    Evidence SHA-256
    488cdc13ed123cf055bcefda4a1c557a8b3acc607c08d6684ee5c04efe49a4b7
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 12:06:50
    Evidence reason
    unavailable
  8. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 05:03:05.462458
    Evidence SHA-256
    f9cff5b9f1950ff481e989dfeecab84b2bf6e847bdeb7bc146f3f704088b4943
    Evidence timestamp as recorded
    2026-10-30 05:03:05.462458
  9. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 05:03:05.462458
    Evidence SHA-256
    f9cff5b9f1950ff481e989dfeecab84b2bf6e847bdeb7bc146f3f704088b4943
    Evidence timestamp as recorded
    2026-10-30 05:03:05.462458
  10. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:07:09.000000
    Evidence SHA-256
    8032a3092e29ebc06748ce83fb44586b69bdde68a0c075d04d00bed1471638ac
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 00:07:09
    Evidence reason
    unavailable
  11. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:07:09.000000
    Evidence SHA-256
    8032a3092e29ebc06748ce83fb44586b69bdde68a0c075d04d00bed1471638ac
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 00:07:09
    Evidence reason
    unavailable
  12. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:07:29.000000
    Evidence SHA-256
    01c4a9ccc201c7d6e03c803cbf016530449a5453ee55372d68ab159df2e4c568
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 12:07:29
    Evidence reason
    unavailable
  13. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:35:38.000000
    Evidence SHA-256
    da497d32a9a509bd8306db90144999c0f08dcd622e93a908202289c330c24890
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 03:35:38
    Evidence reason
    unavailable
  14. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 17:03:14.895165
    Evidence SHA-256
    4876cf7962c9ae9ac450025b216435b36ed8cd01536ced32a6d3b99a8d56ba6d
    Evidence timestamp as recorded
    2026-10-28 17:03:14.895165
  15. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 17:03:14.895165
    Evidence SHA-256
    4876cf7962c9ae9ac450025b216435b36ed8cd01536ced32a6d3b99a8d56ba6d
    Evidence timestamp as recorded
    2026-10-28 17:03:14.895165
  16. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:00:23.000000
    Evidence SHA-256
    78c7bbe908270cf8ef262c54e93548988e4f2de6bbb0d9ff7099e2ab18edd57d
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-28 12:00:23
    Evidence reason
    unavailable
  17. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:00:23.000000
    Evidence SHA-256
    78c7bbe908270cf8ef262c54e93548988e4f2de6bbb0d9ff7099e2ab18edd57d
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-28 12:00:23
    Evidence reason
    unavailable
  18. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:00:23.000000
    Evidence SHA-256
    4727986ae5075c4b7f9d60827e53e51f8dd6b66f57ee7dbde99bd43938e61494
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-28 00:00:23
    Evidence reason
    unavailable
  19. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:00:23.000000
    Evidence SHA-256
    4727986ae5075c4b7f9d60827e53e51f8dd6b66f57ee7dbde99bd43938e61494
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-28 00:00:23
    Evidence reason
    unavailable
  20. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 17:56:33.188942
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · recorded

Recorded events: 12. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    mydpd.cflxv.help detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Google Safe Browsing · Registrar Context: NameSilo · Automated brand label: Dpd · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 10 of 10
  • Spamhaus DBL
    Spamhaus DBL recorded: phishing domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • VirusTotal
    Detections recorded on VirusTotal: 8/92
  • Google Safe Browsing
    Listed as unsafe by Google Safe Browsing (Google Transparency Report)
  • Registrar Context: NameSilo
    Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
  • Automated brand label: Dpd
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

4 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. Added to PhishDestroy

    mydpd.cflxv.help

    View source
  3. VirusTotal

    8/92 engine detections

    View source
  4. URLScan

    Malicious

    View source
How we investigate & report

Public scans, evidence and abuse channels

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.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

mydpd.cflxv.help

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 8 det. ChainPatrol URLQuery Google SB Flagged SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Unverified
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

What information should I collect for my report?

FBI guidelines

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.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including mydpd.cflxv.help)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?
  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
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.

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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/mydpd.cflxv.help"
  title="PhishDestroy threat report for mydpd.cflxv.help"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>