Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 16. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
jorquex.cc favicon

jorquex.cc

In short

The captured jorquex.cc page presents itself as Pevsuki, a shopping storefront whose hero banner advertises a MEGA SALE with the line "Amazing Deals on Everyday Items" and a prominent Order Now button. Above it, a strip reads "We Free Shipping Worldwide," while a search field, account and cart icons, and category links for Home, Woman, New, Tops, Dresses and Sale sit in the header. Below the banner, a Top Recommended section shows product tiles carrying 56% OFF and 54% OFF badges, and a small "Trusted Store" badge appears at the lower right.

“Pevsuki”

Review the evidence
Registrar
United StatesDynadot
Resolved IP
United States47.89.246.240Alibaba Cloud LLC
Registered
Apr 3, 2026
First observed
Oct 29, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 16/92 Spamhaus DBL: phishing domain
VirusTotal
16 / 92
engine detections ·
OTX
5
community references
URLScan
Malicious
engine verdict · score 77
Cloudflare Radar
Phishing
Page captures
8
open gallery
Domain age
212 days
registered 2026-04-03 according to WHOIS · source data differ
OTX: 5 refs Oct 29, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded jorquex.cc on 2026-10-29. VirusTotal: 16/92 engines flag it. Listed on Spamhaus DBL. Risk: critical (100/100). Registrar: Dynadot. Status: Last known active. Hosting: Alibaba Cloud LLC. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
16 / 92
Hosting
United States47.89.246.240Alibaba Cloud LLC
Registrar
United StatesDynadot
Registered
Apr 3, 2026
OTX
5 community refs
Page captures
8
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured jorquex.cc page presents itself as Pevsuki, a shopping storefront whose hero banner advertises a MEGA SALE with the line "Amazing Deals on Everyday Items" and a prominent Order Now button. Above it, a strip reads "We Free Shipping Worldwide," while a search field, account and cart icons, and category links for Home, Woman, New, Tops, Dresses and Sale sit in the header. Below the banner, a Top Recommended section shows product tiles carrying 56% OFF and 54% OFF badges, and a small "Trusted Store" badge appears at the lower right.

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

Source evidenceVirusTotal 16 / 92 · OTX 5 references 8 sources

VirusTotal

16 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
43
Malicious
11
Suspicious
5
Undetected
33

Vendor labels

CRDF
malicious
DNS8
suspicious
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
Fortinet
spam
Netcraft
malicious
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
suspicious
BitDefender
phishing
alphaMountain.ai
suspicious
Forcepoint ThreatSeeker
phishing

Reputation score

0

Registrar

Dynadot Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    NS
    Value
    ns1.dyna-ns.net
  • TTL, seconds
    300
    Type
    A
    Value
    47.89.246.240
  • TTL, seconds
    300
    Type
    SOA
    Responsible mailbox
    hostmaster.jorquex.cc
    Value
    ns1.dyna-ns.net
  • TTL, seconds
    300
    Type
    NS
    Value
    ns2.dyna-ns.net

DNS records observed

JARM fingerprint

15d3fd16d29d29d00042d43d00000041ad16ead50175e1e575f5579aa6b5c8

Certificate

Subject alternative names
  • jorquex.cc
Issuer
Let's Encrypt / YR2
Serial
54fb8516dd4863ef060649fdefe912e5e6
SHA-256
1fa4d635f931278d3e55513f2f0bddad0babc3cc4625c9e37cc515138da9d27d
Subject
jorquex.cc
Valid until
Valid from

Registration record

Registrar
Dynadot Inc
Registrar IANA ID
472
Registrar URL
http://www.dynadot.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net
DNSSEC
unsigned

Registry data (RDAP)

Status
  • transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 43,
    "malicious": 11,
    "suspicious": 5,
    "undetected": 33
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Fortinet": "spam",
    "Netcraft": "malicious",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "suspicious",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
Dynadot Inc
Created
2026-04-03T08:55:20Z
Expires
2027-04-03T08:55:20Z
Updated
2026-04-03T08:55:31Z
First seen
2026-05-12T02:19:47Z
DNS records
[
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "47.89.246.240"
    },
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "hostmaster.jorquex.cc",
        "value": "ns1.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.dyna-ns.net"
    }
]
Dns at
2026-10-23T06:15:34Z
Jarm
15d3fd16d29d29d00042d43d00000041ad16ead50175e1e575f5579aa6b5c8
Certificate
{
    "san": [
        "jorquex.cc"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "54fb8516dd4863ef060649fdefe912e5e6",
    "sha256": "1fa4d635f931278d3e55513f2f0bddad0babc3cc4625c9e37cc515138da9d27d",
    "subject": "jorquex.cc",
    "valid_to": "2026-11-12T02:31:41Z",
    "valid_from": "2026-08-14T02:31:42Z"
}
Registration record
{
    "registrar": "Dynadot Inc",
    "registrar_iana_id": "472",
    "registrar_url": "http://www.dynadot.com",
    "created": "2026-04-03T08:55:20Z",
    "updated": "2026-04-03T08:55:31Z",
    "expires": "2027-04-03T08:55:20Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-04-03T08:55:20Z",
        "last changed": "2026-08-14T03:13:37Z",
        "registration": "2026-04-03T08:55:20Z",
        "registrar expiration": "2027-04-03T08:55:20Z",
        "last update of RDAP database": "2026-10-22T08:22:51Z"
    }
}
Separate source record · 11 malicious + 5 suspicious / 92 · 2026-10-23 06:10:11 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-23T06:10:11Z
fetched_at
2026-10-29T23:15:41Z
stats
{"timeout":0,"harmless":43,"malicious":11,"suspicious":5,"undetected":33}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

beba01b0-ad8e-4fa7-823a-c47e6ea25917

Final URL

https://jorquex.cc/

HTTP response

200

Navigation history

  • URL
    https://jorquex.cc/
    Status
    200

DOM structure hash

420191324e6ddbdea35ab03c94c04176df23c2d74f4404c11356e8ad609300f0

Document hash

3c47858b40dab249d7a46efd683c0c5b7ae0acd61bac4c5d3a3c25b8f8ca7b4b

Phishing classifier result

  • phishing

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    jorquex.cc
    Type
    A
    Value
    47.89.246.240

DNSSEC valid

No

IP address

127.0.1.18

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

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Nameservers
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net
Original source fields · JSON
Uuid
beba01b0-ad8e-4fa7-823a-c47e6ea25917
Final url
https://jorquex.cc/
Status
200
History
[
    {
        "url": "https://jorquex.cc/",
        "status": 200
    }
]
DOM structure hash
420191324e6ddbdea35ab03c94c04176df23c2d74f4404c11356e8ad609300f0
Document hash
3c47858b40dab249d7a46efd683c0c5b7ae0acd61bac4c5d3a3c25b8f8ca7b4b
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "jorquex.cc",
        "type": "A",
        "value": "47.89.246.240"
    }
]
Dnssec valid
false
Ip
127.0.1.18

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

Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-04-03T08:55:20Z",
    "updated": "2026-04-03T08:55:31Z",
    "expires": "2027-04-03T08:55:20Z",
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ]
}

Spamhaus DBL

phishing domain

URLScan

Malicious · engine verdict · score 77

SHA-256 18fad9790f7f2cc71b92e785e2960561f7108c520ee0807e794194e13b121765

Open report
URLScanOriginal source recordObserved: 18 fields

Observed: · Retrieved:

Report ID

01a189b9-02f9-729a-b15d-fe8f72cf7b6c

Final URL

https://jorquex.cc/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://jorquex.cc/
    From
    http://jorquex.cc/
    Status
    307

IP address

47.89.246.240

Contacted IP addresses

  • 47.89.246.240

Autonomous systems (ASN)

  • 45102

Server countries

  • US

Document hash

6c5d74593398868b7285edba64f53c5db909a6fd2cf4052b5a617609d3b62b5d

TLS session and certificate

Subject alternative names
  • jorquex.cc
Cipher
AES_128_GCM
Issuer
YR2
Subject
jorquex.cc
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

170

Differs from the registration date in WHOIS (2026-04-03), which gives 209 days on the scan date 2026-10-29. The two sources disagree; both values are kept as recorded.

Registered domain age, days

170

Differs from the registration date in WHOIS (2026-04-03), which gives 209 days on the scan date 2026-10-29. The two sources disagree; both values are kept as recorded.

Certificate age, days

76

Certificate validity, days

89

Page requests

2

Provider verdicts

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

HTTP headers

Server
nginx
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
01a189b9-02f9-729a-b15d-fe8f72cf7b6c
Final url
https://jorquex.cc/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://jorquex.cc/",
        "from": "http://jorquex.cc/",
        "status": 307
    }
]
Ip
47.89.246.240
Contacted IP addresses
[
    "47.89.246.240"
]
Asns
[
    "45102"
]
Countries
[
    "US"
]
Document hash
6c5d74593398868b7285edba64f53c5db909a6fd2cf4052b5a617609d3b62b5d
Tls
{
    "san": [
        "jorquex.cc"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR2",
    "subject": "jorquex.cc",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-12T02:31:41Z",
    "valid_from": "2026-08-14T02:31:42Z"
}
Domain age days
170

Differs from the registration date in WHOIS (2026-04-03), which gives 209 days on the scan date 2026-10-29. The two sources disagree; both values are kept as recorded.

Apex age days
170

Differs from the registration date in WHOIS (2026-04-03), which gives 209 days on the scan date 2026-10-29. The two sources disagree; both values are kept as recorded.

Tls age days
76
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 77,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html; charset=utf-8"
}
Separate monitor record · 2026-10-30 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a189b9-02f9-729a-b15d-fe8f72cf7b6c
score
0
malicious
false
result_at
2026-10-30T04:30:18Z
enriched_at
2026-10-30T09:10:47Z
source_timestamps
{"urlscan_result_at":"2026-10-30 05:30:18","urlscan_enriched_at":"2026-10-30 10:10:47"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

5 community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 0 / 100 · 2026-10-29T23:17:25Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
0
analyzed_at
2026-10-29T23:17:25Z
source_timestamp
2026-10-30 00:17:25
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
jorquex.cc Pevsuki mega sale shopping page
ai_description
PhishDestroy records the jorquex.cc page titled Pevsuki, a storefront promoting a mega sale with an Order Now call to action.
ai_summary
The captured jorquex.cc page presents itself as Pevsuki, a shopping storefront whose hero banner advertises a MEGA SALE with the line "Amazing Deals on Everyday Items" and a prominent Order Now button. Above it, a strip reads "We Free Shipping Worldwide," while a search field, account and cart icons, and category links for Home, Woman, New, Tops, Dresses and Sale sit in the header. Below the banner, a Top Recommended section shows product tiles carrying 56% OFF and 54% OFF badges, and a small "Trusted Store" badge appears at the lower right. The stored VirusTotal domain result reports 16 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-30 00:16:01
revision
b6579245e1b647a5938c9683dfafcd250e9c5f5a031d1899969410a9e0c17912
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: 23 fields

Mail configuration

SPF lookups
0

CAA records

Domain
jorquex.cc

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Page title and metadata

Page title
500 Internal Server Error
Indexing directives
noindex, nofollow

Trackers

Requests
61
Observed services
  • Name
    Facebook
    Company
    Meta
    Country
    US
    Category
    Advertising
    Requests
    15
  • Name
    Google Translate
    Company
    Google
    Country
    US
    Category
    Customer Interaction
    Requests
    1
  • Name
    Amazon CloudFront
    Company
    Amazon
    Country
    US
    Category
    Hosting
    Requests
    7
  • Name
    Google APIs
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    5
  • Name
    Facebook Connect
    Company
    Meta
    Country
    US
    Category
    Site Analytics
    Requests
    15

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
253
TLS
162
Waiting
178
Connection
162
Download
0
Response time, ms
755

TLS connection

ALPN
http/1.1
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
219
CO₂, grams
0
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    162.159.27.158
    Host
    ns1.dyna-ns.net
  • IP address
    162.159.24.5
    Host
    ns2.dyna-ns.net
DNS zone
jorquex.cc

Cookies

Cookies
  • Name
    _fbp
  • Name
    _bbiafh_vid
  • Name
    _bbiafh_cvid
  • Name
    _bbiafh_vs
  • Name
    utm_source
  • Name
    utm_medium
  • Name
    order_utm_history
  • Name
    landing_page
  • Name
    _bbiafh_ka
  • Name
    first_http_referer
  • Name
    first_visit_time
  • Name
    currency_code
    Session cookie
    Yes
  • Name
    PHPSESSID
    Session cookie
    Yes
  • Name
    _BAIHZAD_ua
    Secure
    Yes
    SameSite
    None
  • Name
    _BAIHZAD_pu
    Secure
    Yes
    SameSite
    None
  • Name
    _BAIHZAD_tz
    Secure
    Yes
    SameSite
    None
  • Name
    _BAIHZAD_ss
    Secure
    Yes
    SameSite
    None
  • Name
    _BAIHZAD_lang
    Secure
    Yes
    SameSite
    None
  • Name
    _BAIHZAD_vs
    Secure
    Yes
    SameSite
    None
  • Name
    _BAIHZAD_dt
    Secure
    Yes
    SameSite
    None

Location

IP address
47.89.246.240
ASN
45102
Organization
Alibaba Cloud LLC
City
Minkler
Country
US

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
jorquex.cc

DNS records

A
  • 47.89.246.240
NS
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net
SOA
Primary nameserver
ns1.dyna-ns.net
Hostmaster
hostmaster.jorquex.cc
Serial
2026081301
Refresh, seconds
16384
Retry, seconds
2048
Expiry, seconds
1209600
Minimum TTL, seconds
300

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
47.89.246.240
IP version
4

Redirects

Redirect chain
  • https://jorquex.cc

Subdomains

Count
1
Subdomains
  • www.jorquex.cc

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

HTTP headers

Response headers
Server
nginx
Content-type
text/html; charset=utf-8
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "jorquex.cc"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Page title and metadata
{
    "title": "500 Internal Server Error",
    "robots": "noindex, nofollow"
}
Trackers
{
    "requests": 61,
    "trackers": [
        {
            "name": "Facebook",
            "company": "Meta",
            "country": "US",
            "category": "Advertising",
            "requests": 15
        },
        {
            "name": "Google Translate",
            "company": "Google",
            "country": "US",
            "category": "Customer Interaction",
            "requests": 1
        },
        {
            "name": "Amazon CloudFront",
            "company": "Amazon",
            "country": "US",
            "category": "Hosting",
            "requests": 7
        },
        {
            "name": "Google APIs",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 5
        },
        {
            "name": "Facebook Connect",
            "company": "Meta",
            "country": "US",
            "category": "Site Analytics",
            "requests": 15
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 253,
        "tls": 162,
        "wait": 178,
        "connect": 162,
        "download": 0
    },
    "response_ms": 755
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 219,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.27.158",
            "host": "ns1.dyna-ns.net"
        },
        {
            "ip": "162.159.24.5",
            "host": "ns2.dyna-ns.net"
        }
    ],
    "zone": "jorquex.cc"
}
Cookies
{
    "cookies": [
        {
            "name": "_fbp"
        },
        {
            "name": "_bbiafh_vid"
        },
        {
            "name": "_bbiafh_cvid"
        },
        {
            "name": "_bbiafh_vs"
        },
        {
            "name": "utm_source"
        },
        {
            "name": "utm_medium"
        },
        {
            "name": "order_utm_history"
        },
        {
            "name": "landing_page"
        },
        {
            "name": "_bbiafh_ka"
        },
        {
            "name": "first_http_referer"
        },
        {
            "name": "first_visit_time"
        },
        {
            "name": "currency_code",
            "session": true
        },
        {
            "name": "PHPSESSID",
            "session": true
        },
        {
            "name": "_BAIHZAD_ua",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BAIHZAD_pu",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BAIHZAD_tz",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BAIHZAD_ss",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BAIHZAD_lang",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BAIHZAD_vs",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BAIHZAD_dt",
            "secure": true,
            "same_site": "None"
        }
    ]
}
Location
{
    "ip": "47.89.246.240",
    "asn": "45102",
    "org": "Alibaba Cloud LLC",
    "city": "Minkler",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "jorquex.cc"
}
DNS records
{
    "A": [
        "47.89.246.240"
    ],
    "NS": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ],
    "SOA": "{\"nsname\": \"ns1.dyna-ns.net\", \"hostmaster\": \"hostmaster.jorquex.cc\", \"serial\": 2026081301, \"refresh\": 16384, \"retry\": 2048, \"expire\": 1209600, \"minttl\": 300}"
}
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": "47.89.246.240",
    "family": 4
}
Redirects
{
    "chain": [
        "https://jorquex.cc"
    ]
}
Subdomains
{
    "count": 1,
    "subdomains": [
        "www.jorquex.cc"
    ]
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-04-03T08:55:20Z",
    "updated": "2026-04-03T08:55:31Z",
    "expires": "2027-04-03T08:55:20Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html; charset=utf-8"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware Security threats Malware
View full Cloudflare Radar report

Questions about jorquex.cc

Is jorquex.cc legit?

PhishDestroy rates jorquex.cc as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-10-29. VirusTotal: 16/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is jorquex.cc safe to connect a wallet?

This report does not record which wallet requests jorquex.cc 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 jorquex.cc?

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 · 8 captures

Cloudflare Radar 1 / 8 Used in the analysis Source file SHA-256: a8d441eeab9926aef2ec25301d395997f0f7df17c666dd9b530d492ee7e29a8b SHA-256 of the prepared copy given to the model: 485634e6c238545008e7a9150cf8adf3947e9fff8ca6a0378a5bcc6fd5033725
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://jorquex.cc/
Position1 / 8
Open capture Source Report Wayback Download
All capture links and hashes (8)
jorquex.cc: caution — Flagged by Spamhaus DBL, 16/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card jorquex.cc: caution — Flagged by Spamhaus DBL, 16/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 49d8975b8d8d

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 77 report ↗
IP Reputation United States47.89.246.240 abuse score 0/100 0 reports checked Oct 30, 2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
Abuse contactabuse@dynadot.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for jorquex.cc →
RegistrationCreated Apr 3, 2026 (212d) — Expires Apr 3, 2027
WHOIS statusclientTransferProhibited
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 29, 2026
DOM Analysisanalyzed Oct 30, 2026score 0/100
Submitted URLhttp://jorquex.cc/
Favicon Hash
Observed page title
Pevsuki
TLS Certificate
Issued by YR2 · stored validity ends in 10 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States47.89.246.240
Network ASN
AS45102
AS name
ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN
Organization
Alibaba Cloud LLC
Observed location
United StatesMinkler, US
Server header
nginx

Nameservers 2

  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

SOA

  • nsname: ns1.dyna-ns.net
  • hostmaster: hostmaster.jorquex.cc
  • serial: 2026081301
  • refresh: 16384
  • retry: 2048
  • expire: 1209600
  • minttl: 300

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
YR2
Valid from
2026-08-14 02:31:42
Valid until
2026-11-12 02:31:41
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint1fa4d635f931278d3e55513f2f0bddad0babc3cc4625c9e37cc515138da9d27d
Certificate names · 1 SAN
  • jorquex.cc

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

viewdns.info · 47.89.246.240rapiddns.io

Latest Classified Outcome 2026-11-01 11:05:41 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-01 11:05:41 UTC
RDAP registration
Observed timeline last reachable: 2026-11-01 11:05:41 UTC last content: 2026-11-01 11:05:41 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.
Recorded subdomains1

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

  • www.jorquex.ccDomain record
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

16 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 16 detections
alphaMountain.ai
BitDefender
CRDF
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Netcraft
Seclookup
SOCRadar
Sophos
VIPRE
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://jorquex.cc/
Final URL: https://jorquex.cc/
Pevsuki
Pevsuki
Response
HTTP 200
HTML body
548.3 KB
Compressed
90.2 KB
Links
112 internal · 0 external
Detected technologies
vuenginx
Selected response headers
Server: nginx
Content-Type: text/html; charset=utf-8
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Open Graph title: Pevsuki
Open Graph description: Pevsuki
Twitter card: summary_large_image
Saved response-header values · 9
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Thu, 29 Oct 2026 22:15:26 GMT
Execution-Time
0.0804870129
Server
nginx
Transfer-Encoding
chunked
Vary
Accept-Encoding
x-trace-id
404D644A-8ABE-143A-36B1-0CB807C5D1AC

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: 2 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-10-29 22:15 UTC.

Open this scan on URLScan 01a189b9-02f9-729a-b15d-fe8f72cf7b6c ↗

Stored observation history4

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

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Domain monitor · First collection record

    Reachable

All retained availability observations18

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-01 12:05:41.000000
    Evidence SHA-256
    a03fc9f1ea9ded972da122dd9d987ccb629a19402eeb2286a68eb3d9841ba78f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:05:41
    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-01 12:05:41.000000
    Evidence SHA-256
    a03fc9f1ea9ded972da122dd9d987ccb629a19402eeb2286a68eb3d9841ba78f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:05:41
    Evidence reason
    alive_content
  3. 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-01 03:49:07.000000
    Evidence SHA-256
    05e5e30bd8a9c27accf9e008626ed3592c40dd5ee99c331fcf9b6d186d1af998
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:49:07
    Evidence reason
    alive_content
  4. 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-01 03:49:07.000000
    Evidence SHA-256
    05e5e30bd8a9c27accf9e008626ed3592c40dd5ee99c331fcf9b6d186d1af998
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:49:07
    Evidence reason
    alive_content
  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-01 00:04:05.000000
    Evidence SHA-256
    f9f61c484253dd3f30562193e64ba55a6fc5049cb7320781f68b7e4809bff86e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:04:05
    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-01 00:04:05.000000
    Evidence SHA-256
    f9f61c484253dd3f30562193e64ba55a6fc5049cb7320781f68b7e4809bff86e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:04:05
    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-10-31 23:20:09.600237
    Evidence SHA-256
    fdac094cb4b92350d9f20b2c0fc69fdcaa33e7da7eb2d1063ea3f2bc257f29ef
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:20:09.600237
    Evidence reason
  8. 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-10-31 12:04:26.000000
    Evidence SHA-256
    79eceb7d65a65e64a917444a0c07446647a55b667ceb7c1c9b84e3198f18adac
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:04:26
    Evidence reason
    alive_content
  9. 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-10-31 12:04:26.000000
    Evidence SHA-256
    79eceb7d65a65e64a917444a0c07446647a55b667ceb7c1c9b84e3198f18adac
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:04:26
    Evidence reason
    alive_content
  10. 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-10-31 00:58:07.000000
    Evidence SHA-256
    c3849a397b499226a6fd3c6ea0bef6401ddcd2e6ec8cd39115efaa0dd0f3f648
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:58:07
    Evidence reason
    alive_content
  11. 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-10-31 00:58:07.000000
    Evidence SHA-256
    c3849a397b499226a6fd3c6ea0bef6401ddcd2e6ec8cd39115efaa0dd0f3f648
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:58:07
    Evidence reason
    alive_content
  12. 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-10-30 22:35:15.875079
    Evidence SHA-256
    97b1f1aad91757df55a07aa8eadffa1ea48bf460a07a53a1e786c935a601fca5
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 22:35:15.875079
    Evidence reason
  13. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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-10-30 13:10:28.000000
    Evidence SHA-256
    08b7d0d47816078d3e3373ef7ef91e15e608fb685e2f82ed46c303bd88ec6ee9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 13:10:28
    Evidence reason
    alive_content
  14. 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-10-30 13:10:28.000000
    Evidence SHA-256
    08b7d0d47816078d3e3373ef7ef91e15e608fb685e2f82ed46c303bd88ec6ee9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 13:10:28
    Evidence reason
    alive_content
  15. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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-10-30 01:23:55.000000
    Evidence SHA-256
    a58f7b7e87a0eabdbbced65b526504eaa94eaa53fc3bd2988a1d253f7ee58fc1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 01:23:55
    Evidence reason
    alive_content
  16. 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-10-30 01:23:55.000000
    Evidence SHA-256
    a58f7b7e87a0eabdbbced65b526504eaa94eaa53fc3bd2988a1d253f7ee58fc1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 01:23:55
    Evidence reason
    alive_content
  17. 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-29 23:14:44.000000
    Evidence SHA-256
    e763ee218ae89421d253143a18e2474ea1d21c49edb5e62ae74d58812fd4b221
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 23:14:44
    Evidence reason
  18. 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-29 23:14:44.000000
    Evidence SHA-256
    e763ee218ae89421d253143a18e2474ea1d21c49edb5e62ae74d58812fd4b221
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 23:14:44
    Evidence reason

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
    jorquex.cc detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • Spamhaus DBL
    Spamhaus DBL recorded: phishing domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 77
  • 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: 16/92
  • OTX Community References
    Community publication references on AlienVault OTX: 5. References are not vendor verdicts and are excluded from the evidence score.
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as Malware, Security threats
  • 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

5 entries
  1. AlienVault OTX

    5 community references

    View source
  2. Cloudflare Radar

    Phishing

    View source
  3. Added to PhishDestroy

    jorquex.cc

    View source
  4. URLScan

    Page captured

    View source
  5. VirusTotal

    16/92 engine detections

    View source
How we investigate & report

Public scans, evidence and abuse channels

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

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

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

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

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

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

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

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

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

Check for cloaking

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

jorquex.cc

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 16 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Malicious OTX 5 refs 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?

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.

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 jorquex.cc)
  • 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/jorquex.cc"
  title="PhishDestroy threat report for jorquex.cc"
  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>