Aller au rapport de sécurité
Tableau de bord analytique
Sécurité des domaines et renseignements sur les menaces
linked-pay-service.com favicon

linked-pay-service.com

“Linkedpay - карты и платежи в Telegram”

Verdict de menace
CritiqueRecours en matière de nom de domaine
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Disponibilité Dernier actif connu Dernière observation d'accessibilité stockée Observé · HTTP probe
Signaux de risque
Détections VirusTotal : 4/92 Correspondances de la liste de blocage stockée : 2 Usurpation de l'identité de la marque : Telegram
OTX: 3 refs 27/09/2026 Telegram CDN
API
Bureau d’enregistrement
Cloudflare
Resolved IP
172.67.170.112
Registered
18/08/2026
Capture enregistrée 1 / 3 View full size
Primary capture Wayback
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 4. Listes de blocage publiques signalant une correspondance : 2. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
Résumé du rapport

linked-pay-service.com — Dernier actif connu (HTTP 200). Usurpation de l'identité de la marque : Telegram; Type d'arnaque : Impersonation. Résumé des preuves: VirusTotal 4/92 (alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar); 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 88/100. Bureau d’enregistrement: Cloudflare.

L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.

Additional indicators at a glance
VirusTotal
VirusTotal
4 det.
OTX references
3 community refs
URLScan
URLScan
Signaler ↗
Certificat TLS
Expiré ou non vérifié
Âge
2 mo New
Statut observé
Dernier actif connu 200
PhishDestroy
DestroyList
Répertorié

Source evidence

6 sources

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.

VirusTotal

4 / 92

Signaler
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

OTX

3 community references

Signaler
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Signaler
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

rapport stocké

Stored URLScan capture preview
Signaler
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analyse terminée

Signaler
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Signaler
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Résumé des preuves

Critique
VirusTotal
4/92
OTX
3 community refs
URLScan
Stored capture

Stored narrative · generated . Provider checks below retain their own observation dates.

Assessment

Stored evidence for linked-pay-service.com: VirusTotal recorded 1 detections among 91 scanners on 2026-09-28. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for linked-pay-service.com. Each item in this report remains at the scope supplied by its dated source record.

Detection Evidence

VirusTotal records 1 detections among 91 scanners in the stored snapshot dated 2026-09-28. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-28 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.

Source Context

MetaMask and SEAL are recorded as named external blocklist observations for linked-pay-service.com in the snapshot dated 2026-09-28. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains linked-pay-service.com as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.

Reachability and Timeline

The record first observed linked-pay-service.com on 2026-09-27. The MetaMask and SEAL blocklist snapshot is dated 2026-09-28 and remains a separate event in the stored timeline. A stored HTTP status 200 was observed for linked-pay-service.com on 2026-09-28. The HTTP status 200 dated 2026-09-28 records a single response for later comparison. The registration date is separately recorded as 2026-08-18. A URLScan reference was stored on 2026-09-27 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.

Registration and Infrastructure

For linked-pay-service.com, the registrar field records Cloudflare, Inc.; this is kept as an exact source value. The source stores 172.67.170.112 as the observed address in this record. The registration date for linked-pay-service.com is recorded as 2026-08-18. The SSL issuer is recorded as Google Trust Services / WE1 in the snapshot dated 2026-09-27. The stored ASN observation records 13335 in this record. The observed server header is recorded as cloudflare in this record. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.

Conclusion

The linked-pay-service.com record states that VirusTotal recorded 1 detections among 91 scanners on 2026-09-28. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-28. PhishDestroy remains a separate publisher catalogue entry in the stored record. For linked-pay-service.com, the registrar field records Cloudflare, Inc.; this remains separate from the other source fields. The observed address field in this record contains 172.67.170.112. The supported conclusion is bounded to the exact stored observations for linked-pay-service.com. Any statement beyond those source values would require additional dated material.

Recommended Actions

Avoid submitting sensitive information to linked-pay-service.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain linked-pay-service.com as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to linked-pay-service.com. The stored record does not justify extending that rule to 172.67.170.112 or to other infrastructure records.

Extracted from stored page analysis

Observed indicators

0 wallet · 1 Telegram

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

Telegram
https://t.me/linked_pay_botStored page reference

IoC extraction recorded 2026-09-28 04:00:09 UTC

Analyse de la détection et de l'évasion

Suspicion de cloaking : les titres du scanner et ceux des visiteurs diffèrent

Pas encore numérisé Aucune différence entre les robots d'indexation et les navigateurs n'a encore été constatée

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.

Indicateur de camouflage enregistré
Pas encore numérisé
Dernier scan de camouflage
En-tête du serveur détecté par le scanner
cloudflare

Note relative à la numérisation: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare

Titre affiché sur le scanner de sécuritéLinkedpay - карты и платежи в Telegram
Titre affiché pour un visiteur du navigateurLinkedpay - карты и платежи в Telegram
Vérification en direct des empreintes digitales d'TDS
Sept empreintes Keitaro ainsi qu’une comparaison entre robot d’indexation et navigateur, générées par le scanner PhishDestroy lorsque ce panneau est ouvert.
En attente

Capture enregistrée · 3 captures

Primary capture 1 / 3
SourcePrimary capture
Recorded2026-09-27 14:46 UTC
StateStored capture
Position1 / 3
Open capture Wayback Télécharger

Domain details

Domaine
URLScan Verdict Analyse terminée score 0 report ↗
Observed indicators0 wallet · 1 Telegram — full values ↗
IP Context Cloudflare shared edge origin IP hidden La réputation Edge-IP n’est pas attribuée à ce domaine.
OTX Tags 2026-09activeall-domainsblocklistcontentcryptodomainesdrainerfraudmonthlyphishdestroyphishingscam
Bureau d’enregistrement Cloudflare US(US)
Contact anti-abus["registrar-abuse@cloudflare.com"]
Registre de l'ICANNICANN Lookup (RDAP) →
Recherche WHOISICANN RDAP pour linked-pay-service.com →
EnregistrementCréé 18/08/2026 (57d · New) — Expires 18/08/2027
Statut HTTP200
Détails techniquesProvenance & timestamps
Première détection27/09/2026
DOM Analysisanalyzed 09/10/2026score 88/1002 brand signals
IoC Extractionscanned 28/09/20260 wallet · 1 Telegram IoC
Submitted URLhttp://linked-pay-service.com/
Favicon Hash
Titre de la page
Linkedpay - карты и платежи в Telegram
Impersonates
Apple Telegram
Certificat TLS
Hostname coverage not recorded · Émis par Google Trust Services / WE1 · stored validity ends in 32 days

Network & certificates

Stored technical evidence

Network & DNS

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

La réputation Edge-IP n’est pas attribuée à ce domaine.

Serveurs de noms 2

  • alexis.ns.cloudflare.com
  • eve.ns.cloudflare.com

Location describes the IP network.

Certificat TLS

Issuer
Google Trust Services / WE1
Valid from
2026-08-18 09:16:42
Valid until
2026-11-16 10:15:31
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-11 07:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprint9fdc4cbf4c3b75612db6b1bacd8945070c325cfe55c72b5e42deef087a731df5

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

viewdns.info · 172.67.170.112rapiddns.io

Latest Classified Outcome 2026-10-14 10:26:01 UTC

Primary outcome Contenu actif 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 Contenu actif Ordinary HTTP content served 90% 2026-10-14 10:26:01 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-14 10:26:01 UTC last content: 2026-10-14 10:26:01 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
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

4 / Les fournisseurs de sécurité 92 ont signalé ce domaine
View on VT
Last analyzed First positive detection Previous stored snapshot: 4 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar
Analyse des performances du site

Google PageSpeed Insights — mobile performance audit of linked-pay-service.com · checked Sep 27, 2026

92
Good
Performance
FCP
2.56s
First Contentful Paint
LCP
2.71s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.56s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. VirusTotal Detections Update 2026-09-27 23:26:28 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: Forcepoint ThreatSeeker.
  2. Threat First Observed 2026-09-27 14:42:33 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.170.112.

Processus de réponse aux menaces Pipeline

Découverte
Analysis
Monitoring

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

Menace détectée
linked-pay-service.com détectés et mis en file d'attente en vue d'une analyse complète
27/09/2026
URLScan.io Capture
Enregistré URLScan report with capture artifacts
27/09/2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
VirusTotal
4/92 recorded on VirusTotal
10/10/2026
Détection des listes noires
Trouvé dans 2 blocklists: MetaMask, SEAL
15/10/2026
OTX Community References
3 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
28/09/2026
Brand Impersonation
Impersonation of Telegram
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
27/09/2026
Technical Analysis Recorded
Le rapport contient des résultats de technologie ou d’analyse médico-légale stockés.
15/10/2026
VT Detection +1
+1 new detection (0 → 1): Forcepoint ThreatSeeker
28/09/2026
DestroyList publié
Listed in the public PhishDestroy/DestroyList repository
27/09/2026
Monitoring Continues
Le domaine reste accessible ou restreint en accès ; des contrôles futurs pourraient mettre à jour cette observation.
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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecÉvaluation du site AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Statut de la liste de blocage publique

Données factuelles et rapports externes

Analyse de sécurité
URLScan Analyzed VirusTotal 4 det. ChainPatrol URLQuery SSL Laboratoires Hostname coverage not recorded CF Radar Ouvrir le rapport OTX 3 refs WOT ScamAdviser Vérificateur de liste noire URL nulle Sucuri SiteCheck Observatoire MDN
OSINT et renseignement
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certificats WHOIS Wayback
DNS et réseau
nslookup.io DNS bgp.tools ASN /Itinéraire
Référencement naturel et nom de domaine
SpyFu Moz DA/PA Ahrefs Liens entrants
Analyse approfondie
Analyse approfondie

Ce site vous a-t-il affecté ?

4 evidence signal groups linked 0 reports recorded Dernier actif connu
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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.

Europol
Trouvez le canal de signalement officiel pour votre pays de l'UE
National police directory
PhishDestroy listing review Pas un rapport des forces de l'ordre
Recours en matière de nom de domaine
Demandez un examen si vous possédez ce domaine et pensez que la liste est incorrecte
Méfiez-vous des escrocs qui prétendent vous aider à récupérer vos biens ! Les criminels peuvent recontacter leurs victimes tout en se faisant passer pour des enquêteurs, des avocats ou des agents de recouvrement. Ne payez pas de frais initiaux et ne partagez pas vos informations d'identification. En savoir plus sur la fraude liée aux aides à la reprise →

Signalez-le à vos autorités locales

Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.

Annuaire de 97 pays

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

Brouillon assisté par l'IA : les détails de l'incident sont traités par le fournisseur d'IA · Examinez-le et soumettez-le vous-même

Vérifier n'importe quel domaine

Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique

Scanner maintenant

Signaler une tentative d'hameçonnage

Signalez les domaines suspects à notre base de données des menaces — protégez la communauté

Signaler

Flux d'alertes en temps réel

Rapports de phishing récents et changements de disponibilité observés

Surveiller

Restez informés, restez en sécurité

Surveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif

Flux d'alertes en temps réel Contester cette annonce
HTML · IFRAME

Intégrer ce rapport

Partagez ces informations sur les menaces sur votre site web ou votre blog

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