Skip to security report
Analytics Dashboard
Domain security and threat intelligence
mydpd.jdevr.xyz favicon

mydpd.jdevr.xyz

In short

mydpd.jdevr.xyz is a phishing page detected by PhishDestroy on 2026-10-22. Risk: critical (80/100). Registrar: NameSilo. Hosting: FranTech Solutions. Google Safe Browsing flags it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

“mydpd.jdevr.xyz”

Registrar
NameSilo
Resolved IP
209.141.47.167
Registered
Oct 22, 2026
PhishDestroy assessment Critical
First observed Oct 22, 2026 13:09 UTC · PhishDestroy
Risk signals
Spamhaus DBL: DBL_PHISH Stored blocklist matches: 1 Young domain: less than one day old Google Safe Browsing: threat flag recorded
Oct 22, 2026
API
This domain has been flagged as malicious
Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
0 / 92
engine detections
Google Safe Browsing
Flagged
Page captures
5
open gallery
Domain age
0 days
Source evidenceVirusTotal 0 / 92 · Google Safe Browsing: flagged 6 sources

Google Safe Browsing

Threat flag recorded

Open report

Spamhaus DBL

DBL_PHISH

VirusTotal

0 / 92 engine detections

Open report

OTX

no community references

Open report

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

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

Analysis

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

PhishDestroy threat report

Overview

PhishDestroy listed mydpd.jdevr.xyz as a suspicious domain based on automated analysis. The page at /track-ch/ returned HTTP 200 on 2026-10-22 and was marked malicious by urlscan.io. A later Cloudflare Radar scan on the same day showed a 404 response, which does not prove the current status of the site.

How the scam works

The detections suggest the site is being used for social‑engineering, typically by impersonating a trusted brand to lure users into revealing personal information. No concrete credential‑capture form was observed, so the risk is limited to potential phishing attempts.

Evidence

Google Safe Browsing flagged the domain for social‑engineering on 2026-10-22. urlscan.io recorded a malicious phishing verdict with a score of 100 on 2026-10-22 and identified the brand DPD. VirusTotal scanned the domain on 2026-10-22 with 92 engines and reported zero malicious or suspicious detections. OTX listed zero pulses on 2026-10-22, external blocklists returned no matches, and PhishDestroy’s internal list marked the domain as blocked.

Infrastructure

The recorded IP was 209.141.47.167 and the network name was FranTech Solutions in the United States. TLS was provided by Let’s Encrypt, with a certificate valid until 2027-01-20 and observed on 2026-10-22. The server header reported openresty and ports 22, 80, and 443 were open. DNS records showed an A record to the same IP and the domain age was recorded as zero days on the scan date.

What to do

Do not enter any credentials, tracking numbers, or personal data on the site; if you have already submitted information, change related passwords and monitor accounts for unusual activity. Defenders should block the exact hostname mydpd.jdevr.xyz and log any connections to its IP address. Continue to monitor for updates, as site availability may change.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-22T13:20:47Z)URLScan screenshot (2026-10-22T11:46:43Z)URLScan capture reportURLScan screenshot (2026-10-22T13:17:18Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Collected source details

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

URLScan · 2026-10-22T13:01:00Z

Observed: · Retrieved:

Uuid
01a163b3-3857-70ab-bc80-49c0aa06ca1b
Final url
https://mydpd.jdevr.xyz/track-ch/
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://mydpd.jdevr.xyz/track-ch/",
        "from": "https://mydpd.jdevr.xyz/track-ch",
        "status": 302
    }
]
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.jdevr.xyz"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR2",
    "subject": "mydpd.jdevr.xyz",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-20T06:09:22Z",
    "valid_from": "2026-10-22T06:09:23Z"
}
Domain age days
0
Apex age days
0
Tls age days
0
Tls valid days
89
Requests
20
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"
}
Cloudflare Radar · 2026-10-22T13:20:47Z

Observed: · Retrieved:

Uuid
202cbb58-f0c2-4190-84ff-ee548de5f35c
Final url
https://mydpd.jdevr.xyz/
Status
404
History
[
    {
        "url": "https://mydpd.jdevr.xyz/",
        "status": 404
    }
]
DOM structure hash
e5a234cb9304b15f34134b61a77b3718c6b9a63fe1299cafe25dcb3f16464ae1
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "mydpd.jdevr.xyz",
        "type": "A",
        "value": "209.141.47.167"
    }
]
Dnssec valid
false
Ip
209.141.47.167
Registration record
{
    "registrar": "NameSilo, LLC",
    "created": "2026-10-22T05:48:57Z",
    "updated": "2026-10-22T05:50:11Z",
    "expires": "2027-10-22T23:59:59Z",
    "nameservers": [
        "ns1.dnsowl.com",
        "ns2.dnsowl.com",
        "ns3.dnsowl.com"
    ]
}
VirusTotal · 2026-10-22T12:33:21Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 37
}
Reputation
0
Registrar
NameSilo, LLC
Created
2026-10-22T05:48:57Z
Expires
2027-10-22T23:59:59Z
Updated
2026-10-22T05:50:11Z
First seen
2026-10-22T07:13:32Z
DNS records
[
    {
        "ttl": 7207,
        "type": "A",
        "value": "209.141.47.167"
    }
]
Dns at
2026-10-22T12:41:43Z
Jarm
29d29d00029d29d00042d42d00000090d94d1f02cef4051cfd1d66dbe44eb0
Certificate
{
    "san": [
        "mydpd.jdevr.xyz"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "68d2c72cfb32e08599bcf0546b2322cefd3",
    "sha256": "99a435dab4383e4c6976e13d1e1ab3b16d28686df33948f52e337dd6c2b98556",
    "subject": "mydpd.jdevr.xyz",
    "valid_to": "2027-01-20T06:09:22Z",
    "valid_from": "2026-10-22T06:09:23Z"
}
Registration record
{
    "registrar": "NameSilo, LLC",
    "registrar_iana_id": "1479",
    "registrar_url": "https://www.namesilo.com",
    "created": "2026-10-22T05:48:57Z",
    "updated": "2026-10-22T05:50:11Z",
    "expires": "2027-10-22T23:59:59Z",
    "status": [
        "addPeriod",
        "clientTransferProhibited",
        "serverTransferProhibited"
    ],
    "nameservers": [
        "ns1.dnsowl.com",
        "ns2.dnsowl.com",
        "ns3.dnsowl.com"
    ],
    "dnssec": "unsigned"
}
Website checks · 2026-10-22T13:24:28Z
Caa records
{
    "domain": "mydpd.jdevr.xyz"
}
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.27.130",
            "host": "ns2.dnsowl.com"
        }
    ],
    "zone": "jdevr.xyz"
}
Location
{
    "ip": "209.141.47.167",
    "asn": "53667",
    "org": "FranTech Solutions",
    "city": "Las Vegas",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "mydpd.jdevr.xyz"
}
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
}
Tech stack
{
    "technologies": [
        "Nginx",
        "OpenResty",
        "HSTS"
    ]
}
Registration record
{
    "registrar": "NameSilo, LLC",
    "created": "2026-10-22T05:48:57Z",
    "updated": "2026-10-22T05:50:11Z",
    "expires": "2027-10-22T23: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",
        "content-type": "text/plain;charset=utf-8",
        "strict-transport-security": "max-age=31536000; includeSubDomains"
    }
}

Questions about mydpd.jdevr.xyz

Is mydpd.jdevr.xyz legit?

No. PhishDestroy classifies mydpd.jdevr.xyz as a phishing page (risk: critical, 80/100); it was first detected on 2026-10-22. Google Safe Browsing flags it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is mydpd.jdevr.xyz safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on mydpd.jdevr.xyz. 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.jdevr.xyz?

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 matchesOpenPhish · PhishDestroy 2
OpenPhish Listed View source
PhishDestroy PhishDestroy list View source

Last checked

Stored Capture · 5 captures

Primary capture 1 / 5
SourcePrimary capture
Recorded2026-10-22 13:09 UTC
StateStored capture
HTTP status at archiveHTTP 200
Final URLhttps://mydpd.jdevr.xyz/track-ch/
Position1 / 5
Open capture Wayback Download
Observed page title
mydpd.jdevr.xyz
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 89 days

Domain details

Domain
Google Safe Browsing Flagged Social engineering checked Oct 22, 2026
IP Reputation abuse score 0/100 0 reports checked Oct 22, 2026
Registrar (base domain) NameSilo US(US) PhishDestroy Investigation
Abuse contact["abuse@namesilo.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for jdevr.xyz →
Registration (base domain)jdevr.xyz · Created Oct 22, 2026 (0d · Brand New!) — Expires Oct 22, 2027
Technical detailsProvenance & timestamps
First DetectedOct 22, 2026
DOM Analysisanalyzed Oct 22, 2026score 68/100
Submitted URLhttp://mydpd.jdevr.xyz/track-ch
ICANN OVERSIGHT Registration: jdevr.xyz

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain jdevr.xyz 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
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 / YR2
Valid from
2026-10-22 06:09:23
Valid until
2027-01-20 06:09:22
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint99a435dab4383e4c6976e13d1e1ab3b16d28686df33948f52e337dd6c2b98556
Certificate names · 1 SAN
  • mydpd.jdevr.xyz

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
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others
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.jdevr.xyz/track-ch
Final URL: https://mydpd.jdevr.xyz/track-ch/
Response
HTTP 200
HTML body
2.3 KB
Compressed
894 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
894
Content-Type
text/html;charset=utf-8
Date
Thu, 22 Oct 2026 13:14:23 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
Stored observation history1

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

  1. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

Recorded activity

3 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. VirusTotal

    0/92 engine detections

    View source
  3. Added to PhishDestroy

    mydpd.jdevr.xyz

    View source

Check for cloaking

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

mydpd.jdevr.xyz

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 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?

2 evidence signal groups linked 0 stored notification records Unverified

Listed domains receive at least one abuse report; this entry has no retained notification history.

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

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

Report to Your Local Authorities

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

97-country directory

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

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.jdevr.xyz)
  • 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

Live Threat Feed Appeal This Listing
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.jdevr.xyz"
  title="PhishDestroy threat report for mydpd.jdevr.xyz"
  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>