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

juangcuan.com

In short

PhishDestroy records that juangcuan.com returned a connection reset error instead of loading any site content.

“juangcuan.com”

Review the evidence
Registrar
United StatesDynadot
Resolved IP
United States34.8.229.132Google Cloud
Registered
Apr 7, 2022
First observed
Oct 30, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 17/92 Spamhaus DBL: phishing domain
VirusTotal
17 / 92
engine detections ·
OTX
3
community references
URLScan
Malicious
engine verdict · score 74
Page captures
5
open gallery
Domain age
1,667 days
registered 2022-04-07 according to WHOIS
OTX: 3 refs Oct 30, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy records that juangcuan.com returned a connection reset error instead of loading any site content.

Critical
Status
Last known active
VirusTotal
17 / 92
Hosting
United States34.8.229.132Google Cloud
Registrar
United StatesDynadot
Registered
Apr 7, 2022
OTX
3 community refs
Page captures
5
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured juangcuan.com page shows a browser error rather than any site content: "This site can't be reached" with the explanation "The connection was reset" and the code ERR_CONNECTION_RESET. The page offers only troubleshooting suggestions and Details and Reload buttons, so no site branding, form or other interaction was reachable at capture time. This means the capture documents a failed load rather than any visible page design or interaction.

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

Source evidenceVirusTotal 17 / 92 · OTX 3 references 8 sources

VirusTotal

17 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
45
Malicious
13
Suspicious
4
Undetected
30

Vendor labels

CRDF
malicious
DNS8
suspicious
ESET
suspicious
VIPRE
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Fortinet
spam
Netcraft
malicious
SOCRadar
phishing
Kaspersky
phishing
LevelBlue
phishing
Seclookup
malicious
Gridinsoft
suspicious
alphaMountain.ai
phishing
Yandex Safebrowsing
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

Sophos
phishing and fraud
alphaMountain.ai
Phishing (alphaMountain.ai)
Forcepoint ThreatSeeker
phishing and other frauds

Popularity ranks

Cisco Umbrella
927046
Cloudflare Radar
1000000

Created

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    SOA
    Responsible mailbox
    hostmaster.juangcuan.com
    Value
    ns1.dyna-ns.net
  • TTL, seconds
    300
    Type
    NS
    Value
    ns1.dyna-ns.net
  • TTL, seconds
    300
    Type
    A
    Value
    34.8.229.132
  • TTL, seconds
    300
    Type
    NS
    Value
    ns2.dyna-ns.net

DNS records observed

JARM fingerprint

29d3fd00029d29d00042d43d00041d6f940079659edb62e1c38c38bd26ee84

Certificate

Subject alternative names
  • juangcuan.com
Issuer
Google Trust Services / WR3
Serial
ade8f206d1acf6e2125542488bdb3164
SHA-256
45a2434f724793cfdc01923653f61a509f1cec2c2abc9b34bf0b7c5da01a178e
Subject
juangcuan.com
Valid until
Valid from

Registry data (RDAP)

Status
  • transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Registrar
DYNADOT LLC
Registrar IANA ID
472
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 13,
    "suspicious": 4,
    "undetected": 30
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Fortinet": "spam",
    "Netcraft": "malicious",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "alphaMountain.ai": "phishing",
    "Yandex Safebrowsing": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "phishing and other frauds"
}
Popularity
{
    "Cisco Umbrella": 927046,
    "Cloudflare Radar": 1000000
}
Created
2022-04-07T00:00:00Z
Updated
2026-04-08T00:00:00Z
First seen
2025-04-08T09:04:31Z
DNS records
[
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "hostmaster.juangcuan.com",
        "value": "ns1.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "34.8.229.132"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.dyna-ns.net"
    }
]
Dns at
2026-10-29T09:44:58Z
Jarm
29d3fd00029d29d00042d43d00041d6f940079659edb62e1c38c38bd26ee84
Certificate
{
    "san": [
        "juangcuan.com"
    ],
    "issuer": "Google Trust Services / WR3",
    "serial": "ade8f206d1acf6e2125542488bdb3164",
    "sha256": "45a2434f724793cfdc01923653f61a509f1cec2c2abc9b34bf0b7c5da01a178e",
    "subject": "juangcuan.com",
    "valid_to": "2026-12-02T10:29:50Z",
    "valid_from": "2026-09-03T09:34:56Z"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-04-07T10:23:01Z",
        "last changed": "2026-09-03T09:59:09Z",
        "registration": "2022-04-07T10:23:01Z",
        "registrar expiration": "2027-04-07T10:23:01Z",
        "last update of RDAP database": "2026-10-22T08:23:31Z"
    },
    "registrar": "DYNADOT LLC",
    "registrar_iana_id": "472"
}
Separate source record · 13 malicious + 4 suspicious / 92 · 2026-10-29 09:44:45 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-29T09:44:45Z
fetched_at
2026-10-30T07:03:33Z
stats
{"timeout":0,"harmless":45,"malicious":13,"suspicious":4,"undetected":30}

Cloudflare Radar

Malicious

Open report
Cloudflare RadarOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Report ID

12904232-961c-4db6-b7c5-2baa78a172ac

Final URL

https://juangcuan.com/

Navigation history

  • URL
    https://juangcuan.com/
    Status
    0

DOM structure hash

0be15d34945b061b4688e4c7a258d982bf21eeec94f047738c21f26a19145958

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    juangcuan.com
    Type
    A
    Value
    34.8.229.132

DNSSEC valid

No

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
12904232-961c-4db6-b7c5-2baa78a172ac
Final url
https://juangcuan.com/
History
[
    {
        "url": "https://juangcuan.com/",
        "status": 0
    }
]
DOM structure hash
0be15d34945b061b4688e4c7a258d982bf21eeec94f047738c21f26a19145958
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "juangcuan.com",
        "type": "A",
        "value": "34.8.229.132"
    }
]
Dnssec valid
false
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2022-04-07T10:23:01Z",
    "updated": "2026-05-17T10:25:47Z",
    "expires": "2027-04-07T10:23:01Z",
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ]
}

Spamhaus DBL

phishing domain

URLScan

Malicious · engine verdict · score 74

SHA-256 59630f476f4c87a924b581741c79b7c67221d0cb8cce548f3a129ff33b3c1458

Open report
URLScanOriginal source recordObserved: 17 fields

Observed: · Retrieved:

Report ID

01a0afbe-53bb-75b6-a32e-113bd3058d73

Final URL

http://juangcuan.com/

HTTP response

200

Redirects

  • To
    https://juangcuan.com/
    From
    http://juangcuan.com/
    Status
    307
  • To
    http://juangcuan.com/
    From
    https://juangcuan.com/
    Status
    307

IP address

34.8.229.132

Reverse DNS (PTR)

132.229.8.34.bc.googleusercontent.com

Contacted IP addresses

  • 34.8.229.132

Autonomous systems (ASN)

  • 396982

Server countries

  • US

Document hash

732caefb28f3c3f77a53f7d140918db287be2dd680486af00f10f32de25fc26e

JavaScript globals

  • _Z_ET

Cookies

  • PHPSESSID

Domain age, days

1624

Registered domain age, days

1624

Page requests

3

Provider verdicts

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

HTTP headers

Server
nginx
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
01a0afbe-53bb-75b6-a32e-113bd3058d73
Final url
http://juangcuan.com/
Status
200
Redirects
[
    {
        "to": "https://juangcuan.com/",
        "from": "http://juangcuan.com/",
        "status": 307
    },
    {
        "to": "http://juangcuan.com/",
        "from": "https://juangcuan.com/",
        "status": 307
    }
]
Ip
34.8.229.132
Ptr
132.229.8.34.bc.googleusercontent.com
Contacted IP addresses
[
    "34.8.229.132"
]
Asns
[
    "396982"
]
Countries
[
    "US"
]
Document hash
732caefb28f3c3f77a53f7d140918db287be2dd680486af00f10f32de25fc26e
Globals
[
    "_Z_ET"
]
Cookies
[
    "PHPSESSID"
]
Domain age days
1624
Apex age days
1624
Requests
3
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 74,
        "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
01a0afbe-53bb-75b6-a32e-113bd3058d73
score
0
malicious
false
result_at
2026-10-30T04:30:31Z
enriched_at
2026-10-30T09:10:46Z
source_timestamps
{"urlscan_result_at":"2026-10-30 05:30:31","urlscan_enriched_at":"2026-10-30 10:10:46"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

3 community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 0 / 100 · 2026-10-30T07:04:53Z

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-30T07:04:53Z
source_timestamp
2026-10-30 08:04:53
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
juangcuan.com connection reset error page capture
ai_description
PhishDestroy records that juangcuan.com returned a connection reset error instead of loading any site content.
ai_summary
The captured juangcuan.com page shows a browser error rather than any site content: "This site can't be reached" with the explanation "The connection was reset" and the code ERR_CONNECTION_RESET. The page offers only troubleshooting suggestions and Details and Reload buttons, so no site branding, form or other interaction was reachable at capture time. This means the capture documents a failed load rather than any visible page design or interaction. The stored VirusTotal domain result reports 17 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-30 08:04:08
revision
9c9dd139299eed2f87689d9d0e55eaf8abc3d1ab88a7734cfd31b2b0fd615d9a
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: 7 fields

Mail configuration

SPF lookups
0

CAA records

Domain
juangcuan.com

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
19
Archived days
30
Snapshots per day
0.03
Average page size, bytes
12724

Ports

Open ports
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    162.159.26.92
    Host
    ns1.dyna-ns.net
  • IP address
    162.159.24.5
    Host
    ns2.dyna-ns.net
DNS zone
juangcuan.com

DNS records

A
  • 34.8.229.132
NS
  • ns2.dyna-ns.net
  • ns1.dyna-ns.net
SOA
Primary nameserver
ns1.dyna-ns.net
Hostmaster
hostmaster.juangcuan.com
Serial
2026090302
Refresh, seconds
16384
Retry, seconds
2048
Expiry, seconds
1209600
Minimum TTL, seconds
300
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "juangcuan.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2025-08-09T03:04:22Z",
    "first": "2023-03-30T10:59:15Z",
    "changes": 19,
    "days_archived": 30,
    "scans_per_day": 0.03,
    "avg_page_bytes": 12724
}
Ports
{
    "open": [
        80,
        443
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.26.92",
            "host": "ns1.dyna-ns.net"
        },
        {
            "ip": "162.159.24.5",
            "host": "ns2.dyna-ns.net"
        }
    ],
    "zone": "juangcuan.com"
}
DNS records
{
    "A": [
        "34.8.229.132"
    ],
    "NS": [
        "ns2.dyna-ns.net",
        "ns1.dyna-ns.net"
    ],
    "SOA": "{\"nsname\": \"ns1.dyna-ns.net\", \"hostmaster\": \"hostmaster.juangcuan.com\", \"serial\": 2026090302, \"refresh\": 16384, \"retry\": 2048, \"expire\": 1209600, \"minttl\": 300}"
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware Security threats Malware
View full Cloudflare Radar report

Questions about juangcuan.com

Is juangcuan.com legit?

PhishDestroy records that juangcuan.com returned a connection reset error instead of loading any site content.

Is juangcuan.com safe to connect a wallet?

This report does not record which wallet requests juangcuan.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 juangcuan.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 · 5 captures

Cloudflare Radar 1 / 5 Used in the analysis Source file SHA-256: a5db7ab655d3900bfb2bf44f8483ca7ce06fc6f795376f14b777be50f1f0af62 SHA-256 of the prepared copy given to the model: 9b2bd0fda53e1c8aebf8b218f9819433925b9342fe39730c23b507fc9285f8eb
SourceCloudflare Radar
Recorded
StateStored capture
Final URLhttps://juangcuan.com/
Position1 / 5
Open capture Source Report Wayback Download
All capture links and hashes (5)
juangcuan.com: caution — Flagged by Spamhaus DBL, 17/92 VirusTotal engines. PhishDestroy risk score 95/100 (critical).
Social preview card juangcuan.com: caution — Flagged by Spamhaus DBL, 17/92 VirusTotal engines. PhishDestroy risk score 95/100 (critical). v 700a40353228

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 74 report ↗
IP Reputation United States34.8.229.132 abuse score 0/100 0 reports checked Oct 30, 2026
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for juangcuan.com →
RegistrationCreated Apr 7, 2022 — Expires Apr 7, 2027
Registrant countryUnited States VirusTotal WHOIS
Registrant037fe422b392eb3f VirusTotal WHOIS
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 30, 2026
DOM Analysisanalyzed Oct 30, 2026score 0/100
Submitted URLhttp://juangcuan.com/
Observed page title
juangcuan.com
TLS Certificate
Issued by Google Trust Services / WR3 · stored validity ends in 32 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States34.8.229.132
Network ASN
AS396982
AS name
GOOGLE-CLOUD-PLATFORM - Google LLC, US
Organization
Google Cloud
Observed location
United StatesKansas City, US
Server header
nginx

Nameservers 2

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

SOA

  • nsname: ns1.dyna-ns.net
  • hostmaster: hostmaster.juangcuan.com
  • serial: 2026090302
  • refresh: 16384
  • retry: 2048
  • expire: 1209600
  • minttl: 300

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WR3
Valid from
2026-09-03 09:34:56
Valid until
2026-12-02 10:29:50
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint45a2434f724793cfdc01923653f61a509f1cec2c2abc9b34bf0b7c5da01a178e
Certificate names · 1 SAN
  • juangcuan.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 · 34.8.229.132rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

17 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 17 detections
alphaMountain.ai
CRDF
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
Kaspersky
LevelBlue
Lionic
Netcraft
Seclookup
SOCRadar
Sophos
VIPRE
Yandex Safebrowsing

Archived Evidence

Wayback Machine Snapshot
View Archive
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://juangcuan.com/
Response
HTTP 200
HTML body
27.1 KB
Compressed
10.0 KB
Links
0 internal · 0 external
Detected technologies
nginx
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
Saved response-header values · 8
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Fri, 30 Oct 2026 01:01:16 GMT
execution-time
0.0064930916
Server
nginx
Transfer-Encoding
chunked
Vary
Accept-Encoding
Via
1.1 google

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

Archived

Captured network requests

Network requests: 3 SHA-256 hashes: 3 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-30 01:01 UTC.

Open this scan on URLScan 01a0afbe-53bb-75b6-a32e-113bd3058d73 ↗

All retained availability observations1

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

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 02:01:19.229710
    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: 12. 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
    juangcuan.com detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 10 of 10
  • 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: 74
  • 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.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 17/92
  • OTX Community References
    Community publication references on AlienVault OTX: 3. 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

    3 community references

    View source
  2. Added to PhishDestroy

    juangcuan.com

    View source
  3. VirusTotal

    17/92 engine detections

    View source
  4. URLScan

    Malicious · engine verdict · score 74

    View source
  5. Wayback Machine

    Page archived

    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.

juangcuan.com

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 17 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Malicious OTX 3 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 juangcuan.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/juangcuan.com"
  title="PhishDestroy threat report for juangcuan.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>