Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 5. 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.yjbow.top favicon

mydpd.yjbow.top

In short

mydpd.yjbow.top is a Dpd impersonation page detected by PhishDestroy on 2026-10-25.

“mydpd.yjbow.top”

Review the evidence
Registrar
NameSilo
Resolved IP
209.141.47.167
PhishDestroy assessment Critical
100/100
Evidence score
First observed Oct 25, 2026 16:19 UTC · PhishDestroy
Risk signals
VirusTotal detections: 5/92 Spamhaus DBL: phishing domain Automated brand label: Dpd Scam type: Impersonation Google Safe Browsing: threat flag recorded
VirusTotal
5 / 92
engine detections ·
OTX
0
community references
Cloudflare Radar
clean
source verdict
Page captures
4
open gallery
Oct 25, 2026
X Telegram API

Analysis

Domain summary

mydpd.yjbow.top is a Dpd impersonation page detected by PhishDestroy on 2026-10-25. Risk: critical (100/100). Registrar: NameSilo. Hosting: FranTech Solutions. VirusTotal: 5/92 engines flag it. Google Safe Browsing flags it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
5 / 92
Page captures
4
Page captures Source results Registration record

PhishDestroy threat report

Overview

The captured screenshot shows an HTTP ERROR 404 page stating that this mydpd.yjbow.top page can't be found and offering a Reload button, observed on 2026-10-25. PhishDestroy listed the domain on 2026-10-25 because Google Safe Browsing flagged SOCIAL_ENGINEERING; a separate urlscan capture that day retrieved a DPD-themed parcel-tracking page, and 2026-10-25 is the first-seen date.

How the scam works

The page supports a category risk in which people contacted about a DPD delivery are steered to a lookalike tracking experience on mydpd.yjbow.top and asked to enter personal, address or payment details, or to pay a delivery fee, under the cover of a parcel-tracking lure.

Evidence

The captured screenshot itself shows only the 404 error page and Reload button, while the urlscan capture on 2026-10-25 reached a DPD-labelled tracking path and scored it malicious at 100 with an ML score of 95. VirusTotal flagged the domain as malicious, Google Safe Browsing flagged SOCIAL_ENGINEERING, and the PhishDestroy assessment classified it as impersonation phishing. Spamhaus listed the domain in the phishing category on 2026-10-25, Cloudflare Radar recorded HTTP 404 on 2026-10-25 matching the screenshot, and the page fetch followed no cross-site redirect. PhishDestroy internal blocklist listed the domain on 2026-10-26 while external blocklists and DNS blocklists showed 0 listings across 12 resolvers and OTX recorded 0 pulses; site inspection of the captured page shows a Vue-based front end with headless-browser detection globals, 23 network requests, and 3 distinct script SHA256 hashes for campaign pivoting, the first beginning e9473ffd649e.

Infrastructure

Notable weaknesses: no Content-Security-Policy, no X-Frame-Options, no X-Content-Type-Options, no Referrer-Policy, no Permissions-Policy, no COOP/COEP/CORP, and DNSSEC unsigned. TLS 1.3 with AES-256-GCM, forward secrecy and ALPN http/1.1; HSTS present without preload; no email authentication records observed; no CAA record observed. The recorded hosting was PONYNET, FranTech Solutions, United States, on an openresty server, first observed 2026-10-25.

What to do

If you entered credentials, change your password on the genuine DPD account service and enable two-factor authentication; if you shared card details, contact your bank. For defenders, block mydpd.yjbow.top, retain the three recorded script hashes for pivoting, and alert on messages linking to this domain.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-25T16:27:24Z)URLScan screenshot (2026-10-25T11:45:57Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 5 / 92 · Google Safe Browsing: flagged 8 sources

VirusTotal

5 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
50
Malicious
3
Suspicious
2
Undetected
37

Vendor labels

G-Data
phishing
Fortinet
spam
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.yjbow.top
Issuer
Let's Encrypt / YR1
Serial
5c5d2fb7840c76636c9d81a80b2845bb47
SHA-256
57b5008172e224ae357cd36491f124877ff2631ea29c00bd515c30a4e69b47d5
Subject
mydpd.yjbow.top
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
Nameservers
  • ns1.dnsowl.com
  • ns2.dnsowl.com
  • ns3.dnsowl.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 50,
    "malicious": 3,
    "suspicious": 2,
    "undetected": 37
}
Vendor labels
{
    "G-Data": "phishing",
    "Fortinet": "spam",
    "SOCRadar": "suspicious",
    "Gridinsoft": "phishing",
    "Google Safe Browsing": "phishing"
}
Reputation
0
Registrar
NameSilo,LLC
Created
2026-10-24T02:47:41Z
Expires
2027-10-24T02:47:41Z
Updated
2026-10-24T02:47:45Z
First seen
2026-10-25T07:51:57Z
DNS records
[
    {
        "ttl": 7207,
        "type": "A",
        "value": "209.141.47.167"
    }
]
Dns at
2026-10-25T16:20:59Z
Jarm
29d29d00029d29d00042d42d00000090d94d1f02cef4051cfd1d66dbe44eb0
Certificate
{
    "san": [
        "mydpd.yjbow.top"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "5c5d2fb7840c76636c9d81a80b2845bb47",
    "sha256": "57b5008172e224ae357cd36491f124877ff2631ea29c00bd515c30a4e69b47d5",
    "subject": "mydpd.yjbow.top",
    "valid_to": "2027-01-23T06:04:17Z",
    "valid_from": "2026-10-25T06:04:18Z"
}
Registration record
{
    "registrar": "NameSilo,LLC",
    "registrar_iana_id": "1479",
    "registrar_url": "https://www.namesilo.com",
    "created": "2026-10-24T02:47:41Z",
    "updated": "2026-10-24T02:47:45Z",
    "expires": "2027-10-24T02:47:41Z",
    "status": [
        "addPeriod",
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ns1.dnsowl.com",
        "ns2.dnsowl.com",
        "ns3.dnsowl.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 3 malicious + 2 suspicious / 92 · 2026-10-25 16:15:37 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-25T16:15:37Z
fetched_at
2026-10-25T17:02:15Z
stats
{"timeout":0,"harmless":50,"malicious":3,"suspicious":2,"undetected":37}

Google Safe Browsing

Threat flag recorded

Open report

Spamhaus DBL

phishing domain

URLScan

Malicious

SHA-256 46ed48655211df734ab4cb992dbf024cd9e7a8c4af028c63d94d2773e5809e1e

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a17325-d1ca-7619-a219-af210557a900

Final URL

https://mydpd.yjbow.top/track-ch/

HTTP response

200

IP address

209.141.47.167

Contacted IP addresses

  • 209.141.47.167

Autonomous systems (ASN)

  • 53667

Server countries

  • US

Document hash

fc44e3259a86f10a0a33cd2c5aadf85fe0d22606f1cf7e113f194c3edf630139

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.yjbow.top
Cipher
AES_256_GCM
Issuer
YR1
Subject
mydpd.yjbow.top
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

23

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
95
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
Original source fields · JSON
Uuid
01a17325-d1ca-7619-a219-af210557a900
Final url
https://mydpd.yjbow.top/track-ch/
Status
200
Ip
209.141.47.167
Contacted IP addresses
[
    "209.141.47.167"
]
Asns
[
    "53667"
]
Countries
[
    "US"
]
Document hash
fc44e3259a86f10a0a33cd2c5aadf85fe0d22606f1cf7e113f194c3edf630139
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.yjbow.top"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR1",
    "subject": "mydpd.yjbow.top",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-23T06:04:17Z",
    "valid_from": "2026-10-25T06:04:18Z"
}
Domain age days
0
Apex age days
0
Tls age days
0
Tls valid days
89
Requests
23
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 95,
        "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"
}
Separate monitor record · 2026-10-26 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a17325-d1ca-7619-a219-af210557a900
score
100
malicious
true
result_at
2026-10-26T04:30:23Z
enriched_at
2026-10-26T09:15:11Z
source_timestamps
{"urlscan_result_at":"2026-10-26 05:30:23","urlscan_enriched_at":"2026-10-26 10:15:11"}
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

221a5d7f-dc45-4775-814a-324f398e3c93

Final URL

https://mydpd.yjbow.top/

HTTP response

404

Navigation history

  • URL
    https://mydpd.yjbow.top/
    Status
    404

DOM structure hash

4dbc72dffccc8f8b936ed5c6039471f9fdd0adc6168a644b2f27e26a223c4772

Document hash

d294cb85db825076bd78e4e91425293de30bc08fed7533d1a2dbc85a29c2e15c

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    mydpd.yjbow.top
    Type
    A
    Value
    209.141.47.167

DNSSEC valid

No

IP address

209.141.47.167

Registration record

Registrar
NameSilo,LLC
Registered
Updated
Expires
Nameservers
  • ns1.dnsowl.com.
  • ns2.dnsowl.com.
  • ns3.dnsowl.com.
Original source fields · JSON
Uuid
221a5d7f-dc45-4775-814a-324f398e3c93
Final url
https://mydpd.yjbow.top/
Status
404
History
[
    {
        "url": "https://mydpd.yjbow.top/",
        "status": 404
    }
]
DOM structure hash
4dbc72dffccc8f8b936ed5c6039471f9fdd0adc6168a644b2f27e26a223c4772
Document hash
d294cb85db825076bd78e4e91425293de30bc08fed7533d1a2dbc85a29c2e15c
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "mydpd.yjbow.top",
        "type": "A",
        "value": "209.141.47.167"
    }
]
Dnssec valid
false
Ip
209.141.47.167
Registration record
{
    "registrar": "NameSilo,LLC",
    "created": "2026-10-24T02:47:41Z",
    "updated": "2026-10-24T02:47:45Z",
    "expires": "2027-10-24T02:47:41Z",
    "nameservers": [
        "ns1.dnsowl.com.",
        "ns2.dnsowl.com.",
        "ns3.dnsowl.com."
    ]
}

PhishDestroy DOM

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

Open report
Separate monitor score · 0 / 100 · 2026-10-25T17:10:04Z

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-25T17:10:04Z
source_timestamp
2026-10-25 18:10:04
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
mydpd.yjbow.top — DPD impersonation phishing page
ai_description
PhishDestroy assesses mydpd.yjbow.top as an impersonation phishing page that appears to target the DPD brand and its delivery customers.
ai_generated_at
2026-10-26T21:02:08Z
ai_generated_by
mimo-flash
interpretation
Narrative generation metadata, separate from provider observation dates.

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: 14 fields

CAA records

Domain
mydpd.yjbow.top

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.26.234
    Host
    ns3.dnsowl.com
  • IP address
    162.159.26.136
    Host
    ns1.dnsowl.com
  • IP address
    162.159.26.49
    Host
    ns2.dnsowl.com
DNS zone
yjbow.top

Location

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

TLS certificate

Issuer
Let's Encrypt / YR1
Subject
mydpd.yjbow.top

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

Registration record

Registrar
NameSilo,LLC
Registered
Updated
Expires
Status
  • 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
Content-type
text/plain;charset=utf-8
Strict-transport-security
max-age=31536000; includeSubDomains
Original source fields · JSON
Caa records
{
    "domain": "mydpd.yjbow.top"
}
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.26.234",
            "host": "ns3.dnsowl.com"
        },
        {
            "ip": "162.159.26.136",
            "host": "ns1.dnsowl.com"
        },
        {
            "ip": "162.159.26.49",
            "host": "ns2.dnsowl.com"
        }
    ],
    "zone": "yjbow.top"
}
Location
{
    "ip": "209.141.47.167",
    "asn": "53667",
    "org": "FranTech Solutions",
    "city": "Las Vegas",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YR1",
    "subject": "mydpd.yjbow.top"
}
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
}
Registration record
{
    "registrar": "NameSilo,LLC",
    "created": "2026-10-24T02:47:41Z",
    "updated": "2026-10-24T02:47:45Z",
    "expires": "2027-10-24T02:47:41Z",
    "status": [
        "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",
        "content-type": "text/plain;charset=utf-8",
        "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

Questions about mydpd.yjbow.top

Is mydpd.yjbow.top legit?

No. PhishDestroy classifies mydpd.yjbow.top as a Dpd impersonation page (risk: critical, 100/100); it was first detected on 2026-10-25. VirusTotal: 5/92 engines flag it. Google Safe Browsing flags it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is mydpd.yjbow.top safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on mydpd.yjbow.top. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used mydpd.yjbow.top?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 4 captures

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

Domain details

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

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain yjbow.top 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
209.141.47.167
Network ASN
AS53667
AS name
PONYNET - FranTech Solutions, US
Organization
FranTech Solutions
Observed location
Las 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 / YR1
Valid from
2026-10-25 06:04:18
Valid until
2027-01-23 06:04:17
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint57b5008172e224ae357cd36491f124877ff2631ea29c00bd515c30a4e69b47d5
Certificate names · 1 SAN
  • mydpd.yjbow.top

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-25 23:00:30 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-25 23:00:30 UTC
RDAP registration
Observed timeline last reachable: 2026-10-25 23:00:30 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

5 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 5 detections
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
SOCRadar
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.yjbow.top/track-ch
Final URL: https://mydpd.yjbow.top/track-ch/
Response
HTTP 200
HTML body
2.3 KB
Compressed
891 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-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 8
Connection
keep-alive
Content-Encoding
gzip
Content-Length
891
Content-Type
text/html;charset=utf-8
Date
Sun, 25 Oct 2026 16:19:47 GMT
Expires
Thu, 01 Jan 1970 00:00:00 GMT
Server
openresty
Strict-Transport-Security
max-age=31536000; includeSubDomains

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

Archived
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

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

Stored observation history2

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

    redirected

    http_redirect

  2. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

All retained availability observations3

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. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    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-26 00:00:30.000000
    Evidence SHA-256
    6eeecd7522c4c486a985f522c55c6d24410335acd8a25e4bc6f90fe2579ff461
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-26 00:00:30
    Evidence reason
    redirect
  2. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    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-26 00:00:30.000000
    Evidence SHA-256
    6eeecd7522c4c486a985f522c55c6d24410335acd8a25e4bc6f90fe2579ff461
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-26 00:00:30
    Evidence reason
    redirect
  3. 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-25 17:29:19.030122
    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.yjbow.top 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 · Brand Impersonation · 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: 5/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.
  • Brand Impersonation
    Automated brand label: Dpd
  • 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. VirusTotal

    5/92 engine detections

    View source
  3. Added to PhishDestroy

    mydpd.yjbow.top

    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.yjbow.top

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 5 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.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

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 →.

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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.yjbow.top)
  • 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.

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.

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.yjbow.top"
  title="PhishDestroy threat report for mydpd.yjbow.top"
  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>