Skip to security report
Domain security and threat intelligence
dpdie.live favicon

dpdie.live

In short

dpdie.live is a phishing page detected by PhishDestroy on 2026-10-25.

“Redirecting...”

Registrar
NameSilo
Resolved IP
162.4.84.247
Registered
Sep 23, 2025
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 15/92 Stored blocklist matches: 1 Google Safe Browsing: threat flag recorded
VirusTotal
engine detections
OTX
community references
Cloudflare Radar
source verdict
Page captures
open gallery
Domain age
Reports sent
No sent record
Oct 25, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 15. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.

Analysis

Domain summary

dpdie.live is a phishing page detected by PhishDestroy on 2026-10-25. Risk: critical (100/100). Registrar: NameSilo. Status: Last known active. Hosting: ParkLogic Pty Ltd. VirusTotal: 15/92 engines flag it. Google Safe Browsing flags it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
15 / 92
Page captures
8

PhishDestroy threat report

Overview

PhishDestroy listed dpdie.live as a suspicious domain after its page, titled “Redirecting…”, was observed on 2026-10-25. The intake reason cites a Google Safe Browsing flag for social‑engineering. An HTTP check on that date returned a 200 response with the recorded title.

How the scam works

The classification reflects a generic social‑engineering risk where attackers host pages that may trick users into revealing credentials or clicking malicious links. No specific malicious behavior was observed on the captured page, so the exact technique cannot be confirmed.

Evidence

Google Safe Browsing flagged the domain for social‑engineering on 2026-10-25. VirusTotal recorded 15 detections from 92 engines on 2026-10-20, with 14 labeled malicious and 1 suspicious, including phishing tags from vendors such as BitDefender, Fortinet and G‑Data. urlscan.io’s scan on 2026-10-24 reported a malicious engine score of 71, though its overall verdict was non‑malicious. The external Phishunt blocklist also contains dpdie.live, and PhishDestroy’s internal list marks it as blocked. OTX reported zero pulses on 2026-10-25.

Infrastructure

The domain was registered on 2025-09-23 through NameSilo, LLC, giving it an age of about 396 days at the time of observation. The domain was recorded pointing to IP 162.4.84.247, which was associated with ParkLogic Pty Ltd in the United States. TLS was provided by Let’s Encrypt, valid until 2026-12-23, and the domain used ns1.ns306.parklogic.com and ns2.ns306.parklogic.com as authoritative nameservers with an MX record pointing to mail.eye-mail.net.

What to do

Visitors should avoid entering any credentials or clicking links on the site and should change passwords if any were submitted. Organizations can add dpdie.live to web filtering and DNS blocklists, monitor for connections to 162.4.84.247, and review access logs for suspicious activity. No wallet‑related actions are required because no wallet interaction was observed.

Source evidenceVirusTotal 15 / 92 · Google Safe Browsing: flagged 5 sources

VirusTotal

15 / 92 engine detections

Open report
VirusTotal · 2026-10-20T10:18:52Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 14,
    "suspicious": 1,
    "undetected": 31
}
Vendor labels
{
    "DNS8": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "malware",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Google Safe Browsing": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Created
2025-09-23T00:00:00Z
Updated
2025-09-23T00:00:00Z
First seen
2025-09-23T09:31:05Z
DNS records
[
    {
        "ttl": 60,
        "type": "SOA",
        "rname": "hostmaster.dpdie.live",
        "value": "ns1.parklogic.com"
    },
    {
        "ttl": 14400,
        "type": "NS",
        "value": "ns1.ns306.parklogic.com"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "172.237.129.242"
    },
    {
        "ttl": 3600,
        "type": "MX",
        "value": "mail.eye-mail.net",
        "priority": 1
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "172.237.129.236"
    },
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "v=spf1 ip6:fdec:ae16:fda7::/48 -all"
    },
    {
        "ttl": 14400,
        "type": "NS",
        "value": "ns2.ns306.parklogic.com"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "172.237.129.108"
    }
]
Dns at
2026-10-20T10:19:11Z
Jarm
27d40d40d00040d00042d43d0000007d20e9b9a3e87aa1ec17cb4d646ce9a5
Certificate
{
    "san": [
        "dpdie.live"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "6059fec203e210931bb8b94ad9b98771a8a",
    "sha256": "d29b17e542ea092448628beaedc631951a70cf1565b5263fa637544d894a6adc",
    "subject": "dpdie.live",
    "valid_to": "2026-12-23T00:58:00Z",
    "valid_from": "2026-09-24T00:58:01Z"
}
Registry data
{
    "status": [
        "renew period",
        "client hold"
    ],
    "events": {
        "last changed": "2026-09-30T02:18:44Z",
        "registration": "2025-09-23T00:00:00Z",
        "registrar expiration": "2026-09-23T00:00:00Z",
        "last update of RDAP database": "2026-10-20T10:19:10Z"
    },
    "registrar": "NameSilo, LLC",
    "registrar_iana_id": "1479"
}

Google Safe Browsing

Threat flag recorded

Open report

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Not recorded
Open report
Cloudflare Radar · 2026-10-25T10:43:40Z

Observed: · Retrieved:

Uuid
f512e75e-c4d8-40cf-aba9-4143d7d8d5d2
Final url
https://dpdie.live/
History
[
    {
        "url": "https://dpdie.live/",
        "status": 0
    }
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "dpdie.live",
        "type": "A",
        "value": "162.4.84.247"
    }
]
Dnssec valid
false

URLScan

Page capture

Not recorded
Open report
URLScan · 2026-10-24T18:13:13Z

Observed: · Retrieved:

Uuid
01a16f1d-ccf1-75eb-b2a9-c0c0fb3b28a6
Final url
https://dpdie.live/
Status
200
Ip
162.4.84.247
Ptr
anycast.parklogic.com
Contacted domains
[
    "parking3.parklogic.com",
    "router.parklogic.com"
]
Contacted IP addresses
[
    "172.232.7.47",
    "172.234.216.100",
    "162.4.84.247"
]
Asns
[
    "63949",
    "154653"
]
Countries
[
    "US",
    "AU"
]
Linked domains
[
    "www.namesilo.com",
    "adorarama.com",
    "parklogic.com"
]
Document hash
c6cbb707f1b51433e293689bdb4fe3bff7aa9a89b97e758aae597bc0fd7b929b
Globals
[
    "plBanner"
]
Tls
{
    "san": [
        "dpdie.live"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "dpdie.live",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-23T00:58:00Z",
    "valid_from": "2026-09-24T00:58:01Z"
}
Domain age days
396
Apex age days
396
Tls age days
30
Tls valid days
89
Requests
8
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 71,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "openresty",
    "content-type": "text/html",
    "permissions-policy": "ch-ua=(self \"https://*.parklogic.com\"), ch-ua-arch=(self \"https://*.parklogic.com\"), ch-ua-bitness=(self \"https://*.parklogic.com\"), ch-ua-full-version=(self \"https://*.parklogic.com\"), ch-ua-full-ver"
}

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 checks · 2026-10-25T10:44:55Z
Mail configuration
{
    "mx": [
        "mail.eye-mail.net"
    ],
    "spf": "v=spf1 ip6:fdec:ae16:fda7::/48 -all",
    "spf_lookups": 0
}
Caa records
{
    "count": 1,
    "domain": "dpdie.live",
    "issuers": [
        "letsencrypt.org"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Trackers
{
    "requests": 1
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": false,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "162.4.84.12",
            "host": "ns2.ns306.parklogic.com"
        },
        {
            "ip": "162.4.84.11",
            "host": "ns1.ns306.parklogic.com"
        }
    ],
    "zone": "dpdie.live"
}
Location
{
    "ip": "162.4.84.247",
    "asn": "154653",
    "org": "ParkLogic Pty Ltd",
    "city": "Los Angeles",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "dpdie.live"
}
DNS records
{
    "A": [
        "162.4.84.247"
    ],
    "MX": [
        "{\"exchange\": \"mail.eye-mail.net\", \"priority\": 10}"
    ],
    "NS": [
        "ns1.ns306.parklogic.com",
        "ns2.ns306.parklogic.com"
    ],
    "SOA": "{\"nsname\": \"ns1.ns306.parklogic.com\", \"hostmaster\": \"hostmaster.parklogic.com\", \"serial\": 1, \"refresh\": 86400, \"retry\": 7200, \"expire\": 1209600, \"minttl\": 300}",
    "TXT": [
        "v=spf1 ip6:fdec:ae16:fda7::/48 -all"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "162.4.84.247",
    "family": 4
}
Subdomains
{
    "count": 1,
    "subdomains": [
        "www.dpdie.live"
    ]
}
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 dpdie.live

Is dpdie.live legit?

No. PhishDestroy classifies dpdie.live as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-25. VirusTotal: 15/92 engines flag it. Google Safe Browsing flags it. Treat the site as unsafe.

Is dpdie.live safe to connect a wallet?

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

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

Explore

Blocklist matchesPhishDestroy · Phishunt 2
PhishDestroy PhishDestroy list View source
Phishunt Listed View source

Last checked

Stored Capture · 8 captures

All capture links and hashes (8)
Observed page title
Redirecting...
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 58 days

Domain details

Domain
Google Safe Browsing Flagged Social engineering checked Oct 25, 2026
IP Reputation abuse score 0/100 0 reports checked Oct 25, 2026
RegistrationCreated Sep 23, 2025 — Expires Sep 23, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 98/100
Submitted URLhttp://dpdie.live/
Favicon Hash
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, 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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
162.4.84.247
Network ASN
AS154653
Organization
ParkLogic Pty Ltd
Observed location
Los Angeles, US
Server header
openresty

Nameservers 2

  • ns1.ns306.parklogic.com
  • ns2.ns306.parklogic.com

Mail routing 1 MX record

  • mail.eye-mail.netpriority 1

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-09-24 00:58:01
Valid until
2026-12-23 00:58:00
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintd29b17e542ea092448628beaedc631951a70cf1565b5263fa637544d894a6adc
Certificate names · 1 SAN
  • dpdie.live

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

Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.dpdie.liveDomain record

The original observation time is not recorded for these hostnames.

Report This Domain Submit evidence & help protect others

VirusTotal Analysis

15 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
CyRadar
DNS8
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
Lionic
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of dpdie.live · checked Oct 25, 2026

97
Good
Performance
FCP
0.77 s
First Contentful Paint
LCP
2.56 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.67 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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 observations2

Source: availability monitor. This journal includes earlier observations and repeated states with distinct dates or evidence. Identical records appear once; an unknown state is not proof that the site is offline.

  1. unknown
    Cause
    stale_current_evidence
    Monitor confidence
    0
    Original source timestamp
    2026-10-25 11:46:45.513500
    Evidence SHA-256
    95dedd1e4016ea57e34bdbce51e0ec491a6e3d89d4fb09684d0437765fe8625c
  2. unknown
    Cause
    probe_inconclusive
    Monitor confidence
    20
    Original source timestamp
    2026-10-25 10:06:24.862259
    Evidence SHA-256
    8895fe784317ce956fd87b3c03d7dee28c93bf969fb14b515b4f932e1c762121

Recorded activity

3 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. VirusTotal

    15/92 engine detections

    View source
  3. Added to PhishDestroy

    dpdie.live

    View source

Check for cloaking

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

dpdie.live

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Last known active
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.

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 dpdie.live)
  • 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

Stay Informed, Stay Safe

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

Official reporting routes

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.

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/dpdie.live"
  title="PhishDestroy threat report for dpdie.live"
  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>