VirusTotal
14 / 91
SignalerInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Urvlentoki™ Official Website 2026 | Advanced AI Trading & Investment Platform”
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 26 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.
urvlentoki-platform.com — Dernier actif connu (HTTP 200). Type d'arnaque : Impersonation. Résumé des preuves: VirusTotal 14/91 (alphaMountain.ai, Bfore.Ai PreCrime, BitDefender, CRDF, ESET); URLQuery 5 alerts; CF Radar malicious; PhishDestroy score 100/100. Bureau d’enregistrement: Dynadot.
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.
14 / 91
SignalerEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
5 threat-system alerts
SignalerAlerts refer to the preserved scan. They do not describe the current state of the site.
provider verdict: malicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
4 community references
SignalerCommunity publication references, not a vendor verdict or evidence of a common operator.
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.
0 external matches
DétailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | urvlentoki-platform.com |
malicious | Sinkholed |
| Quad9 DNS | urvlentoki-platform.com |
malicious | Sinkholed |
| OpenDNS | urvlentoki-platform.com |
phishing | Phishing Block |
| Cloudflare DNS | urvlentoki-platform.com |
malicious | Sinkholed |
| DigiCert UltraDNS | urvlentoki-platform.com |
malicious | Sinkholed |
Stored narrative · generated . Provider checks below retain their own observation dates.
urvlentoki-platform.com returned HTTP status 200 on 2026-10-01, according to the recorded HTTP check. The domain's registration date is listed as 2026-06-24 with Dynadot Inc as registrar.
The PhishDestroy internal listing was recorded as true, and the OTX check on 2026-09-20 counted 4 pulses. VirusTotal, checked on 2026-09-29, reported 14 detections across 91 scanners. The HTTP check on 2026-10-01 returned status 200, while the SSL scan on 2026-09-19 identified Google Trust Services / WE1 as issuer. The first observation of urvlentoki-platform.com was recorded on 2026-09-19, the same date as a PageSpeed performance score of 92.
The PhishDestroy listing and the OTX pulse count were recorded on different dates, so their observations reflect separate moments rather than a single snapshot. VirusTotal's 2026-09-29 check and the 2026-10-01 HTTP response also fall on different days, meaning the records describe distinct points in time. Because the SSL scan and first observation share 2026-09-19, those two records can be compared directly, while later checks cannot be aligned to that same moment.
Reviewers should retain the dated records for urvlentoki-platform.com, including the PhishDestroy listing, OTX count and VirusTotal result, so later comparisons use the same sources. Any subsequent check should be dated and compared against these entries rather than treated as a replacement. During review, avoid submitting sensitive information to the domain until the recorded observations have been independently verified.
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.
La réputation Edge-IP n’est pas attribuée à ce domaine.
meg.ns.cloudflare.comweston.ns.cloudflare.comLocation describes the IP network.
b39104ca9df6708ae68dd9cfd38ee80f3c64a10b93a02e30867bab8477a4583fSaved 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 urvlentoki-platform.com · checked Sep 19, 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: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
104.21.33.215.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Inconnu→live_content
content_served
live_content→Inconnu
probe_inconclusive
Inconnu→live_content
content_served
live_content→Inconnu
probe_inconclusive
Inconnu→live_content
content_served
live_content→Inconnu
probe_inconclusive
Inconnu→live_content
content_served
live_content→Inconnu
probe_inconclusive
Inconnu→live_content
content_served
live_content→Inconnu
probe_inconclusive
Inconnu→live_content
content_served
live_content→Inconnu
probe_inconclusive
Inconnu→live_content
content_served
live_content→Inconnu
probe_inconclusive
Inconnu→live_content
content_served
live_content→Inconnu
probe_inconclusive
Inconnu→live_content
content_served
live_content→Inconnu
probe_inconclusive
Inconnu→live_content
content_served
live_content→Inconnu
probe_inconclusive
Inconnu→live_content
content_served
live_content→Inconnu
probe_inconclusive
live_content→Inconnu
stale_current_evidence
Inconnu→live_content
content_served
Inconnu→live_content
content_served
live_content→Inconnu
probe_inconclusive
Inconnu→live_content
content_served
live_content→Inconnu
probe_inconclusive
Inconnu→live_content
content_served
Inconnu
probe_inconclusive
Inconnu
11 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.
PD-20260919-47E4B1 Recipient: abuse@dynadot.com 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
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