VirusTotal
2 / 91
SignalerInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“merkl.claims | 522: Connection timed out”
Assessment based on the stored source evidence below. Review sources →
app.merkl.claims — Dernier actif connu (HTTP 301). Type d'arnaque : Crypto Scam. Résumé des preuves: VirusTotal 2/91 (Chong Lua Dao, Gridinsoft); 1 external blocklist match (ScamSniffer); PhishDestroy score 71/100. Bureau d’enregistrement: Cloudflare.
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
2 / 91
SignalerEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
1 external matches
DétailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
no community references
SignalerCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
rapport stocké
View stored capture ↗ SignalerA preserved page image documents what the collector received; a capture is not a safety verdict.
Analyse terminée
SignalerThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
SignalerA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
The domain app.merkl.claims, associated with a high threat score of 75/100, is confirmed as a generic phishing operation and is currently down. It has been flagged as malicious by 4 out of 95 security vendors, including Fortinet and SOCRadar, and is listed on 2 public blocklists, indicating a recognized threat. Google Safe Browsing has not flagged this domain, suggesting it may have been operational for a limited time before being taken down.
Registered with Cloudflare, Inc., the domain's first-seen date is December 16, 2025, and it resolves to the hosting IP 188.114.97.3. The lack of a specific brand being impersonated indicates a broader phishing strategy rather than targeting a single entity. Immediate action should involve blocking the domain at the perimeter and submitting it to the registrar's abuse desk for further investigation.
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
For the registrable domain merkl.claims behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
La réputation Edge-IP n’est pas attribuée à ce domaine.
Location describes the IP network.
8ac63f0b87d72cf801047b557529135f1f800bf73cebfe538ef26bc750af2c3emerkl.claimsSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of app.merkl.claims · checked Mar 26, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Enregistrement des observations « crawler contre navigateur » pour cet hôte, ainsi qu'une vérification en temps réel des empreintes numériques pour les systèmes de répartition du trafic de type Keitaro.
cloudflareNote relative à la numérisation: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://app.merkl.claims/; server=cloudflare
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Inconnu→redirected
http_redirect
redirected→Inconnu
probe_inconclusive
Inconnu→redirected
http_redirect
redirected→Inconnu
probe_inconclusive
Inconnu→redirected
http_redirect
redirected→Inconnu
probe_inconclusive
Inconnu→redirected
http_redirect
redirected→Inconnu
probe_inconclusive
Inconnu→redirected
http_redirect
redirected→Inconnu
probe_inconclusive
Inconnu→redirected
http_redirect
redirected→Inconnu
probe_inconclusive
Inconnu→redirected
http_redirect
redirected→Inconnu
probe_inconclusive
Inconnu→redirected
http_redirect
redirected→Inconnu
probe_inconclusive
Inconnu→redirected
http_redirect
redirected→Inconnu
probe_inconclusive
Inconnu→redirected
http_redirect
redirected→Inconnu
probe_inconclusive
Inconnu→redirected
http_redirect
redirected→Inconnu
probe_inconclusive
Inconnu→redirected
http_redirect
Inconnu
probe_inconclusive
Indisponible→Accessible
https://radar.cloudflare.com/scan/e29f83e0-340f-4910-bbe3-5583d4996cc4
Accessible→Indisponible
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
Template-based draft · optional AI wording assistance requires separate consent
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerRapports de phishing récents et changements de disponibilité observés
SurveillerSurveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif