Skip to security report
Domain security and threat intelligence
cuxykay.com favicon

cuxykay.com

In short

cuxykay.com is a phishing page detected by PhishDestroy on 2026-10-25.

“Home - cuxykay”

Registrar
Namecheap
Resolved IP
172.67.137.248
Registered
Oct 9, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 1/92 Spamhaus DBL: DBL_SPAM Young domain: 15 days old
VirusTotal
engine detections ·
OTX
community references
Cloudflare Radar
Page captures
open gallery
Domain age
Reports sent
view timeline
OTX: 5 refs Oct 25, 2026 1 Report Sent CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 1. Exercise extreme caution — do not enter credentials or personal information.

Analysis

Domain summary

cuxykay.com is a phishing page detected by PhishDestroy on 2026-10-25. Risk: critical (86/100). Registrar: Namecheap. Status: Last known active. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. VirusTotal: 1/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

Critical
VirusTotal
1 / 92
OTX
5 community refs
Page captures
6

PhishDestroy threat report

Overview

PhishDestroy listed cuxykay.com as a suspicious domain. The recorded page title is "Home - cuxykay". The domain was first seen by PhishDestroy on 2026-10-25, sixteen days after its registration on 2026-10-09. An HTTP 200 response was recorded on the same day.

How the scam works

No specific malicious behavior was observed on the page, and the listing does not point to a particular fraud scheme. Suspicious domains can be used to host deceptive content, collect credentials, or lure users into fraudulent interactions, but the current evidence does not confirm any of these mechanisms for cuxykay.com.

Evidence

VirusTotal reported one detection out of 92 engines, flagged by SOCRadar on 2026-10-24. Google Safe Browsing showed no warning on 2026-10-25. urlscan captured the site on 2026-10-14 and returned a clean verdict on 2026-10-25. OTX listed five pulses referencing the domain as of 2026-10-25. PhishDestroy’s internal blocklist marks the domain as suspicious, while external blocklists returned zero hits on the check date.

Infrastructure

The domain was registered with NameCheap, Inc. on 2026-10-09. The recorded DNS information on 2026-10-25 listed the nameservers colin.ns.cloudflare.com and nina.ns.cloudflare.com and showed the address 172.67.137.248 in Cloudflare’s network. A Let's Encrypt certificate issued on 2026-10-09 was valid until 2027-01-07. An MX record pointed to mail.cuxykay.com.

What to do

Visitors should avoid entering any credentials or personal information on the site and treat it as untrusted. If credentials were submitted, change the associated passwords immediately. Defenders can add cuxykay.com to blocklists, monitor network logs for connections to the recorded IP, and review any email traffic to the listed MX host.

Source evidenceVirusTotal 1 / 92 · OTX 5 references 9 sources

VirusTotal

1 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 1,
    "suspicious": 0,
    "undetected": 36
}
Vendor labels
{
    "SOCRadar": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Registrar
NAMECHEAP INC
Created
2026-10-09T15:08:42Z
Expires
2027-10-09T15:08:42Z
Updated
2026-10-09T15:29:45Z
First seen
2026-10-09T21:35:18Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3032::ac43:89f8"
    },
    {
        "ttl": 3600,
        "type": "MX",
        "value": "mail.cuxykay.com",
        "priority": 10
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.137.248"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3036::6815:491a"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "colin.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "colin.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "nina.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.73.26"
    }
]
Dns at
2026-10-24T20:31:31Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.cuxykay.com",
        "cuxykay.com"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "5dde0dbb16ee59361a49f3817459c6a47cd",
    "sha256": "a8c7c3e55ccfad10e21b1d96519ecfaf905e5d03117550659f9665f1eff5183b",
    "subject": "cuxykay.com",
    "valid_to": "2027-01-07T14:34:22Z",
    "valid_from": "2026-10-09T14:34:23Z"
}
Registration record
{
    "registrar": "NAMECHEAP INC",
    "registrar_iana_id": "1068",
    "registrar_url": "http://www.namecheap.com",
    "created": "2026-10-09T15:08:42Z",
    "updated": "1-01-01T00:00:00Z",
    "expires": "2027-10-09T15:08:42Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "colin.ns.cloudflare.com",
        "nina.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "registration": "2026-10-09T15:08:42Z",
        "registrar expiration": "2027-10-09T15:08:42Z",
        "last update of RDAP database": "2026-10-23T14:45:46Z"
    }
}
Separate source record · 1 malicious + 0 suspicious / 92 · 2026-10-24 20:17:34 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-24T20:17:34Z
fetched_at
2026-10-25T05:46:05Z
stats
{"timeout":0,"harmless":55,"malicious":1,"suspicious":0,"undetected":36}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Uuid
ffe8f794-5246-4d68-a855-fcecd625196e
Final url
https://cuxykay.com/
Status
200
History
[
    {
        "url": "https://cuxykay.com/",
        "status": 200
    }
]
DOM structure hash
036bf0fef6cec01a22d94648247f243857e0bcef0f6b09be3691c3c21a17a163
Document hash
40c5365766438aabcc575e55c689cf6f8818a1a3cebb644a8e9d17fd41f02673
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Malware",
    "Security threats",
    "Newly Seen Domains",
    "Security Risks",
    "New Domains",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "cuxykay.com",
        "type": "A",
        "value": "104.21.73.26"
    },
    {
        "name": "cuxykay.com",
        "type": "A",
        "value": "172.67.137.248"
    },
    {
        "name": "cuxykay.com",
        "type": "AAAA",
        "value": "2606:4700:3036::6815:491a"
    },
    {
        "name": "cuxykay.com",
        "type": "AAAA",
        "value": "2606:4700:3032::ac43:89f8"
    }
]
Dnssec valid
false
Ip
104.21.73.26
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "NameCheap, Inc.",
    "created": "2026-10-09T15:08:42Z",
    "updated": "2026-10-09T15:29:45Z",
    "expires": "2027-10-09T15:08:42Z",
    "nameservers": [
        "colin.ns.cloudflare.com",
        "nina.ns.cloudflare.com"
    ]
}

Spamhaus DBL

DBL_SPAM

OTX

5 community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Uuid
01a1713d-e3be-70f7-8828-cefd05dac053
Final url
https://cuxykay.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://cuxykay.com/",
        "from": "http://cuxykay.com/",
        "status": 307
    }
]
Ip
172.67.137.248
Contacted domains
[
    "static.cloudflareinsights.com"
]
Contacted IP addresses
[
    "104.16.80.73",
    "172.67.137.248"
]
Asns
[
    "13335"
]
Linked domains
[
    "www.facebook.com",
    "twitter.com",
    "www.instagram.com",
    "afthemes.com",
    "wordpress.org"
]
Social
[
    "https://www.facebook.com/sharer/sharer.php",
    "https://twitter.com/intent/tweet",
    "https://www.instagram.com"
]
Document hash
90d3c1619a8253dabe22e568842bf4cb37379616fa7ff4a02f0d5529f2098f09
Script hashes
[
    "cb6f2d32c49d1c2b25e9ffc9aaafa3f83075346c01bcd4ae6eb187392a4292cf",
    "5274f11e6fb32ae0cf2dfb9f8043272865c397a7c4223b4cfa7d50ea52fbde89",
    "631ea2bc942c1791920270ba02eef37774aa10db3994b4936a2b5f891a970ff7",
    "06f80283c6f1c140fa52e72e8efa51bd9129f08c806e0f2d2d08c3add2de9c8b",
    "41f8607570bdc31a8875edc301a65ee01fbec5d4bd869388121bb25ce9361625",
    "2595496fe48df6fcf9b1bc57c29a744c121eb4dd11566466bc13d2e52e6bbcc8",
    "0f1e21942035c2b709dc953720a650970912eaf0dce6881dabd3b2bbe30ac0e7",
    "fbc199bf7f97061c41664b040e84616a0cb54441a2efc5801d5d401d3a049f3c",
    "14af47320898bd93f367026f7833c9956f14e24856976e4f9e10be31155cdcf2",
    "3e4b378228cd807af990682ed8996a0ed7482bfff7756d7a03ba14a86cf9212a"
]
Globals
[
    "jQuery",
    "heateorSssLoadEvent",
    "heateorSssSharingAjaxUrl",
    "heateorSssCloseIconPath",
    "heateorSssPluginIconPath",
    "heateorSssHorizontalSharingCountEnable",
    "heateorSssVerticalSharingCountEnable",
    "heateorSssSharingOffset",
    "heateorSssMobileStickySharingEnabled",
    "heateorSssCopyLinkMessage",
    "heateorSssUrlCountFetched",
    "heateorSssSharesText",
    "heateorSssShareText",
    "heateorSssPopup",
    "heateorSssDetermineWhatsappShareAPI",
    "heateorSssMoreSharingPopup",
    "heateorSssMastodonPopup",
    "heateorSssFilterSharing",
    "heateorSssFacebookTargetUrls",
    "heateorSssGetSharingCounts",
    "heateorSssFetchFacebookShares",
    "heateorSssFBShareJSONCall",
    "heateorSssSaveFacebookShares",
    "heateorSssCalculateApproxCount",
    "heateorSssCalculateActualCount",
    "heateorSssCapitaliseFirstLetter",
    "heateorSssHideSharing",
    "ClipboardJS",
    "AFlocalizedTime",
    "afLiveSearch",
    "moove_frontend_gdpr_scripts",
    "postscribe",
    "gdpr_lightbox",
    "gdpr_consent__strict",
    "gdpr_consent__thirdparty",
    "gdpr_consent__advanced",
    "gdpr_consent__performance",
    "gdpr_consent__preference",
    "gdpr_consent__cookies",
    "EvEmitter"
]
Storage keys
[
    "wpEmojiSettingsSupports"
]
Tls
{
    "san": [
        "*.cuxykay.com",
        "cuxykay.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "cuxykay.com",
    "protocol": "QUIC",
    "valid_to": "2027-01-07T14:34:22Z",
    "valid_from": "2026-10-09T14:34:23Z"
}
Domain age days
14
Apex age days
14
Tls age days
15
Tls valid days
89
Requests
67
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 68,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8"
}
Separate monitor record · 2026-10-25T04:30:43Z

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

record_source
domain_monitor.urlscan
uuid
01a1713d-e3be-70f7-8828-cefd05dac053
score
0
malicious
false
result_at
2026-10-25T04:30:43Z
enriched_at
2026-10-25T09:11:58Z
source_timestamps
{"urlscan_result_at":"2026-10-25 05:30:43","urlscan_enriched_at":"2026-10-25 10:11:58"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy DOM

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

Open report
Separate monitor score · 0 / 100 · 2026-10-25T05:31:44Z

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-25T05:31:44Z
source_timestamp
2026-10-25 06:31:44
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
cuxykay.com — Suspicious Domain
ai_description
PhishDestroy flagged cuxykay.com, a newly registered site with a generic home page, as a suspicious domain after limited detections and early reporting.
ai_generated_at
2026-10-25T05:28:02Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider observation dates.

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

Collected source details

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

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 26 fields
Mail configuration
{
    "mx": [
        "mail.cuxykay.com"
    ],
    "spf_lookups": 0
}
Caa records
{
    "domain": "cuxykay.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-25T04:02:00Z",
    "first": "2026-10-11T14:19:56Z",
    "changes": 1,
    "days_archived": 2,
    "scans_per_day": 0.07,
    "avg_page_bytes": 26807
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://cuxykay.com/sitemap.xml",
        "https://cuxykay.com/sitemap.rss"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 60
}
Page title and metadata
{
    "ogUrl": "https://cuxykay.com/",
    "title": "Home - cuxykay",
    "ogType": "article",
    "robots": "max-image-preview:large",
    "ogImage": "https://cuxykay.com/wp-content/uploads/2026/10/logo.jpg",
    "ogTitle": "Home - cuxykay",
    "generator": "All in One SEO (AIOSEO) 4.8.5",
    "ogSiteName": "cuxykay -",
    "twitterCard": "summary_large_image",
    "canonicalUrl": "https://cuxykay.com/"
}
Trackers
{
    "requests": 56
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 3,
        "tls": 22,
        "wait": 3364,
        "connect": 9,
        "download": 12
    },
    "response_ms": 3410
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 195303,
    "co2_grams": 0.0071,
    "cleaner_than": 7
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.35.75",
            "host": "colin.ns.cloudflare.com"
        },
        {
            "ip": "173.245.58.136",
            "host": "nina.ns.cloudflare.com"
        }
    ],
    "zone": "cuxykay.com"
}
Location
{
    "ip": "2606:4700:3036::6815:491a",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "cuxykay.com"
}
DNS records
{
    "A": [
        "104.21.73.26",
        "172.67.137.248"
    ],
    "MX": [
        "{\"exchange\": \"mail.cuxykay.com\", \"priority\": 10}"
    ],
    "NS": [
        "colin.ns.cloudflare.com",
        "nina.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"colin.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2417045724, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2606:4700:3032::ac43:89f8",
        "2606:4700:3036::6815:491a"
    ]
}
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
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2606:4700:3036::6815:491a",
    "family": 6
}
Redirects
{
    "chain": [
        "https://cuxykay.com"
    ]
}
Page links
{
    "external": [
        "https://www.instagram.com/",
        "https://www.facebook.com/sharer/sharer.php",
        "https://twitter.com/intent/tweet",
        "https://www.facebook.com/sharer/sharer.php",
        "https://twitter.com/intent/tweet",
        "https://afthemes.com/products/morenews/",
        "https://wordpress.org/plugins/gdpr-cookie-compliance/"
    ],
    "external_count": 7,
    "internal_count": 40
}
Registration record
{
    "registrar": "NameCheap, Inc.",
    "created": "2026-10-09T15:08:42Z",
    "updated": "2026-10-09T15:29:45Z",
    "expires": "2027-10-09T15:08:42Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "colin.ns.cloudflare.com",
        "nina.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=UTF-8"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Security threats Malware Malware New Domains Security Risks

Questions about cuxykay.com

Is cuxykay.com legit?

No. PhishDestroy classifies cuxykay.com as a phishing page (risk: critical, 86/100); it was first detected on 2026-10-25. VirusTotal: 1/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is cuxykay.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on cuxykay.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used cuxykay.com?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 6 captures

All capture links and hashes (6)

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Namecheap SE(SE)
Abuse contactabuse@namecheap.com
RegistrationCreated Oct 9, 2026 (15d · Very New!) — Expires Oct 9, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 86/100
Submitted URLhttp://cuxykay.com/
Favicon Hash
Case ID
Observed page title
Home - cuxykay
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 74 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.137.248
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • colin.ns.cloudflare.com
  • nina.ns.cloudflare.com

Mail routing 1 MX record

  • mail.cuxykay.compriority 10

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-09 14:34:23
Valid until
2027-01-07 14:34:22
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-25 05:02:12 UTC
Collection source
PhishDestroy collector
Certificate fingerprinta8c7c3e55ccfad10e21b1d96519ecfaf905e5d03117550659f9665f1eff5183b
Certificate names · 2 SANs
  • *.cuxykay.com
  • cuxykay.com

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

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

VirusTotal Analysis

1 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 1 detection
SOCRadar

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of cuxykay.com · checked Oct 25, 2026

77
Needs Work
Performance
FCP
3.45 s
First Contentful Paint
LCP
4.5 s
Largest Contentful Paint
CLS
0.005
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
3.45 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://cuxykay.com/
Home - cuxykay
Response
HTTP 200
HTML body
191.1 KB
Compressed
24.5 KB
Links
242 internal · 4 external
Detected technologies
jquerybootstrapwordpressreactcloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: ad9a7757df55eedf5b2d5ba61c8094f54dd640f9c6a58361b11124f5379782e5
Open Graph title: Home - cuxykay
Twitter card: summary_large_image
Saved response-header values · 14
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a4fe527fa989543d-YYZ
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Sun, 25 Oct 2026 04:01:50 GMT
Link
; rel="https://api.w.org/", ; rel="alternate"; title="JSON"; type="application/json", ; rel=shortlink
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=KeXyoS06sfFhQ5oERe081zATyLlM%2Buk0fjYF7PXPPGC6BTvG9vvgS3NQvAATfmaa4EmRpXj5Y5vKgvzY2V8w1eJxX6q23xKs1wmvPkfDApET1nVjNb8Y6qe%2FpqwuPw%3D%3D"}]}
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
Vary
Accept-Encoding

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

Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

All retained availability observations2

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

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 05:08:36.000000
    Evidence SHA-256
    4e0d15e8c7bb4488811b95a3494dc4e2f960af9b6985ebc0881273365aedb737
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 05:08:36
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 05:08:36.000000
    Evidence SHA-256
    4e0d15e8c7bb4488811b95a3494dc4e2f960af9b6985ebc0881273365aedb737
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 05:08:36
    Evidence reason

Recorded activity

7 entries
  1. AlienVault OTX

    5 community references

    View source
  2. VirusTotal

    1/92 engine detections

    View source
  3. Cloudflare Radar

    Phishing

    View source
  4. Abuse report sent

    PD-20261025-730105

    abuse@namecheap.com
  5. Added to PhishDestroy

    cuxykay.com

    View source
  6. URLScan

    Page captured

    View source
  7. Wayback Machine

    Page archived

    View source

Check for cloaking

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

cuxykay.com

Evidence & External Reports

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

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Last known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Report to Your Local Authorities

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

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

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

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including cuxykay.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

Stay Informed, Stay Safe

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

Official reporting routes

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

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

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

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

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

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