Skip to security report
This domain has been flagged as malicious
Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
dhl-tracking.live favicon

dhl-tracking.live

In short

dhl-tracking.live is a DHL impersonation page detected by PhishDestroy on 2026-10-25.

“DHL Seguimiento — ¿Dónde está mi paquete?”

Registrar
Hosting Concepts
Resolved IP
188.114.97.3
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed HTTP probe
Spamhaus DBL: phishing domain Stored blocklist matches: 2 Automated brand label: DHL Scam type: Impersonation Google Safe Browsing: threat flag recorded
VirusTotal
engine detections ·
OTX
community references
Cloudflare Radar
Page captures
open gallery
Domain age
Not recorded
Reports sent
view timeline
OTX: 1 ref Oct 25, 2026 1 Report Sent CDN
X Telegram API

Analysis

Domain summary

dhl-tracking.live is a DHL impersonation page detected by PhishDestroy on 2026-10-25. Risk: critical (85/100). Registrar: Hosting Concepts. Status: Last known active. Hosting: CloudFLARENET-EU. PhishDestroy sent 1 abuse report. Google Safe Browsing flags it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

Critical
VirusTotal
0 / 92
OTX
1 community ref
Page captures
8

PhishDestroy threat report

Overview

PhishDestroy listed dhl-tracking.live as a suspicious domain. The recorded page title was “DHL Seguimiento — ¿Dónde está mi paquete?”. The domain first appeared in PhishDestroy’s intake on 2026-10-25, and an HTTP 200 response was recorded on that date.

How the scam works

The page presented a DHL‑branded tracking interface, a common lure for harvesting shipment numbers or login credentials. Such impersonations typically aim to trick users into providing personal data that can be used for credential theft or further social‑engineering attacks.

Evidence

Google Safe Browsing flagged the URL for social engineering on 2026-10-25. urlscan.io captured the site on 2026-10-25 and returned a malicious phishing verdict with a score of 100, identifying DHL as the impersonated brand. OpenPhish and Phishunt both listed the domain as malicious as of the same date. OTX recorded one pulse referencing the domain on 2026-10-25. PhishDestroy’s internal blocklist marked the domain as true. VirusTotal scanned the domain on 2026-10-25 with 92 engines and reported zero detections.

Infrastructure

The domain was registered on 2026-10-24 through Hosting Concepts B.V. d/b/a Registrar.eu. TLS was provided by Let’s Encrypt, valid from 2026-10-24 to 2027-01-22, covering *.dhl-tracking.live. The recorded IP addresses included 172.67.139.126 and 104.21.26.227, both belonging to the CloudFLARENET‑EU network in GB. No DNSSEC records were observed.

What to do

Visitors should not enter DHL credentials, tracking numbers, or personal data on this site and should delete any information already submitted. Monitor any DHL account for unauthorized activity and report the domain to DHL’s abuse team. Network defenders can block dhl-tracking.live at firewalls or proxies and review logs for connections to the recorded IPs.

Source evidenceVirusTotal 0 / 92 · Google Safe Browsing: flagged · OTX 1 references 9 sources

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Report ID

bdc2a691-371e-4396-bba4-699a49b61196

Final URL

https://dhl-tracking.live/

HTTP response

200

Navigation history

  • URL
    https://dhl-tracking.live/
    Status
    200

DOM structure hash

865c3ff7d0d49be8fb79f3bc733eb88c6ea98a5b4bd7971c420673bb915eca4b

Document hash

feb0163cf638448ea56a0543fb4128d3d9c74ca350635d6fdf4e8a0bd3e5dd4d

Phishing classifier result

  • phishing

URL risk categories

  • Phishing

Domain risk categories

  • Newly Seen Domains
  • Security Risks
  • Phishing
  • Security threats
  • New Domains
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    dhl-tracking.live
    Type
    A
    Value
    172.67.139.126
  • Name
    dhl-tracking.live
    Type
    A
    Value
    104.21.26.227
  • Name
    dhl-tracking.live
    Type
    AAAA
    Value
    2606:4700:3034::6815:1ae3
  • Name
    dhl-tracking.live
    Type
    AAAA
    Value
    2606:4700:3032::ac43:8b7e

DNSSEC valid

No

IP address

172.67.139.126

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
Hosting Concepts B.V. d/b/a Registrar.eu
Registered
Updated
Expires
Nameservers
  • rafe.ns.cloudflare.com
  • henrik.ns.cloudflare.com
Original source fields · JSON
Uuid
bdc2a691-371e-4396-bba4-699a49b61196
Final url
https://dhl-tracking.live/
Status
200
History
[
    {
        "url": "https://dhl-tracking.live/",
        "status": 200
    }
]
DOM structure hash
865c3ff7d0d49be8fb79f3bc733eb88c6ea98a5b4bd7971c420673bb915eca4b
Document hash
feb0163cf638448ea56a0543fb4128d3d9c74ca350635d6fdf4e8a0bd3e5dd4d
Phishing v2
[
    "phishing"
]
Url risks
[
    "Phishing"
]
Domain risks
[
    "Newly Seen Domains",
    "Security Risks",
    "Phishing",
    "Security threats",
    "New Domains",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "dhl-tracking.live",
        "type": "A",
        "value": "172.67.139.126"
    },
    {
        "name": "dhl-tracking.live",
        "type": "A",
        "value": "104.21.26.227"
    },
    {
        "name": "dhl-tracking.live",
        "type": "AAAA",
        "value": "2606:4700:3034::6815:1ae3"
    },
    {
        "name": "dhl-tracking.live",
        "type": "AAAA",
        "value": "2606:4700:3032::ac43:8b7e"
    }
]
Dnssec valid
false
Ip
172.67.139.126
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "Hosting Concepts B.V. d/b/a Registrar.eu",
    "created": "2026-10-24T20:37:18Z",
    "updated": "2026-10-24T20:37:23Z",
    "expires": "2027-10-24T20:37:18Z",
    "nameservers": [
        "rafe.ns.cloudflare.com",
        "henrik.ns.cloudflare.com"
    ]
}

Google Safe Browsing

Threat flag recorded

Open report

Spamhaus DBL

phishing domain

URLScan

Malicious

Open report
URLScanOriginal source recordObserved: 19 fields

Observed: · Retrieved:

Report ID

01a173ec-8d75-7079-b9d3-6d7eafedec2b

Final URL

https://dhl-tracking.live/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://dhl-tracking.live/
    From
    http://dhl-tracking.live/
    Status
    307

IP address

104.21.26.227

Contacted domains

  • static.cloudflareinsights.com
  • www.dhl.com

Contacted IP addresses

  • 104.16.79.73
  • 104.21.26.227

Autonomous systems (ASN)

  • 13335

Document hash

feb0163cf638448ea56a0543fb4128d3d9c74ca350635d6fdf4e8a0bd3e5dd4d

JavaScript globals

  • trackPackage
  • __cfBeacon

TLS session and certificate

Subject alternative names
  • *.dhl-tracking.live
  • dhl-tracking.live
Cipher
AES_128_GCM
Issuer
YE2
Subject
dhl-tracking.live
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

7

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
98
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • dhl
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • DHL
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
cloudflare
Content-type
text/html
X-content-type-options
nosniff
Original source fields · JSON
Uuid
01a173ec-8d75-7079-b9d3-6d7eafedec2b
Final url
https://dhl-tracking.live/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://dhl-tracking.live/",
        "from": "http://dhl-tracking.live/",
        "status": 307
    }
]
Ip
104.21.26.227
Contacted domains
[
    "static.cloudflareinsights.com",
    "www.dhl.com"
]
Contacted IP addresses
[
    "104.16.79.73",
    "104.21.26.227"
]
Asns
[
    "13335"
]
Document hash
feb0163cf638448ea56a0543fb4128d3d9c74ca350635d6fdf4e8a0bd3e5dd4d
Globals
[
    "trackPackage",
    "__cfBeacon"
]
Tls
{
    "san": [
        "*.dhl-tracking.live",
        "dhl-tracking.live"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "dhl-tracking.live",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-22T19:52:59Z",
    "valid_from": "2026-10-24T19:53:00Z"
}
Domain age days
0
Apex age days
0
Tls age days
0
Tls valid days
89
Requests
7
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 98,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "dhl"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "DHL"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html",
    "x-content-type-options": "nosniff"
}
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
01a17326-ce00-74b3-8746-ff6a4d5a5cc7
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

VirusTotal

0 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 9 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
55
Malicious
0
Suspicious
0
Undetected
37

Reputation score

0

Categories

Google
transportation
alphaMountain.ai
Phishing (alphaMountain.ai)

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    104.21.26.227
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    henrik.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3032::ac43:8b7e
  • TTL, seconds
    21600
    Type
    NS
    Value
    rafe.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3034::6815:1ae3
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.139.126
  • TTL, seconds
    21600
    Type
    NS
    Value
    henrik.ns.cloudflare.com

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.dhl-tracking.live
  • dhl-tracking.live
Issuer
Let's Encrypt / YE2
Serial
682792a45f8008326d9833be0fa5e9d953b
SHA-256
2162adfc38fe66601c54b0ce5cbf8e455ae3d9d524ad4354e6d140d74fb2d4e8
Subject
dhl-tracking.live
Valid until
Valid from

Registry data (RDAP)

Status
  • client transfer prohibited
Registry events
Expiration
Registration
Registrar expiration
Last RDAP database update
Registrar
Hosting Concepts B.V. d/b/a Registrar.eu
Registrar IANA ID
1647
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 37
}
Reputation
0
Categories
{
    "Google": "transportation",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
First seen
2026-10-24T20:55:27Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.26.227"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "henrik.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3032::ac43:8b7e"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "rafe.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3034::6815:1ae3"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.139.126"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "henrik.ns.cloudflare.com"
    }
]
Dns at
2026-10-25T15:51:40Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.dhl-tracking.live",
        "dhl-tracking.live"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "682792a45f8008326d9833be0fa5e9d953b",
    "sha256": "2162adfc38fe66601c54b0ce5cbf8e455ae3d9d524ad4354e6d140d74fb2d4e8",
    "subject": "dhl-tracking.live",
    "valid_to": "2027-01-22T19:52:59Z",
    "valid_from": "2026-10-24T19:53:00Z"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-24T20:37:18Z",
        "registration": "2026-10-24T20:37:18Z",
        "registrar expiration": "2027-10-24T20:37:18Z",
        "last update of RDAP database": "2026-10-24T20:55:16Z"
    },
    "registrar": "Hosting Concepts B.V. d/b/a Registrar.eu",
    "registrar_iana_id": "1647"
}
Separate source record · 0 malicious + 0 suspicious / 92 · 2026-10-25 15:46:13 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-25T15:46:13Z
fetched_at
2026-10-25T16:26:20Z
stats
{"timeout":0,"harmless":55,"malicious":0,"suspicious":0,"undetected":37}

OTX

1 community reference

Open report

PhishDestroy DOM

85 / 100 · heuristic score · 1 brand references · 1 classifications

Open report

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
dhl-tracking.live — Suspicious Domain
ai_description
PhishDestroy flagged dhl-tracking.live on 2026-10-25 as a suspicious DHL‑tracking impersonation after Google Safe Browsing labeled it social‑engineering.
ai_generated_at
2026-10-25T16:31:10Z
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: 23 fields

Mail configuration

SPF lookups
0

CAA records

Domain
dhl-tracking.live

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
4248

Page title and metadata

Page title
DHL Seguimiento — ¿Dónde está mi paquete?

Trackers

Requests
1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
12
TLS
52
Waiting
65
Connection
8
Download
0
Response time, ms
137

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
7771
CO₂, grams
0.0003
Cleaner than, %
77

DNS servers

Nameservers
  • IP address
    108.162.195.105
    Host
    henrik.ns.cloudflare.com
  • IP address
    173.245.58.216
    Host
    rafe.ns.cloudflare.com
DNS zone
dhl-tracking.live

Location

IP address
2a06:98c1:3120::3
ASN
13335
Organization
CloudFLARENET-EU
City
London
Country
GB

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
dhl-tracking.live

DNS records

A
  • 188.114.97.3
  • 188.114.96.3
NS
  • rafe.ns.cloudflare.com
  • henrik.ns.cloudflare.com
SOA
Primary nameserver
henrik.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418378423
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2a06:98c1:3121::3
  • 2a06:98c1:3120::3

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2a06:98c1:3120::3
IP version
6

Redirects

Redirect chain
  • https://dhl-tracking.live

Page links

Internal links
1

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html
X-content-type-options
nosniff
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "dhl-tracking.live"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-25T16:23:34Z",
    "first": "2026-10-25T16:23:34Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 4248
}
Page title and metadata
{
    "title": "DHL Seguimiento — ¿Dónde está mi paquete?"
}
Trackers
{
    "requests": 1
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 12,
        "tls": 52,
        "wait": 65,
        "connect": 8,
        "download": 0
    },
    "response_ms": 137
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 7771,
    "co2_grams": 0.0003,
    "cleaner_than": 77
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.195.105",
            "host": "henrik.ns.cloudflare.com"
        },
        {
            "ip": "173.245.58.216",
            "host": "rafe.ns.cloudflare.com"
        }
    ],
    "zone": "dhl-tracking.live"
}
Location
{
    "ip": "2a06:98c1:3120::3",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "dhl-tracking.live"
}
DNS records
{
    "A": [
        "188.114.97.3",
        "188.114.96.3"
    ],
    "NS": [
        "rafe.ns.cloudflare.com",
        "henrik.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"henrik.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418378423, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2a06:98c1:3121::3",
        "2a06:98c1:3120::3"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2a06:98c1:3120::3",
    "family": 6
}
Redirects
{
    "chain": [
        "https://dhl-tracking.live"
    ]
}
Page links
{
    "internal_count": 1
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html",
        "x-content-type-options": "nosniff"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Security threats Security Risks Phishing Phishing New Domains

Questions about dhl-tracking.live

Is dhl-tracking.live legit?

No. PhishDestroy classifies dhl-tracking.live as a DHL impersonation page (risk: critical, 85/100); it was first detected on 2026-10-25. Google Safe Browsing flags it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is dhl-tracking.live safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on dhl-tracking.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 dhl-tracking.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 matchesOpenPhish · PhishDestroy · Phishunt 3
OpenPhish Listed View source
PhishDestroy PhishDestroy list View source
Phishunt Listed View source

Last checked

Stored Capture · 8 captures

All capture links and hashes (8)
Observed page title
DHL Seguimiento — ¿Dónde está mi paquete?
Automated brand references
Dhl
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 88 days

Domain details

Domain
Google Safe Browsing Flagged Social engineering checked Oct 25, 2026
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags dhldomaindomainsphishingscamurlurls
Registrar Hosting Concepts NL(NL)
RegistrationExpires Oct 24, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 85/1001 brand signal
Submitted URLhttp://dhl-tracking.live/
Favicon Hash
Case ID
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

Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
CloudFLARENET-EU
Observed location
London, GB
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • henrik.ns.cloudflare.com
  • rafe.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-24 19:53:00
Valid until
2027-01-22 19:52:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint2162adfc38fe66601c54b0ce5cbf8e455ae3d9d524ad4354e6d140d74fb2d4e8
Certificate names · 2 SANs
  • *.dhl-tracking.live
  • dhl-tracking.live

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

Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

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

100
Good
Performance
FCP
1.5 s
First Contentful Paint
LCP
1.5 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.5 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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://dhl-tracking.live/
Final URL: https://dhl-tracking.live/
DHL Seguimiento — ¿Dónde está mi paquete?
Response
HTTP 200
HTML body
7.9 KB
Compressed
3.1 KB
Links
1 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
Security headers present
X-Content-Type-Options
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 15
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a50290917cf8c573-IAD
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Sun, 25 Oct 2026 16:23:15 GMT
Last-Modified
Sat, 24 Oct 2026 21:19:03 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=IjIqoafeKfZZiaYswQ%2Fnjj7Y5HCQH218gt4jhm2b1cYLr1wRqDPAwlS8Mrjt96Q1DJEJ%2BANT%2FwaQawlpMOyJFXqvoJj3JbnLoAkz5X9JmyRkxslc7tKYk3RthaPjPjOIaEM%2F7Q%
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
Vary
Accept-Encoding
X-Content-Type-Options
nosniff

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

Stored observation history2

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

  1. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  2. Domain monitor · First collection record

    Reachable

All retained availability observations3

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

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 17:38:57.000000
    Evidence SHA-256
    1632110019e678038d28f153ad2985ad4adef4c1b0ef09dba4231bfd3df72b55
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 17:38:57
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 17:38:57.000000
    Evidence SHA-256
    1632110019e678038d28f153ad2985ad4adef4c1b0ef09dba4231bfd3df72b55
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 17:38:57
    Evidence reason
  3. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 17:29:19.030122
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Recorded activity

8 entries
  1. Abuse report sent

    PD-20261025-A07804

    abuse@registrar.eu
  2. URLScan

    Page captured

    View source
  3. AlienVault OTX

    1 community references

    View source
  4. Cloudflare Radar

    Phishing

    View source
  5. Google Safe Browsing

    Threat flag recorded

    View source
  6. VirusTotal

    0/92 engine detections

    View source
  7. Wayback Machine

    Page archived

    View source
  8. Added to PhishDestroy

    dhl-tracking.live

    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.

Check for cloaking

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

dhl-tracking.live

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261025-A07804 Recipient: abuse@registrar.eu
PDF notice generated
Deep Analysis
Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 1 stored notification records Last known active
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.

Official reporting routes

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

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 dhl-tracking.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

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