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

mydpd.ihkjj.top

In short

PhishDestroy records mydpd.ihkjj.top, where the captured page reports an HTTP 404 error stating that no webpage was found for the requested address.

“mydpd.ihkjj.top”

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

Analysis

Domain summary

PhishDestroy records mydpd.ihkjj.top, where the captured page reports an HTTP 404 error stating that no webpage was found for the requested address.

Critical
VirusTotal
1 / 92
Hosting
United States209.141.47.167FranTech Solutions
Registrar
United StatesNameSilo
Page captures
4
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page at mydpd.ihkjj.top is a browser-generated error screen rather than a site interface. It states that no webpage was found for https://mydpd.ihkjj.top/ and identifies the failure as HTTP ERROR 404, with a single Reload button as the only interaction offered.

On VirusTotal, the domain mydpd.ihkjj.top was flagged by 1 of 92 engines in the analysis dated 2026-10-29. The flagging vendor CRDF labeled the domain malicious, while no other engine in this retrieval reported a malicious or suspicious verdict.

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

VirusTotal

1 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
54
Malicious
1
Suspicious
0
Undetected
37

Vendor labels

CRDF
malicious

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.ihkjj.top
Issuer
Let's Encrypt / YR1
Serial
6269f4476120f8f19aad6ad5adbf1d89425
SHA-256
b75599191b7fc96462c940b87038e8d2e215e1a88570150beed160ab518e88b8
Subject
mydpd.ihkjj.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": 54,
    "malicious": 1,
    "suspicious": 0,
    "undetected": 37
}
Vendor labels
{
    "CRDF": "malicious"
}
Reputation
0
Registrar
NameSilo,LLC
Created
2026-10-28T08:27:48Z
Expires
2027-10-28T08:27:48Z
Updated
2026-10-28T08:27:52Z
First seen
2026-10-28T10:49:05Z
DNS records
[
    {
        "ttl": 7207,
        "type": "A",
        "value": "209.141.47.167"
    }
]
Dns at
2026-10-29T13:21:39Z
Jarm
29d29d00029d29d00042d42d00000090d94d1f02cef4051cfd1d66dbe44eb0
Certificate
{
    "san": [
        "mydpd.ihkjj.top"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "6269f4476120f8f19aad6ad5adbf1d89425",
    "sha256": "b75599191b7fc96462c940b87038e8d2e215e1a88570150beed160ab518e88b8",
    "subject": "mydpd.ihkjj.top",
    "valid_to": "2027-01-26T09:41:03Z",
    "valid_from": "2026-10-28T09:41:04Z"
}
Registration record
{
    "registrar": "NameSilo,LLC",
    "registrar_iana_id": "1479",
    "registrar_url": "https://www.namesilo.com",
    "created": "2026-10-28T08:27:48Z",
    "updated": "2026-10-28T08:27:52Z",
    "expires": "2027-10-28T08:27:48Z",
    "status": [
        "addPeriod",
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ns1.dnsowl.com",
        "ns2.dnsowl.com",
        "ns3.dnsowl.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 1 malicious + 0 suspicious / 92 · 2026-10-29 13:16:23 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-29T13:16:23Z
fetched_at
2026-10-29T13:42:58Z
stats
{"timeout":0,"harmless":54,"malicious":1,"suspicious":0,"undetected":37}

Google Safe Browsing

Threat flag recorded

Open report

Spamhaus DBL

phishing domain

URLScan

Malicious · engine verdict · score 80

SHA-256 ea1ab50089d7f177dffe884bf0554e123a7be35c2cf2005f5e6c8cd17f2754c4

Open report
URLScanOriginal source recordObserved: 19 fields

Observed: · Retrieved:

Report ID

01a187c1-08e0-755b-ab68-52e1d3479b1d

Final URL

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

HTTP response

200

Redirect type

same-domain

IP address

209.141.47.167

Contacted IP addresses

  • 209.141.47.167

Autonomous systems (ASN)

  • 53667

Server countries

  • US

Document hash

48402ffd5ccd5e3aa1f289c9200028ad3bc38602744eeefa8d37022d27571bac

Script hashes

  • e9473ffd649e62a74805adc6cc89c6b29ce7f925748af7f5a1e8135e1e17e8ee
  • d0b8826fb0964ef7b075835c14fe14a06f991eb3f606cd26d4452b1e3e1c2dd7

Cookies

  • _vt

TLS session and certificate

Subject alternative names
  • mydpd.ihkjj.top
Cipher
AES_256_GCM
Issuer
YR1
Subject
mydpd.ihkjj.top
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

0

Registered domain age, days

0

Certificate age, days

1

Certificate validity, days

89

Page requests

6

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
80
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
openresty
Content-type
text/html;charset=utf-8
Strict-transport-security
max-age=31536000; includeSubDomains
X-content-type-options
nosniff
Original source fields · JSON
Uuid
01a187c1-08e0-755b-ab68-52e1d3479b1d
Final url
https://mydpd.ihkjj.top/track-ch/
Status
200
Redirected
same-domain
Ip
209.141.47.167
Contacted IP addresses
[
    "209.141.47.167"
]
Asns
[
    "53667"
]
Countries
[
    "US"
]
Document hash
48402ffd5ccd5e3aa1f289c9200028ad3bc38602744eeefa8d37022d27571bac
Script hashes
[
    "e9473ffd649e62a74805adc6cc89c6b29ce7f925748af7f5a1e8135e1e17e8ee",
    "d0b8826fb0964ef7b075835c14fe14a06f991eb3f606cd26d4452b1e3e1c2dd7"
]
Cookies
[
    "_vt"
]
Tls
{
    "san": [
        "mydpd.ihkjj.top"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR1",
    "subject": "mydpd.ihkjj.top",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-26T09:41:03Z",
    "valid_from": "2026-10-28T09:41:04Z"
}
Domain age days
0
Apex age days
0
Tls age days
1
Tls valid days
89
Requests
6
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 80,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "openresty",
    "content-type": "text/html;charset=utf-8",
    "strict-transport-security": "max-age=31536000; includeSubDomains",
    "x-content-type-options": "nosniff"
}
Separate monitor record · 2026-10-30 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a187c1-08e0-755b-ab68-52e1d3479b1d
score
0
malicious
false
result_at
2026-10-30T04:30:31Z
enriched_at
2026-10-30T09:11:46Z
source_timestamps
{"urlscan_result_at":"2026-10-30 05:30:31","urlscan_enriched_at":"2026-10-30 10:11:46"}
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

f946628e-612c-4a7d-8a01-c05f1d6285b3

Final URL

https://mydpd.ihkjj.top/

HTTP response

404

Navigation history

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

DOM structure hash

4dbc72dffccc8f8b936ed5c6039471f9fdd0adc6168a644b2f27e26a223c4772

Document hash

ed2e9dccd95075d710c6f3578f265a996295befeb8ed170bd93f38e088b3cbf9

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    mydpd.ihkjj.top
    Type
    A
    Value
    209.141.47.167

DNSSEC valid

No

IP address

127.0.1.26

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

Registration record

Registrar
NameSilo,LLC
Registered
Updated
Expires
Nameservers
  • ns1.dnsowl.com.
  • ns2.dnsowl.com.
  • ns3.dnsowl.com.
Original source fields · JSON
Uuid
f946628e-612c-4a7d-8a01-c05f1d6285b3
Final url
https://mydpd.ihkjj.top/
Status
404
History
[
    {
        "url": "https://mydpd.ihkjj.top/",
        "status": 404
    }
]
DOM structure hash
4dbc72dffccc8f8b936ed5c6039471f9fdd0adc6168a644b2f27e26a223c4772
Document hash
ed2e9dccd95075d710c6f3578f265a996295befeb8ed170bd93f38e088b3cbf9
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "mydpd.ihkjj.top",
        "type": "A",
        "value": "209.141.47.167"
    }
]
Dnssec valid
false
Ip
127.0.1.26

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

Registration record
{
    "registrar": "NameSilo,LLC",
    "created": "2026-10-28T08:27:48Z",
    "updated": "2026-10-28T08:27:52Z",
    "expires": "2027-10-28T08:27:48Z",
    "nameservers": [
        "ns1.dnsowl.com.",
        "ns2.dnsowl.com.",
        "ns3.dnsowl.com."
    ]
}

PhishDestroy DOM

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

Open report
Separate monitor score · 0 / 100 · 2026-10-29T14:00:57Z

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-29T14:00:57Z
source_timestamp
2026-10-29 15:00:57
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.ihkjj.top HTTP 404 error page
ai_description
PhishDestroy records mydpd.ihkjj.top, where the captured page reports an HTTP 404 error stating that no webpage was found for the requested address.
ai_summary
The captured page at mydpd.ihkjj.top is a browser-generated error screen rather than a site interface. It states that no webpage was found for https://mydpd.ihkjj.top/ and identifies the failure as HTTP ERROR 404, with a single Reload button as the only interaction offered. On VirusTotal, the domain mydpd.ihkjj.top was flagged by 1 of 92 engines in the analysis dated 2026-10-29. The flagging vendor CRDF labeled the domain malicious, while no other engine in this retrieval reported a malicious or suspicious verdict.
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-29 14:45:21
revision
4d161620cfc8e2ec289bc09cb38651896070c39d304242eee9f19fda7d29363f
mode
reviewed
interpretation
Selected public package; text generation time is separate from source 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: 15 fields

CAA records

Domain
mydpd.ihkjj.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.27.173
    Host
    ns1.dnsowl.com
  • IP address
    162.159.27.130
    Host
    ns2.dnsowl.com
DNS zone
ihkjj.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.ihkjj.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

Subdomains

Count
1
Subdomains
  • mydpd.ihkjj.top

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
Strict-transport-security
max-age=31536000; includeSubDomains
Original source fields · JSON
Caa records
{
    "domain": "mydpd.ihkjj.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.27.173",
            "host": "ns1.dnsowl.com"
        },
        {
            "ip": "162.159.27.130",
            "host": "ns2.dnsowl.com"
        }
    ],
    "zone": "ihkjj.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.ihkjj.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
}
Subdomains
{
    "count": 1,
    "subdomains": [
        "mydpd.ihkjj.top"
    ]
}
Registration record
{
    "registrar": "NameSilo,LLC",
    "created": "2026-10-28T08:27:48Z",
    "updated": "2026-10-28T08:27:52Z",
    "expires": "2027-10-28T08:27:48Z",
    "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",
        "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.ihkjj.top

Is mydpd.ihkjj.top legit?

PhishDestroy records mydpd.ihkjj.top, where the captured page reports an HTTP 404 error stating that no webpage was found for the requested address.

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

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

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

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

Explore

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

Checked, no match

Last checked

Stored Capture · 4 captures

Cloudflare Radar 1 / 4 Used in the analysis Source file SHA-256: 4d78333aae2f916e43b1052162ba408d7765b6c0bbc006646bf19c8a0f314b8b SHA-256 of the prepared copy given to the model: fa88e099569aab96a1af1076a9c9d91543605692daacc19eb39a6fbfcd0d82ab
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status404
Final URLhttps://mydpd.ihkjj.top/
Position1 / 4
Open capture Source Report Wayback Download
All capture links and hashes (4)
Observed page title
mydpd.ihkjj.top
TLS Certificate
Issued by Let's Encrypt / YR1 · stored validity ends in 86 days
mydpd.ihkjj.top: Phishing site — Flagged by Google Safe Browsing, Spamhaus DBL, 1/92 VirusTotal engines. PhishDestroy risk score 80/100 (critical).
Social preview card mydpd.ihkjj.top: Phishing site — Flagged by Google Safe Browsing, Spamhaus DBL, 1/92 VirusTotal engines. PhishDestroy risk score 80/100 (critical). v 0973bfc3f7ce

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 80 report ↗
Google Safe Browsing Flagged Social engineering checked Oct 29, 2026
IP Reputation United States209.141.47.167 abuse score 0/100 0 reports checked Oct 29, 2026
Registrar (base domain) NameSilo US(US) PhishDestroy Investigation
Abuse contact["abuse@namesilo.com", "3432650ec337c945s@"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for ihkjj.top →
Registration (base domain)ihkjj.top · Expires Oct 28, 2027
WHOIS statusclientTransferProhibitedaddPeriod
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 29, 2026
DOM Analysisanalyzed Oct 29, 2026score 0/100
Submitted URLhttp://mydpd.ihkjj.top/track-ch
ICANN OVERSIGHT Registration: ihkjj.top

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain ihkjj.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
United States209.141.47.167
Network ASN
AS53667
AS name
PONYNET - FranTech Solutions, US
Organization
FranTech Solutions
Observed location
United StatesLas Vegas, US
Server header
openresty

Nameservers 3

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

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR1
Valid from
2026-10-28 09:41:04
Valid until
2027-01-26 09:41:03
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintb75599191b7fc96462c940b87038e8d2e215e1a88570150beed160ab518e88b8
Certificate names · 1 SAN
  • mydpd.ihkjj.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-31 22:20:09 UTC

The domain no longer resolves in DNS.

Technical details
Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Probe Inconclusive 20% 2026-11-01 02:49:55 UTC
RDAP registration
Observed timeline current episode first observed: 2026-10-30 21:35:15 UTC first terminal observation: 2026-10-30 21:35:15 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

1 / 92 security vendors flagged this domain
View on VT
Last analyzed
CRDF
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.ihkjj.top/track-ch
Final URL: https://mydpd.ihkjj.top/track-ch/
Response
HTTP 200
HTML body
2.4 KB
Compressed
949 B
Links
0 internal · 0 external
Selected response headers
Server: openresty
Content-Type: text/html;charset=utf-8
Content-Encoding: gzip
Security headers present
Strict-Transport-SecurityX-Content-Type-Options
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 9
Connection
keep-alive
Content-Encoding
gzip
Content-Length
949
Content-Type
text/html;charset=utf-8
Date
Thu, 29 Oct 2026 13:44:25 GMT
Expires
Thu, 01 Jan 1970 00:00:00 GMT
Server
openresty
Strict-Transport-Security
max-age=31536000; includeSubDomains
X-Content-Type-Options
nosniff

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

Archived
Registration & observation details3

Availability observations

Outcome first observed
Observation window ends
Estimate basis
first_observation_only

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

Captured network requests

Network requests: 6 SHA-256 hashes: 4 URLScan scan:

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

Open this scan on URLScan 01a187c1-08e0-755b-ab68-52e1d3479b1d ↗

Stored observation history3

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

  1. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  3. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

All retained availability observations13

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

  1. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:49:55.000000
    Evidence SHA-256
    5bec74b829e1e01ff207de659e52eda311747d4eb2dff13d20308b7f3889f80f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 03:49:55
    Evidence reason
    unavailable
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:04:46.000000
    Evidence SHA-256
    ceb6a4ba4e54af9feba3c10e0535e37f15c4f9b2f5881e76ec0c5504a1ae394e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 00:04:46
    Evidence reason
    unavailable
  3. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 23:20:09.600237
    Evidence SHA-256
    d67f17873ab6334771d07dd3b9a9e8bfa490108372ed2f506a6eee3a33b36baa
    Evidence timestamp as recorded
    2026-10-31 23:20:09.600237
  4. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 23:20:09.600237
    Evidence SHA-256
    d67f17873ab6334771d07dd3b9a9e8bfa490108372ed2f506a6eee3a33b36baa
    Evidence timestamp as recorded
    2026-10-31 23:20:09.600237
  5. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:05:04.000000
    Evidence SHA-256
    52a299981b1c5dd9ad10ee5aa1879454540c8873e6cb08867bceb84d84a3c0d8
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 12:05:04
    Evidence reason
    unavailable
  6. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:25:39.000000
    Evidence SHA-256
    956cf85ff299274db144807cc45031963285291e945ad1f8a529f7928c56f5c2
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 03:25:39
    Evidence reason
    unavailable
  7. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 22:35:15.875079
    Evidence SHA-256
    8be630eb9a84e806aba7083927916d9e4d8d4ab0f0eb458cbced6d0f1846248f
    Evidence timestamp as recorded
    2026-10-30 22:35:15.875079
  8. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 22:35:15.875079
    Evidence SHA-256
    8be630eb9a84e806aba7083927916d9e4d8d4ab0f0eb458cbced6d0f1846248f
    Evidence timestamp as recorded
    2026-10-30 22:35:15.875079
  9. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:00:18.000000
    Evidence SHA-256
    81bab34c498f710ebec771df831c2232f3cbccdc530b09a2a33b18e6a3c6c174
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 12:00:18
    Evidence reason
    unavailable
  10. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:00:18.000000
    Evidence SHA-256
    81bab34c498f710ebec771df831c2232f3cbccdc530b09a2a33b18e6a3c6c174
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 12:00:18
    Evidence reason
    unavailable
  11. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:00:19.000000
    Evidence SHA-256
    e01abe1473ded6bca95e24d8c590bc00cf4fb6a0ec6ce7c35c1b719feec4b55c
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 00:00:19
    Evidence reason
    unavailable
  12. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:00:19.000000
    Evidence SHA-256
    e01abe1473ded6bca95e24d8c590bc00cf4fb6a0ec6ce7c35c1b719feec4b55c
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 00:00:19
    Evidence reason
    unavailable
  13. 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-29 14:45:17.833446
    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: 11. 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.ihkjj.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 · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • Spamhaus DBL
    Spamhaus DBL recorded: phishing domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 80
  • 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: 1/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.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

4 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. Added to PhishDestroy

    mydpd.ihkjj.top

    View source
  3. VirusTotal

    1/92 engine detections

    View source
  4. URLScan

    Malicious · engine verdict · score 80

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

Evidence & External Reports

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

Were You Affected by This Site?

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

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

Immediate steps Find reporting contacts

Official reporting routes

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

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

IdentityTheft.gov United States

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

CISA United States

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

CSIRTs Network European Union

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

FIRST Worldwide

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

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

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

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

Report to Your Local Authorities

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

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

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

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

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

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including mydpd.ihkjj.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.ihkjj.top"
  title="PhishDestroy threat report for mydpd.ihkjj.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>