VirusTotal
9 / 92
“XRP Desk”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse-complaints@squarespace.com.
The latest stored availability evidence still shows the domain reachable; 16 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.
xrpdesk.app — Bilinen son aktif (HTTP 200). Marka kimliğine bürünme: MetaMask; Dolandırıcılık türü: Impersonation. Kanıt özeti: VirusTotal 9/92 (alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet); URLQuery 2 det.; PhishDestroy score 93/100. Kayıt kuruluşu: Squarespace Domains II.
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
Stored evidence for xrpdesk.app: VirusTotal recorded 2 detections among 91 scanners on 2026-09-25. 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 xrpdesk.app. Each item in this report remains at the scope supplied by its dated source record.
VirusTotal records 2 detections among 91 scanners in the stored snapshot dated 2026-09-25. 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-25 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.
MetaMask and SEAL are recorded as named external blocklist observations for xrpdesk.app in the snapshot dated 2026-09-25. 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 xrpdesk.app 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.
The record first observed xrpdesk.app on 2026-09-25. The MetaMask and SEAL blocklist snapshot is dated 2026-09-25 and remains a separate event in the stored timeline. A stored HTTP status 200 was observed for xrpdesk.app on 2026-09-25. The HTTP status 200 dated 2026-09-25 records a single response for later comparison. The registration date is separately recorded as 2026-09-23. A URLScan reference was stored on 2026-09-25 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.
For xrpdesk.app, the registrar field records Squarespace Domains II LLC.; this is kept as an exact source value. The source stores 216.24.57.1 as the observed address in this record. The registration date for xrpdesk.app is recorded as 2026-09-23. The SSL issuer is recorded as Google Trust Services / WE1 in the snapshot dated 2026-09-25. The stored ASN observation records 397273 and Render 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.
The xrpdesk.app record states that VirusTotal recorded 2 detections among 91 scanners on 2026-09-25. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-25. PhishDestroy remains a separate publisher catalogue entry in the stored record. For xrpdesk.app, the registrar field records Squarespace Domains II LLC.; this remains separate from the other source fields. The observed address field in this record contains 216.24.57.1. The supported conclusion is bounded to the exact stored observations for xrpdesk.app. Any statement beyond those source values would require additional dated material.
Avoid submitting sensitive information to xrpdesk.app during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain xrpdesk.app 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 xrpdesk.app. The stored record does not justify extending that rule to 216.24.57.1 or to other infrastructure records.
Bu ana bilgisayar için saklanmış tarayıcı-karşı-tarayıcı gözlemleri ile Keitaro tarzı trafik dağıtım sistemleri için gerçek zamanlı parmak izi kontrolü.
cloudflareTarayıcı notu: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
For this gTLD, 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.
Edge-IP itibarı bu etki alanıyla ilişkilendirilmez.
nsc1.squarespacedns.comnsc2.squarespacedns.comnsc3.squarespacedns.comnsc4.squarespacedns.comLocation describes the IP network.
59fcf2a99189a596f474496385e771c7aace4600f1c0c77614ae11da59bd3b37Saved 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 xrpdesk.app · checked Sep 25, 2026
216.24.57.1. 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.
79 kayıtlı benzer alan adı
PD-20260925-CC3905 Recipient: abuse-complaints@squarespace.com Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (Unknown): International Anti-Cybercrime Regulations Budapest Convention on Cybercrime Universal Fraud Prevention Laws Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
Hesap kimlik bilgilerini, kişisel bilgileri veya ödeme bilgilerini girdiyseniz ya da bu alan adından bir dosya indirdiyseniz hemen harekete geçin. Aşağıda olayı bildirmenize ve kendinizi korumanıza yardımcı olacak kaynaklar bulunmaktadır.
resmi siber suç iletişim bilgileri veya şikayet taslağı oluştur → almak için ülkenizi seçin.
Template-based draft · optional AI wording assistance requires separate consent
Saklanan engelleme listesi, WHOIS, DNS ve genel tarama kanıtlarını kullanarak tehdit analizi
Şimdi TaraŞüpheli alan adlarını tehdit veritabanımıza bildirin — topluluğu koruyun
BildirSon kimlik avı raporları ve gözlemlenen kullanılabilirlik değişiklikleri
İzleCanlı tehditleri izleyin veya bunun yanlış bir uyarı olduğunu düşünüyorsanız bu kayda itiraz edin