Skip to security report
Recorded security signals
Stored VirusTotal result: 4/92 engines flagged. malicious: 1. suspicious: 3. Analysis time (as stored): 2026-11-06T15:57:30Z. Retrieved (as stored): 2026-11-08T01:29:28Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
mijn-dhl.help favicon

mijn-dhl.help

In short

PhishDestroy first recorded mijn-dhl.help on 2026-11-07. Stored VirusTotal result: 4/92 engines flagged. malicious: 1. suspicious: 3. Analysis time (as stored): 2026-11-06T15:57:30Z. Retrieved (as stored): 2026-11-08T01:29:28Z.

“DHL Captcha”

Registrar
NetherlandsHosting Concepts
Resolved IP
Netherlands78.159.131.55GLOBAL CONNECTIVITY SOLUTIONS LLP
Registered
Nov 5, 2026
First observed
Nov 7, 2026
PhishDestroy assessment Critical
72/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 4/92 Spamhaus DBL: spam domain Young domain: 3 days old
VirusTotal
engine detections ·
OTX
community references
URLScan
engine verdict · score 97
Page captures
open gallery
Domain age
registered 2026-11-05 according to WHOIS
OTX: 3 refs Nov 7, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded mijn-dhl.help on 2026-11-07. Stored VirusTotal result: 4/92 engines flagged. malicious: 1. suspicious: 3. Analysis time (as stored): 2026-11-06T15:57:30Z. Retrieved (as stored): 2026-11-08T01:29:28Z. Risk: critical (72/100). Registrar: Hosting Concepts. Status: Last known active. Hosting: GLOBAL CONNECTIVITY SOLUTIONS LLP. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
4 / 92
Hosting
Netherlands78.159.131.55GLOBAL CONNECTIVITY SOLUTIONS LLP
Registrar
NetherlandsHosting Concepts
Registered
Nov 5, 2026
OTX
3 community refs
Page captures
2

Recorded source summary

PhishDestroy stores a record for mijn-dhl.help. Source observations are dated separately; missing checks do not establish safety.

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidenceVirusTotal 4 / 92 · OTX 3 references 7 sources

VirusTotal

4 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
1
Suspicious
3
Undetected
35

Vendor labels

Fortinet
spam
LevelBlue
suspicious
alphaMountain.ai
spam
Forcepoint ThreatSeeker
phishing

Reputation score

0

Tags

  • dga

Registrar

Hosting Concepts B.V. d/b/a Registrar.eu

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    brett.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    78.159.131.55
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    brett.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    evelyn.ns.cloudflare.com

DNS records observed

JARM fingerprint

3fd3fd15d3fd3fd21c42d42d00000060355a74bb9dbae90657ae903145081f

Certificate

Subject alternative names
  • mijn-dhl.help
Issuer
Let's Encrypt / YR1
Serial
6477ab2bc30d1b11ed1b4549f38368749e5
SHA-256
d9255c4aa46b9eddb9611bd955f00f2006a1ca6dbc9e930eb07e3e6682ea855e
Subject
mijn-dhl.help
Valid until
Valid from

Registration record

Registrar
Hosting Concepts B.V. d/b/a Registrar.eu
Registrar IANA ID
1647
Registrar URL
https://www.openprovider.com/
Registered
Updated
Expires
Status
  • addPeriod
  • clientTransferProhibited
  • serverTransferProhibited
Nameservers
  • brett.ns.cloudflare.com
  • evelyn.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 1,
    "suspicious": 3,
    "undetected": 35
}
Vendor labels
{
    "Fortinet": "spam",
    "LevelBlue": "suspicious",
    "alphaMountain.ai": "spam",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Registrar
Hosting Concepts B.V. d/b/a Registrar.eu
Created
2026-11-05T13:39:52Z
Expires
2027-11-05T23:59:59Z
Updated
2026-11-05T15:53:11Z
First seen
2026-11-05T14:57:42Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "brett.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "78.159.131.55"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "brett.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "evelyn.ns.cloudflare.com"
    }
]
Dns at
2026-11-07T18:38:27Z
Jarm
3fd3fd15d3fd3fd21c42d42d00000060355a74bb9dbae90657ae903145081f
Certificate
{
    "san": [
        "mijn-dhl.help"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "6477ab2bc30d1b11ed1b4549f38368749e5",
    "sha256": "d9255c4aa46b9eddb9611bd955f00f2006a1ca6dbc9e930eb07e3e6682ea855e",
    "subject": "mijn-dhl.help",
    "valid_to": "2027-02-03T12:57:36Z",
    "valid_from": "2026-11-05T12:57:37Z"
}
Registration record
{
    "registrar": "Hosting Concepts B.V. d/b/a Registrar.eu",
    "registrar_iana_id": "1647",
    "registrar_url": "https://www.openprovider.com/",
    "created": "2026-11-05T13:39:52Z",
    "updated": "2026-11-05T13:39:57Z",
    "expires": "2027-11-05T23:59:59Z",
    "status": [
        "addPeriod",
        "clientTransferProhibited",
        "serverTransferProhibited"
    ],
    "nameservers": [
        "brett.ns.cloudflare.com",
        "evelyn.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

source
VirusTotal
scope
unknown
result_state
observed
numerator
4
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","Forcepoint ThreatSeeker","Fortinet","LevelBlue"]
observed_at
2026-11-06 15:57:30
checked_at
2026-11-08 02:29:33
fetched_at
2026-11-08 01:29:33
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Suspicious

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

a4948a21-798d-49f3-ab60-8666306ebba7

Final URL

https://mijn-dhl.help/start.php

HTTP response

404

Redirect type

same-domain

Navigation history

  • URL
    https://mijn-dhl.help/
    Status
    302
  • URL
    https://mijn-dhl.help/start.php
    Status
    404

DOM structure hash

ce746ee6a10ffaf70f80ffefd38e18610f2059125a40e9705b0a985d0332b68f

Document hash

91cb1a13904b718a5f653240be83343bf884c2ae87d5a9a5958804eda8d20c8f

Domain risk categories

  • Newly Seen Domains
  • Security Risks
  • New Domains

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    mijn-dhl.help
    Type
    A
    Value
    78.159.131.55

DNSSEC valid

No

IP address

127.0.1.16

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

Registration record

Registrar
Hosting Concepts B.V. d/b/a Registrar.eu
Registered
Updated
Expires
Nameservers
  • brett.ns.cloudflare.com
  • evelyn.ns.cloudflare.com
Original source fields · JSON
Uuid
a4948a21-798d-49f3-ab60-8666306ebba7
Final url
https://mijn-dhl.help/start.php
Status
404
Redirected
same-domain
History
[
    {
        "url": "https://mijn-dhl.help/",
        "status": 302
    },
    {
        "url": "https://mijn-dhl.help/start.php",
        "status": 404
    }
]
DOM structure hash
ce746ee6a10ffaf70f80ffefd38e18610f2059125a40e9705b0a985d0332b68f
Document hash
91cb1a13904b718a5f653240be83343bf884c2ae87d5a9a5958804eda8d20c8f
Domain risks
[
    "Newly Seen Domains",
    "Security Risks",
    "New Domains"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "mijn-dhl.help",
        "type": "A",
        "value": "78.159.131.55"
    }
]
Dnssec valid
false
Ip
127.0.1.16

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

Registration record
{
    "registrar": "Hosting Concepts B.V. d/b/a Registrar.eu",
    "created": "2026-11-05T13:39:52Z",
    "updated": "2026-11-05T13:39:57Z",
    "expires": "2027-11-05T23:59:59Z",
    "nameservers": [
        "brett.ns.cloudflare.com",
        "evelyn.ns.cloudflare.com"
    ]
}

Spamhaus DBL

spam domain

URLScan

Malicious · engine verdict · score 97

SHA-256 ea11bbd83f07e146debd8895bb46323cfd31dc3725095f7caff262ac291bb052

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a1b047-473b-73f1-b8e6-06a128f306ab

Final URL

https://mijn-dhl.help/start.php

HTTP response

404

Redirect type

same-domain

Redirects

  • To
    https://mijn-dhl.help/
    From
    http://mijn-dhl.help/
    Status
    307
  • To
    https://mijn-dhl.help/start.php
    From
    https://mijn-dhl.help/
    Status
    302

IP address

78.159.131.55

Reverse DNS (PTR)

293297.ip-ptr.tech

Contacted IP addresses

  • 78.159.131.55

Autonomous systems (ASN)

  • 215540

Server countries

  • AL

Linked domains

  • dhl.com

Document hash

e9e4c8c3223a9816696f87ada013194c01728cbd2c4e1ca5e2c05aa9b4816097

Cookies

  • PHPSESSID

TLS session and certificate

Subject alternative names
  • mijn-dhl.help
Cipher
AES_256_GCM
Issuer
YR1
Subject
mijn-dhl.help
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

0

Registered domain age, days

0

Certificate age, days

0

Certificate validity, days

89

Page requests

4

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-2aab354
Score
97
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
Apache/2.4.29 (Ubuntu)
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Uuid
01a1b047-473b-73f1-b8e6-06a128f306ab
Final url
https://mijn-dhl.help/start.php
Status
404
Redirected
same-domain
Redirects
[
    {
        "to": "https://mijn-dhl.help/",
        "from": "http://mijn-dhl.help/",
        "status": 307
    },
    {
        "to": "https://mijn-dhl.help/start.php",
        "from": "https://mijn-dhl.help/",
        "status": 302
    }
]
Ip
78.159.131.55
Ptr
293297.ip-ptr.tech
Contacted IP addresses
[
    "78.159.131.55"
]
Asns
[
    "215540"
]
Countries
[
    "AL"
]
Linked domains
[
    "dhl.com"
]
Document hash
e9e4c8c3223a9816696f87ada013194c01728cbd2c4e1ca5e2c05aa9b4816097
Cookies
[
    "PHPSESSID"
]
Tls
{
    "san": [
        "mijn-dhl.help"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR1",
    "subject": "mijn-dhl.help",
    "protocol": "TLS 1.3",
    "valid_to": "2027-02-03T12:57:36Z",
    "valid_from": "2026-11-05T12:57:37Z"
}
Domain age days
0
Apex age days
0
Tls age days
0
Tls valid days
89
Requests
4
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-2aab354"
        ],
        "score": 97,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Apache/2.4.29 (Ubuntu)",
    "content-type": "text/html; charset=UTF-8"
}
Separate monitor record · 2026-11-08 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a1b047-473b-73f1-b8e6-06a128f306ab
score
0
malicious
false
result_at
2026-11-08T04:30:10Z
enriched_at
2026-11-08T09:13:25Z
source_timestamps
{"urlscan_result_at":"2026-11-08 05:30:10","urlscan_enriched_at":"2026-11-08 10:13:25"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

3 community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

10 / 100 · heuristic score · 1 brand reference · 0 classifications

Open report
Separate monitor score · 10 / 100 · 2026-11-07T23:20:13Z

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
10
analyzed_at
2026-11-07T23:20:13Z
source_timestamp
2026-11-08 00:20:13
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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: 17 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Crawler rules

User agents
  • *
Present
Yes

HTTP response

Reachable
Yes
HTTP status
302
Request timings, ms
DNS
46
TLS
33
Waiting
16
Connection
19
Download
0
Response time, ms
114

TLS connection

ALPN
http/1.1
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
  • 22
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    108.162.194.213
    Host
    evelyn.ns.cloudflare.com
  • IP address
    108.162.193.76
    Host
    brett.ns.cloudflare.com
DNS zone
mijn-dhl.help

Location

IP address
78.159.131.55
ASN
215540
Organization
GLOBAL CONNECTIVITY SOLUTIONS LLP
City
Amsterdam
Country
NL

TLS certificate

Issuer
Let's Encrypt / YR1
Subject
mijn-dhl.help

DNS records

A
  • 78.159.131.55
NS
  • evelyn.ns.cloudflare.com
  • brett.ns.cloudflare.com
SOA
Primary nameserver
brett.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2419372374
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800

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
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
78.159.131.55
IP version
4

Technology stack

Technologies
  • PHP
  • Ubuntu
  • Apache HTTP Server

Registration record

Registrar
Hosting Concepts B.V. d/b/a Registrar.eu
Registered
Updated
Expires
Status
  • serverTransferProhibited https://icann.org/epp
  • clientTransferProhibited https://icann.org/epp
  • addPeriod https://icann.org/epp
Nameservers
  • brett.ns.cloudflare.com
  • evelyn.ns.cloudflare.com

HTTP headers

Response headers
Server
Apache/2.4.29 (Ubuntu)
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true
}
Status
{
    "up": true,
    "code": 302,
    "timings": {
        "dns": 46,
        "tls": 33,
        "wait": 16,
        "connect": 19,
        "download": 0
    },
    "response_ms": 114
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.194.213",
            "host": "evelyn.ns.cloudflare.com"
        },
        {
            "ip": "108.162.193.76",
            "host": "brett.ns.cloudflare.com"
        }
    ],
    "zone": "mijn-dhl.help"
}
Location
{
    "ip": "78.159.131.55",
    "asn": "215540",
    "org": "GLOBAL CONNECTIVITY SOLUTIONS LLP",
    "city": "Amsterdam",
    "country": "NL"
}
Ssl
{
    "issuer": "Let's Encrypt / YR1",
    "subject": "mijn-dhl.help"
}
DNS records
{
    "A": [
        "78.159.131.55"
    ],
    "NS": [
        "evelyn.ns.cloudflare.com",
        "brett.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"brett.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2419372374, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
}
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": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "78.159.131.55",
    "family": 4
}
Tech stack
{
    "technologies": [
        "PHP",
        "Ubuntu",
        "Apache HTTP Server"
    ]
}
Registration record
{
    "registrar": "Hosting Concepts B.V. d/b/a Registrar.eu",
    "created": "2026-11-05T13:39:52Z",
    "updated": "2026-11-05T13:39:57Z",
    "expires": "2027-11-05T23:59:59Z",
    "status": [
        "serverTransferProhibited https://icann.org/epp",
        "clientTransferProhibited https://icann.org/epp",
        "addPeriod https://icann.org/epp"
    ],
    "nameservers": [
        "brett.ns.cloudflare.com",
        "evelyn.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "Apache/2.4.29 (Ubuntu)",
        "content-type": "text/html; charset=UTF-8"
    }
}

Questions about mijn-dhl.help

Is mijn-dhl.help legit?

PhishDestroy rates mijn-dhl.help as critical risk (72/100) from the recorded evidence; it was first recorded on 2026-11-07. Stored VirusTotal result: 4/92 engines flagged. malicious: 1. suspicious: 3. Analysis time (as stored): 2026-11-06T15:57:30Z. Retrieved (as stored): 2026-11-08T01:29:28Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is mijn-dhl.help safe to connect a wallet?

This report does not record which wallet requests mijn-dhl.help 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 mijn-dhl.help?

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

Last checked

Stored Capture · 2 captures

All capture links and hashes (2)
Observed page title
DHL Captcha
Automated brand references
Dhl
TLS Certificate
Issued by YR1 · stored validity ends in 86 days

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 97 report ↗
IP Reputation Netherlands78.159.131.55 abuse score 0/100 0 reports checked Nov 7, 2026
OTX tags 2026-11activeall-domainsblocklistcontentcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Hosting Concepts NL(NL)
RegistrationCreated Nov 5, 2026 (3d · Brand New!) — Expires Nov 5, 2027
Registrant countryMalaysia VirusTotal WHOIS
Registrant1f8f4166599d23ee89c9828fafe4ad7bs@ VirusTotal WHOIS
HTTP Status302 Found (Temporary)
Technical detailsProvenance & timestamps
First DetectedNov 7, 2026
DOM Analysisanalyzed Nov 8, 2026score 10/1001 brand signal
Submitted URLhttps://mijn-dhl.help/start.php
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
Netherlands78.159.131.55
Network ASN
AS215540
AS name
GCS-AS GLOBAL CONNECTIVITY SOLUTIONS LLP, GB
Organization
GLOBAL CONNECTIVITY SOLUTIONS LLP
Observed location
NetherlandsAmsterdam, NL
Server header
Apache/2.4.29 (Ubuntu)

Nameservers 2

  • brett.ns.cloudflare.com
  • evelyn.ns.cloudflare.com

SOA

  • nsname: brett.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2419372374
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
YR1
Valid from
2026-11-05 12:57:37
Valid until
2027-02-03 12:57:36
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintd9255c4aa46b9eddb9611bd955f00f2006a1ca6dbc9e930eb07e3e6682ea855e
Certificate names · 1 SAN
  • mijn-dhl.help

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

Latest Classified Outcome 2026-11-08 11:00:43 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-11-08 11:00:43 UTC
RDAP registration
Observed timeline last reachable: 2026-11-08 11:00:43 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

4 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
Fortinet
LevelBlue
alphaMountain.ai
Forcepoint ThreatSeeker
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of mijn-dhl.help · checked Nov 7, 2026

83
Needs Work
Performance
FCP
3.24 s
First Contentful Paint
LCP
3.69 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
3.24 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 404
Requested URL: https://mijn-dhl.help/start.php
DHL Captcha
Response
HTTP 404
HTML body
437.2 KB
Compressed
55.7 KB
Links
0 internal · 1 external
Detected technologies
vueapache
Selected response headers
Server: Apache/2.4.29 (Ubuntu)
Cache-Control: no-store, no-cache, must-revalidate
Content-Type: text/html; charset=UTF-8
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 7
Cache-Control
no-store, no-cache, must-revalidate
Connection
close
Content-Type
text/html; charset=UTF-8
Date
Sat, 07 Nov 2026 16:28:06 GMT
Expires
Thu, 19 Nov 1981 08:52:00 GMT
Pragma
no-cache
Server
Apache/2.4.29 (Ubuntu)

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

Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

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: 4 SHA-256 hashes: 2 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-11-07 16:38 UTC.

Open this scan on URLScan 01a1b047-473b-73f1-b8e6-06a128f306ab ↗

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. Availability monitor · Recorded state

    redirected

    http_redirect

All retained availability observations6

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_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    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-11-08 12:00:43.000000
    Evidence SHA-256
    0b7d11143929c6692eb4cbfc89c7054085097bcf1d39fc7c042dd4bc3486d9c2
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-11-08 12:00:43
    Evidence reason
    redirect
  2. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    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-11-08 12:00:43.000000
    Evidence SHA-256
    0b7d11143929c6692eb4cbfc89c7054085097bcf1d39fc7c042dd4bc3486d9c2
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-11-08 12:00:43
    Evidence reason
    redirect
  3. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    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-11-08 00:00:51.000000
    Evidence SHA-256
    0da2078f3615fbc15680075825d5da49ff06e0504feb5e1d1c396db0ecfc60dd
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-11-08 00:00:51
    Evidence reason
    redirect
  4. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    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-11-08 00:00:51.000000
    Evidence SHA-256
    0da2078f3615fbc15680075825d5da49ff06e0504feb5e1d1c396db0ecfc60dd
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-11-08 00:00:51
    Evidence reason
    redirect
  5. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-07 23:22:04.326583
    Evidence SHA-256
    19ed99e260d67463304cd035997394a09991119b8c1f635f2967c41ae291fdce
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 23:22:04.326583
    Evidence reason
  6. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    302
    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-11-07 17:39:03.791697
    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 · in progress

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
    mijn-dhl.help detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Automated brand label: DHL · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • Spamhaus DBL
    Spamhaus DBL recorded: spam domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 97
  • 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: 4/92
  • OTX Community References
    Community publication references on AlienVault OTX: 3. References are not vendor verdicts and are excluded from the evidence score.
  • Automated brand label: DHL
    Collector label, not confirmed by a page check.
  • 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 · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. AlienVault OTX

    3 community references

    View source
  2. Added to PhishDestroy

    mijn-dhl.help

    View source
  3. VirusTotal

    4/92 engine detections

    View source
  4. URLScan

    Malicious · engine verdict · score 97

    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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

mijn-dhl.help

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked 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.

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.

Official reporting routes

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.

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 mijn-dhl.help)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

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.

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/mijn-dhl.help"
  title="PhishDestroy threat report for mijn-dhl.help"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>