Skip to security report
This domain has been flagged as malicious
Security engines reporting a detection: 17. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
clairefondvere.com favicon

clairefondvere.com

In short

clairefondvere.com is a Venus impersonation page detected by PhishDestroy on 2026-10-24.

“Claire Fondvère — Plateforme IA pour gérer votre trésorerie”

Registrar
Dynadot
Resolved IP
158.94.210.119
Registered
May 8, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 17/92 Automated brand label: Venus
VirusTotal
engine detections ·
OTX
community references
Cloudflare Radar
source verdict
Page captures
open gallery
Domain age
Reports sent
view timeline
OTX: 4 refs Oct 24, 2026 1 Report Sent
X Telegram API
ABUSE NOTICE · 24H+ 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 abuse@omegatech.sc. The latest stored availability evidence still shows the domain reachable; 29 hours 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
29 hours
Reports sent
1
Latest case ID
PD-20261024-208866
Current status
HTTP 200 at latest stored check

Analysis

Domain summary

clairefondvere.com is a Venus impersonation page detected by PhishDestroy on 2026-10-24. Risk: critical (100/100). Registrar: Dynadot. Status: Last known active. Hosting: Omegatech LTD. PhishDestroy sent 1 abuse report. VirusTotal: 17/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
17 / 92
OTX
4 community refs
Page captures
4

PhishDestroy threat report

Overview

PhishDestroy added clairefondvere.com to its internal blocklist on 2026-10-24 after an intake flagged it for multiple malicious detections. The recorded page title advertised an AI‑driven cash‑management platform. An HTTP 200 response was recorded on that date, indicating the site was reachable then.

How the scam works

The VirusTotal and other engine detections commonly label sites used for phishing, where visitors are tricked into providing credentials or personal data by mimicking legitimate services. No credential‑collection form or other malicious functionality was observed on the captured page, so the exact technique cannot be confirmed for this domain.

Evidence

VirusTotal scanned the domain on 2026-10-24 and returned 14 malicious and 3 suspicious detections from 92 engines (17 total). Google Safe Browsing checked the same day and did not flag the site. urlscan.io recorded a malicious engine score of 95 on 2026-10-24, though its overall verdict was non‑malicious. OTX listed four pulses mentioning the domain as of 2026-10-24. PhishDestroy’s internal blocklist marked the domain as suspicious, while external blocklists returned zero matches.

Infrastructure

The domain was registered with Dynadot Inc on 2026-05-08, giving it an age of 169 days at the time of detection. It resolved to the recorded IP 158.94.210.119, which was associated with Omegatech LTD in the Netherlands. The site presented a Let’s Encrypt certificate issued on 2026-08-28 and valid until 2026-11-26. Scans observed ports 22, 80 and 443 open.

What to do

Visitors should avoid entering any credentials or personal information on the site and should change passwords if they suspect they have already submitted them. Organizations can block traffic to clairefondvere.com and monitor logs for connections to its recorded IP address. Security teams should keep the domain on deny lists and watch for related indicators in threat feeds.

Source evidenceVirusTotal 17 / 92 · OTX 4 references 9 sources

VirusTotal

17 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 43,
    "malicious": 14,
    "suspicious": 3,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
Dynadot Inc
Created
2026-05-08T14:06:55Z
Expires
2027-05-08T14:06:55Z
Updated
2026-08-13T12:39:12Z
First seen
2026-05-08T14:27:16Z
DNS records
[
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "hostmaster.clairefondvere.com",
        "value": "ns1.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "158.94.210.119"
    }
]
Dns at
2026-10-23T12:28:17Z
Jarm
40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319
Certificate
{
    "san": [
        "clairefondvere.com"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "5abb844b6b26655455f603503ecaca5d713",
    "sha256": "84c1e2b06705642ea32ca883513c8043ec357fb3c3c8f1ab0d73bb3c3b17b774",
    "subject": "clairefondvere.com",
    "valid_to": "2026-11-26T13:40:57Z",
    "valid_from": "2026-08-28T13:40:58Z"
}
Registration record
{
    "registrar": "Dynadot Inc",
    "registrar_iana_id": "472",
    "registrar_url": "http://www.dynadot.com",
    "created": "2026-05-08T14:06:55Z",
    "updated": "2026-08-13T12:39:12Z",
    "expires": "2027-05-08T14:06:55Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-05-08T14:06:55Z",
        "last changed": "2026-08-28T08:32:33Z",
        "registration": "2026-05-08T14:06:55Z",
        "registrar expiration": "2027-05-08T14:06:55Z",
        "last update of RDAP database": "2026-10-23T10:35:01Z"
    }
}
Separate source record · 14 malicious + 3 suspicious / 92 · 2026-10-23 12:22:40 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-23T12:22:40Z
fetched_at
2026-10-24T15:04:46Z
stats
{"timeout":0,"harmless":43,"malicious":14,"suspicious":3,"undetected":32}

Cloudflare Radar

Malicious

Not recorded
Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Uuid
146cd06b-a170-4373-a498-b70350219cbd
Final url
https://clairefondvere.com/
Status
200
History
[
    {
        "url": "https://clairefondvere.com/",
        "status": 200
    }
]
DOM structure hash
32841d7bb7c71311b49342a7b91ced4013753cf7c0832e033dfe1f84ead250cc
Document hash
f8b056a93ff30cc6bc1019bd23ba88039b0f986c56e9a677d94a9c417f37ba1e
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "clairefondvere.com",
        "type": "A",
        "value": "158.94.210.119"
    }
]
Dnssec valid
false
Ip
158.94.210.119
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-05-08T14:06:55Z",
    "updated": "2026-08-13T12:39:12Z",
    "expires": "2027-05-08T14:06:55Z",
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ]
}

OTX

4 community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Uuid
01a16e53-1fad-703b-abb1-bb234889774c
Final url
https://clairefondvere.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://clairefondvere.com/",
        "from": "http://clairefondvere.com/",
        "status": 307
    }
]
Ip
158.94.210.119
Contacted IP addresses
[
    "158.94.210.119"
]
Asns
[
    "202412"
]
Countries
[
    "NL"
]
Document hash
04d05978fdb111358073ab0524e5c1fafc0826615c206987618416b8bd8a4747
Script hashes
[
    "8aa5f8f647356dcd4fc5dbbe0efd5bc0e8da74026bc61e24636e2e1f5749b0ce"
]
Globals
[
    "__dclq",
    "__dclOrig",
    "__dclFlush",
    "__smsCheckBeforeSubmit",
    "__isSmsEnabled",
    "__isSmsVerified",
    "intlTelInput"
]
Cookies
[
    "connect.sid"
]
Domain age days
169
Apex age days
169
Tls age days
57
Tls valid days
89
Requests
10
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 95,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "image/png"
}
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
01a16e53-1fad-703b-abb1-bb234889774c
score
0
malicious
false
result_at
2026-10-24T19:22:40Z
enriched_at
2026-10-25T09:14:59Z
source_timestamps
{"urlscan_result_at":"2026-10-24 21:22:40","urlscan_enriched_at":"2026-10-25 10:14:59"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

98 / 100 · heuristic score · 2 brand references · 1 classifications

Open report
Separate monitor score · 10 / 100 · 2026-10-24T15:09:44Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
10
analyzed_at
2026-10-24T15:09:44Z
source_timestamp
2026-10-24 17:09:44
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
clairefondvere.com — Suspicious Domain
ai_description
PhishDestroy flagged clairefondvere.com as a suspicious domain after multiple security engines reported malicious activity.
ai_generated_at
2026-10-24T15:06:01Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider observation dates.

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

Collected source details

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

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 26 fields
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "clairefondvere.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-24T14:36:33Z",
    "first": "2026-10-24T14:36:33Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 21160
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://clairefondvere.com/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 5
}
Page title and metadata
{
    "title": "Claire Fondvère — Plateforme IA pour gérer votre trésorerie",
    "robots": "index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1",
    "description": "Claire Fondvère analyse vos flux financiers en temps réel et adapte ses recommandations d'allocation à votre profil de risque réel. Découvrez une gestion de trésorerie qui évolue avec vous.",
    "canonicalUrl": "https://clairefondvere.com/"
}
Trackers
{
    "requests": 55,
    "trackers": [
        {
            "name": "Cloudflare",
            "company": "Cloudflare",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "jsDelivr",
            "company": "jsDelivr",
            "category": "Hosting",
            "requests": 4
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 916,
        "tls": 86,
        "wait": 115,
        "connect": 84,
        "download": 139
    },
    "response_ms": 1340
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Carbon
{
    "bytes": 74629,
    "co2_grams": 0.0027,
    "cleaner_than": 28
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.27.158",
            "host": "ns1.dyna-ns.net"
        },
        {
            "ip": "162.159.24.5",
            "host": "ns2.dyna-ns.net"
        }
    ],
    "zone": "clairefondvere.com"
}
Cookies
{
    "cookies": [
        {
            "name": "cf-c",
            "http_only": true,
            "same_site": "Lax"
        },
        {
            "name": "__cf_clicked"
        },
        {
            "name": "ph_phc_t6w4wzJE2sbz4ro8LmZZTssm5go3KD6mP7QsqcDQRSp6_posthog",
            "secure": true,
            "same_site": "Lax"
        }
    ]
}
Location
{
    "ip": "158.94.210.119",
    "asn": "202412",
    "org": "Omegatech LTD",
    "city": "Amsterdam",
    "country": "NL"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "clairefondvere.com"
}
DNS records
{
    "A": [
        "158.94.210.119"
    ],
    "NS": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ],
    "SOA": "{\"nsname\": \"ns1.dyna-ns.net\", \"hostmaster\": \"hostmaster.clairefondvere.com\", \"serial\": 2026082801, \"refresh\": 16384, \"retry\": 2048, \"expire\": 1209600, \"minttl\": 300}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": "same-origin",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "158.94.210.119",
    "family": 4
}
Redirects
{
    "chain": [
        "https://clairefondvere.com"
    ]
}
Page links
{
    "internal_count": 8
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-05-08T14:06:55Z",
    "updated": "2026-08-13T12:39:12Z",
    "expires": "2027-05-08T14:06:55Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ]
}
HTTP headers
{
    "headers": {
        "content-type": "text/html; charset=utf-8",
        "x-content-type-options": "nosniff",
        "referrer-policy": "same-origin"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware Security threats Malware

Questions about clairefondvere.com

Is clairefondvere.com legit?

No. PhishDestroy classifies clairefondvere.com as a Venus impersonation page (risk: critical, 100/100); it was first detected on 2026-10-24. VirusTotal: 17/92 engines flag it. Treat the site as unsafe.

Is clairefondvere.com safe to connect a wallet?

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

What should I do if I used clairefondvere.com?

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

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 4 captures

All capture links and hashes (4)

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 10/100 15 reports PhishingOpen ProxyBad Web Bot checked Oct 24, 2026
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
RegistrationCreated May 8, 2026 (170d) — Expires May 8, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 24, 2026
DOM Analysisanalyzed Oct 24, 2026score 98/1002 brand signals
Submitted URLhttp://clairefondvere.com/
Favicon Hash
Case ID
Observed page title
Claire Fondvère — Plateforme IA pour gérer votre trésorerie
Automated brand references
Base Venus
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 31 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
158.94.210.119
Network ASN
AS202412
Organization
Omegatech LTD
Observed location
Amsterdam, NL

Nameservers 2

  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-08-28 13:40:58
Valid until
2026-11-26 13:40:57
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint84c1e2b06705642ea32ca883513c8043ec357fb3c3c8f1ab0d73bb3c3b17b774
Certificate names · 1 SAN
  • clairefondvere.com

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

Latest Classified Outcome 2026-10-24 23:07:04 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-24 23:07:04 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-24 23:07:04 UTC last content: 2026-10-24 23:07:04 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

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

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

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

100
Good
Performance
FCP
0.99 s
First Contentful Paint
LCP
1.56 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.46 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://clairefondvere.com/
Final URL: https://clairefondvere.com/
Response
HTTP 200
HTML body
809 B
Compressed
422 B
Links
0 internal · 0 external
Selected response headers
Cache-Control: no-cache, no-store, must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
X-Powered-By: Express
Security headers present
X-Content-Type-OptionsReferrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 11
Alt-Svc
h3=":443"; ma=2592000
Cache-Control
no-cache, no-store, must-revalidate
Content-Encoding
gzip
Content-Length
427
Content-Type
text/html; charset=utf-8
Date
Sat, 24 Oct 2026 14:35:56 GMT
Referrer-Policy
same-origin
Vary
Accept-Encoding
Via
1.1 Caddy
X-Content-Type-Options
nosniff
X-Powered-By
Express

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

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Stored observation history2

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

    content_served

  2. Domain monitor · First collection record

    Reachable

All retained availability observations5

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

  1. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    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-25 01:07:04.000000
    Evidence SHA-256
    a8951cbf871572cc44586c8b4f70086b66c4caf9a9f50580bf0503b9cc4681dc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 01:07:04
    Evidence reason
    alive_content
  2. 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-25 01:07:04.000000
    Evidence SHA-256
    a8951cbf871572cc44586c8b4f70086b66c4caf9a9f50580bf0503b9cc4681dc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 01:07:04
    Evidence reason
    alive_content
  3. 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
  4. 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:33:45.000000
    Evidence SHA-256
    407680266309463e2c06cd8f2c7e31a72ee1682449091ab0e1d331f612266ac8
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-24 16:33:45
    Evidence reason
  5. 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:33:45.000000
    Evidence SHA-256
    407680266309463e2c06cd8f2c7e31a72ee1682449091ab0e1d331f612266ac8
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-24 16:33:45
    Evidence reason

Recorded activity

6 entries
  1. AlienVault OTX

    4 community references

    View source
  2. VirusTotal

    17/92 engine detections

    View source
  3. Wayback Machine

    Page archived

    View source
  4. Abuse report sent

    PD-20261024-208866

    abuse@omegatech.sc
  5. Added to PhishDestroy

    clairefondvere.com

    View source
  6. URLScan

    Page captured

    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.

clairefondvere.com

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261024-208866 Recipient: abuse@omegatech.sc
PDF notice generated Notice text archived (291 chars)
Abuse notice text as sent to the provider
Registrar: Dynadot LLC / Dynadot Inc (United States)
Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
Deep Analysis
Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Last known active
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.

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

Report to Your Local Authorities

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

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

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

What information should I collect for my report?

FBI guidelines

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

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including clairefondvere.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

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

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

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

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

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

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

Embed This Report

Share this threat intelligence on your website or blog

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