Skip to security report
Domain security and threat intelligence
htx-io.carrd.co favicon

htx-io.carrd.co

In short

htx-io.carrd.co is a HTX impersonation page detected by PhishDestroy on 2026-08-28. Risk: critical (90/100). Registrar: Carrd. Status: Reachable · access restricted. Hosting: Cloudflare, Inc. VirusTotal: 5/92 engines flag it. Do not enter credentials or connect a wallet.

“HTX — Log In®”

Registrar
Carrd
Resolved IP
104.18.40.34
PhishDestroy assessment Critical
Availability Reachable · access restricted Reachable response; page content was not verified Observed · HTTP probe
VirusTotal detections: 5/92 Stored blocklist matches: 2 Automated brand label: HTX Last known active
Aug 28, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 5. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Source evidenceVirusTotal 5 / 92 5 sources

VirusTotal

5 / 92 engine detections

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

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

Analysis

Critical
VirusTotal
5 / 92
Page captures
2

PhishDestroy threat report

Overview

htx-io.carrd.co is a fake login page that impersonates HTX, the cryptocurrency exchange, and targets its account holders. It is built on Carrd, a free site builder, so the address borrows the builder's domain instead of anything owned by HTX. PhishDestroy first flagged it on 2026-08-28, and it was still online on 2026-10-19.

How the scam works

The page is titled "HTX — Log In®", and the stray trademark symbol is a typical touch on hastily cloned brand pages. Victims usually arrive through ads, direct messages or fake support replies and are asked to sign in. Anything typed into the form, such as an email or phone number, password and one-time 2FA codes, goes to the operators. They can then use those details on the real exchange to take over the account and withdraw its balance before the owner notices.

Evidence

On 2026-10-12, 5 of 92 VirusTotal engines flagged the page: alphaMountain.ai, Chong Lua Dao, Forcepoint ThreatSeeker, Fortinet and LevelBlue. That count is modest, so many browsers and security products will still load the page without a warning. Detection is stronger in the crypto-specific lists. MetaMask's phishing list and SEAL both carry the domain alongside PhishDestroy, which means wallet users and incident responders are already warned about it.

Infrastructure

The site is a subdomain on Carrd's platform, so there was no domain registration that could have revealed when the operation began. Traffic is served through Cloudflare, Inc., with the address geolocated to Canada. That puts the real origin behind a widely used proxy. The page uses a free, automatically issued Google Trust Services certificate. The padlock in the browser only means the connection is encrypted and says nothing about whether the site is legitimate.

What to do

If you typed HTX credentials into this page, go to HTX directly and change your password immediately. Reset your 2FA, end all active sessions, and check your withdrawal address whitelist and API keys for anything you did not create. If you reused that password anywhere else, change it there as well. Contact HTX support at once if you see unfamiliar logins or withdrawals. Defenders should block this subdomain, report it to Carrd and Cloudflare, and warn users that real HTX logins never run on site-builder subdomains.

Collected source details

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

URLScan · 2026-08-28T13:17:53Z

Observed: · Retrieved:

Uuid
01a04884-f23f-71fe-9031-d282926a01c8
Final url
https://htx-io.carrd.co/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://htx-io.carrd.co/",
        "from": "http://htx-io.carrd.co/",
        "status": 307
    }
]
Ip
172.64.147.222
Contacted IP addresses
[
    "172.64.147.222"
]
Asns
[
    "13335"
]
Linked domains
[
    "carrd.co"
]
Document hash
41c6d327372a7f17d3adae3ca9f037c820d4e2a27b2a5fbd3bb98bbbf4afa5ec
Globals
[
    "ontouchcancel",
    "ontouchend",
    "ontouchmove",
    "ontouchstart",
    "_scrollToTop"
]
Tls
{
    "san": [
        "carrd.co",
        "*.carrd.co"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "carrd.co",
    "protocol": "TLS 1.3",
    "valid_to": "2026-10-12T03:43:53Z",
    "valid_from": "2026-07-14T02:43:56Z"
}
Domain age days
12
Apex age days
12
Tls age days
45
Tls valid days
90
Requests
3
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 97,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html",
    "content-security-policy": "frame-ancestors https://carrd.com;",
    "x-frame-options": "deny"
}
Cloudflare Radar · 2026-08-28T13:50:15Z

Observed: · Retrieved:

Uuid
830ef421-a82a-4579-a2e4-5a7a7527f70d
Final url
https://htx-io.carrd.co/
Status
200
Redirected
https-only
History
[
    {
        "url": "http://htx-io.carrd.co/",
        "status": 307
    },
    {
        "url": "https://htx-io.carrd.co/",
        "status": 200
    }
]
DOM structure hash
e0ca826a569c7a29e1fc3503c8fbefdeb8256d40bfea5c9779e6028ef6e601f2
Document hash
41c6d327372a7f17d3adae3ca9f037c820d4e2a27b2a5fbd3bb98bbbf4afa5ec
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "htx-io.carrd.co",
        "type": "A",
        "value": "104.18.40.34"
    },
    {
        "name": "htx-io.carrd.co",
        "type": "A",
        "value": "172.64.147.222"
    }
]
Dnssec valid
false
Ip
104.18.40.34

Questions about htx-io.carrd.co

Is htx-io.carrd.co legit?

No. PhishDestroy classifies htx-io.carrd.co as a HTX impersonation page (risk: critical, 90/100); it was first detected on 2026-08-28. VirusTotal: 5/92 engines flag it. Treat the site as unsafe.

Is htx-io.carrd.co safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on htx-io.carrd.co. 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 htx-io.carrd.co?

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 matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 2 captures

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.
Platform provider Carrd
HTTP Status403 Forbidden
Technical detailsProvenance & timestamps
First DetectedAug 28, 2026
DOM Analysisanalyzed Oct 9, 2026score 90/1001 brand signal
Submitted URLhttp://htx-io.carrd.co/
Favicon Hash
Observed page title
HTX — Log In®
Automated brand references
Htx
TLS Certificate
Issued by Google Trust Services · stored validity ends in 42 days

Network & certificates

Stored technical evidence

Network & DNS

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

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services
Valid from
2026-07-14 02:43:56
Valid until
2026-10-12 03:43:53
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-08-28 16:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprintdb2795fe44ea3653f7c39080d75a72335cc1856ae541883e6101b33004d4a5fc
Certificate names · 1 SAN
  • carrd.co

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-22 10:09:57 UTC

Primary outcome Reachable but protected reason: HTTP access restricted 65% confidence
Attribution Cloudflare mechanism: Access Restriction source: Current Http Probe
Evidence layers Availability: Reachable but protected Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Reachable but protected HTTP access restricted Cloudflare Access Restriction 65% 2026-10-22 10:09:57 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:09:57 UTC last content: 2026-10-07 10:35:27 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.
Technologies · 1 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

5 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 3 detections
alphaMountain.ai
Chong Lua Dao
Forcepoint ThreatSeeker
Fortinet
LevelBlue

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of htx-io.carrd.co · checked Aug 28, 2026

76
Needs Work
Performance
FCP
0.77s
First Contentful Paint
LCP
1.05s
Largest Contentful Paint
CLS
0.869
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.03s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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.

Check for cloaking

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

Page titles differ

alive_content: raw=content_403; http=403; via=https_proxy; server=cloudflare

Browser
HTX — Log In®
Crawler
Page not found
htx-io.carrd.co
Stored observation history20

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→protected

    http_access_restricted · Cloudflare · access_restriction

  2. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  3. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  4. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  5. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

Earlier observations 15
  1. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  2. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  3. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  4. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  5. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  6. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  7. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  8. Availability monitor · Recorded state

    live_content→protected

    http_access_restricted · Cloudflare · access_restriction

  9. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  14. VirusTotal · Detection count

    2→3

  15. Availability monitor · First collection record

    Reachable

Recorded activity

4 entries
  1. VirusTotal

    5/92 engine detections

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. Added to PhishDestroy

    htx-io.carrd.co

    View source
  4. URLScan

    Page captured

    View source

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 0 stored notification records Reachable · access restricted

Listed domains receive at least one abuse report; this entry has no retained notification history.

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.

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 →

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 htx-io.carrd.co)
  • 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

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.

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/htx-io.carrd.co"
  title="PhishDestroy threat report for htx-io.carrd.co"
  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>