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

clartefincore-engine.com

In short

PhishDestroy stores a record for clartefincore-engine.com. Source observations are dated separately; missing checks do not establish safety.

“Clarté Fincore | AI Trading Platform | Official Website”

Registrar
MainReg
Resolved IP
Netherlands185.62.57.28Snel.com B.V.
Registered
Feb 15, 2026
First observed
Oct 24, 2026
PhishDestroy assessment Critical
95/100
Evidence score
First observed Oct 24, 2026 14:40 UTC · PhishDestroy
VirusTotal detections: 18/92
VirusTotal
engine detections ·
OTX
community references
URLScan
engine verdict · score 99
Cloudflare Radar
Page captures
open gallery
Domain age
registered 2026-02-15 according to WHOIS
Reports sent
view timeline
OTX: 5 refs Oct 24, 2026 1 Report Sent
X Telegram API
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is complain@mainreg.com. The latest stored availability evidence still shows the domain reachable; 7 days has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
7 days
Reports sent
1
Latest case ID
PD-20261024-DADE49
Current status
Observed active at latest stored check

Questions about clartefincore-engine.com

Is clartefincore-engine.com legit?

PhishDestroy stores a record for clartefincore-engine.com. Source observations are dated separately; missing checks do not establish safety.

Is clartefincore-engine.com safe to connect a wallet?

This report does not record which wallet requests clartefincore-engine.com makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used clartefincore-engine.com?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Source evidenceVirusTotal 18 / 92 · OTX 5 references 8 sources

VirusTotal

18 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
43
Malicious
14
Suspicious
4
Undetected
31

Vendor labels

CRDF
malicious
DNS8
suspicious
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
suspicious
BitDefender
phishing
Chong Lua Dao
malicious
alphaMountain.ai
spam
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

alphaMountain.ai
Spam, Suspicious (alphaMountain.ai)

Created

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    kyle.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    185.62.57.28
  • TTL, seconds
    21600
    Type
    NS
    Value
    adelaide.ns.cloudflare.com
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    adelaide.ns.cloudflare.com

DNS records observed

JARM fingerprint

40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319

Certificate

Subject alternative names
  • clartefincore-engine.com
Issuer
ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2
Serial
9d9ef8349ecb3afde8ef20cd526ca286
SHA-256
a162fb5fc2b4f6c00cdc6c97c778ec8d37e00efb917b229ffe8df8a72d32ef7e
Subject
clartefincore-engine.com
Valid until
Valid from

Registry data (RDAP)

Status
  • active
Registry events
Last changed
Registration
Registrar expiration
Last RDAP database update
Registrar
MainReg Inc.
Registrar IANA ID
1917
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 43,
    "malicious": 14,
    "suspicious": 4,
    "undetected": 31
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "spam",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Spam, Suspicious (alphaMountain.ai)"
}
Created
2026-02-15T00:00:00Z
Updated
2026-02-15T00:00:00Z
First seen
2026-02-15T14:30:45Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "kyle.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "185.62.57.28"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "adelaide.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "adelaide.ns.cloudflare.com"
    }
]
Dns at
2026-10-19T17:55:44Z
Jarm
40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319
Certificate
{
    "san": [
        "clartefincore-engine.com"
    ],
    "issuer": "ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2",
    "serial": "9d9ef8349ecb3afde8ef20cd526ca286",
    "sha256": "a162fb5fc2b4f6c00cdc6c97c778ec8d37e00efb917b229ffe8df8a72d32ef7e",
    "subject": "clartefincore-engine.com",
    "valid_to": "2026-12-18T23:59:59Z",
    "valid_from": "2026-09-19T00:00:00Z"
}
Registry data
{
    "status": [
        "active"
    ],
    "events": {
        "last changed": "2026-02-15T00:00:00Z",
        "registration": "2026-02-15T00:00:00Z",
        "registrar expiration": "2027-02-15T00:00:00Z",
        "last update of RDAP database": "2026-10-18T17:52:00Z"
    },
    "registrar": "MainReg Inc.",
    "registrar_iana_id": "1917"
}
Separate source record · 14 malicious + 4 suspicious / 92 · 2026-10-19 17:50:17 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-19T17:50:17Z
fetched_at
2026-10-24T17:27:59Z
stats
{"timeout":0,"harmless":43,"malicious":14,"suspicious":4,"undetected":31}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

bb8f3de4-66d8-4982-913b-6d87cfe39823

Final URL

https://clartefincore-engine.com/

HTTP response

200

Navigation history

  • URL
    https://clartefincore-engine.com/
    Status
    200

DOM structure hash

bcf9b28883127f1ad5312a20c07151fd351f91143805304fb214e73d9c444465

Document hash

4f60d433c2108f3165b06d1a6785ac0aea01fc3cb0d3f98e49735d42f2ae2176

Phishing classifier result

  • phishing

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    clartefincore-engine.com
    Type
    A
    Value
    185.62.57.28

DNSSEC valid

No

IP address

185.62.57.28

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware

Registration record

Registrar
MainReg Inc.
Registered
Updated
Expires
Nameservers
  • adelaide.ns.cloudflare.com
  • kyle.ns.cloudflare.com
Original source fields · JSON
Uuid
bb8f3de4-66d8-4982-913b-6d87cfe39823
Final url
https://clartefincore-engine.com/
Status
200
History
[
    {
        "url": "https://clartefincore-engine.com/",
        "status": 200
    }
]
DOM structure hash
bcf9b28883127f1ad5312a20c07151fd351f91143805304fb214e73d9c444465
Document hash
4f60d433c2108f3165b06d1a6785ac0aea01fc3cb0d3f98e49735d42f2ae2176
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "clartefincore-engine.com",
        "type": "A",
        "value": "185.62.57.28"
    }
]
Dnssec valid
false
Ip
185.62.57.28
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "MainReg Inc.",
    "created": "2026-02-15T11:34:03Z",
    "updated": "2026-02-15T14:07:03Z",
    "expires": "2027-02-15T11:34:03Z",
    "nameservers": [
        "adelaide.ns.cloudflare.com",
        "kyle.ns.cloudflare.com"
    ]
}

URLScan

Malicious · engine verdict · score 99

SHA-256 f23e3e1019d00ffe8757d231f4eef956e2e6e0ff96351c2e3f8a0f8011f0cab1

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a16e58-ff59-70cf-b72d-a256da7bee38

Final URL

https://clartefincore-engine.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://clartefincore-engine.com/
    From
    http://clartefincore-engine.com/
    Status
    307

IP address

185.62.57.28

Reverse DNS (PTR)

static-28-57-62-185.hosted-by-snel.com

Contacted domains

  • cdn.jsdelivr.net
  • challenges.cloudflare.com
  • cdnjs.cloudflare.com
  • fonts.gstatic.com
  • www.cloudflare.com
  • fonts.googleapis.com

Contacted IP addresses

  • 104.18.95.41
  • 104.16.123.96
  • 142.250.195.99
  • 104.17.207.5
  • 104.17.25.14
  • 172.217.25.170
  • 185.62.57.28

Autonomous systems (ASN)

  • 13335
  • 15169
  • 62370

Server countries

  • US
  • NL

Document hash

4f60d433c2108f3165b06d1a6785ac0aea01fc3cb0d3f98e49735d42f2ae2176

Script hashes

  • 525d8640da396ef9d31655cd259bc9fb59699a57d691bcc4c1a50daf69ad4de0

JavaScript globals

  • toggleTermsPopup
  • intlTelInput
  • __TS_SITEKEY
  • __tsGet
  • __tsReset
  • __tsNeedsClick
  • __tsShow
  • __lgBS
  • ClientJS
  • __visitorCountry
  • turnstile

Browser storage keys

  • t_cfp

TLS session and certificate

Subject alternative names
  • clartefincore-engine.com
Cipher
AES_128_GCM
Issuer
ZeroSSL ECC DV SSL CA 2
Subject
clartefincore-engine.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

251

Registered domain age, days

251

Certificate age, days

35

Certificate validity, days

90

Page requests

26

Provider verdicts

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

HTTP headers

Content-type
text/html; charset=utf-8
Referrer-policy
no-referrer-when-downgrade
Original source fields · JSON
Uuid
01a16e58-ff59-70cf-b72d-a256da7bee38
Final url
https://clartefincore-engine.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://clartefincore-engine.com/",
        "from": "http://clartefincore-engine.com/",
        "status": 307
    }
]
Ip
185.62.57.28
Ptr
static-28-57-62-185.hosted-by-snel.com
Contacted domains
[
    "cdn.jsdelivr.net",
    "challenges.cloudflare.com",
    "cdnjs.cloudflare.com",
    "fonts.gstatic.com",
    "www.cloudflare.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "104.18.95.41",
    "104.16.123.96",
    "142.250.195.99",
    "104.17.207.5",
    "104.17.25.14",
    "172.217.25.170",
    "185.62.57.28"
]
Asns
[
    "13335",
    "15169",
    "62370"
]
Countries
[
    "US",
    "NL"
]
Document hash
4f60d433c2108f3165b06d1a6785ac0aea01fc3cb0d3f98e49735d42f2ae2176
Script hashes
[
    "525d8640da396ef9d31655cd259bc9fb59699a57d691bcc4c1a50daf69ad4de0"
]
Globals
[
    "toggleTermsPopup",
    "intlTelInput",
    "__TS_SITEKEY",
    "__tsGet",
    "__tsReset",
    "__tsNeedsClick",
    "__tsShow",
    "__lgBS",
    "ClientJS",
    "__visitorCountry",
    "turnstile"
]
Storage keys
[
    "t_cfp"
]
Tls
{
    "san": [
        "clartefincore-engine.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "ZeroSSL ECC DV SSL CA 2",
    "subject": "clartefincore-engine.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-18T23:59:59Z",
    "valid_from": "2026-09-19T00:00:00Z"
}
Domain age days
251
Apex age days
251
Tls age days
35
Tls valid days
90
Requests
26
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8",
    "referrer-policy": "no-referrer-when-downgrade"
}
Separate monitor record · 2026-10-24 19:22 UTC

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

record_source
domain_monitor.urlscan
uuid
01a16e58-ff59-70cf-b72d-a256da7bee38
score
0
malicious
false
result_at
2026-10-24T19:22:37Z
enriched_at
2026-10-25T09:15:01Z
source_timestamps
{"urlscan_result_at":"2026-10-24 21:22:37","urlscan_enriched_at":"2026-10-25 10:15:01"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

5 community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

25 / 100 · heuristic score · 1 brand reference · 1 classification

Open report
Separate monitor score · 25 / 100 · 2026-10-24T17:31:59Z

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
25
analyzed_at
2026-10-24T17:31:59Z
source_timestamp
2026-10-24 19:31:59
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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: 25 fields

Mail configuration

SPF lookups
0

CAA records

Domain
clartefincore-engine.com

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
12825

Crawler rules

User agents
  • *
Present
Yes
Sitemap URLs
  • https://clartefincore-engine.com/sitemap.xml

Sitemap

Present
Yes
URL count
140

Page title and metadata

Open Graph URL
https://clartefincore-engine.com/
Page title
Clarté Fincore | AI Trading Platform | Official Website
Open Graph type
website
Indexing directives
index, follow
Open Graph title
Clarté Fincore | Institutional AI Trading Automation
Open Graph site name
Clarté Fincore
Theme color
#0e0e0e
Description
Clarté Fincore provides institutional-style automated trading bot tooling with AI-powered assistance, execution workflow controls, and risk-focused...
Twitter card
summary
Canonical URL
https://clartefincore-engine.com/
Open Graph description
Clarté Fincore provides institutional-style automated trading bot tooling with AI-powered assistance, execution workflow controls, and risk-focused configuration for informed decisions.

Trackers

Requests
20
Observed services
  • Name
    Cloudflare
    Company
    Cloudflare
    Country
    US
    Category
    Hosting
    Requests
    7
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    2
  • Name
    jsDelivr
    Company
    jsDelivr
    Category
    Hosting
    Requests
    3

Forms and mixed content

Scripts without SRI
  • https://cdn.jsdelivr.net/npm/intl-tel-input@23/build/js/intlTelInput.min.js
Third-party scripts
1

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
27
TLS
28
Waiting
19
Connection
13
Download
50
Response time, ms
137

TLS connection

ALPN
h2
Cipher
TLS_AES_128_GCM_SHA256
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
OCSP stapling
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
49229
CO₂, grams
0.0018
Cleaner than, %
37

DNS servers

Nameservers
  • IP address
    162.159.44.111
    Host
    kyle.ns.cloudflare.com
  • IP address
    172.64.34.1
    Host
    adelaide.ns.cloudflare.com
DNS zone
clartefincore-engine.com

Location

IP address
185.62.57.28
ASN
62370
Organization
Snel.com B.V.
City
Rotterdam
Country
NL

TLS certificate

Issuer
ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2
Subject
clartefincore-engine.com

DNS records

A
  • 185.62.57.28
NS
  • adelaide.ns.cloudflare.com
  • kyle.ns.cloudflare.com
SOA
Primary nameserver
adelaide.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2417052247
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
no-referrer-when-downgrade
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
185.62.57.28
IP version
4

Redirects

Redirect chain
  • https://clartefincore-engine.com

Page links

Internal links
13

Registration record

Registrar
MainReg Inc.
Registered
Updated
Expires
Status
  • ok https://icann.org/epp
Nameservers
  • adelaide.ns.cloudflare.com
  • kyle.ns.cloudflare.com

HTTP headers

Response headers
Content-type
text/html; charset=utf-8
Referrer-policy
no-referrer-when-downgrade
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "clartefincore-engine.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-24T14:42:21Z",
    "first": "2026-10-24T14:42:21Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 12825
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://clartefincore-engine.com/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 140
}
Page title and metadata
{
    "ogUrl": "https://clartefincore-engine.com/",
    "title": "Clarté Fincore | AI Trading Platform | Official Website",
    "ogType": "website",
    "robots": "index, follow",
    "ogTitle": "Clarté Fincore | Institutional AI Trading Automation",
    "ogSiteName": "Clarté Fincore",
    "themeColor": "#0e0e0e",
    "description": "Clarté Fincore provides institutional-style automated trading bot tooling with AI-powered assistance, execution workflow controls, and risk-focused...",
    "twitterCard": "summary",
    "canonicalUrl": "https://clartefincore-engine.com/",
    "ogDescription": "Clarté Fincore provides institutional-style automated trading bot tooling with AI-powered assistance, execution workflow controls, and risk-focused configuration for informed decisions."
}
Trackers
{
    "requests": 20,
    "trackers": [
        {
            "name": "Cloudflare",
            "company": "Cloudflare",
            "country": "US",
            "category": "Hosting",
            "requests": 7
        },
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        },
        {
            "name": "jsDelivr",
            "company": "jsDelivr",
            "category": "Hosting",
            "requests": 3
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://cdn.jsdelivr.net/npm/intl-tel-input@23/build/js/intlTelInput.min.js"
    ],
    "third_party_scripts": 1
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 27,
        "tls": 28,
        "wait": 19,
        "connect": 13,
        "download": 50
    },
    "response_ms": 137
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "ocsp_stapled": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 49229,
    "co2_grams": 0.0018,
    "cleaner_than": 37
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.44.111",
            "host": "kyle.ns.cloudflare.com"
        },
        {
            "ip": "172.64.34.1",
            "host": "adelaide.ns.cloudflare.com"
        }
    ],
    "zone": "clartefincore-engine.com"
}
Location
{
    "ip": "185.62.57.28",
    "asn": "62370",
    "org": "Snel.com B.V.",
    "city": "Rotterdam",
    "country": "NL"
}
Ssl
{
    "issuer": "ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2",
    "subject": "clartefincore-engine.com"
}
DNS records
{
    "A": [
        "185.62.57.28"
    ],
    "NS": [
        "adelaide.ns.cloudflare.com",
        "kyle.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"adelaide.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2417052247, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": "no-referrer-when-downgrade",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "185.62.57.28",
    "family": 4
}
Redirects
{
    "chain": [
        "https://clartefincore-engine.com"
    ]
}
Page links
{
    "internal_count": 13
}
Registration record
{
    "registrar": "MainReg Inc.",
    "created": "2026-02-15T11:34:03Z",
    "updated": "2026-02-15T14:07:03Z",
    "expires": "2027-02-15T11:34:03Z",
    "status": [
        "ok https://icann.org/epp"
    ],
    "nameservers": [
        "adelaide.ns.cloudflare.com",
        "kyle.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "content-type": "text/html; charset=utf-8",
        "referrer-policy": "no-referrer-when-downgrade"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware Security threats Malware
Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Last checked

Stored Capture · 4 captures

All capture links and hashes (4)
clartefincore-engine.com: caution — 18/92 VirusTotal engines. PhishDestroy risk score 95/100 (critical).
Social preview card clartefincore-engine.com: caution — 18/92 VirusTotal engines. PhishDestroy risk score 95/100 (critical). v b0aa12a58d59

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 99 report ↗
IP Reputation Netherlands185.62.57.28 abuse score 0/100 0 reports checked Oct 24, 2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Hosting abuse contact complain@mainreg.com Snel.com B.V. · AS62370
RegistrationCreated Feb 15, 2026 (258d) — Expires Feb 15, 2027
Registrant countryArgentina VirusTotal WHOIS
Registrantd1eba5ec8d184a4cs@fablovkawhoisprotection.com VirusTotal WHOIS
WHOIS statusok
Technical detailsProvenance & timestamps
First DetectedOct 24, 2026
DOM Analysisanalyzed Oct 24, 2026score 25/1001 brand signal
Submitted URLhttp://clartefincore-engine.com/
Favicon Hash
Case ID
Observed page title
Clarté Fincore | AI Trading Platform | Official Website
Automated brand references
Across
TLS Certificate
Issued by ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2 · stored validity ends in 47 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Netherlands185.62.57.28
Network ASN
AS62370
AS name
Snel Snel.com B.V., NL
Organization
Snel.com B.V.
Observed location
NetherlandsRotterdam, NL
Server header
ESF

Nameservers 2

  • adelaide.ns.cloudflare.com
  • kyle.ns.cloudflare.com

SOA

  • nsname: adelaide.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2417052247
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Location describes the IP network.

TLS certificate

Issuer
ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2
Valid from
2026-09-19 00:00:00
Valid until
2026-12-18 23:59:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprinta162fb5fc2b4f6c00cdc6c97c778ec8d37e00efb917b229ffe8df8a72d32ef7e
Certificate names · 1 SAN
  • clartefincore-engine.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-31 10:20:09 UTC

The domain no longer resolves in DNS.

Technical details
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 Probe Inconclusive 20% 2026-11-01 02:57:04 UTC
RDAP registration
Observed timeline last reachable: 2026-10-26 11:01:38 UTC last content: 2026-10-26 11:01:38 UTC current episode first observed: 2026-10-26 20:55:09 UTC observed RIP window: 2026-10-26 11:01:38 UTC → 2026-10-26 20:55:09 UTC · 9.89h midpoint estimate ≈ 2026-10-26 15:58:23 UTC · precision medium · basis bounded
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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • education.clartefincore-engine.comDomain record
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

18 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 18 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of clartefincore-engine.com · checked Oct 24, 2026

67
Needs Work
Performance
FCP
1.81 s
First Contentful Paint
LCP
1.81 s
Largest Contentful Paint
CLS
0.9
Cumulative Layout Shift
TBT
326 ms
Total Blocking Time
SI
1.81 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://clartefincore-engine.com/
Final URL: https://clartefincore-engine.com/
Clarté Fincore | AI Trading Platform | Official Website
Clarté Fincore provides institutional-style automated trading bot tooling with AI-powered assistance, execution workflow controls, and risk-focused...
Response
HTTP 200
HTML body
48.1 KB
Compressed
11.3 KB
Links
32 internal · 0 external
Selected response headers
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Security headers present
Referrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Open Graph title: Clarté Fincore | Institutional AI Trading Automation
Open Graph description: Clarté Fincore provides institutional-style automated trading bot tooling with AI-powered assistance, execution workflow controls, and risk-focused configuration for informed decisions.
Twitter card: summary
Saved response-header values · 9
Alt-Svc
h3=":443"; ma=2592000
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sat, 24 Oct 2026 14:41:08 GMT
Etag
"dm9jl381a14y11zh-gzip"
Last-Modified
Tue, 20 Oct 2026 09:02:08 GMT
Referrer-Policy
no-referrer-when-downgrade
Transfer-Encoding
chunked
Vary
Accept-Encoding

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

Registration & observation details9

Availability observations

Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
9.89
Estimate basis
Bounded by observations
Estimate precision
Medium

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

Captured network requests

Network requests: 26 SHA-256 hashes: 22 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 01:58 UTC.

Open this scan on URLScan 01a16e58-ff59-70cf-b72d-a256da7bee38 ↗

Stored observation history7

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

    dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    live_content→dns_inactive

    dns_nxdomain

Earlier observations 2
  1. Availability monitor · Recorded state

    live_content

    content_served

  2. Domain monitor · First collection record

    Reachable

All retained availability observations33

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. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:57:04.000000
    Evidence SHA-256
    9e06d20b71c395c4237f67d1fcd1ede27ce133b7a1db45baeec5fe96750600fb
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 03:57:04
    Evidence reason
    unavailable
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:11:57.000000
    Evidence SHA-256
    afeb46ef3c1e7be0b157b895f4cd7efbc13b0be4abe60454ae11a6734ee608d7
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 00:11:57
    Evidence reason
    unavailable
  3. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:12:45.000000
    Evidence SHA-256
    bbe8ccc37c1d40a06f4f5e2084c1fac7abc7734b2f311dbe58d70b1240dd2e37
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 12:12:45
    Evidence reason
    unavailable
  4. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 11:20:09.112163
    Evidence SHA-256
    2e34d2905787d1cb41d14eee10dd71d398cf25f60d14075bf54efbe7992ba1bf
    Evidence timestamp as recorded
    2026-10-31 11:20:09.112163
  5. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 11:20:09.112163
    Evidence SHA-256
    2e34d2905787d1cb41d14eee10dd71d398cf25f60d14075bf54efbe7992ba1bf
    Evidence timestamp as recorded
    2026-10-31 11:20:09.112163
  6. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:33:51.000000
    Evidence SHA-256
    ca69a4846993d0d49dc32cebf296fc1f437c86acd424b434e40dce9971b2b9c9
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 03:33:51
    Evidence reason
    unavailable
  7. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:10:37.000000
    Evidence SHA-256
    2709bb1773e863b3bf04aa97d727ab18ab075d879fac5a419fd3f6b25f6305a8
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 12:10:37
    Evidence reason
    unavailable
  8. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 05:03:05.462458
    Evidence SHA-256
    f9cff5b9f1950ff481e989dfeecab84b2bf6e847bdeb7bc146f3f704088b4943
    Evidence timestamp as recorded
    2026-10-30 05:03:05.462458
  9. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 05:03:05.462458
    Evidence SHA-256
    f9cff5b9f1950ff481e989dfeecab84b2bf6e847bdeb7bc146f3f704088b4943
    Evidence timestamp as recorded
    2026-10-30 05:03:05.462458
  10. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:10:39.000000
    Evidence SHA-256
    ec1a91d525d34ca377277b044243bbf2b9ee2fe0c3b09483bd2b8f672c08e611
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 00:10:39
    Evidence reason
    unavailable
  11. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:11:12.000000
    Evidence SHA-256
    8685d043f484e76d5b622e04b4f4cb3661076f00998dbf2ac6774f24f1399f46
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 12:11:12
    Evidence reason
    unavailable
  12. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 05:03:05.313035
    Evidence SHA-256
    8c28aed4f75521c73afc7e2f2348663e7c1a458d23765c350da6f168634f471b
    Evidence timestamp as recorded
    2026-10-29 05:03:05.313035
  13. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 05:03:05.313035
    Evidence SHA-256
    8c28aed4f75521c73afc7e2f2348663e7c1a458d23765c350da6f168634f471b
    Evidence timestamp as recorded
    2026-10-29 05:03:05.313035
  14. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:39:51.000000
    Evidence SHA-256
    d9358f75ea357aa9762355ccb41230126b11070141153d6cc3d05cfc3de66fde
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 03:39:51
    Evidence reason
    unavailable
  15. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:39:51.000000
    Evidence SHA-256
    d9358f75ea357aa9762355ccb41230126b11070141153d6cc3d05cfc3de66fde
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 03:39:51
    Evidence reason
    unavailable
  16. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:06:18.000000
    Evidence SHA-256
    ffbfa5a5451b35e810dfdfd8a5eba1fd74dc456205c41d916af0ac2efd25df97
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-28 12:06:18
    Evidence reason
    unavailable
  17. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:06:47.000000
    Evidence SHA-256
    b73f25bd21dcf06f48f28a72374abf326aeff8a3c703e3a6e1e13c006dc645e3
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-28 00:06:47
    Evidence reason
    unavailable
  18. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 21:55:09.758880
    Evidence SHA-256
    c68bf2f82849c4b3638eb8f300834ab8c592de8a7ac3533cb5b1c1845fd6aefe
    Evidence timestamp as recorded
    2026-10-27 21:55:09.758880
  19. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 21:55:09.758880
    Evidence SHA-256
    c68bf2f82849c4b3638eb8f300834ab8c592de8a7ac3533cb5b1c1845fd6aefe
    Evidence timestamp as recorded
    2026-10-27 21:55:09.758880
  20. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:06:36.000000
    Evidence SHA-256
    0be7b5fc229f69616e98099a05b82fd6f544d3c87b6ac1877c2f5372d86782fa
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 12:06:36
    Evidence reason
    unavailable
  21. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 21:55:09.041159
    Evidence SHA-256
    94e24d965cabb31a5e77ff88eaa3c949b842e0726d9a63de435da554d9d878e6
    Evidence timestamp as recorded
    2026-10-26 21:55:09.041159
  22. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 21:55:09.041159
    Evidence SHA-256
    94e24d965cabb31a5e77ff88eaa3c949b842e0726d9a63de435da554d9d878e6
    Evidence timestamp as recorded
    2026-10-26 21:55:09.041159
  23. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:01:38.000000
    Evidence SHA-256
    5d2791fdf3ef1a8819afe68339619e7874d5dfb69556dd733182e3ba0d622187
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:01:38
    Evidence reason
    alive_content
  24. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:01:53.000000
    Evidence SHA-256
    8276041ff87092ee2b96408faeec9105af44686c11239806c857a535fef39fc1
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 00:01:53
    Evidence reason
    timeout
  25. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:01:53.000000
    Evidence SHA-256
    8276041ff87092ee2b96408faeec9105af44686c11239806c857a535fef39fc1
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 00:01:53
    Evidence reason
    timeout
  26. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 21:55:07.813656
    Evidence SHA-256
    c03dbd2dcd7c6f08fd7189e78b7cd4e699f4a81ddbfb248f4d57c8431243efdd
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 21:55:07.813656
    Evidence reason
  27. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:01:23.000000
    Evidence SHA-256
    7b9636e0900b51c7df800ae3ee20082e75414e74c68cfc867effa9f9b149e1cb
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 12:01:23
    Evidence reason
    timeout
  28. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:01:23.000000
    Evidence SHA-256
    7b9636e0900b51c7df800ae3ee20082e75414e74c68cfc867effa9f9b149e1cb
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 12:01:23
    Evidence reason
    timeout
  29. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 01:07:41.000000
    Evidence SHA-256
    2b7564fa92008a0f33d6bec9d27265afb610625cd7e4c96e704d56929b98634e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 01:07:41
    Evidence reason
    timeout
  30. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 01:07:41.000000
    Evidence SHA-256
    2b7564fa92008a0f33d6bec9d27265afb610625cd7e4c96e704d56929b98634e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 01:07:41
    Evidence reason
    timeout
  31. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 22:55:07.425478
    Evidence SHA-256
    db407a17211d6cfcb77d163e1a7001bdf0972c8f223c354514bcb9984da64451
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-24 22:55:07.425478
    Evidence reason
  32. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 16:40:09.000000
    Evidence SHA-256
    8c66d1f0841b956458af95404431424a5be3ace7cdd6b277044f3bbd12b27e96
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-24 16:40:09
    Evidence reason
  33. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 16:40:09.000000
    Evidence SHA-256
    8c66d1f0841b956458af95404431424a5be3ace7cdd6b277044f3bbd12b27e96
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-24 16:40:09
    Evidence reason

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. Monitoring · recorded

Recorded events: 12. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    clartefincore-engine.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 99
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 18/92
  • OTX Community References
    Community publication references on AlienVault OTX: 5. References are not vendor verdicts and are excluded from the evidence score.
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as malware, Security threats
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: MainReg Inc.. Abuse contacts: 1.
    • complain@mainreg.com
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

7 entries
  1. AlienVault OTX

    5 community references

    View source
  2. Cloudflare Radar

    Phishing

    View source
  3. Abuse report sent

    PD-20261024-DADE49 · Receipt 82422

    complain@mainreg.com
  4. Wayback Machine

    Page archived

    View source
  5. Added to PhishDestroy

    clartefincore-engine.com

    View source
  6. URLScan

    Page captured

    View source
  7. VirusTotal

    18/92 engine detections

    View source
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

Check for cloaking

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

clartefincore-engine.com

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261024-DADE49 Recipient: complain@mainreg.com
PDF notice generated
Deep Analysis
Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Unverified
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Official reporting routes

More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

An estimated $51 billion flowed to illicit crypto wallets in 2024 (source). If you interacted with clartefincore-engine.com — act now.

What should I do immediately?

Urgent

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

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

What information should I collect for my report?

FBI guidelines

According to the FBI, the most important details are transaction data:

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Cryptocurrency addresses — scammer's wallet (e.g., 0x5856...35985)
  • Amount & crypto type — exact amount (e.g., 1.02345 ETH, 0.5 BTC, 500 USDT)
  • Transaction ID (hash) — the unique blockchain transaction identifier
  • 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 clartefincore-engine.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)
  • Chainabuse — flag scam wallets across exchanges & platforms
  • Your crypto exchange — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
  • 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 crypto 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

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Guaranteed crypto recovery is a fraud indicator. 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.

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/clartefincore-engine.com"
  title="PhishDestroy threat report for clartefincore-engine.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>