Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 7. Public blocklists reporting a match: 1. 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.ixrii.help favicon

mydpd.ixrii.help

In short

mydpd.ixrii.help is a phishing page detected by PhishDestroy on 2026-10-26.

“mydpd.ixrii.help”

Review the evidence
Registrar
NameSilo
Resolved IP
209.141.47.167
PhishDestroy assessment Critical
100/100
Evidence score
First observed Oct 26, 2026 16:15 UTC · PhishDestroy
Risk signals
VirusTotal detections: 7/92 Spamhaus DBL: phishing domain Stored blocklist matches: 1 Google Safe Browsing: threat flag recorded
VirusTotal
7 / 92
engine detections ·
OTX
0
community references
Cloudflare Radar
clean
source verdict
Page captures
3
open gallery
Oct 26, 2026
X Telegram API

Analysis

Domain summary

mydpd.ixrii.help is a phishing page detected by PhishDestroy on 2026-10-26. Risk: critical (100/100). Registrar: NameSilo. Hosting: FranTech Solutions. VirusTotal: 7/92 engines flag it. Google Safe Browsing flags it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
7 / 92
Page captures
3
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy added the domain to its blocklist on 2026-10-26 because Google Safe Browsing reported a social‑engineering threat. A page fetch on that date returned HTTP 200 and redirected to /track-ch/. A Cloudflare Radar scan of the root URL on the same day returned HTTP 404, indicating the site may no longer serve content at that path.

How the scam works

The alerts are consistent with typical social‑engineering sites that mimic legitimate brands to lure users into entering personal or tracking information. No specific malicious payload, credential‑harvesting form, or wallet interaction was observed in the captured page content.

Evidence

VirusTotal recorded seven detections on 2026-10-26, with four vendors (ESET, G‑Data, Sophos, Google Safe Browsing) labeling it malicious and three (Fortinet, SOCRadar, LevelBlue) marking it suspicious. Google Safe Browsing flagged the domain for social‑engineering on the same date. urlscan.io scanned the site on 2026-10-26 and returned a malicious verdict with a score of 100, categorising it as phishing and associating it with the DPD brand. OpenPhish listed the domain and PhishDestroy’s internal list also marks it as malicious, while OTX reported zero pulses.

Infrastructure

The recorded IP address 209.141.47.167 belongs to FranTech Solutions in the United States (ASN 53667). The domain uses a Let’s Encrypt certificate issued on 2026-10-26, valid until 2027-01-24, and the TLS record shows a 89‑day validity period. Domain age, apex age and TLS age are all zero days, indicating the domain and its certificate were created on the day of first observation. Nameservers are ns1.dnsowl.com, ns2.dnsowl.com and ns3.dnsowl.com.

What to do

Do not submit any credentials, tracking numbers or personal data to the site; if you have already done so, change related passwords and monitor accounts for unauthorized activity. Security teams should block the exact domain, review proxy and firewall logs for connections to 209.141.47.167, and enforce strict TLS verification for outbound traffic. Continue monitoring reputable threat feeds for any future activity linked to this domain.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-26T16:19:30Z)VirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 7 / 92 · Google Safe Browsing: flagged 8 sources

VirusTotal

7 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
47
Malicious
4
Suspicious
3
Undetected
38

Vendor labels

ESET
phishing
G-Data
phishing
Sophos
phishing
Fortinet
spam
SOCRadar
suspicious
LevelBlue
suspicious
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.ixrii.help
Issuer
Let's Encrypt / YR1
Serial
5da283727495642d6c149bfc315e9e529e9
SHA-256
11ac0a51a04797c838313ed429dfeca3476e648bfca869082fc85d0e1998884b
Subject
mydpd.ixrii.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": 47,
    "malicious": 4,
    "suspicious": 3,
    "undetected": 38
}
Vendor labels
{
    "ESET": "phishing",
    "G-Data": "phishing",
    "Sophos": "phishing",
    "Fortinet": "spam",
    "SOCRadar": "suspicious",
    "LevelBlue": "suspicious",
    "Google Safe Browsing": "phishing"
}
Reputation
0
Registrar
NameSilo, LLC
Created
2026-10-26T07:28:27Z
Expires
2027-10-26T23:59:59Z
Updated
2026-10-26T07:28:31Z
First seen
2026-10-26T08:03:46Z
DNS records
[
    {
        "ttl": 7207,
        "type": "A",
        "value": "209.141.47.167"
    }
]
Dns at
2026-10-26T16:22:05Z
Jarm
29d29d00029d29d00042d42d00000090d94d1f02cef4051cfd1d66dbe44eb0
Certificate
{
    "san": [
        "mydpd.ixrii.help"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "5da283727495642d6c149bfc315e9e529e9",
    "sha256": "11ac0a51a04797c838313ed429dfeca3476e648bfca869082fc85d0e1998884b",
    "subject": "mydpd.ixrii.help",
    "valid_to": "2027-01-24T07:00:06Z",
    "valid_from": "2026-10-26T07:00:07Z"
}
Registration record
{
    "registrar": "NameSilo, LLC",
    "registrar_iana_id": "1479",
    "registrar_url": "https://www.namesilo.com",
    "created": "2026-10-26T07:28:27Z",
    "updated": "2026-10-26T07:28:31Z",
    "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 · 4 malicious + 3 suspicious / 92 · 2026-10-26 16:16:27 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-26T16:16:27Z
fetched_at
2026-10-26T16:51:01Z
stats
{"timeout":0,"harmless":47,"malicious":4,"suspicious":3,"undetected":38}

Google Safe Browsing

Threat flag recorded

Open report

Spamhaus DBL

phishing domain

URLScan

Malicious

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a1784c-6aa9-7028-84d0-e48455753e1d

Final URL

https://mydpd.ixrii.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

e74b1e60634c5662ef8cd2ac7e5623f553bafc69942f0379b765f74b0df30f29

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.ixrii.help
Cipher
AES_256_GCM
Issuer
YR1
Subject
mydpd.ixrii.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

22

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
96
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
01a1784c-6aa9-7028-84d0-e48455753e1d
Final url
https://mydpd.ixrii.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
e74b1e60634c5662ef8cd2ac7e5623f553bafc69942f0379b765f74b0df30f29
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.ixrii.help"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR1",
    "subject": "mydpd.ixrii.help",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-24T07:00:06Z",
    "valid_from": "2026-10-26T07:00:07Z"
}
Domain age days
0
Apex age days
0
Tls age days
0
Tls valid days
89
Requests
22
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 96,
        "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 · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a1784c-6aa9-7028-84d0-e48455753e1d
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
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

a6033358-174d-4268-a900-ecef91d3e72a

Final URL

https://mydpd.ixrii.help/

HTTP response

404

Navigation history

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

DOM structure hash

4dbc72dffccc8f8b936ed5c6039471f9fdd0adc6168a644b2f27e26a223c4772

Document hash

12d1c30616ec9038f1aff285c027ec87220cfc2b6d6a638dcf8269d4d8d606b4

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    mydpd.ixrii.help
    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
a6033358-174d-4268-a900-ecef91d3e72a
Final url
https://mydpd.ixrii.help/
Status
404
History
[
    {
        "url": "https://mydpd.ixrii.help/",
        "status": 404
    }
]
DOM structure hash
4dbc72dffccc8f8b936ed5c6039471f9fdd0adc6168a644b2f27e26a223c4772
Document hash
12d1c30616ec9038f1aff285c027ec87220cfc2b6d6a638dcf8269d4d8d606b4
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "mydpd.ixrii.help",
        "type": "A",
        "value": "209.141.47.167"
    }
]
Dnssec valid
false
Ip
209.141.47.167
Registration record
{
    "registrar": "NameSilo, LLC",
    "created": "2026-10-26T07:28:27Z",
    "updated": "2026-10-26T07:28:31Z",
    "expires": "2027-10-26T23:59:59Z",
    "nameservers": [
        "ns1.dnsowl.com",
        "ns2.dnsowl.com",
        "ns3.dnsowl.com"
    ]
}

PhishDestroy DOM

83 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 0 / 100 · 2026-10-26T16:55:39Z

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-26T16:55:39Z
source_timestamp
2026-10-26 17:55:39
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.ixrii.help — Suspicious Domain
ai_description
PhishDestroy flags mydpd.ixrii.help as a suspicious domain after Google Safe Browsing and VirusTotal identified it as a social‑engineering threat on 2026-10-26.
ai_generated_at
2026-10-26T16:53:48Z
ai_generated_by
threat-v3-groq
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.ixrii.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
ixrii.help

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

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
Content-type
text/plain;charset=utf-8
Strict-transport-security
max-age=31536000; includeSubDomains
Original source fields · JSON
Caa records
{
    "domain": "mydpd.ixrii.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": "ixrii.help"
}
Location
{
    "ip": "209.141.47.167",
    "asn": "53667",
    "org": "FranTech Solutions",
    "city": "Las Vegas",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YR1",
    "subject": "mydpd.ixrii.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
}
Registration record
{
    "registrar": "NameSilo, LLC",
    "created": "2026-10-26T07:28:27Z",
    "updated": "2026-10-26T07:28:31Z",
    "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",
        "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.ixrii.help

Is mydpd.ixrii.help legit?

No. PhishDestroy classifies mydpd.ixrii.help as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-26. VirusTotal: 7/92 engines flag it. Google Safe Browsing flags it. Listed on Spamhaus DBL. Treat the site as unsafe.

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

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

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 · no match in the other 10 2
OpenPhish Listed View source
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.ixrii.help/track-ch/
Position1 / 3
Open capture Wayback Download
All capture links and hashes (3)
Observed page title
mydpd.ixrii.help
TLS Certificate
Issued by Let's Encrypt / YR1 · stored validity ends in 89 days
mydpd.ixrii.help: Phishing site — Flagged by OpenPhish, Google Safe Browsing, Spamhaus DBL, 7/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card mydpd.ixrii.help: Phishing site — Flagged by OpenPhish, Google Safe Browsing, Spamhaus DBL, 7/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 9958026b5796

Domain details

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

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain ixrii.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
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 / YR1
Valid from
2026-10-26 07:00:07
Valid until
2027-01-24 07:00:06
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint11ac0a51a04797c838313ed429dfeca3476e648bfca869082fc85d0e1998884b
Certificate names · 1 SAN
  • mydpd.ixrii.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
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

7 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 7 detections
ESET
Fortinet
G-Data
Google Safe Browsing
LevelBlue
SOCRadar
Sophos
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

All retained availability observations1

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_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-26 17:18:12.960038
    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.ixrii.help detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Google Safe Browsing · Blocklist Detection · Registrar Context: NameSilo · 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: 7/92
  • Google Safe Browsing
    Listed as unsafe by Google Safe Browsing (Google Transparency Report)
  • Blocklist Detection
    Found in blocklists: OpenPhish
  • Registrar Context: NameSilo
    Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
  • 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

    7/92 engine detections

    View source
  3. Added to PhishDestroy

    mydpd.ixrii.help

    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.ixrii.help

Evidence & External Reports

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

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