Skip to security report
Domain security and threat intelligence
cl-service.is favicon

cl-service.is

In short

cl-service.is is a Bancocontinental impersonation page detected by PhishDestroy on 2026-09-14. Risk: critical (98/100). Status: Reachable · access restricted. Hosting: Cloudflare, Inc. VirusTotal: 11/91 engines flag it. Do not enter credentials or connect a wallet.

“Continental”

Resolved IP
172.67.183.178
Registered
Jul 14, 2026
PhishDestroy assessment Critical
Availability Reachable · access restricted Reachable response; page content was not verified Observed · HTTP probe
VirusTotal detections: 11/91 Automated brand label: Bancocontinental Last known active
OTX: 4 refs Sep 14, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 11. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Source evidenceVirusTotal 11 / 91 · OTX 4 references 5 sources

VirusTotal

11 / 91 engine detections

Open report

OTX

4 community references

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.

Analysis

Critical
VirusTotal
11 / 91
OTX
4 community refs
Page captures
9

PhishDestroy threat report

Overview

cl-service.is impersonates Banco Continental. It presents itself under the page title "Continental" to look like the bank's own service portal. Its targets are the bank's customers, especially anyone who reaches it through a link in a text message, email or chat claiming their account needs attention. PhishDestroy first flagged it on 2026-09-14. As of 2026-10-19 the site is still online, and its content remains reachable behind a protection layer.

How the scam works

Bank impersonation pages copy the look and wording of the real login screen, which here is branded "Continental." A victim lured by an urgent message about a blocked account, a suspicious transfer or a required update types in their username and password. Many such pages then ask for one-time codes, card numbers or identity details. The operators use these credentials quickly to log in to the real account, approve transfers or enroll new devices. The victim can lose both account access and the money in it.

Evidence

On 2026-09-25, 11 of 91 VirusTotal engines flagged the domain. The flagging vendors include alphaMountain.ai, BitDefender, CRDF, CyRadar, Forcepoint ThreatSeeker, Fortinet, G-Data and Gridinsoft. That spread across independent vendors is meaningful for a site this new, though most engines had not yet caught up. urlscan.io rated the page malicious and recognised the Banco Continental branding on it, which directly supports the impersonation classification. The domain also appears in four AlienVault OTX threat pulses and is listed on the PhishDestroy blocklist.

Infrastructure

The domain was registered on 2026-07-14, about two months before PhishDestroy detected it. That kind of gap is common when a phishing domain is prepared in advance and then activated for a campaign. The site is served through Cloudflare's network, on an address geolocated to Canada, so the true origin server is hidden behind the proxy. The neutral "cl-service" name on an .is domain carries no bank branding, which lets the link pass a quick glance in a message.

What to do

If you entered your Banco Continental login on this site, change your password immediately through the bank's official app or website, not through any link you received. Then call the bank to report the exposure. Ask the bank to review recent transactions, block any card details you typed in, and reset any one-time-code or device enrollments made after your visit. Watch for follow-up calls or messages posing as the bank's fraud team, which often come next. Defenders should block cl-service.is at the DNS and proxy level and search mail and SMS logs for links to it.

Collected source details

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

URLScan · 2026-09-14T21:22:53Z

Observed: · Retrieved:

Uuid
01a0a1cd-0a5f-7124-bdbf-d1f23fd9d3b3
Final url
https://cl-service.is/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://cl-service.is/",
        "from": "http://cl-service.is/",
        "status": 307
    }
]
Ip
104.21.72.116
Contacted domains
[
    "s3.eu-central-003.backblazeb2.com",
    "telegram.org",
    "static.cloudflareinsights.com"
]
Contacted IP addresses
[
    "45.11.39.254",
    "149.154.167.99",
    "104.21.72.116"
]
Asns
[
    "40401",
    "62041",
    "13335"
]
Countries
[
    "NL"
]
Linked domains
[
    "t.me"
]
Social
[
    "https://t.me/VercettyVC4",
    "https://t.me/XoTabIch_011",
    "https://t.me/mega_service_admin"
]
Document hash
064a4efe92fd9eb2640647868b3ed15eff955268f57a03f6e4b2c8458aa779a4
Script hashes
[
    "852a12c320b2fc9f8720c9bff8d9908a0013bceeaef5f9499da311057fcbd180",
    "06e456da3412e3215f14f8ab5ec351e9fceee5099c0ef03f11208b9c55676d24",
    "67b17a654999a7657ee674f0c33e1f159d519ba409f1bbe585e76bf996297327",
    "afd3c5c50951d598ad11dd2b82d431e2be48040a379061ad01a3fb778532ba22",
    "7e340c2de583d428a8807cec6d0b622e416c1d0f3be2f6b7cd199c561856cca6",
    "47be129fb29bd40c5e40eb7b8c6d4c4c08bba77d509b1bd4c092941911630d6b",
    "06c4e4ccd6c6b0e51d232906909a42a3e13524f02716a4024954d621edac8bae",
    "3bd9a452a97ff5f1cf79144ed813bf961f6a5c97827b4dfc4b8498955bdbf233",
    "fdc68e80151b83234de9ff094346b9964abfdba72c70db97b5180fe1bf1b2a78",
    "8aeee8d6782ff530d2668743699efb757dd8d5091ab49aab2120e894ab08ea68"
]
Globals
[
    "Telegram",
    "TelegramGameProxy_receiveEvent",
    "TelegramGameProxy",
    "__reactRouterVersion",
    "MotionIsMounted",
    "proto",
    "TronWebProto",
    "QuillImageDropAndPaste"
]
Storage keys
[
    "__telegram__initParams"
]
Tls
{
    "san": [
        "cl-service.is",
        "*.cl-service.is"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "cl-service.is",
    "protocol": "QUIC",
    "valid_to": "2026-10-22T14:51:02Z",
    "valid_from": "2026-07-24T13:56:08Z"
}
Domain age days
52
Apex age days
52
Tls age days
52
Tls valid days
90
Requests
98
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 63,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "bancocontinental"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Banco Continental"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html",
    "content-security-policy": "default-src 'self'; script-src 'self' https://telegram.org https://challenges.cloudflare.com; script-src-attr 'none'; object-src 'none'; base-uri 'self'; frame-ancestors 'self' https://web.telegram.or",
    "x-content-type-options": "nosniff",
    "referrer-policy": "strict-origin-when-cross-origin"
}
Cloudflare Radar · 2026-09-14T21:24:10Z

Observed: · Retrieved:

Uuid
7a3981be-4daf-49ed-88d1-8e5f4ac5dfdc
Final url
https://cl-service.is/
Status
200
History
[
    {
        "url": "https://cl-service.is/",
        "status": 200
    }
]
DOM structure hash
01b7518b5b5c84d1855400151432daddce9e5cc75f732e560791880d0850d6e0
Document hash
064a4efe92fd9eb2640647868b3ed15eff955268f57a03f6e4b2c8458aa779a4
Domain risks
[
    "Vehicles"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "cl-service.is",
        "type": "A",
        "value": "104.21.72.116"
    },
    {
        "name": "cl-service.is",
        "type": "A",
        "value": "172.67.183.178"
    },
    {
        "name": "cl-service.is",
        "type": "AAAA",
        "value": "2606:4700:3030::ac43:b7b2"
    },
    {
        "name": "cl-service.is",
        "type": "AAAA",
        "value": "2606:4700:3032::6815:4874"
    }
]
Dnssec valid
false
Ip
104.21.72.116
Registration record
{
    "created": "2026-07-14T14:55:02Z",
    "updated": "2026-07-25T14:36:00Z",
    "nameservers": [
        "opal.ns.cloudflare.com",
        "rohin.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-10-20T14:35:23Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 44,
    "malicious": 13,
    "suspicious": 1,
    "undetected": 34
}
Vendor labels
{
    "CRDF": "malicious",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "LevelBlue": "phishing",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "desenmascara.me": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Popularity
{
    "Cloudflare Radar": 1000000
}
Expires
2027-07-14T00:00:00Z
First seen
2026-07-24T16:05:13Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:10::ac42:a7db"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.20.32.77"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "opal.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.66.167.219"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "rohin.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "opal.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:10::6814:204d"
    }
]
Dns at
2026-10-20T14:39:45Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "cl-service.is",
        "*.cl-service.is"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "bb93162436af095713dc17f0fd3aa39e",
    "sha256": "fa79220b9f66829dadfaee7afa5d8b9a5cd305a1e95f1eb5c5f88d33d75283b4",
    "subject": "cl-service.is",
    "valid_to": "2026-12-20T20:53:41Z",
    "valid_from": "2026-09-21T19:53:55Z"
}
Registration record
{
    "dnssec": "unsigned delegation"
}
Registry data
{
    "status": [
        "active"
    ],
    "events": {
        "last changed": "2026-07-25T14:36:00Z",
        "registration": "2026-07-14T14:55:02Z",
        "soft expiration": "2027-07-14T14:52:15Z"
    }
}

Questions about cl-service.is

Is cl-service.is legit?

No. PhishDestroy classifies cl-service.is as a Bancocontinental impersonation page (risk: critical, 98/100); it was first detected on 2026-09-14. VirusTotal: 11/91 engines flag it. Treat the site as unsafe.

Is cl-service.is safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on cl-service.is. 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 cl-service.is?

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

Extracted from stored page analysis

Observed indicators

0 wallet · 3 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

Telegram
https://t.me/VercettyVC4Stored page reference
Telegram
https://t.me/XoTabIch_011Stored page reference
Telegram
https://t.me/mega_service_adminStored page reference

IoC extraction recorded 2026-09-15 04:00:05 UTC

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 9 captures

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Bancocontinental report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
RegistrationCreated Jul 14, 2026 (100d) — Expires Jul 14, 2027
HTTP Status403 Forbidden
Technical detailsProvenance & timestamps
First DetectedSep 14, 2026
DOM Analysisanalyzed Sep 15, 2026score 98/1001 brand signal
IoC Extractionscanned Sep 15, 20260 wallet · 3 Telegram IoCs
Submitted URLhttp://cl-service.is/
Favicon Hash
Observed page title
Continental
Automated brand references
Bancocontinental
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 59 days

Network & certificates

Stored technical evidence

Network & DNS

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

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • opal.ns.cloudflare.com
  • rohin.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-09-21 19:53:55
Valid until
2026-12-20 20:53:41
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-11 01:03:29 UTC
Collection source
PhishDestroy collector
Certificate fingerprintfa79220b9f66829dadfaee7afa5d8b9a5cd305a1e95f1eb5c5f88d33d75283b4
Certificate names · 2 SANs
  • cl-service.is
  • *.cl-service.is

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:27:07 UTC

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

VirusTotal Analysis

11 / 91 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 6 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
SOCRadar
desenmascara.me

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 cl-service.is · checked Sep 14, 2026

57
Needs Work
Performance
FCP
5.11s
First Contentful Paint
LCP
9.46s
Largest Contentful Paint
CLS
0.064
Cumulative Layout Shift
TBT
1ms
Total Blocking Time
SI
7.55s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable 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.

cl-service.is
Saved result
Cloaked / Filtered
Stored observation history21

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

    cloudflare_challenge · Cloudflare · challenge

  2. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  3. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  4. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  5. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

Earlier observations 16
  1. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  2. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  3. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  4. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  5. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  6. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  7. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  8. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  9. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  10. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  11. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  12. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  13. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  14. Availability monitor · Recorded state

    protected

    cloudflare_challenge · Cloudflare · challenge

  15. VirusTotal · Detection count

    3→6

  16. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    11/91 engine detections

    View source
  4. URLScan

    Page captured

    View source
  5. Added to PhishDestroy

    cl-service.is

    View source

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 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 cl-service.is)
  • 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/cl-service.is"
  title="PhishDestroy threat report for cl-service.is"
  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>