Skip to security report
Analytics Dashboard
Domain security and threat intelligence
01kz4kz0hfaqkfyzbpjc8efzzw.cfworking.com favicon

01kz4kz0hfaqkfyzbpjc8efzzw.cfworking.com

In short

01kz4kz0hfaqkfyzbpjc8efzzw.cfworking.com is a blocklisted domain detected by PhishDestroy on 2026-08-05.

Registrar
Realtime
Registered
Jul 30, 2026
PhishDestroy assessment High
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
Record details & risk signals
Aug 5, 2026
Risk signals
VirusTotal detections: 2/89
VirusTotal
2 / 89
engine detections
Domain age
86 days
API
This domain has been flagged as malicious
Security engines reporting a detection: 2. Exercise extreme caution — do not enter credentials or personal information.

Analysis

High
  • VirusTotal detections: 2/89
Source counts
VirusTotal
2 / 89
Domain summary

01kz4kz0hfaqkfyzbpjc8efzzw.cfworking.com is a blocklisted domain detected by PhishDestroy on 2026-08-05. Risk: high (56/100). Registrar: Realtime. Status: Content unavailable. VirusTotal: 2/89 engines flag it. PhishDestroy detected it 38 days before VirusTotal engines flagged it (in PhishDestroy’s checks). Do not enter credentials or connect a wallet.

Source results Registration record

PhishDestroy threat report

Overview

01kz4kz0hfaqkfyzbpjc8efzzw.cfworking.com is a domain on the PhishDestroy blocklist. It is a long, random-looking subdomain under cfworking.com, and no brand or page title has been tied to it. PhishDestroy first saw it on 2026-08-05. The site has been offline since 2026-09-13, and its DNS was still inactive at the last check on 2026-10-19.

How the scam works

No specific scheme has been confirmed for this host, so we do not attribute it to any particular brand, kit or drainer. Hosts like this usually live for a short time and reach visitors through links in messages, ads or social posts rather than through search. The flags against it point to the usual risks of a malicious page: a fake login or wallet prompt that collects credentials or seed phrases, or a page that pushes visitors to approve something they did not intend. Anyone who reached it from an unsolicited link should treat whatever they entered or approved there as exposed.

Evidence

On 2026-09-13, two of 89 VirusTotal engines flagged the domain: Forcepoint ThreatSeeker and SOCRadar. That is a thin result, and the domain went offline the same day, so most vendors had little chance to analyse it. The listing rests mainly on PhishDestroy's own blocklist entry, backed by those two independent vendor verdicts.

Infrastructure

The parent domain cfworking.com is registered through Realtime Register B.V. The randomized, 26-character label suggests a generated subdomain rather than a name chosen for people to remember, and generated names make individual hosts easy to rotate and discard. The host stopped resolving about five weeks after PhishDestroy first saw it.

What to do

If you visited this host and typed a password, change it everywhere you reuse it and turn on two-factor authentication. If you entered a recovery phrase, move your funds to a new wallet right away. If you connected a wallet or signed anything, review and revoke unfamiliar token approvals. Defenders should block cfworking.com subdomains matching this random pattern at DNS and proxy level, and search logs for traffic to this host from 2026-08-05 onward.

Useful links

VirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 2 / 89 4 sources
SourceResultRecorded · UTCEvidence

VirusTotal

2 / 89 engine detections

Open report

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Not recorded
Open report

Google Safe Browsing

No threat flag

Open report

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

Questions about 01kz4kz0hfaqkfyzbpjc8efzzw.cfworking.com

Is 01kz4kz0hfaqkfyzbpjc8efzzw.cfworking.com legit?

No. PhishDestroy classifies 01kz4kz0hfaqkfyzbpjc8efzzw.cfworking.com as a blocklisted domain (risk: high, 56/100); it was first detected on 2026-08-05. VirusTotal: 2/89 engines flag it. PhishDestroy detected it 38 days before VirusTotal engines flagged it (in PhishDestroy’s checks). Treat the site as unsafe.

Is 01kz4kz0hfaqkfyzbpjc8efzzw.cfworking.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on 01kz4kz0hfaqkfyzbpjc8efzzw.cfworking.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 01kz4kz0hfaqkfyzbpjc8efzzw.cfworking.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

Domain details

Domain
Registrar (base domain) Realtime NL(NL)
Abuse contact["rtr-security-threats@realtimeregister.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for cfworking.com →
Registration (base domain)cfworking.com · Created Jul 30, 2026 (86d · New) — Expires Jul 30, 2027
Time to First Unavailability 38 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 5, 2026

Network & certificates

Stored technical evidence

Network & DNS

Nameservers 1

  • b1.share-dns.net

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-07-30 13:42:17
Valid until
2026-10-28 13:42:16
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintb5552f7162d97e563b8a33df20528e2d550d86dff0ffaa72ea0f547fc4a5f2ee
Certificate names · 1 SAN
  • *.cfworking.com

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

Latest Classified Outcome 2026-10-24 08:55:03 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-23 01:00:18 UTC
RDAP registration Unknown
Observed timeline current episode first observed: 2026-09-30 16:14:55 UTC first terminal observation: 2026-09-30 16:14:55 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

2 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 0 detections
Forcepoint ThreatSeeker
SOCRadar
Registration & observation details3

Availability observations

Outcome first observed
Observation window ends
Estimate basis
first_observation_only

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

Check for cloaking

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

01kz4kz0hfaqkfyzbpjc8efzzw.cfworking.com
Saved result
Unreachable

Collected source details

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

Every stored field, with its source and date
Cloudflare Radar · 2026-09-12T22:34:06Z

Observed: · Retrieved:

Uuid
26e417aa-98d6-4871-9e5d-5362d56814ce
VirusTotal · 2026-10-18T21:06:06Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 52,
    "malicious": 4,
    "suspicious": 0,
    "undetected": 36
}
Vendor labels
{
    "CRDF": "malicious",
    "SOCRadar": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "alphaMountain.ai": "Phishing, Newly Registered (alphaMountain.ai)"
}
Registrar
Realtime Register B.V.
Created
2026-07-30T14:35:19Z
Expires
2027-07-30T14:35:19Z
Updated
2026-09-28T14:35:56Z
First seen
2026-08-05T17:41:09Z
DNS records
[
    {
        "ttl": 600,
        "type": "A",
        "value": "104.237.144.193"
    }
]
Dns at
2026-08-05T17:50:17Z
Jarm
27d40d40d00040d00042d43d000000e1ea2a807a629b496b664cf07ad7c08d
Certificate
{
    "san": [
        "*.cfworking.com"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "6b96bdd0c69b2d4c900fce70b30d4f3743b",
    "sha256": "b5552f7162d97e563b8a33df20528e2d550d86dff0ffaa72ea0f547fc4a5f2ee",
    "subject": "*.cfworking.com",
    "valid_to": "2026-10-28T13:42:16Z",
    "valid_from": "2026-07-30T13:42:17Z"
}
Registration record
{
    "registrar": "Realtime Register B.V.",
    "registrar_iana_id": "839",
    "registrar_url": "http://www.realtimeregister.com",
    "created": "2026-07-30T14:35:19Z",
    "updated": "2026-09-28T14:35:56Z",
    "expires": "2027-07-30T14:35:19Z",
    "status": [
        "clientHold"
    ],
    "nameservers": [
        "poppy.ns.cloudflare.com",
        "zac.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Stored observation history25

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

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

Earlier observations 20
  1. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  6. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  8. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  9. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  10. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  11. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  12. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  13. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  14. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  15. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  16. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  17. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  18. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  19. Availability monitor · Recorded state

    Reachable→Unavailable

  20. VirusTotal · Detection count

    0→2

Recorded activity

2 entries
  1. VirusTotal

    2/89 engine detections

    View source
  2. Added to PhishDestroy

    01kz4kz0hfaqkfyzbpjc8efzzw.cfworking.com

    View source

Community intelligence

1 community report

CategoryJOB_SCAM

They texted me and said there was a site I can sign up for to make money

Evidence & External Reports

Security Analysis
VirusTotal 2 det. ChainPatrol ChainAbuse 1 report URLQuery SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Community Scam Report — ChainAbuse
1 report filed for 01kz4kz0hfaqkfyzbpjc8efzzw.cfworking.com (1 written by a person) · category: Job Scam · source checked
“They texted me and said there was a site I can sign up for to make money”
— reported by Anonymous on Aug 3, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
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?

1 evidence signal groups linked Content unavailable
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.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

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

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 01kz4kz0hfaqkfyzbpjc8efzzw.cfworking.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

Live Threat Feed Appeal This Listing
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/01kz4kz0hfaqkfyzbpjc8efzzw.cfworking.com"
  title="PhishDestroy threat report for 01kz4kz0hfaqkfyzbpjc8efzzw.cfworking.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>