Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 18/92 engines flagged. malicious: 15. suspicious: 3. Analysis time (as stored): 2026-11-01T17:14:12Z. Retrieved (as stored): 2026-11-04T22:15:54Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
reservation.jndmzp.com favicon

reservation.jndmzp.com

In short

On 2026-05-11, reservation.jndmzp.com displayed a centered loading spinner above the heading "Weiterleitung..." (Redirecting...). The page states in German that planned maintenance work is being carried out on its systems, that the team is working to restore the service as quickly as possible, and that visitors should try again in a few minutes, with an apology for the inconvenience.

“网站正在建设中.”

Review the evidence
Registrar
GMO Internet Group
Resolved IP
United States38.165.94.242PEG Tech Inc · CDN
Registered
Aug 8, 2026
First observed
Nov 4, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 18/92
VirusTotal
18 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 25
Page captures
4
open gallery
Domain age
91 days
registered 2026-08-08 according to WHOIS
Nov 4, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded reservation.jndmzp.com on 2026-11-04. Stored VirusTotal result: 18/92 engines flagged. malicious: 15. suspicious: 3. Analysis time (as stored): 2026-11-01T17:14:12Z. Retrieved (as stored): 2026-11-04T22:15:54Z. Risk: critical (100/100). Registrar: GMO Internet Group. Status: Last known active. Hosting: PEG Tech Inc. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
18 / 92
Hosting
United States38.165.94.242PEG Tech Inc · CDN
Registrar
GMO Internet Group
Registered
Aug 8, 2026
Page captures
4
Page captures Source results Registration record

Capture recorded with this analysis · URLScan · 2026-05-11T14:45:27Z
SHA-256: ee7ea1b1be59d39d65e38ea39cd44f7926115d854d6221a8a9f2097e9ec83f5d

PhishDestroy analysis, reviewed version

On 2026-05-11, reservation.jndmzp.com displayed a centered loading spinner above the heading "Weiterleitung..." (Redirecting...). The page states in German that planned maintenance work is being carried out on its systems, that the team is working to restore the service as quickly as possible, and that visitors should try again in a few minutes, with an apology for the inconvenience.

The stored VirusTotal domain result reports 18 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".

Source evidenceVirusTotal 18 / 92 8 sources

VirusTotal

18 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
42
Malicious
15
Suspicious
3
Undetected
32

Vendor labels

CRDF
malicious
DNS8
suspicious
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
LevelBlue
phishing
Seclookup
malicious
Gridinsoft
suspicious
ADMINUSLabs
malicious
BitDefender
phishing
Chong Lua Dao
malicious
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Tags

  • dga

Registrar

GMO Internet Group, Inc. d/b/a Onamae.com

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    600
    Type
    A
    Value
    38.165.94.242

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • jndmzp.com
  • *.jndmzp.com
Issuer
Google Trust Services / WE1
Serial
1fe470cc6b33df22138f42d948f0fc57
SHA-256
93309306ae93a1f38efac8f52d40a3a045f832b805ef53d21428fc1015223462
Subject
jndmzp.com
Valid until
Valid from

Registration record

Registrar
GMO Internet Group, Inc. d/b/a Onamae.com
Registrar IANA ID
49
Registrar URL
https://internet.gmo/
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • a7.share-dns.com
  • b7.share-dns.net
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 42,
    "malicious": 15,
    "suspicious": 3,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "LevelBlue": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "ADMINUSLabs": "malicious",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Registrar
GMO Internet Group, Inc. d/b/a Onamae.com
Created
2026-08-08T18:14:23Z
Expires
2027-08-08T18:14:23Z
Updated
2026-10-12T12:34:04Z
First seen
2026-05-11T13:22:06Z
DNS records
[
    {
        "ttl": 600,
        "type": "A",
        "value": "38.165.94.242"
    }
]
Dns at
2026-11-03T13:41:20Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "jndmzp.com",
        "*.jndmzp.com"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "1fe470cc6b33df22138f42d948f0fc57",
    "sha256": "93309306ae93a1f38efac8f52d40a3a045f832b805ef53d21428fc1015223462",
    "subject": "jndmzp.com",
    "valid_to": "2026-08-09T08:05:45Z",
    "valid_from": "2026-05-11T07:05:47Z"
}
Registration record
{
    "registrar": "GMO Internet Group, Inc. d/b/a Onamae.com",
    "registrar_iana_id": "49",
    "registrar_url": "https://internet.gmo/",
    "created": "2026-08-08T18:14:23Z",
    "updated": "2026-10-12T12:34:04Z",
    "expires": "2027-08-08T18:14:23Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "a7.share-dns.com",
        "b7.share-dns.net"
    ],
    "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
18
denominator
92
malicious
null
suspicious
null
vendors
["ADMINUSLabs","alphaMountain.ai","BitDefender","Chong Lua Dao","CRDF","CyRadar","DNS8","ESET","Forcepoint ThreatSeeker","Fortinet","G-Data","Gridinsoft","LevelBlue","Lionic","Seclookup","Sophos","VIPRE","Webroot"]
observed_at
2026-11-01 17:14:12
checked_at
2026-11-04 23:15:59
fetched_at
2026-11-04 22:16:00
time_basis
as stored; legacy timezone not established

URLScan

Malicious · engine verdict · score 25

SHA-256 12fbb7279d366ae5e1ff7dd747578cd68032108b790f8e3aaea06d9906324e05

Open report
URLScanOriginal source recordObserved: 17 fields

Observed: · Retrieved:

Report ID

019e177f-f228-766c-a81f-3c84e50b812e

Final URL

https://reservation.jndmzp.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://reservation.jndmzp.com/
    From
    http://reservation.jndmzp.com/
    Status
    307

IP address

104.21.35.113

Contacted IP addresses

  • 104.21.35.113

Autonomous systems (ASN)

  • 13335

Document hash

12fbb7279d366ae5e1ff7dd747578cd68032108b790f8e3aaea06d9906324e05

TLS session and certificate

Subject alternative names
  • jndmzp.com
  • *.jndmzp.com
Cipher
AES_128_GCM
Issuer
WE1
Subject
jndmzp.com
Protocol
QUIC
Valid until
Valid from

Domain age, days

0

Registered domain age, days

1182

Certificate age, days

0

Certificate validity, days

90

Page requests

1

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=63072000; includeSubDomains
Content-security-policy
object-src 'none'; base-uri 'self'; frame-ancestors 'none'; form-action 'self'
X-frame-options
DENY
X-content-type-options
nosniff
Referrer-policy
no-referrer
Permissions-policy
camera=(), microphone=(), geolocation=(), payment=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=()
Priority
u=0,i
Original source fields · JSON
Uuid
019e177f-f228-766c-a81f-3c84e50b812e
Final url
https://reservation.jndmzp.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://reservation.jndmzp.com/",
        "from": "http://reservation.jndmzp.com/",
        "status": 307
    }
]
Ip
104.21.35.113
Contacted IP addresses
[
    "104.21.35.113"
]
Asns
[
    "13335"
]
Document hash
12fbb7279d366ae5e1ff7dd747578cd68032108b790f8e3aaea06d9906324e05
Tls
{
    "san": [
        "jndmzp.com",
        "*.jndmzp.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "jndmzp.com",
    "protocol": "QUIC",
    "valid_to": "2026-08-09T08:05:45Z",
    "valid_from": "2026-05-11T07:05:47Z"
}
Domain age days
0
Apex age days
1182
Tls age days
0
Tls valid days
90
Requests
1
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 25,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=63072000; includeSubDomains",
    "content-security-policy": "object-src 'none'; base-uri 'self'; frame-ancestors 'none'; form-action 'self'",
    "x-frame-options": "DENY",
    "x-content-type-options": "nosniff",
    "referrer-policy": "no-referrer",
    "permissions-policy": "camera=(), microphone=(), geolocation=(), payment=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=()",
    "priority": "u=0,i"
}

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 1 field

Observed: · Retrieved:

Report ID

af4ac4bc-0237-487b-958d-9db730b959e2
Original source fields · JSON
Uuid
af4ac4bc-0237-487b-958d-9db730b959e2

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

0 / 100 · heuristic score · 0 brand references · 0 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
reservation.jndmzp.com: Recorded German maintenance redirect notice
ai_description
PhishDestroy records reservation.jndmzp.com showing a German-language redirect notice stating planned maintenance is underway on its systems.
ai_summary
On 2026-05-11, reservation.jndmzp.com displayed a centered loading spinner above the heading "Weiterleitung..." (Redirecting...). The page states in German that planned maintenance work is being carried out on its systems, that the team is working to restore the service as quickly as possible, and that visitors should try again in a few minutes, with an apology for the inconvenience. The stored VirusTotal domain result reports 18 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-04 23:23:34
revision
c24f3f6f0c9e7cd04e4de19136153f4a35e70e093253a328e89099f932a82740
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 8 fields

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Ports

Open ports
  • 80

DNS servers

Nameservers
  • IP address
    172.64.53.25
    Host
    a.share-dns.com
  • IP address
    162.159.27.88
    Host
    b.share-dns.net
DNS zone
jndmzp.com

Location

IP address
38.165.94.242
ASN
54600
Organization
PEG Tech Inc
City
San Jose
Country
US

DNS records

A
  • 38.165.94.242

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
38.165.94.242
IP version
4

Registration record

Registrar
GMO Internet Group, Inc. d/b/a Onamae.com
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • a7.share-dns.com
  • b7.share-dns.net
Original source fields · JSON
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Ports
{
    "open": [
        80
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.53.25",
            "host": "a.share-dns.com"
        },
        {
            "ip": "162.159.27.88",
            "host": "b.share-dns.net"
        }
    ],
    "zone": "jndmzp.com"
}
Location
{
    "ip": "38.165.94.242",
    "asn": "54600",
    "org": "PEG Tech Inc",
    "city": "San Jose",
    "country": "US"
}
DNS records
{
    "A": [
        "38.165.94.242"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "38.165.94.242",
    "family": 4
}
Registration record
{
    "registrar": "GMO Internet Group, Inc. d/b/a Onamae.com",
    "created": "2026-08-08T18:14:23Z",
    "updated": "2026-10-12T12:34:04Z",
    "expires": "2027-08-08T18:14:23Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "a7.share-dns.com",
        "b7.share-dns.net"
    ]
}

Questions about reservation.jndmzp.com

Is reservation.jndmzp.com legit?

PhishDestroy rates reservation.jndmzp.com as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-11-04. Stored VirusTotal result: 18/92 engines flagged. malicious: 15. suspicious: 3. Analysis time (as stored): 2026-11-01T17:14:12Z. Retrieved (as stored): 2026-11-04T22:15:54Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is reservation.jndmzp.com safe to connect a wallet?

This report does not record which wallet requests reservation.jndmzp.com 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 reservation.jndmzp.com?

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

Explore

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

Checked, no match

Last checked

Stored Capture · 4 captures

URLScan · 2026-05-11 1 / 4 Used in the analysis Source file SHA-256: ee7ea1b1be59d39d65e38ea39cd44f7926115d854d6221a8a9f2097e9ec83f5d SHA-256 of the prepared copy given to the model: c57974148b13738f489f65ca9b4f9d5b0d1fa26e369fbcbd18df56334dc1c163
SourceURLScan · 2026-05-11
Recorded
StateStored capture
HTTP status200
Final URLhttps://reservation.jndmzp.com/
Position1 / 4
Open capture Source Report Wayback Download
All capture links and hashes (4)

Domain details

Domain
IP Context United States38.165.94.242 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) GMO Internet Group
Abuse contact["abuse@internet.gmo"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for jndmzp.com →
Registration (base domain)jndmzp.com · Created Aug 8, 2026 (91d) — Expires Aug 8, 2027
WHOIS statusclientTransferProhibited
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 4, 2026
DOM Analysisanalyzed Nov 4, 2026score 0/100
Submitted URLhttp://reservation.jndmzp.com/
Observed page title
网站正在建设中.
TLS Certificate
Issued by Google Trust Services / WE1

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States38.165.94.242
Network ASN
AS54600
Organization
PEG Tech Inc
Observed location
United StatesSan Jose, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • a7.share-dns.com
  • b7.share-dns.net

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-05-11 07:05:47
Valid until
2026-08-09 08:05:45
Hostname coverage
Stored certificate expired or unverified
Validity
Stored certificate expired
Collection source
PhishDestroy collector
Certificate fingerprint93309306ae93a1f38efac8f52d40a3a045f832b805ef53d21428fc1015223462
Certificate names · 2 SANs
  • jndmzp.com
  • *.jndmzp.com

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

viewdns.info · 38.165.94.242rapiddns.io

Latest Classified Outcome 2026-11-07 11:13:16 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-07 11:13:16 UTC
RDAP registration
Observed timeline last reachable: 2026-11-07 11:13:16 UTC last content: 2026-11-07 11:13:16 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

18 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
CRDF
DNS8
ESET
VIPRE
G-Data
Lionic
Sophos
CyRadar
Webroot
Fortinet
LevelBlue
Seclookup
Gridinsoft
ADMINUSLabs
BitDefender
Chong Lua Dao
alphaMountain.ai
Forcepoint ThreatSeeker
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://reservation.jndmzp.com/
网站正在建设中.
Response
HTTP 200
HTML body
6.9 KB
Compressed
1.9 KB
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Content-Type: text/html; charset=UTF-8
Content-Encoding: gzip
Server: Nginx Microsoft-HTTPAPI/2.0
X-Powered-By: Nginx
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 6
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Wed, 04 Nov 2026 20:53:32 GMT
Server
Nginx Microsoft-HTTPAPI/2.0
Transfer-Encoding
chunked
X-Powered-By
Nginx

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

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content 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: 1 SHA-256 hashes: 1 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-04 22:18 UTC.

Open this scan on URLScan 019e177f-f228-766c-a81f-3c84e50b812e ↗

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

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

Separate monitor HTTP observation

Source: domain_monitor. This stored snapshot does not establish current availability.

Observed · UTC
Recorded HTTP status
200
Probe value as recorded
200
Original source timestamp
2026-11-02 16:28:20
All retained availability observations12

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_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 12:13:16.000000
    Evidence SHA-256
    8e720f8543cfdcbe19ec134ad7cdde136d423135d3ac7189b53e7ffd0647e8d3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 12:13:16
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 12:13:16.000000
    Evidence SHA-256
    8e720f8543cfdcbe19ec134ad7cdde136d423135d3ac7189b53e7ffd0647e8d3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 12:13:16
    Evidence reason
    alive_content
  3. current_http_probeunknown
    Observation source
    current_http_probe
    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 03:52:06.000000
    Evidence SHA-256
    fc26fc16988f1de062a24f856b0c63f2065d6f44362ea52f7da9f86c70789457
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 03:52:06
    Evidence reason
    unavailable
  4. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 03:52:06.000000
    Evidence SHA-256
    fc26fc16988f1de062a24f856b0c63f2065d6f44362ea52f7da9f86c70789457
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 03:52:06
    Evidence reason
    unavailable
  5. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 00:04:20.000000
    Evidence SHA-256
    23bef1777c266f00551e8e90af3b21a0decc6b157f699261c3629d84744d07ce
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 00:04:20
    Evidence reason
    alive_content
  6. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 00:04:20.000000
    Evidence SHA-256
    23bef1777c266f00551e8e90af3b21a0decc6b157f699261c3629d84744d07ce
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 00:04:20
    Evidence reason
    alive_content
  7. 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-06 23:21:40.556826
    Evidence SHA-256
    2071dfbc1c6ae55fbd72318bd0bd5b8ac6720ae3a22d4fd33ac3fef7bf7b47da
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-06 23:21:40.556826
    Evidence reason
  8. 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-05 23:21:20.401484
    Evidence SHA-256
    6561edb8793c530bd35b9930c0ef92bee67e8e1395a2c6e53ebfe984a32e4303
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-05 23:21:20.401484
    Evidence reason
  9. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-05 03:29:04.000000
    Evidence SHA-256
    62fe7364639657e360f58b1c7dd1aa1f73a7e843cbd4b8d6fecd50d075fd2b82
    Evidence timestamp as recorded
    2026-11-05 03:29:04
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  10. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-05 03:29:04.000000
    Evidence SHA-256
    8e6b2c15821a89f72745e2fbebf7b6976b8489c226677e7e6c1bfbf72dc3573a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-05 03:29:04
    Evidence reason
    unavailable
  11. 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-04 23:21:01.569244
    Evidence SHA-256
    23fc21981d3f4a4c85bb59e9f7d4d9f56b19dcaacedad495e573240b5ed9121e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-04 23:21:01.569244
    Evidence reason
  12. 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-11-04 23:20:10.925321
    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: 8. 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
    reservation.jndmzp.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 6 of 6
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 25
  • 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: 18/92
  • 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

3 entries
  1. Added to PhishDestroy

    reservation.jndmzp.com

    View source
  2. VirusTotal

    18/92 engine detections

    View source
  3. URLScan

    Malicious · engine verdict · score 25

    View source
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation
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.

reservation.jndmzp.com

Evidence & External Reports

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

Were You Affected by This Site?

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

Immediate steps Find reporting contacts

Official reporting routes

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

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

IdentityTheft.gov United States

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

CISA United States

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

CSIRTs Network European Union

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

FIRST Worldwide

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

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

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

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

Report to Your Local Authorities

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

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

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

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

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

What information should I collect for my report?

FBI guidelines

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

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including reservation.jndmzp.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

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

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

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

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

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

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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/reservation.jndmzp.com"
  title="PhishDestroy threat report for reservation.jndmzp.com"
  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>